Eclipse Community Forums: Newcomers » ADT in Eclipse, installed but failed to start?

Help

Home

Home » Newcomers » Newcomers » ADT in Eclipse, installed but failed to start?

Show: Today's Messages :: Show Polls :: Message Navigator

ADT in Eclipse, installed but failed to start? [message #693649]

Wed, 06 July 2011 23:54

JIA Pei

Messages: 49
Registered: September 2009

Member

Hi, all:

I successfully installed Android SDK 3.1 in Windows, which seems to be installed to C:\Program Files\Android\android-sdk . However, whenever I'd love to start a version of Android, I got the following error message:

PANIC: Could not open: C:\Users\peij\.android/avd/3.1.ini

Why is that? I can't see anything wrong I made so far. Can anybody give me hand???

Cheers
Pei

Report message to a moderator

(no subject) [message #693656 is a reply to message #693649]

Wed, 06 July 2011 23:59

Russell Bateman

Messages: 3798
Registered: July 2009
Location: Provo, Utah, USA

Senior Member

On 06-Jul-11 17:54, JIA Pei wrote:
>
>
> Hi, all:
>
> I successfully installed Android SDK 3.1 in Windows, which seems to be
> installed to C:\Program Files\Android\android-sdk . However, whenever
> I'd love to start a version of Android, I got the following error message:
> PANIC: Could not open: C:\Users\peij\.android/avd/3.1.ini
>
> Why is that? I can't see anything wrong I made so far. Can anybody give
> me hand???
>
> Cheers
> Pei

(Life is so much easier when Windows developers get away from Program
Files when it comes to installing development tools like Eclipse.)

I advise you to go to http://www.vogella.de, find Lars' Android
tutorial, and run through it.

Report message to a moderator

Re: (no subject) [message #696567 is a reply to message #693656]

Thu, 14 July 2011 10:11

Luis Ramon Gallego

Messages: 2
Registered: July 2011

Junior Member

Yes I got the same problem and what I have seen is:

1.- When I create a new device with AVD Manager, I can see on the top of the window, on the list of existing Android Devices, that the path is different to the path in the PANIC error from Eclipse
(In my case)
--Eclipse Error: [2011-07-14 10:55:33 - Emulator] PANIC: Could not open: C:\Users\lrgallego\.android/avd/Galaxy.ini
--AVD Manager devices path: C:\Users\Administrador\.android\avd

2-. I've copied the Galaxy.ini in the path that Eclipse is looking for ... and now Eclipse rich the device (inside this ini file there is a path to the virtual device), but there are some different errors now... and since I'm not getting used with eclipse I can't fix it ... may be other mates will help us for the next step to solve this problem. (I have seen that it's already a bug reported for it)

I'm using Eclipse classic Version: 3.7.0 and Windows 7 Enterprise

The new Errors are:
[2011-07-14 11:52:02 - EMT_BT] ------------------------------
[2011-07-14 11:52:02 - EMT_BT] Android Launch!
[2011-07-14 11:52:02 - EMT_BT] adb is running normally.
[2011-07-14 11:52:02 - EMT_BT] Performing lr.android.essentials.RFCommConnection activity launch
[2011-07-14 11:52:02 - EMT_BT] Automatic Target Mode: Preferred AVD 'GalaxyS' is not available. Launching new emulator.
[2011-07-14 11:52:02 - EMT_BT] Launching a new emulator with Virtual Device 'GalaxyS'
[2011-07-14 11:52:02 - Emulator] invalid command-line parameter: de.
[2011-07-14 11:52:02 - Emulator] Hint: use '@foo' to launch a virtual device named 'foo'.
[2011-07-14 11:52:02 - Emulator] please use -help for more information

Report message to a moderator