Hi,
I recently downloaded BetterBatteryStats to get an idea of what processes are running on my phone, and how I could potentially improve battery life. What I found this morning is that a wakelock is keeping my phone active for large amounts of the phone battery time (up to 60%...sometimes more). This seems to be preventing deep sleep, and perhaps better battery life.
I'm a newbie to Android, so please excuse this potentially ridiculous question....but could my push email (exchange using touchdown) be causing this wakelock? The actual wakelock is called PhoneWindowManger.mBroadcastWakeLock.
Any info would be most appreciated!
By the way....I'm running an SGS3 with stock ICS.
lmyers said:
Hi,
I recently downloaded BetterBatteryStats to get an idea of what processes are running on my phone, and how I could potentially improve battery life. What I found this morning is that a wakelock is keeping my phone active for large amounts of the phone battery time (up to 60%...sometimes more). This seems to be preventing deep sleep, and perhaps better battery life.
I'm a newbie to Android, so please excuse this potentially ridiculous question....but could my push email (exchange using touchdown) be causing this wakelock? The actual wakelock is called PhoneWindowManger.mBroadcastWakeLock.
Any info would be most appreciated!
Click to expand...
Click to collapse
dude check this link http://forum.xda-developers.com/showthread.php?t=1179809&page=548
Related
Those of you using a battery app, what is your usual standby battery drain? I have been having some issues lately trying identify what's killing my battery on standby. I get pretty decent battery life using the device, but it seems to drain quickly on standby.
I am seeing 100ma+ with Wifi on, after turning all radios off and rebooting I can get it down to ~20ma or lower. It seems in the battery usage screen in settings that "Android OS" is using a lot of the battery, but it's hard to tell what actual service or process it is. Is there anyway to pinpoint the exact service or process munching the battery?
Thanks.
I'm no expert on this app, but Betterbatterystats might give you some useful information.
http://forum.xda-developers.com/showthread.php?t=1179809&highlight=BetterBatteryStats
UKseagull said:
I'm no expert on this app, but Betterbatterystats might give you some useful information.
http://forum.xda-developers.com/showthread.php?t=1179809&highlight=BetterBatteryStats
Click to expand...
Click to collapse
Thanks! That actually helped me narrow it down, it seems to be the "locationfriendservice" part of google maps, and a quick search indicated that this is a big problem for lots of folks.
It's possible I just had noticed it before when I was all stock, so I was thinking it was a result of a new kernel or something.
I have done what I can to mitigate the battery-hungry maps processes and will see tonight if I can retain better battery life (was losing like 10%+ in 6 hours on standby!).
I'm posting this hoping for some solid answers to explain when our Note should actually be in "Deep Sleep". I've seen many threads with people having issues with battery life due to our phones not sleeping correctly, me being one of them. Hoping this thread could help answer some questions that I'm sure I'm not the only one asking.
So my questions are...
1. When should our phone actually be deep sleeping?
2.Does having "auto-sync" on prevent or interrupt the phone from deep sleeping?
3.Does anyone know of any apps in particular that seem to be causing excessive wakelocks?
4.If a phone is left completely idle should it be in deep sleep the entire time?
5.What is the easiest way to determine what its causing the phone to wake from sleep. (I know that the app better battery stats will work, but I'm unsure how to use it to find the culprit.)
Anyone who knows the answers please help me understand so I can stop obsessing!
Really depends what app u are running. Best solution is to get a battery monitor (i use bad ass battery monitor); allows me to see wakelocks, screen on time and a bunch of usage details for each app u ran since boot/unplugged
Sent from my SAMSUNG-SGH-I717 using XDA App
Also i.downloaded setCPU and im using on demand setting and my battery got much better... In combination with JuiceDefender
Sent from my SAMSUNG-SGH-I717 using XDA App
connordroid said:
I'm posting this hoping for some solid answers to explain when our Note should actually be in "Deep Sleep". I've seen many threads with people having issues with battery life due to our phones not sleeping correctly, me being one of them. Hoping this thread could help answer some questions that I'm sure I'm not the only one asking.
So my questions are...
1. When should our phone actually be deep sleeping?
2.Does having "auto-sync" on prevent or interrupt the phone from deep sleeping?
3.Does anyone know of any apps in particular that seem to be causing excessive wakelocks?
4.If a phone is left completely idle should it be in deep sleep the entire time?
5.What is the easiest way to determine what its causing the phone to wake from sleep. (I know that the app better battery stats will work, but I'm unsure how to use it to find the culprit.)
Anyone who knows the answers please help me understand so I can stop obsessing!
Click to expand...
Click to collapse
1. Any time the device is idle (you're not purposely running background activity) and the screen is off.
2. It probably will sometimes, briefly. It depends on what's syncing. In my experience, the only sync that has caused issues is the Google currents app (but it can be easily adjusted).
3. Instant messaging apps tend to hold wakelocks if signed in (EXCEPT GTalk, which has little impact on battery). Skype has been notorious for this as well. Any app that can trigger data activity can wake the device into a wakelock.
4. Theoretically, yes it should (or very close to it). In practice, the most I've seen somebody achieve was around 97% (observable via CPU Spy).
5. BetterBatteryStats and CPUSpy together are what you need. In BBS, you're looking for partial wakelocks, kernel wakelocks, and alarms. Partial wakelocks are held by apps. Any partial wakelock more than a few minutes should be looked into (changing settings, or removing the app all together). In kernel wakelocks, you're typically looking for svnet-dormancy wakelocks. These are wakelocks caused by data activity while the screen is off. This should typically be less than 4%, I suppose. Alarms will tell you what processes are waking the device. Throughout BBS, the app name will probably be pretty evident. In most cases, you can google the package name if you're not sure. The developer of Better Battery Stats provides support in his thread if you provide the dump file (it's fairly simple to "dump" your information into a file for observation).
A good observation is to reset the timers in CPU Spy, turn the screen off, and let the device sit idle for a couple of hours. I'd say anything around 95% of deep sleep is pretty good. Personally, most of the time, I get close to 95% (in complete idle, of course). Looking in CPU Spy after a normal day's usage isn't helpful because it'll appear as if your device isn't entering deep sleep sufficiently.
Hey guys, I'm experiencing extremely high AOS usage in the battery stats. It is almost always higher than Display Usage.
SETUP
Rom: HyDrOG3N-ICS 13.05
Kernel: SiyahKernel v3.2.5.1
Battery: Official 2000mah
I've got some UV/UC for CPU and GPU, I don't experience any freezes or slowdown's at all.
I've tried turning off BLN and it didn't affect the AOS usage which means that there must be something else contributing to the high AOS usage.
I've got sync on and some periodic (1hr interval) syncs such as weather. I've got an additional push account. [IMO, this shouldn't be part of AOS]
Does anyone have any ideas how I can find out the culprits for AOS?
betterbaterystats app install an c wats draining....
lambstone said:
Hey guys, I'm experiencing extremely high AOS usage in the battery stats. It is almost always higher than Display Usage.
Click to expand...
Click to collapse
is that betterbatterystats ? or the normal battery stats in the ics options ?
depending on how much screen on time u have ur next big battery sucker will be Aos (since u stated that u have sync on) if the phone is idle most of the time...
in my case i see Aos usage thru the first half of the day being the most battery sucker, passing afternoon its display and calls with Aos after them and at night i have Aos climb back up top... why? because i leave the phone in my pocket most of the time except for when i need to call/send a msg thru whatever app/sms/mms..... or anything and that keeps the phone awake for that short time and then its back to idle in my pocket and the only thing working is Aos checking email and whatever is on in sync
dont be surprized to see it up top its only natural, but keep track of how much power u lose. Losing 0-5% of battery life an hour on idle(screen off/locked) depending on signal strength with sync on is normal... more than that and i would be looking for any wakelocks or whatever is causing the phone to lose so much battery juice.
i have seen bad modems use even more battery juice just trying to maintain a good signal even with data&sync off and 2g
Not sure how I managed to fix it. There wasn't any out of the ordinary wakelocks. I flashed the 3.2.8.2 siyah kernel and at the same time adjusted the polling rate of BMW. Seems like it was battery monitor widget battery polling rate that contribute to the AOS. I always thought that it would show up as a separate usage stat.
Hi Everyone,
I know there are thousands of threads regarding battery consumption on the SGII - I have tried many many suggestions and I still have terrible battery life. I was hoping someone could give me a hand in analyzing if my stats are normal or if there is anything I could do to make it last longer - my battery life is just terrible.
I'm running RootBox 3.2 Jelly Bean.
Please find attached my BBS and Battery graphic. Let me know if there is any other detail that I can attach in order to troubleshoot my battery consumption.
Thanks a lot in advance!
Try using 2G networks when you don't need big bandwith. 2G is enough for WhatsApp, WAP sites, messengers.
renguer0 said:
Try using 2G networks when you don't need big bandwith. 2G is enough for WhatsApp, WAP sites, messengers.
Click to expand...
Click to collapse
I have tried being on 2G the whole day with very similar results
Disable all data connections for a while and compare how much battery was used.
Try GetRIL to get a match baseband and see if it improve it.
nmuntz said:
Hi Everyone,
I know there are thousands of threads regarding battery consumption on the SGII - I have tried many many suggestions and I still have terrible battery life. I was hoping someone could give me a hand in analyzing if my stats are normal or if there is anything I could do to make it last longer - my battery life is just terrible.
I'm running RootBox 3.2 Jelly Bean.
Please find attached my BBS and Battery graphic. Let me know if there is any other detail that I can attach in order to troubleshoot my battery consumption.
Thanks a lot in advance!
Click to expand...
Click to collapse
Your log is not looking that bad considering your screen on time of about 2 hours and the CPU usage.
The cause of the largest wakelocks seem to be your music player and synchronization software. Maybe you could get less wakelocks by reconfiguring them.
fxrb said:
Your log is not looking that bad considering your screen on time of about 2 hours and the CPU usage.
The cause of the largest wakelocks seem to be your music player and synchronization software. Maybe you could get less wakelocks by reconfiguring them.
Click to expand...
Click to collapse
So you are saying 2 hours of screen on time draining over 70% of my battery is decent? Not sure how much its supposed to give
nmuntz said:
So you are saying 2 hours of screen on time draining over 70% of my battery is decent? Not sure how much its supposed to give
Click to expand...
Click to collapse
No, this is not what I'm saying.
First the battery draining is not over 70%, it is 64% (according to what your BBS log says). Second, the amount of time the phone spends running with a 'high' CPU frequency is quite large, or, in other words, the amount of time your phone runs at 'low' CPU frequencies or even better, is in deep sleep, is quite small.
Taking all this together I think you do not have abnormal or excessive battery draining.
Looking at my battery stats I'm troubled by how little the phone is sleeping. Consider:
13 hours on battery
1 hour screen on
6 hours deep sleep
That means that for the 12 hours I want using my phone, it only spent 1/2 of that time in deep sleep.
Shouldn't that number be 90+%? Can anyone help me figure out which app is keeping the phone awake?
Sent from my Amaze 4G using Tapatalk 2
It's impossible to know how much it should be sleeping without any further information.
I recommend grabbing Better Battery Stats and finding out what is causing the wakelocks.
Well, BBS just says that the wake locks were being thrown by the network (ie. rx_wake) which didn't really help me. I don't really know how to use BBS to determine what app is causing a problem.
Moreover, how do I even know there IS a problem if I don't have an answer to my original question (what's reasonable?).
So, I'll re-ask. When the phone isn't being used at all, what percentage of that time should one expect it to be in deep sleep?
Sent from my Amaze 4G using Tapatalk 2
Given the highly variable nature of battery reports, it seems that installed apps makes a huge difference as to how much the phone sleeps.
Goto the Processes tab in BBS, and see if there's a rogue app running in the background. I know the Amazon App Store loves to run even after I close it, same with Facebook.