Develop Bugs

Odd connection issue

It started yesterday and I don't know why. Go to check my weather, hit update and after about 10 seconds I get a bubble telling me that an unknown connection error ocurred and to try again later. I can make phone calls, send and receive texts, but can't check my weather. If I soft reset it works fine. Today, go to check my weather again and same problem. Been making phone calls and texting all morning without issue. Soft reset and again it works fine. Obviously, something is going wrong with my data connection over time, but what could cause it to just shut down completely requiring a soft reset to fix?

More weirdness. I tried manually turning on my data connection in the Connection Manager and as quickly as I turn it on it turns itself off. WTF! I haven't done/added anything to the phone in a week. Is this something on AT$T's end, could they be blocking me from using data for some reason?
About 2 weeks ago I did some regedit to have the data connection turn off automatically after 5 mins of non-use. It was working fine after that and anytime it needed a data connection it would make it. I don't remember where the setting was to change it back, but I doubt this is the problem because this issue just started yesterday.

I'm on AT&T also, on the new leaked ROM, and I have exactly the same issue. It started about 2-3 weeks ago, and I noticed the connection drops overnight (during the day I have no problems), and it'll only come back after restart or reset. I think it's AT&T's network...

Miami_Son said:
Is this something on AT$T's end, could they be blocking me from using data for some reason?.
Click to expand...
Click to collapse
Maybe they work on improving their towers and network lol

T-Mobile does that also.
i get a Could not coonect bubble,and have to manualy enable my data conection.If you guys are Tethering our providers automaticly drop our priority level...Unlimited my ass,they tried to cap me at Edge speed and all i had to do was disable/enable the data conection to blast 3g...

I found the problem, but I still don't know what caused it. I'm leaning towards something done on AT$T's end. I have always had my phone configured to use the AT$T ISP in network properties. Apparently, it no longer likes this setting. Switched back to MediaNet and all is working just fine. Problem is that when I first got the phone I did speed tests using both settings and AT$T ISP was faster, so that's why I set it that way. I can't test it now because it won't stay connected with that setting. Can AT$T block users from a particular connection? I don't tether and the most data I've ever used was 280mb last month. Hardly a reason to block me.

I'm not thethering either, my usage is roughly 600 MB/mo and my network is already set to MediaNet. This problem started recently, didn't have it before.

Looks like it is something going on with AT$T. A number of my friends from different states have reported issues over the past 2 weeks with several having severe connection issues the past few days. These are people on varying devices including iPhones, Blackberrys and smartphones. I hope it is due to AT$T finally upgrading their network and not overload from all the new iPhone users and abusive tetherers.

Incoming callson WiFi calling goes straight to Voicemail

I love the phone and having the hardest time resisting turning the phone back in. I'm on my 2nd S3 and my third Sim card. Everything appears to be going well but I noticed that when my phone is in WiFi calling mode, incoming calls go straight to voice mail. I don't get an alert or anything. If they leave a voicemail, I get that. I searched other phones that have had this issue not just the S3. I am running stock OS but I am rooted.
Can anyone else verify that there incoming calls are working on Wifi Calling ? Any ideas on what I could try ? outgoing calls work fine.
EDIT: Sometimes calls go through, sometimes it doesn't. When it does go through, I can't swipe the green button to answer. It goes through the swipe motion but nothing happens. When I am off of WiFi calling, I can receive calls correctly and I can properly swipe to answer them

soljaofjesus said:
I love the phone and having the hardest time resisting turning the phone back in. I'm on my 2nd S3 and my third Sim card. Everything appears to be going well but I noticed that when my phone is in WiFi calling mode, incoming calls go straight to voice mail. I don't get an alert or anything. If they leave a voicemail, I get that. I searched other phones that have had this issue not just the S3. I am running stock OS but I am rooted.
Can anyone else verify that there incoming calls are working on Wifi Calling ? Any ideas on what I could try ? outgoing calls work fine.
EDIT: Sometimes calls go through, sometimes it doesn't. When it does go through, I can't swipe the green button to answer. It goes through the swipe motion but nothing happens. When I am off of WiFi calling, I can receive calls correctly and I can properly swipe to answer them
Click to expand...
Click to collapse
Ah-ha, you just solved a mystery for me! I like to have my phone automatically connect to any wifi in my usual hangouts to save data. I kept wondering why I was missing calls without hearing my ringtone. I have a theory on what is happening. Back on my old Vibrant, wifi-calling could not work on slower networks. I could get it to initialize but never could it actually make a call. I noticed this when up in the mountains at a lodge that had very slow internet. Maybe it's the same issue? Hopefully others will chime in.
Not sure if this a slow network issue or and ICS issue. My S3 does this also and is frustrating since I auto connect to wifi at home and work. Keep missing damn calls. My S2 started doing the same thing when I updated from GB to ICS. Maybe its a Samsung and ICS thing now that I think about it because the wife and kids all run ICS on HTC Amaze without issue.
Click to expand...
Click to collapse
Disappointing. Are you on T-mobile? (I expect yes as this, to my understanding, is the only US network licensed to use wifi calling?)
I am thinking of buying an S3 but I have to have wifi calling working on UK operator orange.
Click to expand...
Click to collapse
I think most of these threads are locked because XDA is trying to separate them all. Anyways, this is the only way I could respond. Since my first post, I have had more positive experiences with wifi-calling. I think it may be a little of both, slow connection and this newer implementation. On a slow connection it definitely wont work correctly which is what I would expect. What I mean is you can't successfully answer or make a call as the phone app will just hang. Going straight to Voicemail is another mystery altogether. I have 4g internet at home so there is no reason I can think of for that to happen. But like I said since my first post I have successfully made and answered several calls from home using wifi-calling and even a few from a location that had decent internet. Call quality was decent for what it is.
Guys, take a look at this thread. It concerns wifi signal dropping and re-enabling. That would certainly explain why some of the calls made to me when I was at home on wifi went to Voicemail even though I have 4g. I did notice some of this last week.
http://forum.xda-developers.com/showthread.php?t=1790187

