If the Android Studio emulator hangs with a black screen, try checking the LogCat messages and try switching graphics mode. Noticed that the emulator was configured to use software graphics.Ĭhanged this to hardware graphics, started the emulator again and noticed that it started normally. I/ServiceManager(17212): debuggerd: Unable to connect to activity manager (connect failed: Connection refused)ĭecided to check the emulator configuration. I/ServiceManager(17212): Waiting for service SurfaceFlinger. Initializing graphics H/W.ĭ/libEGL(17248): Emulator has vendor provided software renderer, qemu.gles is set to 2.ĭ/libEGL(17248): loaded /vendor/lib/egl/libEGL_swiftshader.soĭ/libEGL(17248): loaded /vendor/lib/egl/libGLESv1_CM_swiftshader.soĭ/libEGL(17248): loaded /vendor/lib/egl/libGLESv2_swiftshader.soĭ/gralloc_ranchu(17248): Emulator without host-side GPU emulation detected.Į/gralloc_ranchu(17248): Could not find software fallback module!?Į/gralloc_ranchu(17248): Į/gralloc_ranchu(17248): connect: failed with fd -1 errno 22Į/gralloc_ranchu(17248): Failed to connect to host (QemuPipeStream)!!!Į/gralloc_ranchu(17248): gralloc: Failed to get host connectionĮ/SurfaceFlinger(17248): hwcomposer module not foundĮ/SurfaceFlinger(17248): ERROR: failed to open framebuffer (I/O error), abortingĪ/libc(17248): Fatal signal 6 (SIGABRT), code -6 in tid 17248 (surfaceflinger)Ī/libc(17248): Ī/libc(17248): debuggerd: handling request: pid=17248 uid=1000 gid=1003 tid=17248 I/SurfaceFlinger(17248): SurfaceFlinger's main thread ready to run.
I/SurfaceFlinger(17248): SurfaceFlinger is starting I decided to pause the emulator to examine the log.įound and followed Christoper Orr’s advice here: telnet localhost 5554Ĭhecked the LogCat messages and noticed this section: I/ServiceManager(16997): Waiting for service SurfaceFlinger.
Emulator on the Windows platform Pros: I can play wid out any crash Feb 25. LogCat showed a lot of messages and they seemed to repeat over and over. Droid4x Free Android Emulator for Windows & Mac 2020 Read More Aug 26. To investigate I connected Android Device Monitor to the emulator. It just showed a black screen with no apparent progress. I recently experienced a situation where Android Studio’s x86 emulator would not start.