Problems with emulator on Windows

[rupak0577]

1. Processing keeps waiting indefinitely for the emulator to become available even after it has completed the boot process. This is probably because this line is not getting executed which means there is a problem with runADB() on Windows. Maybe Processing is trying to execute adb instead of adb.exe?

2. Rerunning a sketch after closing the emulator does not restart it and Processing keeps waiting for it to become available.

3. The watch emulator does not start while the phone emulator is running.

[codeanticode]

@rupak0577 Ok, interesting point. I have been able to run the emulator on Windows 10 without any errors, although I can see that indeed the command in runABD() includes adb instead of adb.exe. Did you try inserting the extension?

Actually, I had a similar problem with zipalign, which I solved by adding the .exe, so this might be the solution here as well. I'm surprised that I can execute abd on my computer. Any thoughts?

[rupak0577]

@codeanticode The issue is because Processing tries to run adb as a system-wide command and not directly from the sdk directory, like it was doing with the emulator.

[codeanticode]

ok, made these changes so runADB is not static anymore so it can use the platformTools path... did a quick test and seems to be ok, could you double check on your system?

Still, the process launch/exec seems a bit messy, some parts use ProcessHelper(adbCmd).execute(), while others Runtime.getRuntime().exec(cmd), not sure why the reason why. This generateAdbCommand() method is kind of confusing too. Would be nice to refactor these things, so process execution is done consistently.

[rupak0577]

Unfortunately it is still not working(no problems on Linux though). Seems like the problem is elsewhere.

[rupak0577]

Can't believe it was the \n...All issues fixed with commit c7b1139