blocks|key|4701213|text|也许亚行已经破产了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4701214|如果你正在使用Windows开发Android，那么在\android-sdk\platform-tools\目录(注意:这是Android+SDK安装的子目录)中打开一个DOS会话。|offset|length|style|CODE|4701215|在DOS窗口中，键入：|4701216|adb+kill-server|code-block|syntax|javascript|4701217|这将扼杀当前的Android+Debug+Bridge+(ADB)。然后，通过键入以下命令重新启动：|4701218|adb+start-server|4701219|要验证您的Android4.4+KitKat仿真器是否正在运行，请键入以下内容：|4701220|adb+devices|4701221|如果仍然不起作用，请重复上述步骤。否则，重新启动IDE+(Eclipse、Android+Studio等)，然后重试。|4701222|entityMap^0|0|R|S|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|19|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

Maybe ADB is kaput!

If you're using Windows to develop Android, then open a DOS session at <code>\android-sdk\platform-tools\</code> directory (Note: This is a sub-directory of the Android SDK installation).

At the DOS window, type:

<pre><code>adb kill-server
</code></pre>

This would kill the current Android Debug Bridge (ADB). Then, start it again by typing:

<pre><code>adb start-server
</code></pre>

To verify if your Android 4.4 KitKat emulator is running, type:

<pre><code>adb devices
</code></pre>

If it still doesn't work, repeat the above steps. Else, restart your IDE (Eclipse, Android Studio, etc) and try again.

blocks|key|195482|text|我也遇到了同样的问题，帮助我重启电脑并启动模拟器时只打开了几个程序(Eclipse、Chrome等等)。我的开发电脑是一台运行Ubuntu+12.04的集成显卡的4+GB笔记本电脑。不费吹灰之力，KitKat模拟器就可以工作了。非常慢，正如预期的那样:(，但工作正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195483|考虑到仿真器需要大量内存，也许当您尝试运行它们时，您的开发机器资源不足？|195484|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 had the same problem, what helped was reboot my computer and start the emulator with only a few programs open (Eclipse, Chrome and nothing more). My development computer is a 4 GB notebook with integrated graphics running Ubuntu 12.04. Nothing fancy, and the KitKat emulator works. Very slowly, as expected :(, but works.

Take into account that emulators are memory hungry, perhaps your development machine is low on resources when you try to run them?

blocks|key|4701335|text|使用非常少量的内存(例如200mb)启动模拟器的第一次运行可能会有所帮助|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4701336|在我的机器上，700MB的模拟器拒绝启动(我等了30分钟，然后把它关掉了)，它只显示了一个空白屏幕-甚至连Android的消息都没有。|4701337|当我将内存减少到128MB时，模拟器在正常时间内启动(在我的m/c上大约50秒)，但RAM不足，无法加载后台应用程序。我把它改成了256MB，一切都变得生机勃勃。现在我可以改变内存高达768MB，它现在加载在相同的时间范围内。|4701338|看起来第一次运行需要少量的内存，但一旦成功，你可以毫无问题地增加内存(在Windows上高达768MB+)。|4701339|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|$]]

It may help to start the first run of the emulator with a very small amount of memory (say 200mb)

On my machine the emulator refused to start (I waited 30 minutes and then killed it) with 700MB It just showed a blank screen - not even the Android message. 

When I reduced the memory to 128MB the emulator fired up in the normal time (about 50 seconds on my m/c) but had insufficient RAM to load the background apps. I changed it to 256 MB and everything burst into life. Now I can change the memory up to 768MB it now loads fine in the same timeframe. 

Seems like the first run needs to be with a small(er) amount of memory but once that has succeeded you can increase them memory (up to 768MB on Windows) without a problem.

blocks|key|4701387|text|目前SDK最大的问题是没有发布x86模拟器图像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4701388|然而，我确实得到了一个在Windows下工作的KitKat+x86仿真器，方法是将x86+JB+AVD和ARM+KitKat+AVD中的in组合在一起，构建aosp_+x86+-eng，并将为x86预先构建的QEMU内核从KitKat+AOSP复制到我的Windows主机上。在Windows扩展上运行的x86+KitKat镜像非常快，与在实际硬件上运行一样快甚至更快，特别是在启用了“使用主机GPU”的情况下。|4701389|如果你不是在构建Android本身，这可能对你没有帮助。但是如果你正在构建AOSP+(或者你可以在网上找到一个预先构建的x86+KitKat+Android镜像和QEMU内核)，我可以发布更多关于如何让它在Windows中工作的详细信息。|4701390|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 biggest problem with the SDK right now is that there is no x86 emulator image posted.

