Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to setup a VM with a complete android development stack (SDK, Platforms, Eclipse etc) for a Hackathon. I'm having real trouble getting the emulator to start in the VM. I realize that the emulator is essentially a VM itself inside the Vbox VM and so is going to be slow, but it just hangs at the Android splash screen and never gets any further.

Might there be something going on with the VM that is causing it to run so very slowly? Is there anything I can do to give the VM more CPU? I've tried setting the execution cap to 100% but it didn't help any.

Anyone know what might be going on here, or have any ideas about how I might speed it up?



share|improve this question

migrated from Nov 19 '11 at 21:02

This question came from our site for system and network administrators.

You can figure out what's taking so long with these commands:

adb kill-server
adb shell logcat

The emulator does take a long time to start up on -- two minutes on high-end hardware. Essentially, it's doing a full device coldstart.

Also, the emulator sometimes fails the first time you try to start a device. Just close the device and launch it again. It should work from then on.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .