IssueTracker

I've raised a similar issue: http://code.google.com/p/android/issues/detail?id=40153

Why does/can it not pick up the previously set Eclipse name if present, as per the non-Android import of a project? This is what I expect to happen; indeed it is what used to happen, and still does for libraries. In particular under certain working configurations, e.g. source control branches, it is necessary to have a naming differentiator.

At the very least the manifest may have an application name/label, which would be better than the activity name.

If you are importing an Eclipse project (which has a .classpath), just use the generic Eclipse project import mechanism; that's still there (Import > General > Existing Projects Into Workspace).

We added Import > Android > Existing Android Code Into Workspace because a lot of people had non-Eclipse projects to import, which was not well supported; you had to "Create New" and then use a checkbox to select "existing code" etc, and the location of the project and the location of the existing sources was ambiguous.

We made the Existing Android Code import option *also* work for Eclipse projects, such that it would be a single obvious way to pull in source code. But this is new code, not the general Eclipse builtin import code, which is why it doesn't pick up the project name in the way it used to. (The related code which handled adding new project from source did act in the same quirky way the code does now, picking a project name from the manifest).

However, making it look up the project name from the .project file as a better default, if present, should be doable so I'll try to add that as well.

Ah, thanks for the explanation. I hadn't realised that the generic Eclipse import was appropriate for Android projects, but on testing it I see that it resolves the problems in my linked issue.

Note that said issue is not wholly redundant; it also reports that the Android-specific import process changes the compatibility level, which I expect is for similar reasons. The Eclipse import does not do this, so I personally no longer have a problem; I just didn't expect different behaviours.

I tweaked the wizard a bit such that there's an edit column and the default names should pick up old Eclipse names: https://android-review.googlesource.com/46770

I have compiled the new ADT and have some feedback. My "Project to Import" column has the names I would like to set on my projects; the New Project Name column shows NativeActivity for all my projects (they are all NativeActivities).

I started to change the names one by one and noticed that the "New Project Name" column is not clickable. I can't do like in a spreadsheet, change the name of a project and press Enter to move to the next row. Would it be possible to fix this. Is there a faster way to copy the "Project to Import" column to "New Project Name". And finally, if there is a jni folder in the project, it would be awesome to add C/C++ nature to the project during the import process.

Thanks!

Thank you for submitting this issue. It was last modified before Android Studio 1.0 Launched in 2014. We have made a large number of improvements in Android Studio since 2014 and hope this issue is already resolved. In order to correctly prioritize issues in our upcoming release, we are closing this bug. If you continue to experience your issue on the latest stable version of Android Studio, please submit a new bug report. We apologize for any inconvenience this may cause you.

I have the same problem:

PANIC: Could not open AVD config file: C:\Users\Владелец\.android\avd\XOR.avd/config.ini

I thought it happens because I've Cyrillic user name (damn pre-installed account that I can't change to Latin), but it seems the reason is different since other users have the same issue.

I am also having this issue. Below is the full Console screen from eclipse.

[2011-08-14 12:38:29 - HelloAndroid] ------------------------------
[2011-08-14 12:38:29 - HelloAndroid] Android Launch!
[2011-08-14 12:38:29 - HelloAndroid] adb is running normally.
[2011-08-14 12:38:29 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-08-14 12:38:29 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'myAVD'
[2011-08-14 12:38:29 - HelloAndroid] Launching a new emulator with Virtual Device 'myAVD'
[2011-08-14 12:38:30 - Emulator] PANIC: Could not open:  C:\Users\Joe Trovato\Unused Folders\.android/avd/myAVD.ini

Everything is installed on the same drive, and all of the paths are correct. Some help would be awesome. thanks.

I found a solution for this problem. I tested with Windows Seven x64.
Open cmd.exe and digit:
rmdir /Q X:\.android
cd %USERPROFILE%
mkdir /J X:\.android .android

where X is the drive that contains .android folder.

Sorry for my English.

I have the same problem:

cmd.exe

emulator -avd d1.avd

PANIC: Could not open: C:\Documents and Settings\╩ышхэЄ\.android/avd/d1.avd.ini

I thought it happens because I've Cyrillic user name (damn pre-installed account that I can't change to Latin).

