My Android emulator for a Pixel 2 running Android Oreo (v26) suddenly started showing a pink and green pixelated screen every time it starts up. I am unable to recover it and it has not managed to boot successfully since.
I am running Ubuntu 17.10 and Android Studio 3.0.1, running NVIDIA display driver 384.90.
So far I have tried forcefully killing the emulator to prevent booting from a saved state, rebooting my workstation, and switching to the X.Org video driver. None of these have had any effect, and using the X.Org driver causes the emulator to fail to launch with a plethora of errors.
Has anybody encountered this before?
I was able to recover the emulator by forcing a clean boot. In the AVD menu, I clicked edit settings next to my emulator, and changed the rendering mode to Software-based. This made the emulator perform a clean boot, and fixed the issue. There is also an action to perform a clean boot in the additional actions menu.
After this, I switched back to Automatic rendering mode to make use of hardware acceleration again.
Related
I am attempting to get car_app_library hello world example to run through android auto to the DHU.
I have two different workstations with Android Studio and the DHU 2.0Beta. I have two different Android Devices, a Galaxy S9+ and a Galaxy Tab S6.
With any combination, with ADB and DHU running, locally on the devices at best, I can get a full white screen to flash which disappears, and no connection from there.
On the device, I have enabled unknown sources in Android Auto, and I have started "Head Unit Server"
On the workstation, DHU simply indicates at all times, "Waiting for phone...".
Studio "Run" indicates "success, operation succeeded" but nothing happens.
I finally got this working after two days. I could tell when it was not working that 1/5 times I'd see a flashed screen prompting for bluetooth and to continue, but I could not click any buttons in time.
Finally,
I uninstalled the "Android Auto for phones" application on the device, and I think this was the real solution
I also moved to canary channel for studio, and then needed to uninstall and reinstall the desktop head unit.
After this, I could get the screen to show that I saw flashing before, and I had to accept it once, then it crashed again, then I started it all again, and it is finally working.
genymotion when i run it, it's window dosn't display and not openning but when open task manager it's in process
note : it was working but i restarted the PC and tapped on restart any way
This sometimes happens after a Windows system upgrade. You need to remove Genymotion completely and re-install it. Follow the instructions from https://support.genymotion.com/hc/en-us/articles/360002815177-How-to-uninstall-Genymotion-Desktop-completely-purge-
I installed Android Studio and when i launch the AVD and drag it to my 2nd monitor it immediately crashes.
It works perfectly fine on my primary monitor
I've tried changing to hardware graphics but the same thing happens. Also tries to change the "OpenGL ES renderer" to "ANGLE (D3D11)" but the UI of my app is messed up.
Any one had the same issue and know a fix for it?
P.S. if it matters my GPU is Radeon RX 580
I'm on a Windows 7 PC. When I run the Android emulator from Android Studio on the command line, I get this error:
Failed on eglChooseConfig
Could not initialize emulated framebuffer
I can fix it by selecting software rendering, but that's really slow, and the GPU emulation was working a couple days before; it just suddenly stopped working.
I've tried changing it not to use multi-core CPU since it's labelled experimental, but I get the same problem.
Update: I just upgraded from AS 2.3.3 to 3.0.1. It installed a bunch of new emulator software, and I still get the same error.
Settings shown below:
It was not working because the display was set to 16-bit color. Set it to 32-bit color, and this particular issue may go away; there are other possible things that can cause the error.
I have been frustrated with Android Emulator for weeks after using x86 emulator. The emulator showed with blank screen for hours even if the LogCat indicate it is running, but I am afraid the application was trapped in a dead loop.
To correct this problem, I have re-installed all my computer and android developing environment, and follow every instructions I could get by searching the internet; while the result was frustrating: there was only one "system_process" running on the emulator.
Then today I noticed there is a SystemUI error, thus I guess if this is caused by the PC configuration when I was using extended desktop. So I detached my laptop from the dock and re-launched the emulator, this time it cost only about 10 seconds to get all the processes ready to simulate android phone.
So I guess there is a bug to handle PC with extended desktop enabled. If you have got similar problem when launching Android Emulator, please try detach your PC from the second display first.