Thanks for the extra info and apologies for falsely slandering your API naming :)
I was under the impression that the UI activities of a package were in the same process as it's services ? So I had noticed the UI was not affected and therefore assumed the services were being targetted specifically. Probably I should move to the beginners board for a period :) Lee On Jun 2, 11:41 pm, Dianne Hackborn <[email protected]> wrote: > On Wed, Jun 2, 2010 at 1:18 AM, Lee <[email protected]> wrote: > > killBackgroundProcesses works (you need a permission for it), but it > > merely restarts the background services, so it's a little poorly > > named. > > Actually it does exactly what it says -- it kills a process. If an > application has a service that it wants to keep running, the normal behavior > of the system kicks in to restart the service for the app. As the > documentation says, this allows the app to do the same thing is the out of > memory killer (killing processes) without breaking applications by causing > their services to be stopped when they don't expect (or unregister their > alarms or the other things that fully stopping an app does). > > -- > 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
