I would like to have more respect about your work but the answer from Romain Guy doesn't respect our patience.
This SDK is simply UNUSEFUL, google save your time if you need to write a simulator like this, no one can use it because is too slow also for a fart app, it's unusable. If you can't do a simulator that can run at an acceptable speed, simply save your time, don't do it. Romain Guy, simulator is slow because its a crappy product, if you can run native android 2.3 on a 600MHz qualcomm processor for mobile phone, you can run android simulator on an I7 3.8GHz with 4 core and 8 threads. Today a modern CPU can simulate three PC OS with excellent performance at the same time, one modern CPU isn't able to simulate android. please, no kidding. On Feb 24, 7:19 pm, Reuben Scratton <[email protected]> wrote: > That does surprises me, considering the triangular tearing seen on the > Honeycomb emulator. I guess that was just framebuffer composition. > > Thanks for the clarification. -- 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
