By Andrie

2009-10-12 11:45:53 8 Comments

I have got a 2.67  GHz Celeron processor, and 1.21  GB of RAM on a x86 Windows XP Professional machine.

My understanding is that the Android Emulator should start fairly quickly on such a machine, but for me, it does not. I have followed all the instructions in setting up the IDE, SDKs, JDKs and such and have had some success in starting the emulator quickly, but that is very rare. How can I, if possible, fix this problem?

Even if it starts and loads the home screen, it is very sluggish. I have tried the Eclipse IDE in version 3.5 (Galileo) and 3.4 (Ganymede).


@Vikas Patidar 2011-03-01 12:40:18


You can now enable the Quick Boot option for Android Emulator. That will save emulator state, and it will start the emulator quickly on the next boot.

Click on Emulator edit button, then click Show Advanced Setting. Then enable Quick Boot like below screenshot.

Quick boot

Android Development Tools (ADT) 9.0.0 (or later) has a feature that allows you to save state of the AVD (emulator), and you can start your emulator instantly. You have to enable this feature while creating a new AVD or you can just create it later by editing the AVD.

Also I have increased the Device RAM Size to 1024 which results in a very fast emulator.

Refer to the given below screenshots for more information.

Creating a new AVD with the save snapshot feature.

Android emulator with save snapshot feature.

Launching the emulator from the snapshot.

Launching the emulator from the snapshot.

And for speeding up your emulator you can refer to Speed up your Android Emulator!:

@Mark Bakker 2011-05-10 11:13:29

When you update and existing device, wipe the user data on the first startup from snapshot

@zhongshu 2011-07-16 13:01:19

I set the AVD as this, but seems still slow when I reboot the AVD, why?

@Vikas Patidar 2011-07-22 06:59:47

@zhongshu: When you reboot AVD then it starts from the beginning state rather than the saved snapshot. So probably it will take more time.

@zhongshu 2011-07-22 07:15:57

so, how to restart the AVD in correct way to use snapshot? (I just right click the Emulator icon in task bar and click 'Quit' and then restart it in AVD manager.)

@Vikas Patidar 2011-07-22 10:17:35

@zhongshu: Oh ! i was just thinking that you might be restarting it from command or terminal mode. The way you had mentioned is correct but there may be something else related to your system configuration.

@djangofan 2011-12-12 02:50:24

For me, its not just the startup speed thats a problem. The environment from Eclipse 3.7 is so slow that mouse clicking seems to have no effect. Often, my Android environment is blank and takes many minutes to show any page change. I have Core2Quad 2.4Ghz, 8GB ram, Ubuntu 11.10 x64.

@Peter Ehrlich 2012-01-01 03:09:07

I was unable to get to the launch options dialog. How do you open it?

@Vikas Patidar 2012-01-02 07:10:05

@Peter Ehrlich : Just go to the Window > Android SDK and AVD Manager and select AVD you want to launch from the list and then click on the Start button in the right pane. It will open the same you want.

@Chris 2012-05-31 15:57:32

Are these two different versions? My Eclipse has Window -> Android SDK Manager and Window -> AVD Manager as separate options. There's nothing that looks like the second dialog in this answer

@n611x007 2013-05-31 04:47:14

command line version?

@awe 2013-08-06 10:56:23

I got "Failed to allocate memory" when setting 1024. It also displayed a warning at the bottom of the configuration window saying: "On Windows, emulating RAM greater than 768M may fail dependin..." I Tried setting it to 770, and then it worked. It failed setting it to 800.

@michaelsnowden 2013-11-14 07:17:17

How do you do the "launch options" portion in intellij? I made my emulator "snapshot-enabled" by just clicking snapshot, but the launch options portion (your second picture) is not something I see.

@Vikas Patidar 2013-11-22 12:48:24

@ Msmit1993: You can use Intel x86 based emulator with HAX tool. Believe me you will will be surprised that emulator faster than your actual device.

@Trojan.ZBOT 2013-12-22 05:09:44

There is a use host GPU option as well, next to snapshot. It might help as one of the answers mentioned.

@Vikas Patidar 2013-12-22 07:44:50

@Trojan.ZBOT Both options are for speed-up but you can not use both together.

@Brian Knoblauch 2014-09-09 17:03:09

Oddly, on my machine (quad core AMD), I've found that reducing RAM makes the emulator faster and increasing RAM slows it down.

@vharron 2015-03-05 01:41:46

Snapshots aren't supported with GPU emulation. GPU emulation makes the emulator much faster so I recommend it over snapshots. x86 images start up pretty fast with HAXM/KVM

@jAC 2015-05-28 11:35:26

This answer and the one mentioning the HAXM really increased the speed. Now it only takes about 10 seconds to load. Great!

@Sam 2015-06-18 12:45:24

I haven't found that this helps at all. I have a HDD rather than a SDD, though, so maybe this is for users with SSDs.

@Vikas Patidar 2015-06-19 06:24:37

@Sam Please refer below answer, it's almost 4 year old trick and not relevant for today.

