blocks|key|53537|text|您的(旧)+Eclipse版本中包含的仿真器非常慢。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53538|最近的模拟器比2010年的速度更快。更新您的SDK/IDE。|53539|就我个人而言，我使用真实的手机进行测试。它更快，测试也更现实。但是，如果你想在许多不同的Android版本上测试你的应用程序，并且不想买几部手机，你将不得不时不时地使用模拟器。|53540|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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.

blocks|key|2539555|text|中描述的选项-cpu-delay+<delay>可以提供帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2539556|entityMap^0|6|I|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

The option <code>-cpu-delay &lt;delay&gt;</code> described in <a href="http://developer.android.com/guide/developing/tools/emulator.html" rel="noreferrer">Emulator Startup Options</a> can help.

blocks|key|2539610|text|尝试禁用您的杀毒软件。也许它会让仿真器更快一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539611|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try to disable your antivirus. Maybe it will make emulator a little bit faster.

blocks|key|2749676|text|我注意到，如果没有连接Dalvik+Debug+Monitor+Server+(DDMS)，模拟器的启动速度会快得多。因此，如果您从虚拟设备管理器"SDK“启动仿真器，而Setup.exe没有启动，仿真器的运行速度会更快。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2749677|如果从Eclipse启动仿真器:+DDMS就在那里，所以有时候仿真器非常慢，但有时候会更快。|2749678|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|2749695|text|模拟器的启动非常慢。好消息是您只需要启动模拟器一次。如果仿真器已经在运行，并且您再次运行应用程序，则仿真器会相对快速地重新安装应用程序。当然，如果你想知道它在手机上的运行速度，最好是在真实的手机上测试它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2749696|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2539708|text|为此添加更多信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539709|我最近将我的Ubuntu安装升级到了Java+(Lucid+Lynx)，这反过来又将我的Ubuntu 10.04版本更新为：|offset|length|2539710|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)|code-block|syntax|javascript|2539711|现在，模拟器(虽然需要一段时间才能启动)似乎比以前运行得更快。|2539712|这可能值得人们升级他们的JVM。|2539713|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/List_of_Ubuntu_releases#Ubuntu_10.04_LTS_.28Lucid_Lynx.29^0|0|18|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

To add further information to this.

I have recently upgraded my Ubuntu installation to <a href="https://en.wikipedia.org/wiki/List_of_Ubuntu_releases#Ubuntu_10.04_LTS_.28Lucid_Lynx.29" rel="noreferrer">Ubuntu&nbsp;10.04</a> LTS (Lucid Lynx) which in turn updated my Java version to:

<pre><code>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)
</code></pre>

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.

blocks|key|2749763|text|您可以使用以下命令创建emulator.bat来启动仿真器。它会启动得更快。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2749764|emulator.exe+-cpu-delay+0+-no-boot-anim+@<avd+name>|code-block|syntax|javascript|2749765|或在Unix上(Mac或Linux风格)：|2749766|emulator+-cpu-delay+0+-no-boot-anim+@<avd+name>|2749767|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

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

<pre><code>emulator.exe -cpu-delay 0 -no-boot-anim @&lt;avd name&gt;
</code></pre>

Or on Unix (Mac or Linux flavors):

<pre><code>emulator -cpu-delay 0 -no-boot-anim @&lt;avd name&gt;
</code></pre>

blocks|key|54047|text|我有间歇性缓慢的模拟器(SDK+v8.0)加载时间，长达3分钟的英特尔酷睿Eclipse920+2.67+GHz+CPU运行在xubuntu10.04+VirtualBox+3.2.12+guest上，并加载了i7+(3.6.1)。我将VirtualBox客户内存从1024亿MB改为2048亿MB，从那时起，我再也没有经历过缓慢的情况(加载时间一致在33秒，VirtualBox负载一致在20%25)。Eclipse和仿真器都占用大量内存。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|54048|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/VirtualBox^0|24|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I had intermittent slow emulator (SDK v8.0) load times, up to three minutes on Intel Core i7 920 2.67&nbsp;GHz CPU running on Xubuntu 10.04 <a href="http://en.wikipedia.org/wiki/VirtualBox" rel="noreferrer">VirtualBox</a> 3.2.12 guest with Eclipse (3.6.1) loaded. I changed the VirtualBox guest memory from 1024&nbsp;MB to 2048&nbsp;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.

blocks|key|2749801|text|我注意到我的模拟器(Eclipse插件)被我的Nvidia显卡抗锯齿设置显著减慢。从图形菜单中删除2x抗锯齿，并将其更改为应用程序控制，使其更具响应性。它仍然很慢，但比以前好多了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2749802|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Eclipse_%2528software%2529|1|http://en.wikipedia.org/wiki/Nvidia^0|A|7|0|N|6|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I noticed that the my emulator (<a href="http://en.wikipedia.org/wiki/Eclipse_%28software%29" rel="noreferrer">Eclipse</a> plugin) was significantly slowed by my <a href="http://en.wikipedia.org/wiki/Nvidia" rel="noreferrer">Nvidia</a> 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.

blocks|key|2749809|text|Android模拟器版本9有一个新的“快照”功能。您可以使用save+the+state+of+the+emulator+(创建仿真器的映像)，并避免在启动仿真器时启动。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2749810|entityMap|0|LINK|mutability|MUTABLE|url|http://good-android-dev.blogspot.com/2011/02/slow-android-emulator-speed-up-it.html^0|U|U|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Android emulator release 9 has a new "snapshot" feature. You can <a href="http://good-android-dev.blogspot.com/2011/02/slow-android-emulator-speed-up-it.html" rel="noreferrer">save the state of the emulator</a> (make an image of the emulator) and avoid booting when you start the emulator.

blocks|key|2539778|text|在3.4+GHz四核6+GB内存的Windows7上，仿真器的速度非常慢！我通过模拟器下载了Launcher-Pro.apk，安装了它，并将其设置为默认启动程序。它使我的仿真速度提高了一倍！屏幕加载更加流畅，速度更快。它似乎不能在2.1或2.2中下载，只有在2.0中才能下载。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2539779|entityMap^0|1A|G|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

On a 3.4&nbsp;GHz quad core 6&nbsp;GB of RAM, Windows 7, the emulator was unusably slow!
I downloaded <code>Launcher-Pro.apk</code> 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.

blocks|key|53677|text|在开发了一段时间后，我的仿真器变得非常慢。我选择了wipe+data，它要好得多。我猜加载您部署的每个APK文件都需要时间。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|53678|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/APK_%2528file_format%2529^0|P|9|1F|3|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

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 <a href="http://en.wikipedia.org/wiki/APK_%28file_format%29" rel="noreferrer">APK</a> file you've deployed.

blocks|key|54174|text|试着缩小模拟器，它会让它更快一点，即使它不是这样，它真的感觉更快了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54175|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try scaling down the emulator, it makes it a bit faster, even if it doesn't it really feels faster.

blocks|key|54184|text|当前(2011年5月)版本的仿真器速度很慢，特别是在使用Android+3.0+(Honeycomb)时，主要是因为仿真器不支持硬件GL+--这意味着GL代码会被转换成软件(实际上是ARM软件)，然后在QEMU中以软件的形式进行仿真。这太慢了。他们正在努力解决这个问题，并部分解决了这个问题，但没有任何类型的发布质量。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|54185|看看视频，看看它的实际效果--跳到大约44分钟。|54186|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Android_version_history#v3.x_Honeycomb|1|http://en.wikipedia.org/wiki/QEMU^0|S|N|0|2T|4|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

The current (May 2011) version of the emulator is slow particularly with <a href="http://en.wikipedia.org/wiki/Android_version_history#v3.x_Honeycomb" rel="noreferrer">Android 3.0 (Honeycomb)</a> 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 <a href="http://en.wikipedia.org/wiki/QEMU" rel="noreferrer">QEMU</a>. 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 <a href="http://www.youtube.com/watch?v=Oq05KqjXTvs" rel="noreferrer">Google I/O 2011: Android Development Tools</a> to see it in action -- jump to about 44 minutes.

blocks|key|53683|text|我在Mac上也有类似的问题。我做了什么；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53684|53685|1)在模拟器上，设置-display+->+disable+screen+orientation|unordered-list-item|53686|2)在Eclipse上，模拟器启动选项->+-cpu-delay+100|53687|53688|这些在降低CPU使用率方面有一些效果(不是大约40-60%25)，而不是最终的解决方案。但是，CPU使用率不再超过100%25！|53689|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

I've similar issues on a Mac. What I did;

<ul>
<li>1) on the emulator, settings-display ->
disable screen orientation</li>
<li>2) on Eclipse, emulator startup options ->
-cpu-delay 100</li>
</ul>

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!

blocks|key|53691|text|我只是使用了默认的Android+3.1，它非常慢，但自从我意识到我的代码与Android+2.3.3兼容后，我就切换到了它。它快了大约50%25，而且模拟器看起来更像我的手机，并且有一个永久显示的键盘，所以它更容易使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53692|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|55234|text|较老的Android版本运行速度要快得多。当我使用上网本时，我使用的是Android+1.5+(API+level+3)。但是也有一些缺点--您的应用程序需要支持较旧的平台(显然)，并且ndk-gdb需要运行Android2.2+(API+level+8)或更高版本。但不管怎样，定期针对旧平台测试应用程序是个好主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|55235|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2750017|text|你需要更多的内存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750018|这就是我这么说的原因：|2750019|我在Windows上使用VirtualBox作为来宾运行Ubuntu10.10。我在虚拟机上安装了Eclipse和Android+SDK。我的物理机器有4+GB的内存，但当我第一次配置Ubuntu虚拟机时，我只给了它1+GB。模拟器大约花了15分钟启动。然后，我更改了配置，为虚拟机分配了2+GB的内存，模拟器在不到一分钟的时间内就开始运行了。|2750020|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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&nbsp;GB of memory, but when I first configured the Ubuntu virtual machine, I only gave it 1&nbsp;GB. The emulator took about 15 minutes to launch. Then, I changed my configuration to give the VM 2&nbsp;GB and the emulator was running in less than a minute.