c:\PROGRA~2\Android\android-sdk

 look the way i fixed it in eclipse was to change the command line for the sdk to PROGRA~2 instead of program files(x86) and then it started working

Hi,

I have the same problem

PANIC: Could not open AVD config file: C:\Users\Lenin Gómez\.android\avd\FirstDevice.avd/config.ini

How can I fix it?

I receive the issue as well with a fresh install of the SDK. My AVD is trying to look in my user profile on C:\Users\ when I've remapped my user directory to Z:\

The issue is that instead of looking in Z:\ for the ".android" folder it attempts to find it in "C:\Users\..." and fails. The obvious solution would be to provide a way to manually direct the AVD to start from a specified location.

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.

Will look into this. There is likely a difference between the way the SDK Manager and emulator pick up the user's directory when this variable is not defined.

[Comment deleted]

Hi

I found that the AVD is being created in C:\windows\system32\config\systemprofile\.android, so when it looks in C:\user\(profile name) it can't find it. If you copy the .android folder from C:\windows\system32\config\systemprofile\.android to C:\user\(profile name) you can start the AVD. The problem is it still wants a copy in C:\windows\system32\config\systemprofile\.android, so you can't move it. Did this on Win 7 32bit.

there is no .android folder in C:\windows\system32\config\systemprofile, i cant still use my avd can anyone tell the perfect solution for this =)

I installed SDK in my D drive .android directory is created in drive i copied that directory to %userprofile% and avd is working fine

Appears to be same issues as "Issue 36930831".

I have a 60GB SSD for my os (Win 7 x64) and a HDD (1TB) for my work and programs. So Win 7 is on a C: drive and everything else on a D: drive. I've relocated all my special folders on to D:. 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.). So a fix is need for that.

In the mean time I use a NTFS symbolic link. Open a command prompt in your user directory on C: (if you relocated all your special windows folders to D: then their should only be a hidden Appdata folder in your users C: folder). Use mklink program to make a hard link to the .android directory on D:. So if user John Doe move all his Users files from C:\Users to D: then the command to make the directory junction would be:

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

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

I have changed my user directory, so the sdk cannot find the file by using code-in path
so you can find the ".android" folder, then mklink it to the place that the sdk knows

The solution is to create a folder named: c:\android
And to add an environment (!user environment) variable named ANDROID_SDK_HOME with the value of c:\android.

PS thanks to Erel, admin from www.basic4ppc.com

Create an environment variable called
ANDROID_HOME pointing to the root directory of the SDK installation i.e. >> tools/ folder!!!!!!!!!!!!!!!!!

Create an environment variable called
ANDROID_HOME pointing to the root directory of the SDK installation i.e. >> tools/ folder!!!!!!!!!!!!!!!!!

i have face same error when start avd from cmd in windows7 . i overcome form this problem using command adb-kiil-server and adb-start-server . to restart the adb it allow to open the avd using command prompt .

found a solution.......i had unzipped the zip file in documents which i had moved from c:/ to d:/.....on opening Documents i found the .android folder. i copied it to c:/user/USERNAME and my avd began working. i have a win 7 32 bit.

No matter your configuration. If the message will be like this
"[2011-11-21 22:31:24 - Emulator] PANIC: Could not open AVD config file: C:\Users\Ярослав\.android\avd\my_defult_android_2_3_3_avd.avd/config.ini"

( "C:\Users\Ярослав\.android\avd\my_defult_android_2_3_3_avd.avd" - it's your AVD device configuration. )

than :

1. copy direcoty "my_defult_android_2_3_3_avd.avd" to some place where the path will not contain "Ярослав" symbols (I in result had the path like this "d:\android\my_avd_devices\avd\my_defult_android_2_3_3_avd.avd").

2. File "my_defult_android_2_3_3_avd.ini" will contained in directory "C:\Users\Ярослав\.android\avd\". Open this file.

3. Change "path=C:\Users\Ярослав\.android\avd\my_defult_android_2_3_3_avd.avd" to "path=d:\android\my_avd_devices\avd\my_defult_android_2_3_3_avd.avd"

4. Save and close. Start your application again))).