@Cows quack 2015-08-12 14:17:45

How do you do it for Android Studio?

@Vikas Patidar 2015-08-13 10:13:06

@KritixiLithos Toos > Android > AVD Manager > Create New Virtual Device > Next > Select hardware > Next > Select System Image > Next > Check Use Host GPU

@huisinro 2016-06-25 04:59:32

Please try our newly released Android Virtual Machine, called Leapdroid, it's totally free, and compatible with Google's QEMU based emulator, with very fast OpenGL impl.

@B-GangsteR 2016-07-01 19:45:30

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).

@Shirkam 2017-07-25 10:47:34

Also, beware than adding more RAM to your emulator makes you use a "better device" as it will be able to allocate more space before it goes out. If all what is wanted is to test functions of an app, that's ok, but keep in mind that if your app is too memory-intensive, lower devices could not be able to run it.

@Ahmad 2012-08-22 17:00:28

Well, since somebody suggested Android x86 as an alternative testing emulator, I'll also present my favorite. This might not be an alternative for everyone, but for me it's perfect!

Use the Bluestacks Player. It runs Android 2.3.4 and is very fluid and fast. Sometimes it is even faster than a normal device. The only downside is, that you can just test apps on the API Level 10 and just on one screen size, but it's perfect just for testing if it's working or not. Just connect the Player with the adb by running

adb connect 

After compiling, it installs instantly. It is very impressive, considering I have rather an average computer hardware (dual core with 4  GB of RAM).

@nesimtunc 2013-06-03 12:44:45

It's really very fast! How can I modify it for requirements like 7' (800x480) tablet? I tried change app size but it's already a tablet.

@Rolf 2014-05-25 17:23:13

I think you meant "fluid and fast" :) Anyway, thanks. Nice tip, too bad it runs Android 2.2

@Ahmad 2014-05-25 18:00:16

@Rolf Oh right, haha :) However, this answer is old. You should check out Genymotion. It's way better.

@Amin Rahkan 2016-12-08 19:55:29

Use the Intel x86 Emulator Accelerator

First, install the Intel x86 Emulator Accelerator (HAXM). This can be downloaded directly from Intel or using Android SDK Manager. In the SDK Manager, it's located under Extras.

SDK Manager Screenshot

In the version of Android Studio I used (0.8.9), Android SDK Manager downloads HAXM but doesn't actually run the installer (I assume this will be fixed in later releases). To run the installer I had to go to C:\Program Files (x86)\Android\android-studio\sdk\extras\intel\Hardware_Accelerated_Execution_Manager and manually launch intelhaxm.exe.

HAXM works with Intel devices, so created a new Emulator with Intel CPU.

Create a new AVD using Intel Atom x86

This improved things considerably, but the emulator was still feeling a bit sluggish. The final step was selecting Use Host GPU in Android Virtual Device Manager (AVD).

AVD Create Options Screenshot

After these changes, Android Emulator was launching in 5-10 seconds and running without any noticeable lag. Be aware that these features are hardware dependent (CPU/GPU) and may not work on some systems.

@Keoz 2017-02-13 21:26:42

Use Host GPU is the key! thanks was wondering why in one machine I had a fast emu and in another I had not

@Anu Martin 2017-09-12 09:06:05

you should enable virtualization on BIOS, if you had an AMD processor then enable Vt-x

@suther 2017-09-13 10:58:09

Notice, this HAXM is only needed (and available) for Windows, not for Linux.

@Filip Dupanović 2011-09-14 16:30:22

You can review the emulator issues on the Google I/O 2011: Android Development Tools talk, starting a 0:40:20.

The emulator runs slowly because the complete Android environment is running on emulated hardware and the instructions are executed on an emulated ARM processor as well.

The main choking point is rendering since it's not running on any dedicated hardware but it's actually being performed through software rendering. Lowering the screen size will drastically improve emulator performance. Getting more/faster memory isn't going to help.

They've mentioned, at the time, that they're developing an interface that would allow the emulator to pipe certain instructions through the host hardware, so eventually, you'll be able to leverage emulator performances with the raw power of desktop hardware.

@James Wald 2012-05-26 14:58:37

Intel released recommended installation instructions for the ICS emulator on May 15, 2012. This worked for me. The emulator is now fast and the UI is smooth.

The first half of the instructions are detailed enough, so I will assume you were able to install the Intel x86 Atom System Image(s) using the Android SDK manager, as well as Intel HAXM.

Now to ensure that everything else is set up so you can enjoy a highly performing emulator:

And start it:

sudo kextload -b (mac)

If HAXM is working properly, you may see this message when launching the emulator:

HAX is working and emulator runs in fast virtual mode

Otherwise, you may see this error:

HAX is not working and the emulator runs in emulation mode emulator:
Failed to open the hax module

  • Use GPU emulation. You cannot use the Snapshot option when using GPU emulation as of this writing. Ensure that GPU emulation is set to "yes".

  • Set the device memory to 1024  MB or more, but not more than the Intel HAXM setting. I use 1024  MB per device and 2048 for HAXM.

