On Thu, May 10, 2012 at 1:25 AM, Johan Appelgren <johan.appelg...@gmail.com>wrote:
> Perhaps the Processes and Threads section in the Dev Guide could make it > more clear that it is up to each app to stop its background threads and > otherwise ensure they don't do anything when they're not in the foreground > then? Seems like a fairly common mistake that is difficult for most users > to understand, they just notice that their phone gets slower over time. > Using the CPU in the background will drain the battery, but unless you are explicitly doing something unusual it will not impact the foreground UI -- all threads in background processes are put into a global background scheduling group; all together all threads in that scheduling group can't use more than about 10% of the CPU. > Which is why, I guess, some games recommend that you force stop all cached > processes before playing. Not very user friendly. > That is very unlikely to be needed or useful. -- Dianne Hackborn Android framework engineer hack...@android.com 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
