And if you're not in the USA, you're kinda screwed for Honeycomb
development.
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,
I am not in US and I really dont want to buy new hardware to develop
for Android as its only an hobby and learning tool.
I was looking for any optimization anyone has done on their system,
such as increasing the default JVM memory, increasing the default
stack space etc.
On Mar 22, 3:11 pm,
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
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
Thanks Mark for your suggestion.
According to the API, the default is 96MB RAM which I am not sure
applies to all versions of API.
I will try your suggestions and other hardware options mentioned in
API and update this thread.
-jm
On Mar 22, 4:23 pm, Mark Murphy mmur...@commonsware.com wrote:
Ok, here is what I did to make the Android 3 emulator slightly more
usable:
- increased emulator vm.heap to 256 from 49
- reduced the resolution to 1024x768, default was much higher
- emulator ram to 512 (tried 1024 but it crashed )
- also increased the eclipse vm to 1024
Its slightly more faster
Honestly, if you have any serious intention of developing for Android 3.0,
you need to forget about the emulator.
--
Chris Stewart
http://chriswstewart.com
On Tue, Mar 22, 2011 at 11:28 AM, j.s. mammen mamm...@gmail.com wrote:
Ok, here is what I did to make the Android 3 emulator slightly
I'm new on android dev, so how much had changed 3.0 from previous version? (I
guess you can develop in 2.x an debug normally then test 3 specific
functionality on device
Chris Stewart cstewart...@gmail.com wrote:
Honestly, if you have any serious intention of developing for Android 3.0,
you
The Honeycomb emulator is reportedly quite slow on all systems. Your laptop is
probably fine. You should probably spring for a real Xoom. The Wifi-only model
is due in US stores by the end of March. I can vouch that the 3G model is quite
nice and works fine for development.
- Richard Lawler
9 matches
Mail list logo
