Yep the problem is largely associated with services and not just random processes running. That is why the running services UI was introduced. Not only does it let you see exactly what is doing this (and deal with it), but it is also the first step in making developers more accountable for (and often even aware of) leaving services around like this that don't need to be.
Regarding this though: On Mon, May 3, 2010 at 4:06 PM, Eric F <[email protected]> wrote: > Another part of the puzzle is educating the iditions, and another part > of the puzzle is to, as developers, use the APIs correctly. They can't > kill your service if it's not running and is triggered by > AlarmManager. > In fact one of the problems with the API that the task killers have been abusing is that it was there for the "force stop" button in the UI. This is not for killing processes. This is for making everything about the app stop: not just its processes and services, but removing its notifications, removing its alarms, EVERYTHING. This is why they have such a bad impact on well-behaved applications, and is something that really needs to be addressed in the platform (it is just not right for one application to do this kind of thing to another one). -- 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
