Tmobile Samsung s3 battery drain

[Cadeveloper27]

Hi i have just gotten a samsung galaxy s3 from tmobile strait from the store. It is great but the battery life is terrible. even with light usage the battery goes down around 30% percent per hour. i have already tried to factory reset and disable all bloat wear that came preloaded (tmobile TV, ect) any suggestions?? i have tied and researched this for hours. thanks again for any help

[/S][/S]

 

[Almeuit]

What's your screen on time?

Sent from my Sprint S3 using AC forums.

 

[Cadeveloper27]

here it is

 

[meyerweb#CB]

If, on the first battery stats screen you posted, you tap on the word "screen" it will show you actual screen on time, in hours and minutes.

But given what you've shown us, a couple of things stand out. Your most used app is Chrome. It would seem you've spent a bunch of time online, which means a bunch of screen-on time. The screen, especially if the brightness is turned up a fair bit, uses a lot of battery. That's the downside of the big, beautiful screens on all modern phones, not just the S3. There's no way to tell what you've been doing on the web, but possibly watching videos or playing online games? Or even just a lot of surfing? Those will suck a lot of battery, too, because they're using both the radio and the cpu or gpu pretty heavily.

With a lot of screen-on time, all you can really do is turn the brightness down. I find that indoors I can set the brightness quite a bit lower than the automatic setting chooses.

The one area that seems possibly out of whack is the Android System usage. If you tap on the refresh button in the top right corner, the words "Android System" will be briefly replaced by the actual process that was the biggest part of A-S's usage. It's a very brief flicker, so you may have to tap it multiple times to figure out what it's saying. Let us know what that is.

If it's 'SurfaceFlinger', that's probably an indication that you were doing a lot of page changes (SurfaceFlinger is the process that does screen redraws), and there's likely no real issue. If it's something else, especially if it's QOSmgr or GSIFF Daemon, then let us know.