Are you Working on Two Monitors and Your Android Emulator Keeps Crashing?
If doing basic Android development isn’t complicated enough… in addition to software programming problems sometimes you have to deal with software problems within your IDE (Integrated Development Environment). Sometimes this can be so confusing because it’s not a problem with your logic… the logic you just coded… it’s a problem with the IDE.
And if that’s the case it can be frustrating. My problem popped up when i switched my Eclipse version to Juno and reinstalled all my development stuff and got everything up and running again. Apparently if you’re running a two monitor set up for your development environment you might be susceptible to this bug.
Here’s how it works:
If you’ve started an android emulator, and you move it to the second monitor and then close it… your emulators will crash from now on. It has to do with a little file called “emulator-user.ini“.
Here’s how you fix it.
If you’re on a Mac like me, you’ll need to make sure you can see all hidden files. Here is a link that will show you how to do that.
The you’ll want to navigate you our User Directory. That’s usually a folder with a little house on it with your Mac user name as the folder name. If you navigate to your desktop within finder and then hold down “Command” and press the Up Arrow, you’ll be there.
Within that folder you should now see a host of ghostly files… you can now go into all these hidden directories and examine their contents. Inside the ghostly “.android => avd” folder you’ll find individual folders for all the emulators you have set up. within the folder with your AVD’s name, you’ll find the offending file “emulator-user.ini”
Just delete it. Your emulator should start. To prevent this problem just don’t close the emulator while on the second monitor. Then you should be fine.
My source for digging up this info is here:
According to this thread the issue has been resolved and will be in the next SDK update.