Actually, bumping the RAM helps a bit. hw.ramSize ("Device RAM size")
of 1024, if you have enough memory on your development machine, does
improve performance. It is still fairly dreadful, but I couldn't even
get it to boot with whatever the default was.On Tue, Mar 22, 2011 at 7:19 AM, String <sterling.ud...@googlemail.com> wrote: > I think the point is that the Honeycomb emulator is abominable on every > configuration that anyone's reported. Even Google has admitted that it's > really bad. > AFAIK, nobody's reported any success with improving the situation by > tweaking settings, either. Why don't you do that, and let us know what you > find? > String > > -- > 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 -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.5 Available! -- 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