[Comment deleted]

@MrDanFow Thanks! Your Solution works!

Same issue – Many of my user directories are mapped to D Drive including the avd directory but the emulator is looking for the avd file on the C Drive.

Error message:

[2011-11-26 17:32:57 - Emulator] PANIC: Could not open: C:\Users\user_name\.android/avd/em22.ini

Used the suggestion from MrDanFow – At the Windows command line typed:

mklink /J "c:\Users\user_name\.android" "d:\Users\user_name\.android"

Problem Fixed!

Would be nice if this just worked out of the box without requiring this work-around as it is off-putting for a newbie.

same here, I also just fixed
thanks a lot!

Great! This done the trick. Big THX.

Not work for me :( The command: C:\Windows\system32>mklink /J "c\User\Алекс\.android" "d:\cacika.avd
The system cannot find the path specified.

One of your arguments is not a path to a existing directory, probabley "d:\cacika.avd", provide the directory name to the Android config files on your D: drive.

I also had such a problem... and solved now...
what  i think where the .android was actually present was a wrong path...
I just copy .android folder from that location and pasted it in the folder where the eclipse was searching ..and it worked....

It can't look like impossible or strange but the trouble can mended....

The solution is to create a folder named: c:\android
And to add an environment (!user environment) variable named ANDROID_SDK_HOME with the value of c:\android.

./android
Tools menu/Manage AVDs...
New...

Since I move my home folder to another driver, default installation will not work.
Add the environment variable ANDROID_SDK_HOME = %your user folder%

e.g.
ANDROID_SDK_HOME=F:\USERS\FRED\

Now it should work.

please try to use
 mklink /J "C:\Users\vru\.android" "D:\.android"
because it could not found the .android folder......ENJOY it!
Aj.Chai

I solved it like this:

C:\Users\my_user_name>mklink /D .android d:\installpath\.android

For me, the problem was a character of my path that doesn't own to ASCII. It was an accent in my user name. An easy solution it's creating a new user make sure to use only ASCII characters.

yaroslav...@gmail.com from Comment #26

Your recipe has worked for me. Thank you!!

solution number 21 works for me, thank you :)

solution 19 is OK. thanks.. but we want adv automatic work..

Thanks MrDanFow. Your solution works and the explanation makes sense.

Reading the MrDanFow's explanation i tougth about coping the folder at D:\MyUser\.android to C:\User\MyUserAndroid\, it worked for me, but i have to do it every time a create or edit a new one avd. thx all

I have this problem because my Windows 7 home directory is on another drive. In my case, MrDanFow's method works.

  Thanks MrDanFow
, I have overcome the problem

I'm running Eclipse on Vista 32bit.

Value of ANDROID_SDK_HOME maybe works immediately.
I restarted Eclipse, but it didn't works.
I rebooted my OS, it works fine.

I didn't create junction.

I just resave C:\Users\вася\.android\avd\EMULATOR.ini using ansi codepage with notepad

EMULATOR - name of avd
 

Thanks MrDanFow. Your method solved my problem too.

I'm using Windows 7 and since my user is not an administrator, setting enviroment variables is not the easiest.

But I found how to set the variable when you're not an administrator.

From the command promt, I wrote:

setx ANDROID_SDK_HOME "D:\Java\Android\android-sdk"

And when restarting the command prompt, i could write "set" and see it was there. When I restarted Eclipse, everything worked just fine.

[Comment deleted]

I copied the android files my compiler was looking for to the location where they couldnt be found.  Seems to be working so far, good luck!!!

Can anyboby help with this?
Thanks

Thanks MrDanFlow:


mklink /J "c:\Users\user_name\.android" "d:\Users\user_name\.android"

Was my solution. Make sure to kill the adb.exe process if you're getting an in use message.

I had my workspace in D:/workspace/android, so it has also created .android at D:/. However, when running the app it has search for it in C:/Users/<username>/

