Why is the Android emulator so slow? How can we speed up the Android emulator?

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

-
Alternate is Genymotion. genymotion.com. This is much mcuh faster. Straightforward installation. – Sukitha Udugamasooriya
You're much better off using Andy the Android Emulator. GenyMotion locks you out of most features unless you pay $35 a month! – Mike Bethany I have found the emulator to run way (and by way I mean waaaay) faster on linux. I've got a laptop with dualboot, on windows the emulator takes about 15 minutes to start up, with linux about 30 seconds. I do not know about other operating systems like OSX, but feels like a windows thing to me. – Daniël van den Berg alternatives (most featuring more responsive, faster emulation) to the official Android emulator have been documented in this question: //allinonescript.com/questions/13112889/… – CCJ Android Studio 2.0 is reported to not only have a much faster emulator, but employ "instant run", which allows certain changes in your source, such as the XML, to be deployed in seconds to the target without the APK having to be rebuilt and redeployed. See android-developers.blogspot.co.uk/2015/11/… – Carl Whalley A new way introduce by google is Instant run you can check it here //allinonescript.com/a/34511114/2489061 – Umar 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. leapdroid.com – huisinro i think your ram is very small for an emulator to run faster. – Zia U Rahman Because it was made by google, which is interested in selling devices, – f470071 One way of avoiding confused comments could be to have a little notice box saying the question is older than, say, 2 years old. Tech is changing rapidly, and you would want age to affect rank, even though the question shouldn't be closed/archived as on lesser sites. – Henrik Erlandsson Real Phone device is cheap enough. – iamcxl Emulators require at least 1gb ram to run, eclipse need 1gb, XP OS need 256mb! so you should have at least 3 gb ram to run emulator properly, try to build lower version of android on emulator like version 2.3, it will be like 10 times faster than android version 4! On top of that, your cpu is too weak! besides, eclipse is outdated now and in order to use android studio and android 6 emulator try cpu i5 and 8gb ram. – Reflection increase your system ram – faisal iqbal If you can have a SSD hard disk, it would tremendously speed up the Android Studio and the emulator. – Pronoy Mukherjee 85 Answers 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. - 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. – NickSoft @rds - So should my AVD emulate intel instead of ARM for it to load faster ? – Trojan.ZBOT nope, this is not optimized for x86... it emulates x86 phone hardware - while the common phone nowadays easily outperforms the machine in question:) – Martin Zeitler 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. – Dan Dar3 No, they are not fast. September 2015. Still suckingly slow – ACV Well compared to how slow they where back in the days they go in lightning speed now. – Bolling The option -cpu-delay <delay> described in Emulator Startup Options can help. - The link goes nowhere now. Is this still relevant? – Andrew S Try to disable your antivirus. Maybe it will make emulator a little bit faster. - I found this to be true as well -- I removed AVG Free and installed MS Security Essentials, and the emulator starts noticeably faster. YMMV. – Guy Starbuck it's still super sluggish on linux systems... which obviously don't typically have av – alex.pilon I have NO antivirus. Still takes ages.. – Robin Maben Did anyone else read this thinking it was a joke? – jdero My emulator is so slow on my Linux without AV that it just opens a black window and hangs.My other computer with Windows doesn't support vt-x so it doesnt work. – Suici Doga I've noticed that the emulator starts much faster if there's no Dalvik Debug Monitor Server (DDMS) connected. So if you start the emulator from Virtual Device Manager "SDK Setup.exe" and Eclipse is not started, the emulator works faster. If you start the emulator from Eclipse: DDMS is there, so sometimes the emulator is extremely slow, but sometimes it's faster. - How to fix the issue? – SmallChess @Shekhar: DDMS = Dalvik Debug Monitor Server – Lie Ryan if we run the emulator through Cordova command line of Git Bash... how to disable the Dalvik Debug Monivor Server anyway? – gumuruh The startup of the emulator is very slow. The good thing is that you only need to start the emulator once. If the emulator is already running and you run your app again, the emulator reinstalls the app relatively quickly. Of course, if you want to know how fast it will run on a phone, it is best to test it on a real phone. - If it takes a couple of hours, there is probably something else wrong. It only takes a couple of minutes for me. – Jay Askren what is your hardware configuration and operating system? – Junior M @Junior Mayhe: I've programmed for Android using Windows, Mac, and Linux. I use Mac most often right now. The computers I've used have 2 to 4 gigs of RAM and a fairly modern 2 to 3 ghz processor. In all cases, it seems take several minutes to first launch the emulator, but then re-installing the app is fairly quick. – Jay Askren @user286101: loading a new apk into an already running emulator takes no more than 10 seconds in my old laptop (1.6Ghz dual core, 1GB RAM), the only problem is I often forgot to leave the emulator running so I had to go through the slow rebooting process (which takes 3-5 minutes). – Lie Ryan @LieRyan "should take no more than 10 seconds" sadly, that's about the time of a simular sized C++ project in today's machines. – kizzx2 +1 , this must be an accepted answer. – Shankar Damodaran It really does take more than an hour to start. Plus, it takes about 10 minutes to respond to simple swipes or clicks. Completely unusable. Simulator is just a miserable way to waste some disc space, nothing more. – f470071 To add further information to this. I have recently upgraded my Ubuntu installation to Ubuntu 10.04 LTS (Lucid Lynx) which in turn updated my Java version to: Java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)  And now the emulator (although takes a while to start) seems to be running faster than previously. It might be worth people upgrading their JVM. - 64-bit java is faster ( ~2 times) than 32-bit java on same machine. – j4n bur53 I can't see why the emulator speed should depend on the Java version. The emulator is not written in Java and does not run on the JVM. – Lena Schimmel I'm using 64-bit Oracle Java 1.6.0_26 and my Emulator is slower than a turtle... its painful. Core2Quad, 64-bit Java+Ubuntu 11.10, 8GB Ram. – djangofan If it's not written in Java and does not run on the JVM, then why does it require Java (and not any version of Java either!) – Rolf 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>  - Adding -no-boot-anim reduced the startup time by around 38%. Thanks! – Timothy003 How to use this command please help me!!! – vijay (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 – Ivan Chau I had intermittent slow emulator (SDK v8.0) load times, up to three minutes on Intel Core i7 920 2.67 GHz CPU running on Xubuntu 10.04 VirtualBox 3.2.12 guest with Eclipse (3.6.1) loaded. I changed the VirtualBox guest memory from 1024 MB to 2048 MB and from that point on, I never experienced the slowness again (load times consistent at 33 seconds, CPU load consistent at 20%). Both Eclipse and the emulator are memory hogs. - I noticed that the my emulator (Eclipse plugin) was significantly slowed by my Nvidia graphics card anti-aliasing settings. Removing 2x anti aliasing from the graphics menu and changing it to application controlled made it more responsive. It is still slow, but better than it used to be. - Android emulator release 9 has a new "snapshot" feature. You can save the state of the emulator (make an image of the emulator) and avoid booting when you start the emulator. - Update: The feature described here has been removed from the latest stable versions of Android studio but it is available as "Quick boot" in the canary channel. 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 the given below screenshots for more information. Creating a new AVD with the save snapshot feature. Launching the emulator from the snapshot. And for speeding up your emulator you can refer to Speed up your Android Emulator!: - When you update and existing device, wipe the user data on the first startup from snapshot – Mark Bakker I set the AVD as this, but seems still slow when I reboot the AVD, why? – zhongshu @zhongshu: When you reboot AVD then it starts from the beginning state rather than the saved snapshot. So probably it will take more time. – Vikas Patidar 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.) – zhongshu @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. – Vikas Patidar 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. – djangofan I was unable to get to the launch options dialog. How do you open it? – Peter Ehrlich @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. – Vikas Patidar 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 – Chris command line version? – n611x007 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. – awe 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. – michaelsnowden @ 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. – Vikas Patidar There is a use host GPU option as well, next to snapshot. It might help as one of the answers mentioned. – Trojan.ZBOT @Trojan.ZBOT Both options are for speed-up but you can not use both together. – Vikas Patidar Oddly, on my machine (quad core AMD), I've found that reducing RAM makes the emulator faster and increasing RAM slows it down. – Brian Knoblauch 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 – vharron This answer and the one mentioning the HAXM really increased the speed. Now it only takes about 10 seconds to load. Great! – jAC 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. – Sam @Sam Please refer below answer, it's almost 4 year old trick and not relevant for today. – Vikas Patidar How do you do it for Android Studio? – Cows quack @KritixiLithos Toos > Android > AVD Manager > Create New Virtual Device > Next > Select hardware > Next > Select System Image > Next > Check Use Host GPU – Vikas Patidar 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. leapdroid.com – huisinro 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). – B-GangsteR 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. – Shirkam On a 3.4 GHz quad core 6 GB of RAM, Windows 7, the emulator was unusably slow! I downloaded Launcher-Pro.apk through the emulator, installed it and set it as the default launcher. It doubled my emulation speed! The screens load much smoother and faster. It doesn't seem to download in 2.1 or 2.2, only in 2.0. - After developing for a while, my emulator became brutally slow. I chose wipe user data, and it was much much better. I am guessing that it takes time to load up each APK file you've deployed. - Try Android x86. It's much faster than the Google Android emulator. Follow these steps: 1. Install VirtualBox. 2. Download the ISO file that you need. 3. Create a virtual machine as Linux 2.6/Other Linux, 512 MB RAM, HD 2 GB. Network: PCnet-Fast III, attached to NAT. You can also use a bridged adapter, but you need a DHCP server in your environment. 4. Install Android x86 on the emulator, run it. 5. Press Alt+F1, type netcfg, remember the IP address, press Alt+F7. 6. Run cmd on your Windows XP system, change the directory to your Android tools directory, type adb connect <virtual_machine_IP>. 7. Start Eclipse, open the ADT plugin, find the device, and enjoy! - so I connected. How do I get the screen to be vertical? I also don't see the phone hardware buttons anywhere. – Alex well, I figured out some of the hardware buttons (below) but I still wish someone would tell me how to change the orientation to portrait mode. Home = Windows key; Back = Esc; Menu = Windows menu key (I had no idea my keyboard had one!); F4 = Reboot options; – Alex I haven't found an opportunity to change screen orientation. groups.google.com/group/android-x86/browse_thread/thread/… they say that the orientation is probably hardcoded somewhere, and I can't find more information. Let me know if you solve the problem. – Pehat Just to remind you guys that you need to enable mouse integration in the device menu if you like to use the mouse in the emulator! – kakopappa Note that if you are using anything that's specific to ARM (like Mono for Android, for instance), it won't work on Android x86. – Matthew Groves So... how much faster? – Bernie Perez I decided to try and install on VMWare. Struggled all day trying to get eth0 to work. Found a developer building VMWare images that work seamlessly... groups.google.com/group/android-x86/browse_frm/thread/… – Michael Gorham For me, netcfg is showing lo 127.0.0.1 255.0.0.0 0x00000049 Is here 127.0.0.1 IP which I should mention in adb command ? its showing "unable to connect to 127.0.0.1:5555" Please help. – Dev 127.0.0.1 is "localhost", so you won't be able to use that to connect. you must not have networking working correctly yet. – jay it did the same thing for me when i tried asus laptop, android-x86-2.3-RC1-eeepc.iso worked correctly – jay also, i had to use NAT, for some reason the 10.* address wasn't working properly for me. then step 7 if you have been using the emulator, open run configurations, target tab, and make sure "Manual" is chosen for target selection mode. then run it and it will prompt you to select a device or AVD. – jay Hello nice method Could you please me how to set screen size as well thanks,kariyachan – DroidBot It doesn't appear they have a single Google TV image for Android 3.1 – djangofan With ADT rev 17 Intel acceleration is integrated. See android-developers.blogspot.jp/2012/03/… and developer.android.com/guide/developing/devices/… – ThomasW No networking for me either with the asus_laptop image. Is the solution to use the eeepc iso? It isn't clear if that's the solution to the networking.... seems like we should be able to solve this with the asus_laptop image. Anyone? – MountainX The Intel system image is still extremely slow... – James Wald A similar setup that usese bridge mode is discussed here: androiddevnotes.com/2011/03/08/1299521520000.html – Tash Pemhiwa Howto of the android-x86 project: code.google.com/p/android-x86/wiki/VirtualBoxHowTo @Click-Upvote: They took eeepc ISO. – sulai To change screen resolution, for example to 320x480, follow this guide: //allinonescript.com/a/8273560/1208581 – sulai I had a problem with the first ISO I tried. If you have the same problem, take a look at superuser.com/questions/410192/… – Felipe Micaroni Lalli Cannot enable network. Should it just work? – jayarjo use android-x86-4.0-RC2-eeepc.iso, see also android-x86.org/documents/virtualboxhowto – PiTheNumber Android x86 supports Google API? Because my project have maps to be loaded. – Bharadwaj How is the GLES2 support ? Are things forward to the host GPU and running at 60 FPS or very far from it ? – RelativeGames FYI, also runs fine in Parallels Desktop – lhunath Whatever I do and whichever image I use, I cannot get android to see the network. I tried both NAT and bridge, I have DHCP on my network, but nothing works. I can't enable wifi in the android if that matters, and the android would not report its mac address. netcfg does show an address that belongs to my DHCP-enabled network, but I want the built-in browser to work. What do I do now? – GSerg If you're using IntelliJ, use the "Show chooser dialog" to launch into x86. – occasl if your app have native c/c++ code in it then you need to add line in Application.mk Line: APP_ABI := all or for sake of efficiency append ",x86" at end. Otherwise app will crash or wont deploy – Karioki Here a video that show you how to do it step by step youtube.com/watch?v=7wIcFiRz76c – Jaider This is very fast on my core i3 system with VT-x in both Windows (with Kaspersky) and Linux (no antivirus, slightly faster). It is as fast as booting it normally – Suici Doga I did everything right but I got offline device! why? – Basheer AL-MOMANI i changed the network setting to Adapter bridged and the ip changed and worked fine – Basheer AL-MOMANI Step 4 states Install Android x86 on the emulator, <-- what emulator? should that step be 'install the iso on your VM in VirtualBox' ? – wal Good idea, but doesn't seem to be working that fast. I've been waiting for 5 minutes for it to boot... – soger This link shows how to perform step 4: tactig.com/install-android-6-0-marshmallow-virtualbox-pc – gimmegimme Also I had to navigate to ~\AndroidSDK\platform-tools, NOT ~\AndroidSDK\tools, to find adb.exe – gimmegimme to get adb connect to work, i had to follow the directions here: //allinonescript.com/a/30002653/1815210 – gimmegimme The native Android emulator now supports x86 images too – Zoe Try scaling down the emulator, it makes it a bit faster, even if it doesn't it really feels faster. - The current (May 2011) version of the emulator is slow particularly with Android 3.0 (Honeycomb) primarily because the emulator does not support hardware GL -- this means that the GL code gets translated into software (ARM software, in fact) which then gets emulated in software in QEMU. This is crazy-slow. They're working on this problem and have it partially solved, but not with any sort of release quality. Check out the video Google I/O 2011: Android Development Tools to see it in action -- jump to about 44 minutes. - I've similar issues on a Mac. What I did; • 1) on the emulator, settings-display -> disable screen orientation • 2) on Eclipse, emulator startup options -> -cpu-delay 100 Those had some effect in lowering CPU use (not it is around 40-60%), not ultimate solution. But again, the CPU use is NOT >100% anymore! - I just took the default Android 3.1, and it was very slow, but since I realised my code was Android 2.3.3 compatible I switched to that. It's about 50% quicker and also the emulator looks more like my phone, and has a keyboard permanently displayed so that it is easier to use. - The emulator seems to slow itself down when idle. This is made apparent by rapidly mousing over the keys on the side and observing the light-up responses. As a workaround, I pass -icount auto to QEMU when starting the emulator. You can make a batch file called my_avd.bat to do it for you: emulator @my_avd -no-boot-anim -qemu -icount auto • @my_avd -- launch a virtual device named 'my_avd' • -no-boot-anim -- disable animation for faster boot • -qemu args... -- pass arguments to qemu • -icount [N|auto] -- enable virtual instruction counter with 2^N clock ticks per instruction This made animations buttery smooth and sped up adb install tenfold. - why does icount auto makes it faster? – Pacerier thank you. -no-boot-anim does seem to boot android faster! – Ajay Impressive .... Specifically I was stuck with very low transfer speed of 'adb'. Now it's really fast, just as fast as x86 image. Thank you – Mohsen Afshin I am using eclipse. Do you know how to set up those options in my environment? – kta @timothy003 Which Version Of Android x86 Do You Test? I test it on android 4.2.2 x86 and it dosen't boot when i add "-qemu -icount auto" – MSS @MSS I have no idea... It's been years since I used the Android emulator. Sorry! – Timothy003 The older Android versions run a lot faster. When I'm on my netbook, I use Android 1.5 (API level 3). There are a couple of drawbacks, though--your apps need to support the older platforms (obviously), and ndk-gdb requires running Android 2.2 (API level 8) or higher. But regularly testing apps against older platforms is a good idea anyway. - You need more memory. Here's why I say that: I'm using VirtualBox on Windows to run Ubuntu 10.10 as a guest. I installed Eclipse and the Android SDK on the VM. My physical box has 4 GB of memory, but when I first configured the Ubuntu virtual machine, I only gave it 1 GB. The emulator took about 15 minutes to launch. Then, I changed my configuration to give the VM 2 GB and the emulator was running in less than a minute. - i have 16Gb 1333 Ram in i5 with sad disk and it is slow as hell .. the problem is not in ram :-( – Zorb The problem is ram if you give it too little. But diminishing returns. There's probably isn't much of a difference between 4gb and 5gb. – Anubian Noob how about if we just follow the windows default setting for making that virtual memory allocation@Corey? – gumuruh 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 a 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. - I tried booting the emulator from Eclipse (Indigo and Android 1.5, no Snapshot) and after 45 minutes I stopped it, because nothing had happened. Statistics: Phenom Quad @2.6 MHz with 4 GB DDR2 Corsair Dominator @800 MHz. The AVD is on an SSD drive and the emulator on a 7200 RPM HDD. I started the emulator manually with the -no-boot-anim option and it loaded in 30 seconds. :) In CMD, navigate to folder where the emulator.exe file is and type emulator.exe @<YourAVDFromEclipse> -no-boot-anim  The emulator.exe file is located in the Android SDK folder under Tools. In Windows, you can find the the Android Virtual Device(AVD) under C:\Users\<NAME>\.android\avd. The projects run from inside Eclipse, targeting the AVD you booted, show up just nicely :D - I would appreciate to know why i got downvoted. This worked for me on a second development machine (a laptop with a core2 and 3GB RAM with a 5200 rpm HDD) – Andrei In AVD Manager select the VD and click edit, set the resolution to little as you are able to read the text on VD. I use 800x600 pixels, RAM set to 512 MB, and it works like a charm without high use of CPU time. - As of Revision 17 of Android SDK Tools, the emulator can use graphic acceleration and CPU-provided extensions for better efficiency. The prerequisites and full configuration and user notes are at: For enabling GPU aceleration, run the emulator from the command line or add "-gpu on" to the additional emulator command line options in the AVD configuration. emulator -avd <avd_name> -gpu on  For using the CPU machine extensions, you have to install the driver (caution because it can conflict with existing VirtualBox or VMware drivers). Once it's installed it will be used automatically whenever you use an x86-based AVD. - I just discovered this myself. Makes the emulator run almost as well as a real device! – Gerald Kaszuba Note that to use GPU acceleration you must use Android 4.0 or later. Also, with current tools you can't use BOTH snapshots and GPU acceleration at the same time, you have to choose (I personally prefer having GPU acceleration and slow emulator start). – mav Android SDK rev. 17 supports Virtual Machine Acceleration using AMD and Intel virtualization technologies. This feature can improve the emulator performance a lot! See the following section in the Android emulator documentation for more details: Configuring Virtual Machine Acceleration Don't forget to install the appropriate driver for your operating system: After you have installed the drivers and downloaded an Android X86 system image (as described in the documentation) you should be able to create a new AVD using the x86 image: For example: • Target: Intel Atom x86 System Image - API Level 10 • CPU/ABI: Intel Atom (x86) - unfortunately, currently AMD-V is only supported on linux (SDK rev 17). – Amir Ali Akbari Intel HAXM made my x86 AVD 200%~300% faster then before! Great! – Lcsky Android ADT 18 now includes a (beta) GPU enabled option (simply enable the GPU acceleration from your AVD properties). It makes a huge difference and even ICS feels relatively comfortable now. - I have noticed that an emulator gets slow over a period of time. So, one can delete the emulator which gets very slow and create a new one with the help of the AVD manager. I have tried it a couple of times and it works well. - 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 com.intel.kext.intelhaxm (mac)  If HAXM is working properly, you may see this message when launching the emulator: HAX is working and emulator runs in fast virt 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. - Be careful when using a virtual machine with Intel HAXM. Apparently the virtual environment can become corrupt if system memory is exhausted. – James Wald android-dev.ro/web/guest/home 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. – sulai 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. – jayarjo Do you also have hardware GPU emulation enabled? – James Wald 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 – Tony 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 – gerrytan I confirm that the emulator now runs like a F1 car on Mac OS. – poiuytrez i donsnt have HAX any other solution for this? – PankajAndroid 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. – James Wald
do i have to stop (because you said I should start it) the Intel HAXM after i finished my work with eclipse? – John Brunner
I generally leave it loaded all the time. It only consumes memory while emulators are running. – James Wald

