So I posted this in a different thread but figured I would post it here to see if anyone could duplicate my findings. I have a Note3 from T-Mobile and for whatever reason leaving the Wi-Fi on will not allow the phone to go into deep sleep mode. I noticed when I was down to 40% battery after 10 hours with only one hour of screen on time. After running some tests I had only 2 minutes of deep sleep those entire 10 hours (tested using BetterBatteryStats) I tried setting "Keep Wi-Fi on during sleep" to Never and unchecking "Always allow scanning" under advanced network settings but neither of them fix the issue. In fact, after several tests I concluded that setting never for "Keep Wi-Fi on during sleep" wasn't even functioning as my access points still showed the client connected while the phone was asleep.
Can anyone else confirm this issue is actually a bug and not just my phone being defective?
Here's my original post on the topic regarding how I found the problem and what I have tested so far:
OK so after only 2 days of owning this phone (got it late Monday night, the T-Mobile variant) I finally figured out why I'm getting such bad battery, and I suspect the same thing may be happening for the other people in this thread. Hopefully this information helps at least one person.
My battery stats was almost identical to all the other users in this thread that had bad battery, I would get barely around 10-12 hours on the phone with less than 2 hours of screen on time. After using multiple apps to track down the issue I finally got what it was.
Wireless. Yes, wireless was my cause. But the thing is Wi-Fi didn't show up at all in any of the battery apps so I assumed it was a non issue. I've had other phones and have always kept the wireless turned on the entire time without problems. The basic problem is not that Wi-Fi is using power itself but it's that by default the phone cannot enter deep sleep while connected to Wi-Fi. This is why trying to use apps like BetterBatteryStats will lead you nowhere initially (though they were useful in finding out what was causing the issue) You can discover this by turning on Wi-Fi and connecting the phone to a charger, then disconnecting it so your BBS information will reset. Then power off the screen and power it back on after 10 minutes. You'll notice in the other section that deep sleep will have less than a minute time while awake probably has close to 9 minutes, if not more. This is with everything else turned off, almost no apps, and no special Samsung stuff enabled.
Under Apps > Settings > Wi-Fi > Menu > Advanced there are two options that should help this: "Keep Wi-Fi on during sleep" and "Always allow scanning" I set the "Keep Wi-Fi on during sleep" to Never and unchecked Always allow scanning and rebooted the phone. And low and behold...nothing. Yes, these options don't work (at least not to fix this problem) The phone still won't enter deep sleep mode while the wireless is enabled. Based on my company's wireless devices I can see that even with the screen off for well over 10 minutes it still shows connected as a client meaning the wireless is not turning off properly while it's in sleep mode. Or perhaps it can't go into sleep mode because the wireless is on which stops it from going into sleep mode and turning off the wireless. My guess is that it's a Samsung bug.
The reason why there's so many people here to get good battery usage is because they're either used to turning Wi-Fi on only when needed and keeping it off. You'll also not notice it if you have more than 6 hours of screen on time because you could easily assume that it would make sense that you phone would only last 10 hours total with that much screen on time, even though it should have technically lasted 20+ hours with only 6 hours of screen on time if the phone could have entered deep sleep.
So what's the real fix for this? Unless it's by design my belief is that it's a bug and won't be fixed until Samsung/T-mobile notices. I can't test to see if the same thing happens on other carriers so if someone feels like testing this theory out it would help.
For now, I guess we're just left to manually turning Wi-Fi on only when needed and leaving it off in all other cases. For those that have the T-mobile variant, make sure you also go into Settings > General > Backup and reset > Collect diagnostics and uncheck the "Allow Diagnostics" as that will probably be the highest offender of Partial Wakelocks (it'll show up as com.carrieriq.tmobile.wakelock or System Manager Application)
If anyone wants more information on my testing let me know!
Click to expand...
Click to collapse
That's because the 'Keep WiFi during sleep: Never" setting only disconnects, it doesn't shut down the WiFi radio.
You're going to have to use a manager (Like Deep Sleep Battery Saver).
Or just hit the toggle yourself... If you're going to keep it disconnected in sleep anyway, just swipe down the notification bar and hit the bloody toggle.
ShadowLea said:
That's because the 'Keep WiFi during sleep: Never" setting only disconnects, it doesn't shut down the WiFi radio.
You're going to have to use a manager (Like Deep Sleep Battery Saver).
Or just hit the toggle yourself... If you're going to keep it disconnected in sleep anyway, just swipe down the notification bar and hit the bloody toggle.
Click to expand...
Click to collapse
The problem is that it doesn't disconnect, the access point 100% shows it is connected and transferring data every now and then. But the real issue isn't weather it disconnects or not but it's the fact that Wi-Fi will not allow the phone to go into deep sleep mode. For now I am fine with switching Wi-Fi off and on as needed, but with no other phone have I needed to do this before and definitely seems like a bug.
But regardless, what I'm trying to figure out if this is a legit bug that I should submit to Samsung/T-mobile or if it's just my phone and I should ask for a replacement. If anyone has BetterBatteryStats and could test this with their Note3 that would help.
My stupid phone has just started this same issue!!!! Freaking annoying, after only 8 hrs from 100% charged state, the battery is at 46% with only 26 mins screen ontime, I checked out that the phone never goes into deep sleep. What is going on and what can be causing this? Did you manage to resolve your issue?
PS I checked out wakelock detector but doesn't tell me a thing, as what program is keeping the phone awake all the time. Starting to hate this phone and miss my S3
What is your GPS accuracy setting set to? GPS, Wifi or Networks? Try setting it to GPS only.
GameBoiye said:
So I posted this in a different thread but figured I would post it here to see if anyone could duplicate my findings. I have a Note3 from T-Mobile and for whatever reason leaving the Wi-Fi on will not allow the phone to go into deep sleep mode. I noticed when I was down to 40% battery after 10 hours with only one hour of screen on time. After running some tests I had only 2 minutes of deep sleep those entire 10 hours (tested using BetterBatteryStats) I tried setting "Keep Wi-Fi on during sleep" to Never and unchecking "Always allow scanning" under advanced network settings but neither of them fix the issue. In fact, after several tests I concluded that setting never for "Keep Wi-Fi on during sleep" wasn't even functioning as my access points still showed the client connected while the phone was asleep.
Can anyone else confirm this issue is actually a bug and not just my phone being defective?
Click to expand...
Click to collapse
Well, your issue looks pretty similar to mine, which I solved with this Xposed mod (you could give it a try if you're on KitKat): http://forum.xda-developers.com/xposed/modules/mod-wi-fi-deep-sleep-t2752947. I was experiencing that even when "Keep Wi-Fi on during sleep" is set to Never, Wi-Fi still was awake most of the time according to battery stats.
Related
Will Wifi drain my battery even when in sleep mode ?
I charged my phone last night as I always do right up to 100%. Left it in sleep mode and went to bed.
Received a call this morning and when the phone switched on noticed my battery was on 26% and it was trying to connect to wifi.
Is wifi similar to bluetooth in that I believe bluetooth will still be active and receiving in sleep mode and will so drain the battery ? I could have sworn I have left wifi on before in sleep mode and it didnt drain the battery, but maybe I am wrong.
So will wifi in sleep drain my battery to that extent ie from 100% to 26% from about 10.30 last night to 10am this morning ?
The wierd thing is I was playing with it all day yesterday and the battery only got to 39% or something.
Is something wrong ?
yes, leaving your wifi on will cause battery drain. If there's any traffic, this gets worse
Also activesync may have been running and trying to connect every 10 minutes or so. The activesync problem has been mentioned in another thread.
Just hope its just battery drain and not a fault.
Yes, I second the observation... 2 hours powered off drains 40% battery power...
That sucks, the blueangel didn't do that. It automatically turned wireless off on shutdown and turned it on again on wakeup.
Now I'll have to get used to doing that manually... :?
If you still have the BA, or if somebody else could check, look for this key in the registry:
HKLM\System\CurrentontrolSet\Control\Power\State\Suspend
There will be various values there. Default = 3, means state D3, which is the suspend state.
If there are any other values there, please note the value name, and the value of it.
If there aren't, check whether there are any subkeys.
For example, the Qtek 9100 has subkey {98C5250D-C29A-4985-AE5F-ADE5367E5006} which, if you look under HKLM\System\CurrentontrolSet\Control\Power\State\Interfaces\, you'll see is "Power-manageable NDIS miniports". Its default value is 4 for state D4, which is the -off- state.
Basically, I suspect, or rather expect, that the BA will have another value or subkey there which will refer to the wireless connection, and set its state to 4 as well. If that's not the case, then it's being handled more directly by whatever power manager adjustments they have made - rather than letting Windows CE's power management handle it as above.
kilrah said:
Yes, I second the observation... 2 hours powered off drains 40% battery power...
That sucks, the blueangel didn't do that. It automatically turned wireless off on shutdown and turned it on again on wakeup.
Now I'll have to get used to doing that manually... :?
Click to expand...
Click to collapse
The daft thing is when you switch your device back on, you arnt connected to the wireless network and it has to find a signal again. So its like its keeping the wifi switched on but for no reason whatsoever !
What would be cool is if on putting the device into sleep mode it would automatically put the wifi into low power mode so you could leave it on without it whacking your battery and you could possibly receive msn alerts.
That was sort of what the BA did.. :?
I still have it but with a broken screen
So unfortunately can't check, maybe someone else?
I think I've found the way to deactivate wifi again when the manager doesn't want to. Tap on the OS's connectivity icon at the top of the screen. It may say Enable wifi or disable wifi. If it says activate, tap once to activate and once again to deactivate. If it says deactivate just tap once. Then go into the wireless manager again, it should now be off. Works for mine at least
I set up the WiFi standby rules to "never", so wifi should be always on even when my device is in standby mode.
This worked very good at the beginning, but since some days WiFi is NOT kept alive. As soon as the device is going into sleep mode i will lose WiFi connection. The WiFi standbye rule is still correctly set to "never".
Thats really lame because i use locale to update my RSS Feeds at home over WiFi on certain time slots. But i get no updates since wifi is not active when the device is sleeping.
Anybody an idea what the problem is? As i said it worked for 2 weeks and suddenly its not working anymore.
Won't that drain the battery to Kingdom Come if you do leave it on on standby? I used to do that on the Tytn II I used to have, and the battery died after 2 hours!
samo.chan said:
Won't that drain the battery to Kingdom Come if you do leave it on on standby? I used to do that on the Tytn II I used to have, and the battery died after 2 hours!
Click to expand...
Click to collapse
well i wouldn't say 2 hours, should be more than that. But i'm only activating wifi at home, and at nights my device is plugged to ac adaptor. So battery is not an issue in my case, and i want to use the better bandwidth at home. I just dont know why is suddenly stopped working...
Settings > Wireless controls > Wi-Fi Settings > Menu > Advanced > Wi-Fi sleep policy. When finished press Menu and then Save. Done.
The "Menu Button to save" Hint did it! thanks!
I always chose the option, but forgot to save via menu button and pressed the back button.
The strange thing here is: when i was coming back to this menu later it would still show the correct setting (WiFi always on), even though i hadn't saved it via menu button. But it wouldn't work, because wifi would be deactivated.
The back button will save your last selection, but won't activate the option!
This is really one of Androids problems: you just don't have one standard way of interacting with the system on many levels. Sometimes "back" button is enough (or the only way) to store your data, other times you have to press hardware buttons to save...
hmm the problem seems to be elsewhere: today in the morning the connection was lost again when i took the phone out of sleep mode. i could see the wifi icon, but the apps couldnt connect to the net (my rss feeds hadn't been updated).
Seems like each time i deactivate wifi manually (when leaving home) the wifi rules settings will be lost, and i have to change the wifi rules again and save the settings. Otherwise wifi won't be kept alive...that's really annoying.
maybe i have to download the "keep wifi alive" app after all from the market...
What make and model is your AP?
it's a netgear router, i will check the exact model today and post it here.
hmm i forgot to check the model, but i changed my router settings yesterday.
the router was set to disconnect after 60 minutes, when the connected device is not using the connection.
i changed that, so the connection is not reset at all, but still as soon as my device goes to sleep mode the wifi connection is basically dead.
After taking the phone out of sleep mode, i can see the "wifi connected" icon still there, but no app has any internet connection.
Hi,
I thought that I could use Tasker (https://play.google.com/store/apps/...EsIm5ldC5kaW5nbGlzY2guYW5kcm9pZC50YXNrZXJtIl0.) to save battery life. So, what I did was to prepare the following profiles:
a) Disable autosync, enable it to 3 minutes every 30 minutes. Sync only between 6:30 and 23:05.
b) Enable autosync while on AC power, disable when not.
c) Disable wifi, enable it for 15 seconds every 15 minutes so the system would have time to connect to a known wifi if available. Then disable wifi unless its already connected.
d) When a wifi connection starts, do nothing. When it gets disconnected (like when I leave home), disable wifi.
I only use EDGE. I only sync gmail, contacts and calendar.
Before this, I had autosync and wifi on all the time so I believed this setting should conserve battery. Everything works, Tasker app itself is not draining much from the battery (according to Betterbatterystats its really negligible) but still, I have a considerably higher energy loss than with default setting.
Do you know whats the reason for this? Is is caused by the wifi enabling and disabling - taking more power? Is it caused by the fact all sync gets done at the same time? Or why is that?
Im generally happy with the Nexus S battery life but this outcome makes me curious ...
EDIT: My advanced wifi system setting always was "never disable wifi when screen is off". Also, for the purpose of this test, I disabled wifi AP on my router to check just for the outcome of the wifi search.
Check out your Awake time (can find this in BetterBatteryStats), you'll probably notice the phone stays awake for longer than it would normally. Normally the phone would go into a practically permanent "sleep" state, powering nothing but your radio, when the screen is off and doing nothing. It would just wake up every X minutes to autosync or for other alarms (exchange sync, etc) and then go back to sleep. I wouldn't be surprised if it is solely the wifi option.
Depending on the advanced setting in the wifi options, it keeps the connection indefinitely or drops it after a certain amount of time, i think around 15mins - 30 mins. This may need to be changed to fit the circumstances.
Overall though, benefiting from the use of Tasker or similar program for battery life purposes doesn't gain much over what android already does (albeit still with alot of room for improvement).
Well, I should've mentioned this: My advanced wifi system setting always was "never disable wifi when screen is off". So thats not possible reason.
Also, for the purpose of this test, I disabled wifi AP on my router to check just for the outcome of the wifi search.
I basically believed that before, the phone had wifi on and checked around every now and then. And with the new setting, it would check less often, therefore saving battery.
Awake time is about 40 minutes in 7 hours sleep.
EDIT: Maybe it would help to adjust the times better.
This is very annoying, I have spent the whole morning trying to find a solution for this issue. The battery runs out already fast as it is, and now the phone is not
Battery drained about 20% at night by itself. Currently draining about 1-2% per 5 minutes when idle. What do I do? I have looked on various different threads for a solution, but did not find anything to fix this issue.
How do I fix this?
Thanks, in advance.
Also some details.
I had my phone at home, I prefer the phone to use WiFi networks when syncing and updating, but to have phone turn them automatically off when not using them, that is when the phone is locked and not syncing and updating anything. But apparently it doesn't do that, it has WiFi on at all times for some reason. And I don't know if its related to WiFi, it doesn't appear to go to "deep sleep"
Yukicore said:
This is very annoying, I have spent the whole morning trying to find a solution for this issue. The battery runs out already fast as it is, and now the phone is not
Battery drained about 20% at night by itself. Currently draining about 1-2% per 5 minutes when idle. What do I do? I have looked on various different threads for a solution, but did not find anything to fix this issue.
How do I fix this?
Thanks, in advance.
Click to expand...
Click to collapse
Yukicore said:
Also some details.
I had my phone at home, I prefer the phone to use WiFi networks when syncing and updating, but to have phone turn them automatically off when not using them, that is when the phone is locked and not syncing and updating anything. But apparently it doesn't do that, it has WiFi on at all times for some reason. And I don't know if its related to WiFi, it doesn't appear to go to "deep sleep"
Click to expand...
Click to collapse
For me, it was the last Google Maps update. Try to disable "Reporting Location" and "Location History" under Location settings on Google Settings app(the one with the green icon). I had around 25% drain over night and half of it came from this.
Try it and see if this can help you.
:fingers-crossed:
Like above say, disable location, especially if you keep wifi on.
Leaving wifi on while sleeping itself is not good for our health anyway, so if you have data switch to 2G, its at least enough to keep internet messages coming while saving battery. And if its wifi wise, apply pm.sleep_mode=1 in your build.prop. AND, scroll up a little, wifi_supplicant_can_interval(something like that, from its SHOULD BE 15 change to 300-600).
Disable unused apps and use greenify.
Galaxo60 said:
For me, it was the last Google Maps update. Try to disable "Reporting Location" and "Location History" under Location settings on Google Settings app(the one with the green icon). I had around 25% drain over night and half of it came from this.
Try it and see if this can help you.
:fingers-crossed:
Click to expand...
Click to collapse
Thank you for the answer, but sadly it didn't seem to do it. My WiFi is still always on, even though I have it set to turn off when phone is sleeping at WiFi advanced settings.
Although the phone entered deep sleep mode when I manually turned WiFi off, but I'm not sure if that was the case.
KiD3991 said:
Like above say, disable location, especially if you keep wifi on.
Leaving wifi on while sleeping itself is not good for our health anyway, so if you have data switch to 2G, its at least enough to keep internet messages coming while saving battery. And if its wifi wise, apply pm.sleep_mode=1 in your build.prop. AND, scroll up a little, wifi_supplicant_can_interval(something like that, from its SHOULD BE 15 change to 300-600).
Disable unused apps and use greenify.
Click to expand...
Click to collapse
I understand, but I forgot to do so, I actually have an app that turns on air plane mode at certain time. But that still doesn't fix the issue that the phone doesn't enter sleep mode with WiFi on and doesn't turn it off, even though it's set to do so.
Also I did not quite understand what you were telling me there, as I got the phone last week and it's my first android phone. The app you suggested could cut it, but that means that whenever there will be an auto check for news sequence I will be downloading it with mobile data? Is there an app that could cause this?
I was about to update on this, but I just got notification about 4.3 update. :laugh:
I will update this post, if this problem still exists.
UPDATE : Of course, still the problem persists, Phone goes to sleep when I have Wi-Fi turned off. But when on, even though I have it set to turn off during sleep mode, it keeps the phone wake and drains the battery.
Restart your router?
Sent from my Nexus 4 using Tapatalk 2
Ulver said:
Restart your router?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
How is it related to my router exactly? My iPod disconnects from Wi-Fi no problem.
Thank you for trying though.
I had left my phone this night with Wi-Fi off, but mobile data and 3G was on, Lost 7% in 7Hours from 47%. Does this seem okay, or a little bit too much? By the time I answered 2 emails and made 1 short phonecall and checked on battery logs from 2 different apps, and changed my wallpaper, battery has dropped to 33%. I'm not proud.
The answer to your problem is JuiceDefender Ultimate, available from Play Store.
Yukicore said:
I had left my phone this night with Wi-Fi off, but mobile data and 3G was on, Lost 7% in 7Hours from 47%. Does this seem okay, or a little bit too much? By the time I answered 2 emails and made 1 short phonecall and checked on battery logs from 2 different apps, and changed my wallpaper, battery has dropped to 33%. I'm not proud.
Click to expand...
Click to collapse
Unfortunately this is normal, the battery life is not the best feature of nexus 4. How many screen on time hours do you get averagely?
This fixed the Wifi always on issue for me.
Turn WiFi on: Settings, WiFi, Menu (3 dots upper right hand corner), advanced, uncheck scanning always on.
Hope this helps.
Noticed in battery settings that my Wifi turns on and off frequently even when my device is sleeping. Doesn't seem to be affecting battery life but I'm wondering why it does this. It happens on both my Nexus 7 (stock rooted) and my Nook HD+ (CM11). I do have the "always scan for networks" settings off.
Attached screenshot is after I didn't really use my Nexus 7 for about a week.
I would imagine this is caused by certain apps requesting data. For example, your Gmail app may be set to refresh every one hour, which means it needs to use the WiFi to search for new data and download it, if needed. Other apps are similar to that as well, depending on your settings.
If it really miffs you, you can always use tasker and create a task that shuts the wifi (I have it put it in airplane mode since it does several things in one shot) off when the display goes off and back on when display comes back on...will need to be rooted.