I updated the Android SDK tools from revision 11 to revision 12, and the emulator now fails to start. When I try to run emulator.exe, I get:
invalid command-line parameter: Files\Android\android-sdk\tools/emulator-arm.exe.
Hint: use ‘@foo’ to launch a virtual device named ‘foo’.
please use -help for more information
The path to emulator.exe is C:\Program Files\Android\android-sdk\tools.
How do I fix it?
As was previously suggested, it does seem to be caused by the fact that there is a space in the default installation path of the Android SDK: C:\Program Files\Android\android-sdk\
There are a couple of possible solves, though-
- move installation directories to paths that do not contains spaces (as already mentioned)…
- but simpler and possibly slightly less cumbersome is simply adjusting the path in Eclipse to use 8-dot-3 directory name(s). Since I’m running Win7, I have two Program Files directories, the second one being “Program Files (x86)” which is where the sdk installed. So the 8-dot-3 path is PROGRA~2. Thus, I simply changed the “SDK Location” value in the Android Preferences in Eclipse from C:\Program Files\Android\android-sdk\ to C:\PROGRA~2\Android\android-sdk\ and everything now works fine.
If you don’t know the 8-dot-3 name of your desired path, just fire up a Command Prompt and execute “DIR /X”… the short name will be displayed next to each directory.
Same problem for me, though this is my first time trying to work with Android SDK in general. I believe the problem is with the location of the SDK. Note the “paramater” “Files\Android\android-sdk\tools/emulator-arm.exe.” I believe there is a bug in google’s code where it doesn’t have the directory the SDK is located in in quotes, meaning, if there is a space anywhere in the directory name, it won’t work. Can someone with their SDK in a directory with no spaces confirm my theory?
To work around the issue, you can call “C:\Program Files\Android\android-sdk\tools\emulator @foo” from the command line, where “foo” is the name of your emulator.
I got this problem just now, and I found a solution.
My path to the emulator-arm.exe is
C:\Program Files\Android\android-sdk\tools. When I try
emulator-arm @my_avd from the command line (
my_avd is my Android Virtual Device name), it works.
I fixed this problem on Windows XP. Just cut from “C:\Program Files\Android\android-sdk” and paste content directory to “C:\Android\android-sdk”. Set my system varaible ‘ANDROID_HOME’=”C:\Android\android-sdk”. Set path to Android SDK in Eclipse as “C:\Android\android-sdk”. That’s it!
Everything works fine.
Since the cause of this issue is the space within filepath names of the Windows install directory then another workaround is to use the file short names (i.e. 8.3 alias filenames).
Specifically, if root install directory for Android SDK is
c:\Program Files\.. then use
c:\Program Files(x86)\.. then use
You can then launch the SDK Manager via the command-line by running:
Fixed in r13. Update your SDK Tools!
I think you are saying you changed the minSDK version of your app and now the emulator wont run…? this is because your emulator is the wrong version… assuming you changed the minSDK of your app correctly, all you need to do is create a emulator with the same SDK version. Open the Android SDK / AVD manager (icon top right of screen next to print token) and create a emulator with minSDK 12.
Moving your Android SDK folder to somewhere that the complete path will be without white spaces will fix the problem.
I also got this problem after updating SDK Tools from revision 11 to 12.
I found it was a problem with a space in the upper directory name where android-sdk-windows resides, then I copied both ‘eclipse’ and ‘android-sdk-windows’ directories from my ‘Program Files (x86)’ to the root of drive D:.
All is solved now!
As an alternative to PROGRA~2 method (which is not working for example in Intellij IDEA), you can create a symlink named, for example, prg to Program Files (run mklink /? from command line to learn how to do it), then run emulator as C:\prg\Android\android-sdk\tools\emulator.exe. Change path to SDK/emulator in your IDE also.
I had a same problem when I setup r12. I found out this problem was caused by blank spaces in the path you setup android SDK. The solution is that you should move the folder of android SDK to a place without spaces, in your case : E:\andriod-sdk or D:\abc\xyz\android-sdk.