However, I did get a KitKat x86 emulator working in Windows by hacking together INIs from an x86 JB AVD and an ARM KitKat AVD, as well as building aosp_x86-eng and copying over the prebuilt QEMU kernel for x86 from the KitKat AOSP into my Windows host. An x86 KitKat image running in Windows with the HAXM extensions is very fast, as fast or faster than running on actual hardware, particularly with "Use host GPU" enabled.

If you're not building Android itself, this probably doesn't help you. But if you ARE building AOSP (or you can find a prebuilt x86 KitKat Android image and QEMU kernel online), I can post additional details on how to get it working in Windows.

blocks|key|195618|text|这可能已经被回答了，我有一个问题，它得到了solved...please请看这篇文章，我相信你会找到正确的：Setting+Up+Android+4.4+kitkat+emulator|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|195619|如果有效的话请告诉我。|195620|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/20034172/setting-up-android-4-4-kitkat-emulator^0|1I|12|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]]]]

This might have been answered ...but I had an issue and it got solved...please see this post and I am sure you will hit it correct:
<a href="https://stackoverflow.com/questions/20034172/setting-up-android-4-4-kitkat-emulator">Setting Up Android 4.4 kitkat emulator</a>

Let me know if it works...

blocks|key|195640|text|我也有同样的问题...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195641|我使用x86模拟器的解决方案是用最新版本更新HAXM并重启我的计算机。|195642|http://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager|offset|length|195643|我希望它能帮助和解决你们中的许多人的问题。|195644|问候|195645|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|2L|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@$F|V|G|W|1|X]]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|E]]]]

I had the same problem with ...

The solution that worked for me with x86 emulator was to update HAXM with the last version and to restart my computer.

<a href="http://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager" rel="nofollow">http://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager</a>

I hope it will help and solve the problem for many of you.

Regards

blocks|key|195675|text|我也有同样的问题。将英特尔HAXM加速器从1.0.1更新到1.0.8+(当前版本)可以帮我解决问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195676|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 had the same issue. Updating Intel HAXM Accelerator from 1.0.1 to 1.0.8 (current release) did the trick for me.

blocks|key|195696|text|除非我启用了“使用主机GPU”，否则我的地图会在曲面上显示为sigabort。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195697|编辑:这似乎与极端分辨率有关。尝试使用较低的分辨率...如果您确实使用了1080x1920这样的res+-+enabling+Host+GPU对我来说是有效的|195698|检查adb+logcat输出从模拟器在启动时，如果您的类似，它可能会工作。|195699|请在下面找到日志...|195700|I/Vold++++(+++46):+Vold+2.1+(the+revenge)+firing+up
I/Netd++++(+++48):+Netd+1.0+starting
D/Vold++++(+++46):+Volume+sdcard+state+changing+-1+(Initializing)+->+0+(No-Media)
W/InterfaceController(+++48):+Warning+(dlopen+failed:+library+"/system/lib/libnetcmdiface.so"+not+found)+while+opening+the+net+interface+command+library
I/SurfaceFlinger(+++51):+SurfaceFlinger+is+starting
I/SurfaceFlinger(+++51):+SurfaceFlinger's+main+thread+ready+to+run.+Initializing+graphics+H/W...
D/libEGL++(+++51):+Emulator+without+GPU+support+detected.+Fallback+to+software+renderer.
D/libEGL++(+++51):+loaded+/system/lib/egl/libGLES_android.so
D/gralloc_goldfish(+++51):+Emulator+without+GPU+emulation+detected.
E/SurfaceFlinger(+++51):+hwcomposer+module+not+found
E/SurfaceFlinger(+++51):+ERROR:+failed+to+open+framebuffer+(No+such+file+or+directory),+aborting
F/libc++++(+++51):+Fatal+signal+6+(SIGABRT)+at+0x00000033+(code=-6),+thread+51+(surfaceflinger)
I/DEBUG+++(+++49):+***+***+***+***+***+***+***+***+***+***+***+***+***+***+***+***
I/DEBUG+++(+++49):+Build+fingerprint:+'generic/sdk/generic:4.4.2/KK/986172:eng/test-keys'
I/DEBUG+++(+++49):+Revision:+'0'
I/DEBUG+++(+++49):+pid:+51,+tid:+51,+name:+surfaceflinger++>>>+/system/bin/surfaceflinger+<<<
I/DEBUG+++(+++49):+signal+6+(SIGABRT),+code+-6+(SI_TKILL),+fault+addr+--------
I/DEBUG+++(+++49):+++++r0+00000000++r1+00000033++r2+00000006++r3+00000000
I/DEBUG+++(+++49):+++++r4+00000006++r5+00000002++r6+00000033++r7+0000010c
I/DEBUG+++(+++49):+++++r8+b6fd084d++r9+b7f1552c++sl+00000000++fp+bef71b9c
I/DEBUG+++(+++49):+++++ip+fffffffe++sp+bef719e8++lr+b6f34ead++pc+b6f43e20++cpsr+00000010
I/DEBUG+++(+++49):+++++d0++0036f09323cb6394++d1++0000000000000000
I/DEBUG+++(+++49):+++++d2++0000000000000000++d3++0000000000000000
I/DEBUG+++(+++49):+++++d4++0000000000000000++d5++41c1e5b1ca000000
I/DEBUG+++(+++49):+++++d6++3f50624dd2f1a9fc++d7++414b7849ee147ae1
I/DEBUG+++(+++49):+++++d8++0000000000000000++d9++0000000000000000
I/DEBUG+++(+++49):+++++d10+0000000000000000++d11+0000000000000000
I/DEBUG+++(+++49):+++++d12+0000000000000000++d13+0000000000000000
I/DEBUG+++(+++49):+++++d14+0000000000000000++d15+0000000000000000
I/DEBUG+++(+++49):+++++scr+00000010
I/DEBUG+++(+++49):+|code-block|syntax|javascript|195701|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Mine gets sigabort on surface flinger unless I enable "Use Host GPU".

