Related
I would say that this isn't bad at all. Wifi and GPS are switched on with sync/fb/twitter all day and random txt messages. 1 minute screen timeout is the most of my battery usage. I was trying out my new car mount which caused the battery graph to reset. Running unnamed 1.2 1GHz max 200 min undervolted on conservative
Sent from my SAMSUNG-SGH-I777 using xda premium
A lot better than me for sure. Yesterday I barely used my phone, but it was dead in about 14 hours. I don't know how you guys do it.
Post your battery usage and apps/widgets
Sent from my SAMSUNG-SGH-I777 using xda premium
How do u do tht I cnt keep my battery charged I'm running aosp cmod set CPU everything it just takes forever to charge and it drains quick
Sent from my LG-VM670 using xda premium
If it takes forever to charge, that means something is constantly using the cpu power and causing it to discharge while you're charging it. I use an extra battery charger and just swap between the two. Please post your wakelocks from betterbatterystats (available somewhere on the forums for free), your battery graph, installed apps, and current widgets you use.
Mine takes around 5 hours to charge, and that's when the phone is completely off. I'll do another test run today with Bluetooth and Kaiten mail turned off. From looking at the wakelocks in Spare Parts (BetterBatteryStats doesn't work for me with MIUI), those looked like the two main offenders.
Here is a graph showing my charging time:
http://www.imgur.com/5fVwe.jpg
Somethings holding a wakelock and causing your phoen to be on all the time.
If Android OS is at 70% or above, you've got something waking up your phone.
If you look around, I've got a thread on known battery drainers here in General. I should ask Jivy26 to add it to the FAQ...
Actually, looking at the graph I think MIUI interpolated between the time my phone died and when I turned it on in the morning, so the 5 hour charging time I mentioned is most likely not correct.
Ok, quick update. I uninstalled some stuff that had a lot of activity in my MIUI battery history. I uninstalled Dolphin Browser HD, Amazon app store, Fancy Widgets, Pulse, Mobile Office, Brilliant Quotes. Also removed the IMDB and Flixster widgets from my home screen.
All of these showed activity in the battery history, but didn't show up as holding wakelocks. I guess whoever the culprit was, it just fell under Android OS.
Anyway, I went to bed with 92% battery and woke up 7 hours later with 91% battery left. This is with Bluetooth and wifi on, running GalnetMIUI 1.11.9 ICS with 200 min/1600 max, ondemand/noop. I guess I can't complain now.
I've also noticed that the ui feels a lot more responsive/less laggy, and the battery drops a lot slower when I'm using the phone.
21cdb said:
All of these showed activity in the battery history, but didn't show up as holding wakelocks. I guess whoever the culprit was, it just fell under Android OS.
Click to expand...
Click to collapse
This is common, if you look at my Known Battery Drainers thread you'll see that there are a lot of usage cases where a rogue app can get its usage blamed on Android OS.
Specifically, any app that drives data to your phone will cause the phone to wake every time it receives data. In some cases, this means 800 milliseconds spent resuming/suspending to process 10 bytes of data (which takes the app itself next to no time.)
It sometimes gets worse on wifi because some apps change data usage patterns when on wifi.
A situation like that usually causes a lot of wlan_wake, wlan_rx, or svnet-dormancy wakelocks in /proc/wakelocks (BBS does not show kernel wakelocks properly yet - chamonix added the feature recently but it's not quite working yet.)
My guess is it was fancy widgets/pulse. I use dolphin browser, amazon app store and they do not effect battery life at all.
That is my suspicion as well, and I will try adding apps back one by one to see which one was the culprit.
Right now RILJ Dialer is waking up my phone constantly with hundreds of wakelocks. Many people seem to have this problem, but I haven't seen a solution.
Well, this is looking very good! I never expected this kind of battery life.
Any thoughts on the wakelocks? Not sure if I should worry about them or not.
http://www.imgur.com/Je89M.jpg
http://www.imgur.com/ZhS6A.jpg
http://www.imgur.com/4u6Wp.jpg
Somethings still causing your phone to stay awake. Try removing all widget from your home pages
Sent from my SAMSUNG-SGH-I777 using xda premium
I honestly don't understand this. A few days ago the RILJ wakelock started showing up on BBS. It seems to keep going up - right now after 16h on battery it's at 16 minutes and the count is nearly 500. It's at the top of the partial wakelock list. The part that got me confused is CPUSpy - from what it shows, my phone deep sleeps perfectly. If I clear stats then lock my phone for, say, one hour, when I turn it back on it'll show 99% of the time spent sleeping and only a few seconds spent at higher frequencies.
How is it possible that I have a pretty frequent wakelock and still be able to deep sleep almost all the time? My battery drain isn't too bad, in fact I think a 3% loss over night (7-8 hours) is brilliant. After using wifi, it'd drain a bit faster, but settles after a while.
And I don't have my phone with me right now so I can't post dumps or screenshots or anything, sorry about that.
Edit: I'm on CM9 RC2, Siyah v3.5 if it happens to matter. I updated to Siyah 3.5 yesterday.
Why did you post this? If your battery is fine and you have no problems then everything is fine, no need for posting right?
Sent from my GT-I9100 using xda app-developers app
Better ask in BBS thread. Maybe a bug, if your battery usage is going fine then I think CPU Spy has no problems .
I don;t think this is really a problem.
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.
In 2 hours, I have lost 29% battery life. I'm pretty sure this can't be normal, especially with 1+hours of Deep Sleep.
http://www.mediafire.com/view/?2panq9fohk2atfe here is the "Better Battery Stats" for those 2 hours.
Thanks for any info
If it matters, I'm running CarbonRom.
pivotraze said:
In 2 hours, I have lost 29% battery life. I'm pretty sure this can't be normal, especially with 1+hours of Deep Sleep.
Click to expand...
Click to collapse
If you were to post this over at the BBS thread, they would tell you a few things right off the bat:
1. the facebook app is a battery killer. I'd start by freezing it (if you need facebook functionality there are more battery friendly apps for it)
2. Looks like you are doing a lot of syncing. turn it all off.
3. Enable root features in bbs since you're rooted (lets you get more info that may become relevant).
4. You need more idle time. plug in and unplug your phone to create an unplugged reference, then leave it be for a few hours.
The AudioOut_2 wakelock is an interesting one, especially since it's high on your list. In my case it showed up when I tried poweramp and it seemed to be related to the auto-start-when-headphones-plugged-in option, so if you use poweramp check that option. Others seem to get it from viber. If you have that, remove or freeze it.
So, give the above a try, and check a new dump. This will probably give you more stuff to look into. If you find a problematic app you can then determine whether it can be fixed by changing its settings, greenified, disabling its autostarts, or if you just need to avoid it.
pivotraze said:
In 2 hours, I have lost 29% battery life. I'm pretty sure this can't be normal, especially with 1+hours of Deep Sleep.
http://www.mediafire.com/view/?2panq9fohk2atfe here is the "Better Battery Stats" for those 2 hours.
Thanks for any info
If it matters, I'm running CarbonRom.
Click to expand...
Click to collapse
From what I see you have had no, or only one bar of signal? If so, you may want to use Airplane Mode. You can use Airplane mode and still use Wi-Fi.
Have you been around Wi-Fi? If you aren't around Wi-Fi, turn it off.
NFC. Is it on? Do you use it? If not.. Turn off.
If your battery level shows inconsistency, you might want to calibrate your battery.
I hope i helped, im not quite sure why you loose 11% every hour, while mostly in deep sleep. Go to performance control and use some tweaks for your kernel.
Tyler44346 said:
From what I see you have had no, or only one bar of signal? If so, you may want to use Airplane Mode. You can use Airplane mode and still use Wi-Fi.
Have you been around Wi-Fi? If you aren't around Wi-Fi, turn it off.
NFC. Is it on? Do you use it? If not.. Turn off.
If your battery level shows inconsistency, you might want to calibrate your battery.
I hope i helped, im not quite sure why you loose 11% every hour, while mostly in deep sleep. Go to performance control and use some tweaks for your kernel.
Click to expand...
Click to collapse
The low signal shouldn't have any affect on the battery of the G, when I was on aosp I used houcha's kernel an I got great battery life around 23 hours with 5 hours of screen on and was at 22%, with set CPU profiles engaged and no kernel tweaks from any app. And I live in an area that primarily has 0-2 bars of service at home and full lte when I work I leave everything on, all radios and data sync. Now that being said for some reason the development is moving towards synergies kernel, and it doesn't have nearly the battery life that houcha's gets
CPU profiles included: https://www.box.com/s/toj5p6qclr1adf69ttfl
Sent from my LG-E970 using XDA Premium HD app
The AudioOut_2 wakelock can be caused by corrupted Mp3 files on your SD card. It was wreaking havoc in our SGS4G community and the fix for us was always to use MP3val to scan and fix those files. It cleared the AudioOut_2 wakelock right up. I know these are totally different phones but hey its worth a shot. http://mp3val.sourceforge.net
Sent from my Nexus 7 using xda app-developers app
dvdbabcock said:
The low signal shouldn't have any affect on the battery of the G, when I was on aosp I used houcha's kernel an I got great battery life around 23 hours with 5 hours of screen on and was at 22%, with set CPU profiles engaged and no kernel tweaks from any app. And I live in an area that primarily has 0-2 bars of service at home and full lte when I work I leave everything on, all radios and data sync. Now that being said for some reason the development is moving towards synergies kernel, and it doesn't have nearly the battery life that houcha's gets
CPU profiles included: https://www.box.com/s/toj5p6qclr1adf69ttfl
Sent from my LG-E970 using XDA Premium HD app
Click to expand...
Click to collapse
Low signal does in fact drain your battery. When you have zero to one or two bars, your phone is searching for signal, It causes the phone to increase power to the antenna, to get signal.
Tyler44346 said:
Low signal does in fact drain your battery. When you have zero to one or two bars, your phone is searching for signal, It causes the phone to increase power to the antenna, to get signal.
Click to expand...
Click to collapse
I understand the premise that low signal causes mor power to be drained, my point was that it doesn't cause 29% on this phone that's not even close to possible
Sent from my LG-E970 using XDA Premium HD app
dvdbabcock said:
I understand the premise that low signal causes mor power to be drained, my point was that it doesn't cause 29% on this phone that's not even close to possible
Sent from my LG-E970 using XDA Premium HD app
Click to expand...
Click to collapse
Sorry, I didn't say thats why your loosing 29%, i was just giving you tips on how to save battery life.
Sent from my Optimus G using xda app-developers app
Also if u are rooted u can download greenify from apps store helps with battery drain by putting apps in hibernation that normally wont go there like facebook and maps..... Etc
Via LG OG running Rootbox 4.2.2
I'm getting some pretty bad wake locks.
It started months after installing JellyBeans19, so I know it isnt JB19 causing the wakelocks. It looks like they started after installing skype, but after uninstalling skype they are still here, Fast forward a few weeks, Installing JellyBeans20, wake locks still there.
If you see in my attachments the cause of the wake locks are NLPWakelock and NLPCollectorWakelock and there are only a few threads on XDA that talk about it, but no one seems to have an answer.
Anyone have an Idea of how to stop these wakelocks? Its really killing my deep sleep. Instead of going to sleep and waking up 8 hours later with only a 5% drain its now draining about 15% in the same time period
http://forum.xda-developers.com/showthread.php?t=2275316&page=2 this might have something that might help in it.
Sent from my SCH-I605 using xda app-developers app