Always double-check the settings after saving! The emulator is very picky about what it allows you to set, and it will revert configurations without telling you.

With these settings the software keyboard no longer appears, nor do the on-screen back, menu, and recent keys. This appears to be a limitation of the current ICS Intel x86 system image. You will need to use the keyboard shortcuts.

On Mac OS you will need to hold fn + control for the F1 - F12 keys to work. Page up/down/left/right can be performed using control + arrow keys.

@James Wald 2012-06-14 15:28:21

Be careful when using a virtual machine with Intel HAXM. Apparently the virtual environment can become corrupt if system memory is exhausted.

@sulai 2012-10-15 13:58:09 This is another good step-by-step instruction for setting up a HAXM x86 AVD in Eclipse. Additionally it explains how to set up Google APIs.

@jayarjo 2012-12-09 18:46:36

Not sure if that's me doing something wrong, but I closely followed the guide and got: "HAX is working and emulator runs in fast virt mode", just before the device started, but... it actually loads even slower than original arm version. I'm on Mac and CPU supports VT.

@James Wald 2012-12-10 14:50:55

Do you also have hardware GPU emulation enabled?

@Tony 2013-02-09 23:22:15

This is the right answer.. I have Intel x86 processor installed and I have GPU enabled. The emulator is very responsive and smooth with these settings. FINALLY ! If you need help setting it up on windows or mac let me know. Adios all

@gerrytan 2013-03-14 00:35:22

Thanks for this, tested on Windows 7 Pro, intel core i7 3770 and it works. On windows Intel Hardware Accelerated Execution Manager (HAXM) only need to be installed, it will start automatically. Just create an AVD with Intel Atom x86 and ensure 'use host GPU' is selected

@poiuytrez 2013-06-25 09:59:56

I confirm that the emulator now runs like a F1 car on Mac OS.

@PankajAndroid 2013-07-16 05:24:11

i donsnt have HAX any other solution for this?

@James Wald 2014-04-07 07:30:47

Another pro tip, on Mac machines you can get additional details about the Intel kernel extension using the kextstat command, e.g. $ kextstat | grep intelhaxm.

@John Brunner 2014-06-29 16:08:51

do i have to stop (because you said I should start it) the Intel HAXM after i finished my work with eclipse?

@James Wald 2014-06-29 21:50:00

I generally leave it loaded all the time. It only consumes memory while emulators are running.

@blaffie 2013-07-02 18:25:27

UPDATE: The latest version of Android studio (2.x) made major improvements to the bundled emulator. It's responsive and has a whole bunch of features.

For those still interested: Try using Genymotion. You can download a version for Windows/Mac OS X/Linux after registering. A plugin for Eclipse is also available:

The installation of the plugin can be done by launching Eclipse and going to "Help / Install New Software" menu, then just add a new Update Site with the following URL: Follow the steps indicated by Eclipse.

This emulator is fast and responsive.

GenyMotion allows you to control various sensors of your device including the battery level, signal strength, and GPS. The latest version now also contains camera tools.

@Eurig Jones 2013-09-14 18:32:38

Genymotion is by far the best way to develop/test your app. It's not only quicker and better than a traditional emulator. It's quicker than a real device too. I use it for 99.99% of my deployments as it means I can see the results in a fraction of the time. It also means I can use OpenGL ES and other things which are not available on a normal emulator.

@Furqan 2013-09-17 07:11:27

agreed Genymotion is the best thing I've ever used for android development

@silvenon 2014-02-08 00:22:56

This is clearly the best solution. You can also link up this article which serves as a nice introduction.

@Apfelsaft 2014-05-07 06:35:41

Newer versions of Genymotion do not include the GooglePlay Services. This link shows how to install them manually:

@Sufian 2014-05-10 12:14:49

@Apfelsaft I have tried the solution provided in the following answer. I used it a while ago and it worked fine.…

@blaffie 2014-05-10 17:16:03

@Apfelsaft Refer to this answer Play Store License. In short, the Play Store is not licensed to run on the emulator.

@user2875404 2015-09-12 11:36:33

I wish the votes were re-set so everyone used Genymotion. By far the best emulator out there.

@user1299518 2015-09-25 14:43:23

Genymotion is so fast, you'll take it for a real device or devices ;)

@milosmns 2016-03-29 14:15:12

It's fine until you reinstall the VBox or any of the tools they use, then it stops working - uninstall doesn't help. But it was good while it lasted.

@Zain Ali 2016-09-12 14:09:14

Genymotion is not free anymore(As it was when I used it last time),Not sure if this is still the best choice for developers

@blaffie 2016-11-02 14:28:58

Since Android studio 2 the emulator has been improved ten fold. It has plenty of features and performs well.

@Dealdiane 2017-03-14 00:28:15

@ZainAli It's still free for personal use at the moment

@Ton 2017-04-22 11:22:57

I don't want to use the Genymotion. The question is why is the Android Emulator SO SLOW?? I don't know why, a few days ago it was running fast and smooth. Then I restarted my computer and it became extremely slow. It must be some reason for this

