Database Info

Wifi Calling/SMS over wifi --issues and solution.

I have had a crazy time both with wifi calling remaining connected (suffered sudden drops), and further SMS over wifi seemed spotty at best.
Part of this was caused by either a bad SIM card, or deletions of stock apps and/or services...which now have been fixed.
At the moment everything is working fine. Don't know if this will affect anyone, but I thought I would just add to the library of knowledge.
First, once I got wifi-calling working (meaning the status bar icon was no longer red), I started to read the log files and realized that every time the wifi was reset, wifi calling would not consistently restart.
What I have realized is that wifi-calling and SMS are dependent on TMOs mobile network via wifi. However, any internet connection is simply that...and any apps you have like FB or Google Voice will work with that wifi internet connection. Conversely,the TMO wifi-calling service/app either connects on a different layer (such as the IP layer) or uses some unusual node-based connection to traverse the 802.11 frequency, over your ISP's and other networks to arrive at the TMO servers which then are linked into the mobile network. You can see this by downloading an app that triangulates and provides tower locations nearby or gives you other mobile network data (i.e., CID, etc)... That data is either not decipherable by the app trying to get this data, or one gets unusual info when compared to non-wifi calling. Bottom line is that there are two separate signals being carried by the wifi: "data" and "mobile wifi calling" and they are completely different.
Another example of proof: if you are having difficulty with SMS using your wifi internet connection, try sending the SMS via Google Voice. If you have an internet connection, it will go through immediately. But regular SMS has problems if wifi-calling is not working correctly.
And one of the biggest culprits of this is wifi fixer or other similar wifi connection apps. Although it's only a guess, the "scan" these apps do are likely a simple ping to determine status of the DATA connection.
I shut off wifi fixer (but left it as a widget to use as needed), and I have perfect wifi calling and SMS.
Whatever criteria wifi fixer apps use when deciding to reset or reassociate the wifi connection is not reflective of the integrity of your connection using wifi calling. In fact wifi calling may partially interfere with your data connection which will typically trigger a reset by wifi fixer.
From now on, if I am planning on simply surfing the web and my wifi signal is less than optimum, I will turn on wifi fixer. Otherwise it just tears down wifi calling connection.
Hope this is of use.
Syntropic
Sent from my HTC One-S (rooted), stock ROM

Thanks for sharing your experience. I have an issue where over time Wifi calling disconnects even though wifi is still working. I have to re-toggle wifi to get Wifi calling back. It's very annoying.

Talk to NRGZ28... I think Energy ROM had a fix for that I'm the Amaze 4G Energy ROM
Sent from my HTC VLE_U using xda premium

syntropic said:
I have had a crazy time both with wifi calling remaining connected (suffered sudden drops), and further SMS over wifi seemed spotty at best.
Part of this was caused by either a bad SIM card, or deletions of stock apps and/or services...which now have been fixed.
Sent from my HTC One-S (rooted), stock ROM
Click to expand...
Click to collapse
Although there have been occasional exceptions, it's unusual for a wifi call on my H1s to last longer than about a minute before dropping off/disconnecting. When this happens, the call time counter changes back to say "Dialing." Of course, there is no dialing, just dead silence. There are no other signs of a problem, no error messages, no indicator icons, etc. On the same wifi network I can make long uninterrupted calls with our older MyTouch 4G - no issues at all with wifi calling.
I'm running unrooted, locked, stock ROM (for now). I don't think I've removed any apps and I think the only wifi-related app I've used is Wifi Analyzer. Could you offer suggests on how to debug this? The firmware update didn't give any improvements. Should I ask Tmo to provide a new SIM card?
Thanks -

esnittle said:
Although there have been occasional exceptions, it's unusual for a wifi call on my H1s to last longer than about a minute before dropping off/disconnecting. When this happens, the call time counter changes back to say "Dialing." Of course, there is no dialing, just dead silence. There are no other signs of a problem, no error messages, no indicator icons, etc. On the same wifi network I can make long uninterrupted calls with our older MyTouch 4G - no issues at all with wifi calling.
I'm running unrooted, locked, stock ROM (for now). I don't think I've removed any apps and I think the only wifi-related app I've used is Wifi Analyzer. Could you offer suggests on how to debug this? The firmware update didn't give any improvements. Should I ask Tmo to provide a new SIM card?
Thanks -
Click to expand...
Click to collapse
Well the first thing I would suggest is a factory reset. This being the most simple option given your phone is not rooted and on stock. The strange part of this is the "Dialing" instead of the normal keypad (which typically reverts when a call is disconnected).
As far as a SIM card, do you ever get any SIM card errors? Like "ER05" or "REV99"?
These are typically the errors of faulty cards or a bad wifi signal. Check out an app called Network Signal Info....it will tell you the strength of the wifi signal compared to the mobile network (although its not always reliable).
Let me know what a factory reset does. All of your apps will be restored by google (and their are apps to modify this restore as well).
Sent from my HTC One-S (rooted), stock ROM

syntropic said:
Well the first thing I would suggest is a factory reset. This being the most simple option given your phone is not rooted and on stock. The strange part of this is the "Dialing" instead of the normal keypad (which typically reverts when a call is disconnected).
As far as a SIM card, do you ever get any SIM card errors? Like "ER05" or "REV99"?
These are typically the errors of faulty cards or a bad wifi signal. Check out an app called Network Signal Info....it will tell you the strength of the wifi signal compared to the mobile network (although its not always reliable).
Click to expand...
Click to collapse
Didn't reset yet, want to test a little more.
I've never gotten a SIM card error. The unexpected "Dialing" with the End Call button still showing is the only indication something is off.
Tonight I ran a few tests calling between our 2 Android phones in the same room, same wifi. 3 calls 1S to MT4G: 2 were perfect and lasted several minutes, while the middle call disconnected after less than a minute. 3 calls MT4G to 1S: all 3 went directly to voicemail, the 1S didn't even ring. Now I recall that's been a complaint before - that calls to me go straight to voicemail when I've been on wifi calling.

esnittle said:
Didn't reset yet, want to test a little more.
I've never gotten a SIM card error. The unexpected "Dialing" with the End Call button still showing is the only indication something is off.
Tonight I ran a few tests calling between our 2 Android phones in the same room, same wifi. 3 calls 1S to MT4G: 2 were perfect and lasted several minutes, while the middle call disconnected after less than a minute. 3 calls MT4G to 1S: all 3 went directly to voicemail, the 1S didn't even ring. Now I recall that's been a complaint before - that calls to me go straight to voicemail when I've been on wifi calling.
Click to expand...
Click to collapse
Are you sure wifi-calling is on? Do you have the blue icon in the status bar?
Sometimes this isn't on, even though wifi is on and you are making a call.. Not sure if that is intentional or not.
Just in case... The switch is in settings> more (under wireless and network buttons)
Sent from my HTC One-S (rooted), stock ROM

syntropic said:
Are you sure wifi-calling is on? Do you have the blue icon in the status bar?
Click to expand...
Click to collapse
Yep, it's on.
Just to be clear, the H1S has received calls when wifi calling is on, it's just sometimes that they go directly to vm. For example, as I'm typing the phone just received a wifi call and is handling it fine, hasn't dropped after 3 minutes.
NO CONSISTENCY, BUT USUALLY DOESN'T WORK.

A factory reset did not fix the problem.

[Q] Receiving no calls out texts while on WiFi

Hey guys I did a search and found nothing. Any time I'm connected to Wi-Fi, I can't receive calls or texts. I'm on Sprint. Anyone else have this issue?

nein7three said:
Hey guys I did a search and found nothing. Any time I'm connected to Wi-Fi, I can't receive calls or texts. I'm on Sprint. Anyone else have this issue?
Click to expand...
Click to collapse
Yes, have done tons of research and am having a similar issue. It's believed to be software related. If LTE or Global are set as the "Preferred Network Type" under Mobile Network AND wifi is turned on, then the mobile signal cuts out when it goes to sleep. With 3G set, the phone works fine with wifi turned on. I've tried wiping the phone and also loaded the factory 4.4.2 image via fastboot this morning and still have the problem. Some people have RMA-ed their phones and still report the issue, so it must be a certain combination of settings. It's also being reported from Sprint and T-Mobile user, so it's not restricted to just one network. As for me, I'm on Sprint in NYC, have an AC router and using an Airave. My Galaxy S4 didn't have any problems.
Here are a few threads that I've found:
XDA - Signal Problem
XDA - Signal issues with new baseband solved by flashing older baseband
On Google's forums:
Nexus 5 sometimes doesn't ring when people are calling

Thanks man, I had read the Google thread but hadn't find the XDA ones. I'll try forcing 3g while on Wi-Fi.

No problem! If you're on Sprint, there is also this:
Circuit Switched Fallback Issues on Sprint
I'm in an area that is reported as not having the issue, so it's not that for me. Plus, I'm on 3G with the Airave. I remember having the HTC Mogul on Sprint and for a while it would just die if the signal was roaming. An update fixed it, but it wasn't fun. At least in this case the phone still works, not as advertised, but it works. Here's to hoping that it's fixed soon!

I'm the Tmobile user in the Google discussion. It's an annoying problem and hope it's fixed with 4.4.3. However the issue just happened to me in the last week before I got the 4.4.2 update. So I'm not sure what could have happened from a month ago when I got the phone until a week ago. Haven't installed any new apps since then.

This does seem to be working now that I am forcing 3g

Weird, right?
4.4.1 and 4.4.2 both have the same baseband and kernel. That's about the timeframe when the updates both came out, so I assume that maybe 4.4.1 is when the majority of users started seeing issues pop up?
From what I've read, this phone handles cell signals much differently because of the newer LTE TDD. It could be any number of things really, but I don't have the expertise to examine the code to see what was changed between the 4.4 and 4.4.1/4.4.2 baseband. I do believe that all of the Wifi and cell signal issue posts that are popping up now are related though.
I'm also noticing my wifi speeds bouncing all over the place (from ~180Mbps -- ~500Mbps) and I'm only a few feet away from my router. I have a Netgear r6300v2 AC router.
12/14/13 Update: I just got off of the phone with Sprint. They show that there is an internal memo on the issue and LG is aware of it. They will be pushing an update as soon as it's ready. Sprint will also be pushing an update for the Airave to help with the issue, starting on 12/19/13.
The support rep told me that it is an issue where the wifi and LTE radios aren't playing nicely together and it's causing this conflict. That's why everything seems to work fine when 3G is set as a preferred network.

PynkFloydd said:
Weird, right?
4.4.1 and 4.4.2 both have the same baseband and kernel. That's about the timeframe when the updates both came out, so I assume that maybe 4.4.1 is when the majority of users started seeing issues pop up?
From what I've read, this phone handles cell signals much differently because of the newer LTE TDD. It could be any number of things really, but I don't have the expertise to examine the code to see what was changed between the 4.4 and 4.4.1/4.4.2 baseband. I do believe that all of the Wifi and cell signal issue posts that are popping up now are related though.
I'm also noticing my wifi speeds bouncing all over the place (from ~180Mbps -- ~500Mbps) and I'm only a few feet away from my router. I have a Netgear r6300v2 AC router.
12/14/13 Update: I just got off of the phone with Sprint. They show that there is an internal memo on the issue and LG is aware of it. They will be pushing an update as soon as it's ready. Sprint will also be pushing an update for the Airave to help with the issue, starting on 12/19/13.
The support rep told me that it is an issue where the wifi and LTE radios aren't playing nicely together and it's causing this conflict. That's why everything seems to work fine when 3G is set as a preferred network.
Click to expand...
Click to collapse
thanks man!

do we have any update on the situation?

Yeah I wish there was an update soon because this problem is starting to become very annoying. Twice this week I had to check my Google Voice because my Text didn't go through on my phone

Anyone have a fix for this yet?

Does anyone know if any custom roms fix this?

I've read Google is aware of the issue and speculation says they will fix it with the 4.4.3 release.

questions:
(the 1st is stupid, but i'll ask anyways) - when this issue occurs, is the phone set to **wifi only** with 3g / lte in airplane mode?
or does it occur when just setting up wifi in ADDITION to 3g / lte?
&, when you typed Receiving no calls out texts while on WiFi , is your application for texting, hangouts?
if it's hangouts, then google neutered it to only allow text thru the cellular network,
but if you're simply joining a wifi hotspot at work or home, with your cellular network enabled, it SHOULD go thru, ive never had an issue like that with wifi toggled.. even with 4.4.1
---------- Post added at 03:54 PM ---------- Previous post was at 03:48 PM ----------
j'vai said:
questions:
(the 1st is stupid, but i'll ask anyways) - when this issue occurs, is the phone set to **wifi only** with 3g / lte in airplane mode?
or does it occur when just setting up wifi in ADDITION to 3g / lte?
&, when you typed Receiving no calls out texts while on WiFi , is your application for texting, hangouts?
if it's hangouts, then google neutered it to only allow text thru the cellular network,
but if you're simply joining a wifi hotspot at work or home, with your cellular network enabled, it SHOULD go thru, ive never had an issue like that with wifi toggled.. even with 4.4.1
Click to expand...
Click to collapse
~hint~
maybe it's simpler than one would expect (shot in the dark)
to sum it up;
on our new triband spark capable phones, does *automatic vs home only* in (change the cdma roaming mode) mean what we THINK it means in relation to it's single chip, single path architect??
back when, in dual pathed phones it MEANT roaming in another provider, when ecsfb, carrier aggregation, spark wasn't a thought..
but these newer triband phone are different beasts, & the effect of the patched worked, fit n finished network of cell sites of upgraded , non upgraded network vision, does toggling automate for smoother performance between these sites on these triband devices, with single paths....?
something as simple as a network toggle, to aid service (on the mobile client side) in this -
"In a CSFB environment, 2 important concepts are employed viz., Mobile Terminating Roaming Retry, Mobile terminating roaming forward. We will discuss MTRR in this blog. In a typical operator environment, voice coverage for the entire geographical area is achieved by employing many MSC’s. These MSC’s may be a mix of Legacy MSC (where upgrading is difficult/impossible) and next generation Softswitch MSC’s. In order to support CSFB, the MSC needs to be upgraded to support SGs interface, so the issue is how do we support CSFB when the UE is in Legacy MSC coverage. This is where MTRR helps in call delivery to Legacy MSC that does not support SGs"
from being parked on an lte channel, being called & successfully *inter-roaming* to 1xtt voice, evdo data (if used), then back to lte parking & usage when applicable..
~shrugz shoulderz~
for those with this issue, what are your setting like, in relation?
---------- Post added at 04:11 PM ---------- Previous post was at 03:54 PM ----------
j'vai said:
questions:
(the 1st is stupid, but i'll ask anyways) - when this issue occurs, is the phone set to **wifi only** with 3g / lte in airplane mode?
or does it occur when just setting up wifi in ADDITION to 3g / lte?
&, when you typed Receiving no calls out texts while on WiFi , is your application for texting, hangouts?
if it's hangouts, then google neutered it to only allow text thru the cellular network,
but if you're simply joining a wifi hotspot at work or home, with your cellular network enabled, it SHOULD go thru, ive never had an issue like that with wifi toggled.. even with 4.4.1
---------- Post added at 03:54 PM ---------- Previous post was at 03:48 PM ----------
~hint~
maybe it's simpler than one would expect (shot in the dark)
to sum it up;
on our new triband spark capable phones, does *automatic vs home only* in (change the cdma roaming mode) mean what we THINK it means in relation to it's single chip, single path architect??
back when, in dual pathed phones it MEANT roaming in another provider, when ecsfb, carrier aggregation, spark wasn't a thought..
but these newer triband phone are different beasts, & the effect of the patched worked, fit n finished network of cell sites of upgraded , non upgraded network vision, does toggling automate for smoother performance between these sites on these triband devices, with single paths....?
something as simple as a network toggle, to aid service (on the mobile client side) in this -
"In a CSFB environment, 2 important concepts are employed viz., Mobile Terminating Roaming Retry, Mobile terminating roaming forward. We will discuss MTRR in this blog. In a typical operator environment, voice coverage for the entire geographical area is achieved by employing many MSC’s. These MSC’s may be a mix of Legacy MSC (where upgrading is difficult/impossible) and next generation Softswitch MSC’s. In order to support CSFB, the MSC needs to be upgraded to support SGs interface, so the issue is how do we support CSFB when the UE is in Legacy MSC coverage. This is where MTRR helps in call delivery to Legacy MSC that does not support SGs"
from being parked on an lte channel, being called & successfully *inter-roaming* to 1xtt voice, evdo data (if used), then back to lte parking & usage when applicable..
~shrugz shoulderz~
for those with this issue, what are your setting like, in relation?
Click to expand...
Click to collapse
just a note -
if you look at slide 7 on the qualcomm snapdragon 800's chipset (you all already know this)
http://www.slideshare.net/jjwu6266/qualcomm-snapdragon-800-mobile-device
there's only ONE chip to handle wifi, 4g, 3g, bt, etc..
with lesser BoM (bill of materials) just maybe, top level s/w userspace toggles, handle more than what meets the eye, the point i was making in another thread..
which not only effects our nexus 5s, but even other phones in various ways depending on the implementation of sw/hd, of the same chipset family..
& sprint has mentioned for the forseeable future, of providing phones, with these types of chips from qualcomm..
~go figure~

nein7three said:
Hey guys I did a search and found nothing. Any time I'm connected to Wi-Fi, I can't receive calls or texts. I'm on Sprint. Anyone else have this issue?
Click to expand...
Click to collapse
the ONLY reason i pointed to the network settings *home vs automatic* in this situation, is because,
the qualcomm sd 800 is an asymmetric multiprocessor, (as will future chipsets be) & you're losing other core networking functions, while gaining another, when you SHOULD have available ALL facilities -
**ASMP vs SMP**
&
Symmetric Multiprocessing Vs. Asymmetric Processing

It actually occurs when the phone is connected to LTE and WiFi together. If my settings were to connect to 3G along with WiFi, SMS works fine.
I have to manually change my Mobile Network settings when I get to home or work, where I will be connecting to WiFi (note cellular service is always ,on, I didn't mean to make it sound as if I am trying to send SMS over WiFi). So when home I turn on WiFi along with 3G connectivity and when I leave I turn off Wifi and switch to LTE.
This issue has been happened while unrooted and running stock ROM and it still happens while rooted running Cataclysm.
Also note, the SMS we miss never will come through, it's not as if later on the message comes through...It's gone forever. It also prevents calls from coming through, it's not just limited to SMS.

nein7three said:
It actually occurs when the phone is connected to LTE and WiFi together. If my settings were to connect to 3G along with WiFi, SMS works fine.
I have to manually change my Mobile Network settings when I get to home or work, where I will be connecting to WiFi (note cellular service is always ,on, I didn't mean to make it sound as if I am trying to send SMS over WiFi). So when home I turn on WiFi along with 3G connectivity and when I leave I turn off Wifi and switch to LTE.
This issue has been happened while unrooted and running stock ROM and it still happens while rooted running Cataclysm.
Also note, the SMS we miss never will come through, it's not as if later on the message comes through...It's gone forever. It also prevents calls from coming through, it's not just limited to SMS.
Click to expand...
Click to collapse
try my suggestion; it won't hurt..
let us know if it rectified anything..

What worked for me was forcing 2G instead of 3G, hope it helps!

Can't activate wifi calling on rooted phone?

I have a google Pixel on Android 7.1.2 on Verizon. I've had wifi calling activated the whole time that I've had the Pixel, on various cell providers, until yesterday. Decided to root my phone to be able to use "Radio Control", an app that will put the phone into Airplane mode when connected to wifi. Did that yesterday, and since then I've not been able to activate wifi calling. My phone is stock other than being rooted...I tried the Radio Control app, and it worked as it should. I've just removed it again, until I can get wifi calling activated. Oh, by the way, rooted by unlocking the bootloader, putting TWRP recovery on the phone, and then installing SuperSu via TWRP.
I've tried:
-Flushing app caches in "Storage", and flushing the phone app cache.
-Having "My Verizon" app on the phone.
-Resetting network settings.
-Activating with and without being in Airplane mode, always with wifi connected, though.
-Removing and restoring "Advanced Calling" setting.
The only thing I haven't tried is that one with the live chicken, a pentagram, and incense. That's my next thing to try.
Any suggestions? I'm really amazed that I can't activate wifi, since Verizon suggests this to stabilize wifi calling for their customers. I guess that they've never actually tried it themselves. Does anyone have wifi calling activated on a rooted Pixel? Do you remember doing anything in particular to get wifi activated, other than trying repeatedly to turn it on in the phone's settings?
By the way, the reason that wifi calling doesn't seem to work well on Verizon isn't wifi calling functionality, wifi calling itself works fine. It's because Verizon only allows the setting "Cellular preferred" for wifi calling. You cannot set "Wifi preferred" for wifi calling. This means that the cell radio is busy nearly all the time in a low cell signal area (like my house), working to make the cell signal usable. I noticed that there was much less battery drain while I was testing "Radio Control" since the phone was in Airplane mode, but I didn't have wifi calling activated at that point. Wifi was connected (of course), but wifi calling was not activated.
I hope that this is all clear, and that someone out there might remember something helpful for me. Or at least be able to tell me that wifi calling can or can't be activated on a rooted phone. If I can't root and get wifi calling activated, I'm going to sell the Pixel, as it doesn't meet my needs. I also have an iPhone that works perfectly with wifi calling on Verizon, but I'd much rather be using the Pixel.
Thanks!

I'm on Verizon and had that happen and found it was because of the theme i was using. Just had to reapply the theme to settings and all fixed. Also, I just checked the settings and you can set it to WiFi preferred.

Droid1019 said:
I'm on Verizon and had that happen and found it was because of the theme i was using. Just had to reapply the theme to settings and all fixed. Also, I just checked the settings and you can set it to WiFi preferred.
Click to expand...
Click to collapse
Sounds good, just a couple of questions. First, which theme? Where do you access the particular theme in settings that you're referring to? The only theme that I've changed from default is the keyboard theme.
The other question is how can you change the wifi calling setting to WiFi preferred? Do you click on the wifi calling setting that has "Cellular preferred", and a menu comes up that includes "WiFi preferred"? I don't get that menu when I click on that setting, all I get is a setting for "roaming", and for 911 address, nothing else.
Also, which Android build are you on? I'm on Android 7.1.2, build NHG47K. Are you on that build? Or maybe N2G47E? I was wondering about that.

I'm on the 7.1.2 K build with a downloaded theme-not in settings. I think you have to set up the emergency address for wifi calling to work. And yes it's roaming preferences where you can change to WiFi preferred.

Just did a factory reset to try removing root and then activating wifi calling unrooted. Then add root again and see if wifi calling sticks or goes away....
So I'm currently unrooted and am not able to activate wifi calling. Sounds like time for a call to Verizon...Should be able to activate wifi calling with stock ROM. Have done this one before *smile*.
Things are not going well...looks like the Pixel may be heading out the door, too much time spent for no results.

RogerSC said:
Just did a factory reset to try removing root and then activating wifi calling unrooted. Then add root again and see if wifi calling sticks or goes away....
So I'm currently unrooted and am not able to activate wifi calling. Sounds like time for a call to Verizon...Should be able to activate wifi calling with stock ROM. Have done this one before *smile*.
Things are not going well...looks like the Pixel may be heading out the door, too much time spent for no results.
Click to expand...
Click to collapse
Did you update emergency address? That's has to be set up for wifi calling to work. https://www.verizonwireless.com/support/knowledge-base-208085/

Any other tips to get wifi calling enable? Whenever I click enable, it just goes to a generic error message and then nothing. So I can't even get to the screen to enter an emergency address. I have a ticket open with Verizon, but since I have an unlocked bootloader, I don't want to do a warranty exchange.

The rest of the story, used iPhone 6S Plus for a couple of months so that I could use wifi calling at home, and sold the Pixel. I did get very tired of the iPhone, even though wifi calling works perfectly on the iPhone on Verizon. So I got the new Verizon 4G/LTE Network Extender so I wouldn't need wifi calling here at home. That's allowed me to get another Pixel phone and use it at home without relying on wifi calling, now have 4/5 bars of cellular signal strength throughout my house. The Network Extender is a really nice piece of hardware, a great upgrade for the old 3G model that had no way to tell what was going on. The new 4G/LTE model has a web admin GUI page that has all kinds of useful status information on it. As well as a one-line display that shows each step in the startup sequence as it comes up.
The new Pixel works just as the old one with wifi calling on Verizon. "Cellular preferred" is the only setting available for wifi calling. Which means that if there's a low cell signal it will generally be used in preference to a strong wifi signal. Don't know why Verizon insists on this setting, I guess that they really don't want to support reliable wifi calling on the Pixel. I've thought about rooting my phone again to see if can get wifi calling working reliably, but now that the Pixel is able to use wifi calling and I don't need wifi calling at home, I'm inclined to leave it alone. In other words, getting wifi calling working perfectly isn't a good enough reason for me to root my phone *smile*. I can root it in the future if I have a good enough reason.
So the bottom line is that I'm pretty happy with the Pixel now, works as I need it to...just tried the Android O Beta, and liked what I saw there. Really glad that I'm back on Android.
Update: found an article here about how to change calling setting to "Wi-Fi preferred" for Pixel on Verizon...tried it and worked for me:
https://forum.xda-developers.com/pixel-xl/how-to/verizon-want-wifi-preferred-wifi-calling-t3622700

Wifi calling enabled but not working (VZW+Airplane mode)

Trying to test the feature before I go overseas. Wifi calling is enabled, HD voice/advanced calling enabled. When I check the hidden menu in *#*#4636#*#* everything is checked.
I turn on airplane mode and enable wifi. When I try to make a call, the dialer says "turn off airplane mode or connect to a wireless network to make a call". I am connected to Wifi though and signal strength is solid. What is the problem?

You rooted? Don't know if that really matters but, I had use adb to edit the settings database. I never could get it to work till I did that. No root needed. Just Google wifi calling preferred ADB.
Sent from my Pixel using Tapatalk
---------- Post added at 09:28 AM ---------- Previous post was at 09:18 AM ----------
baknblack said:
You rooted? Don't know if that really matters but, I had use adb to edit the settings database. I never could get it to work till I did that. No root needed. Just Google wifi calling preferred ADB.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
2 settings need to be changed I forgot but I think one is to prefer wifi and the other is to make wifi the preferred roaming method.
Sent from my Pixel using Tapatalk

I am aware of that guide for ADB. However that is for preferred WiFi calling when both cellular and WiFi are available. It shouldn't help when I'm in airplane mode.

Celeras said:
I am aware of that guide for ADB. However that is for preferred WiFi calling when both cellular and WiFi are available. It shouldn't help when I'm in airplane mode.
Click to expand...
Click to collapse
I never could get mine to work in airplane mode. Kept getting an error.
Sent from my Pixel using Tapatalk

Had same problem with Verizon Wifi calling, fixed it
I had the same problem on my OG 2016 Pixel (rooted) running stock 7.1.2 ROM on VZW, but now fixed - here are the steps:
1. Open Testing Menu (dial *#*#4636#*#* on dialpad).
2. tap the "Phone information" menu.
3. Toggle on the "VoLTE Provisioned" slider (this was toggled off by default on mine). (Also make sure "Wifi Calling Provisioned" is toggled on.)
4. Using the Quicksettings dropdown menu, toggle Airplane Mode.
5. IMPORTANT NOTE - When I tried the 1st time it didn't work because entering Airplane Mode greyed out Wifi icon and disabled all Wifi connections (and data icon showed "no service"), even though Wifi was previously toggled on.
6. To remedy this, drop down your Quicksettings menu again and simply touch the Wifi connections shortcut, wait a couple seconds and all Wifi connections will repopulate, and default Wifi connection should re-connect.
7. Now hit the back button to the Quicksettings dropdown menu, wait another couple seconds and the data icon should change to "Verizon Wireless Wi-Fi Calling" - Wifi calling should now work

Preterist said:
I had the same problem on my OG 2016 Pixel (rooted) running stock 7.1.2 ROM on VZW, but now fixed - here are the steps:
1. Open Testing Menu (dial *#*#4636#*#* on dialpad).
2. tap the "Phone information" menu.
3. Toggle on the "VoLTE Provisioned" slider (this was toggled off by default on mine). (Also make sure "Wifi Calling Provisioned" is toggled on.)
4. Using the Quicksettings dropdown menu, toggle Airplane Mode.
5. IMPORTANT NOTE - When I tried the 1st time it didn't work because entering Airplane Mode greyed out Wifi icon and disabled all Wifi connections (and data icon showed "no service"), even though Wifi was previously toggled on.
6. To remedy this, drop down your Quicksettings menu again and simply touch the Wifi connections shortcut, wait a couple seconds and all Wifi connections will repopulate, and default Wifi connection should re-connect.
7. Now hit the back button to the Quicksettings dropdown menu, wait another couple seconds and the data icon should change to "Verizon Wireless Wi-Fi Calling" - Wifi calling should now work
Click to expand...
Click to collapse
I appreciate the suggestion. I had tried toggling all those options previously but I did it again per your instructions. It did not work.
My quicksettings text goes from "Verizon Wireless" to "Airplane mode" when it is enabled. Then when I put WiFi back on it goes BLANK. It does not say "Verizon Wireless WiFi Calling" like yours did. Any ideas?

I don't understand. I have a cellular signal and my wifi calling just stays on. All I did was change 2 values in the Database.
Sent from my Pixel using Tapatalk

Yes thanks, I already established I am not trying to get it to stay on all the time.

Celeras said:
Yes thanks, I already established I am not trying to get it to stay on all the time.
Click to expand...
Click to collapse
I guess I never caught that fact. Mine doesn't stay on all the time. But, as soon as I walk in my house it pops on. My wife has an S7 and I can't get hers to work unless I turn the cellular off. Evidently Samsung does not have the same settings database.
Sent from my Pixel using Tapatalk

Perhaps a local router misconfiguration?
Celeras said:
I appreciate the suggestion. I had tried toggling all those options previously but I did it again per your instructions. It did not work.
My quicksettings text goes from "Verizon Wireless" to "Airplane mode" when it is enabled. Then when I put WiFi back on it goes BLANK. It does not say "Verizon Wireless WiFi Calling" like yours did. Any ideas?
Click to expand...
Click to collapse
I've heard that a local Wi-Fi router mis-configuration may be the reason Wi-fi calling fails in some instances.
I would test it out on a different router, or have someone with a known good Wi-fi calling phone setup test on your router to eliminate that possibility.
I've also heard that Wi-fi calling breaks when upgrading to Oreo for some folks. Curious what Android version you're running?

Preterist said:
I've heard that a local Wi-Fi router mis-configuration may be the reason Wi-fi calling fails in some instances.
I would test it out on a different router, or have someone with a known good Wi-fi calling phone setup test on your router to eliminate that possibility.
I've also heard that Wi-fi calling breaks when upgrading to Oreo for some folks. Curious what Android version you're running?
Click to expand...
Click to collapse
Hmm, I will give that a shot next time I can. All my tests have been on my home wifi.
And yes I am running the latest stock update, 8.1.0

baknblack said:
You rooted? Don't know if that really matters but, I had use adb to edit the settings database. I never could get it to work till I did that. No root needed. Just Google wifi calling preferred ADB.
Sent from my Pixel using Tapatalk
---------- Post added at 09:28 AM ---------- Previous post was at 09:18 AM ----------
2 settings need to be changed I forgot but I think one is to prefer wifi and the other is to make wifi the preferred roaming method.
Click to expand...
Click to collapse
How would one go about doing this ?

Xdevillived666 said:
How would one go about doing this ?
Click to expand...
Click to collapse
https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/
Sent from my Pixel using Tapatalk

baknblack said:
https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
could this possibly work on other carriers?

Xdevillived666 said:
could this possibly work on other carriers?
Click to expand...
Click to collapse
It will work on pixels if the carrier has wifi calling and your provisioned for it. The menus are different on other phones.
Sent from my Pixel using Tapatalk

baknblack said:
It will work on pixels if the carrier has wifi calling and your provisioned for it. The menus are different on other phones.
Click to expand...
Click to collapse
Thanks. I think my carrier has it but in my menu (I have the pixel) I get this :
Will it stillwork?

Xdevillived666 said:
Thanks. I think my carrier has it but in my menu (I have the pixel) I get this :
Will it stillwork?
Click to expand...
Click to collapse
Ps-my wife's S7 has it enabled. I think they do that crap of " we allow it if you get the phone from us and it happens to be a model.we support".

Xdevillived666 said:
Ps-my wife's S7 has it enabled. I think they do that crap of " we allow it if you get the phone from us and it happens to be a model.we support".
Click to expand...
Click to collapse
It's not provisioned for VOLTE so wifi calling won't work. If you talk real nice to someone at customer service they might do it for you.
Sent from my Pixel using Tapatalk

baknblack said:
It's not provisioned for VOLTE so wifi calling won't work. If you talk real nice to someone at customer service they might do it for you.
Click to expand...
Click to collapse
Thanks. I'll go to a location and try.

I ran into the same issue, possibly after Magisk install on custom RR Rom (Marlin/Latest April Oreo build). It had worked one time but I guess installing Magisk was the most recent change I could think of after which it stopped working with the error message reported by OP. Anyways the only thing that worked was to do a "Network Setting Reset" , then setup Wifi (Airplane mode on) again and Wifi Calling settings back to On with Wi-Fi preferred.
Note: Also in "Mobile Network" in Settings, need to ensure "Roaming/Connect to data services when roaming" option is selected for the "Wifi Preferred" option to stick.
.

Anyone enabled BT WiFi Calling with Pixel 3?

Has anyone been able to set up WiFi Calling using Pixel 3 on BT network (UK) ?
People report being able to do so with Pixel 1 and Pixel 2, but I just cannot get it working with my Pixel 3.
Anny advice/suggestions please?

Are you pay as you go or pay monthly?
That I'm aware of, Wi-Fi Calling is only available with EE and for pay monthly customers.
I know BT runs on EE network, but assuming it still works (which I'm not sure about), I would imagine they apply the same restrictions.
Anyway, I'm a EE PAYGo customer and still I do have the option to enable Wi-Fi Calling.
But still, I'm not sure it actually works.

Thanks matteventu, I am a monthly contract payer.
BT definitely DO offer wifi calling - but state that it is primarily iPhone and latest Samsung phones that they support.
Many report success with P1 and P2, so hoping P3 will be OK too....

I'm on EE contract and WiFi calling definitely works.

Stea1thmode said:
I'm on EE contract and WiFi calling definitely works.
Click to expand...
Click to collapse
Seconding, WiFi calling on EE working no problems.
Btw how do you check you have VoLTE enabled? Is there any visual indicator?

M3th0s said:
Seconding, WiFi calling on EE working no problems.
Btw how do you check you have VoLTE enabled? Is there any visual indicator?
Click to expand...
Click to collapse
Just make a phone call. If you see the network switches to 3G/H, then you don't have VoLTE. If during the phone call you still see the 4G/LTE icon, then you have VoLTE.
(Of course, don't be connected to WiFi to make this test call if you also have Wi-Fi calling XD)
The question indeed is: how do I get proof my Wi-Fi calling works?
I know if you enable it in the settings, then if you go in Info on this phone you see that in "mobile network" that it's not connected to LTE/HSPA, but to "IWLAN" - that from I understood stands for Wi-Fi calling.
The question is. I can enable Wi-Fi calling in the settings, and I do see IWLAN as mobile network type for calls (in place of LTE/HSPA) if I'm connected to Wi-Fi. But does this ASSURE me that I'll be using Wi-Fi for calls? Because I am a EE PAYGo customers and according to their info, I am not supposed to be able to use Wi-Fi calling. So, because I have the options it means I am using it, or the option just shows for everybody and if I'm a PAYGo customer even if I have it enablerd, it won't actually work?
Does anybody can think of any test I can do to see if it works?
Thank you!

matteventu said:
Just make a phone call. If you see the network switches to 3G/H, then you don't have VoLTE. If during the phone call you still see the 4G/LTE icon, then you have VoLTE.
(Of course, don't be connected to WiFi to make this test call if you also have Wi-Fi calling XD)
The question indeed is: how do I get proof my Wi-Fi calling works?
I know if you enable it in the settings, then if you go in Info on this phone you see that in "mobile network" that it's not connected to LTE/HSPA, but to "IWLAN" - that from I understood stands for Wi-Fi calling.
The question is. I can enable Wi-Fi calling in the settings, and I do see IWLAN as mobile network type for calls (in place of LTE/HSPA) if I'm connected to Wi-Fi. But does this ASSURE me that I'll be using Wi-Fi for calls? Because I am a EE PAYGo customers and according to their info, I am not supposed to be able to use Wi-Fi calling. So, because I have the options it means I am using it, or the option just shows for everybody and if I'm a PAYGo customer even if I have it enablerd, it won't actually work?
Does anybody can think of any test I can do to see if it works?
Thank you!
Click to expand...
Click to collapse
Thanks for the tip ! Was so used to the volte icon on the s8 that I had no idea how to check .
Allow me to return the favour .
Slide down the notification pane all the way to the bottom and if you have WiFi calling it'll have your network name + WiFi calling next to it .
Screenshot for reference

M3th0s said:
Thanks for the tip ! Was so used to the volte icon on the s8 that I had no idea how to check .
Allow me to return the favour .
Slide down the notification pane all the way to the bottom and if you have WiFi calling it'll have your network name + WiFi calling next to it .
Screenshot for reference
Click to expand...
Click to collapse
Ohhh I see. Then that's why I didn't know if it worked, because I never saw that "EE Wi-Fi Calling" and didn't even know it was supposed to be there with Wi-Fi enabled *and* actually working ?
Thank you, now I'm 100% sure EE stands to their terms lol and I have no Wi-Fi calling as PAYGo customer ?

Finally it works fine. I had to chat with BT Mobile and they had to activate it for me.
Happy Bunny