Omg...why does android Os drain 35% of the battery?

[rxgadget]

Try going to Google Play and installing Wakelock Detector. I found Facebook was keeping the phone awake and even with screen off the app was pulling down info. Apparently, Facebook now updates itself outside of Google Play. I found this out on a ton of Android Blogs including Android Central and here. Technically this is against Google Play policies so can't wait to see what happens this week

Sent from my Nexus 7 using Tapatalk HD

 

[Whyareallthegoodnamestaken]

Hmmm I only just got my Nexus and I don't like the sound of this. I don't use it anyway. How do I disable it? I've unchecked background sync but it won't uninstall.

Sent from my Nexus 7 using Tapatalk HD

 

[sdmarathe]

that is a very bad argument made by a lot of so called experts. Swiping or emptying the list of running apps in JB or ICS, indeed DOES put them in the background. It also checks if they have any thread active and if not, puts them to idle or even close. IF you notice carefully, the RAM usage generally goes from say 90% to 45% and the slowly grows back up to 70%.

 

[sdmarathe]

All that removing apps from the recent apps list does is remove them from that list. It does not actually close the apps themselves.

Sent from my Nexus 4 using Android Central Forums

that is a very bad argument made by a lot of so called experts. Swiping or emptying the list of running apps in JB or ICS, indeed DOES put them in the background. It also checks if they have any thread active and if not, puts them to idle or even close. IF you notice carefully, the RAM usage generally goes from say 90% to 45% and the slowly grows back up to 70%.

 

[Diknak]

What do you mean by "putting them in the background"? That doesn't even make sense because that is not how Android works. As soon as the app loses focus, the activity freezes and no longer consumes CPU cycles, so it is already "in the background". To see this in action, open a browser that has an embedded video. Play the video and press the home button. You will notice that you no longer hear audio, which happens because the activity is frozen.

If services are running, there is no impact to swiping them off the recent apps list. To see this in action, use iHeart or some other music app and start playing music. Return to the home screen and open the recent apps and swipe it away. You will notice that your audio does not stop.

Sorry, but you are misinformed on the subject.

 

[mot524]

"What do you mean by "putting them in the background"? That doesn't even make sense because that is not how Android works. As soon as the app loses focus, the activity freezes and no longer consumes CPU cycles, so it is already "in the background"."

False and quickly disproven by anybody. Run an app that does something computationally intensive, e.g., draws a fractal with a lot of iterations. Start a task and switch away from the app. Come back a while later. The task is done. It was clearly using CPU power.

"To see this in action, open a browser that has an embedded video. Play the video and press the home button. You will notice that you no longer hear audio, which happens because the activity is frozen."

I'm sure what you're seeing is a feature. Whoever wrote the video player knows you don't want to watch or listen to the video while you're switched to a different app, so they went to some effort to pause the video for you when they receive a notification that the app has lost focus.

 

[mot524]

that is a very bad argument made by a lot of so called experts. Swiping or emptying the list of running apps in JB or ICS, indeed DOES put them in the background. It also checks if they have any thread active and if not, puts them to idle or even close. IF you notice carefully, the RAM usage generally goes from say 90% to 45% and the slowly grows back up to 70%.

I downloaded an app called "Android Assistant" that lists processes. It makes a distinction between apps, widgets, and services. Some apps (e.g., Facebook messenger) seem to have associated services that do not get killed when you kill the apps using the stock Android task manager.

I just killed all the apps on my phone using the stock task manager. Many processes did end but a lot of services are still running and using CPU power and memory (e.g., Facebook messenger).