Database Info

Random WiFi slow down

I'm noticing strange WiFi issues, in that my data speeds keep slowing down to a standstill for no reason.
In fact, when I first booted the device, and started to install my apps, I wondered why there were downloading so slowly, so I installed "SpeedTest" and sure enough my data speeds were like 1.5mbps. To test that my network hadn't just suddenly gone crazy, I ran the test from my laptop and that confirmed normal speeds.
To remedy this, I changed my advanced wifi settings to just use the 2.4 ghz signal, then changed my router settings (a BT Home Hub 3) from smart wireless (auto changes channel to the "best" channel to just remain on that already pre determined best channel.
I then immediately saw an improvement, as it was downloading now at about 27mbps... and so I thought I'd cracked it.
Apparently not.... It regularly goes back to downloading really slowly, and sometimes, messing with all those settings again doesn't do anything to improve the speeds.
Anyone else experiencing this, or has any insights as to what is going on? could it be a wifi driver issue, which may be rectified in later updates or baseband versions?
Here are some pics to give you an idea... all from the same network

Back to awesome after changing router security settings... I wonder how long it will last this time?
Sent from my Nexus 5 using Tapatalk

Exactly the same for me:
http://forum.xda-developers.com/showthread.php?t=2514501
I'm being sent a replacement but I can't say I'm convinced that one will be any different.
This issue occurred on my BT home hub, a tp-link access point, and the access points where I work.

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.

WiFi keeps disconnecting after the nougat update.

So far I love the nougat update. The main problem I have now is the WiFi disconnects when I turn off the screen. Really annoying because I listen to music a lot at work and ever since then the music will stop randomly so the wifi will have to connect again. Rebooting does nothing and I don't want to hard reset the phone to see if it will fix it. I have already gone through 3 different note 5 because of stupid problems. it seems like a battery saving thing. the old update power saving feature used to do the same thing and wouldn't let background apps use data when the phone was off and now its doing it on all the power settings. Not sure what to do.

first off, make sure your wifi is set to stay on always during sleep (at least just to test to see if that fixes things). That said, I've experienced this too (even with that setting set to "always") and hopefully I've fixed it but need more time (and others seeing this issue) to verify the fix and actually I really don't have a fix, just a work around.
I think what's going on is that wifi is being subjected to the battery optimization/power saving stuff and is disabled or whenever when the screen goes off. I've turned off all "power saving stuff" and now wifi seems to stay on.
---------- Post added at 09:56 AM ---------- Previous post was at 09:27 AM ----------
This seems to be a pretty broad issue with Nougat updates, on many device models. Some have suggested disabling the advanced wifi setting "smart network". I just did that and will see how it goes.

Yep same problem here and I have tired nearly everything but smash the phone so far.

I gave up trying to fix it. Nothing is working and I'm not wiping the system just for that. Mostly only happens at work on that wifi. Home doesn't really disconnect much.

painball64 said:
I gave up trying to fix it. Nothing is working and I'm not wiping the system just for that. Mostly only happens at work on that wifi. Home doesn't really disconnect much.
Click to expand...
Click to collapse
I'm thinking it happens for me when the phone tries to swap between to wifi access points of the same ssid... like at hotels and work.

Might be right but I know it has something to do with it going to sleep when my screen shuts off. I have the always on turned on but it only happens when my screen is off and I turn it back on

painball64 said:
I gave up trying to fix it. Nothing is working and I'm not wiping the system just for that. Mostly only happens at work on that wifi. Home doesn't really disconnect much.
Click to expand...
Click to collapse
I tried a factory reset to fix the Wi-Fi issue. It did nothing except waste my time. I've been with the Note series since the 2 and I'm done with them. I seem to also have some issue with the damn things. I've never been on IOS but I'm ready to take it for a spin.
Sent from my SM-N920V using XDA-Developers Legacy app

skunkle88 said:
I tried a factory reset to fix the Wi-Fi issue. It did nothing except waste my time. I've been with the Note series since the 2 and I'm done with them. I seem to also have some issue with the damn things. I've never been on IOS but I'm ready to take it for a spin.
Sent from my SM-N920V using XDA-Developers Legacy app
Click to expand...
Click to collapse
It's not your phone that's causing the problem it's Nougat itself and that and other reasons are exactly why I downgraded back to MM 6.0.1.. I have the firmware if you want to try that.

MrMike2182 said:
It's not your phone that's causing the problem it's Nougat itself and that and other reasons are exactly why I downgraded back to MM 6.0.1.. I have the firmware if you want to try that.
Click to expand...
Click to collapse
Thank you for the offer but I'm just gonna ride this out till September. Also thank you for being so helpful in the forums! I see you helping others all the time.
Sent from my SM-N920V using XDA-Developers Legacy app

MrMike2182 said:
It's not your phone that's causing the problem it's Nougat itself and that and other reasons are exactly why I downgraded back to MM 6.0.1.. I have the firmware if you want to try that.
Click to expand...
Click to collapse
Hello Mr Mike,
I'm to the point I can no longer stand this issue. I'm constantly getting an exclamation mark beside my wifi. The thing that boggles me the most is I don't see very many complaints when researching this issue. Am I missing something simple? I also know it's not my router. My wife has an S7 edge, my son uses my old Note 3, and my daughter has an eclipse tablet. None of those devices have this issue. I also know that nothing associated with wifi is set up to sleep. I'm at a loss!
I would hate to roll back to marshmallow but I'm seriously considering it! I'm constantly streaming music and this issue has made this a nightmare.
Any help to fix this would be greatly appreciated!!
Sent from my SM-N920V using XDA-Developers Legacy app

skunkle88 said:
Hello Mr Mike,
I'm to the point I can no longer stand this issue. I'm constantly getting an exclamation mark beside my wifi. The thing that boggles me the most is I don't see very many complaints when researching this issue. Am I missing something simple? I also know it's not my router. My wife has an S7 edge, my son uses my old Note 3, and my daughter has an eclipse tablet. None of those devices have this issue. I also know that nothing associated with wifi is set up to sleep. I'm at a loss!
I would hate to roll back to marshmallow but I'm seriously considering it! I'm constantly streaming music and this issue has made this a nightmare.
Any help to fix this would be greatly appreciated!!
Sent from my SM-N920V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do you have "smart network switch ebabled"? If you have no need for your mobile data to be enabled then disable it for as long as you're going to be near the Wi-Fi network so you can still receive texts and other stuff.. Just as a sort of test to see if your mobile data is fighting with your Wi-Fi data.. Also how many devices are connected to your Wi-Fi at the time the drop usually happens? For instance if I'm using most of the Wi-Fi data, like say your speeds capped at 10MB and your wife is downloading using almost all of the speed and then other devices will not be able to use that data and your phones going to think the Wi-Fi network is being slow and rather drop it altogether.

MrMike2182 said:
Do you have "smart network switch ebabled"? If you have no need for your mobile data to be enabled then disable it for as long as you're going to be near the Wi-Fi network so you can still receive texts and other stuff.. Just as a sort of test to see if your mobile data is fighting with your Wi-Fi data.. Also how many devices are connected to your Wi-Fi at the time the drop usually happens? For instance if I'm using most of the Wi-Fi data, like say your speeds capped at 10MB and your wife is downloading using almost all of the speed and then other devices will not be able to use that data and your phones going to think the Wi-Fi network is being slow and rather drop it altogether.
Click to expand...
Click to collapse
I've tried enabling and disabling smart switch and I have the same issue. I just tried forgetting the network and setting wi-fi back up fresh (after a factory reset, logging into my Samsung account sets up my Wi-Fi from previously saved settings). So far I haven't I disconnected.
The wife and kids do use some data, but not enough to warrant the issues I've been having. Once again thanks for a quick response. I will report if resetting the connection works.
Sent from my SM-N920V using XDA-Developers Legacy app

skunkle88 said:
I've tried enabling and disabling smart switch and I have the same issue. I just tried forgetting the network and setting wi-fi back up fresh (after a factory reset, logging into my Samsung account sets up my Wi-Fi from previously saved settings). So far I haven't I disconnected.
The wife and kids do use some data, but not enough to warrant the issues I've been having. Once again thanks for a quick response. I will report if resetting the connection works.
Sent from my SM-N920V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Enable developer options and under Network make sure nothing is on.. I don't know much about your type of setup but I have internet through the cable company but I use my own modem and Wi-Fi network built into it and manually control what devices can use, like what amount of speed, the IP address it can use and so on so I don't really have any issues like that.. I even have it setup so it's a white list type setup so nothing can be connected unless I personally add that devices MAC address.. Neighbors always trying to get free internet!!

Hey just found something. There's a way to check to see what's making the wifi disconnect. For me it is my gear s2. Goto wifi settings and under advanced, scroll to bottom and control history is there. I clicked on it and it said gear s plugin turned my wifi off. So I went and disabled the wifi setting on my watch and made sure to turn sync wifi profiles off also. It seemed to help at home but at work it's still happening but less often. I don't think this is the culprit for most but I have seen an improvement at least for me, it seems.

The only solution I've found is to stop buying Samsung. I went 3 months without sensors working and now my wifi is garbage. So long Samsung!
Sent from my SM-N920V using XDA-Developers Legacy app

MrMike2182 said:
Enable developer options and under Network make sure nothing is on.. I don't know much about your type of setup but I have internet through the cable company but I use my own modem and Wi-Fi network built into it and manually control what devices can use, like what amount of speed, the IP address it can use and so on so I don't really have any issues like that.. I even have it setup so it's a white list type setup so nothing can be connected unless I personally add that devices MAC address.. Neighbors always trying to get free internet!!
Click to expand...
Click to collapse
So I think I've narrowed the issue down. Yesterday I had a pool party and used a Brookstone speaker I have that plugs into the 3.5mm jack (I usually connect to several Bluetooth speakers I use). I did not have one single issue. Is it conceivable that using Bluetooth is causing my Wi-Fi issues? If so, any ideas on a fix?
Sent from my SM-N920V using XDA-Developers Legacy app

skunkle88 said:
So I think I've narrowed the issue down. Yesterday I had a pool party and used a Brookstone speaker I have that plugs into the 3.5mm jack (I usually connect to several Bluetooth speakers I use). I did not have one single issue. Is it conceivable that using Bluetooth is causing my Wi-Fi issues? If so, any ideas on a fix?
Sent from my SM-N920V using XDA-Developers Legacy app
Click to expand...
Click to collapse
It could yes since a lot of them use 2.4GHZ like Wi-Fi does but it's usually unlikely that Bluetooth would cause your Wi-Fi to get messed up because Bluetooth uses AFH which basically identifies bad channels (i.e. those that are already in use) Bluetooth technology nowadays uses what’s called spread-spectrum frequency hopping. That is, they rotate between 70 randomly chosen frequencies within their range, changing 1,600 times a second. That makes it unlikely that two devices will share the same frequency. But if you have your Wi-Fi unit in a spot where it has to pass between a bunch of walls before it gets to you that could also cause a problem since Wi-Fi signals don't like traveling through walls and other objects.

MrMike2182 said:
It could yes since a lot of them use 2.4GHZ like Wi-Fi does but it's usually unlikely that Bluetooth would cause your Wi-Fi to get messed up because Bluetooth uses AFH which basically identifies bad channels (i.e. those that are already in use) Bluetooth technology nowadays uses what’s called spread-spectrum frequency hopping. That is, they rotate between 70 randomly chosen frequencies within their range, changing 1,600 times a second. That makes it unlikely that two devices will share the same frequency. But if you have your Wi-Fi unit in a spot where it has to pass between a bunch of walls before it gets to you that could also cause a problem since Wi-Fi signals don't like traveling through walls and other objects.
Click to expand...
Click to collapse
Only 1600 times a second lol. Thanks, I'm going to try setting up a repeater to widen my signal.
Sent from my SM-N920V using XDA-Developers Legacy app

I'm pretty sure it's the new "app power monitor" battery saver that comes with Nougat. You can disable it by going to Battery> Advanced Settings> App power monitor > OFF. I recently tried it and it worked instantly and consistently.
It looked like a good idea... basically, it was an official Android version of "Greenify", only it repeatedly turns off wifi. What a joke. I turned that off, and now my wifi is stable, instead of turning off every 5 seconds.
Where do we go from here? I still want the battery savings... I guess I'll go back to Greenify and Package Disabler Pro...

I'll try that out thanks

Wifi on but not connected most of the time?

So i know this is a widespread problem because im on my 3rd pixel 3 and i have exactly the same problem on every one.
When im at home wifi is on but half the time it isnt connected, but as soon as i poke about on the wifi settings it connects. Its like its in some kind of sleep mode or something. I end up using all my mobile data whilst indoors a few meters away from the router! Ive had a pixel 3 since it came out and just cant seem to fix this problem.
Please tell me its a well known problem and some one has worked out a fix

I have not had that problem, but you may be able to reduce the mobile data usage by turning off "Switch to mobile data automatically" in Settings, Wi-Fi preferences.

gords78 said:
So i know this is a widespread problem because im on my 3rd pixel 3 and i have exactly the same problem on every one.
When im at home wifi is on but half the time it isnt connected, but as soon as i poke about on the wifi settings it connects. Its like its in some kind of sleep mode or something. I end up using all my mobile data whilst indoors a few meters away from the router! Ive had a pixel 3 since it came out and just cant seem to fix this problem.
Please tell me its a well known problem and some one has worked out a fix
Click to expand...
Click to collapse
This is no a known issue and if you're on your 3rd pixel i don't think had anything to do with the phone. It's most likely an issue on your router side. Have you tried resetting it?

Are you by chance using WiFi which is configured as hidden network? This is typically done by checking the checkbook next to "do not broadcast SSID" checkbox.
If you are connecting to such network, there is a setting you have to check while setting up that WiFi connection. It is hidden in normal dialog and so it is easy to miss. This was the root cause for similar issue I have seen on my Android devices including Pixel.

Im not using a hidden network. The weirdest thing is whenever i notice its not using wifi as soon as i pull down on the screen at the top it will connect. like its been caught out lmao. was using the phone just now, an alert comes up to tell me ive used 2gb of data. so i pull down on top of screen and theres an x on the wifi icon, its on but theres an x (probably means not connected to anything) then a second later it connects. i dont click on anything it just connects whenever i pull the top bar down to check. its been happily eating my data while on sat in doors but as soon as i check that status it connects! its damn crazy!
This is exactly what it does every time without fail whenever i notice there is no wifi.

Fix your router bro

gords78 said:
Im not using a hidden network. The weirdest thing is whenever i notice its not using wifi as soon as i pull down on the screen at the top it will connect. like its been caught out lmao. was using the phone just now, an alert comes up to tell me ive used 2gb of data. so i pull down on top of screen and theres an x on the wifi icon, its on but theres an x (probably means not connected to anything) then a second later it connects. i dont click on anything it just connects whenever i pull the top bar down to check. its been happily eating my data while on sat in doors but as soon as i check that status it connects! its damn crazy!
This is exactly what it does every time without fail whenever i notice there is no wifi.
Click to expand...
Click to collapse
The x on the wifi icon means you are connected to the router, but the router is not connected to the internet. Like everyone else, I think you have a router problem. Rebooting the router may help, but it may be time to replace the router.

Where are you located? It could be that your internet is unable to ping google servers. I have that issue whenever I clean flash, but I am in China so that is why.

This is not a widespread issue and as almost everyone has said, you have a router issue. It's possible that your router "sleeps" when nothing is trying to use it but that's just a guess. My suggestion, get a new router.

Android Wifi Calling issue

Hi,
I have noticed a strange behaviour using Wifi Calling. When I am away from home, and returning, it takes the phone about 15-20 mins for the wifi calling icon to show up and to be available. If I use airplane mode on/off it works instantly. I have seen this a few times on IOS as well, but seems more frequent on Android. So far tested on Samsung S22U and Sony Xperia 1 IV.
Also, today, while I was in a call, using VoWifi, the call dropped and when I looked immediately on the phone, vowifi icon was gone and it came back in a matter of 10 seconds.
Has anyone faced these issues and was able to narrow down the cause of it? My Wifi network does not have a firewall in place nor am I doing any sort of filtering. Changing between DNS servers makes no difference.

Turn off automatic WiFi network login on your phone and check again if it helped.

Hi, I do not have such option available. You mean wifi auto connect when in range?

Yes, because the phone can switch when the signal from the first router is weakening. (1)
Also, by setting up a manual connection, you can be sure that you are connecting to the router you want to connect to, not just any one. (2)

ze7zez said:
Yes, because the phone can switch when the signal from the first router is weakening. (1)
Also, by setting up a manual connection, you can be sure that you are connecting to the router you want to connect to, not just any one. (2)
Click to expand...
Click to collapse
So you're saying turn those 2 settings off? I just recently ran into this issue with my Wi-Fi conking out intermittently and I'm experiencing 20% battery loss over night. I'm thinking its bad hardware. I just turned off these settings. I'll report back if it helps.