|
Post by AnkuLua on Mar 4, 2018 1:20:31 GMT
Some devices can set the permission of background app to use network. Please make sure that AnkuLua can use network in background. Please also turn off all power saving features.
|
|
drekx
New Member
Posts: 31
|
Post by drekx on Apr 13, 2018 1:54:55 GMT
I have recently started getting errors on 2 scripts. The errors are both similar as in it hits a IOException error after looping through script between 20-30 times. This happens to both an ffbe script and the snap/play script, they both use to work no problem for me. I have tried also on both Memu and on my S8+ and it's pretty much the same thing unfortunately. Once the error shows up it's impossible to run any scripts anymore as they will crash either at beginning or at end of main loop, only way to fix this to be able to run scripts again is to restart the device.
FFBE Auto: Runtime error: java.io.IOException: Result 255Result255Result 255 stack traceback: [C]: in function 'click' ?: in function 'click' /sdcard/Download/FFBEAutoZ20/FFBEAutoZ.lua:1390: in function 'ese_speed' /sdcard/Download/FFBEAutoZ20/FFBEAutoZ.lua:3844: in main chunk
Snap & Play: Runtime error: java.io.IOException: Result 255Result 255Result 255 stack traceback: [C]: in function 'click' ?: in function '?' /sdcard/Download/snapAndPlay.v1.9.0.lua:864: in function 'playback' /sdcard/Download/snapAndPlay.v1.9.0.lua:912: in main chunk
|
|
|
Post by AnkuLua on Apr 13, 2018 6:15:25 GMT
Do those devices run on daemon or root? If root, please turn off notification and log.
|
|
drekx
New Member
Posts: 31
|
Post by drekx on Apr 13, 2018 6:52:44 GMT
Do those devices run on daemon or root? If root, please turn off notification and log. On Memu it runs on root and on the S8+ it runs on daemon. I have turned off all notifications, not sure where to turn off log. Edit: Tried it but still same issue for both scripts.
|
|
|
Post by bakemono on Mar 24, 2019 8:44:30 GMT
What's the largest action list that you can feed to the manualTouch command?
I want to create a dynamic touch condition of 450-550 clicks in a region in 30 seconds. ContinueClick seems too static and robotic like, so I tried to create a dynamic action table
table.insert(actionList, {action = "touchDown", target = Location(randx, randy)}) table.insert(actionList, {action = "wait", target = (randMSWait / 1000.0)})
I have this in a loop that cycles 450-550 times thus creating 900-1100 table values
When I run this actionList in manualTouch I get after about 300+ taps:
Runtime error: java.io.IOException: Socket read timeout.Socket read timout.Socket read timeout. stack trackeback: [C]: in function 'manualTouch' ?: in function 'manualTouch'
Any ideas? I'm running Daemon and have tried rebooting the device.
|
|
|
Post by bakemono on Mar 24, 2019 9:01:00 GMT
I followed an option to turn on Beta fast touch and click, that did the trick! It doesn't bomb out like previously. I set the touchDown to 1.0 ms and extra time to 0.0. Is there any issues with doing these low values?
Edit: Looks like 1.0 ms was too quick on some objects in the game. Moved it to 30.0 ms as the default value was that and then incorporated a 30.0 ms reduction in the time between to account for the change.
Edit 2: Looks like Beta fast touch won't click through certain screens. Is there anything we can do about this? It's when the game takes over the entire screen and you can click anywhere on the screen but it's not registering any of the clicks that are happening with the Beta fast touch. But as soon as I manually touch the screen it completes and I can continue.
|
|
|
Post by bleakstare on Jun 2, 2019 23:53:44 GMT
When I run mine occasionally I get this error
Runtime error: java.io.IOException: Accessibility mode does not supportkillApp() stack traceback: {C}: in function 'killApp' ?: in function 'killApp' [string "roclickersummonerswar.luae2"}:5036: in function 'a234547708790768795421321435433443543'
running it on a galaxy s8 active. not using daemon or root doing it with accessibility mode.
not sure if this is the correct place to post this.
|
|
|
Post by Acera on Jun 3, 2019 10:51:32 GMT
When I run mine occasionally I get this error Runtime error: java.io.IOException: Accessibility mode does not supportkillApp() stack traceback: {C}: in function 'killApp' ?: in function 'killApp' [string "roclickersummonerswar.luae2"}:5036: in function 'a234547708790768795421321435433443543' running it on a galaxy s8 active. not using daemon or root doing it with accessibility mode. not sure if this is the correct place to post this. The script you are using uses a function that is not supported by Accessibility Mode. So you need to switch to daemon or root.
|
|
|
Post by kittycatz on Jan 7, 2020 10:46:13 GMT
Using MEMU latest version. No daemon/root.
Any idea how to solve this? Thanks!
|
|
|
Post by AnkuLua on Jan 7, 2020 10:56:30 GMT
Using MEMU latest version. No daemon/root.
Any idea how to solve this? Thanks!
Try daemon or other emulator.
|
|
|
Post by kittycatz on Jan 7, 2020 11:04:23 GMT
which emulator you suggests? bluestacks 1?
|
|
oggie
New Member
Posts: 16
|
Post by oggie on Jan 11, 2020 16:16:24 GMT
This is happenig more and more often now since the latest version. I have tried all the options and get the error every once in a while. I also have had the experience that the Ankulua script just stops without any error (I find the Play button instead of the Stop button).
Could a better exception handling be implemented in Ankulua, so that the interpreter and service can recover from these type of Exceptions and issues?
|
|
|
Post by AnkuLua on Jan 12, 2020 0:14:09 GMT
This is happenig more and more often now since the latest version. I have tried all the options and get the error every once in a while. I also have had the experience that the Ankulua script just stops without any error (I find the Play button instead of the Stop button). Could a better exception handling be implemented in Ankulua, so that the interpreter and service can recover from these type of Exceptions and issues? What's your device or emulator? If emulator, try increase memory or changing CPU number. What's the Android version? Which method did you use, root, daemon or media projection?
|
|
oggie
New Member
Posts: 16
|
Post by oggie on Jan 12, 2020 14:17:39 GMT
This is happenig more and more often now since the latest version. I have tried all the options and get the error every once in a while. I also have had the experience that the Ankulua script just stops without any error (I find the Play button instead of the Stop button). Could a better exception handling be implemented in Ankulua, so that the interpreter and service can recover from these type of Exceptions and issues? What's your device or emulator? If emulator, try increase memory or changing CPU number. What's the Android version? Which method did you use, root, daemon or media projection? I'm using Nox with Android 5 emulator. It has the same CPU and memory settings as always and was working fine before. After new version, the issues began. I run with daemon, but have tried root with same results. It seems like a memory management issue. Often I see the exception, and sometimes ankulua just stops without any message whatsoever. And it is the same script that I've been using for years.
|
|
|
Post by AnkuLua on Jan 12, 2020 15:12:28 GMT
What's your device or emulator? If emulator, try increase memory or changing CPU number. What's the Android version? Which method did you use, root, daemon or media projection? I'm using Nox with Android 5 emulator. It has the same CPU and memory settings as always and was working fine before. After new version, the issues began. I run with daemon, but have tried root with same results. It seems like a memory management issue. Often I see the exception, and sometimes ankulua just stops without any message whatsoever. And it is the same script that I've been using for years. Please assign more memory. Sometimes, the game update may consume more memory. You may try one CPU. Some users reported that one CPU is more stable. Or you could try "Clean up disk space" in nox System settings.
|
|