WiFi keeps disconnecting after the nougat update. - Verizon Samsung Galaxy Note5

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

Related

WiFi *profile* keeps getting disabled?

I've noticed that the profile for my home wifi network keeps getting disabled. Usually, I'll leave for a bit, then come back and about half the time it never reconnects. When I go into the wifi list, it's marked as disabled. I enable it and it works fine from that point unless I leave again. It's my understanding a profile will get disabled when it cannot connect to a network for some reason, but clearly it can. My G2 and SGS never have this problem. Is this a setting somewhere? Thanks...
I am having this same issue. I dont know how to fix it
This is more serious than I realized! I just got disconnected randomly even while staying in perfect coverage. Not only does it disconnect, but it DISABLES the connection and won't reconnect again unless I manually tell it to. I rely 100% on WiFi calling while home and now I'm missing all kinds of calls and texts because WiFi is disconnected...
I'm hoping this is just is a software issue that can be resolved pretty quickly, officially or unofficially...
This phone has like 10 legit problems already. Tmobile needs to hurry up with the updates or the refunds will kill them.
It might help if you talk about the router you're using. I have a Netgear N600 and haven't had any Wi-Fi issues either connecting, staying connected, or automatically reconnecting. Bluetooth on the other hand...
BarryH_GEG said:
It might help if you talk about the router you're using. I have a Netgear N600 and haven't had any Wi-Fi issues either connecting, staying connected, or automatically reconnecting. Bluetooth on the other hand...
Click to expand...
Click to collapse
It's a Linksys WRT610N. Very modern and very stable router. There's no reason this phone should have any problem with it. I literally have a G2 and SGS sitting side-by-side with the G2x and only the G2x has this problem. The SGS is Froyo and the G2 is Gingerbread. I also have a slew of other wireless (on both 2.4ghz and 5.8ghz bands) and wired clients connected that all have zero issues. I don't know why it would work on one router and not the next...
Are you using WPA2-AES encryption or something else?
zaventh said:
Are you using WPA2-AES encryption
Click to expand...
Click to collapse
Yes. And you're right, the phone is very temperamental across a number of areas.
Did you set up your wifi to never go to sleep? Cause if you havent - it disconnects every time you turn off the screen.
In order to do that, go to Settings=>Wireless & Networks=>Wi-Fi Settings=> click on the "menu" button on your phone=> Advanced=> Wi-Fi sleep policy=> and choose Never.
I did that, and my wifi calling is flawless ... and I rely on it pretty much all the time that I am at home (thanks for that stupid t-mobile signal)
I have the same issue and the setting I have by default to Never go to sleep... Also, has nothing to do with router as any of my other phones have this issue including Nexus One.
Did by any chance any of you with this issue restore some Titanium Back-ups? Because when I restored mine from a back-up of my 1st G2x (exchanged) I also restored the previous wi-fi settings and after that the wi-fi wouldn't work correctly. I did a factory reset and it fixed the problem.
Edit: If all else fails, then try a factory reset. I know it sucks, but it could fix everything.
Sent from my LG-P999 using XDA App
I'm having issues with this as well. Wifi set to never sleep, I haven't restored any apps. I constantly lose connection. I've tried the factory reset thing etc. and it doesn't help.
I can connect to my wireless g Linksys access point but not my airport extreme ... my Linksys is open my ape is not(I realize I wrote ape LOL)
Sent from my LG-P999 using Tapatalk
WiFi seems to be losing dns services
I have the same WiFi problems and while a factory reset clears the problem
temporarily and changing the WiFi sleep setting to never is an immense help
once it's gone off-line I can't get it to come back.
I have noticed that if it has a cached dns lookup to an ip address that that
ip address is still accessible. So if you can get OTA data live, look up google.
Switch to wifi, google is still accessible and you can do queries but you can't
click through on the links because the dns lookup fails.
I've fiddled with killing myaccount, suggested elsewhere, without success.
Unless there is some robust configuration change that pops up soon I suppose
I'll have to return it...
boylan said:
I have the same WiFi problems and while a factory reset clears the problem
temporarily and changing the WiFi sleep setting to never is an immense help
once it's gone off-line I can't get it to come back.
I have noticed that if it has a cached dns lookup to an ip address that that
ip address is still accessible. So if you can get OTA data live, look up google.
Switch to wifi, google is still accessible and you can do queries but you can't
click through on the links because the dns lookup fails.
I've fiddled with killing myaccount, suggested elsewhere, without success.
Unless there is some robust configuration change that pops up soon I suppose
I'll have to return it...
Click to expand...
Click to collapse
Did you also uninstall market updates and freeze the market updater?
It got mine working again without any problems. Sucks that this has to be done to get wifi to work properly.
I've frozen MyAccount and WiFi calling and it's working at the moment.
Truely I was a little tired and forgot about the market updates until I got
back here.
Insane that one has to do something like this for such a basic feature.
I mean who is going to use the OTA networking when wifi is available?
Let alone the cost issues. I went from 880kbps to 10100kbps going from
OTA to wifi.
This device must have rushed out the door.
Useless at any speed
So I've uninstalled the updates to and FROZEN:
My Account
Market Updater
WiFi Calling
AppPack
and the phone is still trippy. I've discovered also (via the engineering menu)
that the networking ping test fails - "network unreachable". The wifi
data looks good but it doesn't show the current gateway or dns configuration
information.
I'm at a loss for what to try next. Anyone got any suggestions?
Is there something like a netstat android app?
I am having the SAME issue as well as the OP..... =/
wifi recovery
Too soon to say that this is a consistent work-around but I'm
having some short term luck with
rebooting the phone (remove battery) in Airplane mode
enabling wifi
turning airplane mode off
Not sure if the battery pop is necessary. I suspect it's not.
I also suspect that freezing/deinstalling the various updates
is pointless.
Probably the whole work-around is to change the
Wi-Fi sleep policy to never:
settings->wireless & network settings->Wi-Fi settings->advanced
and use the airplane/wifi enable reboot sequence.
If someone has a permanent work-around based on precise setup
sequence and freezing applications I'd like to hear it - I think I've
followed the several posts on this topic and that path is unreliable but
it never hurts to be wrong.
dj75728 said:
Did by any chance any of you with this issue restore some Titanium Back-ups? Because when I restored mine from a back-up of my 1st G2x (exchanged) I also restored the previous wi-fi settings and after that the wi-fi wouldn't work correctly. I did a factory reset and it fixed the problem.
Edit: If all else fails, then try a factory reset. I know it sucks, but it could fix everything.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine does this and I never restored any system data. I only restored apps.
Strange.
I use WiFi calling at work with no problems. It is a Netgear router. I haven't had problems at home with my Linksys router either.

