Database Info

[Q] Nexus 5 - Battery usage shows Wi-Fi always on?? (even when manually turned off)

I'm on a 32gb Google Play purchased white Nexus 5, activated on Sprint. I went through a whole charge cycle yesterday with Wi-Fi off, and under battery usage / Wi-Fi / Use Details / Wi-Fi running, it showed "Wi-Fi running" 17 hours. I never even had Wi-Fi turned on once.
I've been playing with it today, turning Wi-Fi on and off, and no matter what, the Wi-Fi usage time matches my phone on time. It seems according to the battery meter my Wi-Fi is always on. Any one else seeing this? What is the deal?

Go into wifi settings, click the menu button in the lower right corner, go to advanced.
Uncheck "Scanning always available". There you go.
Although TBQH the battery impact seems minimal (especially if it's able to use wifi to get a location lock, as that's much more power efficient than turning on the GPS).

that is because even though you have turned WiFi off, its still available to app to get better location. if you want to turn that off, go to settings, wifi, options, advanced and uncheck "scanning always available"
that will turn off wifi completely. hope that helps.

beestea said:
I'm on a 32gb Google Play purchased white Nexus 5, activated on Sprint. I went through a whole charge cycle yesterday with Wi-Fi off, and under battery usage / Wi-Fi / Use Details / Wi-Fi running, it showed "Wi-Fi running" 17 hours. I never even had Wi-Fi turned on once.
I've been playing with it today, turning Wi-Fi on and off, and no matter what, the Wi-Fi usage time matches my phone on time. It seems according to the battery meter my Wi-Fi is always on. Any one else seeing this? What is the deal?
Click to expand...
Click to collapse
Go into WIFI settings and click the menu (three dots menu) for advanced settings. You will find an option that makes the phone to scan for networks even when disabled.

mocoflip said:
Go into WIFI settings and click the menu (three dots menu) for advanced settings. You will find an option that makes the phone to scan for networks even when disabled.
Click to expand...
Click to collapse
Thank you all very much! Will see if it helps my battery life at all!

Thanks folks.
Following my update to 4.4.2 I was experiencing wifi using a lot more battery than normal. I tend to turn wifi off at night, and phone had started using more battery than normal. This fix in advanced settings got things back to normal for me. Battery usage much better. Odd that the update seemed to have set this to on for me.

Thanks a lot guys..this was bugging my head as well..

Hi Guys,
I've just updated to Lollipop by sideloading the OTA.
My battery usage stats say that my WiFi is constantly on and the phone is Awake, even with WiFi turned off AND 'Scanning Always Available' also turned OFF.
What could be going on and does anyone have any suggestions to fix?
Thanks

Same thing happening to me Wifi constantly on Android 5.0 Nexus 5
randommonth said:
Hi Guys,
I've just updated to Lollipop by sideloading the OTA.
My battery usage stats say that my WiFi is constantly on and the phone is Awake, even with WiFi turned off AND 'Scanning Always Available' also turned OFF.
What could be going on and does anyone have any suggestions to fix?
Thanks
Click to expand...
Click to collapse
Same thing is happening to my device. I upgraded to Android 5.0 yesterday using the OTA upgrade and battery life has been horrendous. When I view battery use it shows WiFI as being constantly on...even when I have it manually turned off. I also have "scanning alwaysa available" turned off. Need more insight on this issue.

randommonth said:
Hi Guys,
I've just updated to Lollipop by sideloading the OTA.
My battery usage stats say that my WiFi is constantly on and the phone is Awake, even with WiFi turned off AND 'Scanning Always Available' also turned OFF.
What could be going on and does anyone have any suggestions to fix?
Thanks
Click to expand...
Click to collapse
rebornlol said:
Same thing is happening to my device. I upgraded to Android 5.0 yesterday using the OTA upgrade and battery life has been horrendous. When I view battery use it shows WiFI as being constantly on...even when I have it manually turned off. I also have "scanning alwaysa available" turned off. Need more insight on this issue.
Click to expand...
Click to collapse
I had this same issue. I think I fixed it, check out my thread for a solution: http://forum.xda-developers.com/google-nexus-5/help/fix-lollipop-wifi-off-t2947870
Basically, flash Kitkat factory images, sideload OTA, factory reset, and hopefully that resolves it. Nasty little bug.

Thanks
Thanks for reading my post and suggesting the solution you have written up on your thread. I am going to see if somehow the problem becomes resolved within the next couple of days. Otherwise, I will flash back to clean KitKat image and upgrade to Lollipop as you suggested.
When I upgraded to Lollipop yesterday, it wasn't a clean install. I simply installed over my current KitKat config.

thattypicalnerd said:
I had this same issue. I think I fixed it, check out my thread for a solution: http://forum.xda-developers.com/google-nexus-5/help/fix-lollipop-wifi-off-t2947870
Basically, flash Kitkat factory images, sideload OTA, factory reset, and hopefully that resolves it. Nasty little bug.
Click to expand...
Click to collapse
Thanks for the reply, but what you suggest is basically how I have arrived at this situation...
1. I flashed the KitKat factory images a few months ago to resolve an unrelated issue
2. I sideloaded the Lollipop OTA update earlier this week, then discovered the WiFi Awake issue chewing battery.
3. I performed a factory reset (from the O/S, not from recovery) 2 days ago and then re-setup my phone, making sure to untick the option during setup which turns scanning always available on.
4. Today, with Wifi turned off and scanning always available turned off, my phone battery stats indicate my WiFi to be constantly ON.
That said I will give your method another try, but beyond that I was considering flashing the Lollipop factory images, will this help?
Cheers

randommonth said:
Thanks for the reply, but what you suggest is basically how I have arrived at this situation...
1. I flashed the KitKat factory images a few months ago to resolve an unrelated issue
2. I sideloaded the Lollipop OTA update earlier this week, then discovered the WiFi Awake issue chewing battery.
3. I performed a factory reset (from the O/S, not from recovery) 2 days ago and then re-setup my phone, making sure to untick the option during setup which turns scanning always available on.
4. Today, with Wifi turned off and scanning always available turned off, my phone battery stats indicate my WiFi to be constantly ON.
I was considering flashing the Lollipop factory images, will this help?
Cheers
Click to expand...
Click to collapse
How I arrived at that situation was by clean flashing the Lollipop factory images Maybe try it again? I'm honestly not sure what the difference in doing the two is (flashing factory Lollipop vs flashing factory Kitkat -> OTA -> wipe), but it seems to have done something for me. Also are you rooted? I did not root after following those steps, as all I really used root for was monitoring battery stats.

randommonth said:
Hi Guys,
I've just updated to Lollipop by sideloading the OTA.
My battery usage stats say that my WiFi is constantly on and the phone is Awake, even with WiFi turned off AND 'Scanning Always Available' also turned OFF.
What could be going on and does anyone have any suggestions to fix?
Thanks
Click to expand...
Click to collapse
rebornlol said:
Same thing is happening to my device. I upgraded to Android 5.0 yesterday using the OTA upgrade and battery life has been horrendous. When I view battery use it shows WiFI as being constantly on...even when I have it manually turned off. I also have "scanning alwaysa available" turned off. Need more insight on this issue.
Click to expand...
Click to collapse
thattypicalnerd said:
I had this same issue. I think I fixed it, check out my thread for a solution: http://forum.xda-developers.com/google-nexus-5/help/fix-lollipop-wifi-off-t2947870
Basically, flash Kitkat factory images, sideload OTA, factory reset, and hopefully that resolves it. Nasty little bug.
Click to expand...
Click to collapse
randommonth said:
Thanks for the reply, but what you suggest is basically how I have arrived at this situation...
1. I flashed the KitKat factory images a few months ago to resolve an unrelated issue
2. I sideloaded the Lollipop OTA update earlier this week, then discovered the WiFi Awake issue chewing battery.
3. I performed a factory reset (from the O/S, not from recovery) 2 days ago and then re-setup my phone, making sure to untick the option during setup which turns scanning always available on.
4. Today, with Wifi turned off and scanning always available turned off, my phone battery stats indicate my WiFi to be constantly ON.
That said I will give your method another try, but beyond that I was considering flashing the Lollipop factory images, will this help?
Cheers
Click to expand...
Click to collapse
thattypicalnerd said:
How I arrived at that situation was by clean flashing the Lollipop factory images Maybe try it again? I'm honestly not sure what the difference in doing the two is (flashing factory Lollipop vs flashing factory Kitkat -> OTA -> wipe), but it seems to have done something for me. Also are you rooted? I did not root after following those steps, as all I really used root for was monitoring battery stats.
Click to expand...
Click to collapse
I had the same issue as well and found it was actually caused by viber app. if you have viber app you can got into the app
->settings->general->Wifi-sleep policy and change it to use device's settings.
If that doesn't help try booting into safe mode and check your battery stats, thats how i found out it was actually caused by a 3rd party app.

A question?
My wifi is always on too as a function of Settings>Wifi>Advanced>Keep Wifi on during sleep>Always.
My question is, when I'm at work I have no chance of connecting to any Wifi networks (there aren't any!), is it going to save my battery turning this off?
Regards all,
Paul.