@Prashanth Sams 2012-12-13 09:33:19

IMPORTANT NOTE: Please first refer to the Intel list about VT to make sure your CPU supports Intel VT.

HAXM Speeds Up the Slow Android Emulator

HAXM stands for - "Intel Hardware Accelerated Execution Manager"

Currently, it supports only Intel® VT (Intel Virtualization Technology).

The Android emulator is based on QEMU. The interface between QEMU and the HAXM driver on the host system is designed to be vendor-agnostic.


Steps for Configuring Your Android Development Environment for HAXM

  1. Update Eclipse: Make sure your Eclipse installation and the ADT plug-in are fully up-to-date.

  2. Update your Android Tools: After each Eclipse plug-in update, it is important to update your Android SDK Tools. To do this, launch the Android SDK Manager and update all the Android SDK components. To take advantage of HAXM, you must be on at least release version 17.

Enter image description here

  • Download the x86 Atom System Images and the Intel Hardware Accelerated Execution Manager Driver. Follow the image below:

Enter image description here

  • Install the HAXM Driver by running "IntelHaxm.exe". It will be located in one of the following locations:

    • C:\Program Files\Android\android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager

    • C:\Users\<user>\adt-bundle-windows-x86_64\sdk\extras\intel\Hardware_Accelerated_Execution_Manager

    If the installer fails with the message that Intel VT must be turned on, you need to enable this in the BIOS. See the description for how to do this in Enabling Intel VT (Virtualization Technology) .

Install .exe or .dmg

  • Create a new x86 AVD: Follow the image below:

Create AVD

  • Or as for new SDK, Enter image description here

@Todd Price 2013-02-07 03:11:13

Good write-up. If you're looking for docs from Google (includes a few differences for Mac), they can be found here:

@Kshitiz Sharma 2013-02-18 05:29:25

Doesn't work on Linux.

@Rhyous 2013-04-29 14:35:53

I tried this solution. It worked. However, I installed using MonoDroid and couldn't find IntelHaxm.exe for a minute. It was here: C:\Users\jbarneck\AppData\Local\Android\android-sdk\extras\i‌​ntel

@Raphael Oliveira 2013-04-30 15:39:02

How to use this with a Google Api Emulator? I need it because my app uses GCM.

@conny 2013-04-30 18:39:24

@RaphaelOliveira The Google frameworks are not distributable together with the x86 image because of licensing issues. What you need to do is manually copy the relevant Google library .jar(-s) and permission .xml(-s) from an -armeabi AVD of the corresponding Android version. Search keywords: "google maps library missing android x86 emulator".

@Guillermo Varini 2013-05-09 01:34:19

not able to install Install the HAXM Driver as my pc doesnt support Intel Virtualization Thecnology(VT-x). Any other solution? (not buying a pc jeje)

@n611x007 2013-05-31 04:50:14

I guess this changes the processor from ARM to x86? ^_^ so no native / JNI applications, am I right?

@Nick 2013-06-14 14:22:58

@naxa you can still do native, you just have to set up your build to make binaries for both platforms.

@Sharique Abdullah 2013-06-20 19:28:02

Except for issues with ARM / MIPS stuff. This is the best choice I guess.

@KarenAnne 2013-06-28 07:10:29

Will this speed up the emulator? Thanks.

@Ponting 2013-07-06 16:08:24

What if i have to use Google API because i am running google services on emulator.

@Reda 2013-07-10 12:20:27

Wow, can't thank you enough! Can't believe I was living with the slow emulator all this time. I thought that was normal. I really miss the fast start up times though, isn't there a way to enable snapshot alongside GPU acceleration?

@nerdherd 2013-07-20 17:23:08

Holy smokes, GPU emulation is the answer I have been looking for! The emulator runs perfectly now, and with the x86 image the startup time isn't thaaaaaat bad (still could be better). As @Reda asks, anyone know of a way to get snapshots and GPU enabled?

@Bharadwaj 2013-07-31 09:37:25

This CPU option will not be available for Google API's. Any suggestions for that?

@awe 2013-08-06 11:02:33