The fastest emulators at the moment of writing this are the built-in x86 emulators which come with the Android SDK. You can find them in AVD manager where you create virtual machines. Simply pick any of them and then you pick the type of CPU (choose x86 for best performance). It will be as fast as your machine.

The latest such machine for Android 4.0 and 4.0.3 can be found in Giving your Android Emulator a Boost: Building Android ICS with Goldfish & x86 KVM support on EC2 - TestObject.

Note: This is only for a development purpose. To test for performance, you still have to either use a real device or test on the emulator with ARM CPU.

-

Enabling snapshot may not make it faster in the first run; do not go for big SD size. Adjust the SD card size to 100 MB in the first run.

-

For fast testing (<1 second) use buildroid with VirtualBox's first network card set to “host only network” and then run

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb connect *.*.*.*:5555
connected to *.*.*.*:5555


(^) DOS / bash (v)

# adb connect *.*.*.*:5555
connected to *.*.*.*:5555


where *. *. * .* is the buildroid IP address you get by clicking the buildroid app in buildroid main screen.

-

Well, since somebody suggested Android x86 as an alterantive 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 127.0.0.1


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

-
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. – nesimtunc
I think you meant "fluid and fast" :) Anyway, thanks. Nice tip, too bad it runs Android 2.2 – Rolf
@Rolf Oh right, haha :) However, this answer is old. You should check out Genymotion. It's way better. – Ahmad

I would insist you to install BlueStacks now as it works the same as the emulator with many other functionalities in that (for example, it gives access to Android Market). Also you can run applications directly from Eclipse to BlueStack Device/Emulator with a great performance speed. It just takes a fraction of second to run your application from Eclipse to the BlueStack emulator.

-

Remove unwanted activation of some of the plugins at start-up by going to windows-->preference-->General-->Startup and shutdown. Also make sure you don't use those plugins in any of your views

Eclipse is not a word processor. Better to disable the spell check. Disabling spell check will reduce the eclipse burden by going to Windows-->Preference-->General-->Editors --> Text Editors-->Spelling

When eclipse builds the project, it will delete all output folders and rebuild classes built by other compilers. We can disable such features, as deleting the output folders and rebuilding will take sometime. Goto Windows-->Preference-->Java-->Compiler-->Building

Disabling label decorations which is of less use for you, will also help you to gain some performance . Goto Windows-->Preference-->General-->Appearance-->Label Decorations

Close unwanted projects and use working set option to move from one group of project to another smoothly.

You could also disable Eclipse automatic building, if it is not needed for you. Goto Project-->Build Automatically (uncheck it)

Do not keep lot of tabs opened in the editor. Better to have around 20 tabs . Regularly close the unused tabs. To open resource we can always use ctrl+shift+R and ctrl+shift+T (java resource) instead of opening lot of tabs