Not sure if this a slow network issue or and ICS issue. My S3 does this also and is frustrating since I auto connect to wifi at home and work. Keep missing damn calls. My S2 started doing the same thing when I updated from GB to ICS. Maybe its a Samsung and ICS thing now that I think about it because the wife and kids all run ICS on HTC Amaze without issue.

Wifi Calling
sflagg73 said:
Not sure if this a slow network issue or and ICS issue. My S3 does this also and is frustrating since I auto connect to wifi at home and work. Keep missing damn calls. My S2 started doing the same thing when I updated from GB to ICS. Maybe its a Samsung and ICS thing now that I think about it because the wife and kids all run ICS on HTC Amaze without issue.
Click to expand...
Click to collapse
Disappointing. Are you on T-mobile? (I expect yes as this, to my understanding, is the only US network licensed to use wifi calling?)
I am thinking of buying an S3 but I have to have wifi calling working on UK operator orange.

This happens on sprint phones as well...

I see this thread is open again. My experiences with wifi-calling have bore out what I thought: A weak signal will cause problems. I only wish that every call went to voicemail. What happens often with me is that wifi-calling will partially work, as in I can answer a call but the person can't hear me at all and I may catch one or two words from them. If they terminate the call, the phone app is fine, but if I terminate the call, the phone app hangs and freezes everything! Today it was so bad I had to pull the battery and reboot. Maybe wifi calls going to voicemail is an imperfect function that Samsung or rather T-Mobile built into the app. It kinda makes sense as this app could never complete a wifi call if you were connected to slow internet when it was a separate app. In any case I would rather have my wifi calls go straight to voicemail (and get a pop-up notification) than have the app try to work but wind up hanging my phone. What do you guys think?

I don't know about slow networks. I've already exchanged one T-Mobile S III because of Wi-Fi calling problems. My replacement works much better on my work network than it does on my home network and it is much, much slower than my home network is.

dcugooner said:
I don't know about slow networks. I've already exchanged one T-Mobile S III because of Wi-Fi calling problems. My replacement works much better on my work network than it does on my home network and it is much, much slower than my home network is.
Click to expand...
Click to collapse
This isn't particularly good news for me. If it isn't software problem that manifests when coupled with a slow network then a future update won't fix it. That's what I was hoping the problem would turn out to be. If its hardware, then the time I have to do something about it is limited as I dropped my first phone and the replacement has a limited warranty, I think. Plus, I've paid to have invisi-shield placed on the front and back and would have to eat that cost if I get another replacement.

Epic Fail
I have this issue and am at my wits end to resolve it. Wifi calling is a major feature that worked fine(except echo) with my Vibrant. However, nothing I have tried will fix my ability to answer calls on WiFi. I have the SIM from the GS3 box. My E911 address exists since my bb8900. WiFi Power Save is off. All routers I use, Linksys E4200 and Linksys WNR1000, Linksys 614. Wireless N and G. T-mo CS could not help. I understand that the WiFi calling changed from UMA to IMS. No separate app. GS2 users with same issue. Anyone with a clue? Please help.

IrieBro said:
I have this issue and am at my wits end to resolve it. Wifi calling is a major feature that worked fine(except echo) with my Vibrant. However, nothing I have tried will fix my ability to answer calls on WiFi. I have the SIM from the GS3 box. My E911 address exists since my bb8900. WiFi Power Save is off. All routers I use, Linksys E4200 and Linksys WNR1000, Linksys 614. Wireless N and G. T-mo CS could not help. I understand that the WiFi calling changed from UMA to IMS. No separate app. GS2 users with same issue. Anyone with a clue? Please help.
Click to expand...
Click to collapse
how did you turn off the wifi power save?
I experience the bad quality calls on wifi, at my workplace it is perfect, but at my home, its terrible.
my home network is faster than my workplace.
I think this is something to do with the firewall as well.
and I couldn't find the way to turn off firewall on the dam verizon fios actionnet router.
---------- Post added at 01:27 PM ---------- Previous post was at 01:27 PM ----------
you can also try to broadcast the wifi on channel 3 only, that helped me in my case.

