Related
I started using JuicePlotter yesterday, and noticed that at night my battery barely drains, if at all (hooray for setcpu!). Until exactly 5am when it starts draining heavily at a steady rate. I've done all of the obvious stuff (I think), like making sure I have nothing set to begin syncing at that time, but I can't seem to pin it down.
Does anyone know of a way to find out what's turning on at 5am and draining the battery?
Do you have an Exchange sync setup?
If you do you may want to check and see if your Peak times start at 5AM. If so you may want to set it to update less frequently.
Does JuiceDefender run on a schedule and keep 3G off until 5am?
Thanks for the suggestions guys
I have exchange set up, but its set to "as items arrive" for both peak and non-peak hours (which is set to 8am anyway - yeah, being on call 24/7 sucks).
I'm also not using any kind of timing app like juice defender to schedule anything.
One wierd thing I noticed that may be tied to this, is that certain apps like twitdroyd and fb update immediately when I open the apps, even though they're set to refresh manually, and not to update when I open the apps. Still trying to figure that one out.
Night mode is enabled from 2 am to 5 am. Depending on your settings, Data/3G/Wifi are disabled between those times.
nslouie said:
Night mode is enabled from 2 am to 5 am. Depending on your settings, Data/3G/Wifi are disabled between those times.
Click to expand...
Click to collapse
This sounds promising - can you tell me how to check any night mode settings? (searching turns up nada)
fachadick said:
This sounds promising - can you tell me how to check any night mode settings? (searching turns up nada)
Click to expand...
Click to collapse
He is referring to JuiceDefender, I bet. I would guess a lot of people who use JuicePlotter also use JuiceDefender. It does exactly as he described: turns data off from 2am to 5am. I use it, and it does help. It also keeps data off when the screen is off during the rest of the day, except for a quick check every so often.
hankbear said:
He is referring to JuiceDefender, I bet. I would guess a lot of people who use JuicePlotter also use JuiceDefender. It does exactly as he described: turns data off from 2am to 5am. I use it, and it does help. It also keeps data off when the screen is off during the rest of the day, except for a quick check every so often.
Click to expand...
Click to collapse
rats - I was hoping he was referring to something in regular settings. I'm not using JuiceDefender, or anything similar.
well if you do have it setup for everything to be off between 2 - 5 then wouldn't that make sense that as soon as 5 hit your apps will start syncing even Google apps as they have been trying to sync that whole time and just started queuing up and finally your radios turned back on. I have not used juice yet so i do not know much about it just throwing in some pennies.
One other thing the refresh manually is only for when the app is closed as soon as that app opens its going to sync with its servers. When you set it to manual then that means when you open the app you manually refreshed it and the phone did not do that while idle or you were busy on some other app. Its like twitter for desktops if you set your refresh manually then while the app is open it will not refresh until you hit refresh
fachadick said:
rats - I was hoping he was referring to something in regular settings. I'm not using JuiceDefender, or anything similar.
Click to expand...
Click to collapse
One thought: Do you have a good signal in the spot where your phone sits at 5am? A bad signal is the best way to drain a battery fast. A friend's house has an awful Sprint signal, and my battery will drain in four or five hours there, even with no use, whereas I get well over 24 hours with average use in good signal strength areas.
Back when I first got my phone, I used System Panel to figure out what was causing the battery drain. I liked using it so much, I even ended up purchasing it. The history part is what you want, and it will work without paying for a bit, so you can find the problem.
xlrdxrevengex said:
well if you do have it setup for everything to be off between 2 - 5 then wouldn't that make sense that as soon as 5 hit your apps will start syncing even Google apps as they have been trying to sync that whole time and just started queuing up and finally your radios turned back on. I have not used juice yet so i do not know much about it just throwing in some pennies.
Click to expand...
Click to collapse
that would make sense if I was running something like that, but I'm not - as a part of my job, I need to be able to reply immediately to specific emails. At any hour. Total PITA, but hell, it's better than not having a job, right? JuicePlotter's pretty neat though - it just sits in the background monitoring your battery levels and graphs them. For example, it was showing an almost horizontal line from when I stopped using the phone the night before until exactly 5am when it started a gradual decline.
xlrdxrevengex said:
One other thing the refresh manually is only for when the app is closed as soon as that app opens its going to sync with its servers. When you set it to manual then that means when you open the app you manually refreshed it and the phone did not do that while idle or you were busy on some other app. Its like twitter for desktops if you set your refresh manually then while the app is open it will not refresh until you hit refresh
Click to expand...
Click to collapse
Are you sure about this? I mean it makes sense, but I would be willing to swear that back when I was running stock I would open FB or Twitdroyd and it would wait for me to hit refresh before syncing with their servers. Twitdroyd, for example, I would set to keep 80 tweets, and I would check it only occasionally, so I could read those 80 tweets whenever I wanted. Now when I check it, because it syncs immediately, I lose anything older than the most recent 80 tweets. As a workaround, I've increased the number of tweets to keep, but it's still annoying.
ok so hmm what rom are you using. not wanting to bash the dev but could it be that rom?
hankbear said:
One thought: Do you have a good signal in the spot where your phone sits at 5am? A bad signal is the best way to drain a battery fast. A friend's house has an awful Sprint signal, and my battery will drain in four or five hours there, even with no use, whereas I get well over 24 hours with average use in good signal strength areas.
Click to expand...
Click to collapse
My signal's not great, but the phone didn't move between 4am and 5am, and the battery only started draining at 5am.
hankbear said:
Back when I first got my phone, I used System Panel to figure out what was causing the battery drain. I liked using it so much, I even ended up purchasing it. The history part is what you want, and it will work without paying for a bit, so you can find the problem.
Click to expand...
Click to collapse
I actually purchased SystemPanel this morning with the hope that it would help me get to the bottom of this (I had been using the free version for a while, and now I had an excuse to buy it). It shows me history of battery, device usage, and cpu activity, but even if I see that the cpu or the device is being used, I'm still not sure how that's going to help me pinpoint what's going on. First I need to build up some history anyway though.
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 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.
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.
I've had the phone for near a week now and this is the first time doze has failed me. Left it alone at 10pm with about 50% left and looks like it went to zero in about four hours. (screenshot) I've tested other nights and it worked as expected -- wifi and cell coming on and off periodically. When checking usage, I was disturbed to find Facebook took up 25% of my battery. Is there some way Facebook is overriding doze?
dipson626 said:
I've had the phone for near a week now and this is the first time doze has failed me. Left it alone at 10pm with about 50% left and looks like it went to zero in about four hours. (screenshot) I've tested other nights and it worked as expected -- wifi and cell coming on and off periodically. When checking usage, I was disturbed to find Facebook took up 25% of my battery. Is there some way Facebook is overriding doze?
Click to expand...
Click to collapse
Wow. Looks like it was constantly awake during that time. You didn't happen to turn on photo syncing with Facebook?
Sent from my Nexus 5X using Tapatalk
Facebook is one of the worst when it comes to battery drains, I stopped using it and i just use a browser to stay logged in. Snapchat is also pretty bad, I think it was top 3 in my list while I slept earlier. First time happening, i turned off location on snapchat, ill see if that helps
btort1 said:
Facebook is one of the worst when it comes to battery drains, I stopped using it and i just use a browser to stay logged in. Snapchat is also pretty bad, I think it was top 3 in my list while I slept earlier. First time happening, i turned off location on snapchat, ill see if that helps
Click to expand...
Click to collapse
Same here. Facebook did this to me back when I had an HTC Hero, killed my battery in 8 hours no problem. The moment they changed the application to a "service" and had those wake-lock bugs I ditched it, never looked back.
No application should install itself as an always-on service unless its there for push messages. I decided that having my phone last all day was more important than getting facebook messages immediately.
EeZeEpEe said:
Wow. Looks like it was constantly awake during that time. You didn't happen to turn on photo syncing with Facebook?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yea, it looks like it was constantly connected. Don't have photo syncing, but good thought.
btort1 said:
Facebook is one of the worst when it comes to battery drains, I stopped using it and i just use a browser to stay logged in. Snapchat is also pretty bad, I think it was top 3 in my list while I slept earlier. First time happening, i turned off location on snapchat, ill see if that helps
Click to expand...
Click to collapse
I stopped using Snapchat a while ago for that reason. Facebook, however, never really gave me a problem on my N6. It usually hovered around 6-7% use. No app is worth that much drain, let alone Facebook. If this is a normal occurrence, I'll probably just uninstall it.
ryan stewart said:
Same here. Facebook did this to me back when I had an HTC Hero, killed my battery in 8 hours no problem. The moment they changed the application to a "service" and had those wake-lock bugs I ditched it, never looked back.
No application should install itself as an always-on service unless its there for push messages. I decided that having my phone last all day was more important than getting facebook messages immediately.
Click to expand...
Click to collapse
Hopefully this was a one time occurrence since it worked fine on my N6. I've got no problem getting rid of it though, because like you said, I'd rather have my phone last all day (or night in this case).
Second Night Update
While I agree the Facebook app is bad, it looks like it was not the culprit. Uninstalled, doze again failed to kick in overnight and drained 18% over about seven hours. Not as bad as the 50% the first time, but still no bueno. It looks like Android OS kept it awake for seven hours. I know doze is pretty new, but there are some smart people here; anyone got any ideas/theories as to what's going on and remedy? Screenshots
I'm experiencing the same EXACT issues except I don't have Facebook installed
tjrocks91 said:
I'm experiencing the same EXACT issues except I don't have Facebook installed
Click to expand...
Click to collapse
Good to know I'm not alone! Even after uninstalling Facebook I've got the same problem with Android OS keeping it on. I'm considering clearing the cache and see if that changes anything.
Wow you have a perfectly diagonal line. Try a battery monitoring app. Might have more useful information as to what is draining overnight.
Sent from my Nexus 5X using Tapatalk
I did a factory reset and installed ~10 of my most used apps instead of restoring all apps and it's been sleeping fine now, no wakelocks
I also turned off WiFi and Bluetooth scanning, location services are on battery saving, and Google location reporting is off
I am willing to bet there are going to be some hiccups with marshmallow or even some newer hardware features of the phone and some apps until everything gets up to speed.
Just wondering, what build are you guys on? MDA89E or MDB08I?? I'm on MDA89E
I got 08I immediately after turning it on, Ive always lost like 1-2% overnight.
Maybe that is what the last-minute update was for, fixing that bug that you (unfortunately) found.