Disable unwanted plugins. Full J2EE eclipse version has an option to disable/uninstall plugins. Goto Help-->Software Updates-->Manage Configuration. Right click on any installed plugin to get disable option. If this option is not available then enable Classic Update by going to Windows-->Preference-->Capabilty and check classic update. Now the manage configuration option should be available in help menu

-

To reduce your emulator start-up time you need to check the "Disable Boot Animation" before starting the emulator. Refer to the Android documentation.

If in case you don't know, you do not need to close the emulator every-time you run/debug your app. If you click run/debug when it's already open, your APK file will get uploaded to the emulator and start pretty much immediately. Emulator takes annoyingly long time only when it started the first time.

Here are some tips to speed up the Android emulator: How to speed up the Android Emulator by up to 400%.

-

Here's what I noticed nobody mentioned it at all.

Assign all available processors to the emulator

Here's what you can try. It does speed up the emulator for me, especially during loading time. I noticed the emulator is only using a single core of the available CPU. I set it to use all available processors.

I'm using Windows 7.

When the Android emulator is starting, open up the Task Manager, look under the Process tab, look for "emulator-arm.exe" or "emulator-arm.exe *32"... Right click on it, select Processor Affinity and assign as much processor as you like to the emulator.

-
This sped things up quite a bit on my Windows 7 machine – Rocco The Taco
How to do that on Windows 8? – Eng.Fouad
I suppose you could use Windows 8 task manager to do the same ? Sorry I don't have windows 8 at the moment. – Harvey Darvey
On Windows 10, and I assume Windows 8 as well, you have to go to the Details tab in the Task Manager to do this. Though in my case all 4 cores were already selected. I wish they'd allow AMD devices to run the x86 images as well, even without the HAXM driver they should be faster than the ARM images. – A.Grandt