EDIT:
Seems this is related to extreme resolutions.
Try using lower resolution... if You do use res like 1080x1920 - enabling Host GPU works for me

Check adb logcat output from emulator while booting, if yours is similar it might work.

Please find log below... 

<pre><code>I/Vold ( 46): Vold 2.1 (the revenge) firing up
I/Netd ( 48): Netd 1.0 starting
D/Vold ( 46): Volume sdcard state changing -1 (Initializing) -&gt; 0 (No-Media)
W/InterfaceController( 48): Warning (dlopen failed: library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
I/SurfaceFlinger( 51): SurfaceFlinger is starting
I/SurfaceFlinger( 51): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 51): Emulator without GPU support detected. Fallback to software renderer.
D/libEGL ( 51): loaded /system/lib/egl/libGLES_android.so
D/gralloc_goldfish( 51): Emulator without GPU emulation detected.
E/SurfaceFlinger( 51): hwcomposer module not found
E/SurfaceFlinger( 51): ERROR: failed to open framebuffer (No such file or directory), aborting
F/libc ( 51): Fatal signal 6 (SIGABRT) at 0x00000033 (code=-6), thread 51 (surfaceflinger)
I/DEBUG ( 49): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 49): Build fingerprint: 'generic/sdk/generic:4.4.2/KK/986172:eng/test-keys'
I/DEBUG ( 49): Revision: '0'
I/DEBUG ( 49): pid: 51, tid: 51, name: surfaceflinger &gt;&gt;&gt; /system/bin/surfaceflinger &lt;&lt;&lt;
I/DEBUG ( 49): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 49): r0 00000000 r1 00000033 r2 00000006 r3 00000000
I/DEBUG ( 49): r4 00000006 r5 00000002 r6 00000033 r7 0000010c
I/DEBUG ( 49): r8 b6fd084d r9 b7f1552c sl 00000000 fp bef71b9c
I/DEBUG ( 49): ip fffffffe sp bef719e8 lr b6f34ead pc b6f43e20 cpsr 00000010
I/DEBUG ( 49): d0 0036f09323cb6394 d1 0000000000000000
I/DEBUG ( 49): d2 0000000000000000 d3 0000000000000000
I/DEBUG ( 49): d4 0000000000000000 d5 41c1e5b1ca000000
I/DEBUG ( 49): d6 3f50624dd2f1a9fc d7 414b7849ee147ae1
I/DEBUG ( 49): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 49): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 49): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 49): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 49): scr 00000010
I/DEBUG ( 49): 
</code></pre>

blocks|key|195725|text|我在安装Windows+Server2012+R2时也遇到过类似的问题。根本原因是缺少显卡驱动程序(微软的普通驱动程序还不够)。我正在使用一个拼凑起来的frankenbox，我发现遵循这里的说明来找到合适的驱动程序是很有用的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195726|http://support.amd.com/en-us/kb-articles/Pages/HowtoidentifythemodelofanATIgraphicscard.aspx#DID|offset|length|195727|一旦我有了正确的驱动程序，模拟器就可以正常启动了。|195728|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2O|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

