I have multiple emulators provided by Android Studio. I have a Pixel 3 and a Pixel 4 both running Android api 30. Both work fine for a while, but eventually there is this popup:
After this point, the emulator becomes unusable. Notice that the home and back buttons at the bottom of the screen are gone. The emulator glitches horribly, with animations slowing down and leaving residue on the screen.
What I have tried
Quitting the emulator application and turning it back on again. Same issue again.
Pressing the emulator power button and restarting the emulator like I would a physical device. Same issue.
Deleting the emulator and creating new one. This works for a while but eventually the error happens again.
I followed the advice here: Android emulator error: "System UI has stopped"
The .ini file had no entry for hw.mainKeys so I tried adding it. No effect.
Stats
MacBook Pro (16-inch, 2019)
processor: 2.6 GHz 6-Core Intel Core i7
memory: 16 GB 2667 MHz DDR4
graphics: AMD Radeon Pro 5300M 4 GB, Intel UHD Graphics 630 1536 MB
Android studio 4.4.1
At this point, it's becoming difficult to continue development, since I have to keep recreating my emulator and reinitializing the device data that I need for testing.
The fixes reported by some users are in the following list. However each of the fixes have worked only for some small group of users.
Update your HAXM version (check manually in SDK manager)
Use a lower resolution emulator
Try a different API version or system image
The only fix that works for all users is to wipe your emulator and start it again (which means setting up your accounts again). This fixes it for short times but the problem always returns pretty fast.
The problem has been common since at least late 2017, on both windows & mac. There was a starred issue on Google bug tracker too but I cannot find the related question on StackOverflow which linked to it
Related
I am facing the same problem. I have ASUS ROG 17 inch Laptop, 16GB RAM, i7 processor, nvidia graphics card 3gb RAM , Windows 7 Home Edition service pack 1, Android studio 3.62, HAXM 7.56, Android Emulator 30.0.5, Android SDK 29.0.6. When I starts my emulator, nexus 6p API 28, Android 9.0, it tooks almost 3 to 4 minutes. and after booting it display message, System UI is not responding,. Wait or close app. When i click wait, it will took a while and starts successfully. But sometimes, It won't. I have to close Android Studio, shut down the system and restart it again. I wondered, why its not working smoothly on such a high configuration laptop.
The solution is that you can't do anything about it. You have assigned 2GB of RAM, but that's too low for the emulator (though it shows that as recommended).
The only way about it is to create and run a new emulator with the default configurations, i.e. don't change anything in the memory or RAM section.
This solution worked for me although the performance of the emulator isn't too good.
My sincere thanks for your reading this.
I have just installed Android Studio and am attempting to run the default Hello World! script that is present when you create a new project.
Every time I try to run the the program in an Android Emulator my Emulator crashes and I get the error "Android Emulator Closed Unexpectedly" Every. Single. Time.
I have the Intel x86 Emulator Accelerator (HAXM installer) installed as suggested:
I try to run a Nexus 4 emulator with 512 mb of Ram and it never works:
When I run this I get:
During this, my system physical memory peaks at 80% but never goes to 100 (which I would expect if it were crashing).
I have searched similar questions including
Android emulator crashing on Windows 7 64 Bit Android 4.0 emulator always has a crashing Launcher? Android studio emulator fails to start with memory limit related error message and they say to lower the memory size (which is what I am trying to do). Unfortunately this isn't working
Any idea how I can solve this issue?
My computer specs are as follows:
64 Bit Windows
6gb Ram
Intel Core i3
I downloaded and installed all correct versions as instructed here: https://developer.android.com/studio/install.html
In my case, this issue took the whole weekend to solve.
All options I tried, until:
Android Development Studio prompted me to update the Android Emulator Version to 25.3.1 (no idea what it was on before as I didn't check this before). This was a download of ~170mb.
Once I downloaded and installed the update, the emulator now seems to run OK on low memory settings - settings in keeping with the answer to this question here: Android emulator generates a very annoying error
I am now running with settings:
RAM memory to 5012
Virtual heap 32
Internal storage 200 mb
External storage 64 mb
So basically, it was a complete fluke that this worked.
To anyone that gets this error after rooting the android image, (if using snapshots). You need to start the virtual device with the -writable-system parameter like when you rooted the device, excerpt from docs.
Snapshots
...Starting a virtual device by loading a snapshot is much like waking a physical from a sleep state, as opposed to booting it from a powered-off state.
I was also having the same problem, Every time I was starting Emulator, it was closing unexpectedly. then I tried to change the Emulator Performance in settings of AVD Managers; In Software it's not working but in Hardware it was showing blank black screen.
Then I realized, there might be some issue with Graphics Card(mine NVIDIA GeForce 940MX), It was showing this error
After Updating/Restarting the problem was not resolving, then I Disabled then Enabled the Graphics Card Driver in the Device Manager and It worked!!😊
LONG STORY SHORT: Check, the problem might be due to your Graphics Card!😐
in my case, i attempted using gennymotion [ you may install it asking google genymotion . com] this could serve as alternative.
if gennymotion after installation returns this error message "the version of openGl supported by your graphics card is too old:Genymotion requires at least openGl 2.0 support. "
then know our challenge is arising from not having required graphics driver
either you checkout this link [https://buffered.com/support/solve-opengl-error/] on how to resolve it in steps.
or you download the graphics drivers using the links below
Here are the links to the 4 most prominent graphics card manufacturers in the world:
Intel: http://www.intel.com/content/www/us/en/support/detect.html
restart your systems after installation of the appropriate graphics driver and continue your project .
The Android Emulator 2.0 freezes some time after GPS is enabled.
The Android part completely freezes, the "control GUI" panel still works (but obliviously no effect to Home etc).
adb lists the emulator but no response for adb logcat etc.
The emulator must be closed with ctrl-alt-del. Next freeze comes faster. Instead of occurring within a minute, it occurs within tens of seconds. The PC must be rebooted to get back to a minute.
I want GPS and pressure sensors so GENYmotion and Visual Studio emulators are not an option.
Windows 10 Pro 64bit (before/after Anniversary Edition)
8GB RAM, Intel i5-3570, 30GB available on the Windows disk
Intel HAXM 6.0.3
Occurs for x86, x86_64, arm. Primarily been using Android 7.0 emulator, similar for older versions.
Also occurs with fresh AVD
Default settings for emulators (have tried deactivation multi-core, give more RAM etc)
AVD launched from AS 2.1.2 and 2.2beta1
Nothing seen in system logs, AS logs though: C:\Users\.AndroidStudioPreview2.2\system\log\threadDumps-20160814-103215-AI-145.3128856\freeze-20160814-120115-75\threadDump-20160814-120226.txt Cannot make out something from the logs.
Google has released an update and closed the issue.
Working for me.
Because the emulator was really slow I installed the intel x86 emulator. I changed the settings in my emulator (ARM to intel atom). Now when I run a project it takes me to the emulator selection screen and when I select it, the project starts running, but the emulator doesn't pop up.
I tried switching the cpu back to ARM, but it still doesn't work.
When I close Android studio it asks me if I want to disconnect from the project so I'm sure it is running.
I came across a few posts that said to give the device 768 ram, but that didn't work.
Anyone knows a solution?
I was facing the exact same issue, but for me reducing the device RAM to 768 did fix it. Therefore I'd suggest continuing to decrease the RAM values and trying to launch it.
How about to use Rock speed Emulator - Genymotion?
I know it sometimes take time to launch emulator and launch app in emulator too. But it depends on your configuration of your PC and settings you have done in Eclipse or Android Studio.
For example: You may have kept "Build Automatically" ON and it sometimes slow down running time.
My current rep is not high enough yet to comment on another answer, so I am adding a new "answer" to +1 Paresh Mayani's answer to use Genymotion. I only recently discovered it and found it to be much much faster than the emulator. Instead of emulation it runs an Android rom in a VM using VirtualBox. I've found that it runs full speed on my machine and is just as fast in debug mode as normal mode, which is impressive since even my Nexus 5 struggles when connected to a debugger.
In my case also x86 was creating problem, I installed Android 5.0.1 armeabi-v7a and have set 768MB as RAM size and it worked.
Try to check and run the emulator ie. store a snapshot for faster startup...
I have tried that by checking the button and works fine.
If you're using an AMD machine try using the "ARM EABI v7 system image". For an intel chip use the "APIs Intelx86 Atom system image". Also, try a different tablet from the Android Studio settings e.g(Nexus 6), as the API level might not be supported from in the Nexus5 VM. You will also have a little wait time for the android emulator, mine takes about 7mins
I cannot understand if it's a bug of the emulator or what else
Some days ago I updated my Galaxy S from Froyo (2.2.3, I think) to Gingerbread 2.3.4. I was pleased about the improved performances, in particular I noticed the game that I'm developing. While before I had around 30 FPS, with the Gingerbread the FPS was around 45.
So I had a (Bad) idea: Maybe Google guys fixed also the non-excellent performances of the emulator! (I never updated my SDK and related softwares since I Intalled it, it was the r7)
I started my SDK Manager and I started the update to r12. The Manager installed everything, I started Eclipse, then my game on a HVGA 320x480 emulator as usually, and suprise. Only 10 FPS, where just some hours before I had 25-30.
The Android OS on the emulator seems to react like before, And I've noticed That sometimes, when just lanched the game for the first time with the emulator just booted (not from snapshot) the game runs for 1-2 seconds at 25-30, Then drops immediately to 10
So I tried the following:
updating the ADT Plugin for eclipse
reinstalling the SDK r12 with the official installer (in another location)
tried a lot of different Adroid OS targets
running the virtual machine directly from the SDK Manager with Eclipse closed
speeding up my Win7 by stopping all not necessary services, processes and Antivirus
starting the HVGA emulator with the flag "Scale display to real size" (damn, the screen is really small)
Googled a lot
Nothing helped me, everytime the framerate was 10 FPS! It's like the emulator runs a frame limiter on 2d graphics. And on the real phone works great.
Is not a problem related to PC hardware specs, because my pc isn't so bad (dual core E8400 3.0 Ghz, 4GB RAM, Ati radeon 4870 1GB, Win7x64)
Then finally I tried the WVGA 480x800 emulator. And another surprise: 13 fps!
I spent a lot of hours to try to fix this problem, whitout success. And I have not so much time for my game project, so I wonder if:
Is it a "known issue" this decrease of performances though the sdk releases, and should I only do testing on my phone, waiting patiently that Google fix the emulator?
Is it possible to get and reinstall the old versions of sdk/emulator (If I could choose, I would back my r7). I need to test my application on different screen sizes, and so the emulator is not usable.
SOLVED: I found that adding the options:
-no-boot-anim -qemu -icount auto
to the emulator solved the problem!
(eclipse: Run->Run Configurations.. then tab "Target", textBox "Additional Emulator Command Line Options" )