Skip to main content

Android emulator-arm.exe crashing in Windows XP

I have tried to install Android SDK (r12) to start playing with developing applications for the platform. For no reason, I picked Windows XP Sp3 as my development OS.

Customary to getting started with new programming language or platform is to create the equivalent "Hello World". The sample program was small and easy to digest but running it for the first time was not a good experience.

The default Android Virtual Device configuation as per the tutorial keeps crashing on Windows XP. This is the message that I am seeing:
emulator-arm.exe has encountered a problem and needs to close.
We are sorry for the inconvenience
Searching the blogosphere shows the following sites that standout:
The information from Stackoverflow did give a good hint as to what might be the issue. It seems like the Android SDK, specially the emulator, does not like spaces in the directories. With VirtualBox virtualization at my disposal, I started poking around with the installer.

To make the long trial and error short, below are the key changes to make Android development a little smoother.

Before installing the Android SDK (installer_r12-windows.exe), set the following system environment variable:
ANDROID_SDK_HOME = d:\home
Of course you have to change d:\home to your desired folder. Ensure that the folder exists, this is important before starting with the installation. By the way, this is the folder where the Android virtual device(s) will be created.

Now, install Android SDK. I would suggest to use c:\android\sdk for the destination folder.  If not, ensure that the path location does not include any spaces and that the individual folder length is less than or equal to eight characters.

With all this set, continue with the installation of Android software development environment and enjoy!!!

~ts

Comments

Anonymous said…
As I had the SDK already installed, I copied the .android-directory from the old location to the new one and set the ANDROID_SDK_HOME as you described. That also worked for me.
Good to know that SDK need not be re-installed.

Thanks for the additional information.
Administrador said…
Thanks for information.
Administrador said…
Thanks for information.
@Administrador
You are welcome... thanks for the comment.
....$Vignesh said…
i changed the path as well as the resolution to work
Good to know that it is workig for you :). Thanks for dropping a note!
Anonymous said…
Thanks for post! You have to change the Andoid SDK path in Eclipse - Window/Preferences - SDK Location. I'm using Eclipse Helios.
Sr said…
Thanks a lot for the post, it works for me as well
Sr said…
Thanks a lot for the post
Anonymous said…
Thanks boss, you saved my day!
I am glad to be of help... thanks for dropping a note.

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.