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.
Related
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
I am new to android development, and I am having problems with Android Studio and the emulator. Both running together slow both systems to a crawl. My machine has Windows 10 Home and Linux Mint KDE 18.2 on it.
I have been trying to get it to work on both OSes. On Windows 10, I have 4gb of RAM, HAXM installed, and everything closed, it is somewhat usable (not much).
On Linux, I have 10gb of RAM (because of swap space). On KDE, it does not work at all. On fluxbox (with everything else closed), it is doable, but still slow.
In Android Studio (on Linux), I have increased the VM heap to 2gb, and enabled offline gradle work. With the emulator, I am using the Nexus 5x emulator (api v. 7.1.1, x86_64) with the device frame turned off, the RAM at 1024, and the heap at 256.
On Linux, memory does not seem to be the issue; when I open a system monitor, it shows both processors running at 100%. Basically, what can I can I do now?
If anyone needs any more info, just ask. Thanks in advance.
Edit
I did see this question: Why is the Android emulator so slow? How can we speed up the Android emulator?
This question is about the android emulator w/ eclipse. Also, I have tried the suggestions in that post. The suggestion I would like to do (use a snapshot) does not seem to be present in Android Studio (v 2.3.3).
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.
I install the android studio and when I try to start AVD(NEXUS 5) this is
not working. AVD screen show black screen with android label. I wait about 30 mint
but AVD not start.
console show the error
hax-is-not-working-and-emulator-runs-in-emulation-mode
I reduce the RAM set to 1GB not working.
I set RAM to 512MB not working.
I also uncheck the use gpu host but all in vain.
I check the HAXLog file but there is nothing.
My machine is core i3 windows 7.
It support the virtualization technology and this is also enable from the boot menu.
How I can overcome from this problem.
THANKS...
After adding an AVD, it takes a long time to run. On my less than year old Core2Duo 2.8 GHz running Win7x64 and 4Gb of RAM, initializing a 2.2 version took at least 5 to 10 minutes (if not longer). Once it starts initializing you can watch the logcat in the DDMS panel of eclipse and watch it unpack and install all of the apps in the emulator.
I do not know what to do. I purchased a new laptop, hp pavillion i5 6GB RAM, started Android 3.2 emulator and it is still as slow as unusable!!!
It's not that it is slow, it's that I cannot do anything.
I set 1GB of RAM, disabled camera on emulator and run it. When I click on Applications, they first load for 30s and then I am not able to start any app, not mine, not default ones. All I can do is return to desktop and open Applications menu.
I see people complain that the emulator is slow and I am not even able to make it run. What is worse, my laptop eats games like a sandwich, but it chokes with Android emulator 3.2. The same is with Android 3.0 emulator!
Can anyone help me set up the emulator so that I can run it on my machine?
PS. if you want, I will record a video and post it to visually see what I am talking about.
I do not know what to do. I purchased a new laptop, hp pavillion i5 6GB RAM, started Android 3.2 emulator and it is still as slow as unusable!!!
The Android emulator uses a single core. If you had gone with a Core i7 with Turbo Boost, that would have helped. Your Core i5 is not an especially powerful CPU on a per-core basis.
The Android 3.x emulators also do all graphics purely in software (no hardware graphics acceleration) and convert ARM instructions to x86 on the fly.
Can anyone help me set up the emulator so that I can run it on my machine?
Start by using the Android 4.0 emulator, with the latest Android development tools. This uses your desktop's GPU for graphics rendering, and it helps performance a bit.
If that proves insufficient, you can start switching to x86 emulator images if you are not doing NDK development (where you will tend to want to test on ARM). At the moment, the only official x86 image is for 2.3.3, but there is an unofficial one for 4.0.3 built from the AOSP that runs exceptionally fast (at least on Linux, haven't tried it on Windows).
My only suggestion to you would be to change the "ADB Connection Timeout (ms)" in Eclipse under Window->Preferences->Android->DDMS. I am using a HP Pavillion 486 laptop, and was really struggling with the emulators. I changed the default timeout value from 5000 ms (5 sec) to 60000 ms (1 minute). This didn't solve all of my problems, but it did help in the startup of both the emulator and my applications.