WPSM
There is a link earlier in this thread to another XDA thread. Phone app --> *#0011# --> menu button --> WiFi--> Press WPSM On/Off button.
My GS3 would drop a WiFi signal 3 inches from the router at work and 3 feet from the router at home. At least THAT is fixed now. However, I don't seem to get the same WiFi signal range as my Vibrant did using the same routers Trying the channel 3. I do have a few setting set to auto at least on my home router.
-greenboy- said:
how did you turn off the wifi power save?
I experience the bad quality calls on wifi, at my workplace it is perfect, but at my home, its terrible.
my home network is faster than my workplace.
I think this is something to do with the firewall as well.
and I couldn't find the way to turn off firewall on the dam verizon fios actionnet router.
---------- Post added at 01:27 PM ---------- Previous post was at 01:27 PM ----------
you can also try to broadcast the wifi on channel 3 only, that helped me in my case.
Click to expand...
Click to collapse

when my wifi calling was giving me issues i had to go on the tmobile site and set my area for 911 calls for the wifi calling. after that it worked flawlessly

duhitsrandy said:
when my wifi calling was giving me issues i had to go on the tmobile site and set my area for 911 calls for the wifi calling. after that it worked flawlessly
Click to expand...
Click to collapse
Yes, that's required, but not the underlying issue of the thread.

I've had wifi calling weirdness too. I called my sisters Verizon cell and there was no tone but after xx seconds it got her voicemail. When I call my phone on my house phone (Comcast) my phone rings but there's no tone on the house phone!

I NEVER get a ring. Just someone picks up our voicemail does.
Sent from my SGS3 Stock Rooted & Odexed
I love this thing!

WiFi Calling dropping calls...

Ok, it seems for me the issue with wifi calling not working at all is resolved (I always have the "Wifi calling is ready!" notification) but when I receive a WiFi call it will randomly disconnect after a few minutes. Might be 5 min, might be 20, and after that if I or they call back it might disconnect in as little as 2-3 minutes! Doesn't seem to matter if I answer on my handset or my GearS, still always drops in <20 min.
It's not my internet connection dropping, I also have Skype with In/Out running and can place/receive calls on it without any interruptions (on both my N4 and my PC).
Any suggestions?
Phone is 100% stock, not rooted, Android 4.4.4.

Wi-Fi calling was a PITA on KitKat with my Netgear router. Netgear support and DD-WRT forums for my router were both saying to disable the firewall. Forward porting and setting my phone as DMZ with static address didn't help with UDP packets and maintaining a connection.
Lollipop its better and the reason I'm not going back to KitKat but hardly tolerable without root.
I know this doesn't apply to you but with Adaway, I monitored the DNS requests for Wi-Fi calling and whitelisted them. That seemed to help with the Wi-Fi connection list issues. There's webservicesgateway and vowifi dns requests to look for. Didn't post for security concerns.

Yeah, I'm scared to make the jump to lollipop because right now my GearS is working perfectly and I'm scared to change anything major (spent 2 weeks fighting in on the "compatible" SGN2, finally said "screw it, I'm due for an upgrade" and got the SGN4) as Is aid I've not even rooted my SGN4 for fear of 'breaking' my smartwatch...
Router could be the issue, since it's a brand I've never heard of before ("ComTrend") but It's a router/modem combination that my ISP requires so I cant swap it out... may try the suggestions you mentioned, just in case, but not going to hold my breath...
If anyone else has suggestions, please post them. Right now I'm in a situation where I need VoIP (I literally get 0-1 bars reception, so bad that if I answer a call it drops) and to get Skype to work I have to turn off calls comming to my handset (otherwise the Phone App overtakes skype, then drops the instant I answer) which means I miss calls when NOT at home thanks to skype playing poorly with my cellular data... >.<

Off topic: did you consider asking Sprint for an Airave unit? Bad cell signal.
Mine was free to use and got exchanged/upgraded for newer model a couple of times.
I let mine go with Wi-Fi calling because it conflicts. Had to pick one.

I've had two actually. Back when it was amde by Samsung it worked GREAT, (thought they charged me soemthing like $5/month for it) but now the new "Airvana" version has stopped getting a GPS signal... why I cant program it in I dont get (since WiFi calling works with out constant GPS) It's been sitting around gathering dust for a while, I might get it out and try to make it work again, maybe they upgraded their system enough that it wont turn off... or maybe I'll try sticking it in the attic or something... thanks for the suggestion!

Mesh WiFi issues after latest update

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

VZW S20 Ultra wifi calling issue?

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.