Problems with the emulator across platforms?

[codeanticode]

Testing the emulator with the latest release (4.0.2) and also the previous one, it seems that the emulator hangs during startup on Linux, Windows, and Mac. Need to do further testing.

[q2dg]

If it helps, I offer myself as a tester.

I use Processing Android 4.0.2 in Fedora 28 x86-64 with Android SDK installed by default options (that is, I haven't touched anything by hand; everything has installed through popups offered by Processing). My problem is "Lost connection with emulator while launching. Try again". I'm using x86 emulator instead of ARM's one.

[codeanticode]

@q2dg Thanks a lot! Yes, need to look into that "Lost connection" error, I have seen it popping up from time to time.

[codeanticode]

The situation might not be as hopeless as I originally thought. Tested the emulator on Mac, Windows, and Linux using the most recent versions of Processing and the Android mode (3.5.3 and 4.0.4, respectively) and I was able to install and the sketch in the emulator on the first two. Installation fails on Linux with the following error:

Emulator process exited with status 1.
EmulatorController: Emulator never booted. NOT_RUNNING
Error while starting the emulator. (NOT_RUNNING)

[codeanticode]

Tested emulator with latest version of the mode, 4.2.1. It works on Linux (Ubuntu 20.04) and macOS Catalina (although HAXM authorization fails in the latter). It doesn't work on Windows 10 (with the error EmulatorController: Emulator never booted. NOT_RUNNING, Error while starting the emulator. (NOT_RUNNING))

[BUZDOLAPCI]

Tested emulator with latest version of the mode, 4.2.1. It works on Linux (Ubuntu 20.04) and macOS Catalina (although HAXM authorization fails in the latter). It doesn't work on Windows 10 (with the error EmulatorController: Emulator never booted. NOT_RUNNING, Error while starting the emulator. (NOT_RUNNING))

Running Processing with Admin rights seems to fix this issue for me, not sure if it's the same case with you.

[codeanticode]

Ok, thanks for the info. I'd say that running as admin could be useful as a workaround, but the emulator should run without requiring it :-)

[codeanticode]

Using the --skin argument (806def2) and with recent device art pulled from Android Studio (e254f20, 2ad6507) seems to solve most of the issues with the emulator