Issue with ADV - can't find INI files

Can you post the exact error message?

UtahWJR said:

I have created an AVD using AVD Manager and when I try and start it I get a message stating it can't find the INI file for the AVD. Path where it is looking for the file does not exist

C:\Users\Administrator\.android/avd/Android22.ini

Path above does not look right - did not think you could combing forward/backward slashes.

Also, I can't find the Android22.ini file anywhere on the system.

Windows 7 Pro.

Suggestions?

Click to expand...

You didn't install all needed files for AVD. What it says when you start SDK Manager

Here it is how look mine:

PANIC: Could not open: C:\Users\BillR\.android/avd/Android22.ini

Looking at my machine I don't have the .android subdirectory and it won't let me create one - keeps telling me it needs a file name.

I have looked everywhere and I can't figure out where the ini files are being stored since I don't get an error when I create a new AVD,

Have AVD installed on another Win7 machine and it has the .android subdirectory and it has my emulator ini files.

Since I can live with out Emulator if needed just for giggles I tried a compile & run for HelloWorld from the IDE and get an error:

Compiling code. 0.01
Generating R file. 0.00
Compiling generated Java code. 1.15
Convert byte code - optimized dex. 0.43
Packaging files. 0.34
Signing package file (debug key). Error

jarsigner: attempt to rename bin\temp.ap_ to bin\temp.ap_.orig failed

Cleaning your project may solve this problem. Tools - Clean Project

Tried cleaning project with no change. Also turned off debug and still get the same error message.

Are these 2 issues maybe related?
Thoughts?

Just tried doing a simple compile first and then a compile & run and don't get the signing error - still won't run. Is that the step I was missing?

A little further research shows that the problem with the compile appears to be due to the directory I was working in was on the desktop - moved it to a subfolder and it compiles fine.

Using Bridge and that appears to be a quicker way to test than using AVD - still would like to figure out what's up there but have spent enough hours today to give it a rest for now.

Happy Turkey Day for everyone in the US.

Thanks.

Determined that the issue with AVD was caused by the SDK manager installing files in a shared folder called HOME while the AVD manager was looking for the files in the current USER folder. Removed the share and everything now works as expected.

UtahWJR said:

Determined that the issue with AVD was caused by the SDK manager installing files in a shared folder called HOME while the AVD manager was looking for the files in the current USER folder. Removed the share and everything now works as expected.

Click to expand...

SDK Manager installs AVD in .android folder in users directory

Here it is mine: