Database Info

Nexus 5 Wifi Issue

So I've had my Nexus 5 for roughly around a month and I hadn't experienced any issues others have had with wifi not connecting until now. My N5 will show im connected to my home wifi with full bars, but going into quick settings shows it to be orange. Suggesting there's no data transfer, I cannot use any internet based apps with wifi. I've tried some suggestions, switching my router off then on, rebooting the phone, turning some settings off in the advanced panel in wifi settings. All have failed.
I was just wondering if anyone else has this problem and if anyone has a fix to it.

Dillllz said:
So I've had my Nexus 5 for roughly around a month and I hadn't experienced any issues others have had with wifi not connecting until now. My N5 will show im connected to my home wifi with full bars, but going into quick settings shows it to be orange. Suggesting there's no data transfer, I cannot use any internet based apps with wifi. I've tried some suggestions, switching my router off then on, rebooting the phone, turning some settings off in the advanced panel in wifi settings. All have failed.
I was just wondering if anyone else has this problem and if anyone has a fix to it.
Click to expand...
Click to collapse
There was a thread around here somewhere that suggested turning off your mobile data helped fix this problem, I think it was in the N5 General forums.....here it is:
http://forum.xda-developers.com/showthread.php?t=2550690
Don't know if it'll help or not, just saw your thread and had just looked at the other one, figured I'd toss it out there.

Thanks for the reply, just tried that solution but still no luck.

I have a similar problem except that there are phases of wifi not working.
Sometimes I would have around 20-30 seconds of WiFi not working and there would be no data transfer.
Speeds are still fast when it is working however.
I played a little with only using mobile data and no wifi, and everything worked. (Small sample size however).
Seems like this is a WiFi only issue.

So somehow overnight the wifi has managed to fix itself, will report back if the problem returns.

The issue with the wifi returned unfortunately.

Dillllz said:
The issue with the wifi returned unfortunately.
Click to expand...
Click to collapse
Don't know if you've tried this but change your WiFi frequency band in advanced setting to either "5 GHz only" or "2.4 GHz only," whatever your router uses. Might be worth a try.

Thanks for the help, but I've tried changing some settings in advanced wifi settings but it hasn't worked. Even what you recommended I've tried that before and it didn't work.

wifi issue
Also I have the same issue - Im connected to router by wi-fi, home and work and time by time (5x a day) wifi stops working. Wifi is enabled in settings, but there is no connection. Restart the cellphone helps, but after that, maybe an hour, it appears again.
Issue was in 4.4 and still appers in 4.4.1.
Yet did not found how to solve it.

I have the same issue on my gnex running shiny 4.4, but I also had the same issue on 4.3. Tried the wifi options, nothing worked. Unfortunately, no solution for this device that has to last one more week. The double swipe down and tapping wifi gets the connection back, but it is only a work around.
The N5 connects seamlessly to my home and work wifi. A few days ago, I flashed the hammerhead factory image, TWRP and the 4.4.1 update.

Nexus 5 - wifi not switch automatically from data
pcloadletter1 said:
I have the same issue on my gnex running shiny 4.4, but I also had the same issue on 4.3. Tried the wifi options, nothing worked. Unfortunately, no solution for this device that has to last one more week. The double swipe down and tapping wifi gets the connection back, but it is only a work around.
The N5 connects seamlessly to my home and work wifi. A few days ago, I flashed the hammerhead factory image, TWRP and the 4.4.1 update.
Click to expand...
Click to collapse
Hey,
I have the same problem with 4.4.2.(factory rom, no root or not unlocked). Sometimes the wifi not works and get orange. I must put airplane mode to fix it. Its annoying.
But as well happens to me:
When I go out from office or home (where I have wifi connections saved in phone) the phone automatically switch to data plan from carrier. But when I come back the phone stays with data and there is not automatic switch to wifi. Sometimes it help to put wifi off or always airplane mode on/off for a while.
I do not know if it is normal behave of android but I would like have automatic switch to wifi.
I tried to change wifi details (changing bands, etc.) but not helped.
Please help. Thank you.