blocks|key|53705|text|您可以在Google+I/O+2011:+Android+Development+Tools+talk上查看仿真器问题，从0:40:20开始。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|53706|仿真器运行缓慢，因为完整的Android环境在仿真硬件上运行，指令也在仿真的ARM处理器上执行。|53707|主要的瓶颈是渲染，因为它不在任何专用硬件上运行，但实际上是通过软件渲染来执行的。减小屏幕尺寸将显著提高仿真器的性能。获得更多/更快的内存不会有什么帮助。|53708|他们当时提到，他们正在开发一种接口，该接口将允许仿真器通过主机硬件传输某些指令，因此最终，您将能够利用桌面硬件的原始功能来利用仿真器的性能。|53709|entityMap|0|LINK|mutability|MUTABLE|url|http://www.youtube.com/watch?v=Oq05KqjXTvs&feature=player_embedded#!^0|4|16|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

You can review the emulator issues on the <a href="http://www.youtube.com/watch?v=Oq05KqjXTvs&amp;feature=player_embedded#!" rel="nofollow noreferrer">Google I/O 2011: Android Development Tools</a> 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.

blocks|key|2539850|text|我尝试从Eclipse+(Indigo和Android1.5，没有快照)启动模拟器，45分钟后我停止了它，因为什么都没有发生。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539851|统计数据:+Phenom+Quad+@2.6兆赫兹，4+GB+DDR2海盗船支配者@800兆赫兹。AVD位于SSD驱动器上，仿真器位于7200+RPM硬盘上。|2539852|我使用-no-boot-anim选项手动启动了模拟器，它在30秒内加载。:)|offset|length|style|CODE|2539853|在CMD中，导航到emulator.exe文件所在的文件夹，然后键入|2539854|emulator.exe+@<YourAVDFromEclipse>+-no-boot-anim|code-block|syntax|javascript|2539855|emulator.exe文件位于工具下的Android+SDK文件夹中。|2539856|在Windows中，你可以在C:\Users\<NAME>\.android\avd下找到Android虚拟设备(AVD)。|2539857|这些项目从Eclipse内部运行，目标是您引导的AVD，显示得很好:D|2539858|entityMap^0|0|0|3|D|0|9|C|0|0|0|C|0|E|S|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@$F|11|G|12|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@$F|14|G|15|H|I]]|9|@]|A|$]]|$1|L|3|M|5|N|7|16|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|17|8|@$F|18|G|19|H|I]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1A|8|@$F|1B|G|1C|H|I]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1D|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|X|$]]

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&nbsp;MHz with 4&nbsp;GB DDR2 Corsair Dominator @800&nbsp;MHz. The AVD is on an SSD drive and the emulator on a 7200&nbsp;RPM HDD.

I started the emulator manually with the <code>-no-boot-anim</code> option and it loaded in 30 seconds. :)

In CMD, navigate to folder where the <code>emulator.exe</code> file is and type

<pre><code>emulator.exe @&lt;YourAVDFromEclipse&gt; -no-boot-anim
</code></pre>

The <code>emulator.exe</code> file is located in the Android SDK folder under Tools.

In Windows, you can find the the Android Virtual Device(AVD) under <code>C:\Users\&lt;NAME&gt;\.android\avd</code>.

The projects run from inside Eclipse, targeting the AVD you booted, show up just nicely :D

blocks|key|2539860|text|在AVD+Manager中选择VD并单击编辑，将分辨率设置为小，因为您可以阅读VD上的文本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2539861|我使用800x600像素，RAM设置为512兆，它的工作方式非常出色，不占用大量的CPU时间。|2539862|entityMap^0|1|B|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

In <code>AVD Manager</code> 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&nbsp;MB, and it works like a charm without high use of CPU time.

blocks|key|55246|text|从Android+SDK工具的17版开始，模拟器可以使用图形加速和CPU提供的扩展来提高效率。前提条件以及完整的配置和用户说明位于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|55247|http://developer.android.com/guide/developing/devices/emulator.html#acceleration|offset|length|55248|要启用GPU加速，请从命令行运行仿真器，或者在AVD配置中的其他仿真器命令行选项中添加"-gpu+on“。|55249|emulator+-avd+<avd_name>+-gpu+on|code-block|syntax|javascript|55250|要使用CPU机器扩展，您必须安装驱动程序(注意，因为它可能与现有的VirtualBox或VMware驱动程序冲突)。安装完成后，无论何时使用基于x86的AVD，它都会自动使用。|55251|entityMap|0|LINK|mutability|MUTABLE|url|1|https://en.wikipedia.org/wiki/Graphics_processing_unit|2|http://en.wikipedia.org/wiki/VirtualBox|3|http://en.wikipedia.org/wiki/VMware^0|0|0|28|0|0|3|3|1|0|0|X|A|2|18|6|3|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|H|3|I|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]|$D|1F|E|1G|1|1H]]|A|$]]|$1|O|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|C]]|V|$5|R|S|T|A|$U|W]]|X|$5|R|S|T|A|$U|Y]]|Z|$5|R|S|T|A|$U|10]]]]

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: 

<a href="http://developer.android.com/guide/developing/devices/emulator.html#acceleration" rel="noreferrer">http://developer.android.com/guide/developing/devices/emulator.html#acceleration</a> 

For enabling <a href="https://en.wikipedia.org/wiki/Graphics_processing_unit" rel="noreferrer">GPU</a> aceleration, run the emulator from the command line or add "-gpu on" to the additional emulator command line options in the AVD configuration.

<pre><code>emulator -avd &lt;avd_name&gt; -gpu on
</code></pre>

For using the CPU machine extensions, you have to install the driver (caution because it can conflict with existing <a href="http://en.wikipedia.org/wiki/VirtualBox" rel="noreferrer">VirtualBox</a> or <a href="http://en.wikipedia.org/wiki/VMware" rel="noreferrer">VMware</a> drivers). Once it's installed it will be used automatically whenever you use an x86-based AVD.

blocks|key|54137|text|Android+SDK+Rev.17支持使用AMD和Intel虚拟化技术的虚拟机加速。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54138|这个特性可以大大提高仿真器的性能！|54139|有关更多详细信息，请参阅Android模拟器文档中的以下部分：Configuring+Virtual+Machine+Acceleration|offset|length|54140|不要忘记为您的操作系统安装适当的驱动程序：|54141|54142|Configuring+VM+Acceleration+on+Windows|unordered-list-item|54143|Configuring+VM+Acceleration+on+Mac|54144|Configuring+VM+Acceleration+on+Linux|54145|54146|安装驱动程序并下载Android+X86系统镜像后(如文档所述)，您应该能够使用x86镜像创建新的AVD：|54147|例如：|54148|54149|目标:英特尔凌动x86系统映像-+Level+10|54150|CPU/ABI:英特尔凌动(x86)|54151|54152|54153|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/guide/developing/devices/emulator.html#accel-vm|1|http://developer.android.com/guide/developing/devices/emulator.html#vm-windows|2|http://developer.android.com/guide/developing/devices/emulator.html#vm-mac|3|http://developer.android.com/guide/developing/devices/emulator.html#vm-linux^0|0|0|V|14|0|0|0|0|0|12|1|0|0|Y|2|0|0|10|3|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1J|8|@]|9|@$F|1K|G|1L|1|1M]]|A|$]]|$1|H|3|I|5|6|7|1N|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1P|8|@]|9|@$F|1Q|G|1R|1|1S]]|A|$]]|$1|N|3|O|5|M|7|1T|8|@]|9|@$F|1U|G|1V|1|1W]]|A|$]]|$1|P|3|Q|5|M|7|1X|8|@]|9|@$F|1Y|G|1Z|1|20]]|A|$]]|$1|R|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|22|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|23|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|24|8|@]|9|@]|A|$]]|$1|X|3|Y|5|M|7|25|8|@]|9|@]|A|$]]|$1|Z|3|10|5|M|7|26|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|28|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|29|8|@]|9|@]|A|$]]]|14|$15|$5|16|17|18|A|$19|1A]]|1B|$5|16|17|18|A|$19|1C]]|1D|$5|16|17|18|A|$19|1E]]|1F|$5|16|17|18|A|$19|1G]]]]

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: <a href="http://developer.android.com/guide/developing/devices/emulator.html#accel-vm" rel="noreferrer">Configuring Virtual Machine Acceleration</a>

Don't forget to install the appropriate driver for your operating system:

<ul>
<li><a href="http://developer.android.com/guide/developing/devices/emulator.html#vm-windows" rel="noreferrer">Configuring VM Acceleration on Windows</a></li>
<li><a href="http://developer.android.com/guide/developing/devices/emulator.html#vm-mac" rel="noreferrer">Configuring VM Acceleration on Mac</a></li>
<li><a href="http://developer.android.com/guide/developing/devices/emulator.html#vm-linux" rel="noreferrer">Configuring VM Acceleration on Linux</a></li>
</ul>

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:

<ul>
<li>Target: Intel Atom x86 System Image - API Level 10</li>
<li>CPU/ABI: Intel Atom (x86)</li>
</ul>

blocks|key|55253|text|Android+ADT+18现在包括一个(测试版)+GPU启用选项(只需从您的AVD属性启用GPU加速)。这有很大的不同，即使是ICS现在也感觉相对舒适。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|55254|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2750039|text|我注意到模拟器会在一段时间内变慢。因此，可以删除速度非常慢的仿真器，并在AVD管理器的帮助下创建一个新的仿真器。我已经试过几次了，效果很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750040|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2539866|text|在撰写本文时，最快的仿真器是Android+SDK附带的内置x86仿真器。你可以在你创建虚拟机的AVD管理器中找到它们。只需选择它们中的任何一个，然后选择CPU的类型(选择x86以获得最佳性能)。它将和你的机器一样快。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539867|适用于Android4.0和4.0.3的最新版本可以在中找到。|2539868|注意:这仅用于开发目的。要测试性能，您仍然必须使用真实的设备或在配备ARM+CPU的仿真器上进行测试。|2539869|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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 <a href="http://blog.testobject.org/2012/04/giving-your-android-emulator-boost.html" rel="nofollow">Giving your Android Emulator a Boost: Building Android ICS with Goldfish &amp; x86 KVM support on EC2 - TestObject</a>.

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.

