ABD Connection?

[PrincessHope25]

upon startup it says "abd connection" fails 5 times and then gets stuck.

Ive tried restarting my pc and once it worked but then only pinged the top left of the screen and thus couldnt pick the date set.

old version (4.1) works fine with no issues

[rayofshadow23]

Hello there, i have the same issue. But only on istance 1 (1.ahk). All the others work correctly..
@Arturo-1212 how can i debug/log the ADB connection failure?

[rayofshadow23]

[Luneye]

Just go in your task manager, type in the search bar adb and kill every adb processes. Then restart the bot.

[rayofshadow23]

Done, still the same issue

[Luneye]

Here is how you can debug this. Please just start Instance 1 on MuMu, but do not run the Arturo's Bot, make sure to close any running AutoHotKey scripts.

1. Open MuMu MultiPlayer 12. Look up for the ADB button, on the top right corner.

2. Click on this button and locate the ADB port that the instance 1 should be using.

Save this value in mind, you will need it for the next step.

3. Open a terminal (cmd) and type in the following command:
   cd C:\Program Files\Netease\MuMuPlayerGlobal-12.0\shell
   if C:\Program Files\Netease\MuMuPlayerGlobal-12.0\ is where your MuMu folder is located

Then type this command:
adb connect 127.0.0.1:adb_Port_Instance_1

Replace the adb_Port_Instance_1 with the one you found in step 3.

This should be what the command returns. If not, send me your screenshot.

[rayofshadow23]

@Luneye using VS code and a debugger for AHK i've discovered that the first istance was trying to connect to port 16384, instead of 16416. Thanks to your screen I've realized that the error could have been the fact that the main account and the first "usable" istance were both named: "1".
Now I renamed the very first istance "main_account", and everything is working fine

thanks!