The true solution..... many users, like me, we have the Library path at D:\Library\MyUser... The AVD by default is created at .android DIR at d:\Library... just copy this .android DIR at C:\Users\'YourUser'\.android\.... and BINGO !!!!

any questions at: alexenter@gmail.com

[Comment deleted]

i had a same problem:

cmd.exe:

C:\Program Files\Android\android-sdk\tools\emulator -avd qwe

//qwe - name of my virtual device

PANIC: Could not open: C:\Users\ВасяПупкин\.android\avd\qwe.avd\config.ini

...

My solution:

COPY folder: "C:\Users\ВасяПупкин\.android"
(only copy, not move, because it is still useful)
for example in "C:\.android",
(or only a folder with the virtual device)

then
in folder: "C:\Users\ВасяПупкин\.android\avd\"
exist file: "qwe.ini"

in this i change string:
     "path=C:\Users\ВасяПупкин\.android\avd\qwe.avd"
to
     "path=C:\.android\avd\qwe.avd"

I have found a solution, it is a very awkward but work, firt of all open your AVD manager and look were is that program creating the virtual machines or devices, in my case is in documentsfolder\.android, but you can notice that when you start a virtual device it seek the data in userfolder\.android, so now lets to fix the problem.

-press windows + r, and type cmd, and press intro
-look that you are now in user folder by default
-type mkdir .adroid
-that last will create a folder in userfolder
-the last step is copy the content of the document in the avd maanger is creating the machines to the new folder, and that's all the machine is working now
-notice that if you create more devices after this steps you may to replace again the data.


This was my solution i don't know how to change the path for solving the problem permanently but this absolutly works

Hi Everyone,

I've solved this as follows:

1. Created an environment variable named ANDROID_SDK_HOME
2. Assigning to this variable the tools folder path (in my case is C:\Program Files (x86)\Android\android-sdk\tools)
3. Restarted Eclipse, and problem solved :)

I'm using Windows 7 x64

Solution is simple. Just copy the entire ".android" folder to the location shown in error.
Then restart or re-run your program and here it runs normally.

Comment 19 works like a charm. Haven't tried the others but setting ANDROID_SDK_HOME environment variable sounds sensible too.

** For those whose problem is having non-ascii chars in the user name, else skip this. **

The proper fix is in the hands of the android sdk devs, and it's to properly support windows 7 file names, including localization. In the while, you can use the DOS 8.3 file names to get this working for those directory names which have non-standard characters on them. You don't have to move anything or randomly create links around, and definitely you don't need admin rights to do this.

In my case, the user dir is "C:\users\jesús\", which has a tilde, and android sdk doesn't like that. I launched cmd, then did this:

dir c:\users\ /x

That will provide the short name, which will resemble the starting of the long name, and will probably end in something like "~1", or "~2", you get the idea. The tilde '~' is obtained by pressing left alt and then writing 126 in the numeric pad to the right (on a conventional pc keyboard). You can also get them on a spanish keyboard by double pressing alt+4 in the alphabetic keyboard, but that might not work on other layouts.

In my case it was "JESS~1", so I pressed control+esc to open the menu, wrote "var", an option appeared in the menu to set the user vars (not system ones), I selected it and pressed enter. Then just create a var called ANDROID_SDK_HOME and assigned to it the fixed path value,

C:\Users\JESS~1\Desktop\andoid\android-sdk-windows

If there are more parts with accents or non-standard chars, make sure you use the 8.3 convention in all the needed places. Use dir /x to find the short name(s).

A last note: the VMs created beforehand will fail to run, it seems they hard code the paths at creation time. So you will need to delete them and create new ones.

@MrDanFow comment 19,
Your solution works flawlessly!
 

Hi Everyone,
The solution 19 works perfectly!

Thanks

Comment 49 worked for me (I have non-ascii chars in C:/.../.android dir).
Just resaved my *.ini AVD config file with Notepad using ANSI codepage - works like a charm.

Comment 21 was nice and simple! I was having an issue with the emulator on multiple desktops that I created with Dexpot.