blocks|key|2750042|text|启用快照可能不会使其在第一次运行时变得更快；不要使用较大的SD大小。在第一次运行时，将SD卡大小调整为100+MB。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750043|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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&nbsp;MB in the first run.

blocks|key|2750045|text|要进行快速测试(<1秒)，请使用buildroid，并将VirtualBox的第一个网卡设置为“仅主机网络”，然后运行|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2750046|C:\Program+Files+(x86)\Android\android-sdk\platform-tools>adb+connect+*.*.*.*:5555
connected+to+*.*.*.*:5555|code-block|syntax|javascript|2750047|(%5E)+DOS+/+bash+(v)|2750048|#+adb+connect+*.*.*.*:5555
connected+to+*.*.*.*:5555|2750049|其中*。*。*+.*是通过在buildroid主屏幕中单击buildroid应用程序而获得的buildroid+IP地址。|2750050|entityMap|0|LINK|mutability|MUTABLE|url|http://www.buildroid.org/blog/?page_id=121|1|https://www.virtualbox.org/wiki/Downloads^0|G|9|0|S|A|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|16|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|17|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]|W|$5|R|S|T|C|$U|X]]]]

For fast testing (&lt;1 second) use <a href="http://www.buildroid.org/blog/?page_id=121" rel="nofollow">buildroid</a> with <a href="https://www.virtualbox.org/wiki/Downloads" rel="nofollow">VirtualBox</a>'s first network card set to “host only network” and then run

<pre><code>C:\Program Files (x86)\Android\android-sdk\platform-tools&gt;adb connect *.*.*.*:5555
connected to *.*.*.*:5555
</code></pre>

(^) DOS / bash (v)

<pre><code># adb connect *.*.*.*:5555
connected to *.*.*.*:5555
</code></pre>

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

blocks|key|2539871|text|好吧，既然有人推荐Android+x86作为替代的测试模拟器，我也会介绍我最喜欢的。这可能不是每个人的替代方案，但对我来说是完美的！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539872|使用Bluestacks+Player。它运行的是Android+2.3.4，非常流畅和快速。有时它甚至比普通设备更快。唯一的缺点是，你只能在API+Level+10和一个屏幕尺寸上测试应用程序，但它只适用于测试它是否工作。只需运行以下命令即可将播放器与adb连接|offset|length|style|CODE|2539873|adb+connect+127.0.0.1+|code-block|syntax|javascript|2539874|编译后，它会立即安装。这是非常令人印象深刻的，考虑到我有一个相当普通的计算机硬件(双核和4+GB的RAM)。|2539875|entityMap|0|LINK|mutability|MUTABLE|url|http://bluestacks.com/^0|0|3J|3|2|H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@$D|10|E|11|1|12]]|A|$]]|$1|H|3|I|5|J|7|13|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

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 <a href="http://bluestacks.com/" rel="noreferrer">Bluestacks Player</a>. 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 <code>adb</code> by running

<pre><code>adb connect 127.0.0.1 
</code></pre>

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

blocks|key|2539877|text|我会坚持你现在安装BlueStacks，因为它的工作原理与模拟器一样，还有许多其他功能(例如，它可以访问Android+Market)。此外，您还可以以极快的性能将应用程序直接从Eclipse运行到BlueStack设备/仿真器。将应用程序从Eclipse运行到BlueStack仿真器只需要几秒钟的时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2539878|entityMap|0|LINK|mutability|MUTABLE|url|http://bluestacks.com/^0|9|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I would insist you to install <a href="http://bluestacks.com/" rel="nofollow">BlueStacks</a> 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.

blocks|key|2539880|text|通过进入windows-->preference->General-->Startup+and+shutdown，删除一些插件在启动时不需要的激活。还要确保您没有在任何视图中使用这些插件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539881|Eclipse不是一个文字处理器。最好禁用拼写检查。禁用拼写检查将减少eclipse的负担，方法是进入Windows+-->首选项-->常规-->编辑器-->文本编辑器-->拼写|2539882|当eclipse构建项目时，它将删除所有输出文件夹，并重新构建由其他编译器构建的类。我们可以禁用这些功能，因为删除输出文件夹和重建需要一段时间。转到Windows-->Preference-->Java-->Compiler-->Building|2539883|禁用对你来说不太有用的标签装饰也会帮助你获得一些性能。转到Windows-->Preference-->General-->Appearance-->Label装饰品|2539884|关闭不需要的项目，并使用工作集选项顺利地从一组项目移动到另一组项目。|2539885|如果您不需要Eclipse自动构建，也可以禁用它。转到项目-->自动构建(取消选中)|2539886|不要在编辑器中保持大量打开的选项卡。最好有20个左右的标签。定期关闭未使用的选项卡。要打开资源，我们总是可以使用ctrl%2Bshift%2BR和ctrl%2Bshift%2BT+(java资源)，而不是打开许多标签|2539887|禁用不需要的插件。完整的J2EE+eclipse版本有一个禁用/卸载插件的选项。转到帮助-->软件更新-->管理配置。右键单击任何已安装的插件即可获得禁用选项。如果此选项不可用，请转到Windows-->Preference->Capabilty启用Classic+update，然后选中classic+Update。现在，管理配置选项应在帮助菜单中可用|2539888|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

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

blocks|key|53732|text|要减少仿真器的启动时间，您需要在启动仿真器之前检查“禁用引导动画”。请参阅the+Android+documentation。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|53733|如果你不知道，你不需要在每次运行/调试你的应用时都关闭模拟器。如果在APK文件已经打开时单击run/debug，APK文件将被上传到仿真器并立即启动。Emulator只在第一次启动时花费了令人恼火的长时间。|53734|这里有一些提升安卓模拟器速度的小贴士：。|53735|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/tools/help/emulator.html^0|11|P|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

To reduce your emulator start-up time you need to check the "Disable Boot Animation" before starting the emulator. Refer to <a href="http://developer.android.com/tools/help/emulator.html" rel="noreferrer">the Android documentation</a>.

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: <a href="http://www.nuxeo.com/blog/speeding-up-the-android-emulator/" rel="noreferrer">How to speed up the Android Emulator by up to 400%</a>.

blocks|key|53737|text|我只是注意到一些我不能解释的东西，但是嘿，对我来说它是有效的！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53738|我从源码编译Android，内置的仿真器在几秒钟内启动(我的机器是双核AMD2.7+GHz)，然后马上，可能是第一次运行两个，系统就启动了。另一方面，使用Eclipse+ADT包会导致半小时的模拟器启动。不能接受。|53739|在这里工作的解决方案(我没有办法在其他机器上测试它，所以如果你愿意的话，可以测试和验证)：|offset|length|style|BOLD|53740|53741|下载并在您的机器上构建Android+SDK。这可能需要一些时间(你知道，编译整个系统是很累人的)。可以在这里找到说明：|unordered-list-item|53742|Initializing|ordered-list-item|53743|Downloading+|53744|Building+(我将命令更改为'lunch+sdk-eng‘和'make+sdk+-j4'；此外，构建技巧也很有用，特别是关于option)|53745|53746|和-jN+ccache|53747|​|53748|SDK+|53749|完成后，运行'android‘，SDK管理器应该会出现。下载工具和所需的平台包。如果找不到命令，请尝试重新运行。用于设置路径的build/envsetup.sh和'lunch+sdk-eng‘命令；它们在退出终端会话后会丢失。|53750|
|53751|运行’模拟器‘以检查其启动速度。对我来说，它比捆绑Eclipse的要快得多。|53752|53753|如果它能工作，就把Eclipse指向你刚刚编译的SDK。窗口-首选项-Android在左窗格->中选择SDK+location。它应该是带有'tools‘子目录和’platform‘子目录的目录。对我来说，如果需要的话，就是<source+base+dir>/out/host/linux-x86|CODE|53754|53755|Apply/OK，重启Eclipse。如果它没有任何抱怨，运行你的Android应用程序。在我的例子中，模拟器在几秒钟内启动，并在一分钟内完成引导。虽然还有一点延迟，但我完全可以接受。|53756|53757|此外，我同意从快照运行，并将状态保存到快照。我的建议只关心模拟器的启动时间。我仍然不知道为什么默认情况下它会这么长。无论如何，如果对您有效，请尽情享受:)|53758|entityMap|0|LINK|mutability|MUTABLE|url|http://source.android.com/source/initializing.html|1|http://source.android.com/source/downloading.html|2|http://source.android.com/source/building.html^0|0|0|0|A|0|0|1|0|C|0|1|0|B|1|1|0|8|2|1|0|0|0|0|0|0|0|0|34|10|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1V|8|@$F|1W|G|1X|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|20|8|@]|9|@$F|21|G|22|1|23]]|A|$]]|$1|Q|3|R|5|P|7|24|8|@]|9|@$F|25|G|26|1|27]]|A|$]]|$1|S|3|T|5|P|7|28|8|@]|9|@$F|29|G|2A|1|2B]]|A|$]]|$1|U|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|2D|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|2E|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2F|8|@]|9|@]|A|$]]|$1|11|3|12|5|M|7|2G|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2H|8|@]|9|@]|A|$]]|$1|15|3|16|5|M|7|2I|8|@]|9|@]|A|$]]|$1|17|3|14|5|6|7|2J|8|@]|9|@]|A|$]]|$1|18|3|19|5|M|7|2K|8|@$F|2L|G|2M|H|1A]]|9|@]|A|$]]|$1|1B|3|14|5|6|7|2N|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|M|7|2O|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]]|1I|$1J|$5|1K|1L|1M|A|$1N|1O]]|1P|$5|1K|1L|1M|A|$1N|1Q]]|1R|$5|1K|1L|1M|A|$1N|1S]]]]

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&nbsp;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):

<ul>
<li>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: 