I have a 32 gb nexus 5. My Wifi is always on. Whenever i try to turn it off, it automatically turns right back on. If i restart the phone, wifi will be off for sometime. But as soon as i go to the drop down menu, zap, its on again. Any help on this? And of course this is draining my battery faster.

Working solutions
tejasbr said:
I have a 32 gb nexus 5. My Wifi is always on. Whenever i try to turn it off, it automatically turns right back on. If i restart the phone, wifi will be off for sometime. But as soon as i go to the drop down menu, zap, its on again. Any help on this? And of course this is draining my battery faster.
Click to expand...
Click to collapse
============================================
1. Wiping Cache Partition.
2. An app must be interfering with the android system. Uninstall applications like Clean Master, Ram Boosters, Process Killers ,etc.
Your phone doesn't need these optimizers and they are the source of the problem creating problems with the usage, asking for permissions to interfere with the system.
NOTE : Process killers, ram boosters mostly the problem, you don't need to disable WiFi everytime after use, just go to wifi options -> advanced -> Keep wifi on during sleep -> Never and select WiFi freq band as requied.
After this step you need to clear cache again and then you will never see WiFi on top i.e System will function normally.
============================================

Real Cause of battery drain/wake lock in MJ7/MK2 and fix

I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.

mongoose3800 said:
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
Click to expand...
Click to collapse
Funny thing is that when i am using mobile data the drain is worse, So I'm pretty sure this is not the main issue man. Also, I have a Mobile 'WiFi' router. Only me has WiFi connection in my entire hostel. So I don't really think it's the issue. Good finds tho! It will definitely help someone. Cheers!

Agree with stanley, this is not the only cause.

39089665568
vndnguyen said:
Agree with stanley, this is not the only cause.
Click to expand...
Click to collapse
Agreed. There are many things that will cause elevated use. But Im talking the rapid drain that occurs when you're not using the phone. Ever since taking the action I describbed my battery life has been excellent. Eg 94% after 14 odd hours with no use. And, I'm still connecting to my home wifi. Beforehand it could be below 60% with no use and this is the real problem people are talking about. Hope that makes sense.

Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.

aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
I don't get it. What am I supposed to do exactly?

aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
What about unicast traffic? i know the Client Isolation sort of "VLAN"s every client associated, just wondering if that might affect client to client communication?
Good point btw, im also wondering how many services wake the damn thing up, waking up over network is more an enterprise workstation scenario...to me it sounds like HotSpot 2.0 services being active, but i have not enabled it.
HS2.0 can let client and AP sort of talk without associating.

Nazty111 said:
I don't get it. What am I supposed to do exactly?
Click to expand...
Click to collapse
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.

aydc said:
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
Click to expand...
Click to collapse
This is very true. Back on my old GNex i used to have crazy wifi wakelocks and I couldn't for the life of me figure it out. I never figured it out, actually. But I am positive it is one of the two PC's on my network that are broadcasting packets across the network, waking my phone up. I haven't had time to extensively test the wifi wakelock in the environment i've previously encountered it in to see if it still applies, but since I haven't changed anything regarding any of the two computers involved on that network, I'm positive I will have the same wifi wakelock issue when I get back and test. Is there a way (besides using Shark) to see what programs are broadcasting packets across the network?
But to get back on topic, I am experiencing battery drain connected to ONE router with ONE AP. I am in an apartment building with several other routers nearby, though. Maybe they are broadcasting packets somehow that the kernel is interpreting and keeping the phone awake? However it seems as though the Android OS bug keeps coming back for everyone no matter what, even in airplane mode.

Wifi has evolved a lot the last decade, not just by technology standards but into integration as well. carriers use them as small cells, we'll see them more often in the future (malls, stadiums, etc), and HS2.0 adds to make it a bit more seamless, they call it offload, taking your data needs through small wifi cells rather then the macro cells (3g, 4g), hence offload.
my point is that they would have never invested in that if the wifi chips inside consumer products were not efficient enough, so nearby APs shouldnt be a problem at all. But im still puzzled for what would one need the waking up process through wifi?
If Wifi is the general bugger, then somebody throw an eye on the Passport service, thats the consumer name for HS 2.0 services.
PS, tested AP Isolation on my sh!tty WRT120N, no difference unfortuantely.

Will there be a future update from Sammy or will we get Kitkat directly
Sent from my SM-N900 using Tapatalk

