Can I configure my Android emulator to work fast?

I am using android emulator to run my programs. But it is very slow. It takes about 90 seconds to start and show the main screen. Can I customize it so that I can reduce this time significantly? Thanks

+59
android emulation tweak
Dec 28 '09 at 6:03
source share
13 answers

I had a similar problem ( here) . However, mine worked 10-15 minutes. 90 seconds flash quickly, given the many threads in Android discussion groups. The emulator is slow in nature, and the only recommendation I read was to keep the emulator open, not to close it and restart it. However, as mentioned in my thread, if you have a physical Android device, you can just run it on this. This is what I am doing at the moment, and it was first-class advice. No long wait. If you do not have a physical device, I can only suggest that you do not close the emulator between code changes, since the system recognizes the change.

+35
Dec 28 '09 at 6:07
source share

use these 3 options.

emulator --cpu-delay 0 --no-boot-anim --cache ./cache --avd avd_name

the first two are obvious. the third will make the memory of the emulator look constant. you can point it to any file that cannot be destroyed at boot (for example, with / tmp) it looks like a constantly-on sleep mode.

+31
Oct 25 '10 at 6:17
source share

If you absolutely cannot use a physical Android device, then you can run the Android OS on Virtualbox, and then get the IP address of the emulated Android. Then you connect the ADB to the emulator using this IP address. This is his push. I wrote a more detailed guide to this approach on my blog. http://www.bobbychanblog.com/2011/07/faster-android-emulator-alternative-using-virtualbox/

+9
Jul 11 2018-11-11T00:
source share
  • The -no-boot-anim option is good.
  • Do not turn off the emulator, just run the application.
  • To speed things up, try the new snapshot feature described here .
+7
Mar 24 2018-11-21T00:
source share

Scaling the emulator down accelerated the loading of the emulator ...

 emulator -cpu-delay 0 -no-boot-anim -cache ./cache -scale 0.8 -avd avd_name 
+2
Mar 14 '11 at 19:37
source share

these are actually all great answers, but have you thought about replacing the plunger from the standard 96mb to something like 512? works for me :)

+2
Apr 21 '11 at 20:12
source share

If you have a mobile device with you, it’s much faster (and more reliable) to compile it through a USB device. It takes about 5 seconds to compile and install on your phone, I no longer use the emulator - it just slows down.

It is not only slow, but everything except static widgets (animation) will work on the emulator, and you will notice a delay.

+2
May 14 '11 at 10:51
source share

I recommend you use Genymotion . This is a very fast emulator (less than 10 seconds to run in my case)

It has the Google Apps application installed, including the Google Play application, which makes it possible to download any application. This is a good feature for testing applications using Maps Api.

+2
Oct 28 '13 at 8:37
source share

You need to install Intel HAXM

  • open the SDK and install

enter image description here

  • Create a new AVD

enter image description here

  • Now at startup you should get this

enter image description here

if not, you will need to install Accelerated Execution Manager

See Launching the new Intel emulator for Android on how you can do this.

enter image description here

See how much faster you get videos

+2
Feb 08 '14 at 13:33
source share

When developing my game "Elastic World" I had the same problem. After waiting for minutes to start the emulator, the game worked with a maximum of 20 FPS. Even on low android devices, I could easily get 60 FPS.

So, I switched to the Android VMWare machine, following the instructions on this site: http://www.android-x86.org/documents/installhowto/

The same game loop now runs at 250 FPS. (it does not play at that speed, and my game is limited to max. 60 FPS, but overriding this limit, it gives 250 FPS).

+1
Jul 04 2018-12-12T00:
source share

Try to use lower resolution for your emulator, for example, HVGA. The emulator becomes slower the more pixels it needs to render, since it uses software rendering.

Also, if your computer has enough memory, add at least 1 GB of memory to the emulator. This is the “Device Memory Size” value when creating the AVD.

Also set the “Enabled” flag for snapshots. This will save the state of the emulator and allow it to start much faster.

0
Jan 18 '12 at 6:05
source share

Just check the "Snapshot" checkbox in your AVD Manager. It will save the state of your AVD when you close it. So, as soon as you start the emulator again, this state will be loaded. Consequently, the loading time of your AVD will be significantly reduced.

0
Nov 13 '12 at 15:55
source share
  • First I follow this.
  • Run the emulation using the command: emulator -cpu-delay 0 -no-boot-anim -cache ./cache -avd <adv-name> -gpu on (follow the link and link )
results

run ~ 2-3 times faster

0
Aug 29 '13 at 2:02
source share



All Articles