I tried this, but the log said that HAXM failed to start, and still loading slowly... :(

@Vamsi Challa 2013-08-19 15:03:18

Didn't work for me. Don't know what's wrong on my system. For a moment, I imagined, my emulator on fire... Bad luck..

@Guillaume 2013-08-21 20:49:49

You are saying API17, but are showing API15..

@Ben Wheeler 2013-09-04 18:07:35

This worked, but I was stuck for a while on two things: first, "sudo kextunload –b" didn't work on my shell (macosx running bash) and I needed to use "sudo kextunload /System/Library/Extensions/intelhaxm.kext" instead when reinstalling the accelerator (I needed to up the RAM to 1536 MB). Second, I tried using an existing virtual device that was set up for acceleration, but it wasn't working; I set up a new one trying to mimic the settings above and that worked great. Initial startup took a few minutes, but after that seconds.

@Javier Novoa C. 2013-09-11 17:17:16

well @Kshitiz Sharma , it DO works on Linux, but you cannot install it via the android manager as is... First you need Quem (via KVM), and then you may use it. I just installed it and voilá, pretty neat! :D look here for mor references:…

@user1619275 2013-09-12 09:23:22

That works great. Thanks a lor for sharing this! When "Use Host GPU" is enabled, the emulator flickers heavily, but also without Host GPU enabled it's really fast now.

@numediaweb 2013-09-19 11:04:39

In my windows 7 64b setup, IntelHaxm.exe is in the C:\Users\<user>\AppData\Local\Android\android-sdk\extras\int‌​el\Hardware_Accelera‌​ted_Execution_Manage‌​r

@Jeff T. 2013-10-21 06:41:10

I tried but failed. Finally I found a new virtual device should be created instead of editing the existing one, then it works !!

@cprcrack 2013-11-10 14:23:41

You need to install HAXM manually:…

@xtmq 2013-12-17 19:33:50

@Trojan.ZBOT 2013-12-22 05:10:23

@PrashanthSams - Thanks. It is much faster now, but goddamn phone is locked. Need to make is faster. I will also try dragon fire approach

@Karioki 2014-02-21 05:52:23

if your app have native c/c++ code in it then you need to add line in Line: APP_ABI := all or for sake of efficiency append ",x86" at end. Otherwise app will crash or wont deploy.

@Kaveh 2014-02-23 19:52:32

There is now a x86 image with Google API. You may want to update the answer.

@ziftech 2014-03-05 12:42:19

It's really fast, but cause BSOD when running on windows 8

@prasanthv 2014-04-04 15:23:35

@Kshitiz Sharma For Linux user KVM. This was a great article:…

@ABS 2014-05-11 22:21:44

This solution will be usable ONNNNLY for a restricted range of CPU's! Not all Intel CPU's! For example my CPU is C2Duo E4600 and doesn't support Intel VT! And many of Intel processors are so. Refer for details.

@MeetM 2014-05-25 14:14:55

@Jerry101 2014-06-19 08:06:44

One more trick is needed for large screen tablets and phones (else the emulator startup may stream logcat messages for a good part of an hour, then croak): (Step 1) Install HAXM with 2048 MiB of memory. (Step 2) For a large-screen AVD, allocate up to 2048 MiB of memory. Ignore the "Windows can't handle giving it more than 768 MB of memory" warning. (This assumes your computer has like 8+ GB of RAM.)

@null 2014-07-28 04:47:08

Anyone who still has trouble installing Haxm even after VT is turned on, read this.

@testing 2016-03-25 09:36:49

This solution doesn't work if you need Hyper-V (e.g. for other simulators like Windows Phone 8.1).

@Zoe 2017-09-09 07:25:23

Running the hardware accelerated images are faster, but they are still slow - very slow. I have pumped 4 gigs of RAM to get it to run at least without having 5 second delays. While it is a speedup to use HAXM, it still requires a massive amount of memory to run near decent

@AG1 2017-11-15 07:23:01

HAXM has been open sourced:

@Sumukh Bhandarkar 2017-10-14 06:42:04

Firstly, you need to upgrade your RAM to atleast 8GB.

If you cannot upgrade your RAM, then try running the application on your Android Phone by connecting it via Data Cable and USB Debugging set as ON.

Also, you may use some other emulators like GenyMotion or Nox.

However, with the amount of RAM that you seem to be having, even other emulators may tend to be slow.

@Nicolas Raoul 2009-12-16 05:53:46

The emulator included in your (old) version of Eclipse is very slow.

Recent emulators are faster than they use to be in 2010. Update your SDK/IDE.

Personally, I use a real phone to do my tests. It is faster and tests are more realistic. But if you want to test your application on a lot of different Android versions and don't want to buy several phones, you will have to use the emulator from time to time.

@NickSoft 2012-03-11 11:04:04

vmware runs with unnoticed performance difference compared to the real machine. Even if emulator is emulating ARM it should be faster, even on the same system frequency and my PC is 3.6GHz which is slower than 500 MHz android phone.

@Trojan.ZBOT 2013-12-22 05:14:13

@rds - So should my AVD emulate intel instead of ARM for it to load faster ?

@Martin Zeitler 2014-05-28 18:58:55

nope, this is not optimized for x86... it emulates x86 phone hardware - while the common phone nowadays easily outperforms the machine in question:)

@Dan Dar3 2015-09-08 21:31:58

You do realize that both run the same emulator right? android-sdk\tools\emulator-x86.exe, nothing to do with Eclipse, you've probably just started using Intel x86 images with Intel HAXM.

@Bolling 2015-09-18 12:57:21

Well compared to how slow they where back in the days they go in lightning speed now.

@andgps 2010-09-11 04:12:12

You can create emulator.bat with following command to start the emulator. It will start faster.

emulator.exe -cpu-delay 0 -no-boot-anim @<avd name>

Or on Unix (Mac or Linux flavors):

emulator -cpu-delay 0 -no-boot-anim @<avd name>