Is custom ROM or kernel will fix it??

For some unknown reason, as soon as I updated my router's firmware, the problem disappeared.

Updated Android 6.0 solved the issue
Dillllz said:
So I've had my Nexus 5 for roughly around a month and I hadn't experienced any issues others have had with wifi not connecting until now. My N5 will show im connected to my home wifi with full bars, but going into quick settings shows it to be orange. Suggesting there's no data transfer, I cannot use any internet based apps with wifi. I've tried some suggestions, switching my router off then on, rebooting the phone, turning some settings off in the advanced panel in wifi settings. All have failed.
I was just wondering if anyone else has this problem and if anyone has a fix to it.
Click to expand...
Click to collapse
So I had the unfortunate experience of having my wifi go down while on vacation and for 3 weeks I spent a good chunk of time wiping and reinstalling multiple versions from Cyanogen, Paranoid android and 4.4 - 5.1 to no avail. I just did another factory wipe today and installed the new Android 6.0
The Finger Pointing Game is OVER
Read through 30+ pages of other android users with similar experience and some people send their units back to LG and some even managed getting a new handset. There was never any hardware issues with my unit I just couldn't turn on the WiFi but after the install WiFi works? Guess next time you push a software update to our Phones CHECK YOUR SH*T google and Maybe DON'T Take 3 months to FIX your F*CK Up.

I have a similar issue. Since Lollipop my phone almost never automatically connects to my WiFi anymore. What's wrong?

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.

[Q] Wifi issue ! (Lollipop 5.1)

Hi All,
I got the Lollipop 5.1 OTA 2 days ago and installed it - everything went smooth and the phone working fine...
But I noticed that if I reboot my router (or turn it off / on again) the Wifi don't reconnect unless I turn on the screen (the second I turn on the screen the wifi connect normally).
I didn't have this issue with Lollipop 5.0.1
P.S.
I know that this is happening because I have a led on my router telling me if any of my Wifi devices is connected or not. And to make sure I also entered the router settings to see if my phone is connected or not.
Anyone noticed that issue with the new lollipop 5.1 ?
Cheers,

I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same

skorzo said:
I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same
Click to expand...
Click to collapse
I've got some similar behaviour here, both when updated from 5.0, and with a fresh install from the factory images. When I arrive at a place with known WiFi, the phone only connects once I turned on the screen. After that, it stays connected until I move out of range and back again.

It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
That being said, I have my wifi set to always stay connected, and I've seen it not connected when I turned the screen on, then connect a couple seconds later. So, there's that. Curious how often it does that.

Aerowinder said:
It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
Click to expand...
Click to collapse
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?

dadrc said:
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?
Click to expand...
Click to collapse
My "research" has led me to believe this is the case.

Anything in terms of a workaround?
I came across those settings in the developer options (see screenshot), especially the "Always allow WiFi Roam Scans" looked promising. Been playing with them, but so far no luck.

Hi All,
exactly the same issues as yours guys are happening since I received the OTA 5.1 and installed it !
I Guess something messed up with this new update in regard of the wifi... as you mentioned.
If you come across a workaround or a confirmation from "Google" please share.
Cheers,
(With almost everyone nowadays having data ..it is difficult to notice such a behavior due to the fast wifi/data switching)

I have seen this happen as well. My battery graph will even show a missing area for WiFi indicating it turned itself on and off twice within a few hours and then stayed on after that.

Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.

Tasker will help you

OsBuilder said:
Tasker will help you
Click to expand...
Click to collapse
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.

dadrc said:
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.
Click to expand...
Click to collapse
I'm sorry, but my phone is now in the service center , and press that I do not remember specifically . The idea is that when you disable wifi, a time interval is forced to connect to a particular network . Look presence on the internet , here is full of instructions.

