The issue with HC is that it now has a huge screen to draw, and the emulator itself doesn't implement any hardware acceleration of drawing, so it needs to emulate ARM code that is rendering to a window, and then emulate yet more ARM code that composites together the final display.
Implementing hardware acceleration of drawing in the emulator is extremely non-trivial. It's not a matter of needing performance testing and improvement. The bottle-neck is very obvious, it is just difficult to solve. And wouldn't you like to have *some* kind of working HC emulator now before devices ship? On Wed, Jan 26, 2011 at 5:58 PM, Jake Basile <jakerbas...@gmail.com> wrote: > I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe > 5-10 FPS on the Honeycomb emulator. This thing needs serious performance > testing and improvement. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