I just noticed something I can't explain, but hey, for me it works!

I was compiling Android from sources anyway and the built-in emulator started in a few seconds (my machine is dual core AMD 2.7 GHz) and in a minute, perhaps two at the first run, the system was up. Using Eclipse ADT bundle, on the other hand, resulted in half an hour of emulator startup. Unacceptable.

The solution that works here (I have no means to test it on other machines, so if you feel inclined, test and verify):

• Download and build Android SDK on your machine. It may take some time (you know, compilation of whole system is tiresome). Instructions can be found here:
1. Initializing
3. Building (I changed commands to 'lunch sdk-eng' and 'make sdk -j4'; besides that build tips are useful, especially concerning ccache and -jN option)
• When done, run 'android' and the SDK manager should appear. Download tools and desired platform packages. If commands are not found, try rerunning '. build/envsetup.sh' and 'lunch sdk-eng' commands to set up pathes; they are lost after exiting a terminal session.
• Run 'emulator' to check how fast it starts up. For me it's MUCH faster than the Eclipse-bundled one.
• If that works, point Eclipse to the SDK you just compiled. Window-Preferences-Android in left pane -> choose SDK location. It should be dir with 'tools' subdir and something in 'platforms' subdir. For me it's <source base dir>/out/host/linux-x86
• Apply/OK, restart Eclipse if needed. If it does not complain about anything, run your Android app. In my case, the emulator starts in a few seconds and finishes boot in under a minute. There is still a bit delay, but it entirely acceptable for me.

Also, I agree with running from snapshot and saving state to snapshot. My advice concerns only emulator startup time. I still have no idea why it is so long by default. Anyway, if that works for you, enjoy :)

-

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.

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

• Install the HAXM Driver by running "IntelHaxm.exe". It will be located in one of 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) .

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

• Or as for new SDK,
-
Good write-up. If you're looking for docs from Google (includes a few differences for Mac), they can be found here: developer.android.com/tools/devices/emulator.html#accel-vm – Todd Price
Doesn't work on Linux. – Kshitiz Sharma
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 – Rhyous
How to use this with a Google Api Emulator? I need it because my app uses GCM. – Raphael Oliveira
@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". – conny
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) – Guillermo Varini
I guess this changes the processor from ARM to x86? ^_^ so no native / JNI applications, am I right? – n611x007
@naxa you can still do native, you just have to set up your build to make binaries for both platforms. – Nick
Except for issues with ARM / MIPS stuff. This is the best choice I guess. – Sharique Abdullah
Will this speed up the emulator? Thanks. – KarenAnne
What if i have to use Google API because i am running google services on emulator. – Ponting
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? – Reda
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? – nerdherd
This CPU option will not be available for Google API's. Any suggestions for that? – Bharadwaj
I tried this, but the log said that HAXM failed to start, and still loading slowly... :( – awe
You, my man, are a GOD... Thank you. @awe, be sure you have not skipped the installation step. I sure did before, but after that it's working. – cosmincalistru
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.. – Vamsi Challa
You are saying API17, but are showing API15.. – Guillaume
This worked, but I was stuck for a while on two things: first, "sudo kextunload –b com.intel.kext.intelhaxm" 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. – Ben Wheeler
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: software.intel.com/en-us/blogs/2012/03/12/… – Javier Novoa C.
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. – user1619275
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 – numediaweb
@Alexander The owner of this question has the rights to accept it; perhaps he is not :( – Prashanth Sams
I tried but failed. Finally I found a new virtual device should be created instead of editing the existing one, then it works !! – Jeff T.
You need to install HAXM manually: //allinonescript.com/questions/10761696/… – cprcrack
@PrashanthSams - Thanks. It is much faster now, but goddamn phone is locked. Need to make is faster. I will also try dragon fire approach – Trojan.ZBOT
if your app have native c/c++ code in it then you need to add line in Application.mk Line: APP_ABI := all or for sake of efficiency append ",x86" at end. Otherwise app will crash or wont deploy. – Karioki
There is now a x86 image with Google API. You may want to update the answer. – Kaveh
It's really fast, but cause BSOD when running on windows 8 – ziftech
You must have an INTEL CPU for this to work. :( – john ktejik
@Kshitiz Sharma For Linux user KVM. This was a great article: software.intel.com/en-us/android/articles/… – prasanthv
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 ark.intel.com/Products/VirtualizationTechnology for details. – Ali Bagheri Shakib
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.) – Jerry101
Anyone who still has trouble installing Haxm even after VT is turned on, read this. – null
Does this work in a Mac Mini with Mavericks? Thanks. – Ricardo
@PeterMortensen Thank you for the edits. Please accept this post as right answer, if you find this is really valuable and a perfect match for the question. Thank you :) – Prashanth Sams
This solution doesn't work if you need Hyper-V (e.g. for other simulators like Windows Phone 8.1). – testing
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 – Zoe
HAXM has been open sourced: github.com/intel/haxm – AG1

Now on ADT 21, it provides more options for a fast emulator... You should use 512 MB RAM, lower CPU Time, Device Selection and VM Heap Size high. For better results, you should use Intel Atom in CPU/ABI... Using Snapshot and CPU Host may not increase your speed of the emulator, but there are useful ones for other purposes.

-

I just started yesterday on Windows 7 and was facing the same problem. The easiest solution, I found and is working for me is to use the low config device in the emulator. I used Nexus One instead of Nexus 7 and select the snapshot for the device in Android Virtual Device.

And, also important is to leave open the emulator. It works both in Eclipse and Android Studio.

In a window, it says snapshot does not generally work when RAM is more than ~700. So, selecting a lower configured one easily help to test Hello World and then for developing your application. Later, we can test on a high-end device.

For me, virtualization support does not work as my hardware does not support it.

-

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: http://plugins.genymotion.com/eclipse. Follow the steps indicated by Eclipse.

This emulator is fast and responsive.

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

-
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. – Eurig Jones
agreed Genymotion is the best thing I've ever used for android development – Furqan
amazingly fast emulator. – Funky Dude
This is clearly the best solution. You can also link up this article which serves as a nice introduction. – silvenon
Fastest i ever seen!! – Karioki
@Apfelsaft I have tried the solution provided in the following answer. I used it a while ago and it worked fine. //allinonescript.com/questions/20121883/… – Sufian
@Apfelsaft Refer to this answer Play Store License. In short, the Play Store is not licensed to run on the emulator. – blaffie
I wish the votes were re-set so everyone used Genymotion. By far the best emulator out there. – user2875404
Genymotion is so fast, you'll take it for a real device or devices ;) – user1299518
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. – milosmns
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 – Zain Ali
Since Android studio 2 the emulator has been improved ten fold. It has plenty of features and performs well. – blaffie
@ZainAli It's still free for personal use at the moment – Dealdiane
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 – Ton

The use of Android x86 provides better productivity than the Android emulator.

Whereas working with Android x86 4.2, it provides extremely fast debugging compared to Android emulator. It's many many times faster for configuration

It is working with the latest Android X86 4.2 (Jelly Bean) and VirtualBox.

I have found different ways to connect with the Internet and ADB.

CASE 1: Only Internet {NAT Adapter}

The easiest solution is just use a NAT adapter that will directly connect you to the Internet if the host is connected to the Internet, but you won't get the ADB connection with this setup.

Here you will get a public IP address, so you can't connect to the host computer.

The easiest solution is just use the host-only adapter.

Note: The default host-only adapter may not work due to DHCP server settings. Either create a new HostOnlyAdapter or run DHCP server for existing an adapter.

You will have to take care in this case.

If you are using LAN for the Internet connection you shall use the bridge adapter with your Ethernet card. It will give you a local IP address and the virtual machine will connect to the Internet using the host machine.

Alternatively if you are with Wi-Fi, just do the same by selecting the Wi-Fi adapter.

For other types of connection, you shall go with the same way.

To check the IP address, just press Alt+F1 (for a console Window). (To switch back to the graphics view, press Alt+F7.)

You will see the console window. Type netcfg.

It will show the IP address.

Now move on to your host, run the command prompt, and move to the adb directory.

type adb connect <your IP address>


Note: If ADB is not running or responding you can do the following.

adb kill-server



You can check devices connected to ADB:

adb devices


-

Try to reduce the screen size of the emulator while creating a new Android virtual device.

I have seen that this will launch the emulator very fast compared to the default options provided in AVD manager.

-

If you have an Intel CPU, install Intel Hardware Accelerated Execution Manager.

Then assign it as the emulator's CPU in Emulator Settings. When I did it on my Core i7 CPU, it was taking about 10 minutes. Now it is opening in 15 seconds.

-
What do you mean with "Emulator Settings" ? – gustavogbc

Try reducing screen size, and maybe you should consider using Ubuntu. I've had the same issue, and somehow my emulator on the same PC works five times faster when using Linux.

-
Screen size has nothing to do with it, and Ubuntu is, in my experience, as slow as Windows 7. – Dr Eval
I think screen size can affect speed. More pixels = more calculations and more RAM necessary. How can you be so sure that "screen size has nothing to do with it"? – Rolf

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

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.

-
I have used Genymotion, and I have to say it is comparatively fast than the default Android emulator. – Anurag
"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. – Almo

Short answer: because of the ARM -> x86 instruction translations. The Emulator works in a similar fashion to a virtual machine that is tasked with booting a full fledged OS and running your test application afterwards. The ARM -> x86 translations can be very time consuming, less for your app, but more for when the OS is booting (it's proportional to complexity and number of instructions involved).

Some suggested running the code on x86 emulators. What this means is instead of loading an ARM based OS, you load an x86 variant that will run faster on your x86 machine, as no ARM->x86 translation are necessary. Still, this is not a perfect solution:

Android applications that use NDK and come packed with native libs (*.so) compiled for ARM, will not work on x86 emulators, so such programs will fail to run. But if you get to that point and get to deal with NDK/native JNI code, you probably know enough about emulators already.

-

The emulator is actually running, but it seems like the graphical interface may be the problem.

When the Android splash screen is up and you are waiting forever it looks like the following:

The emulator is actually running because you can run the following command-line tool and see the listed processes:

adb -s emulator-5554 shell ps


That will provide you with a list of processes which are running on the device, which seems stuck.

I piped the output to a file and here is a list of all the running processes:

USER     PID   PPID  VSIZE  RSS     WCHAN    PC         NAME

root      1     0     696    500   c02ae25a 0805a406 S /init
root      2     0     0      0     c02315a2 00000000 S kthreadd
root      3     2     0      0     c021f9dc 00000000 S ksoftirqd/0
root      5     2     0      0     c022e8d7 00000000 S kworker/u:0
root      6     2     0      0     c022e085 00000000 S khelper
root      7     2     0      0     c022e8d7 00000000 S kworker/u:1
root      255   2     0      0     c02886de 00000000 S sync_supers
root      257   2     0      0     c028935e 00000000 S bdi-default
root      259   2     0      0     c022e085 00000000 S kblockd
root      267   2     0      0     c022e085 00000000 S ata_sff
root      278   2     0      0     c04f610f 00000000 S khubd
root      283   2     0      0     c022e085 00000000 S md
root      297   2     0      0     c022e085 00000000 S cfg80211
root      298   2     0      0     c022e8d7 00000000 S kworker/0:1
root      413   2     0      0     c0283057 00000000 S kswapd0
root      481   2     0      0     c02cd713 00000000 S fsnotify_mark
root      501   2     0      0     c022e085 00000000 S crypto
root      590   2     0      0     c022e085 00000000 S iscsi_eh
root      611   2     0      0     c048aa21 00000000 S mtdblock0
root      619   2     0      0     c048aa21 00000000 S mtdblock1
root      627   2     0      0     c048aa21 00000000 S mtdblock2
root      666   2     0      0     c022e8d7 00000000 S kworker/0:2
root      700   2     0      0     c022e085 00000000 S binder
root      724   2     0      0     c022e085 00000000 S deferwq
root      725   1     624    348   c02ae25a 0805a406 S /sbin/ueventd
root      932   2     0      0     c055236e 00000000 S mmcqd/0
root      939   2     0      0     c0340f30 00000000 S yaffs-bg-1
root      941   2     0      0     c0340f30 00000000 S yaffs-bg-1
root      942   2     0      0     c0340f30 00000000 S yaffs-bg-1
system    943   1     1340   400   c056a35d b76a1eb6 S /system/bin/servicemanager
root      944   1     5540   924   ffffffff b7646c11 S /system/bin/vold
root      947   1     1548   504   c05785ce b766c163 S /system/bin/debuggerd
radio     948   1     6420   1016  ffffffff b76d3c11 S /system/bin/rild
system    949   1     20088  2876  ffffffff b7655eb6 S /system/bin/surfaceflinger
drm       951   1     10480  2920  ffffffff b7585eb6 S /system/bin/drmserver
keystore  954   1     5036   1416  c056a35d b765deb6 S /system/bin/keystore
root      955   1     1324   440   c02d0083 b76b28ab S /system/bin/qemud
shell     958   1     1428   668   c03e9ad9 b767fa76 S /system/bin/sh
root      959   1     4680   304   ffffffff 08063530 S /sbin/adbd
graphics  1012  1     17980  4276  ffffffff b7652eb6 S /system/bin/bootanimation
media     4743  1     25288  6232  ffffffff b75beeb6 S /system/bin/mediaserver
root      4744  1     3944   1164  00000000 b7628976 R /system/bin/netd
root      4770  4744  0      0     c021de78 00000000 Z iptables
root      4771  959   1768   540   00000000 b766fa76 R ps


For fun I then ran the following command and killed the "Android" animation:

adb -s emulator-5554 shell kill 1012


The splash screen became blank so something is really happening.

I tried and succeeded at killing some other processes and that made me feel good but the emulator still didn't ever seem to start. Oh well. I'm running a QuadCore i7 with 8Gb of ram. Also running the haxm with the settings described in other posts in this question.

Note: I'm updating this on 09/19/2014 - I learned that this odd behavior where the emulator would attempt to start the instance but never would was all related to the file rights on the emulator files. They were set to read-only because of the way they were copied, so the emulator attempts to install and write to its "virtual disk" but it's "virtual disk" is really a file or set of files which my OS has set to read-only and so it fails. These failures cause the emulator to never start. I set the files to full access and the emulator starts up in record time.

-

Try using the Intel X86 Atom Storage Image for a relatively faster boot up than using ARM based images when emulating the device.

Another thing to be taken into the notice is that according to your system configuration, running an Android emulator with 1.21 GB RAM can be a sluggish experience, because the emulator requires up to some certain percentage of RAM which is used for emulating the device, not forgetting about the RAM used by the ADT.

Try a system image of 2.1 - 2.3.3 for at least a runnable experience. Plus not forgetting about Save to Snapshot for quicker loading. Though the first load may take time. But saving to a snapshot definitely saves up some time.

-

Simple easy solution for beginners. I have tried many ways and stopped with Genymotion in combination with Eclipse. Genymotion simply adds a virtual device to Eclipse.

Step by step:

2. Install this package included build in VirtualBox.
3. Install the plugin into Eclipse from here.
4. Start GenyMotion and create a virtual device you want use, and start it.
5. In Eclipse, go to Window -> Preferences -> GenyMobile -> GenyMotion, and set the path to GenyMotion (in my case, C:/ProgramFiles/GenyMobile/Genymotion).
6. Click on a project name in Eclipse that you want to start. Start the application using "Run as". In the list of devices, you should see the emulated device.
7. You cam emulate what you want.

In my case, this solution is the one and only fast solution. No emulators in Eclipse have never worked so fast, and every setting was very slow. Only this solution works almost in realtime. I can recommend (notebook i3, 2.6 GHz).

-

This is what has worked for me:

• Setting AVD RAM to 512 MB
• Setting SD card memory to 10 MB
• Setting a large SD card memory size is one of the biggest causes of a slow AVD.
-

I had the same problem, but I fixed it by deleting the .android folder from C:\Users\User\.

Now everytime I start Eclipse or AVD, I delete that folder. After that my AVD boots up in 20 to 30 seconds and the emulator works smoothly with a negligible lag.

OPTIONAL : If the problem still persists, try to clone the NEXUS S AVD.

-
What is AVD? Do you mean ADB? – Peter Mortensen
Android Virtual Device @PeterMortensen – PeeHaa

A new option is the Visual Studio Emulator for Android--it's fast, Hyper-V, x86, and free to download even without VS.

-
Is it only for Windows? – Robert
Yes--it uses Hyper-V, which is only on Windows. – John Kemnetz
I agree with the claim - the best emulator on the planet. I am a witness after suffering from using other emulators for quite a few years. It is so much better than others, especially when it comes to debugging. Genymotion is not bad but it requires VirtualBox that conflicts with Hyper-V. This answer needs to go to the top. – Hong
@JohnKemnetz may I add only on Windows Professional or higher. – James_Parsons

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

-
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. – MSS
@MSS I do not know the background history behind VS Emulator but I did it practically and found what I said. – Anil8753
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. – MSS
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
I am developing android app using Android Studio and deploying it similar to other ADB devices. Just give a try – Anil8753
probably MS runs emulator thru virtualization. virtualization governor - software won't show you real resources used by VM – razor

For a better experience, I would recommend the shop.genymotion.com licensed genymotion. If you want to test it out, first you can get genymotion here

-
Came here to say that... missed by only 2 hours. The emulator is not HW accelerated and is built mostly to check screen sizes and form factors. – Royi Benyossef
i don't think so for checking the all resolution we require emulator – Ajay Pandya
Require no, but the best usage of the tool - yes. – Royi Benyossef

You may try Genymotion instead of android emulator. It is faster and better than the android emulator.

-
Genymotion - genymotion.com I'm using this. This is indeed a good emulator. Installation is straight forward. – Sukitha Udugamasooriya

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

-

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.

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.
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".
-
Genymotion is not free anymore. – MaXi32

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

-

You have to use online emulator from

http://developer.samsung.com/remotetestlab/rtlDeviceList.action

-
this link page may never change. – Dhiren

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.

-
can you remove this answer please? it doesnt add anything to the question, and because the english is appalling it makes the question worse – Isaac
I had fixed my poor english , but my response is logic , i talk about my experience in native android emulator and other custom emulator – Sofien Rahmouni Virtuel
no, you mentioned an emulator that was already mentioned, no need to mention it twice. – Isaac
Or three times. – Almo

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

-

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.

And Instant run will look like this

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

-
Android Studio 2.0 is stable now. Instant run increases build speeds not emulator speed, check for more info: <android-developers.blogspot.lt/2016/04/…; – Arūnas Bedžinskas
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. android-developers.blogspot.ae – Umar
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.. – Vamsi Challa

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.

-

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.

-

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.

-
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. – MaXi32

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

-
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. – Christian
@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. – CyprUS
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). – Christian

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:

http://androidveteran.blogspot.in/2016/01/android-emulator-multi-touch.html

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

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

-
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... – Gábor
@Gábor may i know your hardware configurations ? – Chintan Soni
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. – Gábor

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.

http://www.leapdroid.com

Source code: https://github.com/leapdroid

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

-

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

-
It is free for personal use – Abdul Samad
It's not free for personal use ANYMORE. genymotion.com/pricing-and-licensing – MaXi32

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.

-

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: https://medium.com/android-news/how-visual-studio-emulator-for-android-can-improve-your-android-development-9e17a6213839#.hlh7ba6ut

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: https://blogs.msdn.microsoft.com/visualstudioalm/2014/11/12/introducing-visual-studios-emulator-for-android/

-
"I wonder why nobody has mentioned the Visual Studio Emulator as an alternative." It's suggested right here: //allinonescript.com/a/28417080/508666 – PeeHaa
My bad! I missed it somehow. Should I delete the post? :/ – T.M
I've not voted to delete because yours has a nice benchmark picture. But it's up to you and the android community whether it stays. – PeeHaa

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.

-
Nice solution. Using the physical device is nice to PCs with low memory. – Andrey Luiz
Vysor free is sooo low-resolution. You can barely read text. – Hendy Irawan
@Hendy-Irawa you have lots of options for this... speed/resolution-quality – r3dm4n

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.

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

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.

-
Use Host GPU is the key! thanks was wondering why in one machine I had a fast emu and in another I had not – Keoz
you should enable virtualization on BIOS, if you had an AMD processor then enable Vt-x – Anu Martin
Notice, this HAXM is only needed (and available) for Windows, not for Linux. – suther

We can use genymotion as emulator, as it runs on Virtual box, hence we can set a lower size of RAM that it can use. AND IT DOESN'T INCREASES.

Where else in traditional emulator, we can set our own limit of RAM to be used, but it exceeds it.

Its the solution for people who are fed up with low RAM size of system (system RAM < 8 GB)

-

Android emulator is working slow in your pc because of the configuration of your pc. Emulator is like virtual mobile it takes space from your hard disk and also takes RAM to run the emulator so increase your pc configuration and run faster on emulator.

-

You can use latest built-in emulators in android studio. Genymotion has introduced 2.9.0 version for android 7.1 as well.

See the latest updates in built-in emulators in Android studio.

-

-Install HAMX -RAM Size:1576 MB -VM Heap Size:128 MB

And Most Important Use API Level Android 6.0 x86

These Increase Almost Speed Up Your Emulator Fast.

-

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.

-

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.

-

Use genimotion as emulator... It is simple and fast.

-
yea and you have to pay for it! – Maksim Kniazev

Firstly, your RAM needs to be upgraded to atleast 8GB If you cannot upgrade your RAM, then run the application on your Android Phone, 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.

-

I am using android studio emulators.They are very fast as compared older version.Download the latest version of android studio Android Studio And Go to the Tools>Android>Avd Manager Install the Android api level which you want Android Emulator

-

There is a preview available for the new android emulator in the canary channel with quick boot functionality

-