dadrc said:
Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.
Click to expand...
Click to collapse
http://www.androidpolice.com/android_aosp_changelogs/android-5.1.0_r1-to-android-5.1.0_r3-AOSP-changelog.html
Almost all of the changes on these different builds are SIM related for specific carriers.
LMY47I was only released to LGD821 devices with SIM cards from Indian and Australian carriers

Same problem here. I am slowly losing faith in Google. Get the frickin basics going guys!!!
Back to my 5.0.1 build.

I've gone back to 5.0.1, too. Pity, except for this I was pretty happy with 5.1. Maybe 5.1.1 will actually be usable.

Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.

fabiastik said:
Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.
Click to expand...
Click to collapse
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.

MindLeader said:
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.
Click to expand...
Click to collapse
This trick didn't work.

I have this proble too

WiFi plaguing Android Marshmallow

After using 6.0 for a day or so, I noticed that the WiFi was draining huge amount of juice from the phone, even taking the top spot on the battery chart. This seems to happen even if the WiFi is turned off.
http://i.imgur.com/X2YoNvv.png
So how can we fix this? Well, we'll have to go through bunch of settings to do so. It seems like Google deliberately hid this deep inside location settings. This is how we can "temporarily" fix this issue: Head to Settings -> Location -> Click those 3 dots at the top right corner -> Scanning -> Turn off both WiFi scanning and Bluetooth scanning.
Even with this "fix" I noticed that it keeps draining battery life for no reason, not as much, but the problem still exists. This shouldn't happen! Especially when Marshmallow was built around battery life improvements. The fact that this bug has been causing problems since M Preview #3 shows either Google "missed" this chaos of a bug (or) only cares about that juicy location data. This should be a straightforward-user-friendly option, not one that is buried behind buttons and menus.
It's not a bug, it's a feature

Had the same issue after flashing the factory image. So I flashed 5.1.1 again booted the phone then rebooted into recovery and sideloaded the 6.0 OTA. Booted the phone and preformed a factory reset. Now I don't have that problem.

jdawg0024 said:
Had the same issue after flashing the factory image. So I flashed 5.1.1 again booted the phone then rebooted into recovery and sideloaded the 6.0 OTA. Booted the phone and preformed a factory reset. Now I don't have that problem.
Click to expand...
Click to collapse
Pics

im currently having this exact issue.

I had same problem also tried disabling Wi-Fi scanning and automatically turning off Wi-Fi when idle but it did not give better results.
Just today i switched phone Wi-Fi to 2.4 GHZ only mode - this workaround seem to work, no drain any more.

DaimonPl said:
I had same problem also tried disabling Wi-Fi scanning and automatically turning off Wi-Fi when idle but it did not give better results.
Just today i switched phone Wi-Fi to 2.4 GHZ only mode - this workaround seem to work, no drain any more.
Click to expand...
Click to collapse
Thanks for that. This actually sounds possible.
On the first day when I flashed 6.0 with OTA, I really felt that the battery life has extended.
Then I switched through a lot of settings and also ended up with 2.4 and 5 (auto) on wifi.
Disabling all wifi related options did not help at all....
Will try this out now. :good:

I'm having severe delays with my wifi on my N5 with 6.0. In speedtest I'm pushing over 90mbps on 5GHz band, but it takes over 30 seconds to load a webpage/ apps. It's not gradually loading it's almost like a stall. Then after the page or app loads instantly. Why is this happening? Is it a severe delay to the server? IDK wtf is going on... I don't have battery drain issues from the wifi this is a different issue.

Same problem... Scanning and wifi off! Wifi drain. At first sight problem only seems to manifest while no wifi available. Tried the 2.4ghz only and seems to reduce though not eliminate the problem...

DaimonPl said:
I had same problem also tried disabling Wi-Fi scanning and automatically turning off Wi-Fi when idle but it did not give better results.
Just today i switched phone Wi-Fi to 2.4 GHZ only mode - this workaround seem to work, no drain any more.
Click to expand...
Click to collapse
Works indeed better.. Wifi disappears from the Battery Usage chart, but when it was supposed to went on idle while I put it away, draining started again it seems.
There is a fat bug in the Power-Management in Android M 6.0 final, if you ask me...