@Timothy003 2011-06-10 21:39:41

Adding -no-boot-anim reduced the startup time by around 38%. Thanks!

@Ivan Chau 2015-06-26 03:58:21

(Android Studio) Select Run > Edit Configurations.... In the left panel of Run/Debug Configurations dialog, select or create a configuration. Under Target Device options, select AVD. In Emulator tab, enter -no-boot-anim in Additional command line options field

@JRE.exe 2014-05-11 14:11:02

Emulators are slow. There's really nothing you can do about it, but there are alternatives to the emulator.

  1. Genymotion - Preferred

  2. VirtualBox

  3. BlueStacks

  4. YouWave

  5. Windows Android Emulator

  6. Jar of Beans

  7. Andy

To make your emulator faster, you can host a GPU and use a lighter Android version (Android 2.3 (Gingerbread)). Developing on a Mac would be better. Why use an emulator, BTW? Using a real phone makes more sense.

@Anurag 2015-11-18 07:21:58

I have used Genymotion, and I have to say it is comparatively fast than the default Android emulator.

@Almo 2018-01-30 15:01:43

"Why use an emulator, BTW? Using a real phone makes more sense." I'm at work, and we don't have enough phones to go around. I'm not a tester, so I don't get priority on them.

@Martin Zeitler 2018-03-02 11:01:27

the emulator isn't slow, but your machine. x86 images suggested.

@Bhuro 2018-08-27 03:58:42

@Almo, Real phones are a good choice, but emulator give you space to make your app compatible with most of android Version + design in different screens, ... that's the way to let your app run with fewer bugs before it goes to testing with real phones. I have personally seen some of the design issues can be easily fixed via checking them in the different emulators ... Not all can afford to have at least 1 phone of different os and screen sizes ...

@Kaveesh Kanwal 2015-07-21 04:54:56

You can download the genymotion emulator from here. This is fast and efficient.

@Bhuro 2018-08-27 03:59:56

I got a crash when I tried to use some of the Google APIs, ...

@Kaveesh Kanwal 2018-08-30 10:47:13

No need to use any 3rd party emulator. Use android studio's own emulator which is now very stable and fast.

@Bhuro 2018-09-07 14:31:23

but those are the intel images with Intel processor on windows OS, ... what about AMD processor ... and Linux?

@Sofien Rahmouni Virtuel 2015-11-14 14:08:13

Yes, you are right since native android emulator is very slow than the other custom emulators like genymotion. I figured out that while I was running functional calabash android test.

On the native android emulator, this issue is produced when "timeout exception" occurs, so I moved to genymotion emulator who resolved the problem.

P.S: genymotion emulator is not free anymore.

@Anil8753 2015-03-18 06:25:17

Android emulator is dead slow. It takes 800MB memory while running. If you are on Windows, You can use Microsoft Android Emulator. It is superb, provides you functionalities more than Android Studio Emulator. And most important it is fast ( consumes 13MB only). It comes with Visual Studio 2015 Technical Preview. I am using it and happy with it. I downloaded and installed entire VS pack, I need to look how we can install VS Emulator only.

Visual Studio Emulator for Android


@MSS 2015-04-04 18:14:17

how do you calculate dude? it's an operation system and need a lot of ram to run. and 13 Mb It's really stupid please watch again.

@Anil8753 2015-04-05 12:04:42

@MSS I do not know the background history behind VS Emulator but I did it practically and found what I said.

@MSS 2015-04-05 12:17:34

Maybe You Made Mistake I Meant It's Impossible To Emulate Real Android OS in such Small Piece Of RAM And VS Emulator Must Be A Simple Debugging Environment For C# Made Applications And Probably Unable To Run Standard Android Application.

@Anil8753 2015-04-05 14:47:20

Yes, I am not sure about that it is real full Android emulation or just a light basic Android features emulation. Please let it give a try. Run this emulator first and later deploy your Android studio App.

@Anil8753 2015-04-05 16:43:29

I am developing android app using Android Studio and deploying it similar to other ADB devices. Just give a try

@razor 2016-05-26 11:07:25

probably MS runs emulator thru virtualization. virtualization governor - software won't show you real resources used by VM

@Potassium Ion 2017-07-17 23:17:00

I would suggest playing around with the OpenGL settings. I have a dual-core (quad-thread) i3-2350M running on it's internal GPU, and I get terrible performance if I use SwiftShaders, but changing it to "Desktop Native OpenGL" (Extended Controls > Settings > OpenGL ES Renderer) makes it run smoothly.

If the device doesn't boot, play around with the OpenGL ES API Level setting and the GPU emulation setting in the device config.

I don't know why, but on my 2011 Intel processor, it makes a world of difference.

@Suman Astani 2017-07-16 12:31:03

Android Studio performance is greatly optimized in Linux. Windows system might be running different heavy programs in background. Linux is best suited to use available system resources efficiently. Recently I have install android studio in Kali Linux. The speed of emulator and studio performance is way better than windows.

And the software development tools gets downloaded faster from android SDK. As the packages are bundled in binary files. The size of binary files are low.

@r3dm4n 2016-11-27 11:17:54

My solution is Vysor . I get both of the best worlds. I don't put too much charge on my machine, but I can also see my real Android device on the screen so I don't have to reach for it, take my hands off the keyboard etc. Furthermore there are always some feature that don't work best on an emulator.

There is free version with ads and a payed one which compared to other solutions, won't break the bank.

@Andrey Luiz 2017-03-01 18:45:48

Nice solution. Using the physical device is nice to PCs with low memory.

@Hendy Irawan 2017-09-30 10:21:27

Vysor free is sooo low-resolution. You can barely read text.

@r3dm4n 2017-09-30 10:31:20

@Hendy-Irawa you have lots of options for this... speed/resolution-quality

@T.M 2016-07-10 19:54:29

I wonder why nobody has mentioned the Visual Studio Emulator as an alternative. It's way faster than the native Android Studio Emulator.

Here's a link to performance comparison:

enter image description here

What's even better is that the apk files and even gapps (or any other flashable zip) can be installed just by drag and drop. However, the downside is that it requires Hyper-V which is only available on Windows (that too, from Windows 8 onwards). Other limitations (along with the description of the above) and other details can be found here:

@PeeHaa 2016-07-12 09:15:19

"I wonder why nobody has mentioned the Visual Studio Emulator as an alternative." It's suggested right here:

@TapanHP 2016-07-10 11:38:09