<ol>
<li><a href="http://source.android.com/source/initializing.html" rel="nofollow">Initializing</a></li>
<li><a href="http://source.android.com/source/downloading.html" rel="nofollow">Downloading</a> </li>
<li><a href="http://source.android.com/source/building.html" rel="nofollow">Building</a> (I changed commands to 'lunch sdk-eng' and 'make sdk -j4'; besides that build tips are useful, especially concerning ccache and -jN option)</li>
</ol></li>
<li>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.</li>
<li>Run 'emulator' to check how fast it starts up. For me it's MUCH faster than the Eclipse-bundled one.</li>
<li>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 <code>&lt;source base dir&gt;/out/host/linux-x86</code></li>
<li>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.</li>
</ul>

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

blocks|key|54317|text|重要说明：sure+first请参阅the+Intel+list+about+VT以确保您的CPU支持英特尔VT。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|54318|HAXM加速了运行缓慢的Android+Emulator|54319|HAXM代表-“英特尔硬件加速执行管理器”|54320|目前它仅支持英特尔®VT+(英特尔虚拟化技术)。|54321|安卓模拟器是基于QEMU的。QEMU和主机系统上的HAXM驱动程序之间的接口设计为独立于供应商。|54322|​|54323|📷|atomic|54324|54325|为HAXM配置Android开发环境的步骤|54326|Eclipse更新Eclipse:确保您的安装和ADT插件完全up-to-date.|54327|Update了您的|ordered-list-item|54328|工具:在每次Eclipse插件更新之后，更新您的Android+SDK工具是很重要的。为此，启动Android+SDK管理器并更新所有Android+SDK组件。要利用HAXM，您必须至少使用版本17。|54329|54330|54331|54332|54333|54334|下载x86+Atom系统映像和英特尔硬件加速执行管理器驱动程序。如下图所示：|unordered-list-item|54335|54336|54337|54338|54339|54340|通过运行"IntelHaxm.exe“安装HAXM驱动程序。它将位于以下位置之一：|54341|54342|-+`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`|code-block|syntax|javascript|54343|如果安装程序失败并显示必须打开英特尔VT的消息，则需要在BIOS中启用此功能。有关如何在+中执行此操作的说明，请参阅说明。|54344|54345|54346|54347|54348|创建新的x86+AVD:按照下图操作：|54349|54350|54351|54352|54353|54354|或适用于新的SDK、|54355|54356|54357|54358|entityMap|0|LINK|mutability|MUTABLE|url|http://web.archive.org/web/20160102075218/http://ark.intel.com/Products/VirtualizationTechnology|1|http://en.wikipedia.org/wiki/QEMU|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/00ca2d244e35a6f85c2d850c6c32c67c.jpeg|imageAlt|3|https://ask.qcloudimg.com/http-save/yehe-900000/536b2e6e1dc94e22dec3d8677731a27b.png|4|https://ask.qcloudimg.com/http-save/yehe-900000/35d5ace8f9482cdd6c433301985aa7a7.png|5|http://en.wikipedia.org/wiki/BIOS|6|http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/Enabling-Intel-VT-Virtualization-Technology/ta-p/388479|7|https://ask.qcloudimg.com/http-save/yehe-900000/bae218fa7d641407527bb1b8a5ba94ae.png|8|https://ask.qcloudimg.com/http-save/yehe-900000/9bd21d5ca7636b110ecd8fba8fde989e.png|9|https://ask.qcloudimg.com/http-save/yehe-900000/96ac8cd62e6a742d8b3c7419d168e2d4.jpeg^0|0|4|A|5|I|N|0|0|0|0|4|7|E|0|0|8|4|1|0|0|0|1|2|0|0|0|0|0|0|0|0|0|1|3|0|0|0|2|C|F|G|0|0|0|0|1|4|0|0|0|0|0|0|S|4|5|18|1|6|0|0|0|1|7|0|0|0|0|0|0|0|1|8|0|0|0|0|0|0|1|9|0|0^^$0|@$1|2|3|4|5|6|7|2Z|8|@$9|30|A|31|B|C]|$9|32|A|33|B|C]]|D|@$9|34|A|35|1|36]]|E|$]]|$1|F|3|G|5|6|7|37|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|38|8|@$9|39|A|3A|B|C]|$9|3B|A|3C|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|3D|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|3E|8|@]|D|@$9|3F|A|3G|1|3H]]|E|$]]|$1|N|3|O|5|6|7|3I|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|3J|8|@]|D|@$9|3K|A|3L|1|3M]]|E|$]]|$1|S|3|O|5|6|7|3N|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|3O|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|3P|8|@]|D|@]|E|$]]|$1|X|3|Y|5|Z|7|3Q|8|@]|D|@]|E|$]]|$1|10|3|11|5|Z|7|3R|8|@]|D|@]|E|$]]|$1|12|3|-4|5|6|7|3S|8|@]|D|@]|E|$]]|$1|13|3|O|5|6|7|3T|8|@]|D|@]|E|$]]|$1|14|3|Q|5|R|7|3U|8|@]|D|@$9|3V|A|3W|1|3X]]|E|$]]|$1|15|3|O|5|6|7|3Y|8|@]|D|@]|E|$]]|$1|16|3|-4|5|6|7|3Z|8|@]|D|@]|E|$]]|$1|17|3|18|5|19|7|40|8|@$9|41|A|42|B|C]|$9|43|A|44|B|C]]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|45|8|@]|D|@]|E|$]]|$1|1B|3|O|5|6|7|46|8|@]|D|@]|E|$]]|$1|1C|3|Q|5|R|7|47|8|@]|D|@$9|48|A|49|1|4A]]|E|$]]|$1|1D|3|O|5|6|7|4B|8|@]|D|@]|E|$]]|$1|1E|3|-4|5|6|7|4C|8|@]|D|@]|E|$]]|$1|1F|3|1G|5|19|7|4D|8|@]|D|@]|E|$]]|$1|1H|3|-4|5|6|7|4E|8|@]|D|@]|E|$]]|$1|1I|3|1J|5|1K|7|4F|8|@]|D|@]|E|$1L|1M]]|$1|1N|3|1O|5|6|7|4G|8|@]|D|@$9|4H|A|4I|1|4J]|$9|4K|A|4L|1|4M]]|E|$]]|$1|1P|3|O|5|6|7|4N|8|@]|D|@]|E|$]]|$1|1Q|3|Q|5|R|7|4O|8|@]|D|@$9|4P|A|4Q|1|4R]]|E|$]]|$1|1R|3|O|5|6|7|4S|8|@]|D|@]|E|$]]|$1|1S|3|-4|5|6|7|4T|8|@]|D|@]|E|$]]|$1|1T|3|1U|5|19|7|4U|8|@]|D|@]|E|$]]|$1|1V|3|-4|5|6|7|4V|8|@]|D|@]|E|$]]|$1|1W|3|O|5|6|7|4W|8|@]|D|@]|E|$]]|$1|1X|3|Q|5|R|7|4X|8|@]|D|@$9|4Y|A|4Z|1|50]]|E|$]]|$1|1Y|3|O|5|6|7|51|8|@]|D|@]|E|$]]|$1|1Z|3|-4|5|6|7|52|8|@]|D|@]|E|$]]|$1|20|3|21|5|19|7|53|8|@]|D|@]|E|$]]|$1|22|3|-4|5|6|7|54|8|@]|D|@]|E|$]]|$1|23|3|Q|5|R|7|55|8|@]|D|@$9|56|A|57|1|58]]|E|$]]|$1|24|3|O|5|6|7|59|8|@]|D|@]|E|$]]|$1|25|3|-4|5|6|7|5A|8|@]|D|@]|E|$]]]|26|$27|$5|28|29|2A|E|$2B|2C]]|2D|$5|28|29|2A|E|$2B|2E]]|2F|$5|2G|29|2H|E|$2I|2J|2K|-4]]|2L|$5|2G|29|2H|E|$2I|2M|2K|-4]]|2N|$5|2G|29|2H|E|$2I|2O|2K|-4]]|2P|$5|28|29|2A|E|$2B|2Q]]|2R|$5|28|29|2A|E|$2B|2S]]|2T|$5|2G|29|2H|E|$2I|2U|2K|-4]]|2V|$5|2G|29|2H|E|$2I|2W|2K|-4]]|2X|$5|2G|29|2H|E|$2I|2Y|2K|-4]]]]

IMPORTANT NOTE: Please first refer to <a href="http://web.archive.org/web/20160102075218/http://ark.intel.com/Products/VirtualizationTechnology" rel="noreferrer">the Intel list about VT</a> to make sure your CPU supports Intel VT.

<h3>HAXM Speeds Up the Slow Android Emulator</h3>

HAXM stands for - "Intel Hardware Accelerated Execution Manager"

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

The Android emulator is based on <a href="http://en.wikipedia.org/wiki/QEMU" rel="noreferrer">QEMU</a>. The interface between QEMU and the HAXM driver on the host system is designed to be vendor-agnostic.

<img src="https://i.stack.imgur.com/FtslF.jpg" alt="HAXM">

<h3>Steps for Configuring Your Android Development Environment for HAXM</h3>

<ol>
<li>Update Eclipse:
Make sure your Eclipse installation and the ADT plug-in are fully up-to-date.</li>
<li>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.</li>
</ol>

<img src="https://i.stack.imgur.com/Tmobo.png" alt="Enter image description here">

<ul>
<li>Download the x86 Atom System Images and the Intel Hardware Accelerated Execution Manager Driver. Follow the image below:</li>
</ul>

<img src="https://i.stack.imgur.com/DufnA.png" alt="Enter image description here">

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

<ul>
<li><code>C:\Program
Files\Android\android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager</code></li>
<li><code>C:\Users\&lt;user&gt;\adt-bundle-windows-x86_64\sdk\extras\intel\Hardware_Accelerated_Execution_Manager</code></li>
</ul>

If the installer fails with the message that Intel VT must be turned on, you need to enable this in the <a href="http://en.wikipedia.org/wiki/BIOS" rel="noreferrer">BIOS</a>. See the description for how to do this in <a href="http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/Enabling-Intel-VT-Virtualization-Technology/ta-p/388479" rel="noreferrer" title="Enabling Intel Virtualization Technology">Enabling Intel VT (Virtualization Technology) </a>.</li>
</ul>

