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 <[email protected]> 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. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > 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 [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] 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 [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
