Develop Reference

Android Emulator (from Android Studio) lagging

Searched for a solution, didn't find anything helpful.
I have a GTX 970 and an i5 4690k OC 4.2 GHz.
The Emulator from Android Studio is lagging as hell and I don't know why.
Intel HAXM is installed, 4G Ram is allocated to the Android Device. I just can't find a solution. Btw. I don't think my processor is too bad since I can run 2 VMs at once and the Emulator works fine on my XPS 15 9560 (i7 7700HQ & GTX 1050)
Does anyone have an idea what to do?
Config:
Also tried using Software for graphics emulation, much more slower. Btw for reference this runs in the background and doesn't seem to resolve:
The SDK used
CPU Usage:
Also, I installed the AVD also on the same system on Hackintosh:
CPU: 10% and works smoothly

Cut the RAM way back. There is no Android device of note that has 8GB of RAM. Something in the 1-2GB range should be fine.
Cut the VM heap way back. For example, my emulator images use 48-128MB, not 8GB.
If those don't help, experiment with a lower-resolution emulator (e.g., Nexus 4 1280x768) and see if that changes your results.

Fixed it! I did a random windows update to Version 1803 and now the emulator works perfectly! Thanks for all your suggestions and answers!

also think that the RAM settings are at fault ...
in particular the heap size matching the total capacity.
the default settings, which should run smooth(er) are:
CPU: 4 Cores (while available)
RAM: 1536MB
Heap: 384MB
also check background processes once, in particular AntiVirus with on-access scanner, etc. (some people have 2-3 of them installed); one of them is enough and if present, disable it once for a test. the emulator ordinary is much less of a memory hog than Android Studio with Gradle can be. if everything fails, the screenshot shows that there is one bank available, which could take 2 DIMM. booting another system from external media might also worth a try, in order to rule out the current OS install. and I also have that "preparing for setup" on one emulator image; that's nothing to worry about.

Could you try changing the OpenGL ES Renderer to Desktop Native OpenGL
And OpenGL ES API Level to Renderer Maximum
This made my emulator very responsive, almost 2x faster.
Like this picture
Also it might be worth mentioning that I set both my camera's to none.

android studio emulator loading but not working

I have used Eclipse to write apps for android multiple times without issue but I am now trying the new Android Studio which I like but here is my problem.
When I run the app I pick my AVD and then tell it to start. The emulator starts loading and then says paired. Then it starts telling me to swipe up and left and right to display and remove cards. Then it says to put hand on screen to dim the screen, ok well I'm on a MacBook Pro so that don't work I swipe to get past that part sometime I can others I can't. Next it says to touch the clock and say some words which also can't do on my Mac, and that is where the emulator stay it never goes to a home screen and it does this no matter what AVD I choose. How can I get the Emulator to just plain open to the home screen like it should.
Thanks for any help.

In your AVD Manager, edit your AVD and make sure your Target is "Android L" and not "Android X.XW". The "W" stands for "wear" and that is causing your issue.

Alright I figured it out. I remember having a similar problem recently when I was taking an android development class for college using eclipse and sure enough that was it.
So here was the solution eclipse gave same problem. for some reason if you have caught exemptions such as hard coding a string etc. the emulator will not run till you ignore these exemptions or fix every last ! mark in your code. Once you do this the emulator will load and run properly.

I also had the same problem with my AVD. The Android Emulator window just used to pop us and the green bars flowed infinitely. After lots of trial and error I arrived at a solution for my problem. the problem was with the Heap size and the RAM size.
Initially the default heap size was 128 MB and RAM was 1563 , I just changed the heap size to 512 MB and reduced the RAM size( high RAM was making my PC run slow) also I enabled hardware acceleration. And Yipeee, it worked.

Android emulator slow & faulty after SDK upgrade

Recently upgraded from API 16 to 17. Has been retaining all AVDs that were added before and they were working fine after the upgrade too. But today I deleted all old AVDs and added few new ones, each with each device specification available. Earlier, the booting time was around 5 minutes for AVDs with recent versions (4.1.2) and around 2 minutes for AVD with 2.3.3. But now, AVDs with 4.1.2 or 4.2.2 takes 10 to 15 minutes to boot. Moreover, it fails to load launcher. When I touch on the launcher button on the Home screen, it loads the list of Apps and displays a usage tip, "To add an app to your Home screen, touch & Hold it" over it. So far expected. But touching on "OK" for this tip leads to "Unfortunately, Launcher has stopped" error. Not touching on anything leads me back to the home screen.
Tried unchecking AVD options, "Hardware keyboard present" and "Display a skin with hardware controls". Still the issue remains.

It was a memory issue. Problem fixed on incrementing the default value of VM heap by a factor of 16. (16 to 32 and 32 to 48).

I know this should be more a comment then an answer, but I'm too new to StackOverflow. Hopefully a mod transfers this answer.
Are you using an Intel image? Because those ARM images are really slow. When you want to use an Intel image you should also install HAXM (https://stackoverflow.com/a/10772162/1741111). Be sure to select it the right settings. 768 RAM is the maximum on Windows.
These are my settings:

Yes, same issue on my latest SDK for Android 4.4. I am running the "ARMeabi-v7a", from the AVD (Android Virtual Device) Manager.
Every time I started the emulator, it would crash once you selected the apps screen, and tried to launch an app. The emulated app launcher would crash with
Unfortunately, the Launcher has stopped.
Really a pain.. I am running at the API level 19, so probably due to internal program bloat...
Once I raised the VM heap memory from 16 to 48, I noted that a special help program runs, with a big outline of a hand pointing at the "Downloads" app, and explaining that you can press and hold any app to move it to the main screen.
I am running on a WIN-XP (32-bit) old dual core Centrino Toshiba Satellite Pro, so maybe on newer 64-bit machines, the error does not show up. But thanks, Rajeesh.
I just used AVD Manager to edit the parameter screen for the ARMeabi-v7a emulated target device, and now the emulator launches successfully, and I can see (and run) my first "Hello World" app, built with the Eclipse ADT stuff. - Mark_L

Android 4.0.3 emulator crashes: Failed to allocate memory: 8

The problem started when I changed the skin built-in display setting to WXGA720.
Then everytime I'm trying to run the emulator it says the following message:
Starting emulator for AVD 'android403'
Failed to allocate memory: 8
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I already tried to lower down the RAM size to 800 MB and then 512 MB (or even 256) but it didn't work either...
I don't know what to do...
Here's a screenshot of the emulator settings window:
Thanx upfront.

I do sometimes have the same problem. Maybe my solution works for you as well: Instead of choosing the WXGA720 skin preset, manually set the resolution to 720*1280, and manually set the RAM to 768 or even 512.
Seems stupid, but it makes a difference if the skin preset is uses or a manual resolution configuration.

I had the same problem. I have set the resolution manually to 720 X 1280. Set the RAM size as 128MB and SSD to 16 MB. The app came up without any problems after that

This may sound silly, but I resolved the issue by adding "MB" after the RAM setting, changing (for example) 1024 to 1024MB.

I figured it out. The problem was in the amount of ram I had specified for the virtual machine, and it was 1024MB, now I have 512MB and it is ok. enjoy ;)

I also faced the same problem for x86 emulator for android 4.0.3. This problems happens to me only when i try to launch emulator from eclipse. But works fine when i launched the emulator from command line. Try to launch the emulator from command line.
Go to android tool directory and use "emulator -avd " to launch your emulator.

I had the same problem, trying to emulate the Galaxy S3. Setting the resolution to 720 x 1280 and dropping ram from 1024 to 700 worked for me. Could't get it to work at all on the built in wxga720 settings.

I was with the same problem today, but I manage how to solve it ( at least for me, because I was doing it in the wrong way), hope that it can be usefull for you too.
I was trying to change de Device RAM memory direct by Eclipse via Android Virtual Device Manager. I don't know why, but this changes does not affect the "hardware.ini" file that is present in : \android-sdk\platforms\android-16\skins\WXGA800-7in , for example.
To change the device RAM, or just to add MB you need to change this file.

Is it just me...or is android honeycomb 3.0 emulator really slow?

Well? I've tried increasing the RAM size of the emulator to 1024 MB and there was little improvement on the speed, however, it's still unusable. It has the speed of a turtle.
Anyone got better ideas to make it faster? Is there something I'm not doing correctly?

Check out the android developer documentation regarding 3.0 emulator performance. Scroll down to About Emulator Performance.
Copied tip for convenience:
Tip: To improve the startup time for the emulator, enable snapshots for the AVD when you create it with the SDK and AVD Manager (there's a checkbox in the AVD creator to Enable snapshots). Then, start the AVD from the AVD manager and check Launch from snapshot and Save to snapshot. This way, when you close the emulator, a snapshot of the AVD state is saved and used to quickly relaunch the AVD next time. However, when you choose to save a snapshot, the emulator will be slow to close, so you might want to disable Save to snapshot after you've acquired an initial snapshot (after you close the AVD for the first time).

Seems like everything 3.0 and beyond is slow for me. Everything before that runs very fast in emulator for me. However, I have an Intel integrated graphics card in my laptop. When I turn 3D setting to "Application Settings," I get relatively decent performance from the emulator, at least when it starts up, but then when I try to start any app from the default main app menu (contacts, for example) I get launcher errors. That happens for me on 3.0, 3.1 and 3.2. The one thing I'm suspicious of is that I'm running 64-bit Java SDK. Seem to be a number of posts out there related to 64-bit, but mostly they seem to be point to using 64-bit SDK with 32-bit Eclipse or vice versa, but in my tests, I am not even running Eclipse, haven't even reinstalled the ADT yet, just the Android SDK and created a few emulator instances. Again, prior to 3.0 everything is fast. 3.0 and beyond not good, but A LOT better with graphics settings as I mentioned above. If I could get past the launcher issues, I think I might be all set. Oh, btw also, for 3.0 and beyond, I bumped the memory up to 1024. I've tried increasing the heap for apps to double the default (from 48 to 96) but that doesn't seem to have alleviated my launcher problems.

It is slow. You can try creating a new Emulator with a smaller resolution.

I remember someone at google I/O saying that the HoneyComb emulator will run really really slow due to hardware acceleration turned on.
The PC may use software rendering for OpenGL hence the bad performance. The almost everything you see on the HoneyComb screen is rendered using OpenGL ES.
감사합니다,
Reno