<img src="https://i.stack.imgur.com/Trlj7.png" alt="Install .exe or .dmg">

<ul>
<li>Create a new x86 AVD: Follow the image below:</li>
</ul>

<img src="https://i.stack.imgur.com/V7sf1.png" alt="Create AVD">

<ul>
<li>Or as for new SDK,
<img src="https://i.stack.imgur.com/2EhQV.jpg" alt="Enter image description here"></li>
</ul>

blocks|key|2539906|text|现在在ADT+21上，它为快速仿真器提供了更多选项...您应该使用512+MB的RAM，较低的CPU时间，较低的设备选择和较高的VM堆大小。为了获得更好的结果，您应该在CPU/ABI中使用Intel+Atom+...使用快照和CPU主机可能不会提高模拟器的速度，但有一些有用的用于其他目的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539907|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Now on ADT 21, it provides more options for a fast emulator... You should use 512&nbsp;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.

blocks|key|2750096|text|我昨天刚开始使用Windows+7，也面临着同样的问题。我发现的最简单的解决方案是在模拟器中使用低配置设备。我使用Nexus+One而不是Nexus+7，并在Android+Virtual+Device中为该设备选择快照。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750097|而且，同样重要的是让仿真器保持开放。它在Eclipse和Android+Studio中都可以工作。|2750098|在一个窗口中，它表示当RAM大于~700时，快照通常不工作。因此，选择一个配置较低的and很容易帮助您测试Hello+World，然后开发您的应用程序。稍后，我们可以在高端设备上进行测试。|2750099|对我来说，虚拟化支持不起作用，因为我的硬件不支持它。|2750100|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I just started yesterday on Windows&nbsp;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.

blocks|key|2539909|text|在创建新的Android虚拟设备时，请尝试减小模拟器的屏幕尺寸。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2539910|我已经看到，与AVD管理器中提供的默认选项相比，这将非常快地启动仿真器。|2539911|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Android_%2528operating_system%2529^0|5|7|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Try to reduce the screen size of the emulator while creating a new <a href="http://en.wikipedia.org/wiki/Android_%28operating_system%29" rel="nofollow">Android</a> virtual device.

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

blocks|key|54229|text|如果您有英特尔处理器，请安装Intel+Hardware+Accelerated+Execution+Manager。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|54230|然后在仿真器设置中将其指定为仿真器的CPU。当我在我的Core i7处理器上做这件事时，大约需要10分钟。现在它将在15秒后开放。|54231|entityMap|0|LINK|mutability|MUTABLE|url|http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager|1|http://en.wikipedia.org/wiki/Intel_Core#Core_i7^0|E|18|0|0|R|7|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

If you have an Intel CPU, install <a href="http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager">Intel Hardware Accelerated Execution Manager</a>.

Then assign it as the emulator's CPU in Emulator Settings. When I did it on my <a href="http://en.wikipedia.org/wiki/Intel_Core#Core_i7">Core&nbsp;i7</a> CPU, it was taking about 10 minutes. Now it is opening in 15 seconds.

blocks|key|53763|text|试着减小屏幕尺寸，也许你应该考虑使用Ubuntu。我也遇到过同样的问题，不知何故，我在同一台PC上的模拟器在使用Linux时速度提高了五倍。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|53764|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Ubuntu_%2528operating_system%2529^0|I|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Try reducing screen size, and maybe you should consider using <a href="http://en.wikipedia.org/wiki/Ubuntu_%28operating_system%29" rel="nofollow">Ubuntu</a>. I've had the same issue, and somehow my emulator on the same PC works five times faster when using Linux.

blocks|key|54360|text|仿真器很慢。对此您真的无能为力，但除了仿真器之外，还有其他选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54361|54362|ordered-list-item|54363|VirtualBox|offset|length|54364|BlueStacks|54365|YouWave|54366|Windows+Android+Emulator|54367|Jar+of+Beans|54368|Andy|54369|54370|为了让你的模拟器更快，你可以安装一个图形处理器并使用一个更轻量级的安卓版本(Android+2.3+(姜饼))。在Mac上开发会更好。为什么要使用仿真器，BTW？使用真正的手机更有意义。|54371|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/VirtualBox|1|http://www.bluestacks.com/|2|http://youwave.com/download.html|3|http://windowsandroid.en.softonic.com/download|4|http://tpthings.blogspot.in/2013/08/jar-of-beans-android-jelly-beans-411.html|5|http://www.andyroid.net/|6|https://en.wikipedia.org/wiki/Android_version_history#Android_2.3.E2.80.932.3.2_Gingerbread_.28API_level_9.29^0|0|0|0|0|A|0|0|0|A|1|0|0|7|2|0|0|O|3|0|0|C|4|0|0|4|5|0|0|12|B|6|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|C|3|-4|5|D|7|1H|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1I|8|@]|9|@$G|1J|H|1K|1|1L]]|A|$]]|$1|I|3|J|5|D|7|1M|8|@]|9|@$G|1N|H|1O|1|1P]]|A|$]]|$1|K|3|L|5|D|7|1Q|8|@]|9|@$G|1R|H|1S|1|1T]]|A|$]]|$1|M|3|N|5|D|7|1U|8|@]|9|@$G|1V|H|1W|1|1X]]|A|$]]|$1|O|3|P|5|D|7|1Y|8|@]|9|@$G|1Z|H|20|1|21]]|A|$]]|$1|Q|3|R|5|D|7|22|8|@]|9|@$G|23|H|24|1|25]]|A|$]]|$1|S|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|27|8|@]|9|@$G|28|H|29|1|2A]]|A|$]]|$1|V|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]|13|$5|Y|Z|10|A|$11|14]]|15|$5|Y|Z|10|A|$11|16]]|17|$5|Y|Z|10|A|$11|18]]|19|$5|Y|Z|10|A|$11|1A]]|1B|$5|Y|Z|10|A|$11|1C]]|1D|$5|Y|Z|10|A|$11|1E]]]]

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

<ol>
<li><a href="http://www.genymotion.com/" rel="noreferrer">Genymotion - Preferred</a></li>
<li><a href="http://en.wikipedia.org/wiki/VirtualBox" rel="noreferrer">VirtualBox</a></li>
<li><a href="http://www.bluestacks.com/" rel="noreferrer">BlueStacks</a></li>
<li><a href="http://youwave.com/download.html" rel="noreferrer">YouWave</a></li>
<li><a href="http://windowsandroid.en.softonic.com/download" rel="noreferrer">Windows Android Emulator</a></li>
<li><a href="http://tpthings.blogspot.in/2013/08/jar-of-beans-android-jelly-beans-411.html" rel="noreferrer">Jar of Beans</a></li>
<li><a href="http://www.andyroid.net/" rel="noreferrer">Andy</a></li>
</ol>

To make your emulator faster, you can host a GPU and use a lighter Android version (<a href="https://en.wikipedia.org/wiki/Android_version_history#Android_2.3.E2.80.932.3.2_Gingerbread_.28API_level_9.29" rel="noreferrer">Android 2.3</a> (Gingerbread)).
Developing on a Mac would be better. Why use an emulator, BTW? Using a real phone makes more sense.

blocks|key|53766|text|简而言之:由于ARM+->+x86指令翻译。Emulator的工作方式类似于虚拟机，它的任务是启动一个成熟的操作系统，然后运行您的测试应用程序。ARM+->+x86翻译可能非常耗时，对你的应用程序来说耗时较少，但在操作系统启动时会耗费更多时间(这与复杂性和涉及的指令数量成比例)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53767|有些人建议在x86模拟器上运行代码。这意味着不需要加载基于ARM的操作系统，而是加载一个在x86机器上运行速度更快的x86变体，因为不需要进行ARM->x86转换。不过，这并不是一个完美的解决方案：|53768|使用NDK并附带为ARM编译的本地库(*.so)的安卓应用程序将不能在x86模拟器上运行，因此此类程序将无法运行。但是如果您已经了解了这一点并开始处理NDK/原生JNI代码，那么您可能已经对仿真器有了足够的了解。|53769|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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.

blocks|key|54373|text|使用ADB实用程序，我发现了更多重要的信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54374|模拟器实际上正在运行，但似乎图形界面可能是问题所在。|54375|当Android闪屏打开时，你永远都在等待，它看起来如下所示：|54376|📷|atomic|offset|length|54377|​|54378|仿真器实际上正在运行，因为您可以运行以下命令行工具并看到列出的进程：|54379|adb+-s+emulator-5554+shell+ps+|code-block|syntax|javascript|54380|这将为您提供在设备上运行的进程列表，这似乎是卡住的。|54381|我将输出通过管道传输到一个文件，下面是所有正在运行的进程的列表：|54382|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|54383|为了好玩，我运行了下面的命令并杀死了"Android“动画：|54384|adb+-s+emulator-5554+shell+kill+1012|54385|启动画面变得空白，因此确实发生了一些事情。|54386|我尝试并成功地杀死了一些其他进程，这让我感觉很好，但仿真器似乎仍然无法启动。哦，好吧。我运行的是一个内存为8+8Gb的QuadCore+i7。使用这个问题的其他帖子中描述的设置运行haxm。|54387|备注：我在2014年9月19日更新了这篇文章-我了解到，仿真器尝试启动实例但永远不会启动的这种奇怪行为与仿真器文件上的文件权限有关。它们被设置为只读，因为它们被复制的方式，所以模拟器试图安装和写入到它的“虚拟磁盘”，但它的“虚拟磁盘”实际上是一个或一组文件，我的操作系统设置为只读，所以它失败了。这些故障会导致仿真器永远无法启动。我将文件设置为完全访问，仿真器在创纪录的时间内启动。|style|BOLD|54388|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c71a2be1c38116d0ac5fbcdf39e1682b.png|imageAlt^0|0|0|0|0|1|0|0|0|0|0|0|0|0|0|0|0|0|0|2|0^^$0|@$1|2|3|4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1L|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1M|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1N|8|@]|9|@$I|1O|J|1P|1|1Q]]|A|$]]|$1|K|3|L|5|6|7|1R|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1S|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1T|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|1U|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1V|8|@]|9|@]|A|$]]|$1|X|3|Y|5|Q|7|1W|8|@]|9|@]|A|$R|S]]|$1|Z|3|10|5|6|7|1X|8|@]|9|@]|A|$]]|$1|11|3|12|5|Q|7|1Y|8|@]|9|@]|A|$R|S]]|$1|13|3|14|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|20|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|21|8|@$I|22|J|23|19|1A]]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|1C|$1D|$5|1E|1F|1G|A|$1H|1I|1J|-4]]]]

