Does anybody know what keeps Google from creating an Android native x86 emulator? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

If you have ever developed apps for Apple iOS - you know that your app usually runs 1000 times faster on the emulator than on an actual device. This is because the build in XCode is set up in such a way that it creates an i386-build of the app for native x86 emula开发者_运维百科tor. On the contrary Android emulator uses QEMU and takes naive approach to emulating the actual ARM-build of the OS. I think it would really speed up things if they created an x86 port of the emulator - especially taking into account that there is another virtualization layer - DalvikVM, which is the only thing to be ported - the apps will still get compiled into the same byte-code.

Maybe someone here has an in-depth explanation why is it so difficult to make a good-performing emulator so that the Android apps become testable in it?

---

The bad performance is caused by the software GL rendering. Google is working on it, so sooner or later there will be a smooth running emulator