Sunday, June 6, 2010

Re: [android-developers] Re: Multitasking on Android - Why So Incredibly Bad?

Hello Diane!

I think you've misunderstood me somewhat. The problem doesn't seem to be that there isn't enough RAM available - that's a given already (because I know I'm using way too much RAM with all my open browser windows), and the process will be stopped anyway, no matter what I do.

The thing is, I'm guessing that WHEN the browser is closed, the browser state is saved in the phone internal storage (which is what I've been talking about this whole time - maybe I just haven't been clear enough in that respect - any time I don't explicitly say "RAM" when I'm talking about memory, I'm talking about the phone's internal application storage and _not_ the RAM), and the browser's state would require more space than the phone storage currently has available.

That would at least explain the symptoms I've been having, and the fact that the workaround, well, works.


On Sun, Jun 6, 2010 at 8:42 PM, Dianne Hackborn <hackbod@android.com> wrote:
Um, internal storage has very little to do with available RAM.  In fact apps on the SD card use a little more RAM than those in internal storage.  So this solution is just happening to do something as a side-effect...  maybe things are paging slightly faster because the SD card is faster than internal storage, so the browser isn't as slow to save its state.

On Sun, Jun 6, 2010 at 9:18 AM, Simon Broenner <simonbroenner@gmail.com> wrote:
Hello everyone!

The solution (or rather, workaround) for me, so far, has been to root the device and move my apps to the SD card, freeing up more of the phone's internal memory. I now have around 60MB of free device memory (albeit with 200MB+ of apps installed), and have only been able to reproduce the problem once (tried about 10-15 times).

Obviously this situation is still not ideal, but it's one I can live with. Hopefully the problem will more or less subside as device memory becomes larger and larger, and less and less applications need to be installed on the device memory itself due to Apps2SD being built in from Froyo onwards.

Thank you all for your help!

On Sun, Jun 6, 2010 at 6:11 PM, Dianne Hackborn <hackbod@android.com> wrote:
It's a constant in ActivityManagerService.  You wouldn't want to just change it, because it could seriously impact responsiveness.  The solution would be to have the activity manager be able to go on with the switch, but keep the application in foreground for longer, giving it a chance to respond with its state.


On Sun, Jun 6, 2010 at 3:27 AM, Mark Murphy <mmurphy@commonsware.com> wrote:
Simon Broenner wrote:
> Is there a way to increase the time that the browser (and/or other apps)
> has to save its state? Probably only with very deep changes in Android
> itself, if I'm not mistaken?

It's not something an application can choose on its own, but rather
would be in the device's firmware, somewhere.
Android Training...At Your Office: http://commonsware.com/training

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en



--
Dianne Hackborn
Android framework engineer
hackbod@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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en



--
Simon Broenner

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en



--
Dianne Hackborn
Android framework engineer
hackbod@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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en



--
Simon Broenner

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

No comments:

Post a Comment