> Yep the problem is largely associated with services and not just random > processes running. That is why the running services UI was introduced.
Trouble with that is, it doesn't show the *running* services but the *started* services. Esp. services written for 1.x might just linger around to do some work when required, and not be "foreground" services, so they can be kicked anytime without trouble. Sure, stopService would've been the better solution in most cases, but these services won't bother, but developers get queries why their service is "running" all the time. While other services or broadcast receivers might regulary calculate 10-digit prime numbers without being shown... > 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). Any plans so far? -- 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
