简体繁体 English

Android 4.0模拟器无法启动

[英]Android 4.0 emulator won't start

原文 2011-10-20 07:29:35 3 7 android/ emulation/ avd/ android-4.0-ice-cream-sandwich

When trying to create and start an Android 4.0 emulator I get the Android emulator skin but the OS doesn't seem to start. 在尝试创建和启动Android 4.0模拟器时，我获得了Android模拟器皮肤，但操作系统似乎没有启动。

I've installed the ARM EABI v7 package from Android SDK manager at tried to create an emulator, but got an error message about a missing userdata.img file. 我已尝试从Android SDK管理器安装ARM EABI v7软件包，尝试创建模拟器，但收到有关缺少userdata.img文件的错误消息。

I then found that the system $ANDROD_LIB$/system-images/android-14/armeabi-v7a/ library was created and copied these files into $ANDRROID_LIB$/platforms/android-14/images/ after which I could create a the emulator image. 然后我发现系统$ ANDROD_LIB $ / system-images / android-14 / armeabi-v7a / library被创建并将这些文件复制到$ ANDRROID_LIB $ / platforms / android-14 / images /之后我可以创建一个模拟器图片。

When starting this new emulator this as stated above only shows the Skin (window) but don't start the OS. 启动此新仿真器时，如上所述，仅显示外观（窗口），但不启动操作系统。 Im on a Mac, and all previously created emulators still work fine. 我在Mac上，所有以前创建的模拟器仍然可以正常工作。

7 个解决方案

A few tips: mine was also taking ages to start up (gave up after about 30mins). 一些提示：我的启动时间也很长（约30分钟后放弃）。 Then I compared the settings of my 3.1 AVD and my new 4.0 AVD. 然后我比较了我的3.1 AVD和我的新4.0 AVD的设置。 Turns out that the hardware property Abstract LCD density setting of the 4.0 AVD is set by default to 240, which means high density. 事实证明，4.0 AVD的硬件属性Abstract LCD密度设置默认设置为240，这意味着高密度。 That means a lot of pixels to draw. 这意味着要绘制很多像素。 I read here that that's one of the issues of a slow starting AVD. 我在这里读到，这是一个缓慢启动AVD的问题之一。 So I changed that property to be the same as for the 3.1, so it 160. After that, the AVD started about as fast as the 3.1 (several minutes)! 因此我将该属性更改为与3.1相同，因此它为160.之后，AVD的开始速度与3.1（几分钟）一样快！

(Also reduced the Device ram size from 512 to 256, but don't think that was the one who fixed it) （还将设备ram大小从512减少到256，但不要认为那是修复它的人）

I had the same problem, have you set the GPU acceleration in the emulator option? 我遇到了同样的问题，您是否在模拟器选项中设置了GPU加速？ I have set that in my emulator and the emulator wouldn't start... I was just seeing the frame like you said. 我已经在我的模拟器中设置了它并且模拟器无法启动...我只是看到你说的框架。 Didn't really find a solution to this, except turning off GPU acceleration. 除了关闭GPU加速之外，没有真正找到解决方案。

My emulator was stuck on, "Waiting for HOME ('android.process.acore') to be launched...". 我的模拟器被卡住了，“等待HOME（'android.process.acore'）被启动......”。 This is how I solved it. 这就是我解决它的方式。 In your ADT select Run Configurations and edit your virtual device to use host gpu by selecting the, "Use Host GPU" checkbox option in your edit device configuration window. 在ADT中选择运行配置，然后通过选择编辑设备配置窗口中的“使用主机GPU”复选框选项来编辑虚拟设备以使用主机gpu。

我以为我的Android 4.0模拟器也被冻结了，但事实证明我只需要等待大约5分钟才能启动它。

Once Check the TaskManager to check any adb/emulator is running. 检查TaskManager以检查任何adb /模拟器是否正在运行。

If you find stop the services and restart the eclipse and create Emulator. 如果你发现停止服务并重新启动eclipse并创建模拟器。

已安装的rev 15工具和想法110.291我可以选择armeabi-v76启动模拟器并在30分钟后重新启动它现在它开始了。

To fix mine, I had to: 要修理我的，我不得不：

open up the SDK manager, 打开SDK管理器，
check the box next to "Android 4.0 (API 14) >> ARM EABI v7a System Image", 选中“Android 4.0（API 14）>> ARM EABI v7a系统映像”旁边的框，
then click the "Delete" button at the bottom. 然后单击底部的“删除”按钮。
After it deleted, I restarted Eclipse. 删除后，我重新启动了Eclipse。
Then I went back in, checked the same box on the SDK manager again, 然后我回去了，再次检查SDK管理器上的相同框，
and reinstalled it. 并重新安装它。
Then restarted Eclipse again. 然后再次重启Eclipse。