android 模拟器 PANIC: Could not open: AVD 解决方法

最新推荐文章于 2023-06-02 20:45:33 发布

转载最新推荐文章于 2023-06-02 20:45:33 发布 · 3.3k 阅读

Android 专栏收录该内容

136 篇文章

订阅专栏

本文提供两种解决方案来解决Android模拟器启动失败的问题。一种方案是通过创建NTFS符号链接来修正路径问题；另一种方案是设置环境变量ANDROID_SDK_HOME，并在Eclipse中配置新的变量user.home，确保指向正确的.android目录。

参考文章：

http://stackoverflow.com/questions/18540607/starting-emulator-for-avd-then-panic-could-not-open

http://android.stackexchange.com/questions/51742/cannot-start-emulated-android-device-avd-device-in-windows-7

解决方法一：

This is a bug in the ADT Plugin. For a workaround until it is fixed use a NTFS symbolic link.

I have a C: drive for windows 7 and a D: drive for all my work and data. After installing windows 7 I relocate all my special folders from C:\Users\John Doe to D:\John Doe. The ADT Plugin is trying to load the emulator from C: when it and the configure files are on D: (PANIC: Could not open etc.). NTFS can get the ADT Plugin to read from D: using a NTFS symbolic link. Open a command prompt in C:\Users\John Doe (obviously use your user name), use the mklink command.

 mklink /J "C:\Users\John Doe\\.android" "D:\John Doe\\.android"

Now when the ADT plugin is trying to reference .android on C:, NTFS sends the request to D: and the emulator starts correctly.

Original Source

解决方法二：

If it is not a path issue, then:

Create a environment variable called: ANDROID_SDK_HOME and set it to C:\Users\Administrator Open Eclipse > Window > Preferences and click in Run/Debug and String Substitution Add a new variable called: user.home and set it to C:\Users\Administrator Create an AVD and run it.

Try these steps

Create a environment variable called: ANDROID_SDK_HOME and set it to C:\Users\<<Administrator>>
Open Eclipse > Window > Preferences, click in Run/Debug and String Substitution. Add a new variable called user.home and set it to C:\Users\<<Administrator>>
Create an AVD and run it.

Note The <<Administrator>> means the name of your Windows account; it is where resides the folder which contains your .android directory

An android project member says here:

As a work-around, you can define the environment variable ANDROID_SDK_HOME to point to the directory containing your .android directory. The emulator and SDK Manager will pick it up properly.

Also you should check that the AVD is created in the location D:\NN\.android\avd (check in your screenshoots, just above the list of AVD, the path in List of existin Android Virtual Devices).