Just a follow up. I have still had no battery drain since avoiding connecting to wifi networks that use multiple APs. Now, i only connect to wifi networks where i know there is only one AP. Before I stumbled across this the drain and Android os wake lock was bad, really bad, after I had connected to large wifi networks - I just hadn't put two and two together. This is more than coincidence - my testing is sound and replicable. And, this week I have been in remote areas with weak to no 3g signal and the battery life has still been fantastic and no wake locks so that sort of rules that out - Sure there is a little increase in battery usage but nothing dramatic, something to be expected and certainly not something to complain about. I have seen many claims to fix battery drain but these are just fine tuning and not addressing the major drain caused by Android OS wake locks. Clearly, there must be an issue with the wifi software driver in MJ7/MK2 and I hope Samsung/Google are aware of it. The annoying thing is getting Samsung to acknowledge the issue and take feedback.

I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app

EddieN said:
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.

mongoose3800 said:
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
Click to expand...
Click to collapse
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.

EddieN said:
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
Click to expand...
Click to collapse
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz

mongoose3800 said:
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
Click to expand...
Click to collapse
It could be. Both networks I have been connected to have been 2.4GHz Wireless-N capable routers. I just find it odd that a lot of things don't add up when looking at awake times in Settings -> Battery and comparing it to kernel/partial wakelocks in BBS/WLD/CPU Spy. All of the times seem to be roughly in the same ballpark, but they never add up to correspond to each other. Surely there must be information missing in this regard.

I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).

duffmannr3 said:
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
Click to expand...
Click to collapse
Thanks for your input. Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue

EddieN said:
Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
Click to expand...
Click to collapse
It's the issue about "multiple" APs, but I don't think that it is about the number of APs. What I have read is that there is so much traffic on those big networks, e.g. broadcasts from other devices. I don't know how it should be with your problem that wifi doesn't turn off - can you see if it's reconnecting after some standby time? If yes, then wifi is turned off during sleep, but is just not shown in statistics.
EddieN said:
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Click to expand...
Click to collapse
I'm currently on MJ7/MK2. My device is unbranded and I'm living in Germany. It came on 26th of December and was about 30MB or so.
EddieN said:
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
Click to expand...
Click to collapse
It's definitely worth a try! There was absolutely no hint that pointed to this one app. I started with having a look at the battery statistics ~every 30min after a fresh reboot. After a few days it was clear that it only could be the alarm app, battery draining started only in the morning.

Battery drain while phone is idle

My battery only lasts about 8-9 hours after a full charge without me actually using the phone.
The top offenders are always some combination of Google Services, Google Play Services, Android OS and Android System. Google Services/Google Play Services always has a high keep awake time.
I have tried tons of stuff.. Uninstalling Google Play Services updates, booting into recovery and clearing the cache, factory resets, turning off Location services, location reporting, etc. turning them all on, all 3 location discovery modes, turning off wifi during sleep, turning off LTE, etc.. nothing worked..
.. until suddenly, without me changing anything that I could identify, the drain stopped. And it worked for about 3 days like that. I would only lose 1% battery every couple of hours of idling. At the end of a day of moderate use I was at 60%.
Then, I installed a couple more apps, and the dran came back. And now the drain won't go away.. I've factory reset, cleared the cache, etc. etc. and still it just drains.
Could this be a hardware issue? I'm not sure if I should RMA it or what.. (this is my 2nd that has done this BTW).

trance9 said:
My battery only lasts about 8-9 hours after a full charge without me actually using the phone.
The top offenders are always some combination of Google Services, Google Play Services, Android OS and Android System. Google Services/Google Play Services always has a high keep awake time.
I have tried tons of stuff.. Uninstalling Google Play Services updates, booting into recovery and clearing the cache, factory resets, turning off Location services, location reporting, etc. turning them all on, all 3 location discovery modes, turning off wifi during sleep, turning off LTE, etc.. nothing worked..
.. until suddenly, without me changing anything that I could identify, the drain stopped. And it worked for about 3 days like that. I would only lose 1% battery every couple of hours of idling. At the end of a day of moderate use I was at 60%.
Then, I installed a couple more apps, and the dran came back. And now the drain won't go away.. I've factory reset, cleared the cache, etc. etc. and still it just drains.
Could this be a hardware issue? I'm not sure if I should RMA it or what.. (this is my 2nd that has done this BTW).
Click to expand...
Click to collapse
Do you have Google backup enabled? It could get stuck somewhere sometimes and drain your battery.

ctbear said:
Do you have Google backup enabled? It could get stuck somewhere sometimes and drain your battery.
Click to expand...
Click to collapse
No. I have the backup disabled. And also the Photo backup. I tried to disable everything I can. Even without installing any apps on the stock ROM it drains.

Try formatting the data partition, backup what u need first. fastboot format userdata
also maybe try running a 3rd party launcher

turn off nfc in "other" and set gps in low power consumption in "geolocation"

Also get an app to switch from 3g to LTE while your phone is idle.
Looks like LTE is really really a bad friend for power consumption.

Turning off WiFi and or data when not using it helps. I recently downloaded greenify and its helping my battery life a bit.
Sent from my Nexus 5 using xda premium

So I went out to the store for a couple hours and I noticed I had basically no drop in battery while out. The main difference I could determine would be while out I am not on wifi.
When I got back the drain started again. I wondered if it was specific to my router, so I connected to a 5 GHz N router. I had been connecting to a 2.4 Ghz G router. So far, it seems that the drain is much faster if I switch to the G router, and when I switch to the N router it drains slower. Both routers have a strong signal.
So, I can just stay connected to the N router at home, but I'm not sure if there is a hardware defect with the wifi radio in the phone on 2.4.. Or if there's a misconfiguration or something on the router itself or what. I'm also not 100% sure it is even resolved since I only am a couple hours into testing and its very erratic.
BTW, if anyone has trouble connecting to 5GHz, the reason I wasn't connected to the N router in the first place, I found that you need to on a "Non-DFS" Channel. If your router is set to Auto, it may choose a DFS channel which the Nexus can't connect to. Apparently certain channels may have military activity on them and if so the device has to avoid that channel.. but rather than implement that on the Nexus those channels just don't work. I set my router to Channel 48 w/ 40 MHz width and it's working so far.

trance9 said:
So I went out to the store for a couple hours and I noticed I had basically no drop in battery while out. The main difference I could determine would be while out I am not on wifi.
When I got back the drain started again. I wondered if it was specific to my router, so I connected to a 5 GHz N router. I had been connecting to a 2.4 Ghz G router. So far, it seems that the drain is much faster if I switch to the G router, and when I switch to the N router it drains slower. Both routers have a strong signal.
So, I can just stay connected to the N router at home, but I'm not sure if there is a hardware defect with the wifi radio in the phone on 2.4.. Or if there's a misconfiguration or something on the router itself or what. I'm also not 100% sure it is even resolved since I only am a couple hours into testing and its very erratic.
BTW, if anyone has trouble connecting to 5GHz, the reason I wasn't connected to the N router in the first place, I found that you need to on a "Non-DFS" Channel. If your router is set to Auto, it may choose a DFS channel which the Nexus can't connect to. Apparently certain channels may have military activity on them and if so the device has to avoid that channel.. but rather than implement that on the Nexus those channels just don't work. I set my router to Channel 48 w/ 40 MHz width and it's working so far.
Click to expand...
Click to collapse
It wouldn't be the first time I've seen the wifi take a crap on an otherwise good router. My guess is that's what's happening.

Aerowinder said:
It wouldn't be the first time I've seen the wifi take a crap on an otherwise good router. My guess is that's what's happening.
Click to expand...
Click to collapse
Yeah I was noticing that the wifi and cell signals turn orange momentarily every now and then when I open the settings pane in the notification pull down. Maybe the wifi is getting dropped and re-connecting continuously.
I guess I will have to find another 2.4Ghz router to connect to figure out if its an issue with all 2.4Ghz routers.

sounds like it could be something syncing.. most are set to sync while on WiFi

meangreenie said:
sounds like it could be something syncing.. most are set to sync while on WiFi
Click to expand...
Click to collapse
A friend of mine had some problems with Foursquare notifications and in general using geolocalization...do u use those kind of apps often?

Wifi connection troubles after update to 6.0

I'm not sure if this is a Nexus 5 problem or a 6.0 Marshmallow problem but the problem occurred after the update to 6.0 on both Nexus 5s for me and my wife.
There seems to be some bug with my phone while it is asleep (screen is off but phone is on). When it is in this mode, it will not stay connected to wifi. For example, when I enter an area that has wifi, my phone will not connect. It will only connect when I wake the phone. And this isn't just a matter of the phone taking a while to connect. It NEVER connects. Before the update, my phone used to make a connection with my home router before I even walked inside. Now, I can be inside for hours and the phone never connects, until I wake it up. As soon as I wake the phone, the phone makes the connection with no problem. After a few minutes of the phone being asleep, I will wake the phone and the wifi connection will be gone. Now that it is awake again, it connects again with no problem.
I have tried forgetting the network and creating a new one, I have tried different routers, I have tried wiping the cache partition. I haven't tried a full factory reset, and I'd prefer not to, but I guess I will if I have to.
Just thought I would check here first and see if anyone had other thoughts.

Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro

vn800art said:
Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro
Click to expand...
Click to collapse
Thanks for the reply. Yes, that is what I thought at first also. I meant to say in my original post that my wifi settings are set to "Always On" during sleep. I've tried toggling that between the settings but still have the trouble.

Sorry, my Nex 5 has not this issue on Android 6 build MRA58K.
Alessandro

Yup, have the same issue. When the phone goes to sleep, it seems to disconnects from the wifi and never connects after I wake the phone. When I go into the wifi settings, I see "WIFI Connection Failure". I have to reconnect manually. Like the OP, have it set to always on as well. I also know it's not a router issue because I've tried this on four different routers (two linksys, one Dlink, one TPLink) All same results.
Wonder if this is a phone issue?

Please go here and click on the star to vote for this issue.
https://code.google.com/p/android/issues/detail?id=190667
Google upped this to a high priority Friday morning (Nov 6). The bad news is I think there a couple different WiFi symptoms being discussed here. Most of what is being discussed is the issue being discussed here (not reconnecting when the screen is off).
No idea when this will be fixed, so I build a Tasker profile to toggle WiFi every 15 minutes when not already connected to force a reconnect. I’ve observed it getting disconnected on its own overnight. This should avoid unnecessarily using cellular data.
I’m perpetually waiting for the next release of Android to fix annoying bugs.

vn800art said:
Settings - wifi - menu - advanced - Second choice down from the top - choose how to keep WiFi depending on your battery charge %. Regards. Alessandro
Alessandro
Click to expand...
Click to collapse
GaryP2 said:
Please go here and click on the star to vote for this issue.
https://code.google.com/p/android/issues/detail?id=190667
Google upped this to a high priority Friday morning (Nov 6). The bad news is I think there a couple different WiFi symptoms being discussed here. Most of what is being discussed is the issue being discussed here (not reconnecting when the screen is off).
No idea when this will be fixed, so I build a Tasker profile to toggle WiFi every 15 minutes when not already connected to force a reconnect. I’ve observed it getting disconnected on its own overnight. This should avoid unnecessarily using cellular data.
I’m perpetually waiting for the next release of Android to fix annoying bugs.
Click to expand...
Click to collapse
Thanks for the update Gary. The comment #6 describes my situation exactly. In doing some troubleshooting of my own, I find the disconnection trouble to happen less while on a 5Ghz network vs 2.5. I still have the trouble of it not connecting initially when I come into range, but I find that it is able to hold the connection while asleep.

I am also experiencing this on my Nexus 5 and also found and starred the thread above.
I just listened to 20min of streaming with Spotify to then realize that it had gone into Doze and used the mobile data!
This is more than annoying...
Maybe by disabling Doze for some specific connectivity-related system app? Anyone tried that?

Yes, I moved virtually all of the services type of apps (the ones with the green generic Android icon) to the battery not optimized list. It didn't make any difference for me.
In some ways it seems like it might be a Doze problem, and in other ways it doesn't. Doze shouldn't be affecting anything when the phone is in my pocket and I walk in the house to my WiFi. It also shouldn't be affecting anything when the phone is being charged, which is when I see frequent WiFi disconnects.
It will be real disappointing if this isn't fixed with 6.0.1.

This is still an issue with 6.0.1. Nexus 5 (2013) 6.0.1 MMB29K updated through OTA ZIP pushed with ADB.
Things work properly for a while right after a reboot and then WiFi never connects until the screen is turned on.
Google Connectivity Services C.1.6.7 (2466695) update didn’t make a difference either.

Same problem as the thread starter. HTC A9 anroid 6.0. (newest available OS)

Same problem here with a Nexus 5 .
Please star the problem if you have it.
https://code.google.com/p/android/issues/detail?id=170078

Has anyone tested with a non-stock kernel ?
I'm asking because the problem seems +/- resolved on CM13 (non caf).
No counting CM13, do you know of a more stable rom with the problem resolved?

Does anyone here have Wemo devices? I am reading that wemos, and possibly other devices that emit their own wireless network, may cause problems. I have several of these devices around the house, and wonder if that might be contributing. However, that only would solve the dropped connection bug I have, not the failing to connect while asleep but I have.

Hi mates, my Nexus 5 (android 6.0.1,M8974A-2.0.50.2.29) gets the same troubles with wifi connection but today I tried to put some apps in non optimized list of Doze and seems workig fine.
Thats my non optimized Doze list:
-Google Play Services
-System UI
Try it and let me know if it works properly.

frontomix said:
Hi mates, my Nexus 5 (android 6.0.1,M8974A-2.0.50.2.29) gets the same troubles with wifi connection but today I tried to put some apps in non optimized list of Doze and seems workig fine.
Thats my non optimized Doze list:
-Google Play Services
-System UI
Try it and let me know if it works properly.
Click to expand...
Click to collapse
I had Google Play Services already set to not optimize, but hadn't tried System UI. I will try that out and see what happens.

whitenack said:
I had Google Play Services already set to not optimize, but hadn't tried System UI. I will try that out and see what happens.
Click to expand...
Click to collapse
Welp, that didn't work. Still have the error after not optimizing System UI in addition to Google Play Services.

I don't know if the issue is resolved, but at least for me, it never worked fine so many days after testing some new workaround.
So, this was what I did in my Nexus 5 (latest build, MOB30H).
Uninstall or deactivate Google Connectivity Services, reset your network settings (you will lose your Wifi networks and BT pairings), reboot.
My Nexus 5 has been connecting to the wifi networks even with the screen off for the last 6 days.

Miguun said:
I don't know if the issue is resolved, but at least for me, it never worked fine so many days after testing some new workaround.
So, this was what I did in my Nexus 5 (latest build, MOB30H).
Uninstall or deactivate Google Connectivity Services, reset your network settings (you will lose your Wifi networks and BT pairings), reboot.
My Nexus 5 has been connecting to the wifi networks even with the screen off for the last 6 days.
Click to expand...
Click to collapse
Miguun, has the error returned, or still fixed? I just got the May update, so fingers crossed that fixes it. Otherwise, I guess I'll try your fix. I don't look forward to entering the wifi network information again.

Yup, it is still working !!

[Q] wifi switches on and off

Hi,
since yesterday I have problem with wifi in my S7 (SM-G930F). It keeps turning on and off every second or two. I cannot switch it off because it keeps switching. I have rebooted my device, but it didn't help me. My phone is not rooted, it has stock 6.0.1 firmware. How to fix it? Despite it's impossible to use wifi now, it keeps draining my battery.
edit:
logs attached here: logs

duchian said:
Hi,
since yesterday I have problem with wifi in my S7 (SM-G930F). It keeps turning on and off every second or two. I cannot switch it off because it keeps switching. I have rebooted my device, but it didn't help me. My phone is not rooted, it has stock 6.0.1 firmware. How to fix it? Despite it's impossible to use wifi now, it keeps draining my battery.
edit:
logs attached here: logs
Click to expand...
Click to collapse
Boot to recovery and clear caches, reboot and see how it is then

done. Sadly, it didn't help me.
edit: I've just used this app but it also failed. If nothing help me I will wait till Monday to show it to my coleagues from Customer Support. Maybe they will find solution

duchian said:
done. Sadly, it didn't help me.
edit: I've just used this app but it also failed. If nothing help me I will wait till Monday to show it to my coleagues from Customer Support. Maybe they will find solution
Click to expand...
Click to collapse
I'd backup with smart switch, and factory reset the phone
Or flash the latest stock ROM over the top with ODIN

*Detection* said:
I'd backup with smart switch, and factory reset the phone
Or flash the latest stock ROM over the top with ODIN
Click to expand...
Click to collapse
I think it may be related with some strange wifi:
11-11 11:20:11.682 3462 3896 I WifiConfigStore: " Social WiFi" is a captive portal!
11-11 11:20:11.682 3462 3896 I WifiConfigStore: not authenticated yet
11-11 11:20:11.682 3462 3896 I WifiConfigStore: login url: "https://accounts.google.com/ServiceLogin?passive=1209600&continue=https://accounts.google.com/o/oauth2/auth?scope%3Dopenid%2Bemail%2Bprofile%26response_type%3Dcode%26state%3Dp6Vwdj6Gibz9wS9yez6dSfomZT3WiPZC%26redirect_uri%3Dhttps://socialwifi.com/social-auth/complete/google-oauth2/%26client_id%3D240279395513.apps.googleusercontent.com%26from_login%3D1%26as%3D-1601b637b91f0d80&oauth=1&sarp=1&scc=1#identifier"
Click to expand...
Click to collapse
I saw it yesterday at work, but not authenticated. Now it is remembered in list. Sadly S7 has no option to forget networks out of range. Todays we have national holidays, but on Monday I will be at work and try to forget this network. I do not want to change rom because rom from my operator has wifi calling enabled and it is awesome.

Is there any chance that WiFi scanning is turned on? I recently saw that WiFi scanning will briefly turn my WiFi on then off repeatedly (shows with an indicator on top and I hadn't noticed that before). This first showed up when I installed Android Auto since it turned on my WiFi scanning option by default. As soon as I turned WiFi scanning off, the WiFi worked as it had before. It may be worth a look.

I've run into the same issue. Started yesterday, which may have come with the latest PJG update... Not sure.
But it's rendered my phone pretty much useless. The constant toast message popping up, saying "Network connectivity is available" gets in the way of the keyboard and I can't type a damn thing!
Like you, I've found it's stuck with reboots and a factory reset, which makes me think it could be the firmware or modem.
Edit: Disabling WiFi Scanning stopped the errors. Root cause is still unknown, though. I've never had to disable that before...

crizyal said:
Is there any chance that WiFi scanning is turned on? I recently saw that WiFi scanning will briefly turn my WiFi on then off repeatedly (shows with an indicator on top and I hadn't noticed that before). This first showed up when I installed Android Auto since it turned on my WiFi scanning option by default. As soon as I turned WiFi scanning off, the WiFi worked as it had before. It may be worth a look.
Click to expand...
Click to collapse
Yep. It was turned on, but I have it enabled since I bought this phone. Turning off neutralized my problem, but why it was broken for last few days when I haven't done anything with my phone? I rely on this feature because of localization accuracy and disabling it is just temporary fix.
edit:
Guys, one more thing:
do you have "Samsung Gear" app installed? I think this app is forcing to enable and disable wifi. Under localization it shows battery usage as high and it was updated last week

duchian said:
Guys, one more thing:
do you have "Samsung Gear" app installed? I think this app is forcing to enable and disable wifi. Under localization it shows battery usage as high and it was updated last week
Click to expand...
Click to collapse
My phone does not have the Samsung Gear app installed. I do use Samsung Pay regularly and that was also updated (engine and app). I don't know how that would relate to WiFi though.

jimmy-bish said:
I've run into the same issue. Started yesterday, which may have come with the latest PJG update... Not sure.
But it's rendered my phone pretty much useless. The constant toast message popping up, saying "Network connectivity is available" gets in the way of the keyboard and I can't type a damn thing!
Like you, I've found it's stuck with reboots and a factory reset, which makes me think it could be the firmware or modem.
Edit: Disabling WiFi Scanning stopped the errors. Root cause is still unknown, though. I've never had to disable that before...
Click to expand...
Click to collapse
Turning off WiFi scanning stops the constant switching of WiFi. I tried removing the system settings permission from all the apps that had it (even the Google app) but it doesn't seem to have any effect.

I am seeing the same issue, I did not touch my screen in the following video
Video on Dropbox
disabling "Wi-Fi scanning" in location helps.

Hi,
I had the same issue before.
What I did was(Not sure how its displayed in english):
-Settings;
-Backup and Reset
-Reset network settings
I was having constant disconnections from wifi and it solved it.
Give it a try

DiogoCDS said:
Hi,
I had the same issue before.
What I did was(Not sure how its displayed in english):
-Settings;
-Backup and Reset
-Reset network settings
I was having constant disconnections from wifi and it solved it.
Give it a try
Click to expand...
Click to collapse
Did the above solve the problem?

I am using G930F in US on ATT and encountered the same problem in past few days, where wifi kept turning on and off. Was searching this post, and found out that if i turn off wifi scanning i can get wifi to stay off (when i switched off ) and wifi on (when switched to on) and not flip back and forth.
go to settings.
- click on search
- type in improve accuracy
- select from choice
- turn off wifi scanning
Try that and hope that helps.

I have the same problem. The side effect is that it will drain the battery really fast.
As others have mentioned, after I have turned off the WiFi scanning in the location setting the problem is temporarily gone. However it should not be the solution as I really need the WiFi location to work. I don't know what is causing the bug.
P. S. I only see this problem starting from the last week or so. I leave the WiFi scanning location function on since I have bought the phone in May. Mine is Exynos version.

several Samsung devices have this issue.
I and several others have it on a note 4, and some people have also reported having this problem on S6 variants.

The problem is Google Play Services 10.0.84 version. Another cell phones with this version of Google Play Services have the same problem (ej. Google Pixel phone) but not all.

The problem is the Android Wear App. Deinstall the app and wifi works perfekt.
This issue starts with the last update of the wear app.
Hope i could help you.

Gerry65 said:
The problem is the Android Wear App. Deinstall the app and wifi works perfekt.
This issue starts with the last update of the wear app.
Hope i could help you.
Click to expand...
Click to collapse
I tried uninstalling Android Wear but it didn't make a difference. The wifi kept switching on and off.

As mentioned above, it's Google Play Services 10.0.84. Just disable wifi scanning until there is an update. Hopefully google won't take too long to push a fix.