2.0 includes a UI showing you which -services- are running and the resources they are using. This is what you really care about, not whatever random processes are being kept around by the system in case it needs them later. (Fwiw, the worst that can happen is a bad app sits there spinning the CPU draining your battery; you'll see this in the battery usage. As of 1.6 it can't get more than 5% or so of the CPU so it won't cause the foreground UI to slow down.) So having a "task killer" that kills process is really not that useful -- this comes from thinking about the system like a standard desktop, but it is not. For example, the app may have a service running, causing the process to come right back; it may have alarms scheduled, causing the process to come right back; it may be watching for broadcasts, causing it to come right back. That is why the API to force stop an app does what it does.
2009/11/17 Cédric Berger <[email protected]> > On Fri, Oct 16, 2009 at 00:07, Dianne Hackborn <[email protected]> > wrote: > > If you kill the process, it will not impact the alarms, the same as it > won't > > impact notifications etc. > > > > What these programs are doing is using the API that is tended to force > stop > > -everything- about the application: stop all services, cancel all alarms, > > remove all notifications, etc. This is all working as intended, the apps > > are just abusing this API to cause things to happen that you probably > don't > > want to have done. > > > > Wouldn't it be better if task killer, at least by default, just kill > all processes instead of using this API that completely kill/remove > apps ? > > (Though I think it would still be helpful to be able to completely > kill some applications, just that task killer have to be more explicit > in this case, and require the user to clearly ask to) > > Current situation is not really user friendly. It is really hard to > understand which applications are really running, which ones are off > but will be waken up by alarms and when, .... > Especially with our restrained device resources, a good task manager > is much needed (both to report apps usage, and to be able to control > them if needed). > > (And of course I truly agree that a lot of apps do use resources > needlessly -autostart with no useful reason, always running process > when they could just be triggered up on some events,...-) > > -- > 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