Using the ADB utility I've discovered some more information that is important. 

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:
<img src="https://i.stack.imgur.com/Dz24r.png" alt="enter image description here">

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

<pre><code>adb -s emulator-5554 shell ps 
</code></pre>

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:

<pre><code>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
</code></pre>

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

<pre><code>adb -s emulator-5554 shell kill 1012
</code></pre>

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.

blocks|key|2539926|text|在模拟设备时，请尝试使用英特尔X86原子存储映像，以获得比使用基于ARM的映像更快的启动速度。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539927|另一件要注意的事情是，根据您的系统配置，运行具有1.21+GB+RAM的Android模拟器可能是一种缓慢的体验，因为模拟器需要高达一定百分比的RAM用于模拟设备，不要忘记ADT使用的RAM。|2539928|尝试2.1+-+2.3.3的系统映像，以获得至少可运行的体验。此外，不要忘记保存到快照，以便更快地加载。虽然第一次加载可能需要时间。但是保存到快照肯定会节省一些时间。|2539929|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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&nbsp;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.

blocks|key|2750129|text|为初学者提供简单易用的解决方案。我尝试过很多方法，但最终还是放弃了Genymotion和Eclipse的结合。Genymotion只是向Eclipse添加了一个虚拟设备。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2750130|一步一步：|2750131|Eclipse+here.|2750132|Install中的VirtualBox.|unordered-list-item|2750133|
|2750134|Install+|2750135|2750136|，转到Window+->+Preferences+->+GenyMobile+->+GenyMotion，并将路径设置为Genymotion+(在我的例子中，是Eclipse中你想要启动的项目名称上的)。使用"Run+as“启动应用程序。在设备列表中，您应该可以看到模拟的设备。|2750137|2750138|您可以模拟所需的设备。|2750139|2750140|在我的例子中，这个解决方案是唯一快速的解决方案。Eclipse中没有一个仿真器工作得如此之快，而且每个设置都非常慢。只有这种解决方案几乎是实时工作的。我可以推荐(notebook+i3，2.6千兆赫)。|2750141|entityMap|0|LINK|mutability|MUTABLE|url|http://www.genymotion.com/|1|https://cloud.genymotion.com/page/launchpad/download/^0|X|A|0|0|0|8|4|1|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|D|3|E|5|6|7|1B|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|H|3|I|5|J|7|1G|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1H|8|@]|9|@]|C|$]]|$1|M|3|N|5|J|7|1I|8|@]|9|@]|C|$]]|$1|O|3|L|5|6|7|1J|8|@]|9|@]|C|$]]|$1|P|3|Q|5|J|7|1K|8|@]|9|@]|C|$]]|$1|R|3|L|5|6|7|1L|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1M|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]|$1|V|3|W|5|6|7|1O|8|@]|9|@]|C|$]]|$1|X|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]]|Y|$Z|$5|10|11|12|C|$13|14]]|15|$5|10|11|12|C|$13|16]]]]

Simple easy solution for beginners. I have tried many ways and stopped with <a href="http://www.genymotion.com/" rel="noreferrer">Genymotion</a> in combination with Eclipse. Genymotion simply adds a virtual device to Eclipse.

Step by step:

<ol>
<li>Download Genymotion with VirtualBox included from <a href="https://cloud.genymotion.com/page/launchpad/download/" rel="noreferrer">here</a>.</li>
<li>Install this package included build in VirtualBox.</li>
<li>Install the plugin into Eclipse from <a href="https://cloud.genymotion.com/page/doc/#collapse8" rel="noreferrer">here</a>.</li>
<li>Start GenyMotion and create a virtual device you want use, and start it.</li>
<li>In Eclipse, go to Window -> Preferences -> GenyMobile -> GenyMotion, and set the path to GenyMotion (in my case, C:/ProgramFiles/GenyMobile/Genymotion).</li>
<li>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.</li>
<li>You cam emulate what you want.</li>
</ol>

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&nbsp;GHz).

blocks|key|2539931|text|这是对我有效的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539932|2539933|将AVD内存设置为512+MB|unordered-list-item|2539934|将SD卡内存设置为10+MB|2539935|设置较大的SD卡内存大小是导致AVD速度较慢的最大原因之一。|2539936|2539937|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

This is what has worked for me:

<ul>
<li>Setting AVD RAM to 512&nbsp;MB</li>
<li>Setting SD card memory to 10&nbsp;MB</li>
<li>Setting a large SD card memory size is one of the biggest causes of a slow AVD.</li>
</ul>

blocks|key|2539939|text|一个新的选择是Visual+Studio+Emulator+for+Android--它是快速、Hyper-V、x86和free+to+download+even+without+VS。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2539940|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/12/introducing-visual-studio-s-emulator-for-android.aspx|1|http://en.wikipedia.org/wiki/Hyper-V|2|http://aka.ms/vsemu^0|7|Y|0|1C|7|1|1O|W|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

A new option is the <a href="http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/12/introducing-visual-studio-s-emulator-for-android.aspx">Visual Studio Emulator for Android</a>--it's fast, <a href="http://en.wikipedia.org/wiki/Hyper-V">Hyper-V</a>, x86, and <a href="http://aka.ms/vsemu">free to download even without VS</a>.

blocks|key|2539942|text|Android模拟器非常慢。运行时需要800MB内存。如果您使用的是Windows，则可以使用Microsoft+Android+Emulator。它是一流的，提供了比Android+Studio+Emulator更多的功能。最重要的是它的速度很快(只消耗13MB+)。它附带了Visual+Studio+2015技术预览版。我正在使用它，并对它感到高兴。我下载并安装了整个VS包，我需要看看我们如何才能安装VS+Emulator。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539943|Visual+Studio+Emulator+for+Android|offset|length|2539944|编辑:试用https://www.visualstudio.com/vs/msft-android-emulator/|2539945|entityMap|0|LINK|mutability|MUTABLE|url|https://www.visualstudio.com/en-us/msft-android-emulator-vs.aspx|1|https://www.visualstudio.com/vs/msft-android-emulator/^0|0|0|Y|0|0|5|1I|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

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.

<a href="https://www.visualstudio.com/en-us/msft-android-emulator-vs.aspx" rel="noreferrer">Visual Studio Emulator for Android</a>

EDIT:
Try <a href="https://www.visualstudio.com/vs/msft-android-emulator/" rel="noreferrer">https://www.visualstudio.com/vs/msft-android-emulator/</a>

blocks|key|2539947|text|为了获得更好的体验，我推荐shop.genymotion.com许可的genymotion。如果你想测试它，首先你可以得到genymotion+here|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2539948|entityMap|0|LINK|mutability|MUTABLE|url|https://www.genymotion.com/#!/^0|1P|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

For a better experience, I would recommend the shop.genymotion.com licensed genymotion.
If you want to test it out, first you can get <a href="https://www.genymotion.com/#!/" rel="nofollow">genymotion here</a>

blocks|key|55268|text|你可以尝试Genymotion而不是android模拟器。它比android模拟器更快更好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|55269|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|2750151|text|您可以从here下载genymotion仿真器。这是快速而高效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2750152|entityMap|0|LINK|mutability|MUTABLE|url|https://www.genymotion.com/#!/download^0|4|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can download the genymotion emulator from <a href="https://www.genymotion.com/#!/download" rel="nofollow noreferrer">here</a>. This is fast and efficient.

blocks|key|54233|text|有几件事确实加快了我的速度，因为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54234|1.通过在AVD的编辑窗口中选中"Use+Host+GPU“复选框，将渲染过程委托给GPU。|offset|length|style|BOLD|54235|2.下载英特尔凌动(+x86+)镜像，或者如果您是windows/mac用户，则下载英特尔x86仿真加速器HAXM|54236|不幸的是，英特尔x86图片的问题是你没有谷歌应用程序，它们只有ARM图片。|54237|这就是Genymotion派上用场的地方|54238|54239|下载并安装VirtualBox。对于Windows用户来说，没有必要单独安装VirtualBox，因为它可以从Genymotion网站上获得，并与Genymotion模拟器捆绑在一起。|ordered-list-item|54240|去Genymotion+website注册。您将收到验证邮件，因此只需单击proceed.|54241|Download的验证链接并安装Genymotion+emulator.|54242|Start+Genymotion即可。您可能需要在Genymotion设置中配置Android+SDK位置的路径(如果您已将SDK安装在非默认位置)。由于这是第一次启动，因此没有设备。点击“添加”并下载新设备。要查看可用的设备，请在弹出对话框中写入您的凭据，然后单击"Connect".|54243|Select该设备，然后单击“Start”。|54244|54245|entityMap|0|LINK|mutability|MUTABLE|url|https://www.virtualbox.org/|1|http://www.genymotion.com/^0|0|0|1A|0|0|1L|0|0|11|0|0|K|0|0|0|2K|5|A|0|0|0|19|1|I|1|0|0|10|0|0|3Z|0|0|M|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1K|8|@$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1O|8|@$D|1P|E|1Q|F|G]]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|R|3|S|5|Q|7|1U|8|@$D|1V|E|1W|F|G]]|9|@$D|1X|E|1Y|1|1Z]]|A|$]]|$1|T|3|U|5|Q|7|20|8|@$D|21|E|22|F|G]]|9|@]|A|$]]|$1|V|3|W|5|Q|7|23|8|@$D|24|E|25|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|Q|7|26|8|@$D|27|E|28|F|G]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|29|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]]]

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