Comment 49 really work=)Thank you=)

My error is
[2012-08-18 21:19:58 - Emulator] PANIC: Could not open AVD config file: C:\Users\Mark AnĹľe\.android\avd\Gingerbread-2.3.3.avd/config.ini

But the .android file IS on C:\, in \Users\Mark\.addroid location! What seems to be the problem!?

set Environment variable
for example : ANDROID_SDK_HOME d:\

The environment variable tips seemed to have worked for me.

ANDROID_SDK_HOME = C:\users\my.username

I restarted eclipse, ran the Android Virtual Device Manager, no "PANIC!" stuff now.

Previously, I got a "PANIC: ..." message even though the path it looked for was actually correct!  Something about the environment variable ANDROID_SDK_HOME has fixed this.

Thanks!  That was pissing me off!

I installed the SDK, and have the same issue. I cant get the eclipse plugin to work, I cant get the emulator to work having followed the online instructions to the letter.

If i open thee AVD and try and start an AVD, I get:

android sdk PANIC: Could not open: C:/Users/Me/.android/avd/android4.1.ini

i tried setting a user env var:
ANDROID_SDK_HOME = C:\Users\Me

But that did not help.

I am admistrator. Windows 7 64bit. Tried doing it by running as administator too, no joy.  Tried lauching the emulator from the command line with parameters, just flash up a windows then closes it again.

Is there an old version anywhere which still works?  I just need the emulator, but cant get it working from the current download.

OK, got the emulator running by:
1) making the Env var change
2) re-launching AVD manger as administrator
3) re-creating the AVDs

However, it is too slow on my 16GB RAM quad core i7-2720 with Quadro 2000M to be usable.

Simple and easy:
C:\>mklink /J "d:\Users\coelhse1\.android" "d:\coelhse1\.android"
Worked for me.

Tks eli.pavlov.vn!

It worked!

The issue is with the ANDROID_SDK path. If the path is defined the AVD manager looks for the .android folder inside the ANDROID_SDK path. But the configuration is stored your home folder. If you don't need to use the ANDROID_SDK path just remove it from where you have defined it.

Linking to the folder is just a temp fix. If you change the SDK location issue will come back.

Hope this helps.

I just met this issue when I redirected my Desktop folder to a place other than %USERPROFILE%\Desktop. I found that while creating a VD (virtual device), AVD Manager uses folder Desktop\..\.android, while running a VD, the AVD Manager looks for it in %USERPROFILE%\.android. That makes this issue happen, when you redirected the Desktop folder. Seems the developer for AVD doesn't read Windows documents well.

You can just copy the .ini file from where it actually is, to the location where the AVD Emulator is pointing.

DanFow's method worked thanks.

In Eclipse, navigate to Window -> Preferences -> Android -> Build, and see the "Default debug keystore:" path location.

Create a custom path by specifying your current location for the .android directory where you are getting the error.

For a good explanation of the underlying cause of this, see comment #6 of issue 36947852 

http://code.google.com/p/android/issues/detail?id=31593

This work for me thanks !

solution #21 worked for me too

Dear "novalan..." (#51): Thanks so much! Your SETX command solved the problem I've been wrestling with for 2 days! The emulator window now appears!

thankyou #57 your answer worked for me!!!! been trying for ages.

alexen...@gmail.com thanks...#57
your answer is correct...and working....!!!

thank you that work:
#75hob...@gmail.comOK, got the emulator running by:
1) making the Env var change
2) re-launching AVD manger as administrator
3) re-creating the AVDs

However, it is too slow on my 16GB RAM quad core i7-2720 with Quadro 2000M to be usable.

1. copy your android debug location to C:/Users/<Your User>/.android
  Ex: My android bebug location in E:/.android
      I copy all of things in this folder to C:/Users/MinhIT/.android
2. open Eclipse. select tab: Window > Preferences > Android > Build > Browse
   and select to C:/Users/<Your User>/.android/debug.keystore

Thank you, it appears this feedback is no longer relevant to current versions of the Android emulator.

If a similar problem arises with the current version, please open a new issue with all details. Thanks.