Related
All,
I recently got a Lumia 900 (yesterday) and for whatever reason I am having a hell of a time getting it to connect to my WiFi network at home, and other places as well.
The problem is that when I go to connect to my WPA2 WiFi network, I get the error saying that the network did not respond, please try again.
I have rebooted my wireless AP, router, etc. Other devices such as iPad, iPhones connect fine.
Another thing I noticed is that I cannot connect to some Open WiFi networks either, the error comes back saying that the Network could not be reached.
I took it down to the AT&T store and it connected up to their secure network so they said isn't the phone, it must be my router..
Anyone have any ideas on this? The phone will connect (as seen at the AT&T store) to some WiFi networks, just not the ones I need... :\
Are you running n at home?
ragingclue said:
Are you running n at home?
Click to expand...
Click to collapse
Not 802.11n exclusively, no. I am running 802.11b, g and n mode. I tried just 802.11g and that didn't seem to make a difference.
That is odd then. I'm running g+n and not having issues.
I wonder if this is similar to the data connectivity issues some people were having?
I am running my Lumia 900 on g+n and not having any issues either online pinkish color on automatic brightness.
Sent from my SGH-I727R
Maybe it is try device because I have been able to connect to like any network.
Sent from my Lumia 900 using Board Express
Wintrmte said:
All,
I recently got a Lumia 900 (yesterday) and for whatever reason I am having a hell of a time getting it to connect to my WiFi network at home, and other places as well.
The problem is that when I go to connect to my WPA2 WiFi network, I get the error saying that the network did not respond, please try again.
I have rebooted my wireless AP, router, etc. Other devices such as iPad, iPhones connect fine.
Another thing I noticed is that I cannot connect to some Open WiFi networks either, the error comes back saying that the Network could not be reached.
I took it down to the AT&T store and it connected up to their secure network so they said isn't the phone, it must be my router..
Anyone have any ideas on this? The phone will connect (as seen at the AT&T store) to some WiFi networks, just not the ones I need... :\
Click to expand...
Click to collapse
I believe Nokia has fixed the wifi issue with an update.. ...
Have you checked if there is an update for your device?
Also try changing the The channels, maybe 11 or 13 and see if it makes a difference
I hope you have put the right password for your router
tfn said:
I believe Nokia has fixed the wifi issue with an update.. ...
Have you checked if there is an update for your device?
Also try changing the The channels, maybe 11 or 13 and see if it makes a difference
I hope you have put the right password for your router
Click to expand...
Click to collapse
I checked for an update and their isn't one, according to the phone and the updater.. I am definitely using the right password.
I will try the different channel thing though and report back.
Did you restrict Macs on your router?
Wintrmte said:
Not 802.11n exclusively, no. I am running 802.11b, g and n mode. I tried just 802.11g and that didn't seem to make a difference.
Click to expand...
Click to collapse
I've seen this before. The setting for mine requires mixed mode, if, any other setting is not set to default. Strange I know. But it's definitely a setting on the ap.
What brand is yours.
No MAC address filtering and I tried changing the channels, no luck.
Any other suggestions?
Update: Found an old LinkSys WRT54GL with the Tomato custom firmware I had loaded on it a few years ago.
Plugged it in, and the Lumia 900 connected right up.
I set my main wireless router (CenturyLink Q1000) to match the settings of just 802.11g and still, the Lumia would not connect.
I even tried re-flashing the phone with the AT&T Black [not ALIVE] firmware, still would not connect to the CenturyLink Q1000.
I cannot explain why the phone works with some access points, and not others. Not sure where else to go from here. The fact that I got it working with a completely different access point running an opensource firmware and not a commercial (centurylink) unit is baffling, albeit most frustrating.
Working fine with my Linksys E4200 (default settings) at home and some off brand router at work. WPA2, set for b,g & n. No problems on either router with my Surround or L900. Connects as soon as I get within range.
Sent from my Lumia 900 using Board Express Pro
Wintrmte said:
Update: Found an old LinkSys WRT54GL with the Tomato custom firmware I had loaded on it a few years ago.
Plugged it in, and the Lumia 900 connected right up.
I set my main wireless router (CenturyLink Q1000) to match the settings of just 802.11g and still, the Lumia would not connect.
I even tried re-flashing the phone with the AT&T Black [not ALIVE] firmware, still would not connect to the CenturyLink Q1000.
I cannot explain why the phone works with some access points, and not others. Not sure where else to go from here. The fact that I got it working with a completely different access point running an opensource firmware and not a commercial (centurylink) unit is baffling, albeit most frustrating.
Click to expand...
Click to collapse
I guess this confirms the Lumia 900 Black...is the best 900.
Wintrmte said:
Update: Found an old LinkSys WRT54GL with the Tomato custom firmware I had loaded on it a few years ago.
Plugged it in, and the Lumia 900 connected right up.
I set my main wireless router (CenturyLink Q1000) to match the settings of just 802.11g and still, the Lumia would not connect.
I even tried re-flashing the phone with the AT&T Black [not ALIVE] firmware, still would not connect to the CenturyLink Q1000.
I cannot explain why the phone works with some access points, and not others. Not sure where else to go from here. The fact that I got it working with a completely different access point running an opensource firmware and not a commercial (centurylink) unit is baffling, albeit most frustrating.
Click to expand...
Click to collapse
This centurylink brand doesn't sound too reputable.
xsever said:
This centurylink brand doesn't sound too reputable.
Click to expand...
Click to collapse
ISP give them out. But if most people are not having problems and the ones that are seem to be using a single manufacturers equipment then it would point to the equipment rather than the phone.
hx4700 Killer said:
ISP give them out. But if most people are not having problems and the ones that are seem to be using a single manufacturers equipment then it would point to the equipment rather than the phone.
Click to expand...
Click to collapse
Correct.. The modem is actually manufactured by ActionTec, and Centurylink gives them to you when you get their DSL service.
If the phone worked with another router, then i'd say it's the router.
Go with Linksys.
This is pretty strange so I thought I'd check here with people.
I got my new Sprint Note 2 today. When I was at home it connected to my wifi network and worked fine. When I got to work I connected it to our wifi network and the internet won't work. If I turn off wifi internet comes back.
Here's the kicker, I have my old iPhone right next to it connected to the work wifi network and it is connected fine to the internet. This is definitely going through wifi as I no longer have a data plan on that phone.
I checked with our IT admin who said that there is no need to "accept" a device on our wifi network. He also rebooted the network for good measure. After both phones lost the network (from the reboot) and reconnected the same thing happened. No internet from my Note but internet works fine on the iPhone. Restarting my Note doesn't fix the problem.
Any ideas? Thanks.
I have the same problem. Need help too.
Sent from my GT-N7100 using xda app-developers app
ks-man said:
This is pretty strange so I thought I'd check here with people.
I got my new Sprint Note 2 today. When I was at home it connected to my wifi network and worked fine. When I got to work I connected it to our wifi network and the internet won't work. If I turn off wifi internet comes back.
Here's the kicker, I have my old iPhone right next to it connected to the work wifi network and it is connected fine to the internet. This is definitely going through wifi as I no longer have a data plan on that phone.
I checked with our IT admin who said that there is no need to "accept" a device on our wifi network. He also rebooted the network for good measure. After both phones lost the network (from the reboot) and reconnected the same thing happened. No internet from my Note but internet works fine on the iPhone. Restarting my Note doesn't fix the problem.
Any ideas? Thanks.
Click to expand...
Click to collapse
Is the wi-fi sleep mode on?
Very odd. I've had no such problem at home,work or university
Sent from my GT-N7100 using xda premium
My network admin created a second wifi network to connect to (I guess our router supported it) and when I connected to the new one I got internet.
If it helps others try and solve the issue he tried pinging the IP address that my phone was using and said that he could only send information but not get anything back.
ks-man said:
This is pretty strange so I thought I'd check here with people.
I got my new Sprint Note 2 today. When I was at home it connected to my wifi network and worked fine. When I got to work I connected it to our wifi network and the internet won't work. If I turn off wifi internet comes back.
Here's the kicker, I have my old iPhone right next to it connected to the work wifi network and it is connected fine to the internet. This is definitely going through wifi as I no longer have a data plan on that phone.
I checked with our IT admin who said that there is no need to "accept" a device on our wifi network. He also rebooted the network for good measure. After both phones lost the network (from the reboot) and reconnected the same thing happened. No internet from my Note but internet works fine on the iPhone. Restarting my Note doesn't fix the problem.
Any ideas? Thanks.
Click to expand...
Click to collapse
Try changing your wifi channel config in the router.
Hi, I've got the International version N7100 and experiencing weird wifi problem. I have tried to reset my wifi router and use static IP but it doesn't solve the problem. Btw, the problem is whenever I connect my Note 2 to wifi it would lose connection after a while then messes my router and connection of my PC to router as well. Never had this issue until I brought the Note 2 home a week ago. I had to restart my router and turn off my wifi on Note 2 for everything else to work. My iPad, iPhone and PC are all doing fine when Note 2's wifi is off.
I used to have terrible problems with my Virgin Superhub which all went away when I changed the security settings to WEP hexidecimal from WPA2-PSK (AES). Laptops and phones would have intermittent connections all the time which a reboot or channel change would sort out but only temporarily. Give it a whirl.
Sent from my GT-N7100 using xda app-developers app
I've been experiencing the same problem. It's especially annoying when I try to download big size apps on Google Play ( > 1 gb) because it will stop any moment and i will have to re-download it over and over again. It never happens when I connect to school wifi but it just happens when I connect to my wifi at home. Weird. Nothing is wrong with my wifi at all because my other computer is always connected 24/7 without any problem.
I have a similar problem on Omega Ron v5.0 with latest Andrei kernel. The phone gets stuck sometimes in getting IP address part or have disconnects. It's annoying.
Regards
GT-N7100 cihazımdan Tapatalk 2 ile gönderildi
quick reset of router and modem does wonders!
boodies said:
quick reset of router and modem does wonders!
Click to expand...
Click to collapse
Afraid not.
I did that after other efforts failed but still have to go through same issue every now and then. This is not a permanent problem but something that occurs at least once a day for me.
Also having Wifi issues with GN2 from Sprint
I got the GN2 on it's release date (this past Thursday) through Sprint. Got it home got set up, connected...everything worked beautifully.
After a couple of hours, downloading apps etc. I noticed it had stalled. Turned off WiFI and used the network to finish. Turned back on WiFi and Voila, action again, but a few hours later it stalled.
I first made sure all of my settings were in agreement. No sleep mode or anything like that was enabled. No power saver either.
Couple hours goes by, WiFi connectivity stalls (even though it shows a full signal) I contacted TWC and made sure it wasn't the modem/router. I changed the wifi channel, tinked with the bandwidth... everything worked...an hour later it stalled. Called Sprint they said I had a dud, took it back, exchanged it, got the new one... SAME ISSUES. YEsterday I connected to my Church network HOPING it was an issue at home, but not so. After an hour on the network it stalled.
Contacted Samsung today and they have had no complaints according to them so i said I'm happy to be the first... If anyone finds a fix please let me know.
PD
PastorDroid said:
Contacted Samsung today and they have had no complaints according to them so i said I'm happy to be the first... If anyone finds a fix please let me know.
PD
Click to expand...
Click to collapse
Do you have any solution yet? I have the same issues with 2 different networks. I already contacted Samsung, but they only say I should do a reset of my device and read the setup instuctions for wifi. I'm still in contact with Samsung and hardly try to get a solution.
Stay tuned, I'll post any news I can get.
jetsetwilly said:
I used to have terrible problems with my Virgin Superhub which all went away when I changed the security settings to WEP hexidecimal from WPA2-PSK (AES). Laptops and phones would have intermittent connections all the time which a reboot or channel change would sort out but only temporarily. Give it a whirl.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I'd prefer it to work with the stronger encryption of WPA2 rather than WEP.
OP: it will be great if you could add a poll to the thread as that way we can see whats the percentage of users are experiencing this issue,
Thanks
Sent from my GT-I9300 using xda premium
ks-man said:
This is pretty strange so I thought I'd check here with people.
I got my new Sprint Note 2 today. When I was at home it connected to my wifi network and worked fine. When I got to work I connected it to our wifi network and the internet won't work. If I turn off wifi internet comes back.
Here's the kicker, I have my old iPhone right next to it connected to the work wifi network and it is connected fine to the internet. This is definitely going through wifi as I no longer have a data plan on that phone.
I checked with our IT admin who said that there is no need to "accept" a device on our wifi network. He also rebooted the network for good measure. After both phones lost the network (from the reboot) and reconnected the same thing happened. No internet from my Note but internet works fine on the iPhone. Restarting my Note doesn't fix the problem.
Any ideas? Thanks.
Click to expand...
Click to collapse
I had this issue with my S3, but never with the Note 2. What i did in that instance was reinstall the OS and that seemed to have fixed the issue. Hope this helps!
Sent from my iPad using Tapatalk HD
Same issue here. Connect wifi and I'm able to hold connection for as little as minutes at times. Turn back on 4G and I'm fine. If I re enable wifi straight after it works intermittently. This is true of both my home and office wifi. So I'm lead to believe it's the phone.
Hi,
Almost the same thing here. everytime I go out of my home and comeback the wifi network seems to work but no internet access. I have to stop and restart wifi then it works.
very strange issue. ok I have a work around but I'm going to open a ticket to Samsung.
Same issue - connects for about 30 seconds
I've tried on different routers. Other devices (iphone, ipad, S3, etc.) all work fine. Sees the wifi network. connects, then disconnects and TURNS OFF WIFI. I can't figure out how to go to service mode to see if this is a timer issue. I've tried on both G and N networks. using a verizon fios, actionteck router (and netgear). Also, will not remember the password credentials. tried router reboot and fidling, etc. Driving me nuts. any suggestions ???
Hey guys,
So all of a sudden, my wifi is searching and not connecting in a campus setting. My Samsung Galaxy Note 10.1 2014 is still connected to the same wifi my Note 4 was. I have tried rebooting, removing battery, shutting off and on data and wifi, and airplane mode. Nothing reconnects it. Also tried forgetting all networks since there are 5 when searching for networks it finds and reconnecting to one, still no dice. It's been 4 hours, still can't reconnect. Any ideas?
Dedline said:
Hey guys,
So all of a sudden, my wifi is searching and not connecting in a campus setting. My Samsung Galaxy Note 10.1 2014 is still connected to the same wifi my Note 4 was. I have tried rebooting, removing battery, shutting off and on data and wifi, and airplane mode. Nothing reconnects it. Also tried forgetting all networks since there are 5 when searching for networks it finds and reconnecting to one, still no dice. It's been 4 hours, still can't reconnect. Any ideas?
Click to expand...
Click to collapse
Have you tried to forget the network and then ADD it with + Add Wi-Fi network? I actually had an issue playing with a Galaxy note 10.1 2012 edition, I turned my hotspot (sprint note 4) on and named it the same as our current network (was showing how open networks aren't always the network they say and anybody can create a Starbucks-Guest network.... I used starbucks-guest because I didn't want to put my schools on here). The tablet didn't see the network even after reboots, but when I added the network manually it connected right away. Also was this connecting to the same access points or different ones on the other side of campus?
Yep tried forgetting, re-adding the wifi spot and nothing.
I've been having wifi connection issues since day one of getting this phone.
Not sure if I have the same problem.
But at least once a day, it seems the phone can no longer make a connection to my wifi.
The only solution is to either just power off the phone and restart or do what Sprint asked me to do.
Sprint said to try and reset the network connection information by dialing ##72786#
The phone will power off and then restart do some background stuff and then power off again and restart.
Once that is done, all is fine.
I've never had this happen on any other of my Android devices. I even use a static IP with my phone setup.
And yes, I have tried just using the default of DHCP.
I had thought it was my router (Asus RT-AC68U) which transmits both 2.4ghz and 5ghz. I have both setup and I try to use 5ghz the most.
I did upgrade the router software because I was one version behind, but that did not fix anything.
Also, I had a Sprint femocell in my house (provided for free from Sprint) because I had bad signal issues years ago.. But because this phone uses LTE and now it seems the phone comes with built-in WiFi Calling. (Means instead of using the cellular network it will use my network and ISP to make Sprint calls, all voice and text messages come through normally, it's basically a built-in femocell).
I returned that, whoops still in the box, need to get that mailed out fast.
I'm not sure how widespread this issue is, but I suspect it's bigger that just the two of us here. And if I'm in the wrong thread, please let m know.
Thanks
Rob
My wife has the S8 and I have the S8+. After the latest update (July 9-10'ish) both of our phones are having problems with our Mesh WiFi, but not our non-Mesh WiFi. We don't have issues with the connectivity to the actual WiFi, that always stays connected, but every few minutes, we'll get an exclamation point next to the WiFi signal meter, and our Internet connectivity drops. When I check WiFi connections during this time, it shows "Internet may not be available". Then, after 1-3 minutes or so, it's working fine again. While this is happening, none of our other devices have any problems with Internet connectivity.
T-Mobile had me boot into Safe Mode, and the problem didn't happen at all in safe mode. So, I did a master rest, and with just factory apps installed, it was happening again. T-Mobile asked me to wipe the cache partition. While trying to boot to that menu, my phone went into a boot loop, then after trying several different button combinations, it just turned off and wouldn't power back on again. So, T-Mobile sent me a replacement. Since receiving the replacement, I have not installed the update, and I have not had the problem on my phone at all. But, there's still my wifes phone. T-Mobile tells me I'm the only one having this problem, so they don't know what the solution is.
Our Mesh WiFI system is fairly new, so I kept the old WiFI active as a fall back option. There are no problems when connecting to that SSID, so I'm thinking the update has caused some issues when jumping between access points on the mesh system. I was also thinking maybe it's a double NAT issue, since my modem doesn't have a true bridge mode option. (My modem hands my mesh WiFi router a 192.168.1.xxx IP, but my devices that connect to the mesh WiFi get a 192.168.0.xxx IP) I tried putting the Mesh WiFi in the DMZ and making sure it gets the public IP. That didn't work. The WiFi manufacturer had me open ports 500 & 4500 to the WiFi router. That didn't work.
Does anyone have any other ideas for me? At the point, T-Mobile is telling me that it's my WiFI because it doesn't happen when connected to the non-mesh WiFi. But, it didn't start happening until the last update, and it's not happening on my replacement phone. We rely very heavily on WiFi calling, so this has been problematic. Obviously I can connect my wife's phone to the old system, but we don't get full coverage in our house from it, which is why we went to a mesh system.
I welcome and appreciate all suggestions.
Thank you
JTB
I have the same problem with my non-mesh Google Wifi router occasionally. it's annoying.
jtbarnes said:
My wife has the S8 and I have the S8+. After the latest update (July 9-10'ish) both of our phones are having problems with our Mesh WiFi, but not our non-Mesh WiFi. We don't have issues with the connectivity to the actual WiFi, that always stays connected, but every few minutes, we'll get an exclamation point next to the WiFi signal meter, and our Internet connectivity drops. When I check WiFi connections during this time, it shows "Internet may not be available". Then, after 1-3 minutes or so, it's working fine again. While this is happening, none of our other devices have any problems with Internet connectivity.
T-Mobile had me boot into Safe Mode, and the problem didn't happen at all in safe mode. So, I did a master rest, and with just factory apps installed, it was happening again. T-Mobile asked me to wipe the cache partition. While trying to boot to that menu, my phone went into a boot loop, then after trying several different button combinations, it just turned off and wouldn't power back on again. So, T-Mobile sent me a replacement. Since receiving the replacement, I have not installed the update, and I have not had the problem on my phone at all. But, there's still my wifes phone. T-Mobile tells me I'm the only one having this problem, so they don't know what the solution is.
Our Mesh WiFI system is fairly new, so I kept the old WiFI active as a fall back option. There are no problems when connecting to that SSID, so I'm thinking the update has caused some issues when jumping between access points on the mesh system. I was also thinking maybe it's a double NAT issue, since my modem doesn't have a true bridge mode option. (My modem hands my mesh WiFi router a 192.168.1.xxx IP, but my devices that connect to the mesh WiFi get a 192.168.0.xxx IP) I tried putting the Mesh WiFi in the DMZ and making sure it gets the public IP. That didn't work. The WiFi manufacturer had me open ports 500 & 4500 to the WiFi router. That didn't work.
Does anyone have any other ideas for me? At the point, T-Mobile is telling me that it's my WiFI because it doesn't happen when connected to the non-mesh WiFi. But, it didn't start happening until the last update, and it's not happening on my replacement phone. We rely very heavily on WiFi calling, so this has been problematic. Obviously I can connect my wife's phone to the old system, but we don't get full coverage in our house from it, which is why we went to a mesh system.
I welcome and appreciate all suggestions.
Thank you
JTB
Click to expand...
Click to collapse
I'm having the same exact problem with my S8+ and my netgear orbi, all was good until about a month ago, and I've tried pretty much everything, and the exclamation point still comes every few minutes. I can't wait to get rid of this phone honestly. And I've had EVERY Samsung phone to date, and this one has given me the most problems by far. I am on my 5th S8+. HURRY NOTE 8!
Running Luma mesh network... Have the same issue on my S8+ after the update...
Definitely due to the update... No issue prior
whelmar said:
Running Luma mesh network... Have the same issue on my S8+ after the update...
Definitely due to the update... No issue prior
Click to expand...
Click to collapse
Had the same issue. Go into developer options and turn on Wi-Fi verbose logging. Fixed it for me. Try it out
jtbarnes said:
My wife has the S8 and I have the S8+. After the latest update (July 9-10'ish) both of our phones are having problems with our Mesh WiFi, but not our non-Mesh WiFi. We don't have issues with the connectivity to the actual WiFi, that always stays connected, but every few minutes, we'll get an exclamation point next to the WiFi signal meter, and our Internet connectivity drops. When I check WiFi connections during this time, it shows "Internet may not be available". Then, after 1-3 minutes or so, it's working fine again. While this is happening, none of our other devices have any problems with Internet connectivity.
T-Mobile had me boot into Safe Mode, and the problem didn't happen at all in safe mode. So, I did a master rest, and with just factory apps installed, it was happening again. T-Mobile asked me to wipe the cache partition. While trying to boot to that menu, my phone went into a boot loop, then after trying several different button combinations, it just turned off and wouldn't power back on again. So, T-Mobile sent me a replacement. Since receiving the replacement, I have not installed the update, and I have not had the problem on my phone at all. But, there's still my wifes phone. T-Mobile tells me I'm the only one having this problem, so they don't know what the solution is.
Our Mesh WiFI system is fairly new, so I kept the old WiFI active as a fall back option. There are no problems when connecting to that SSID, so I'm thinking the update has caused some issues when jumping between access points on the mesh system. I was also thinking maybe it's a double NAT issue, since my modem doesn't have a true bridge mode option. (My modem hands my mesh WiFi router a 192.168.1.xxx IP, but my devices that connect to the mesh WiFi get a 192.168.0.xxx IP) I tried putting the Mesh WiFi in the DMZ and making sure it gets the public IP. That didn't work. The WiFi manufacturer had me open ports 500 & 4500 to the WiFi router. That didn't work.
Does anyone have any other ideas for me? At the point, T-Mobile is telling me that it's my WiFI because it doesn't happen when connected to the non-mesh WiFi. But, it didn't start happening until the last update, and it's not happening on my replacement phone. We rely very heavily on WiFi calling, so this has been problematic. Obviously I can connect my wife's phone to the old system, but we don't get full coverage in our house from it, which is why we went to a mesh system.
I welcome and appreciate all suggestions.
Thank you
JTB
Click to expand...
Click to collapse
Go into developer settings and turn on Wi-Fi verbose logging.
Had same issue and now it's gone. Hope it helps
richieandsandy said:
Go into developer settings and turn on Wi-Fi verbose logging.
Had same issue and now it's gone. Hope it helps
Click to expand...
Click to collapse
Seems to help, thanks!!
richieandsandy said:
Go into developer settings and turn on Wi-Fi verbose logging.
Had same issue and now it's gone. Hope it helps
Click to expand...
Click to collapse
Thank you! I just changed that setting. I really hope that works!
Other fix is enabling guest network on your router. It worked for me with Netgear Orbi.
I have an orbi and the above fix didn't quite fix my troubles. After enabling guest mode, then what? Use guest mode? Or does just the act of enabling guest mode change something? Thanks in advance.
Wi-Fi Verbose Logging
Yep! This is a problem the carries and Samsung have chosen to ignore so far. I have the exact same issue with two S8's in my household. Everything, all devices, LG, Apple, HTC, Google, Amazon, PC's, etc., including the S8's worked on our mesh wifi network until the two S8's took on the latest update. After that point neither S8 device would consistently work properly on the mesh network. While all other devices, including a Note 5 and Samsung Smart TV, among a plethora of other devices, continued to work flawlessly. It is definitely tied to the latest update on the S8 devices. I reset the wifi, the phones, etc., including factory resets but that did not solve the problem. Verizon sent 2 replacement phones and we have not allowed the latest update to load on the phones and the replacement phones are working perfectly! The latest software version that screws up mesh wifi connectivity is: NRD90M.G950USQU1AQG4. Beware. So far, neither Verizon or Samsung will acknowledge the issue. Only after hours of trouble shooting and persistence on my part about this issue being a well documented situation in on-line forums did they respond by saying they found one case similar to mine but they did not see this as a wide spread issue. Well, for anyone with a mesh wifi network, this is a big issue and irritating as heck! Come on Samsung! Own up to the issue, support your customers, and fix the problem. The evidence that there is a problem at this point is pretty convincing. All one has to do is go on-line and search the issue and bam, there it is. All somebody at Samsung has to do is take an S8 load the latest update and try it on a mesh wifi network. Really try it that is... It work at first but as soon as the mesh network moves the device to a channel or frequency that is less congested, the device will lose connectivity. Sometimes it is sporadic but eventually it becomes a more persistent problem to the point of uselessness. Either put out a patch or push out the wifi portion prior update for us to revert back to. Don't call us liars and ignore the issue. Hard to achieve customer loyalty and retention with behavior like that. I've already had to muddle through the Note 7 fiasco with the 3 recalls and final discontinuing of the device itself. Samsung, don't leave me hanging again.
UPDATE:
Turning on the Wi-Fi verbose logging did not solve my issue. It seemed to work at first. However, after a few minutes it said it was no longer connected to the web when trying to load some very common url's. However, this time there is no "!" next to the Wi-Fi signal on the S8. It now just stops working. Wish I hadn't let it update on the replacement phone. Again working just fine before the NRD90M.G950USQU1AQG4 update.
Help....anyone!?
dave812 said:
I have an orbi and the above fix didn't quite fix my troubles. After enabling guest mode, then what? Use guest mode? Or does just the act of enabling guest mode change something? Thanks in advance.
Click to expand...
Click to collapse
After enabling guest-network, forget the main SSID and connect to guest-network. If you "allow guest to see each other..." you will be able to see other devices, like printer, Sonos, Roku, etc.
I tried the fix above and did not work for me either. Going back to login in in guest-network.
You can also see this: https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/534/page/12
Just curious if anyone else has had any issues with WiFi calling on their S20 variants. I have a stock S20 Ultra on Verizon. I recently noticed my wifi calling would simply just not connect at all. It was also failing on sending some text messages, problems that I surmised might have been a recent wonky app installed. I then factory-refreshed the phone from scratch, and installed from scratch, manually picking and choosing my apps to avoid the same fate. But even so, my WiFI calling is sporadic at best. Incoming calls will ring in mostly, but if I answer the call, I get no sound at all and no one can hear me. Outgoing almost never works, unless I restart the phone, then toggle wifi calling off, wait a minute, turn it back on, and then wait for the icon to display as WiFi Calling able. Then I can get one call out. I can immediately hang up and try again, any number, and it'll just sit there waiting to connect. I have only been able to test it while on my home network. I did also recently upgrade to 50m Fiber internet, though everything is routed through a Google OnHub router for wireless so I can monitor devices in the home. I'm still connecting to the same band that I was prior, and that my other phones (my S105G and S9+) have had no issues connecting and calling from. I do not have a strong enough signal inside the house for calls to connect over the network, so that's out. All other data on the phone works fine from wifi. Texts work more reliably but still suffer from the occasional Sending Error where it times out and I have to resend. Or it'll take an extra 20-30 seconds before it sends. I get the same results if I connect directly to the modem's Instead.
Are there any other suggestions on settings or checks I can look at between phone and network that anyone can think of? This only seemed to happen within the last couple months, too. When the phone was brand new, everything seemed fine.
Edit: Workaround / half solution found, post #6.
Howdy. I just got the S20+ 5G from Verizon. I noticed my mobile data connection going in and out fairly often and texts getting stuck sending. I also noticed wifi calling draining the battery. I've disabled wifi calling for now. I'm a little peeved a $1200 phone has an issue like this.
I know it's been a bunch of months, but I just wanted to follow-up with this. I haven't found a solution but I've all but ruled out the phone as the culprit. As it turns out, all the other phones suffer from the same issues. I even bought a Verizon LTE Network Extender, which has at least solved my text issue - they work reliably now. But voice calling is still a one-way street. Calls can come in, I can hear the other person all day long but nothing can be said back. Since it happens the same way on all the phones, and since it happens even with the network extender, I can only assume the issue lies somewhere either in the modem settings somewhere that I haven't found, or in the ISP backbone itself. Sadly, they're pretty worthless when it comes to tech support (and I should know - I work for them...). I've tried most things I can think of in the modem/router itself, took out my Google OnHub altogether, and still nothing. I've heard ports opened up being a common issue but for some reason, the ports that most people suggest are already showing in use and unable to be set aside. I revisit the issue every few months, but if I ever do find a solution for my case, I'll post back then.
CharlzO_2000 said:
I know it's been a bunch of months, but I just wanted to follow-up with this. I haven't found a solution but I've all but ruled out the phone as the culprit. As it turns out, all the other phones suffer from the same issues. I even bought a Verizon LTE Network Extender, which has at least solved my text issue - they work reliably now. But voice calling is still a one-way street. Calls can come in, I can hear the other person all day long but nothing can be said back. Since it happens the same way on all the phones, and since it happens even with the network extender, I can only assume the issue lies somewhere either in the modem settings somewhere that I haven't found, or in the ISP backbone itself. Sadly, they're pretty worthless when it comes to tech support (and I should know - I work for them...). I've tried most things I can think of in the modem/router itself, took out my Google OnHub altogether, and still nothing. I've heard ports opened up being a common issue but for some reason, the ports that most people suggest are already showing in use and unable to be set aside. I revisit the issue every few months, but if I ever do find a solution for my case, I'll post back then.
Click to expand...
Click to collapse
From what you've shared the connection issues would point to your ISP. If you haven't already done so request Verizon do a reset on the fiber connection or switch to DSL if they offer it. At times a COLO, the actual distribution point closest to your home isn't properly maintained or the equipment is in need of upgrades or repair. The only other consideration might be a firmware defect. If your S20 Ultra is operating on Unlocked FW you might want to flash Verizon's latest FW to your device. ATT/Verizon are notorious for compatibility issues with non-native FW.
I actually just came back to add more confusion to my post, but I'll answer above as best as I can:
I don't have Verizon for home service, but Verizon Wireless for my cell. My S20 Ultra was purchased directly through the store, with all Verizon updates installed and current. My home internet is new 50/50 Fiber internet, which was just deployed to the area about 8-9 months ago. I was the first person on the loop to be installed, and it runs fine. I could up the speed if I wanted, but have no need for more. It's new cable from the unit in the field, up to the road, and new drop to the house and new equipment. From that standpoint, everything has been rock solid and works fine. I certainly am not letting them off the hook (or, wasn't until five minutes ago) for what might be a setting somewhere between points.
However, during some more testing, someone mentioned they had an issue with WiFi calling not working. So I did more testing with my S20 Ultra. Turns out, WiFi calling isn't even working at all on my device. I can place it in airplane mode (so it doesn't see my Network Extender), enable wifi, and no matter what I try to do, it will not recognize WiFi for calling purposes. I can enable it fine, it shows enabled, I can restart and toggle all day long. But the moment I try to make a call that way, it tells me I must turn off Airplane mode to make a call. This is in spite of the phone having wifi calling enabled, with WiFi set as the preferred call type in it's settings. This is full wifi from within feet of the router. On a whim though, I took out my SIM card and put it back in my S10 5G sitting in it's box. Calling works perfectly, on both wifi calling, and the network extender. So all that did was confuse me more.
I have an S9+ that doesn't work. I have an iPhone 11 Max that doesn't work. I have an S20 Ultra that doesn't work. But an S10 5G that does. It's the only phone I've found in the house so far that I can make or receive calls from/to, and be heard on the other end. All the other phones, connected to the same wifi and the same network extender all suffer from the same thing. At this point, I've basically hit a wall and am ready to throw in the towel. I was ready to spend another evening messing with the modem until my S10 worked perfectly. It worked on the extender fine. I put it to Airplane mode, enabled wifi calling, and within twenty seconds it registered an outgoing call to my house as a wifi call, completed, and could hear fine. A bunch of coincidences all at once. My fiber internet came with a new modem, though the same model that my regular DSL used prior - when everything worked fine. This new one is configured exactly the same, I kept the wifi configuration exactly the same as before to eliminate having to set a dozen devices back up. So I thought that change still somehow did the phones in, as it was shortly after that I realized that they weren't working right. But then the S10 connected just fine, using the same new modem and everything.
Pretty sure I just live in the bermuda triangle of befuddlement here. I'm just going to abandon trying to figure it out, and go back to just calling back anyone that tries calling, from my home phone instead.
A workaround /semi-solution has presented itself:
The reason my S10 worked was because it was connecting to the 2.4GHz radio instead of the 5GHz one (my router is set up with both configured through what is called "Total Control Wireless" where it configures both under one umbrella with the same SSID, security and password and then lets the devices pull whichever it prefers). But my S10 still had my 2.4 guest wifi in it, and connected to that without me realizing it.
By switching my S20 to Airplane mode, and connecting to my 2.4GHz guest wifi, it works. It does NOT work though, if I don't enable airplane mode. I believe this is due in part to some others I've seen posted where the Samsung phones will automatically attempt to use cellular signal regardless of wifi calling enabled or set as preferred. Noting that the preferred call type is under 'roaming' and likely not subjected to just always using it. So it sees a signal at all, be it from the extender or from even a small signal seeping through the wall, and I guess it tries to use that instead of the wifi. Airplane mode on, 2.4Ghz radio, and I can make and receive calls all day, with no issues with voice.
I still have some more to play with, like disabling the 5GHz band altogether, and so on, but for now at least, I seem to have narrowed it down. Even though this router is set up exactly as before, my guess is something in there isn't liking it. I even set up the 5GHz guest radio, which did nothing either. But for now, I at least have a workaround, even if it means having to remember to disable airplane mode when I leave the house. I think there's rules I can make for that somewhere...
Last follow-up. I don't know if this is really a solution, but for future reference:
I disabled the 5GHz radio in my modem/router. For records, it's an Arris NVG448BQ. I'm not sure what would've changed from the old modem to the new, but I guess it's possible that I didn't have both bands enabled on that one.
However, changing to strictly a 2.4 GHz radio has eliminated the issues altogether with my S20. I will be able to test the other phones later but I suspect the same thing. I don't think it's so much the phones as much as it is something somewhere in the 5 GHz side of the router, despite being unable to find any difference in the way they were set up. I even left it enabled as a separate SSID, and still nothing.
I also was able to disconnect my Network Extender (glad I spent money on that...) and thus eliminate the need to toggle airplane mode on and off. I was worried that the phone would still see a trace amount of cellular signal and prevent things from working, but I made a 30 minute test call on wi-fi calling (which now shows enabled reliably and available, no funky restarting or toggling needed), and repeated testing with sending and receiving text and SMS messages are all working as they should once again.
As far as phone-related though, I'm calling this one solved finally. I do suspect that with a better router and advanced band filtering, I could make things work somehow, but I really don't have any need to do so at this time.
Case closed.
Confirm carrier setting. Or re install carrier setting.
Go to setting / general / about.
Network must be Verizon 4G LTE. Network is good all the time.
HD Voice is activated/
Charlz0_2000 gives 2.4 GHz setting is the best solution here available.
As a follow-up to my last follow-up, and I promise after this one, I'm done. The ultimate cause of all this, was a faulty modem - which I half-suspected at times anyway as there should be no reason an S20 shouldn't be able to use the 5GHz band for Wifi calling. My Modem started completely rebooting at random a week ago, and I finally was able to get a replacement today from my ISP. As soon as I had it installed and configured, I connected to the 5GHz band with my phone and was able to make and receive calls over WiFi with no issues at all. I will keep the bands separate as I do have some smart devices that have a hard time with the "smart" umbrella that the modem defaulted to.
But just for future trouble-shooting for others with WiFi calling issues, it's worth a shot to try one band or the other specifically as a work-around.
Cheers all.