All, please check whether it is actually drain or merely incorrect reporting of battery statistics. Symptoms seem similar to this thread
Remember battery 'drain' is where the level is falling at an abnormally fast rate. If WiFi is merely appearing at the top of the stats, but your battery life is actually fine, then it's not drain.
You need to leave your phone over several hours, and take measurements. When investigating or troubleshooting, then logically change one thing at a time, and re-measure again over a long period of time for comparison.

eddiehk6 said:
All, please check whether it is actually drain or merely incorrect reporting of battery statistics. Symptoms seem similar to this thread
Remember battery 'drain' is where the level is falling at an abnormally fast rate. If WiFi is merely appearing at the top of the stats, but your battery life is actually fine, then it's not drain.
You need to leave your phone over several hours, and take measurements. When investigating or troubleshooting, then logically change one thing at a time, and re-measure again over a long period of time for comparison.
Click to expand...
Click to collapse
There is definitely a drain problem... because of Google Play Services not letting System into sleep mode and pulling constantly on Wifi...
That is how I think it comes to the problem.
Mine is now running smoothly, after I went into: Settings > Apps > Google Play Services (and maybe also Google Play Store) > hit menu ... > Deinstall Updates > Restart
If you go back into Play Store later on, it updates to the current version.
I also reseted the Network Settings... somewhere.

I tried what was suggested by others in this thread and din't have any luck. I posted how I solved the issue here:
reddit dot com/r/Nexus5/comments/3npesh/wifi_drain_persists_in_android_m_final_release/cvwo3x5

I did another modification. In Location settings I changed mode to device only (GPS).
So together:
- set WIFI to 2GHz only
- disable wifi scanning in location settings
- set location scanning to device only (GPS)
- set WIFI to automatically turn off in idle mode (advanced wifi settings)
WIFI is no longer main battery consumer (screen is now as expected). I'm not sure which of those is crucial but they all look like may improve things a bit (and together give big difference)

.

I thought this was bugging me too. WiFi is top of the list in battery stats. But then I disabled ElementalX gestures (doubletap2wake in my case) and that improved things a lot. Even though WiFi is still reported as the biggest power user.
This may be just me and of course it could always be better, but it might be worth giving this a try.

I'm having his exact issue. It's with any resources I access through WiFi, from sftp to ftp to web data, internal and external lans, internet, etc. It's definitely a 6.0 issue. I had it on preview 3 as well, and it was bad enough make me downgrade at the time. Now the official release is out and doing the same thing, I'm REALLY hoping they can fix this soon. It's practically unusable if you don't have dial-up time to kill.

Check my previous post - it completely fixed problem for me

I've experienced the same issue, after a week from the ota update (week in which I had a great battery lifetime), the problem arose out of the nowhere, and after searching the web for a workaround, it seems that putting the wifi in 2.4 ghz only made the trick...
Really hope that google will fix this soon...

eyesore said:
There is definitely a drain problem... because of Google Play Services not letting System into sleep mode and pulling constantly on Wifi...
That is how I think it comes to the problem.
Mine is now running smoothly, after I went into: Settings > Apps > Google Play Services (and maybe also Google Play Store) > hit menu ... > Deinstall Updates > Restart
If you go back into Play Store later on, it updates to the current version.
I also reseted the Network Settings... somewhere.
Click to expand...
Click to collapse
This is the only thing that worked fully for me. Getting it to 2GHz made it a little bit better but didn't actually solve it. Uninstalling updates from play services and play store solved it for good and I didn't have to flash 5.1.1 and ota update.
:good:Thanks eyesore!

Hello. I have this issue... I disabled localisation through WiFi and I have also done a network settings reset but the problem still persists (not too much as before -45%- but around 25%).
How can I solve?

[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.