I don't know of any changes causing services to not restart. We did do a lot of tuning of how quickly we restart services to for example back off the delay at lot faster if we can't keep things running, in order to behave better under the increasing memory pressure we have as the system grows a bit and more and more applications seem to have background services running (for good reason or not). If you want to know for sure what is going on, try "adb shell dumpsys activity.services" which will show the state of all running services, whether there is memory for them to be actively running or not. I really hope your service wouldn't disappear from there, just delayed on being restarted. (Fwiw, all of the google applications share a background service that takes care of the push updates for their data, so a bug where this doesn't get restarted should get a fair amount of attention.)
Eclair will have another round of more visible work for how we deal with them. This is definitely an area of the platform that has needed to evolve a lot as applications make more use of it. On Mon, Oct 19, 2009 at 11:56 AM, dadical <[email protected]> wrote: > > I've noticed that background services seem to get killed more > aggressively in 1.6, particularly when memory is low. Does that make > sense? Also, OCCASIONALLY, background services that have their > processes killed to recover resources don't seem to restart. This has > been incredibly difficult for me to debug, as attaching a debugger > seems to change the rules of the resource mgmt game in some way. Any > hints? > > > > Dianne Hackborn wrote: > > Yeah, I don't know about GC optimizations, but background threads now get > > placed in a scheduling class that together can't use more than 5-10% of > the > > CPU; this helps a lot in keeping the foreground responsive. > > > > On Sun, Oct 18, 2009 at 4:06 PM, CraigsRace <[email protected]> wrote: > > > > > > > > My games run smoother too. 1.6 is a great improvement! > > > > > > I seem to remember talk of background processes getting a lower > > > priority in 1.6, which might also be helping. > > > > > > > > > On Oct 19, 7:33 am, Nikolay Ananiev <[email protected]> wrote: > > > > My game's animations are way more smoother in Android 1.6. Google did > a > > > > great job optimizing 1.6 > > > > > > > > On Sun, Oct 18, 2009 at 7:32 PM, Jason Van Anden > > > > <[email protected]>wrote: > > > > > > > > > I am unsure if this is something I am noticing because my app is > > > released > > > > > or not, but it seems to me that 1.6 GC's smaller amounts a lot more > > > > > frequently. It seems to make for a lot less stuttering when > graphics > > > are > > > > > drawn. (Then again, maybe I changed something in my code). > > > > > > > > > Curious ... anyone else notice this? > > > > > > > > > Jason Van Anden > > > > >http://www.bubblebeats.com > > > > > > > > > > > > > -- > > 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. > > > -- 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 -~----------~----~----~----~------~----~------~--~---
