Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

"Starting emulator for AVD" then Panic: could not open..."

Tags:

android

avd

panic

I'm new to android app dev. When I created a new AVD, when I click start on this AVD: I get the following:

Starting emulator for AVD 'Nexus_4_16_AVD'
PANIC: Could not open: Nexus_4_16_AVD

like image 266
jerryh91 Avatar asked Aug 30 '13 19:08

jerryh91


People also ask

Why is my AVD not working?

In case you get an error like "Intel virtualization technology (vt,vt-x) is not enabled". Go to your BIOS settings and enable Hardware Virtualization. 3) Restart Android Studio and then try to start the AVD again.

Why emulator is not opening?

If the Android Emulator does not start properly, this problem is often related to discovering that your application's minimum SDK is higher than your emulator SDK. If that's not the case, make sure you have HAXM installer on your SDK Manager.

Why is my emulator stuck?

Fix 4 – Uninstall and Reinstall AVD From Android Studio, select “Tools” > “SDK Manager” > “SDK Tools“. Uncheck “Android Emulator“. Select “Apply” to have the emulator uninstalled. Once the emulator has been removed, check the “Android Emulator” box again, then select “Apply” to reinstall it.


1 Answers

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

OR

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.

Original Source

like image 160
Umer Farooq Avatar answered Sep 20 '22 19:09

Umer Farooq