CODEWITHSUNDEEP
android
yamini
yamini

Reputation: 181

android emulator error:[2011-08-02 11:14:01 - Emulator] PANIC: Could not open: C:\Users\hallo\.android/avd/myemu.ini

I am beginner android application developer. I have done lot of apps in eclipse on emulator and device also. But now it is giving error at the time of running project on emulator. It is working on device phone but on emulator it is giving following error:

[2011-08-02 11:14:00 - hello1] ------------------------------

[2011-08-02 11:14:00 - hello1] Android Launch!

[2011-08-02 11:14:00 - hello1] adb is running normally.

[2011-08-02 11:14:00 - hello1] Performing com.mahiways.Hello1.Hello1Activity activity launch

[2011-08-02 11:14:00 - hello1] Automatic Target Mode: launching new emulator with compatible AVD 'myemu'

[2011-08-02 11:14:00 - hello1] Launching a new emulator with Virtual Device 'myemu'

[2011-08-02 11:14:01 - Emulator] PANIC: Could not open: C:\Users\hallo\.android/avd/myemu.ini

How can I solve this problem?

Upvotes: 18

Views: 30211

Answers (5)

magyk
magyk

Reputation: 51

Solution is as follows:

  1. Set the environment variable: ANDROID_SDK_HOME value of your SDK directory. As I have is: variable name ANDROID_SDK_HOME value of the E:\java\androidsdk

  2. Modify the configuration file in the eclipse installation directory. Locate the following files: eclipse \ configuration.settings \ opened of org.eclipse.ui.ide.prefs, in a later supplement to change just to configure the environment variables.

    As I add is: ANDROID_SDK_Home = E\:\\java\\androidsdk (Note that the slash format)

  3. Restart eclipse, reconstruction of the AVD can be run successfully.

Upvotes: 5

Daniel S. Fowler
Daniel S. Fowler

Reputation: 2033

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.

Upvotes: 30

gtiwari333
gtiwari333

Reputation: 25156

The configuration files for your emulator might have been saved by AndroidSDK and AVD Manager some where else in your hard drive.

Do the following:

  • First search for the .android folder on you harddisk.
  • After you find that, move the .android folder to your user root directory - which may be "C:\Users\hallo\" in your case.

These type of project creation errors(with cause and solution) is described here.

Upvotes: 3

David Aleu
David Aleu

Reputation: 3942

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

It should work now.

Upvotes: 2

Amil
Amil

Reputation: 503

I was having this problem also but finally found a solution.
What you need to do is:
1. Create a new Windows system variable called ANDROID_SDK_HOME and set it to the directory of your Android SDK installation
2. In your "eclipse\configuration.settings\org.eclipse.ui.ide.prefs" file, also add a definition for ANDROID_SDK_Home

Then, all of your AVD files will be created in your "android-sdk/.android/avd" folder

Upvotes: 9

Related Questions