No, it is not slowed down, it is running as fast as possible. Emulators are pretty intrinsically not able to use multiple processors, so you are emulating a ~400MHz CPU on a 1.2GHz CPU, so it is unlikely you'd get the same performance as real hardware. Your comparison to VirtualBox is misleading because afaik know it is a virtualization solution, not emulation -- the code of the virtual environment is the same x86 code that the host CPU runs.
You may want to try just developing directly against a real device. It may run faster than the emulator on your PC, and the development environment is nearly the same. On Thu, Aug 27, 2009 at 6:16 AM, Casper Bang <[email protected]> wrote: > > While I really like the emulator and how realistically it mostly > behaves, at prototyping/RAD times I wish I could over-clock it and > have to wait less for it. Not so much an issue on a full size desktop, > but I do find it odd how slow it is on a Core II Duo 1.2GHz > considering the performance I get when firing up a full fledged > Windows in VirtualBox. Has the QEMU emulator been "slowed down" such > as to better mimic the typical real hardware? And if so, is there a > way to tweak this? > > /Casper > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
