Related
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!
Been having some issues with callers not hearing me. I tried swapping out the modems (can't remember exactly which ones but can figure it out if necessary), tried different kernels (while I was on TeamSonic rom), and switched from Sonic to FrostyJB and still happening.
I am on wifi calling at my home (crappy signal). It happened on all calls this morning. I made all the above saps and changes this morning as well. I tried a call when I left and was outside of wifi and call worked fine.
This sound like a defect or setting thing? Don't see a lot of settings in the Wifi Calling menu.
Thanks!
There are a few things that could be the problem. You need to determine if it is the phone or the wifi.
What kind of signal are you getting? Are you able to test your wifi for internet? Is this all of a sudden, meaning were you able to use wifi calling without problems prior to this recent problem?
I always had problems with wifi calling so I never use it on my HTC one s and this one too
Sent from my SGH-T999 using Tapatalk 2
pytyper483 said:
There are a few things that could be the problem. You need to determine if it is the phone or the wifi.
What kind of signal are you getting? Are you able to test your wifi for internet? Is this all of a sudden, meaning were you able to use wifi calling without problems prior to this recent problem?
Click to expand...
Click to collapse
It has been happening more frequently lately but I am not really sure on a time frame. I don't make gobs of calls. I have had the phone for about a month or so and didn't have any problems early on. I have tried a few different ROMs but I wouldn't call myself a flashaholic.
My wifi signal at home is pretty decent. My speeds are usually around the 18 - 19 range. No problems with internet. The calls connect pretty quickly.
I do have a cell-fi (sp?) unit on the way from t-mobile which my help but I would just like to try and figure out if something is off with the device.
Thanks!
Information update:
I just made a call from my office (same no cell signal and decent wifi) and call worked fine. Wifi speeds here are a bit slower, usually around 8-9.
Haven't changed router or modem at home. Time Warner Cable is the provider.
Will check my son's phone tonight. He also has the S3 but being a teenager, I am not entirely sure he knows how to make an actual phone call...
Does the problem seem to happen at the same times of day? Depending on how your isp is set up, heavy network traffic can cause the issue. Also remember that your voice going out is like uploading a file on that upstream data is going to be slower than downstream.
Is your cable modem or router kind of outdated? Last year I upgraded my modem and saw a huge improvement. The DOCSYS 3.0 tech is a lot faster than a DOCSYS 1.0 rated modem can handle.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Does the problem seem to happen at the same times of day? Depending on how your isp is set up, heavy network traffic can cause the issue. Also remember that your voice going out is like uploading a file on that upstream data is going to be slower than downstream.
Is your cable modem or router kind of outdated? Last year I upgraded my modem and saw a huge improvement. The DOCSYS 3.0 tech is a lot faster than a DOCSYS 1.0 rated modem can handle.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Today it happened around 8:00 am (EST) and again around noon. I'll check the upload speeds as well.
I swapped out the modem about 4-5 months ago. Not sure of the make. It is the one Time Warner provides. Haven't noticed any major problems with our PC though.
Router does have a few years on it.
I suspect that you're getting one way voice translation... the router is forwarding the incoming voice traffic to your phone but failing to do the same for your outbound traffic. I have a Cisco enterprise class router at my house (I'm an IT geek so I *play* with it) and until I opened up a bunch of ports to a bunch of sites I saw being blocked in the router logs I was having the same issue.
I asked T-Mobile for a list of voice gateway IP addresses at their end but none of the tier 1/2 techs were ever able to give me any useful info regarding IP addresses or ports... The phone keeps finding new IP addresses it wants to connect to so in the end I gave up on getting wifi calling working reliably and have mine set to prefer cellular.
A SOHO or Home router ought to automatically open up the necessary ports but I would suggest looking at the manufacturers web page to see if there's a firmware update for your router. If there is, apply it and see if that fixes the problem. Else buy another one and see if that resolves it. If it doesn't then you can always take it back.
Hope this helps
I thought it was just me that had a wifi problem
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling. It's possible the signal is so weak it's dropping once you have the phone up to your face and it's moving around and stuff. Try using speakerphone with the phone on the desk or wherever you have some signal. You should also try to get a signal booster from tmo.
Definately check to see if there's any firmware updates for your router like ronin said.
Is it a G or N router? If it is N, check your other devices that connect to it as well. If anything connects to it at 802.11G then all connections with the router can be throttled down to G speeds. If so disconnect the G device, reconnect your S3 and try it again.
Also have you restarted the modem and router recently? Unplug them both from power for about 15-30 seconds. Then plug back in and give it a minute or two for everything to reconnect.
Sent from my SGH-T999 using xda app-developers app
I've been having the same problem all day today. I couldn't quite determine if it's my service or wi-fi, until then, I have it off for now.
Please read forum rules before posting
Questions go in Q&A
Thread Moved
Friendly Neighborhood Moderator
psykhotic said:
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling. It's possible the signal is so weak it's dropping once you have the phone up to your face and it's moving around and stuff. Try using speakerphone with the phone on the desk or wherever you have some signal. You should also try to get a signal booster from tmo.
Click to expand...
Click to collapse
Didn't have to do all of this with V2
psykhotic said:
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling. It's possible the signal is so weak it's dropping once you have the phone up to your face and it's moving around and stuff. Try using speakerphone with the phone on the desk or wherever you have some signal. You should also try to get a signal booster from tmo.
Click to expand...
Click to collapse
I didn't know about the cell connection requirement. The cell signal at my house is far north of crappy but the signal in my office is bad as well and no issues. I do have the tmo booster (cell-fi?) on the way. Hopefully that will fix it.
Thanks!
J_Bone said:
I didn't know about the cell connection requirement. The cell signal at my house is far north of crappy but the signal in my office is bad as well and no issues. I do have the tmo booster (cell-fi?) on the way. Hopefully that will fix it.
Thanks!
Click to expand...
Click to collapse
Someone told me once they'll send you one for free if you have lousy coverage at your home. Is that true?
Sent from my SGH-T999 using xda app-developers app
J_Bone said:
I didn't know about the cell connection requirement. The cell signal at my house is far north of crappy but the signal in my office is bad as well and no issues. I do have the tmo booster (cell-fi?) on the way. Hopefully that will fix it.
Thanks!
Click to expand...
Click to collapse
Woah.. holding my phone landscape killed my WiFi calling. WiFi went from 3 bars to 1 and WiFi calling disappeared. Holding the phone the other way fixed it.....I just had an iPhone 4 problem
DocHoliday77 said:
Someone told me once they'll send you one for free if you have lousy coverage at your home. Is that true?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
If you had good credit they will and you have to have SOME service. Like 1 bar or w.e.
ronin4740 said:
I suspect that you're getting one way voice translation... the router is forwarding the incoming voice traffic to your phone but failing to do the same for your outbound traffic. I have a Cisco enterprise class router at my house (I'm an IT geek so I *play* with it) and until I opened up a bunch of ports to a bunch of sites I saw being blocked in the router logs I was having the same issue.
I asked T-Mobile for a list of voice gateway IP addresses at their end but none of the tier 1/2 techs were ever able to give me any useful info regarding IP addresses or ports... The phone keeps finding new IP addresses it wants to connect to so in the end I gave up on getting wifi calling working reliably and have mine set to prefer cellular.
A SOHO or Home router ought to automatically open up the necessary ports but I would suggest looking at the manufacturers web page to see if there's a firmware update for your router. If there is, apply it and see if that fixes the problem. Else buy another one and see if that resolves it. If it doesn't then you can always take it back.
Hope this helps
Click to expand...
Click to collapse
I believe you are right on. I could not get my Wifi Calling to function properly at work. Text works great, sending and receiving. My phone rings when I receive a call, but I cannot hear anything, neither does the caller. Similarly, when I dial a number, the other phone rings, but no audio is heard on either end. I called TMobile Tech Support and they read me a memo from Samsung that this is a "Known Issue" with "one-way audio" on wifi calling. A salesperson in the store read to me the same memo. Interesting thing is when I got home, everything works, both voice and text. I tried it at another wifi location and everything works also. But not at work. I am convinced it is a problem with the network at work. Puzzle is that Wifi Calling works great on my HD2 with Custom Rom at work using the same enterprise network. But I would hate to keep swapping the micro sim from the S3 into a sim adapter into the HD2 just to get reception at work. I was hoping the upcoming JB upgrade will solve the problem, but reading the above explanation makes me worried now. Anybody out there with any work around?
isaywedoit said:
I believe you are right on. I could not get my Wifi Calling to function properly at work. Text works great, sending and receiving. My phone rings when I receive a call, but I cannot hear anything, neither does the caller. Similarly, when I dial a number, the other phone rings, but no audio is heard on either end. I called TMobile Tech Support and they read me a memo from Samsung that this is a "Known Issue" with "one-way audio" on wifi calling. A salesperson in the store read to me the same memo. Interesting thing is when I got home, everything works, both voice and text. I tried it at another wifi location and everything works also. But not at work. I am convinced it is a problem with the network at work. Puzzle is that Wifi Calling works great on my HD2 with Custom Rom at work using the same enterprise network. But I would hate to keep swapping the micro sim from the S3 into a sim adapter into the HD2 just to get reception at work. I was hoping the upcoming JB upgrade will solve the problem, but reading the above explanation makes me worried now. Anybody out there with any work around?
Click to expand...
Click to collapse
You'd have to have access to the networking equipment at your work to really know the answer why... Short version is that Home routers/firewalls reflexively open ports when a device inside the network tries to access an IP address. UPnP is an example of this... Enterprise class routers/firewalls don't do this as it's considered insecure. So, you have to know what ports the traffic is coming from/going to and allow traffic on those ports. You also want to know what outside IP address it's destined for so you can lock down that traffic to just certain destinations, not the whole internet...
So, if it doesn't work at your office then there's likely very little you can do to fix it unless you're in the IT department or have a really good relationship with the Network Administrator of your IT department.
psykhotic said:
One thing to keep in mind is you HAVE to have a cell connection to use wifi calling.
Click to expand...
Click to collapse
Lol, really? Show me evidence of this.
What would be the point of Wifi calling if you have a cell connection? I've used Wifi calling since my MT4G and that's a total crock of BS
There would be NO POINT to Wifi calling if you have a cell signal.. common sense...
My WiFi Calling has never worked properly, and attempts to get support from Sprint have only ended in frustration. It works fine on incoming calls, but almost always (its worked once or twice) within 10 seconds of initiating an outgoing call the call is disconnected and my WiFi Calling is disabled for about 30-50 seconds, after that WiFi Calling turns back on. I assume that something is causing me to be disconnected from the WiFi Calling server. Sprint can't even tell me who runs the server if its them or a third party). They have told me it was related to my geographic location, but I've demonstrated it having the same behavior in multiple Sprint stores on their Wifi networks. The latest is that they are telling me to upgrade to Lollipop (which I haven't tried yet). Can anyone enlighten me or anything?
I've noticed that wifi calling is flaky. Sometimes it doesn't work, most of the time it does. Sprint support was able to help me fix it one time. If you've tried to go into Sprint stores for help and called Sprint support, maybe turn it off and wait a week or so and then turn it back on....i know it sounds like a crappy answer but that's what I had to do.
DarkManX4lf said:
I've noticed that wifi calling is flaky. Sometimes it doesn't work, most of the time it does. Sprint support was able to help me fix it one time. If you've tried to go into Sprint stores for help and called Sprint support, maybe turn it off and wait a week or so and then turn it back on....i know it sounds like a crappy answer but that's what I had to do.
Click to expand...
Click to collapse
I appreciate the answer, however this problem has been going on for months and it has not been "flaky" for me. All incoming calls work. All outgoing calls (with two exceptions) have been experienced what I previously described. This has been going on for many months. This problem isn't going to fix itself. Now, Sprint claims that the Lollipop release includes "enhancements" to WiFi Calling, so perhaps that might fix something. I doubt it though.
This morning I decided to do the lollipop update, everything seemed to go well and im pretty sure my wifi calling was working after I did the update, now later on this afternoon I cant get it to connect its showing a wifi calling symbol on my notification bar with a slash through it and keeps telling me Wifi Calling connection error, anyone have any idea how to fix this? Thanks!!
Yep, I'm getting the same thing today. It happened the other day and I restarted my phone and it resolved itself. Today a restart hasn't fixed it. No idea why it's not working. Nothing has changed with my phone's software. Doesn't make any sense.
cody_cummins said:
This morning I decided to do the lollipop update, everything seemed to go well and im pretty sure my wifi calling was working after I did the update, now later on this afternoon I cant get it to connect its showing a wifi calling symbol on my notification bar with a slash through it and keeps telling me Wifi Calling connection error, anyone have any idea how to fix this? Thanks!!
Click to expand...
Click to collapse
I didn't try WiFi calling since the update last week, and sure enough, I had the same issue. I even went as far as doing packet captures on my network to see what the issue was. I found a few "fixes" on the Sprint forums but none worked. So, I have two SSID's at my house, one is 2.4Ghz and one is 5Ghz (a new access point) I always connect to the 5ghz here at the house (but I don't use wifi calling at my house). So, for the heck of it, I switched my connection to the 2.4Ghz and turned on Wifi calling and BAM! It worked(I had previously used wifi calling on this network when I was testing it out when I first got my phone last year)! I switched back to the 5Ghz, didn't work. What I did to get it working: While I switched back to the 2.4ghz AP, i went into SETTINGS-WIFI CALLING, pressed and held on the 5Ghz network and tapped "remove", then re-added that SSID to wifi calling and now it works.
Please note I also have "Wi-fi Range Alert" and "Update address Notification" selected in Wi-Fi Calling settings (three dots on the upper right hand) and it did ask me to update my address information (and I saved the information). Not sure if this is critical, but I can only say this fixed the issue I had. Also note that I had previously tried:
1) Clearing the cache from APPLICATION MANAGER-ALL-> WFC SETTINGS and WI-FI CALLING
2) Dialing ##72786#
I can't say for sure doing the above two things actually did anything to help.
Earlier I tried reprovisioning my phone and it didn't fix it, also tried other things, so decided to give sprint a phone call a little bit ago and they had me go through the provision process again but they were refreshing it on they're end and it fixed the issue, hope the same works for you!!
Edit: Maybe that's what I didn't do was clear the cache before provision, I did it after wards!
MrSickle said:
I didn't try WiFi calling since the update last week, and sure enough, I had the same issue. I even went as far as doing packet captures on my network to see what the issue was. I found a few "fixes" on the Sprint forums but none worked. So, I have two SSID's at my house, one is 2.4Ghz and one is 5Ghz (a new access point) I always connect to the 5ghz here at the house (but I don't use wifi calling at my house). So, for the heck of it, I switched my connection to the 2.4Ghz and turned on Wifi calling and BAM! It worked(I had previously used wifi calling on this network when I was testing it out when I first got my phone last year)! I switched back to the 5Ghz, didn't work. What I did to get it working: While I switched back to the 2.4ghz AP, i went into SETTINGS-WIFI CALLING, pressed and held on the 5Ghz network and tapped "remove", then re-added that SSID to wifi calling and now it works.
Please note I also have "Wi-fi Range Alert" and "Update address Notification" selected in Wi-Fi Calling settings (three dots on the upper right hand) and it did ask me to update my address information (and I saved the information). Not sure if this is critical, but I can only say this fixed the issue I had. Also note that I had previously tried:
1) Clearing the cache from APPLICATION MANAGER-ALL-> WFC SETTINGS and WI-FI CALLING
2) Dialing ##72786#
I can't say for sure doing the above two things actually did anything to help.
Click to expand...
Click to collapse
It was fixed, now its doing it again, I bet its this sweet modem that im renting from Comcast, what a joke of a company
Having the same issue sperradically. Literally just before clicking on this thread I went to my phone and it had the symbol with the exclamation mark, pulled it down said "Connection Erro..." tapped on it, made a 'boop' sound then nothing) which is what I had since I got home around 5:30 today... and by the time Ifinished reading these posts, it went back to "WiFi Calling is Ready"
today I wonder if they were doing maintenence or something since a lot of ppl had the problem, (for me I first turned it on day-before-yesterday and it worked great till today though I might just have been lucky) I tried turning it off and on, I tried forcing stop and restarting, re-setting my location, etc and I still got the same error till just now, so... yeah... Sprint WiFi Calling seems flakey... (I have a skype in/out account I've been using for calls since I dont get decent reception and was hoping to replace it with this, but...)
Same here, decided to update this morning and WIFI calling is dead Jim. Tried reprovisioning after a cache clear, no change. Still dead, which sucks because I depend on it due to my in house signal being so poor.
Anyone have any other ideas?
If your desperate you can do what I did to solve my lack-of-reception...
Set up Skype
Add a skype-in number (~$4/month iirc)
Add skype out subscription (~$4/month iirc)
Activate "Google Voice Integration" on your sprint account
Add the skype-in number to google voice
turn off voice to the sprint mobile device (inside google voice)
Now when people call your number it gets routed through google-voice to skype, which will ring on your phone like normal. (just dont plan on getting a Gear because so far I've found NO way to accept/place skype calls using the gear)
Follow up that has fixed my issue with WFC after the 5.01 update on my Note 4.
Contacted Sprint via Chat.
updated Profile and PRL under system update in settings.
Pulled the battery for 30 sec and restarted. Turned on location and updated E911 settings and I'm back up and going.
Update:
For the last two days I've had no issues with wifi calling except when I went to town (where I dont need it anyway) it even reconnected and worked when I got back home. Dont know if it was a fluke or I've just been lucky, but it seems to have stabilized for me (at least for now) will report back it if acts up again.
UPDATE 2:
welp, looks like I jinxed myself. not been able to use wifi calling all day now...
Noticed a pattern though, last time it did this was when it rained, I wonder if wifi calling requires the GPS to be connected so rain kills it. (or it might be a coincidence, just something to think about)
cody_cummins said:
It was fixed, now its doing it again, I bet its this sweet modem that im renting from Comcast, what a joke of a company
Click to expand...
Click to collapse
Don't rent modems from the cable company. Usually its a cheap piece of crap. For what they charge you to rent the modem you can buy one on anazin/newegg and it'll pay for itself in less then a year
Sent from my SM-N910P using XDA Free mobile app
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.