My Samsung S3 battery goes from fully charged to "low battery" often before I get home from work. I just put up with it because troubleshooting Android is such a pain even with Better Battery Stats.
But by exceeding my data quota this month I see exactly what the problem is. Android 4.3 disabled data last night because I went over my quota.
It is now 6:02PM and my battery is at 82% when it would usually be at 5% by now. I still used my phone almost exactly the same amount as I have a desktop at work. My battery usually goes down to 5% just doing nothing in my pocket and making a few calls and texts and some music listening.
My poor battery life is due to all the data transfer bull Google is doing in the background every day.
Better battery stats can identify the process like Bam_dmux or fast dormancy, but it doesn't tell you which apps are actually calling the wakelock.
If Android did keep proper track of this I am sure many apps would be deleted (including Google Apps) from phone in a instant.
But it is too much trouble to try to figure out which one it is so we just put up with 6 hour standby battery life when the manufacturer claims 72 hours.
What a mess ..... I am going to have to research "restrict background data" now to waste more of my time.
Looking at Data Usage in setting doesn't help much because it only tells how much not how often
HaHaHaHa: Google Search on = android "restrict background data" gives 192,000 hits
Does anyone know a good site or method to do this?
But by exceeding my data quota this month I see exactly what the problem is. Android 4.3 disabled data last night because I went over my quota.
It is now 6:02PM and my battery is at 82% when it would usually be at 5% by now. I still used my phone almost exactly the same amount as I have a desktop at work. My battery usually goes down to 5% just doing nothing in my pocket and making a few calls and texts and some music listening.
My poor battery life is due to all the data transfer bull Google is doing in the background every day.
Better battery stats can identify the process like Bam_dmux or fast dormancy, but it doesn't tell you which apps are actually calling the wakelock.
If Android did keep proper track of this I am sure many apps would be deleted (including Google Apps) from phone in a instant.
But it is too much trouble to try to figure out which one it is so we just put up with 6 hour standby battery life when the manufacturer claims 72 hours.
What a mess ..... I am going to have to research "restrict background data" now to waste more of my time.
Looking at Data Usage in setting doesn't help much because it only tells how much not how often
HaHaHaHa: Google Search on = android "restrict background data" gives 192,000 hits
Does anyone know a good site or method to do this?
Last edited:
