Let me preface this by saying I'm not complaning about battery life as 36h is very good. That said, I feel like my phone is awake much longer that it should be. Anyone have any ideas why my Awake time is so much higher than my Screen-on time?
Once again, I'm not complaining but considering my phone was awake almost 5x longer than the screen was on, I feel like I could squeeze some more life out of the phone. I had 1 exchange account @ 15min, 1 gmail on push, no talk/g+, ~2-3 hours off wifi (4g), gps on, bluetooth off, 4.0.4, leanKernel.
When analyzing the wakelocks, I don't see anything that would explain almost 6 hours of extra awake time:
Considering most of this charge I was on wifi, I think I should have been able to achieve more than 1.5h screen-on time. Especially when I see people getting 4-5+ hours on theirs. What could be causing this seemingly excess awake time?
Since those screen shots, I've done another full cycle and here are my results. Same settings as before. It looks as if I did a bit better with the ratio of awake vs screen on, but I still only got ~20 hours. I'll admit, this had much more 4g time and heavier usage.
As you can see it's better, as it was only awake about 3x as much as the screen. You can see where I was at home in the second screenshot (The long bar of wi-fi) and that included me sleeping yet it shows that the phone was consistantly waking up overnight without any usage. Short of "email", I'm not sure what could be causing it. I got MAYBE 3 e-mails overnight.
Signed out of talk/g+/latitude
Location services was NOT disabled in either set of screenshots. Disabled it and charging now. Maybe that will help?
Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely
armanatz said:
Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely
Click to expand...
Click to collapse
I have attached all the wakelocks to the previous two posts. I didn't attach CPU spy but I did check it every time. Usually it's between 60-80% but most often it's >70% in deep sleep.
Just did a fresh wipe with a app restore using the market. Location services have been disabled. I have uninstalled all gMaps updates and disabled the app. Is this good enough? Should I convert to user and uninstall using TB?
Just wanted to chime in and say I'm seeing a very similar profile to what you posted. And I'm not entirely sure, but I think this started when I flashed this ROM. What I feel like I'm seeing is that active use of the phone seems to be more of a drain than it used to, but I'm not sure how much of that would be placebo (i.e. remembering when I first got the phone around the holidays and there were a lot of relaxed days at home with constant wifi).
But right now I'm seeing 5.5 hours of awake time and 1 hour of screen on time, with 27% remaining. Total time is 42 hours, which seems to round everything out to a decent battery life, but again, 1 hour of use for 70% of the battery seems lower than what I remember. Not sure if a vote for seeing the same behavior is one for this being normal or us both having the problem, but I can try to post screenshots/more detailed info later if it would help.
This is on the above linked rom with stock kernel, 4.0.4 radios.
That's the same ROM I'm using and I agree, 70% usage for 1h screen time seems too much. I've seen people get over 2.5h screen on time on pure 3/4g
I'm going to see if disabling maps and location services help. Will report back.
I would be interested to see any SS you have, might help.
Sent from my Galaxy Nexus using XDA App
This is after a fresh wipe, fresh kernel install, no maps, no g+, no gTalk, no GPS, no location services, just gmail and 1 exchange @ 15 minutes
Any advice as to what's going on would be very helpful. Thanks in advance.
I also have a problem with wake-locks.
Since phone is relatively new ~2weeks its still stock 4.0.2 GSM. After some time my battery life fell and thanks to XDA i think i found the problem Google backup.
I disabled Google backup to see if i get the same awake time tomorrow.
If the problem doesn't go away, is it possible to resolve this problem without factory reset of the phone?
Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?
Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.
JoeSyr said:
Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?
Click to expand...
Click to collapse
This looks to me like some sort of Maps issue. Try to uninstall/disable maps and see if it goes away. Looks like it's stuck trying to locate you with maps somehow based on those wakelock names.
Catoss said:
Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.
Click to expand...
Click to collapse
Hopefully the factory reset will fix it, that is an odd problem.
It seems to me like my problem was the version of leankernel I was using. I went from 10.0exp2 to 2.01exp2 and it's much much better
Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.
Timdor said:
Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.
Click to expand...
Click to collapse
mine is opposite of that, i standby fine on data but terribly on wifi. im guessing that is background syncing. i just have to figure out what is doing it
i have my wifi set to never too for better battery life. It seems counter intuitive, but wifi is better on power than 3g/4g. So preventing the phone from leaving wifi back to cellular is better for battery. All my phones have been like this.
yeah thats what i thought it does but mine drains faster on wifi...i leave it on cause i barely get signal in my room an if i sit on 3g it just takes a long time to do anything
What type of drain do you get over 3g vs wifi?
Yesterday I was playing around on 3g all day and I was seeing an average of 6%/hr. My phone is consistantly awake 20-25% of the time according to betterbatterstats. Screen on will always be far less than half of my awake time. Wifi drains around 1%/hr
I did a wipe of my 4.0.4 install and flashed a fresh kernel download. I'm not logging into exchange because, for some reason, I think that's my problem.
Also, changing to Never didn't really fix my issue.
Related
I've been constantly battling sleep issues. I am on PRI/NV 1.77 and latest radio. I tried downgrading to 1.77 just recently to see if it would fix it and it hasn't, but I'm staying put.
Running latest MIUI and Savage 1.6 kernel.
Spare parts had been showing on average 50% running time even though my screen on time would be something like 5%. I had read that ideally these ratios should match, since it means your phone is properly sleeping.
Spare parts shows paltry wake locks of just a few seconds or minutes for Android System as the top app. I've killed all my widgets and even tried airplane mode and don't notice too much of a drop. After getting rid of all updating widgets (minimal text and the MIUI cal widget) and stopping google calendar sync I'm currently at 30% running vs 5% screen on. I've basically got everything that would run in the BG disabled -- set cpu, system monitor, etc. Is this a "good ratio"? Any other ideas on debugging what seems to be an obvious wake lock? I've looked at logcat and don't see a thing that looks interesting, hardly any activity. Am I just being crazy or does it seem like I still have a wake lock?
Thanks for reading
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
freeza said:
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
Click to expand...
Click to collapse
Thanks for the reply.
So, this is a bad ratio then, i'm not nuts?
I kill EVERYTHING then sleep and i'm still seeing the issues. Is there some more fool proof way I can guarantee nothing is running before sleeping? My guess would be something syncing more than it should have. Should I try toggling everything app's sync off and then sleeping?
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
lil-dice said:
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
Click to expand...
Click to collapse
Interesting, I had that UID 10018 problem before and I never figured it out. It maybe Google Talk, Gmail, or even the Calendar. You may have to try clearing caches of one or all three to really see.
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
lil-dice said:
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
Click to expand...
Click to collapse
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
freeza said:
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
Click to expand...
Click to collapse
I'm not sure how to get to that in MIUI, in battery settings i jut see my minutes since unplugged. No Awake time.
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Saturn2K said:
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Click to expand...
Click to collapse
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
lil-dice said:
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
Click to expand...
Click to collapse
That's just how it is for all AOSP kernel using roms. Their wifi sleep mode is absolutely terrible. On the plus side, it seems as though it doesn't use an absurd amount of battery to keep the wifi on.
I think my phone is suffering from the Android OS keep awake bug. I just charged my phone to 100%, rebooted, opened and closed the camera app and left it alone for about an hour and a half. I am down to 92% batter life remaining. This seems excessive. The Android OS app shows a keep awake time of exactly 93 minutes which is also exactly the same as the up time.
I don't quite understand BetterBatteryStats just yet, but BetterBatteryStats shows "gps-lock" as 1h27m4s under Kernel Wakelocks since charged. Nothing else comes close. The highest Partial Wakelock is ActivityManager-Launch with 12s. Under Other Awake is 93 minutes and Screen on is 2 minutes. BetterBatteryStats is the first item under Process the surfaceflinger and com.android.phone.
Before rebooting I had set my GPS settings to (and they remained this way after reboot)
-Google's Location Service : Unchecked
-GPS satellites : Checked
-Location & Google search : Unchecked
Other stats:
-Verizon LTE
-bigxie IML74K Build 2
-franco.Kernel #12 (hotplug enabled, 350k low, 120k high)
-No widgets
-No other apps were opened
-Gmail is set to sync. I haven't run or configured Google+ (don't use it). Gmail/Calendar/Contacts should be the only things syncing, no facebook sync.
I had similar issues before flashing the kernel and rom.
How can I get this thing to go to sleep? I don't think this should be consuming so much battery life while idle.
you have a "bad app" that is preventing the phone from deep sleeping.
get cpu spy from the market to verify how long your phone is staying in each state
do you have any notifications in the notification bar?
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
lethologica said:
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
Click to expand...
Click to collapse
I don't use BetterBatteryStats so I wouldn't know.
I personally set my CPU speeds from 700-1200MHz (as indicated by Franco and others... setting it to ~300 is bad because it makes the phone use more power to catch up)
How many apps do you have? can you use AppBrain or something to provide me a list of what apps you use?
I just took a list at my CPU Spy...
0:09:51 1200Mhz
920 MHz... 0:01:35
700MHz: 0:09:49
Deep Sleep: 3:21:43
82%... 3h 50m 35s on battery
Android OS 28%
Screen 24%
Google Voice 14%
Phone idle 14%
Android system 7%
Cell standby 3%
Nova Launcher 3%
Wi-Fi 2%
Beautiful Widgets 2%
Market 2%
700-1200MHz. Conservative Governor. Hotplug off
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
lethologica said:
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
Click to expand...
Click to collapse
It doesn't have to be a system app. A app can be started as the moment as Android OS is started.
Not all apps are listed in that battery monitor. I can tell you that for sure. Definitely something is wrong with your phone setup.
The best way to debug it (in my opinion) would be to backup all of your apps and reflash the ROM from scratch. Flash bigxie's ROM (or try another ROM if you choose to) and Franco's Kernel.... install CPU Spy and leave the phone off for like 5-10 minutes. See if it deep sleeps.
Edit: Try this https://market.android.com/details?...251bGwsMSwxLDEsIm5leHRhcHAuc3lzdGVtcGFuZWwiXQ this should help you figure out what app it is.
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
lethologica said:
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
Click to expand...
Click to collapse
You did update to the latest Google Maps right? it contained fixes for the battery. Maps is a huge drain if it runs in the background. I always leave my GPS deactivated even though it's activated ondemand. I just don't trust it.
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
lethologica said:
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
Click to expand...
Click to collapse
It's probably software. Something is keeping the GPS on. Either by a app or ROM. Most likely app.
If you're not using gps with google location services, it will take a while to lock.
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
joshnichols189 said:
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
Click to expand...
Click to collapse
Any idea on how to figure out what that app is?
I'm not sure how to find an app that is constantly requesting GPS, but I know the app Watchdog will help find an app that is running in the background consuming processor cycles.. you might want to try that but I have no idea if it will work.
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
did you tuck your phone in?
I had that problem with a Rom and turning on and off the Bluetooth would fix the problem.
Sent from my GalaxyNexus using Tapatalk
imail724 said:
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
Click to expand...
Click to collapse
Try disabling GPS when you're not using it. Worked for me.
i tried to freeze the google maps, but still getting the GPS wakelock.
from the other thread, some one mentioned about facebook.
i freeze facebook in titanium backup. looks like the GPS time is not increasing.
are you guys having this issue installed facebook app?
the other thread:
http://forum.xda-developers.com/showthread.php?t=1419087&page=3
I charged my Nexus LTE(unrooted,4 days old) till it was 100% before I went to bed. As soon as I set my alarm I unplugged it to test to idle. Well I just woke up 6 hours later and it was completly dead. I have it on the charger now, I hope i can see the spycpu cause that was main purpose for leaving it off. I do not sleep surf either.
Is this a defective phone?
Wow that's nuts. I definitely never get that sort of battery drain. Are you rooted? Using a custom rom or just stock?
jd1001 said:
Wow that's nuts. I definitely never get that sort of battery drain. Are you rooted? Using a custom rom or just stock?
Click to expand...
Click to collapse
unrooted.
I have to leave for work now with out a phone, I will try to check up via computer (feeling like a dinosaur).
Ha ha I know I feel so bad when I don't have my phone. Maybe see if it happens again tonight. If it does I would get on to the carrier. Have a good day at work!
jd1001 said:
Ha ha I know I feel so bad when I don't have my phone. Maybe see if it happens again tonight. If it does I would get on to the carrier. Have a good day at work!
Click to expand...
Click to collapse
Ill try both.
It has been documented the Verizon has battery issues but not sure if they were meant to be fixed in the 4.0.2 update
davewinkwink said:
I charged my Nexus LTE(unrooted,4 days old) till it was 100% before I went to bed. As soon as I set my alarm I unplugged it to test to idle. Well I just woke up 6 hours later and it was completly dead. I have it on the charger now, I hope i can see the spycpu cause that was main purpose for leaving it off. I do not sleep surf either.
Is this a defective phone?
Click to expand...
Click to collapse
Are you sure it was dead or you just had a sleep of death? If it truly was dead you definitely have something draining your battery during idle. I highly recommend you turn off your LTE antenna if you haven't already unless your using data intensive apps and you need it, such as surfing or netflix or something. Also, change your sync times to less often, I do every 15min. Sign out of google talk, use wifi when you can, adjust screen brightness, disable bluetooth. White backgrounds will eat your battery faster as well. What else am i forgetting.... Root will help if you can manage to, its incredibly easy especially with the new rootkit out, because you can load francos newest build which has increased my battery 2x, with 25% drain in the last 8.5 hours even with a 1/2 hr of whale tail last night. Also make sure your not running something stupid in your background thats eating your battery like a task killer or battery spy or something, those just rape your battery
If you turn on Google+ instant upload and it has thousands of pictures to upload that will kill your battery in a few hours. If your phone is staying awake because of Android OS then try turning off your GPS.
Sent from my Transformer Prime TF201 using xda premium
As noted in a lot threads on a lot of forums, there are some phones that have a problem with the Android OS and the "Keep Awake" time. There seems to be an issue with some phones not truly going to sleep when the power button is used to turn off the screen as opposed to letting the screen turn off automatically when the screen times out. This results in a very high time in the Settings/Battery/Android OS/Keep Awake menu.
In stock form and with every rom that I have installed, my "Keep Awake" time was always about 50-60% of my total battery time. If the phone had been off charger for 8 hours, I'd have 4-6 hours of Andorid OS "Keep Awake" time. This was true even if the phone had been in my pocket unused and seems to be exacerbated by my habit of turning the screen off manually with the power button every single time. I used to never let the screen timeout.
There seems to be two "fixes" according to Franco (of kernel fame). One concerns the camera. Seems the camera is started and then turned off during startup. But in so doing, it leaves a sensor active and this prevents the phone from actually going to sleep. So he recommends starting and using the back button to go back to the home screen. The other is DRM Protected Content. He recommends this be disabled or frozen. A third, that I don't believe I recall seeing him recommend but that I have seen on his thread at XDA (down for blackout right now) is to disable Maps.
I have done all three of those and my Keep Awake time has gone from 40-50% of my total battery time down to a few percentage points. I mean if I don't use my phone it will now show less than a minute of Keep Awake time per hour.
Good luck
My VZW nexus can idle with moderate use on constant LTE and get 15 hours with out issue. Hell I have even gotten more so check google+ as suggested. If it went dead on idle with nothing running constantly to cause it than I would say your phone and/or battery is defective
Geezer Squid said:
As noted in a lot threads on a lot of forums, there are some phones that have a problem with the Android OS and the "Keep Awake" time. There seems to be an issue with some phones not truly going to sleep when the power button is used to turn off the screen as opposed to letting the screen turn off automatically when the screen times out. This results in a very high time in the Settings/Battery/Android OS/Keep Awake menu.
In stock form and with every rom that I have installed, my "Keep Awake" time was always about 50-60% of my total battery time. If the phone had been off charger for 8 hours, I'd have 4-6 hours of Andorid OS "Keep Awake" time. This was true even if the phone had been in my pocket unused and seems to be exacerbated by my habit of turning the screen off manually with the power button every single time. I used to never let the screen timeout.
There seems to be two "fixes" according to Franco (of kernel fame). One concerns the camera. Seems the camera is started and then turned off during startup. But in so doing, it leaves a sensor active and this prevents the phone from actually going to sleep. So he recommends starting and using the back button to go back to the home screen. The other is DRM Protected Content. He recommends this be disabled or frozen. A third, that I don't believe I recall seeing him recommend but that I have seen on his thread at XDA (down for blackout right now) is to disable Maps.
I have done all three of those and my Keep Awake time has gone from 40-50% of my total battery time down to a few percentage points. I mean if I don't use my phone it will now show less than a minute of Keep Awake time per hour.
Good luck
Click to expand...
Click to collapse
Ive been getting good battery life, despite my awake time being around 6-8 hours at the end of a charge. I tried the camera close but that never helped, I've just disabled DRM though. Also, GPS locator has been associated with this, which is probably what you meant by "maps". I just turn off my location unless i need it for navigation in location settings
how do you disable drm? and what exactly is it?
Peesashiz said:
how do you disable drm? and what exactly is it?
Click to expand...
Click to collapse
It has to do with digitally protected files, music, etc. One time I went home screen/menu/settings/apps/all/drm/disable. The last time I did it from Titanium and pressed the freeze button for that app.
Good luck.
BTW, both actions can be reversed.
Hey everybody,
Just made the jump from the iPhone 4S and have done the custom ROM/kernel thing the past week. Things were good at the start but I feel them slowly deteriorating.
I find my battery life during sleep has become much worse than before. I mean, it still kills the 4S which would see ~25% overnight. But I'm seeing 10% overnight right now, and was ~2% earlier in the week. I normally have my phone on the charger at night, but didn't last night and I'm kinda glad I got to see this. Makes me realize why I was likely chewing through more in the day too.
You can see what I'm running below in my signature. Last night I had 5 instances where the phone woke on its own. Likely due to emails coming in.
Am I expecting too much from my modifications? Am I doing something wrong? I'm ready to toss AOKP aside because of other issues anyway, but yesterday I also read it was known to have some excessive battery drain as well. Without turning this into a battle to defend the ROM you use (like half the threads in here), if you have other suggestions, feel free to throw in a ROM suggestion. I'll attach some pictures of my battery screen so anyone willing to give me a hand can help.
Thanks in advance.
I had this problem when I was running franco too. Switched to leankernel and never looked back. I get about 4-6% drain overnight as long as I dont do something stupid like leave something running by exiting with home instead of the back button. I also have wifi on 24/7 and gps off unless im nav'in. No BT
Screwedupsmitty said:
I had this problem when I was running franco too. Switched to leankernel and never looked back. I get about 4-6% drain overnight as long as I dont do something stupid like leave something running by exiting with home instead of the back button. I also have wifi on 24/7 and gps off unless im nav'in. No BT
Click to expand...
Click to collapse
I'm hesistant to blame the kernel. I was using franco prior to AOKP without issue. I didn't make that clear in the OP. I went 4.0.4 Stock -> Stock + franco -> AOKP b31 + franco. Things were good the first two steps and I'd like to think the first few days on AOKP.
Perhaps I have some background processes chewing battery - but there's nothing with a higher battery drain than Chrome beta with 2%. My phone idle and Cell standby had huge drain though. Could a weaker than normal signal cause this? Could my radio be the culprit?
Steps to best diagnose idle battery drain.
-Install CPU Spy and Better Battery Stats.
-Charge phone to full and let it run for several hours undisturbed (easiest to charge before bed, then unplug it when you know it won't be used till morning).
-Take quick note of your % loss per hour. Around 1%, you're golden. 1-2 is pretty normal. >3 and you've got issues.
-Launch CPU Spy. Most of the time should be deep sleep (we're talking about 95%). If your phone has been awake a lot, there's either an app that refuses to let your phone rest, or an OS/Kernel issue. If it's not extreme but noticeable, you likely just need to reign in settings on some apps to keep them from syncing so often or working in the background.
-Launch Better Battery Stats. Select Partial Wakelocks from the menu. These are all cases of apps waking the phone up, sorted by length. Go look at problem apps' settings/consider uninstalling if you don't need them. Kernel wakelocks should be low too.
Keep in mind that the goal here isn't really to get all these things to zero so do not obsess over small showings. Facebook with push notifications but updates set to never keeps my phone awake for about a minute or two every night, for instance. So does Handcent SMS. If you flash a rom and your phone needs to do a lot of syncing it's likely to show up in this kind of test as well. But for a night with nothing going on, nothing should be keeping your phone up for more than a few minutes total.
myrdog said:
I'm hesistant to blame the kernel. I was using franco prior to AOKP without issue. I didn't make that clear in the OP. I went 4.0.4 Stock -> Stock + franco -> AOKP b31 + franco. Things were good the first two steps and I'd like to think the first few days on AOKP.
Perhaps I have some background processes chewing battery - but there's nothing with a higher battery drain than Chrome beta with 2%. My phone idle and Cell standby had huge drain though. Could a weaker than normal signal cause this? Could my radio be the culprit?
Click to expand...
Click to collapse
Weaker than normal signal can kill a phone battery, when I'm in lecture out in the bumfuck nowhere school I go to, I get -100 to -120dbm, which kills my battery while i'm at school. If thats your situation not much to do besides hope radios may increase your signal, but if not then your basicly as SOL as i am and may have to just charge it
JoeSyr said:
Steps to best diagnose idle battery drain.
-Install CPU Spy and Better Battery Stats.
-Charge phone to full and let it run for several hours undisturbed (easiest to charge before bed, then unplug it when you know it won't be used till morning).
-Take quick note of your % loss per hour. Around 1%, you're golden. 1-2 is pretty normal. >3 and you've got issues.
-Launch CPU Spy. Most of the time should be deep sleep (we're talking about 95%). If your phone has been awake a lot, there's either an app that refuses to let your phone rest, or an OS/Kernel issue. If it's not extreme but noticeable, you likely just need to reign in settings on some apps to keep them from syncing so often or working in the background.
-Launch Better Battery Stats. Select Partial Wakelocks from the menu. These are all cases of apps waking the phone up, sorted by length. Go look at problem apps' settings/consider uninstalling if you don't need them. Kernel wakelocks should be low too.
Keep in mind that the goal here isn't really to get all these things to zero so do not obsess over small showings. Facebook with push notifications but updates set to never keeps my phone awake for about a minute or two every night, for instance. So does Handcent SMS. If you flash a rom and your phone needs to do a lot of syncing it's likely to show up in this kind of test as well. But for a night with nothing going on, nothing should be keeping your phone up for more than a few minutes total.
Click to expand...
Click to collapse
This is what every user should use to diagnose battery problems at first.
Hi guys
I have a LTE Note II and have had this battery drain on standby where wifi will absolutely destroy my battery. This has been going on for months and months and I'm just not sure if Samsung are ever going to resolve this and it is quite the pain in the arse.
I've done many tweaks to my phone, and all location services are off. Also, I've set it as a static IP, but nothing seems to help. I think this is related to the wlan_rx_wake wakelock? I get the impression my phone is responding to the wifi and getting woken up constantly.
Does anyone else experience this and do you have any suggestions?
P.S. please don't mention my apps causing it. It definitely is not. I know my way around Android and also, my Nexus 4 with the same setup (but location + google now turned ON) absolutely annihilates my Note II battery life on standby. This is clearly a Samsung problem that they have ignored for the best part of a whole year, and it seems to be related to wifi.
Any help would be greatly appreciated.
Thanks
Do u have some figures about this battery drain to be able to compare with my phone?
It could be a bad modem/connection. What is your configuration?
Primokorn said:
Do u have some figures about this battery drain to be able to compare with my phone?
It could be a bad modem/connection. What is your configuration?
Click to expand...
Click to collapse
No exact figures but I have been observing it for months now and it hasn't been the case with any other phone I use. With wifi on, it'll drain around 20% overnight. With Wifi off, it'll drain 5 or so %. With Wifi on on every other phone I own/owned, it will barely drain at all overnight.
Type *#0011#
Check wifi setting
Sent from my GT-N7100 using xda app-developers app
This is what I got when I entered that it
After *#0011# go to menu and select wifi in order to see if power safe mode is on.
Yeah it is on
Is that bad?
Sent from my Nexus 4 using Tapatalk 4
That's not bad, it improves battery usage. I don't recognize your problem. Does the phone go into deep sleep with wifi on? Which rom do you use?
Hielko said:
That's not bad, it improves battery usage. I don't recognize your problem. Does the phone go into deep sleep with wifi on? Which rom do you use?
Click to expand...
Click to collapse
Stock ROM. And yeah, but it is constantly being woken up.
Sorry for the bump, but this hasn't changed.
I'm not sure if this is to do with just the N7105, but it is something that just won't go away. I'm now finding I lose between 20 and 30% overnight (around 7 hours) with wifi on, or about 10% with data on. With these both turned off but the phone radio still being on, it only drops about 2% in the same time. This was tested with bluetooth/gps and sync turned off.
I don't really have the time to write up everything that I have tried, but suffice to say I have tweaked the phone a lot over the past few months trying to sort this out, but nothing works.
Here is a quick summary of the stuff I have done.
Firstly, I have to run a stock rom and kernel because there is an app I need that will not work on custom roms/kernels. It also doesn't work on root but I have found a procedure to toggle unroot/root when need be and it works fine. Therefore I'm stuck on 4.1.2 as I want to be rooted but I cannot use any custom rom or kernels.
I have tried factory wiping the phone/installing later versions of 4.1.2, etc etc and the same problems still exists with a freshly wiped phone and no apps installed. This problem also doesn't happen with my Nexus 4 or any other phone I have owned with the same setup, so I am very certain it is not due to a misbehaving app.
I have frozen a lot of bloat with titanium backup, I have hibernated a hell of a lot of stuff with greenify (including system app where there are no perceivable negative consequences)
I have added a few tweaks to the build.prop such as to disable fast dormancy and a few other supposed power saving ones which are meant to help with the msm_hsic wakelock.
There are many other things such as setting a static IP, and also tweaking with my router based on some advise I found on these forums. Nothing much has helped.
Location services and google now are off, and I'm not using the Samsung bloatware apps.
I use betterbatterystats and the partial wakelocks are fine. Very low infact.
However, IMO it is two "kernal wakelocks" which are causing me the problem.
wlan_rx_wake - in regards to the wifi
mdm_hsic_pm0 - in regards to the data
These are by no means outrageously high. My estimation is perhaps 10 mins wake up time and around 2000 "expire time" (whatever that means) every 3 hours or so. However, these two are always the highest kernel wakelock depending on if i'm using wifi (wlan_rx_wake) or data (mdm_hsic_pm0). My phone is also not being kept awake too long too in general.. at a guess around 3 hours awake time for every 2 hours screen on time for every 15-20 hours.
I can't remember if these kernel wakelocks were super duper high in the past, and the fixes I tried actually lowered them, but I still notice this massive Idle drain when on data or wifi (just over 1% per hour - or 2-3% per hour respectively).
In regards to the Wifi.. I suspect that packets are being sent from my router which are constantly waking up my phone. Unfortunately, I haven't been able to solve this problem with any of the router-side fixes I've tried.
This leads me to suspect that the wifi and data radio of the N7105 is power hungry, or I've had a faulty unit since day one. I keep hearing about this stellar battery life for this phone but, for me, the best I've ever got is around 20 hours. This may sound good but the problem is it is 20 hours with 6 hours screen on time, or 20 hours with 2 hours screen on time. This doesn't seem to make a difference where I should be getting two days when I only have 2 hours screen on time.
Any help would be greatly appreciated, and any experiances of others with the N7105 may help find out if it indeed is more power hungry. I'd also like to add that my network does not support 4G yet so this is all on 3G and NOT LTE.
Thank you, and sorry for such a long post.
fade2black101 said:
Hi guys
I have a LTE Note II and have had this battery drain on standby where wifi will absolutely destroy my battery. This has been going on for months and months and I'm just not sure if Samsung are ever going to resolve this and it is quite the pain in the arse.
I've done many tweaks to my phone, and all location services are off. Also, I've set it as a static IP, but nothing seems to help. I think this is related to the wlan_rx_wake wakelock? I get the impression my phone is responding to the wifi and getting woken up constantly.
Does anyone else experience this and do you have any suggestions?
P.S. please don't mention my apps causing it. It definitely is not. I know my way around Android and also, my Nexus 4 with the same setup (but location + google now turned ON) absolutely annihilates my Note II battery life on standby. This is clearly a Samsung problem that they have ignored for the best part of a whole year, and it seems to be related to wifi.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
I ain't expert...
but, I would suggest like this :
Go to wifi, press menu and then Advanced (advanced setting of the wifi).
uncheck/untick "Scanning always available"
"Keep wifi on during sleep" = set to Never.
uncheck / untick "auto network switch btwen wifi network and mobile networks"
all these helps me to minimize the usage of wifi during night times (when I sleep). Anyway, device also need to have a deepsleep
Hope can help you as well.
Sent from the corner of this rounded earth.