<ol>
<li>Download and install <a href="https://www.virtualbox.org/" rel="noreferrer">VirtualBox</a>. For Windows users it's not necessary to install VirtualBox separately, because it is available from the Genymotion site, bundled with the Genymotion emulator.</li>
<li>Go to <a href="http://www.genymotion.com/" rel="noreferrer">Genymotion website</a> and sign up. You'll receive a validation mail, so just click on the validation link to proceed.</li>
<li>Download and install the Genymotion emulator.</li>
<li>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".</li>
<li>Select the device and click "Start".</li>
</ol>

blocks|key|53778|text|现在不用模拟器，我们可以在Chrome，App+Runtime+for+Chrome上使用弧焊机应用程序来测试安卓应用程序|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|53779|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.chrome.com/apps/getstarted_arc^0|K|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Now instead of using emulator we can test Android apps using ARC Welder app on Chrome,
<a href="https://developer.chrome.com/apps/getstarted_arc" rel="noreferrer">App Runtime for Chrome</a>

blocks|key|2539967|text|试试Genymotion+for+Android+Studio。太快了！只需要一次安装。不再有AVD的痛苦。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2539968|entityMap|0|LINK|mutability|MUTABLE|url|https://www.genymotion.com/^0|2|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Try <a href="https://www.genymotion.com/">Genymotion</a> for Android Studio. Blazing fast! Just needs one time installation. No more AVD pain.

blocks|key|2750162|text|加快Android模拟器和应用程序测试的好方法是安装或升级您的Android+Studio到Android+Studio+2.0版本，然后转到应用程序打开设置/首选项，转到构建，执行，部署→即时运行。单击Enable+Instant+Run。在此之后，这将确保您的项目拥有正确的gradle插件，以便与Instant+Run一起工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2750163|📷|atomic|2750164|​|2750165|Instant+run将如下所示|2750166|2750167|2750168|然而，Android+Studio现在正在预览中，你可以现在就试一试。|2750169|entityMap|0|LINK|mutability|MUTABLE|url|http://tools.android.com/download/studio/builds/2-0-preview|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/592a707eb25aba7faa974e58ed4a2cae.png|imageAlt|2|https://ask.qcloudimg.com/http-save/yehe-900000/ef2e380d04ebf059be274854561e91e0.png^0|1A|I|0|0|0|1|1|0|0|0|0|1|2|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|1D|8|@]|9|@]|C|$]]|$1|K|3|E|5|F|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|L|3|H|5|6|7|1I|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1J|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]|W|$5|X|S|Y|C|$Z|10|11|-4]]|12|$5|X|S|Y|C|$Z|13|11|-4]]]]

Good way to speed up Android Emulator and app testing is Install or Upgrade your Android Studio to <a href="http://tools.android.com/download/studio/builds/2-0-preview" rel="noreferrer">Android Studio 2.0</a> 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.
<a href="https://i.stack.imgur.com/GvMpa.png" rel="noreferrer"><img src="https://i.stack.imgur.com/GvMpa.png" alt="enter image description here"></a>

And Instant run will look like this 
<a href="https://i.stack.imgur.com/eMLVC.png" rel="noreferrer"><img src="https://i.stack.imgur.com/eMLVC.png" alt="New Run &amp; Stop Actions in Android Studio for Instant Run"></a>

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

blocks|key|2539970|text|我建议你使用Android手机进行USB调试开发。与虚拟设备相比，它在测试应用程序时提供了更好的体验和更好的输出。或者你也可以使用其余答案中提到的选项，并可以使用Bluestacks+App+Player，这也是一个很好的选择，以防Android设备不可用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539971|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|54249|text|将您当前的Android+Studio更新为Android+Studio+2.0，并更新系统镜像。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|54250|Android+Studio2.0模拟器的运行速度比Android以前的模拟器快了大约3倍，并且通过ADB增强功能，您现在可以将应用程序和数据推送到模拟器上，速度比向物理设备上推送应用程序和数据快10倍。与物理设备一样，官方的安卓模拟器也包含内置的Google+Play+Services，因此您可以测试更多的API功能。最后，新的仿真器具有丰富的新功能来管理呼叫、电池、网络、GPS等。|54251|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/sdk/index.html|1|https://developers.google.com/android/?utm_campaign=android_launch_studio_040716&utm_source=anddev&utm_medium=blog^0|M|I|0|0|3G|K|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Update your current Android Studio to <a href="http://developer.android.com/sdk/index.html" rel="nofollow">Android Studio 2.0</a> 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 <a href="https://developers.google.com/android/?utm_campaign=android_launch_studio_040716&amp;utm_source=anddev&amp;utm_medium=blog" rel="nofollow">Google Play Services</a> 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.

blocks|key|54253|text|添加更多RAM并使用SSD驱动器。根据我的经验，Android+Studio最好运行在8到12+GB的RAM上，使用SSD驱动器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54254|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|53781|text|如果可以，切换到使用Ubuntu进行Android开发。我切换到用于Android开发的Ubuntu+14.04+LTS，我很高兴我采取了这一步。上面提到的所有步骤对Windows上的延迟影响很小或没有影响。Linux是解决您所面临的所有问题的正确答案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53782|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|54390|text|我们过去在低速Android+Emulator上运行项目的日子已经一去不复返了。今天，Android+Emulator使用了类固醇。你听到我说的了。没有其他仿真器能像Android仿真器一样快。你可以去我的博客了解更多细节：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54391|http://androidveteran.blogspot.in/2016/01/android-emulator-multi-touch.html|offset|length|54392|我已经详细解释了新的Android模拟器。看看这个。|54393|相信我，他们的速度和你真正的设备一样快。|54394|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|23|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]]]

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:

<a href="http://androidveteran.blogspot.in/2016/01/android-emulator-multi-touch.html" rel="nofollow">http://androidveteran.blogspot.in/2016/01/android-emulator-multi-touch.html</a>

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

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

blocks|key|2539982|text|你可以试试我们新的Android虚拟机Leapdroid，它与原来的Android模拟器完全兼容。因为它使用虚拟化技术，而不是仿真，所以它提供了相当高的原生速度。此外，我们使用了一种名为LeapGL的新OpenGL技术，它以原生速度执行OpenGL图形。与其他虚拟机相比，我们的虚拟机具有最好的性能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539983|http://www.leapdroid.com|offset|length|2539984|源代码：https://github.com/leapdroid|2539985|Leapdroid完全兼容Eclipse和Android+Studio，因为它使用相同的adb端口。|2539986|entityMap|0|LINK|mutability|MUTABLE|url|http://www.leapdroid.com/|1|https://github.com/leapdroid^0|0|0|O|0|0|4|S|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

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.

<a href="http://www.leapdroid.com" rel="noreferrer">http://www.leapdroid.com</a>

Source code:
<a href="https://github.com/leapdroid" rel="noreferrer">https://github.com/leapdroid</a>

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

