On Fri, Jan 7, 2011 at 2:29 PM, Moto <medicalsou...@gmail.com> wrote:
> I guess my knowledge on the subject was not far off... I guess I was being > mislead by all these task killers and users complaining... They just assume > a visible process is hogging CPU and memory. Well it could on applications > that aren't managing things properly. > Actually, even misbehaving applications can't -- if they are to the point of hogging memory, then as being in the background in will be on the list of things to be killed to get memory back. And if it is trying to suck CPU, all of the background apps put together can only get at most 10% of the CPU cycles from any foreground processes that want them. Prior to 2.3, one thing they could do is use CPU in the background when no foreground apps are trying to run, which could more quickly drain the battery (and they would show up in battery usage due to this). In 2.3 we now try to look for this to more aggressively kill background processes with this behavior. -- 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