Wifi connection connected but won't load pages

It said connected in the wifi setting and it shows bars but it just won't load any website in the browser .. anyone got a fix for this?
I have the same issue. Tried different combinations of restarting wifi, turning on/off cell data, on/off wifi calling, etc... all with no result. I've also tried on different networks (both public and private)-- it'd start working for a while and then all of a sudden stop and never work again.
Seems similar to the problem here: forums. t-mobile.c om/t5/T-Mobile-G2x/G2x-WiFi-DNS-issue-not-the-4G-switching-one/m-p/831439 (sorry there's a new user no link restriction)
Does anyone have any suggestions?
Thanks
coldest~~~ said:
It said connected in the wifi setting and it shows bars but it just won't load any website in the browser .. anyone got a fix for this?
Click to expand...
Click to collapse
is it specific to the browser or can you not move any data?
Idk, whenever I have had problems connecting to the tmo network, which is a separate issue.. it was always that wifi calling was still on even tho wifi was turned off. Every time I had probs w/ data on tmo network, it's been wifi calling.. Your case seems to be diff tho.
Is it specific to just your network or all other networks? Try shutting off wifi, reboot... then turn it on again? Idk.. just tossing out ideas.
Some found the root cause and I am posting his finding as I do have the same issue and can reproduce the error:
I think I have discovered a new WiFi-related bug in the G2x's software. I have witnessed this occurring on my phone, and have also reproduced it on a store demo unit. I believe it is unrelated to the switching-to-4G problem people are having with the My Account app, since it occurs even if I have set up the Google account on first boot after a factory reset.
The details of the problem are:
- Every so often, the phone randomly gets stuck in a state where it is not able to initiate any new connections that are made using a DNS name. Attempting to navigate to a web site, h**p://w*w.google.c*m for example, will result in a generic failure message.
- However, attempting to connect directly to an IP address instead of a DNS name works perfectly. For example, navigating to 74.125.225.16 will work fine and will load the Google home page.
- When the phone is in this state, using a DNS lookup tool such as "DNS Lookup" from the Marketplace *will* work, even when using the default DNS server address that the DHCP server is giving the phone.
- The problem has occurred for me when data is off and WiFi is on. I do not know if data being off is a requirement, since this is the way I usually run the phone, so this may be coincidental.
- Switching WiFi off and back on again will *sometimes* work to solve the problem, but sometimes will not. When this doesn't work, switching WiFi off, then switching data on, then back off again, and then finally switching WiFi back on again will occasionally correct the problem. However, I have seen situations where none of these things worked, and the only way to get DNS working again was to factory reset the phone.
- I haven't figured out the exact pattern yet, but this issue seems to occur when the phone has been inactive for a certain period of time. I have often discovered that the phone is in this state upon waking up in the morning after leaving the phone on the charger overnight.
- I have, however, found a method to reproduce the problem that seems to work fairly consistently:
1. Turn WiFi on, and data off.
2. Power cycle the phone.
3. When the phone starts up, start the browser and attempt to browse to w*w.google.c*m. It should fail.
4. Try to browse to 74.125.225.16. It should work.
Just wanted to get this issue in the forums to see how many others have been noticing the same thing.
I know that once the device has less than 10% battery it automatically turns the WiFi off to save battery power. Were the devices this was happening on have a low battery?
Fully charged. It even happens when pluged in with the charger.
My Wifi wouldn't even work if I froze it with Bloat Freezer. It has to run in the background for wifi to work. I found that Wifi can get really inconsistent with it disabled.
smartloom said:
Som
- I haven't figured out the exact pattern yet, but this issue seems to occur when the phone has been inactive for a certain period of time. I have often discovered that the phone is in this state upon waking up in the morning after leaving the phone on the charger .
Click to expand...
Click to collapse
Same problem here. After about 30 minutes of being idle, as soon as I pick up the phone it tries to connect 2g/4g. The log are saying theres no connection, so it appears that wifi its going to sleep and not waking up so android is trying to connect 2g/4g
Really starting to be a pain
I have frozen the bloat, and I think the problem is getting worse.
Toggle airplane mode is a quick workaround to get wifi to wake up
Sent from my LG-P999 using XDA App
Same thing happened to me, I did 2 factory resets, and it seems it has been fixed, don't really know what causes it.
Sent from my LG-P999 using XDA App
This may or may not be related, but...
It looks like I found a hacky fix for the dns/wifi/4g bug: install "Set DNS" from the market.
Now when I go into market, and display my downloaded apps, it jumps from wifi to 4g then back to wifi as it should, fast.
Whether or not it should even do go to 4g is debatable, all I can say is my 2 Galaxy Tabs had the same behavior.
If everyones connectivity issues are really due to the DNS settings getting wiped out, then this will work around the problem until I/we find the location of the actual bug.
Would you guys having this problem also post it here?
http://www.lgforum.com/forum/boards/general/lg/topics/g2x-wifi-problems
Thanks.
I figure the more people that post there, the more the chances are of LG fixing it quickly.
Work around:
enable airplane mode
reboot
enable wifi
wait a few seconds after the wifi connects, background crap stops
disable airplane mode.
The set dns app looks like a winner. Haven't tried it but that's what's
wrong.
The freezing and other suggestions are all useless crap.
Updates...
I did a factory reset and installed JuiceDefender (I don't know which one worked) but it seems to be all fine now... will update if things become problematic again
I've been having this problem as well. I've always been able to fix it by toggling WiFi off and back on again. I downloaded SetDNS and when it happened again last night I tried that and it worked great.
Glad to see it's a software problem and not a hardware problem.
same problem here. hopefully it won't happen in cyanogen mod
boylan said:
Work around:
enable airplane mode
reboot
enable wifi
wait a few seconds after the wifi connects, background crap stops
disable airplane mode.
The set dns app looks like a winner. Haven't tried it but that's what's
wrong.
The freezing and other suggestions are all useless crap.
Click to expand...
Click to collapse
This fixed the problem, at least until the next time I reboot my phone
How do you use SetDNS? This software bug in G2X reboots my router (DGL-4500) sometimes.
Question bout SetDNS app
Does the phone have to be rooted to use the setdns app? I try to use it but it says "Cannot get root. App will not function."

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 issues

Anyone else with WiFi issues? 90% of the time I have no problems but 10% of the time it seems the connection hangs. Data transfer will pause and resume 30 secs or a minute later. I have tested this with speed test and was able to reproduce. Happens on both my 2ghz and 5ghz networks. I am rooted but I'm going to do a factory reset to see if issue persists. I do know it's not my WiFi as my other devices have no trouble. But this is quite annoying.
Sent from my HTC6525LVW using Tapatalk
murryrulz said:
Anyone else with WiFi issues? 90% of the time I have no problems but 10% of the time it seems the connection hangs. Data transfer will pause and resume 30 secs or a minute later. I have tested this with speed test and was able to reproduce. Happens on both my 2ghz and 5ghz networks. I am rooted but I'm going to do a factory reset to see if issue persists. I do know it's not my WiFi as my other devices have no trouble. But this is quite annoying.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Are you by chance using an Apple router or access point? For some reason, they don't seem to play well with Android devices, including my M8. I've had a similar experience with 4 Android devices and 2 different Apple routers. The devices continuously disconnect and reconnect.
No I'm using an Asus ac66. The funny thing is the connection doesn't drop. It always says connected. The data just stops flowing and then starts again. For example I'll run a speed test and the download will pause then start up again. Very odd. Never had a phone do this before
Sent from my Nexus 7 using Tapatalk
I've got an Apple Airport Extreme. I also have several Android devices. Have had many that I no long have or use. I've never had any problem with my wifi on any of them. I have to wonder if your problem isn't related to something else. Or, possibly your router needs to be replaced. Might be a matter of settings too. But, like I said, I've never had any problems with mine.
Within the "Advanced Wi-Fi" settings there is an auto-enabled option called "Wi-Fi Optimization" which minimizes battery usage when Wi-Fi is on. I assume this monitors for extended periods of inactivity (screen off, no active downloads, etc.) and temporarily disables/hibernates Wi-Fi activity.
I've kept this option enabled and haven't had any issues so far, but maybe you could try testing with/without this setting enabled? Another thing to try would be checking highly-used radio channels in your area with an application like InSSIDer and making sure your router is broadcasting on a low-use channel. I see no correlation with the radio channel and your new M8, but it's worth a try
insertnewsn said:
Within the "Advanced Wi-Fi" settings there is an auto-enabled option called "Wi-Fi Optimization" which minimizes battery usage when Wi-Fi is on. I assume this monitors for extended periods of inactivity (screen off, no active downloads, etc.) and temporarily disables/hibernates Wi-Fi activity.
I've kept this option enabled and haven't had any issues so far, but maybe you could try testing with/without this setting enabled? Another thing to try would be checking highly-used radio channels in your area with an application like InSSIDer and making sure your router is broadcasting on a low-use channel. I see no correlation with the radio channel and your new M8, but it's worth a try
Click to expand...
Click to collapse
I have the same issues. and ive turned off wifi optimizaiton, ive set my wifi control frequency to 149, ive tried to switch between 2.4 and 5ghz. i feel like my issue is with the phone not picking up the wifi signals very well... we live in a brick house, and the asus ac68u sits right in the middle of th house, and my room is only right around the corner. everyone elses phone picks up 5ghz or 2.4ghz frequency fine in my room, even my gf's M8 (we bought ours from verizon same time for the deal). i literally get wifi in my rom 10% of the time or its choppy and slow. so everytime im in my room i have to switch to cellular :|

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.

Categories

Resources