H-m-m-m. Interesting point. Emulating a 1Ghz CPU on a 2Ghz CPU is bound to be slow. But given that, I would be still be happy if the emulator were only 1/25th the speed of the emulated system (I have dealt with worse). It is still, after all, faster than waiting for a developer version;)
On Feb 24, 8:33 pm, Zsolt Vasvari <[email protected]> wrote: > I second this. The emulator is unusable for Xoom and I wouldn't hold > ny breath for any significant improvements in the speed of the > emulated machine, no matter what Romain is saying. Even if they > manage to double the speed of the emulator, it would still be pretty > much unusable. You will never be able to satisfactorily emulate a > 1GHz processor on a 2GHz processor of a completely different > architecture. > > What Google should do is sell a developer version of Xoom, like they > do with Nexus One, perhaphs a 16GB WI-FI only version. Until then, I > doubt too many indy devs would make a Honeycomb version of their apps. > > In the last 6 months, Google has made thousands of dollars off my app > -- I think it would be in their best interest to help successful > developers get their hands of their latest platform. > > On Feb 25, 9:25 am, Arron <[email protected]> wrote: > > > > > > > > > I bought the Xoom cuz I was unable to program and test my code > > effectively on the emulator. I wish we can get one for a discounted > > rate or one that's not tied to Verizon for developers. > > > On Feb 24, 4:09 pm, Indicator Veritatis <[email protected]> wrote: > > > > Nice though that fix would be, to date, there has been a reasonable > > > workaround for the emulator slowness: launch once at the beginning of > > > your work session and don't kill it. > > > > As long as the emulator can be set back to a last-known-good-state, > > > such a workaround is livable. What is not livable is ADT failing to > > > return from a Clean operation. And since I find it really, really hard > > > to believe that the cause of this problem is just String's own cockpit > > > error, I will not be loading the latest SDK because of that report. > > > > I am sure lots of other people will be having a similar reaction. > > > Google has got to respond by either explaining what String did wrong, > > > or fixing the problem in the latest SDK release. That is clearly more > > > important than fixing emulator slowness, which is sure to be a slow > > > and major project. > > > > On Feb 24, 11:03 am, Romain Guy <[email protected]> wrote: > > > > > The problem is that the emulator is an emulator, not a simulator, nor > > > > does > > > > it virtualize your computer's CPU. Tools like VMWare or VirtualBox > > > > achieve > > > > great performance thanks to virtualization, apps in the guest OS run > > > > directly on your hardware CPU. In the case of Android's emulator, a > > > > completely different architecture (ARM) is emulated entirely in > > > > software. We > > > > are aware of the pain caused by the emulator and we are thinking of > > > > ways to > > > > fix it. > > > > > On Thu, Feb 24, 2011 at 10:58 AM, sblantipodi > > > > <[email protected]>wrote: > > > > > > 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 > > > > > -- > > > > Romain Guy > > > > Android framework engineer > > > > [email protected] > > > > > Note: please don't send private questions to me, as I don't have time to > > > > provide private support. All such questions should be posted on public > > > > forums, where I and others can see and answer them- Hide quoted text - > > > - Show quoted text - -- 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