I had similar issues on a Windows Server 2012 R2 installation. The root cause was a missing video driver (the vanilla Microsoft one wasn't enough). I was working with a cobbled-together frankenbox and found it useful to follow the instructions on finding the right driver here: 

<a href="http://support.amd.com/en-us/kb-articles/Pages/HowtoidentifythemodelofanATIgraphicscard.aspx#DID" rel="nofollow">http://support.amd.com/en-us/kb-articles/Pages/HowtoidentifythemodelofanATIgraphicscard.aspx#DID</a>

Once I had the right drivers the emulator started up just fine...

blocks|key|195770|text|首先，转到IDE的SDK管理器插件，并选择要为其创建Android虚拟设备的API级别。并确保安装了API的SDK平台。如果SDK显示未安装，请先下载它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195771|下载完成后自动安装。重新启动IDE。启动AVD插件，然后为您下载的AVD选择API。|195772|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|$]]

Firstly go to SDK manager plugin of Your IDE and choose the API level for which you are going to create Android Virtual Device. And make sure that API's SDK Platform is installed. If SDK showing Not installed , then firstly download it.

After automatic Installation on Downloading completion. Restart your IDE . Start your AVD plugin and then select the API for your AVD that you download.

blocks|key|4701686|text|有了同样的问题，我配置AVD使用516MB的RAM，它加载正常。希望这对你或其他人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4701687|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|$]]

Having had the same problem, I configured AVD to use 516MB of RAM and it loaded ok. Hope this helps you or someone else.

blocks|key|195884|text|在我的例子中，解决方案是切换到不同的系统映像。我使用的是Atom+x86_64+one，一旦我切换到Atom+x86，这个模拟器就可以完美地工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195885|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|$]]

In my case, the solution was to switch to a different system image. I was using the Atom x86_64 one, and as soon as I switched to Atom x86, the emulator worked perfectly.

blocks|key|4701777|text|我认为英特尔x86(Kitkat)的系统映像中存在错误。因为只有在使用-partition-size和-memory选项的情况下，才会使用超过256MB的存储空间和内存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4701778|所以我更改了系统镜像，有两个系统镜像，一个是系统镜像，另一个是x86+API(x86系统镜像)。对我来说，这不会发生在Google+API图像上。|4701779|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 think there is a bug in system image of Intel x86(Kitkat).
Because it happens only with -partition-size and -memory option to use more than 256MB stroage and memory.

So I've change the system image, there is two system images for kitkat,
one is Intel x86 Atom system image and the other is Google APIs(x86 system image). For me it does not happen with Google APIs image.

blocks|key|4701806|text|使用命令行一次，然后它也可以在Studio中正常工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4701807|emulator+-avd+ExampleVDName+-debug-all+-noaudio+-nocache+-wipe-data+-dns-server+8.8.8.8|offset|length|style|CODE|4701808|在使用它之前，不要忘记导航到tools目录。你需要知道你的SDK在哪里。在我的例子中，我必须首先导航到这个目录，然后使用上面的命令。|4701809|cd+C:\AndroidSDK\tools|4701810|附言:别忘了使用你自己的虚拟设备的名字，而不是ExampleVHDName。|4701811|entityMap^0|0|0|2F|0|0|0|M|0|N|E|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|O|$]]

Use command line once, and then it will work normally from the Studio as well:

<code>emulator -avd ExampleVDName -debug-all -noaudio -nocache -wipe-data -dns-server 8.8.8.8</code>

Before using this, don't forget to navigate to the tools directory. You need to know where your SDK is located. In my case, I had to navigate to this directory first, and then use the command above.

<code>cd C:\AndroidSDK\tools</code>

P.s.: don't forget to use the name of your own Virtual Device, instead of <code>ExampleVHDName</code>.

I am creating an emulator for Android 4.4 KitKat, but the emulator takes very long and isn't starting.
I tried many devices like Nexus4, Galaxy Nexus, Nexus S etc. but none of that worked.
Just a black screen with the android logo for long time.
Any suggestions?

Emulator for Android 4.4 KitKat is not starting

Android Studio

Windows Server

Android

Windows

Eclipse

Ubuntu

QEMU

我正在为Android4.4 KitKat创建一个模拟器，但是模拟器需要很长时间，并且不能启动。我试过很多设备，比如Nexus4、Galaxy Nexus、Nexus等等，但都不起作用。只有一块黑屏，上面有安卓的标志。有什么建议吗？

问安卓4.4 KitKat仿真器未启动
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安卓4.4 KitKat仿真器未启动EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安卓4.4 KitKat仿真器未启动
EN