11

When I try to launch my Android Virtual Device, I get the following error.

Files\Android\android-sdk-windows\tools/emulator-arm.exe.
Hint: use '@foo' to launch a virtual device named 'foo'.
Please use -help for more information.

I have been using the emulator for months, and I just downloaded new updates from SDK/AVD Manager.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
A Taylor
  • 153
  • 1
  • 1
  • 9
  • 1
    Please refer to this post for a solution. It did not come up in the search but it did correct my problem. The space in the path name (PROGRAM FILES) seems to be causing the problem. I took the the renaming suggestion to change the path name to PROGRA~1 and my problem was resolved. http://stackoverflow.com/questions/6603194/starting-android-emulator-in-sdk-tools-revision-12 – A Taylor Jul 08 '11 at 20:38

5 Answers5

9

This problem is caused by blank spaces in the path you setup in the Android SDK. The solution is that you should move the folder of the Android SDK to a place without spaces, in your case:

E:\andriod-sdk-windows

or 

D:\abc\xyz\android-sdk-windows
Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Hung Tran
  • 1,595
  • 2
  • 17
  • 17
  • Thank you Hung Tran. I changed the path name to remove the space by using PROGRA~1 instead of PROGRAM FILES as suggested in another link and it works now. – A Taylor Jul 09 '11 at 11:52
  • How does that work when you use visual studio?? with monotouch? – Joe Jul 16 '11 at 01:45
4

Please refer to the Stack Overflow post Starting the Android emulator in SDK tools, revision 12 for a solution. It did not come up in the search, but it did correct my problem. The space in the path name (PROGRAM FILES) seems to be causing the problem. I took the renaming suggestion to change the path name to PROGRA~1, and my problem was resolved.

Community
  • 1
  • 1
A Taylor
  • 153
  • 1
  • 1
  • 9
  • 1
    Additional note: If you have "Program Files (x86)" folder, then it should be PROGRA~2. – NPC Sep 12 '11 at 09:46
3

It looks like someone already reported this problem, Issue 18317: Emulator in R12 doesn't properly invoke emulator-arm.exe if the install path as a space in it

... to summarize:

  • Yes, there will be a fix. We're working on it.

  • The primary workaround is install in a path with no spaces, e.g. c:\android.

  • If that's not a choice, the second workaround right now is to use the "short path" Windows notation, e.g. "C:\PROGRA~1" either on command lines or in the Eclipse preferences. Remember that the number might change depending on your directories; you can use "dir /X c:\" in cmd.exe to see the exact short path for a given directory.

We'll have to wait for their fix but in the meantime we can just remove the spaces in the Android installation directory.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
artsylar
  • 2,648
  • 4
  • 34
  • 51
2

In Eclipse go to Windows -> Preferences -> Android and in your SDK location replace C:\Program Files\android-sdk-windows with C:\PROGRA~1\android-sdk-windows

Dima
  • 1,788
  • 2
  • 22
  • 30
1

If you want to run the emulator only without eclipse you'll need to create a .bat file with the SDK short path:

for 32 bits machines: C:\PROGRA~1\Android\android-sdk\SDK Manager.exe

for 64 bits machines: C:\PROGRA~2\Android\android-sdk\SDK Manager.exe

luchezco
  • 11
  • 1