blocks|key|2750176|text|Android+studio+2.02已经推出了，它有更快的模拟器，如果你想使用第三方，使用Genymotion模拟器，他们是相当快的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750177|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|54402|text|HAXM是一种为英特尔处理器快速开发仿真器的方法HAXM是内核驱动程序部分，而用户空间仿真器部分是基于QEMU的-这意味着QEMU有一个使用HAXM的分支(这个QEMU分支是非常特定于android仿真器的(而且似乎也是基于旧版本的QEMU)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|54403|但是，当我使用我的英特尔核心i3处理器和4+GigaBytes内存时，它对速度的影响并不大。所以这对我来说不是一个解决方案。|style|BOLD|54404|因为我使用的是4GBRAM，所以cpu+emulator变成了RAM食客，但为了更方便起见，我更喜欢基于支持的模拟器。由于android+studio现在引入了Instant-Run，所以在第一次发布后，应用程序的安装速度变得更快了，但我总是面临问题，似乎没有办法摆脱这一点。|54405|我也使用了Droid4x，它对我来说非常方便，但我找不到一种方法来安装不同的api版本，我使用它与kitkat，它比安卓模拟器更快，它也是支持VT的，所以我找到了另一种方法和一个很好的解决方案，那就是你可以阅读更多关于它的here，最新的我使用的是LeapDroid它真的很强大看比较here|54406|我更喜欢在4+4GB内存的PC上使用Real+device，然后使用模拟器。|54407|entityMap|0|LINK|mutability|MUTABLE|url|https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager|1|2|https://en.wikipedia.org/wiki/QEMU|3|4|5|6|https://developer.android.com/studio/run/index.html#instant-run|7|http://www.droid4x.com/|8|https://blogs.msdn.microsoft.com/visualstudioalm/2014/11/12/introducing-visual-studios-emulator-for-android/|9|http://www.leapdroid.com/|10|http://www.leapdroid.com/#comparison^0|0|4|0|O|4|1|1F|4|2|1P|4|3|28|4|4|38|4|5|0|9|7|K|B|0|28|B|6|0|1D|6|1Z|3|5|7|7|33|4|8|3G|9|9|3Y|4|A|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]|$A|1F|B|1G|1|1H]|$A|1I|B|1J|1|1K]|$A|1L|B|1M|1|1N]|$A|1O|B|1P|1|1Q]|$A|1R|B|1S|1|1T]]|C|$]]|$1|D|3|E|5|6|7|1U|8|@$A|1V|B|1W|F|G]|$A|1X|B|1Y|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1Z|8|@]|9|@$A|20|B|21|1|22]]|C|$]]|$1|J|3|K|5|6|7|23|8|@$A|24|B|25|F|G]|$A|26|B|27|F|G]]|9|@$A|28|B|29|1|2A]|$A|2B|B|2C|1|2D]|$A|2E|B|2F|1|2G]|$A|2H|B|2I|1|2J]]|C|$]]|$1|L|3|M|5|6|7|2K|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|2L|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|U]]|W|$5|Q|R|S|C|$T|X]]|Y|$5|Q|R|S|C|$T|X]]|Z|$5|Q|R|S|C|$T|X]]|10|$5|Q|R|S|C|$T|X]]|11|$5|Q|R|S|C|$T|12]]|13|$5|Q|R|S|C|$T|14]]|15|$5|Q|R|S|C|$T|16]]|17|$5|Q|R|S|C|$T|18]]|19|$5|Q|R|S|C|$T|1A]]]]

<a href="https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager" rel="nofollow">HAXM</a> is a way to make emulators fast for intel processors <a href="https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager" rel="nofollow">HAXM</a> is the kernel driver part, and the user-space emulator part is based on <a href="https://en.wikipedia.org/wiki/QEMU" rel="nofollow">QEMU</a> - which means there is a branch of <a href="https://en.wikipedia.org/wiki/QEMU" rel="nofollow">QEMU</a> which uses HAXM (This <a href="https://en.wikipedia.org/wiki/QEMU" rel="nofollow">QEMU</a> branch is very android-emulator-specific (and also seems to be based on older version of <a href="https://en.wikipedia.org/wiki/QEMU" rel="nofollow">QEMU</a>). 

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 <a href="http://www.android-x86.org/" rel="nofollow">Android*86</a> support based emulator. And as android studio now introduce <a href="https://developer.android.com/studio/run/index.html#instant-run" rel="nofollow">Instant-Run</a> 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 <a href="http://www.droid4x.com/" rel="nofollow">Droid4x</a> 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 <a href="https://www.visualstudio.com/en-us/msft-android-emulator-vs.aspx" rel="nofollow">Visual Studio Emulator</a> You can read more about it <a href="https://blogs.msdn.microsoft.com/visualstudioalm/2014/11/12/introducing-visual-studios-emulator-for-android/" rel="nofollow">here</a> , The latest i used is <a href="http://www.leapdroid.com/" rel="nofollow">LeapDroid</a> its really a powerful See the comparisons <a href="http://www.leapdroid.com/#comparison" rel="nofollow">here</a> 

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

blocks|key|2750179|text|我想知道为什么没有人提到Visual+Studio+Emulator作为替代方案。它比原生的Android+Studio+Emulator快得多。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2750180|这里有一个性能比较的链接：https://medium.com/android-news/how-visual-studio-emulator-for-android-can-improve-your-android-development-9e17a6213839#.hlh7ba6ut|2750181|​|2750182|📷|atomic|2750183|2750184|更好的是，apk文件甚至gapps+(或任何其他可闪存的zip)都可以通过拖放来安装。然而，缺点是它需要Hyper-V，这只在Windows上可用(从Windows+8开始也是如此)。其他限制(以及上面的描述)和其他详细信息可以在此处找到：https://blogs.msdn.microsoft.com/visualstudioalm/2014/11/12/introducing-visual-studios-emulator-for-android/|2750185|entityMap|0|LINK|mutability|MUTABLE|url|https://medium.com/android-news/how-visual-studio-emulator-for-android-can-improve-your-android-development-9e17a6213839#.hlh7ba6ut|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b3e0eb12580a9d8c6c4e3b5fa7f01370.jpeg|imageAlt|2|https://blogs.msdn.microsoft.com/visualstudioalm/2014/11/12/introducing-visual-studios-emulator-for-android/^0|C|M|0|D|3N|0|0|0|0|1|1|0|0|3C|30|2|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|H|3|I|5|6|7|1C|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1D|8|@]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|M|3|I|5|6|7|1H|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|P|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]|X|$5|Y|T|Z|E|$10|11|12|-4]]|13|$5|S|T|U|E|$V|14]]]]

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

Here's a link to performance comparison: <a href="https://medium.com/android-news/how-visual-studio-emulator-for-android-can-improve-your-android-development-9e17a6213839#.hlh7ba6ut" rel="noreferrer">https://medium.com/android-news/how-visual-studio-emulator-for-android-can-improve-your-android-development-9e17a6213839#.hlh7ba6ut</a>

<a href="https://i.stack.imgur.com/NVEpc.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/NVEpc.jpg" alt="enter image description here"></a>

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

blocks|key|2750187|text|我的解决方案是Vysor。我得到了两个最好的世界。我没有给我的机器充电太多，但我也可以在屏幕上看到我真正的Android设备，这样我就不必伸手去拿它，把手从键盘上移开等等。此外，总有一些功能在模拟器上效果不佳。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2750188|与其他解决方案相比，有带广告的免费版本和付费版本，不会让银行破产。|2750189|entityMap|0|LINK|mutability|MUTABLE|url|https://www.vysor.io/^0|7|5|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

My solution is <a href="https://www.vysor.io/" rel="noreferrer">Vysor</a> . 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.

blocks|key|2750191|text|使用英特尔x86模拟器加速器|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750192|首先，安装英特尔x86仿真加速器(HAXM)。可以直接从英特尔下载，也可以使用Android+SDK管理器下载。在SDK管理器中，它位于Extras下。|2750193|​|2750194|📷|atomic|offset|length|2750195|2750196|在我使用的Android+Studio版本(0.8.9)中，Android+SDK+Manager下载HAXM，但实际上并不运行安装程序(我假设这将在以后的版本中得到修复)。要运行安装程序，我必须转到C:\Program+Files+(x86)\Android\android-studio\sdk\extras\intel\Hardware_Accelerated_Execution_Manager并手动启动intelhaxm.exe。|2750197|HAXM可与英特尔设备配合使用，因此创建了采用英特尔CPU的新仿真器。|2750198|使用英特尔凌动x86创建新的AVD|2750199|这在很大程度上改善了情况，但模拟器仍然感觉有点慢。最后一步是在Android虚拟设备管理器(AVD)中选择Use+Host+GPU。|2750200|2750201|2750202|2750203|在这些变化之后，Android+Emulator在5-10秒内启动并运行，没有任何明显的延迟。请注意，这些功能依赖于硬件(CPU/GPU)，可能在某些系统上不起作用。|2750204|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/f49ee77d61cabc2d31e2129e99a8b71c.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/b219ec0d15607d2aa0636732234b12ac.png^0|0|0|0|0|1|0|0|0|0|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1B|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1C|8|@]|9|@$I|1D|J|1E|1|1F]]|A|$]]|$1|K|3|E|5|6|7|1G|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1H|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1I|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1J|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1K|8|@]|9|@]|A|$]]|$1|T|3|E|5|6|7|1L|8|@]|9|@]|A|$]]|$1|U|3|G|5|H|7|1M|8|@]|9|@$I|1N|J|1O|1|1P]]|A|$]]|$1|V|3|E|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1R|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15|16|-4]]|17|$5|11|12|13|A|$14|18|16|-4]]]]

<h2>Use the Intel x86 Emulator Accelerator</h2>

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.

<a href="https://i.stack.imgur.com/8FDM4.png" rel="noreferrer"><img src="https://i.stack.imgur.com/8FDM4.png" alt="SDK Manager Screenshot"></a>

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.

<h2>Create a new AVD using Intel Atom x86</h2>

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

<a href="https://i.stack.imgur.com/ZBkIK.png" rel="noreferrer"><img src="https://i.stack.imgur.com/ZBkIK.png" alt="AVD Create Options Screenshot"></a>

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.

blocks|key|53784|text|Android+Studio的性能在Linux中得到了极大的优化。Windows系统可能在后台运行不同的繁重程序。Linux最适合有效地使用可用的系统资源。最近我在Kali+Linux中安装了android+studio。模拟器的速度和工作室的性能比windows要好得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53785|从android+SDK下载软件开发工具的速度更快。因为包被捆绑在二进制文件中。二进制文件的大小很小。|53786|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|53788|text|我建议使用OpenGL设置。我有一个双核(四线程)+i3-2350M运行在它的内部图形处理器上，如果我使用SwiftShaders，性能会很差，但将它改为"Desktop+Native+OpenGL“(Extended+Controls+>+Settings+>+OpenGL+ES+Renderer)可以让它运行得很流畅。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|53789|如果设备不能启动，可以在设备配置中使用OpenGL+ES+API+Level设置和GPU仿真设置。|53790|我不知道为什么，但在我2011年的英特尔处理器上，它产生了巨大的不同。|53791|entityMap^0|2T|1D|0|J|J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

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" (<code>Extended Controls &gt; Settings &gt; OpenGL ES Renderer</code>) makes it run smoothly.

If the device doesn't boot, play around with the <code>OpenGL ES API Level</code> 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.

blocks|key|55304|text|首先，你需要将你的内存升级到至少8+8GB。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|55305|如果您无法升级RAM，请尝试通过数据线连接到Android手机上运行该应用程序，并将USB调试设置为ON。|55306|此外，您还可以使用其他一些仿真器，如GenyMotion或Nox。|offset|length|55307|但是，考虑到您似乎拥有的RAM数量，即使是其他仿真器也可能会很慢。|55308|entityMap|0|LINK|mutability|MUTABLE|url|https://www.genymotion.com/|1|https://downloadnox.com/^0|0|0|I|A|0|T|3|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]|$F|Z|G|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

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 <a href="https://www.genymotion.com/" rel="nofollow noreferrer">GenyMotion</a> or <a href="https://downloadnox.com/" rel="nofollow noreferrer">Nox</a>.

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

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 doesn't. 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 <a href="https://en.wikipedia.org/wiki/Eclipse_%28software%29" rel="noreferrer">Eclipse IDE</a> in <a href="https://en.wikipedia.org/wiki/Eclipse_%28software%29#Releases" rel="noreferrer">version 3.5</a> (Galileo) and <a href="https://en.wikipedia.org/wiki/Eclipse_%28software%29#Releases" rel="noreferrer">3.4</a> (Ganymede).

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在x86 Windows XP专业版计算机上安装了2.67 GHz赛扬处理器和1.21 GB内存。我的理解是，在这样的机器上，安卓模拟器应该启动得相当快，但对我来说，情况并非如此。我已经按照所有的说明设置了集成开发环境、软件开发工具包、JDK等等，并在快速启动模拟器方面取得了一些成功，但这是非常罕见的。如果可能的话，...

问为什么Android模拟器这么慢？我们如何提高Android模拟器的速度？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么Android模拟器这么慢？我们如何提高Android模拟器的速度？EN