Depends - obviously if your killing stuff it's good to aware *what* you're actually nuking. Nuking stuff that needs to be running obviously impact performance, however killing stuff that's just 'there' (and eating cpu) cos you ran it sometime subtracts resources and that's a bad thing. It's nice to have the choice - and what works for me might well not work well for others but then my perspective isn't typical perhaps (hey, i've been playing with the SDK). I'm not digging around killing services - just front end user apps. The linked article is good - and I don't disagree with it in principle but not all apps behave themselves all of the time.
That said, i'm going to experiment a bit with this - perhaps write some rogue apps to deliberately provoke android..


LinkBack URL
About LinkBacks
Reply With Quote
And why not? It's perfectly simple to work out what to kill and what not (to me anyway) in ATK 
(Yes, yes, Android is different, but I have lots of apps I'm only going to want once a month maybe, why should I leave it taking any resources at all?)
