I just got my G3 yesterday but the battery drains so quickly. I rooted and added BBS and there are so many sensors and such kept awake. In just wanted to see if anyone has a clue,what I should do to contain these.
tomkins0752 said:
I just got my G3 yesterday but the battery drains so quickly. I rooted and added BBS and there are so many sensors and such kept awake. In just wanted to see if anyone has a clue,what I should do to contain these.
Click to expand...
Click to collapse
Kernel wakelocks don't keep the device awake per se. Those are processes that run when the screen is on. That's why the duration of all of them is almost the same. There's not going to be much you can do about those until/if custom kernels come along. You can try a factory reset, though I don't think it will help.
You should focus on partial wakelocks since those keep the CPU on when the screen is off.
hawkswind1 said:
Kernel wakelocks don't keep the device awake per se. Those are processes that run when the screen is on. That's why the duration of all of them is almost the same. There's not going to be much you can do about those until/if custom kernels come along. You can try a factory reset, though I don't think it will help.
You should focus on partial wakelocks since those keep the CPU on when the screen is off.
Click to expand...
Click to collapse
This list for kernel wakelocks goes on for a while. The partial wakelocks are minimal, but whatever is causing these kernel wakelocks is whats causing the device to get warm, and subsequently draining the battery at an accelerated rate (roughly 7%+ per hour with minimal usage.)
I have never before seen such an extensive list from BBS on any of my other devices. Usually its the accumulator of all the partial wakelocks at the top of the list of kernel wakelocks by a large margin.
tomkins0752 said:
This list for kernel wakelocks goes on for a while. The partial wakelocks are minimal, but whatever is causing these kernel wakelocks is whats causing the device to get warm, and subsequently draining the battery at an accelerated rate (roughly 7%+ per hour with minimal usage.)
I have never before seen such an extensive list from BBS on any of my other devices. Usually its the accumulator of all the partial wakelocks at the top of the list of kernel wakelocks by a large margin.
Click to expand...
Click to collapse
I'm with you. Been searching around for things I can freeze/hibernate to minimize wakelocks. Like stated earlier though we really need a custom kernel to get rid of a lot of those Kernel ones. The Partials aren't really that bad.
I have only had this phone since earlier today though so I'm keeping my eye on BBS like you are
Sent from my VS985 4G using Tapatalk
This phone does seemto have a ridiculous abou amount of activity going on. I had the dreaded (nlpcollectorwakelock) battery drain my first day but a reset took care of it. My battery had since calmed down and I'm getting good sot now. My android os stays at around 14-20%as well but a long as my sot is decent I'm not stressing anymore
Sent from my VS985 4G using Tapatalk
Yea mine is only draining at around 3% am hour with my use according to BBS.
That's just on WiFi and doing some browsing + Tapatalk+ a little YouTube.... So I can't complain.
It'll take a few charge cycles plus keeping an eye what else I can freeze and hibernate.
Considering the display on this thing that's pretty good I'm happy.... Be a little happier with a SaberMod ROM and Kernel though [emoji2]
Sent from my VS985 4G using Tapatalk
tomkins0752 said:
I just got my G3 yesterday but the battery drains so quickly. I rooted and added BBS and there are so many sensors and such kept awake. In just wanted to see if anyone has a clue,what I should do to contain these.
Click to expand...
Click to collapse
My battery life is just as good as on my G2. Under normal (moderate/moderate-heavy) use I can get a day out of it easily. Yesterday I went to bed with about 44% left after over 13 hours use (with 2.75 hours of screen-on time).
I would recommend using CPU Spy to make sure the phone is going into Deep Sleep. There might be some process keeping it at a higher functioning state and not allowing the phone to hit Deep Sleep. For the most part, the phone should be in Deep Sleep longer than any other processor state.
I think a factory reset is in order. If that does not help you might just have a bad device, or a bad battery.
mrhumble1 said:
My battery life is just as good as on my G2. Under normal (moderate/moderate-heavy) use I can get a day out of it easily. Yesterday I went to bed with about 44% left after over 13 hours use (with 2.75 hours of screen-on time).
I would recommend using CPU Spy to make sure the phone is going into Deep Sleep. There might be some process keeping it at a higher functioning state and not allowing the phone to hit Deep Sleep. For the most part, the phone should be in Deep Sleep longer than any other processor state.
I think a factory reset is in order. If that does not help you might just have a bad device, or a bad battery.
Click to expand...
Click to collapse
My phone is showing a huge number of sensors wakelocking the phone, and it was only in deep sleep 17% of the time since I unplugged it 6 hours ago. That kernel wakelock for the sensors needs to be fixed and then our battery life will be stupid good. You can't get as much screen on time on the G3 as I do on my G2. I was getting up to 10 hours of screen on time on my G2 the best i've managed was 3.5 on the G3. However, custom kernels will probably help there.
PWn3R said:
My phone is showing a huge number of sensors wakelocking the phone, and it was only in deep sleep 17% of the time since I unplugged it 6 hours ago. That kernel wakelock for the sensors needs to be fixed and then our battery life will be stupid good. You can't get as much screen on time on the G3 as I do on my G2. I was getting up to 10 hours of screen on time on my G2 the best i've managed was 3.5 on the G3. However, custom kernels will probably help there.
Click to expand...
Click to collapse
The Sensor WakeLocks are quite ridiculous indeed, but what is your phone showing for Partial WakeLocks and Alarms in Better Battery Stats???
Only way I could get mine under control was to use App Ops to limit Google Play Services to NOT keep my phone Awake.
Then I located COM.LGE.IMS and disabled its Receivers then froze it.
Then I Greenify everything possible lol
That Com.LGE.ims thing was waking my phone like crazy, maybe 50-100 times an hour if I remember correctly and I don't even use the feature its tied into... WiFi Calling
- Sent From My G3
Related
Hi everyone
So I recently got a S2, upgraded it from stock Gingerbread to stock ICS via Kies, then flashed CM9. CM9 was great, but I quickly noticed worse battery drain than that of GB. I sorted out all wakelocks, now facebook is the top one in better battery stats list and it's only 10mins in a day so I don't think that's a problem. When charging, vbus_present shows up and keeps the phone from sleeping, but that's a normal thing when the phone is plugged, right? CPUspy shows the phone is in deep sleep the majority of time I don't use it, so I assume I have no wakelock problem.
But even then, the battery still seems a bit bad. When in deep sleep with wifi and mobile data off, it would lose around 1.5% per hour; and with moderate/high use (internet with wifi or gaming), I'd be lucky to have it last 3 hours. Charging to 100% from zero takes about 3 hours.
I also tried recalibrating the battery through BC, but haven't noticed too much of a difference.
Recently I found a guide on disabling fast dormancy via the build.prop file. Still waiting for results though.
So, my questions
1, My battery usage seems normal, doesn't it? 1.5% per deep sleep hour is acceptable I guess, but 3 hours of usage seems a bit short. Too short.
2, What effects does fast dormancy have?
1) Totally unacceptable. Mine lasts at least 7-8 hours with high use..
Does your phone heat up while the heavy use ???
What brightness level do you use for the display ???
How many apps do you have that can gain internet access ???
2) By default, the Samsung Galaxy S II has Fast Dormancy support enabled. One of the goals of Fast Dormancy is to increase the battery life of a device, by limiting the amount of signaling between the phone and the cell network. But, when Fast Dormancy it is not enabled in the network and is enabled on the phone it ironically works the other way around, and actually drains more battery than before.
Luckily, Fast Dormancy can be disabled on the phone. For the Galaxy S II, do the following:
Dial *#9900#
Press “Disable Fast Dormancy“
Press “Exit“.
Easy as that!
Thanks for the suggestion I have brightness manual and at around 20%. Wifi is disabled when not used, and mobile data is always turned off unless I need it, so basically apps only get internet access when I want them to. I have also disabled sync for both google and facebook, but fb still pushes notifications to me while it's connected. Is that a major battery drain, and if yes, how to disable it?
Anyways, facebook, instagram, youtube are the only apps than can access the internet. No messengers or anything that may keep a wakelock.
My phone doesn't heat up during normal use, maybe a bit when I do some gaming (Max Payne?)
Also, *#9900# doesn't do anything on my phone. It doesn't bring up a menu or anything like that.
Bump. Guys?
Delivered using Nyan Cat's rainbow powers.
Install BetterBatteryStats (search for it on here/Google Play), might help you nail what's causing the drain.
Yes I did, as said in my original post. After a night the highest wakelock are just around 10 minutes, and that one was facebook. Uninstalling it however had no effect.
Delivered using Nyan Cat's rainbow powers.
Thinking logically, there's got to be something else in those stats (partial wakelocks in particular) that's causing that drain. There's no way having fast dormancy enabled/disabled is either going to cause/fix the drain you've mentioned getting '3 hours of usage'; (I can get 5 & a bit hours screen on with CM9 & variable usage/mostly 'moderate' use) given everything else you say you've tried.
Post BBS logs here if you want someone to have a look.
Edit to add - Also post a screenshot of the 2nd screen in settings/battery, the one that has history 'details' at the top, with the 'mobile network signal' bar underneath the main battery graph.
Here you go: pastebin.com/1UwicChJ
I just registered half a day ago and don't have enough posts yet to paste links, so sorry the phone was only on battery for nearly 2 hours with some light browsing and facebook, but I hope it works.
Anyway, I looked through my running processes, and dsp manager is the only non-OS process running, besides facebook. I got CM9 so it came by default. Could dspmanager be the culprit?
Delivered using Nyan Cat's rainbow powers.
It's a new phone he's got there and I doubt it could be anything battery related itself.
I'm using CM9 nightlies and I get around 9 hours moderate use. It has been said though that a lot of these CM9 builds have battery drain and heat issues.
I use Juicedefender to help with the battery life which seems to work.
Sent from my GT-I9100 using Tapatalk 2
MistahBungle said:
Edit to add - Also post a screenshot of the 2nd screen in settings/battery, the one that has history 'details' at the top, with the 'mobile network signal' bar underneath the main battery graph.
Click to expand...
Click to collapse
About 1/3 of this time was on wifi browsing. The drop is much more drastic if I play games.
Delivered using Nyan Cat's rainbow powers.
A couple of observations. There's nothing that stands right out in the BBS log. The other one is, looking at that graph you've lost ~15% over a bit under 2 hrs. The screen has been on most of the time the phone has been awake (confirmed by the BBS log) if you look at the respective bars. You've also been using WiFi for most of the time the screen has been on/phone has been awake.
Roughly speaking, going by the screenshot, you'd get ~5hrs+/- screen on time if you kept using the phone in the same way you had during that just under 2 hrs, and this is pretty much normal. I haven't had drain issues for ages, so I double checked my details on the 2nd screen of settings/battery to make sure CM9 is reporting these details accurately (screenshot attached). Certainly in my case, this screenshot reflects what my phone had been doing for the just under 5 hrs it had been off charge/since last reboot; that is, >90% of the time in idle/deep sleep. So it probably isn't CM9 reporting these details inaccurately in your case either.
The BBS log & screenshot don't illustrate the problem you talked about in your OP. Now, if I had to take a stab in the dark at what's causing problems when you do have them (and FWIW, I do believe you're having the problems you mentioned in your OP at times), in the absence of any other info, maybe your WiFi router is constantly sending the phone packets (what's been referred to as a 'dirty router' on here before) when you're connected to WiFi & not actually using it. This scenario has been known to cause relatively high levels of drain.
So to be honest with you, based on that screenshot & the BBS log, I'm not really seeing a problem.
Now, if you want to post the same again when you actually have a problem with drain similar to what you described in your OP, happy to have a look at them. But for that ~2hrs covered by the BBS log & screenshot you posted, that's pretty much normal.
MistahBungle said:
A couple of observations. There's nothing that stands right out in the BBS log. The other one is, looking at that graph you've lost ~15% over a bit under 2 hrs. The screen has been on most of the time the phone has been awake (confirmed by the BBS log) if you look at the respective bars. You've also been using WiFi for most of the time the screen has been on/phone has been awake.
Roughly speaking, going by the screenshot, you'd get ~5hrs+/- screen on time if you kept using the phone in the same way you had during that just under 2 hrs, and this is pretty much normal. I haven't had drain issues for ages, so I double checked my details on the 2nd screen of settings/battery to make sure CM9 is reporting these details accurately (screenshot attached). Certainly in my case, this screenshot reflects what my phone had been doing for the just under 5 hrs it had been off charge/since last reboot; that is, >90% of the time in idle/deep sleep. So it probably isn't CM9 reporting these details inaccurately in your case either.
The BBS log & screenshot don't illustrate the problem you talked about in your OP. Now, if I had to take a stab in the dark at what's causing problems when you do have them (and FWIW, I do believe you're having the problems you mentioned in your OP at times), in the absence of any other info, maybe your WiFi router is constantly sending the phone packets (what's been referred to as a 'dirty router' on here before) when you're connected to WiFi & not actually using it. This scenario has been known to cause relatively high levels of drain.
So to be honest with you, based on that screenshot & the BBS log, I'm not really seeing a problem.
Now, if you want to post the same again when you actually have a problem with drain similar to what you described in your OP, happy to have a look at them. But for that ~2hrs covered by the BBS log & screenshot you posted, that's pretty much normal.
Click to expand...
Click to collapse
Okay, much appreciated so I guess I'll take it from your reply that 5 hours with wifi browsing isn't too bad. Seems okay, but I still find it a bit strange that (in my case) wifi browsing uses just as much battery as games do. I always thought it was a light activity!
Or maybe it wasn't the battery that had a problem, but that I set my expectations a bit too high. I came to this S2 from a BlackBerry 9700, whose battery would last half a week with very frequent use. But anyway, I just got this phone for a week, so I consider myself a pretty heavy user. Probably when I get familiar with it, I won't feel the need to play with it every five minutes and battery will last a bit longer then! xD
Nah. Anything with screen on is far from 'light activity'. Screen consumes far & away the most juice. In saying that, I've seen some people on here say they can get 8-9 hrs screen on with 2000mAh battery. How they do it I have absolutely no idea.
But if yeah, 5 hrs with the screen on most of the time whether browsing or playing games (games in particular are very CPU/GPU intensive & thus use a lot of zzzzs; unless they're really basic games like chess or similar), or anything else isn't too bad. Can you do better ? Obviously, if people say they can get 8-9 hrs. But it's not a matter of doing A, B & C and you'll magically end up with massive screen on times. Every phone is setup & used differently, and getting the absolute max out of every charge takes a lot of trial & error and experimenting with settings/setup.
There are tons of threads about the subject on here if you feel like going down that path. For me, I'm happy with the battery life I get these days because you can really obsess over it & spend a lot of time stressing over it/trying to maximise it for often very little gain. I'd rather simply use my phone a lot during the day & charge it at night.
Yeah Crackberries are like Japanese cars, they can run on fumes pretty much ;-) Having a dual core processor, a decent GPU & a huge screen kinda changes things.
There is one thing you can do fairly easily tho. And that's to make sure the phone spends as much time as possible in deep sleep when you're not using it. That will ensure that you have enough juice to get you by when you do want to use it. Simple ways to help achieve that is to turn off data/WiFi completely when you're not using it (tho many people don't like to do this for different reasons; which is perfectly OK if you're happy to live with the resultant drain), and make sure you've got no apps that are doing things they shouldn't be doing (like syncing, for example) while the phone should be sleeping. Again, there are lots of threads about same if you ever feel like a bit of light reading ;-)
So yeah, if you do find you experience drain that's not normal/outside the usual pattern you have, definitely post details & people can have a look for you. And as you said, you'll get to know what really is normal with regard to drain & so on is as you use the phone more (I tended to use it constantly for that first couple of weeks as well).
nyancatland said:
Okay, much appreciated so I guess I'll take it from your reply that 5 hours with wifi browsing isn't too bad. Seems okay, but I still find it a bit strange that (in my case) wifi browsing uses just as much battery as games do. I always thought it was a light activity!
Or maybe it wasn't the battery that had a problem, but that I set my expectations a bit too high. I came to this S2 from a BlackBerry 9700, whose battery would last half a week with very frequent use. But anyway, I just got this phone for a week, so I consider myself a pretty heavy user. Probably when I get familiar with it, I won't feel the need to play with it every five minutes and battery will last a bit longer then! xD
Click to expand...
Click to collapse
Already took such measures. Wakelocks killed my battery over my first night with the phone, and I woke up after 7 hours to find a ~50% battery completely empty. Now things are alright, I clear CPUSpy stats before I sleep and wake up to around 95% of deep sleep time. Overnight drain varies between 5 and 10%.
And yes, yes you are right. Maybe I should stop going nuts. I'm checking BBS and CPUSpy every hour, reading every XDA thread on battery, and calculating my battery drainage every morning I wake up :laugh::laugh::laugh:
Re: dirty/'noisy' WiFi networks, have a look at this post as an example of what I was talking about above.
MistahBungle said:
Re: dirty/'noisy' WiFi networks, have a look at this post as an example of what I was talking about above.
Click to expand...
Click to collapse
Umm...so I just woke up, and noticed a wakelock in the kernel category. It was PowerManagerService, and it occupied around half an hour. Overnight, aftet I've slept 10 hours (got a day off ), my battery came from 24% down to 13%. That's a rate of roughly 1% per hour. Is that normal? And also, what is that PowetManagerService wakelock?
Delivered using Nyan Cat's rainbow powers.
Fantastic. Looks like you got your 10 posts That tip is about as useful as "don't plant cauliflowers in concrete".
trojans63 said:
Turn off wifi and dont play games and your batter will last longer
Click to expand...
Click to collapse
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.
Hey guys, I am having a problem with my Amaze, more specifically, the battery is dying absolutely WAY to quickly. For example, yesterday morning, after unplugging my fully charged phone, I dropped it straight into my pocket, and maybe looked at it twice the entire day. When I pull it it at the end of the day, the battery is red, with 8% left. If I were to be using it, the battery would last about 30 minutes on a full charge, most likely. I've also noticed that the phone is really hot, even in my pocket. If it helps, I am on ICS and have been using it since it was leaked in April, however, this problem is new (about 2 days ago is when it first started), as I usually get about 8-10 hours with moderate usage. Can you guys please help me? Thanks!
Well if it just started happening recently, and you haven't made any changes, then the battery may just be going bad... If that's the case, you can call HTC and they will send you one free replacement.
sent from my NRGized Amaze,
powered by faux kernel v.10
could be just the battery.. but if you don't mind me asking - how long have you owned the device? I suggest you dl JuiceDefender from the playstore and see if that helps - Definitely helps my device get through the day with moderate use and one time charge every 1 1/4 a day but this could vary on owners usage. Also, check your settings to conserve battery life such as turning off wifi, gps, auto syncs on your fb, gmail etc. and adjust your brightness to the lowest if possible and OH... less widgets and windows > less power that the battery consumes. Hope that helps!
b33j7030 said:
could be just the battery.. but if you don't mind me asking - how long have you owned the device? I suggest you dl JuiceDefender from the playstore and see if that helps - Definitely helps my device get through the day with moderate use and one time charge every 1 1/4 a day but this could vary on owners usage. Also, check your settings to conserve battery life such as turning off wifi, gps, auto syncs on your fb, gmail etc. and adjust your brightness to the lowest if possible and OH... less widgets and windows > less power that the battery consumes. Hope that helps!
Click to expand...
Click to collapse
Like I said, this just started happening. I didn't just decide to leave all my wifi and GPS and Bluetooth on all day. Also, to answer your question, I've had it since the beginning of the year. I think it's just the battery. I'll call HTC and report back.
cool.. i'm hoping its just the battery.
b33j7030 said:
cool.. i'm hoping its just the battery.
Click to expand...
Click to collapse
Thanks. The overheating does concern me a bit, however.
HarryHyper said:
Thanks. The overheating does concern me a bit, however.
Click to expand...
Click to collapse
you're not alone in that dept but its highly tolerable... look on the bright side.. least you'll have a pocket warmer during WINTER lol
b33j7030 said:
you're not alone in that dept but its highly tolerable... look on the bright side.. least you'll have a pocket warmer during WINTER lol
Click to expand...
Click to collapse
LOL.
Alright guys, looks like it solved itself. Interesting...
I usually only get 6-8 hours on my battery, and its been like that from the beginning. is there something wrong with my phone then?
erkk_69 said:
I usually only get 6-8 hours on my battery, and its been like that from the beginning. is there something wrong with my phone then?
Click to expand...
Click to collapse
Nope, battery life isn't that great with this phone, depending on how much you use your phone and what all you use it for you will get any where from 6-14 hrs + or - some. Also your Rom and kernel will make a difference..
sent from my NRGized Amaze,
powered by faux kernel v.10
I find usually its the user when it comes to battery I get roughly 20 hours with regular use
Sent from my HTC_Amaze_4G using xda premium
HarryHyper said:
Alright guys, looks like it solved itself. Interesting...
Click to expand...
Click to collapse
Nice!... Glad to hear
This happens to me from time to time, and the phone is ALWAYS hot when this happens.
What I've come to discover that it's usually something that' activating the phone while asleep.
The phone is hot, because the processor is being used. That's why the battery is completely dead so quickly, something is pulling it out of deep sleep and causing it to run full bore. The key sign is the phone is hot.
I recommend you get an app that lets you see wakelocks, and what's keeping the phone awake etc (I use GSAM battery monitor) Whenever I notice my phone becoming hot for no apparent reason, I know for a FACT that my battery will be dead in a matter of hours. Lately it has been "Android System" that's the culprit, and I can't quite nail down what is doing it, but it's very random and not much of a problem because I do a reboot and things are back to normal.
First, try to reboot your phone. Get system tuner and see what processes are using the processor when the phone is hot (make sure you show ALL processes, even the default excluded ones). Check the wakelocks. Get battery monitor and check the mA usage (it keeps a running history). When my phone is running optimally, I have a mA drain of around 70-90mA when screen off/deep sleep, and it should maintain this type of drain... when my phone is becoming hot for no reason, I see numbers anywhere from 300-600mA drain for no apparent reason. A lot of the time there was an APP that was offending, so I would first check that. Like I said though lately it has been "Android System" and it's kind of hard to nail that down, but it's so random.
When my phone is cool to the touch most of the time, I know it's running optimally because it's achieving deep sleep. I've found a lot of it has to do with what you had running before you turn the screen off. A reboot ALWAYS fixes it for me. If you can't seem to nail down the offending app, do a full reset back to stock and you should notice that your phone runs very very cool when the screen is off and it's sleeping. I usually get anywhere from 24hrs-2 days of moderate use with the screen off governor set to conservative, and maximum clock for screen off ~600mHZ. I use interactive governor for screen on, but that's for responsiveness and you'll probably have better luck with ondemand for battery life. YOu can set these in System Tuner.
Just remember, if the phone is HOT, it's using energy. If it's hot, something, somewhere, is causing the processor to run at a high clock frequency. If the phone is HOT after being in your pocket/screen off for a good amount of time, something is definitely wrong/rogue app. The phone should never be hot returning from deep sleep. I bet if you check your default battery monitor (The android one) you'll notice that the bar for AWAKE is probably almost solid blue, something is preventing it from going into deep sleep. If I notice my phone is hot when I take it out of my pocket, I immediately know that something isn't right. This should NOT happen.
sportsstar89 said:
I find usually its the user when it comes to battery I get roughly 20 hours with regular use
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I'm just past my 9th day of using my Amaze 4G.... so far, if I turn off data and turn off autosync, my drain per hour goes below 1%/hour... so i could get >50 hour idle battery life + 4 hours screen usage
with data on and autosync off, maybe 2%/hour -> this translates to ~ 20hour idle battery life + 4 hour screen usage
with data on and autosync on, maybe 4%/hour -> 10 hour idle battery + 4 hour screen usage
I have only calendar widget on my home page, only Google Accounts on auto-sync (2 mail account, 1 contact, 1 calendar)....
EnergyROM 6.21.2012 ICS 4.0.3, faux kernel 0.07, ankor battery
ericdjobs said:
This happens to me from time to time, and the phone is ALWAYS hot when this happens.
What I've come to discover that it's usually something that' activating the phone while asleep.
The phone is hot, because the processor is being used. That's why the battery is completely dead so quickly, something is pulling it out of deep sleep and causing it to run full bore. The key sign is the phone is hot.
I recommend you get an app that lets you see wakelocks, and what's keeping the phone awake etc (I use GSAM battery monitor) Whenever I notice my phone becoming hot for no apparent reason, I know for a FACT that my battery will be dead in a matter of hours. Lately it has been "Android System" that's the culprit, and I can't quite nail down what is doing it, but it's very random and not much of a problem because I do a reboot and things are back to normal.
First, try to reboot your phone. Get system tuner and see what processes are using the processor when the phone is hot (make sure you show ALL processes, even the default excluded ones). Check the wakelocks. Get battery monitor and check the mA usage (it keeps a running history). When my phone is running optimally, I have a mA drain of around 70-90mA when screen off/deep sleep, and it should maintain this type of drain... when my phone is becoming hot for no reason, I see numbers anywhere from 300-600mA drain for no apparent reason. A lot of the time there was an APP that was offending, so I would first check that. Like I said though lately it has been "Android System" and it's kind of hard to nail that down, but it's so random.
When my phone is cool to the touch most of the time, I know it's running optimally because it's achieving deep sleep. I've found a lot of it has to do with what you had running before you turn the screen off. A reboot ALWAYS fixes it for me. If you can't seem to nail down the offending app, do a full reset back to stock and you should notice that your phone runs very very cool when the screen is off and it's sleeping. I usually get anywhere from 24hrs-2 days of moderate use with the screen off governor set to conservative, and maximum clock for screen off ~600mHZ. I use interactive governor for screen on, but that's for responsiveness and you'll probably have better luck with ondemand for battery life. YOu can set these in System Tuner.
Just remember, if the phone is HOT, it's using energy. If it's hot, something, somewhere, is causing the processor to run at a high clock frequency. If the phone is HOT after being in your pocket/screen off for a good amount of time, something is definitely wrong/rogue app. The phone should never be hot returning from deep sleep. I bet if you check your default battery monitor (The android one) you'll notice that the bar for AWAKE is probably almost solid blue, something is preventing it from going into deep sleep. If I notice my phone is hot when I take it out of my pocket, I immediately know that something isn't right. This should NOT happen.
Click to expand...
Click to collapse
what program do you use to measure battery drain? I use Battery Monitor Widget, but it's not giving me an accurate answer (lets say I had the phone on idle w/o data/sync... the available % is stable over 5 hours (~1% loss per hour), but the current usage says at least -100mAh)
for me, the idle battery drain (apps autosyncing/using data) is the problem
I see my device properly going to sleep (deep sleep is the majority of the usage, not too many wakelocks/processes.....)
with data off and sync off, idle battery usage goes to a minimum
paperWastage said:
I'm just past my 9th day of using my Amaze 4G.... so far, if I turn off data and turn off autosync, my drain per hour goes below 1%/hour... so i could get >50 hour idle battery life + 4 hours screen usage
with data on and autosync off, maybe 2%/hour -> this translates to ~ 20hour idle battery life + 4 hour screen usage
with data on and autosync on, maybe 4%/hour -> 10 hour idle battery + 4 hour screen usage
I have only calendar widget on my home page, only Google Accounts on auto-sync (2 mail account, 1 contact, 1 calendar)....
EnergyROM 6.21.2012 ICS 4.0.3, faux kernel 0.07, ankor battery
what program do you use to measure battery drain? I use Battery Monitor Widget, but it's not giving me an accurate answer (lets say I had the phone on idle w/o data/sync... the available % is stable over 5 hours (~1% loss per hour), but the current usage says at least -100mAh)
for me, the idle battery drain (apps autosyncing/using data) is the problem
I see my device properly going to sleep (deep sleep is the majority of the usage, not too many wakelocks/processes.....)
with data off and sync off, idle battery usage goes to a minimum
Click to expand...
Click to collapse
I use battery monitor widget to measure drain.. as far as accuracy, I'm not sure? I don't know if it's EXACT but it seems to be a pretty good indicator of drain. When in deep sleep the phone usually measures anywhere from 70~mA-120mA. Usually it stays below 100. Before I changed the screen off governor / max freq (screen off) it was almost always 100+. Screen off governor is conservative with a max freq of ~600MHz.
I have no idea how exact it is, but when it's reporting ~300mA, my battery is definitely draining much faster.. and when it's reporting 500-900mA~ my battery is draining incredibly fast, so it at least seems to be a solid indicator of current usage.
ericdjobs said:
I use battery monitor widget to measure drain.. as far as accuracy, I'm not sure? I don't know if it's EXACT but it seems to be a pretty good indicator of drain. When in deep sleep the phone usually measures anywhere from 70~mA-120mA. Usually it stays below 100. Before I changed the screen off governor / max freq (screen off) it was almost always 100+. Screen off governor is conservative with a max freq of ~600MHz.
I have no idea how exact it is, but when it's reporting ~300mA, my battery is definitely draining much faster.. and when it's reporting 500-900mA~ my battery is draining incredibly fast, so it at least seems to be a solid indicator of current usage.
Click to expand...
Click to collapse
On my previous phone (LG Optimus T / Optimus One/ P509, CM9 ICS ROM), Battery Monitor Widget reports more accurate readings (idle with data off= -2mA or -20mA<dont remember>, accurately representing that 1% of battery would last at least 2 hours)
Phone with the new kernel (KozmiK Ruby -0.5a) still goes battery drain crazy (even with Juice Defender installed now).... I hit 10%, then got fed up, turned off data... then the phone slowly sipped battery for the next 3 hours going down only 1%.... sigh
I think Facebook Messenger is the data hogger in my case, since I do use it often... will try a new ROM build without logging onto facebook messenger, see how it goes
paperWastage said:
I'm just past my 9th day of using my Amaze 4G.... so far, if I turn off data and turn off autosync, my drain per hour goes below 1%/hour... so i could get >50 hour idle battery life + 4 hours screen usage
with data on and autosync off, maybe 2%/hour -> this translates to ~ 20hour idle battery life + 4 hour screen usage
with data on and autosync on, maybe 4%/hour -> 10 hour idle battery + 4 hour screen usage
I have only calendar widget on my home page, only Google Accounts on auto-sync (2 mail account, 1 contact, 1 calendar)....
EnergyROM 6.21.2012 ICS 4.0.3, faux kernel 0.07, ankor battery
Click to expand...
Click to collapse
What you said is true, at least for data on - autosync on. My battery last around 10 hours idle + 3.5 - 4 hours on screen usage. It seems that autosync eats a lot of battery. Will try to turn that monster off and see how much it will improve. I have bad habit to push refresh button on gmail/facebook widget, even with autosync on,
I used to get 14-16 hours. Now my battery won't last more than 6 hours. I gotta replace my Anker
Sent From My HTC Amaze 4G via Someone's Room
Most recently I got 1 day and five hours with a fair amount of use by using faux 011 kernel and using CPU editor script to set it to battery saving profile. I'm at 45% right now with fairly heavy use after over 18 hours.
Battery life is totally under your control, it takes some work to get it where you want it.. but you also have the option of buying a bigger anker battery with external charger for $20 and carrying that spare battery, and simply not giving a damn.
Just saying, battery doesn't have to matter for a very small price and a little space to carry the spare battery in your pocket.
Sent from my HTC_Amaze_4G using xda app-developers app
refer to post #6 and onwards.
Theshawty said:
So, it seems Samsung phones in general have a 1 to 2 second wake-up lag and mostly it doesn't seem to matter if you run on the stock firmware or on a custom firmware based on AOSP.
Why do most/all Samsung devices have this and does it haunt them in general? Galaxy Nexus didn't have it, yet it's made by Samsung? (though with Google's standards)
Click to expand...
Click to collapse
It's waking up from deep sleep and that takes 1-2 sec. Widgetlocker seems to be little quicker than the original stock locker.
Casanoaa said:
It's waking up from deep sleep and that takes 1-2 sec. Widgetlocker seems to be little quicker than the original stock locker.
Click to expand...
Click to collapse
Why is this only plaguing Samsung devices but not Samsung-Google devices and all other android devices?
Are you saying a different CPU governor and a slightly higher minimum frequency could help it?
Are you saying a different CPU governor and a slightly higher minimum frequency could help it?
Click to expand...
Click to collapse
Actually he's saying that another lockscreen than the default one should be faster since less extravagant.
All Android devices have a lag when waking up from deep sleep, exactly as do other devices such as computers.
Deep sleep means the system is actually in a sort of standby, the kernel and all processes have to resume normal operation and the CPU being clocked up before you can use it again.
You could prevent deep-sleep but that would drain your battery since at least one cpu-core needs to be online 24/7 in that case.
d4fseeker said:
Actually he's saying that another lockscreen than the default one should be faster since less extravagant.
All Android devices have a lag when waking up from deep sleep, exactly as do other devices such as computers.
Deep sleep means the system is actually in a sort of standby, the kernel and all processes have to resume normal operation and the CPU being clocked up before you can use it again.
You could prevent deep-sleep but that would drain your battery since at least one cpu-core needs to be online 24/7 in that case.
Click to expand...
Click to collapse
Would it have anything to do with idle+lpa (deep idle)? I don't think that the nexuses have deep idle activated in the kernel.
Sent from my GT-I9300 using xda premium
Let's say if one with normal to less use get's around 2 days of battery time, and with heavier use around 1 day 15 hours both with deep idle activated. How much less would this be with deep idle (IDLE+LPA) completely off?
I mean, the Galaxy Nexus has a lower battery mAh than the S3, so theoretically the battery should still last a lot longer than 1 day with medium-heavy usage? Plus, I don't mind charging every night.
I am currently running CM10.
Theshawty said:
Let's say if one with normal to less use get's around 2 days of battery time, and with heavier use around 1 day 15 hours both with deep idle activated. How much less would this be with deep idle (IDLE+LPA) completely off?
I mean, the Galaxy Nexus has a lower battery mAh than the S3, so theoretically the battery should still last a lot longer than 1 day with medium-heavy usage? Plus, I don't mind charging every night.
I am currently running CM10.
Click to expand...
Click to collapse
Even underclocked and undervolted and tweaked getting a full 24 hours of actual medium to heavy use (not idle, since most of the uptime on a device is idle) is pushing it. If you set deep sleep/idle off your phone would die in a day~ without even touching it, would be like your using your phone with light use I suppose. The google phones do this also, every android does.
Just a guesstimate, those features are there for a reason. Not only will the device drain battery faster but its will also cause more wear and tear on the hardware.
Cdjones187 said:
Even underclocked and undervolted and tweaked getting a full 24 hours of actual medium to heavy use (not idle, since most of the uptime on a device is idle) is pushing it. If you set deep sleep/idle off your phone would die in less than a day without even touching it. The google phones do this also, every android does.
Click to expand...
Click to collapse
First of all that's not true.
It wouldn't die in less than a day without touching it.
I can leave my galaxy nexus and not touch it and it will stay on for over 3 days, and they don't have deep idle.
He isn't trying to remove deep sleep, he wants to disable deep idle.
Different thing completely.
Sent from my GT-I9300 using xda premium
nodstuff said:
First of all that's not true.
It wouldn't die in less than a day without touching it.
I can leave my galaxy nexus and not touch it and it will stay on for over 3 days, and they don't have deep idle.
He isn't trying to remove deep sleep, he wants to disable deep idle.
Different thing completely.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Exactly! None of the Google devices as far as I know have deep idle enabled (but deep sleep), and the battery life was more than decent. I could get over a day of medium use, and approx 18h of heavy usage but I don't mind charging every night. I've been charging my phones every night since many years back, so it's a habit of mine. I'm just happy if it gets me 8h.
I'm having this issue of my phone not sleeping when the phone is off. I checked kernel wakelocks and the number 1 culprit is Power Manager Service. Anybody have any idea what this is. A distant second is wlan_rx_wake but I'm not too worried about this.
The devs are working on it. If you aren't on the latest CM9 build then you should update.
GrayTheWolf said:
The devs are working on it. If you aren't on the latest CM9 build then you should update.
Click to expand...
Click to collapse
I'm actually not on AOSP stuff. I'm on one of Neo's roms.
Edit: I just ran a test and for 34 minutes the phone slept for 33 of them. Even though the phone lost 4 percent of battery in that time. I see people saying they have crazy good battery drain rates (like .25%/hr). I thought i would get better life but I guess thats just the way it is.
jdm2008315 said:
I'm actually not on AOSP stuff. I'm on one of Neo's roms.
Edit: I just ran a test and for 34 minutes the phone slept for 33 of them. Even though the phone lost 4 percent of battery in that time. I see people saying they have crazy good battery drain rates (like .25%/hr). I thought i would get better life but I guess thats just the way it is.
Click to expand...
Click to collapse
that rate is based on usage. keeping apps from starting. keeping apps running in foreground all the time. lots of frozen unnecessary apps. screen brightness between 10-20%. betterbatterystats monitors wakelocks
dyetheskin said:
that rate is based on usage. keeping apps from starting. keeping apps running in foreground all the time. lots of frozen unnecessary apps. screen brightness between 10-20%. betterbatterystats monitors wakelocks
Click to expand...
Click to collapse
When saying .25% per hour I was talking about during sleep but I get 3-4% during sleep. I am going to try and wipe everything and start from scratch. But if my phone is sleeping >90% of the time when the screen is off, there's not much I can do to improve battery drain during sleep no(app wise), and screen brightness won't help at this level cause it's when the screen is off?
have to watch for partial wakelocks or any wakelocks. apps automatically starting when not needed or still running will reduce your amount of deep sleep. use betterbatterystats to monitor usage while it's off