I know that question was already asked. But I'm adding some more details and asking more precise questions that can solve this problem.
Actually, when I start an AVD with 312 MB of RA it does manage to do it respectably (even if it's considered slow).
But when I ask for 512 MB of RAM, it's like it will never start at all (in fact never), and noticed that the AVD only works on a single core a 100%. Plus it populates the RAM quite quickly until it reaches around 175MB (5-10MB/s) and then slows down dramatically (250KB/s).
How can this happen and how can I do for preventing such RAM filling performance drops ? Or even set the AVD to use more than one single core ?
I run this on a Core I5, with 4GB of RAM.
Edit: Why so much downvotes ?
Problem solved: Templating from a Nexus 5 messed up everything, went to Nexus 4 and everything works like a charm.
a. Use the Intel system images available on the SDK manager.
b. Use this software by Intel to make your emulator run faster.
c. Use Genymotion.
Related
I have tried looking at this SO post but I already have 16GB of RAM and I don't want to decrease AVD memory. I do not understand why the Android Emulator takes up so many resources (%25+ CPU, Almost 1GB of RAM) when running a simple app (Like this: Single Activity with a RecyclerView and its Adapter. That's it). Any help would be appreciated.
My fan is always on when using the Android Emulator in Android Studio.
This is normal for the Android Emulator. My numbers are the same.
This is a big pain for me and even bigger after upgrading the AndroidStudio version.
One alternative is to use an external Device for Debugging in place of an Emulator.
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.
I want to create a really big swap file on my Android phone or at least to try it.
System: Android 7.0
Phone: Samsung GALAXY S7 edge
Root: YES
I have already tried the ROEHSOFT RAM EXPANDER which works well but it allows me to create only max. 4 GB of swap file. I am talking about 20 GB or something like this. I know that it is crazy and may be unstable but I undergone every risk. I do not care about the speed. I would appreciate if you helped me and told me any guide how to do that. I undergone all the risks and the possibilites of crash of the phone. It is not my main phone so I do not care about it. I just need the RAM. Thanks everybody for help.
I am beginning android development using the latest versions of the android SDK and eclipse. I have followed the Hello Android Tutorial
and used every combination of targets available but the Emulator freezes on the load screen with the flashing "android" title.
I have checked the other related question and DID wait about 15 minutes. but still no change. Any help with this would be great. Thanks.
I had a similar issue, and still do sometimes today. Have you tried deleting the AVD and then re-creating it?
Also try changing some of the AVD's values, give it more ram, larger SD card. You can do this through Window > Android SDK and AVD Manager > Edit the AVD, and then add values / modify the SD card size.
EDIT: Also - just for reference, I have a Intel Core i7 with 16gb of RAM and AVD's STILL take forever to load.
EDIT: Another handy thing to know is that if you check the "Snapshot" option when editing the AVD, it will save the last state and load that instead of a full [slow] boot. Kind of like putting your computer to sleep.
Adding values / modify the SD card size may be better .
Try not to close the Android Emulator , to avoid re-open .
Yah android emulator takes time to start up, but it should start within 2-3 mins. Check your RAM and processor. The RAM must be atleast 1GB (preferably more) to speed up loading emulator.
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