Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am running the Android SDK inside a Windows XP VM in VMWare. As such, the Android Emulator takes forever to boot…
I have recently heard of another emulator — the MotoDev. For those of you who tried both, could you tell if the MotoDev has any speed advantage over the standard Android Emulator?
I’m the Product Manager for MOTODEV Studio. There is not a separate emulator inside Studio, but rather another view of the existing emulator process that is displayed inside an Eclipse View. It’s no faster than what you already have and depending on which transfer mechanism you use (native window vs. VNC), it could be up to 20% slower (native window is faster for Windows and Linux).
Now, as for why your emulator is taking forever…
The first time you start an emulator image (i.e. “AVD”), it has to recreate the entire target filesystem on your local disk. Subsequent launches will take less time.
If I understand correctly, you’re letting the Android emulator pretend it’s running its’ file system through QEMU (Arm Emulator) inside a Windows XP pseudo-file system (VMWare Disk Image) that’s running on whatever host operating system you have (your OS). That’s a lot of file system manipulation going on. If you can reduce the file system mapping, you’re going to see speed improvements. Can you map the Windows Android SDK into a real folder on your native file system? Removing that layer of abstraction is going to speed things up.
Good luck!
Eric