Enyby

Try another firmware/another device/get root.

Try. Maybe try another firmware.

Yes. Something wrong with your firmware. 05-11 10:36:36.069 2501 2501 I android-daemon: mem: 0 05-11 10:36:36.069 2501 2501 I android-daemon: mem: 2 05-11 10:36:36.069 2501 2501 I android-daemon: mem: 1 05-11 10:36:36.069 2501 2501 I android-daemon: init 105 ... 05-11 10:36:36.069 2501 2501 I android-daemon: old umask: 77 05-11 10:36:36.071 2412 2496 W AndroidService: getArch: /data/user/0/io.va.exposed/virtual/data/user/0/com.qfuwfktqbjnxyapmclde/files/GG-466686090/lib5.so 05-11 10:36:36.071 2412 2496 W AndroidService: java.io.IOException: Cannot run program "/data/user/0/io.va.exposed/virtual/data/user/0/com.qfuwfktqbjnxyapmclde/files/GG-466686090/lib5.so": error=-1005993984, Unknown error -1005993984 05-11 10:36:36.071 2412 2496 W AndroidService: at java.lang.ProcessBuilder.start(ProcessBuilder.java:983) 05-11 10:36:36.071 2412 2496 W AndroidService: at java.lang.Runtime.exec(Runtime.java:691) 05-11 10:36:36.071 2412 2496 W AndroidService: at java.lang.Runtime.exec(Runtime.java:559) 05-11 10:36:36.071 2412 2496 W AndroidService: at android.ext.DaemonLoader.getArch(DaemonLoader.java:299) 05-11 10:36:36.071 2412 2496 W AndroidService: at android.ext.DaemonLoader.getDaemonPath_(DaemonLoader.java:274) 05-11 10:36:36.071 2412 2496 W AndroidService: at android.ext.DaemonLoader.<init>(DaemonLoader.java:132) 05-11 10:36:36.071 2412 2496 W AndroidService: at android.ext.DaemonLoader.getDaemonPath(DaemonLoader.java:62) 05-11 10:36:36.071 2412 2496 W AndroidService: at android.ext.DaemonManager$31.run(DaemonManager.java:1694) 05-11 10:36:36.071 2412 2496 W AndroidService: Caused by: java.io.IOException: error=-1005993984, Unknown error -1005993984 05-11 10:36:36.071 2412 2496 W AndroidService: at java.lang.UNIXProcess.forkAndExec(Native Method) 05-11 10:36:36.071 2412 2496 W AndroidService: at java.lang.UNIXProcess.<init>(UNIXProcess.java:133) 05-11 10:36:36.071 2412 2496 W AndroidService: at java.lang.ProcessImpl.start(ProcessImpl.java:128) 05-11 10:36:36.071 2412 2496 W AndroidService: at java.lang.ProcessBuilder.start(ProcessBuilder.java:964) 05-11 10:36:36.071 2412 2496 W AndroidService: ... 7 more Daemon started but GG get "error=-1005993984, Unknown error -1005993984". As I write above: You need check this.

You must write down the log, and not show me the screen. _______________________________________________ added 1 minute later In the previous log record, you did not run GG, but should. You should have run GG while writing the log, only then the log is useful.

In your case - launch GG via VirtualXposed. Wait for message from your screen.

File empty. It is very odd. Need record logcat via adb. How to collect logcat (#c1aa00vp) I think you not give for Virtual space some permissions. Maybe your firmware have custom runtime permisiions.

@298088_1434558260 Start GG, Press "fix it" button, select "record logcat", wait for restart gg, reproduce issue, close gg, sent logcat file to me.

@Ariboyes Read the first post and provide everything that it says.

Look like all ok.

There can be many solutions. starting from the bad option - use in each submenu of its cycle, ending with the normal option - using one cycle and storing the current state, and on it already open the desired menu. These are already nontrivial things, which strongly depend on the overall structure of the code, your knowledge and skills.

Go to is bad. And go to to other function can lead to unpredictable things or not work at all.

Function call is not a go to. If you do not run other part code you must use else block of the if. And use indentation will be good for easy read code. if gg.getResultCount() ~= 3 then zabissk() else -- other code end