Posting this in general since I figure it's not phone specific but for reference, I have a Samsung Vibrant running ICS.
I've been having an issue with the phone refusing to go into deep sleep. I suspect that it's a misbehaving app as it'll go into deep sleep after a reboot, for perhaps 2-8 hours, after this, it'll default to the set minimum voltage and refuse to go any lower.
What I'm looking for is a way to track down and slay this little battery eating monstrosity. I have this app to peek at the inner magic but to be perfectly blunt, I have no idea what I'm doing. Hoping someone can provide a little troubleshooting device. Going from 100% battery to 30% in 5 hours sucks.
I use "batteryBatteryStats" to show what applications are causing wakelocks, really helped me out a few months ago.
https://market.android.com/details?id=com.asksven.betterbatterystats&hl=en
I left my Note overnight to test the battery drain and lost 40%. I used CPU spy to see what was happening and the phone never really went into Deep Sleep. Android OS was the biggest battery drain.
What's the best way/app to see what is keeping my phone from going into deep sleep? I am not rooted.
Please try a search you will get lots of good answers.
http://forum.xda-developers.com/showthread.php?t=1516565
And get Better Battery Stats to find out what is triggering you out of sleep if the above thread does not help.
Sent from my SGH-I897 using XDA
jpeg42 said:
Please try a search you will get lots of good answers.
http://forum.xda-developers.com/showthread.php?t=1516565
And get Better Battery Stats to find out what is triggering you out of sleep if the above thread does not help.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I don't need to be told to do a search. That's the first thing I do before I post a thread. The subject of that particular thread didn't seem to apply.
factory reset should take care of andriod os eating battery more then screen.dont install any app for few hours.only install cpu spy.
Thanks for the suggestion, but I'd rather not have to do a factory reset every time a rogue app is draining my battery. Reinstalling everything all over again is a pain (not rooted, so Titanium backup is not an option) and that's like telling a user to reinstall Windows every time they see a little performance degredation.
I'm pretty sure there has to be a better way. I'll try betterbatterystats and see if it can help me narrow down the problem.
yeh i have an unrelated problem, will resetting device fixes it, but definately not a viable solution
but on topic in better battery stats look under 'partial wake locks',and see what programs are listed first (and the time spent on the apps)
that should normally tell you whats making the phone not got to sleep
u not gone find anything with battery stats.one of ur app is causing this issue.
u can give battery stats a try.when u.have a virus in windows, dont have have to do full recovery instead buying a virus program and trying to fix it.
greyhulk please try that solution Jpeg42 linked to.
Thursday I was down to 30% when I left work(10 hours). Friday I turned on the screen before unplugging and I was at 25% with 2 hours of screen on time and 21 hours since I unplugged.
Unplugging the phone with the screen off seems to prevent deep sleep. Give it a try.
If all else fails, it might be the battery itself. Hardware issue.
-On another NOTE, Samsung goes 5.3"
mintu123 said:
u not gone find anything with battery stats.one of ur app is causing this issue.
u can give battery stats a try.when u.have a virus in windows, dont have have to do full recovery instead buying a virus program and trying to fix it.
Click to expand...
Click to collapse
Your post is virtually incoherent, however, I will say you seem to be saying BetterBatteryStats won't help, and it most certainly will. What there is no need for is a factory reset, that's like nuking a planet to kill a flea.
Pops_G said:
greyhulk please try that solution Jpeg42 linked to.
Thursday I was down to 30% when I left work(10 hours). Friday I turned on the screen before unplugging and I was at 25% with 2 hours of screen on time and 21 hours since I unplugged.
Unplugging the phone with the screen off seems to prevent deep sleep. Give it a try.
Click to expand...
Click to collapse
Yeah, reading the thread over, that's exactly what I did last night: Took it off the charger with the screen off. I skipped over that thread originally because the title lead me to believe that it had to do with battery drain while plugged in.
I'll give it another test tonight and see if that makes a difference.
I just wanted to post my experiences with deep sleep.
I was getting some pretty bad drain, and I couldn't figure out why. Thanks to the search engine and running into this thread, I tried what you all tried here.
I am running Launcher Pro, and I wasn't going to deep sleep at all. Did the trick posted, even rebooted without it plugged in and it still wasn't sleeping at all.
I cleared the defaults and went back to the default launcher. It went to deep sleep just fine. I cleared the defaults again, then set the launcher back to launcher pro. It is now deep sleeping with the launcher pro as the default.
I then put the phone on the charger, woke it up, unlocked it and unplugged it. Its still deep sleeping. Really weird how it acted, and I figured for everyone else's sake in case they run into that issue again, it could be your launcher that is causing the issue.
A reboot with the phone, after the launcher switch, as the launcher pro as the default, resulted in no deep sleep. Launching the stock launcher while LauncherPro is still the default launcher resulted in no deep sleep.
After a reboot, with no default launcher, launching the stock launcher resulted in, it does not deep sleep.
After a reboot with no default launcher, launching LauncherPro, no deep sleep.
Some really goofy stuff going on...
I am using the overclock kernel but I am not overclocking. I installed it to lower the cpu to 192mhz instead of 384mhz.
I noticed that my phone (Lenovo P700i) barely goes into deep sleep. At the minimum, it always runs at 250 mhz.
Is this considered a deep sleep problem even though BetterBatteryStats shows that there don't seem to be any significant wakelocks?
there's two build props that will make your device enter sleep instanly...If you understand how to edit them..you may want to search for deep sleep build prop tweaks..hope this helps..
Does this app can fix the issue: http://forum.xda-developers.com/showthread.php?t=2030696 ?
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.
Hi, I've had quite a few roms on the Vibrant (all JB) and they've all suffered from poor battery life due to a GPS wakelock getting out of control and leaving the phone stuck at 100mhz, unable to go into deep sleep. The wakelock I see mostly is ste-gps-interface. There isn't much out there except a previous post that I made thinking I fixed it (which wasn't the case, I just did something to make it happen more frequently). Interestingly enough too if you google "ste-gps-interface" nearly all the information out there is for the Vibrant. I know there have been GPS issues with this phone and I guess I'm lucky that GPS works at all.
Basically what would happen is that once the wakelock got started, nothing short of a reboot would clear it, and then it would happen maybe only a few hours after rebooting the phone again. Actually turning GPS off is not a solution. I think I even tried to kill the GPS daemon and that was not a solution either. Installing tweaking scripts seemed to trigger it more for me but I couldn't pinpoint any one action - it would just be the case that the longer I had the phone on, with any rom, inevitably the wakelock issue would rear its ugly head. I'm surprised not more people have mentioned it on here, but it could be that they're not aware of it, and just assuming that battery life is a little bad. It's acceptable when idling at 100mhz but I'd never get a full day out of it. I'm about one day and 4 hours now and at 40% with this fix. I have gone about 4 days with this fix and it seems to be holding so I'm fairly confident to say that at least for me it seems to have solved the problem.
Here is what I did. Download the app Greenify. This hibernates apps and services when the screen goes off. Curious to see if this would help my issues, I greenified Maps. This seemed to help a little bit, but the issue popped up again. I then turned Google Now into a user app via Titanium Backup and Greenfied that as well (Greenify won't let you freeze system apps, and it's safe to make google now a user app because it's not an essential process). You can find this app on the market. I have gone over a day today and I have only had 10 mins of the wakelock, opposed to nearly continuous (hours upon hours) of the wakelock, draining the battery. The only drawback I could see is if you depend on services that need maps or google now to be running when the phone is off, like latitude or location history. I imagine too that hibernating this nasty service just helps with battery life in general.
I'm very curious about this fix, because I wonder if it's a bug on Google's end. I've often thought that the location services seem buggy and excessive. This is worth trying just for battery alone. You can verify if you have the wakelock issue by using BetterBatteryStats and looking at kernel wakelocks (will have a ste-gps-interface wakelock going for almost the entire boot time), or even just looking at any CPU state breakdown - if you see only a tiny bit of time in deep sleep and the rest in 100mhz, that could indicate you're experiencing it as well. Please let me know if this helps anyone and thank you to the app developer of Greenify
I've tried to search for an answer but i can't seem to find more info on the subject... Correct me if i'm wrong but as I understand it coalescing makes is so that the wake timers of the greenified apps synchronize (maybe other apps too?). They wake up at the same time, thus keeping the phone awake a shorter period.
I can see how this can save battery but won't it hog available RAM instead? I'm concerned since i have a Galaxy S6 with piss poor RAM-management and kills off apps as soon as ram-usage hits about 80%, which is pretty much all the time.
faldo said:
I've tried to search for an answer but i can't seem to find more info on the subject... Correct me if i'm wrong but as I understand it coalescing makes is so that the wake timers of the greenified apps synchronize (maybe other apps too?). They wake up at the same time, thus keeping the phone awake a shorter period.
I can see how this can save battery but won't it hog available RAM instead? I'm concerned since i have a Galaxy S6 with piss poor RAM-management and kills off apps as soon as ram-usage hits about 80%, which is pretty much all the time.
Click to expand...
Click to collapse
The coalescing and the syncing all happen when the phone is asleep.
tnsmani said:
The coalescing and the syncing all happen when the phone is asleep.
Click to expand...
Click to collapse
Nah, it's not asleep when syncing, the wakelocks keeps it awake the short amount of time it takes to sync. Install Better battery stats and you'll see that it's not asleep
faldo said:
Nah, it's not asleep when syncing, the wakelocks keeps it awake the short amount of time it takes to sync. Install Better battery stats and you'll see that it's not asleep
Click to expand...
Click to collapse
That is true, but what I meant was that the coalescing will happen only when you are not using the phone and so the RAM usage may not be an issue.
If the coalescing and syncing happens when you are using the phone, then it may create a problem but it is not so.
Since it takes place during sleep, albeit the phone wakes up for the syncing, RAM should not be a concern. Have you faced any issue because of this?