Android 4.0 模拟器无法启动

发布于 2024-12-10 22:50:49 字数 364 浏览 0 评论 0原文

当尝试创建并启动 Android 4.0 模拟器时,我获得了 Android 模拟器皮肤,但操作系统似乎无法启动。

我已从 Android SDK 管理器安装了 ARM EABI v7 软件包,尝试创建模拟器,但收到有关缺少 userdata.img 文件的错误消息。

然后我发现系统 $ANDROD_LIB$/system-images/android-14/armeabi-v7a/ 库已创建并将这些文件复制到 $ANDRROID_LIB$/platforms/android-14/images/ 之后我可以创建一个模拟器图像。

当启动这个新的模拟器时,如上所述,仅显示皮肤(窗口),但不启动操作系统。我使用的是 Mac,所有以前创建的模拟器仍然可以正常工作。

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.

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.

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.

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.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(7

追我者格杀勿论 2024-12-17 22:50:49

一些提示:我的也需要很长时间才能启动(大约 30 分钟后就放弃了)。然后我比较了 3.1 AVD 和新的 4.0 AVD 的设置。事实证明,4.0 AVD 的硬件属性抽象 LCD 密度设置默认设置为 240,这意味着高密度。这意味着需要绘制大量像素。我在此处读到,这是 AVD 启动缓慢的问题之一。所以我将该属性更改为与 3.1 相同,因此为 160。之后,AVD 启动速度与 3.1 一样快(几分钟)!

(还将设备内存大小从 512 减少到 256,但不要认为这是修复它的人)

A few tips: mine was also taking ages to start up (gave up after about 30mins). Then I compared the settings of my 3.1 AVD and my new 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. That means a lot of pixels to draw. I read here that that's one of the issues of a slow starting 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)!

(Also reduced the Device ram size from 512 to 256, but don't think that was the one who fixed it)

无畏 2024-12-17 22:50:49

我也遇到了同样的问题,请问你在模拟器选项中设置了GPU加速吗?我已经在我的模拟器中设置了它,但模拟器无法启动...我只是看到了像你说的那样的框架。除了关闭 GPU 加速之外,没有真正找到解决方案。

I had the same problem, have you set the GPU acceleration in the emulator option? 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.

咿呀咿呀哟 2024-12-17 22:50:49

我的模拟器卡在“等待 HOME('android.process.acore')启动...”。我就是这样解决的。在 ADT 中,选择“运行配置”并通过在编辑设备配置窗口中选择“使用主机 GPU”复选框选项来编辑虚拟设备以使用主机 GPU。

My emulator was stuck on, "Waiting for HOME ('android.process.acore') to be launched...". 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.

哆啦不做梦 2024-12-17 22:50:49

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

I thought my Android 4.0 emulator was frozen too, but it turned out I just had to wait about 5 minutes for it to start up.

岁月无声 2024-12-17 22:50:49

安装了 rev 15 工具并使用 idea 110.291 我可以选择armeabi-v76启动模拟器并在30分钟后重新启动它,现在它启动了。

Installed rev 15 tools and with idea 110.291 I could choose armeabi-v76 start the emulator and restart it after 30 minutes and now it started.

溺ぐ爱和你が 2024-12-17 22:50:49

检查任务管理器以检查是否有任何 adb/模拟器正在运行。

如果发现停止服务并重新启动 eclipse 并创建模拟器。

Once Check the TaskManager to check any adb/emulator is running.

If you find stop the services and restart the eclipse and create Emulator.

人间不值得 2024-12-17 22:50:49

为了修复我的问题,我必须:

  • 打开 SDK 管理器,
  • 选中“Android 4.0 (API 14) >> ARM EABI v7a System Image”旁边的框,
  • 然后单击底部的“删除”按钮。
  • 删除后,我重新启动了Eclipse。
  • 然后我返回,再次选中 SDK 管理器上的相同框,
  • 然后重新安装。
  • 然后再次重新启动Eclipse。

现在它正在发挥作用。

To fix mine, I had to:

  • open up the SDK manager,
  • check the box next to "Android 4.0 (API 14) >> ARM EABI v7a System Image",
  • then click the "Delete" button at the bottom.
  • After it deleted, I restarted Eclipse.
  • Then I went back in, checked the same box on the SDK manager again,
  • and reinstalled it.
  • Then restarted Eclipse again.

Now it is working.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文