View Single Post
Old 03-13-2013, 08:59 PM   #14
afv011
Captain Penguin
afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.afv011 ought to be getting tired of karma fortunes by now.
 
afv011's Avatar
 
Posts: 2,817
Karma: 2076640493
Join Date: May 2009
Location: Vancouver, BC
Device: nook*, nexus 10
Quote:
Originally Posted by Blossom View Post
Unlike other Android devices that seem to manager this okay this device doesn't you have to keep a close eye on what's running and what needs to be killed because it's suddenly taking up 50% of more of your cpu and the device will come to stand still if you don't. The Kindle app is one that does this alot. Another is the built the browser which I don't use because of it.
I'm sceptical. The problem is not with "Samsung not managing the apps" - that's done by the Android Framework and Samsung are very unlikely to alter that. If an app eats CPU all the time, it will do so on a Samsung device or any other Android device. Android has what's call "wake locks"; while an app holds a wake lock the device will not suspend (enter deep sleep mode); a misbehaved app could hold and not release a wake lock, causing quick battery drain. Such an app would misbehave on any Android device, the app manager built into Android does not kill apps based on how much CPU they use, but based on how many resources (memory) are available; background apps will be killed to make room for foreground ones.
afv011 is offline   Reply With Quote