HAXM is a way to make emulators fast for intel processors HAXM is the kernel driver part, and the user-space emulator part is based on QEMU - which means there is a branch of QEMU which uses HAXM (This QEMU branch is very android-emulator-specific (and also seems to be based on older version of QEMU).

But still when i used with my intel core i3 processor with 4 GigaBytes RAM it doesn't effect more to speed. So this wasn't a solution for me.

As i am using 4GB RAM cpu Emulator becomes RAM eater but for making it more convenient there are some ways I prefer Android*86 support based emulator. And as android studio now introduce Instant-Run So After first launch app installation became faster, but i always faced problem and seems like no-way to get out of this.

I also used Droid4x and it goes preety convenient to me but i can't found a way to install different api versions ,I used it with kitkat and it was faster then android emulator and it is also VT support enabled, So i found another way and a good solution that is Visual Studio Emulator You can read more about it here , The latest i used is LeapDroid its really a powerful See the comparisons here

I prefer to use Real device then emulators on 4GB ram PCs.

@Abdul Samad 2016-07-01 09:43:17

Android studio 2.02 has been launched, it has faster emulators, if you want to go with third party, use Genymotion emulators, they are pretty fast

@MaXi32 2016-10-01 08:48:27

Genymotion is not free. Consider changing your answer, or this is just promotional answer.

@Abdul Samad 2016-10-03 07:05:31

It is free for personal use

@MaXi32 2016-10-03 16:39:35

It's not free for personal use ANYMORE.

@LEMUEL ADANE 2016-04-09 12:24:47

Add some more RAM and use SSD drive. Android Studio is best run on 8 to 12 GB of RAM using SSD drives based on my experience.

@MaXi32 2016-10-01 08:50:19

I have 10GB ram and using SSD on my laptop. my processor is i3, with a graphic card Nvidia Geforce 920M. The emulator still slow.

@huisinro 2016-06-21 17:16:38

You can try our new Android virtual machine, Leapdroid, which is fully compatible with the original Android emulator. Since it uses virtualization technology, instead of emulation, it provides pretty much native speed. In addition, we use a new OpenGL technology called LeapGL, which performs OpenGL graphics in native speed. Our vm has the best performance compared to others.

Source code:

Leapdroid is fully compatible with Eclipse and Android Studio, as it uses the same adb ports.

@Chintan Soni 2016-06-13 17:52:34

Gone were those days, when we used to run projects on slow Android Emulators. Today, Android Emulators are on steroids.. Yeah you heard me. No other emulators are as fast as Android Emulators. You can go to my blog for more details:

I have explained in details about new Android Emulators. Check it out.

Believe me they are as fast as your real device works.

@Gábor 2016-08-14 19:37:43

Well, you call this fast? AS 2.1.2, Marshmallow, latest image downloaded right now, HAXM, everything. The emulator itself can't start in about 30 minutes, let alone testing anything on it...

@Chintan Soni 2016-08-15 03:36:47

@Gábor may i know your hardware configurations ?

@Gábor 2016-08-15 10:18:02

Quad-core @ 2,4 GHz, 8 GB memory, system on SSD with plenty of free space, Windows 10 Pro, AS 2.1.2, HAXM 6.0.3 (as per the SDK Manager). The virtual device is a Nexus 5X/6 as created and downloaded by the AVD Manager, fresh. I can't run anything directly from AS because it always times out at 300 sec. I tried to start the emulator first and leave it running but it can't start in 25-30 minutes. Not freezing, the "android" logo is animated all the time. Instant Run enabled. Running on my physical device is error free.

@CyprUS 2016-05-25 01:56:02

If you can, switch to using Ubuntu for Android development. I switched to Ubuntu 14.04 LTS for Android development, and I am glad that I took the jump. All of the steps mentioned made little or no difference in the lag on Windows. Linux is the correct answer to all the problems you are facing

@Christian 2016-06-30 18:38:00

Despite all those negative votes, that's the best "solution". I did that 4 years ago and I've been living happy since then. People should TEST on windows, but not develop ON it.

@CyprUS 2016-06-30 19:15:40

@Christian : I wonder why the down votes. Hacking for a solution on Windows is futile, I know this because I have tried all the steps.

@Christian 2016-07-01 16:32:00

Yeah... there are so many advantages when developing on Ubuntu... there are no usb drivers to install... eclipse runs pretty much faster, no more freezings/hangins... it's so much better... I wonder WHY ppl insist in windows (for android development).

@Umer 2016-04-09 08:48:57

Update your current Android Studio to Android Studio 2.0 And also update system images.

Android Studio 2.0 emulator runs ~3x faster than Android’s previous emulator, and with ADB enhancements you can now push apps and data 10x faster to the emulator than to a physical device. Like a physical device, the official Android emulator also includes Google Play Services built-in, so you can test out more API functionality. Finally, the new emulator has rich new features to manage calls, battery, network, GPS, and more.

@abissa 2016-02-22 18:33:40

I suggest you to use the Android phone for developing by USB Debugging. It gives better experience in testing the apps and a better output compared to virtual devices. Or you can also use the options mentioned in rest of the answers and can go with Bluestacks App Player, it is also a good option in case of non-availability of Android Device.

@Umer 2015-12-29 12:31:19

Good way to speed up Android Emulator and app testing is Install or Upgrade your Android Studio to Android Studio 2.0 version and then go to app open Settings/Preferences, the go to Build, Execution, Deployment → Instant Run. Click on Enable Instant Run. And After That This will ensure you have the correct gradle plugin for your project to work with Instant Run. enter image description here

And Instant run will look like this New Run & Stop Actions in Android Studio for Instant Run

However Android Studio is right now in Preview you can try it now.

@Arūnas Bedžinskas 2016-04-08 12:47:04

Android Studio 2.0 is stable now. Instant run increases build speeds not emulator speed, check for more info: <‌​tml>

@Umer 2016-04-09 08:40:57

The new emulator runs ~3x faster than Android’s previous emulator. and now you can now push apps and data 10x faster to the emulator than to a physical device.

@Vamsi Challa 2016-06-09 12:20:15

Please be aware that when you are using Instant Run, there are some issues when installing on devices < 5.0. If you see that your app crashes on devices from kitkat and below, disable instant run and re-build it. You should be good to go..

@Vipul J 2015-11-18 05:05:49

Try Genymotion for Android Studio. Blazing fast! Just needs one time installation. No more AVD pain.

@DineshM 2015-10-27 14:04:28

Now instead of using emulator we can test Android apps using ARC Welder app on Chrome, App Runtime for Chrome

@NooBskie 2015-10-21 06:38:05

A few things that definitely sped things up for me with this were

1. delegating the rendering process to the GPU by checking "Use Host GPU" checkbox in AVD's edit window.

2. downloading the Intel Atom (x86) image or if you are a windows/mac user downloading the Intel x86 Emulator Accelerator HAXM

Unfortunately the thing with Intel x86 images is that you don't get Google Apps, they only come with ARM images.

which is where Genymotion comes in handy

  1. Download and install VirtualBox. For Windows users it's not necessary to install VirtualBox separately, because it is available from the Genymotion site, bundled with the Genymotion emulator.
  2. Go to Genymotion website and sign up. You'll receive a validation mail, so just click on the validation link to proceed.
  3. Download and install the Genymotion emulator.
  4. Start Genymotion. You might need to configure path to your Android SDK location in Genymotion settings (probably if you've installed SDK in a non default location). Since this is a first start, there are no devices. Click on "Add" and download new device. To see available devices, write your credentials in the pop-up dialog and click "Connect".
  5. Select the device and click "Start".

@MaXi32 2016-10-01 08:55:36

Genymotion is not free anymore.

Related Questions

Sponsored Content

31 Answered Questions

[SOLVED] How to emulate GPS location in the Android Emulator?

41 Answered Questions

[SOLVED] How can you speed up Eclipse?

  • 2008-11-25 03:18:56
  • user2427
  • 571572 View
  • 1230 Score
  • 41 Answer
  • Tags:   eclipse performance

30 Answered Questions

[SOLVED] How to get the build/version number of your Android application?

26 Answered Questions

10 Answered Questions

[SOLVED] Improve INSERT-per-second performance of SQLite?

5 Answered Questions

My Android application is working very slowly

5 Answered Questions

30 Answered Questions

[SOLVED] How do you install an APK file in the Android emulator?

1 Answered Questions

23 Answered Questions

[SOLVED] How do I rotate the Android emulator display?

Sponsored Content