Wifi Calling Service on BYOD Unlocked Phones

[BRIMAC41]

When will Vz certify/activate the use of Wifi calling on BYOD unlocked phones?

Currently I do have HD Calling / Wi-Fi Calling provisioned on my account.

I purchased a Moto X4 standard (XT-1900-1) directly from Moto after verifying from Moto & VZ that the phone was fully compatible with the Vz network.

However, it appears that Vz will not allow unlocked BYOD phones to use their Wi-Fi Calling feature (unlike T-Mobile, Sprint and AT&T).  after many hours of troubleshooting on the phone & web with both tier 1 & 2 support at VZ & Moto the only answer that I get is that it should work but each company blames the other for the issue.

I would note that the phone currently has Oreo 8.0.0 and there are no options within the settings menus to activate or turn on/off Wif calling.

I have tried to turn off your Cellular data when making the call to have it force a switch to Wi-Fi Calling with with no luck.

I even took a look at the newest Vz network extender 2.  Unfortunately, my Vz HDSL only provides 4-6 Mbps Down & 0.5-0.8 Mbps Up which is substantially less than Vz's minimum requirement of 10 Mbps Down & 5 Mbps Up and woefully lower than VZ's preferable rates of 20 Mbps Down & 10 Mbps Up.

I have been a loyal customer for more than 30 years residential and more than 20 years wireless & Internet.

There must be some way for Vz to activate the Wifi Calling feature for BYOD phones since the phones that they sell are unlocked currently.

If that is not possible, will Vz be bringing the X4 to there lineup with the Wifi calling  feature functional?

[boringusername]

BRIMAC41 wrote:

When will Vz certify/activate the use of Wifi calling on BYOD unlocked phones?

Never. Each carrier handles it differently, so if you want/need wi-fi calling on Verizon you need a Verizon version of a phone. Only VoLTE will work on unlocked phones, wi-fi or video calling will not.

[bugl3t]

So BYOD is garbage. Only a VERIZON purchased phone allows you to have wifi calling even if the device has HD calling

Content modified as required by Verizon Wireless Terms of Service

[rcschnoor]

bugl3t wrote:

So BYOD is [removed]. Only a VERIZON purchased phone allows you to have wifi calling even if the device has HD calling

This is incorrect. I have a 1st generation Pixel and a Pixel 3 which are BOTH the unlocked version purchased directly from Google and NOT the Verizon version. Both of these devices have wifi calling activated on the devices and it works just fine.

I also have 2 unlocked iPhone 7's on my account with wifi calling available, I believe.

[Intel1919]

Yep, I can confirm I cannot add wifi calling (get it to work) on my Samsung Note 8, sourced directly from Samsung.  Before I saw this thread, I did activate the feature on my account.   I even called in, got transferred to level 2.  They confirmed the feature is activated on my line, but were perplexed the control for feature (advanced calling) is not showing in Settings --> Connections (after rebooting, waiting an amount of time). 

Visual vm is the same type of issue.  Won't work on a non-vzw purchased device. 

Sorry Verizon, you could very easily solve this by allowing us users to download an app from the Play Store, where it only would work with a vzw account, and feature activated within the account. 

Classic "control" by VZW NJ engineering.  They HATE wifi calling for the simple (and reasonable) reason is they cannot control the experience of the call.  That was the answer I received 3 or 4 years ago when I owned the carrier relationship for a large Enterprise, asking the same question to VZW when other carriers did this.  Looks like nothing has changed......

Our argument t then, as it now, give me choice and let me decide the best network to use.  I am a bit surprised this has not been resolved.  I think a may need to look at one of the other networks then.  Probably won't leave as VZW, IMO, is still a superior network for how/where I use it.

[boringusername]

Intel1919 wrote:

Classic "control" by VZW NJ engineering. They HATE wifi calling for the simple (and reasonable) reason is they cannot control the experience of the call.

Wrong. If that was true they would allow wi-fi calling AT ALL. If you think Verizon is so shady and terrible then switch carriers

[Intel1919]

@ boaringusername....  I never said anything about VZW "is so shady and terrible" -- in fact, I stated "....  VZW, IMO, is still a superior network for how/where I use it.  How you made the jump to your statement is interesting, at best.  My comments are valid that they do not like WiFI calling for the reasons I post.  Sales/marketing won that round vs. Engineering. 

I am stating my observed behavior with this feature (and another one).  I can tell you from experience, someone that is very technical in the Enterprise Mobile space + who has experience with VZW (10,000 + lines of service, manage complex in-building cellular (iDAS) deployments for 3G/4G coverage within large venues (shared architecture for all carriers to join), and they were the last ones to support WiFi calling.  My team would beat them up continuously about this feature so our teams could use WiFi in areas of our properties that had better WiFi coverage vs. cellular.    I am referencing a culture there, i.e. VZW NJ (Headquarters) culture.  They have a chip on their shoulder, have a great network for past 10 years, and only recently (last few years) realizing they have competition from folks like TMO and handful of MVNOs as well. 

Thanks for the suggestion (obvious) -- I have a choice at this point, either get a VZW sourced device or move to another carrier. 

[IronJoe]

There is a lot of misleading information here.  Verizon WiFi calling is not different than T-Mobile WiFi calling.  Wifi Calling is WiFi calling now in 2019.  I had a iPhone Xs and had WiFi calling enabled.  I returned this phone to go back to my OnePlus 6T (OnePlus is a better phone for me) and WiFi calling WAS working until I updated my IMEI on My Verizon.  Now it doesn't even show up on my phone settings.

I also have a Mint Mobile SIM in the same phone and Wifi calling and text both works just fine.  Same as visual voicemail.

It's VZ limiting us from using it on unlocked phones because I am assuming they make money by selling phones. 😉

[JoeyRoda]

---

@IronJoe wrote:

There is a lot of misleading information here.  Verizon WiFi calling is not different than T-Mobile WiFi calling.  Wifi Calling is WiFi calling now in 2019.  I had a iPhone Xs and had WiFi calling enabled.  I returned this phone to go back to my OnePlus 6T (OnePlus is a better phone for me) and WiFi calling WAS working until I updated my IMEI on My Verizon.  Now it doesn't even show up on my phone settings.

I also have a Mint Mobile SIM in the same phone and Wifi calling and text both works just fine.  Same as visual voicemail.

It's VZ limiting us from using it on unlocked phones because I am assuming they make money by selling phones. 😉

---

This is true, I have a Moto G6 Unlocked XT1925-6. I switched from Metro by TMobile and I had WiFi calling with their sim card and upon switching and putting the Verizon sim card in, the WiFi calling option in my settings is not there anymore.

[kidhudi]

so basically to have wifi calling on a oneplus device is not going to happen on the verizon network even though it is an accepted BYOD?

https://www.verizonwireless.com/articles/unlocked-oneplus-6t-smartphone-at-verizon/

guess we gotta start looking at t-mobile or metropcs then 

terrible

[MIElectric]

your comment was unhelpful, unproductive, unneeded, and very unintelligent. Which makes you a troll. Please refrain from unintelligent comments like, "well if you dont like it then just leave it" the whole purpose of discussion groups is to improve things, If you cant complain then people who can implement changes dont know what to change to make peoples use of their products better. With your thinking we should have kept slavery and just moved somewhere that didnt have it.

I for one would like to see phone makers, and service providers open up the market and allow all services on any phone to be transferable to another service provider. I understand the difference of cdma and gsm, and it does seem a bit much to have both in a single device, but it can be done. But even if that was the limitation that a cdma phone cant got to a gsm network, it would be nice is everything else worked.

Think about it, I buy a phone because it suits me, now I chose which service provider works for me, but what if I move and that service provider doesnt have service, now I have to get another phone and move all the apps/settings/etc to a new phone? It would be much better to be able to have it work in all aspects with another service provider.

[Garyrate1974]

They are shady.  Same thing happened to me on my Note 8.  I rooted the phone, turned on the service, and Verizon still refused to turn it on.  Did you hear that???  I turned it on, was all set.  They illegally claim they won't update the software because it is a Samsung manufactured phone.  Who do they think they are kidding? Samsung makes the phones either way.  They want to make sure you can't leave because you don't have the additional antennae included in the unlocked phones.  Hear that???  Port your number... nope... trade in your unlocked phone to be artificially and synthetically locked in.

They forced me to send my Samsung phone back, and buy their piece of garbage.  Same phone, but ran so much slower, battery drained so much faster too.  Just awful the cronyism that goes into these companies.  I pray that Tmobile/Sprint don't merge.  I was just looking into switching to T-mobile to get away from the over-priced Verizon.  I have to go into airplane mode just to use the wi-fi calling.  I never had to do that with Sprint.   Truth is only that Verizon inundates you with their bloatware to try to sell you needless services.

It's like buying a TV and the cable company saying nope... you can't use our signals on that device.  Imagine that.  That is the next thing that is going to happen.  Break the companies up.  They are wasteful, and not doing anybody any favors.    

[tgm1024]

---

@Garyrate1974 wrote:

They are shady.  Same thing happened to me on my Note 8.  I rooted the phone, turned on the service, and Verizon still refused to turn it on.  Did you hear that???  I turned it on, was all set.  They illegally claim they won't update the software because it is a Samsung manufactured phone.  Who do they think they are kidding? Samsung makes the phones either way.

---

No, that part isn't quite right.  My S10+ (bought directly from Samsung) *does* work, however the software compatibility issue is both the issue of the manufacturer's sofware and the carrier's.

As a software engineer, I've dug into this much further than I wanted to, but I was curious and this is what happens AFAICT:

1. In my case, the WiFi calling software from Samsung for the S10+ (bought from Samsung) wasn't entirely compatible with the Verizon network so after a rep enabled it on their end, Verizon auto-downloaded a couple small pieces of software when I got home (perhaps linux driver level for all I can tell from here) and it worked.

2. MOTIVATIONS ASIDE, In the case of older phones, they either (A)Never wrote the software for downloading to non-carrier phones (this part is silly, because it's the same code and simply a matter of making sure you set up an appropriate packaging to not assume that certain pieces of software are already there that would be there if the full carrier skin was there) or (B)Couldn't figure out how to separately download the parts of the carrier skin that it needs.

3. In the case of T-Mobile, the manufacturer drivers of various phones (for all I know it's because of the boot loaders...I simply cannot fault-isolate that without looking at the source code) have built-in WiFi calling connected software that is compatible enough already to work (with T-Mobile).

4. The built-in WiFi calling software of all recent Google Pixels is compatible enough with Verizon to work out of the box.

5. In the case of Apple, there's never any issue.  Everyone bends over backwards so far to make sure their WiFi calling always works no matter what, because no one dares tick them off for any reason and it's job 1 of Apple and Verizon to have no hiccups.  In fact, I have no doubt whatsoever that Apple is the very first manufacturer they worry about.  Apple mobile devices (a single manufacturer with their single OS) are now at 45% saturation.

[dwatson808]

---

@tgm1024 wrote:

---

4. The built-in WiFi calling software of all recent Google Pixels is compatible enough with Verizon to work out of the box.

We have two Google Store Pixel 2s. Because we know our current house has problematic coverage, we ported back to VZW and got Pixel 2s, solely because of support for WiFi Calling and we were assured at the time that this applied to Google Store Pixel 2s.

WiFi Calling on VZW worked sometimes on Oreo; but in the early days, 1Q18, WiFi Calling kept mysteriously turning off in the phone for no apparent reason. Somewhere along the way (Pie? A "Phone" app update? A "Carrier Services" update? A Pixel 2 fix/security update? Something VZW did?) WiFi Calling stopped randomly turning off and kinda, sorta, worked OK. The qualifier is because the phones will try Wireless first even in signal situations where an outgoing call wouldn't complete or an incoming call would ring but would disconnect upon answering. When the phones were showing "Verizon WiFi Calling", WiFi Calling worked as expected.

Sometime about a month ago, WiFi Calling for our Pixel 2s stopped working except for very occasionally. Even with no wireless signal, with WiFi working fine for all other apps, we no longer see "Verizon WiFi Calling" and cannot place or receive calls. This was true for both of us when one of us was running Pie and the other Version 10. It's true with both of us running Version 10. It's true at home. It's true in Airplane Mode/WiFi On at Starbucks on a different ISP, different WiFi, different router.

Google Store Pixel Support told me WiFi Calling working or not has nothing to do with them. (I was told it's a Verizon app like Facebook is a Facebook app.) Verizon says it's some (completely non-specific) problem with both of our devices. One of them suggested that it's because the phones are the nonVZW models. (In four other phone/live chat sessions, they've all noted they were nonVZW but said they should work despite this.) Some people at VZW have said it should work and they are setup/provisioned correctly--and in some troubleshooting moments--VZW forces some kind of feature sync to the phones while they are off--we've had it connect to Verizon WiFi Calling and work for multiple calls. Sooner or later, it stops working again.

Maybe some Google code update broke things. Maybe VZW threw some bits deep in their network bowels to kill WiFi Calling for nonVZW Pixel 2s. Who knows? Regardless, our phones, at home, are little more now than tiny WiFi tablets.

Until the government steps in and forces the carriers to support BYODs equally with devices they sell, similar to what was once done to separate hardware from service on wired carriers, under some kind of compatibility test regime or third party certification or something, the only way to have a prayer of long term reliable operation of WiFi Calling on VZW seems to be either buying Apple iPhones (because VZW does care about making all iPhones work, and, frankly, it's a lot simpler for them to do so because there are so many iPhones out there and so few software variations on them) or buy your phones from VZW, with their branding spewed all over it, their crapware, and their SIM locks. VZW especially, but any carrier in general, presently has very little motivation to care if BYOD devices work well on their networks and they have conflicting economic motivations to "encourage" their service customers to also be their hardware customers.

[NewOldcustomer]

---

@dwatson808 wrote:

---

@tgm1024 wrote:

---

4. The built-in WiFi calling software of all recent Google Pixels is compatible enough with Verizon to work out of the box.

We have two Google Store Pixel 2s. Because we know our current house has problematic coverage, we ported back to VZW and got Pixel 2s, solely because of support for WiFi Calling and we were assured at the time that this applied to Google Store Pixel 2s.

WiFi Calling on VZW worked sometimes on Oreo; but in the early days, 1Q18, WiFi Calling kept mysteriously turning off in the phone for no apparent reason. Somewhere along the way (Pie? A "Phone" app update? A "Carrier Services" update? A Pixel 2 fix/security update? Something VZW did?) WiFi Calling stopped randomly turning off and kinda, sorta, worked OK. The qualifier is because the phones will try Wireless first even in signal situations where an outgoing call wouldn't complete or an incoming call would ring but would disconnect upon answering. When the phones were showing "Verizon WiFi Calling", WiFi Calling worked as expected.

Sometime about a month ago, WiFi Calling for our Pixel 2s stopped working except for very occasionally. Even with no wireless signal, with WiFi working fine for all other apps, we no longer see "Verizon WiFi Calling" and cannot place or receive calls. This was true for both of us when one of us was running Pie and the other Version 10. It's true with both of us running Version 10. It's true at home. It's true in Airplane Mode/WiFi On at Starbucks on a different ISP, different WiFi, different router.

Google Store Pixel Support told me WiFi Calling working or not has nothing to do with them. (I was told it's a Verizon app like Facebook is a Facebook app.) Verizon says it's some (completely non-specific) problem with both of our devices. One of them suggested that it's because the phones are the nonVZW models. (In four other phone/live chat sessions, they've all noted they were nonVZW but said they should work despite this.) Some people at VZW have said it should work and they are setup/provisioned correctly--and in some troubleshooting moments--VZW forces some kind of feature sync to the phones while they are off--we've had it connect to Verizon WiFi Calling and work for multiple calls. Sooner or later, it stops working again.

Maybe some Google code update broke things. Maybe VZW threw some bits deep in their network bowels to kill WiFi Calling for nonVZW Pixel 2s. Who knows? Regardless, our phones, at home, are little more now than tiny WiFi tablets.

Until the government steps in and forces the carriers to support BYODs equally with devices they sell, similar to what was once done to separate hardware from service on wired carriers, under some kind of compatibility test regime or third party certification or something, the only way to have a prayer of long term reliable operation of WiFi Calling on VZW seems to be either buying Apple iPhones (because VZW does care about making all iPhones work, and, frankly, it's a lot simpler for them to do so because there are so many iPhones out there and so few software variations on them) or buy your phones from VZW, with their branding spewed all over it, their crapware, and their SIM locks. VZW especially, but any carrier in general, presently has very little motivation to care if BYOD devices work well on their networks and they have conflicting economic motivations to "encourage" their service customers to also be their hardware customers.

---

 The pixel phones are all equally compatible, no matter where you bought them.   If your having a problem, it’s a defective phone/s.  If you are under warranty, use it.  Even if out of warranty, complain to google.  

Pixel 3/3xl are the first non carrier android you can take to any US carrier and get equal treatment as far as features like Wifi calling   

[dwatson808]

I complined to Google. They couldn't have cared less. Maybe I didn't complain to the right place? Every Verizon Support person we've tried to work on this with has sneered at our nonVZW Pixels although only one of them was explicit in suggesting this was the source of he problem. (AT&T to this day will not provision WiFi Calling to non-AT&T sourced Pixels 2s.)

Having two separate phones, both of which do everything we ask of them on WiFi except WiFi Calling--and even that has been seen to work at times, and was working regularly until a month or so ago--be somehow hardware defective and worthy of warranty swap seems really hard to fathom.

At the moment, we are using Google Fi on the eSIMs on both phones, with almost flawless performance at home vs. almost zero performance from VXW, and trying to figure out what's next. Probably cancelling VZW.

[NewOldcustomer]

---

@dwatson808 wrote:

I complined to Google. They couldn't have cared less. Maybe I didn't complain to the right place?   Are you out of warranty?   Without warranty coverage you’re spitting into the wind with google  

Every Verizon Support person we've tried to work on this with has sneered at our nonVZW Pixels although only one of them was explicit in suggesting this was the source of he problem. (AT&T to this day will not provision WiFi Calling to non-AT&T sourced Pixels 2s.)

  It’s NOT   I have owned all 3 generations of pixels, purchased direct from Google at launch and used on prepaid  all 3 worked with Wifi calling on Verizon prepaid  

At&t NEVER SOLD Pixel phones.  Still doesn’t.  AT&T never allowed the pixel 2 to have Wifi calling   They did eventually get HD voice   Only the pixel 3 and 3 xl have Wifi calling   Not the pixel 3a/3aXL

Having two separate phones, both of which do everything we ask of them on WiFi except WiFi Calling--and even that has been seen to work at times, and was working regularly until a month or so ago--be somehow hardware defective and worthy of warranty swap seems really hard to fathom.   If it never worked at all you could have made a case for it being a non carrier phone.  Intermittent or poor working = defective phones or really bad Wifi.  If you have slow satellite internet you could point to that.  

At the moment, we are using Google Fi on the eSIMs on both phones, with almost flawless performance at home vs. almost zero performance from VXW, and trying to figure out what's next. Probably cancelling VZW.

---

[dwatson808]

Our WiFi/ISP is an ASUS RT-AC68U / 300/20 terrestrial cable, fast and reliable for all purposes of a dozen of so WiFi devices including 3 iPads, a Kindle, Google Home Mini, Chromecast Audio, JBL Playlist 150, Chromebook, Dell XPS13, 2017 MacBook Pro, 2 Pixels 2s, etc. These all work fine on our WiFi, with the sole exception of WiFi Calling with our Pixel 2s in the last month or so. E.g., both phones downloaded and installed Version 10 over the WiFi just fine. I installed Windows 10 1903 on a laptop just fine over WiFi. And any number of GB+ MacOS updates. The Mac and Dell both back themselves up over the WiFi to our NAS continually. I stream to Google Home Mini, JBL Playlist 150, or Chromecast Audio over our WiFi. We watch streaming video on iPads, Chromebook, XPS13, MacBook Pro over our WiFi just fine. Google Fi outgoing/incoming calls over WiFi from the exact same Pixel 2s work just fine. In the last 24 hours, my Pixel 2 passed 344 MB of traffic over our WiFi, per the router's traffic stats. Only 2x Pixel 2s WiFi Calling with VZW fails to work.

Both of our Pixel 2s WiFi Calling also mostly did not work at Starbucks on a completely different WiFi/router/ISP setup when we went there to test the (Verizon Support) theory that the problem was our WiFi/router/ISP. (One of them even said if my router was over two years old I needed to replace it. I'd installed an ASUS firmware update, issued September 5th, one day earlier. The router model we have is still in current production/distribution.) I say WiFi Calling at Starbucks mostly did not work because we tested both phones a total of nine or ten times and I had WiFi Calling come up and connect exactly once on my phone; never on my wife's phone. Made a test call. It worked great. Turned off WiFi and turned it back on. Even three or four minutes later, "Verizon WiFi Calling" was nowhere to be seen and attempts to place calls failed saying phone was in airplane mode and had no wireless network connection. Web browsing, YouTube, receiving/sending email all worked fine over Starbucks' WiFi the whole time. Only WiFi Calling with both Pixel 2s and VZW mostly failed to work.

I can only conclude that the problem is not our WiFi/router/ISP.

At one point Friday, I changed my phone from using Google Fi eSiM to VZW hardware SIM to see if I had any SMS/MMS messages pending delivery at VZW. The phone came up within ten or fifteen seconds saying "Verizon WiFi Calling". I placed a test call just fine. Put phone in airplane mode for ten seconds or so. Disabled airplane mode. Phone came back up, typically for that location in our house, No Service. Within a minute or so, it had received enough VZW to say "Verizon" but with no bars alternating no signal. And no WiFi Calling. Attempting to place a call failed with "No Wireless Connection". Phone was receiving email over WiFi. I could browse the web on the phone over WiFi. Or watch a YouTube video on the phone over WiFi. But no Verizon WiFi Calling. I restarted the phone. Exact same situation. Piddling amounts of Verizon wireless signal. Other WiFi connectivity working fine. No "Verizon WiFi Calling". No ability to place calls since no wireless network. Changed back to the eSIM/Google Fi and placed a test call successfully over WiFi within a matter of seconds after phone started showing Google Fi in upper right corner of Quick Settings panel. And so it goes.

/rant

[dwatson808]

---

@NewOldcustomer wrote:
I have owned all 3 generations of pixels, purchased direct from Google at launch and used on prepaid  all 3 worked with Wifi calling on Verizon prepaid
...
If it never worked at all you could have made a case for it being a non carrier phone.  Intermittent or poor working = defective phones or really bad Wifi.  If you have slow satellite internet you could point to that.

---

We are postpaid, FWIW. I also owned a Pixel (OG) until its audio codec failed. (And we've owned Google Store 2x Nexus 1s, Galaxy Nexus, Nexus 4, Nexus 5, Nexus 5x.) We were on AT&T with a microcell when I had the Pixel (OG). When I replaced the dead Pixel with a Pixel 2, I tried to make it work with AT&T WiFi Calling, and found out about AT&Ts attitude about non-carrier phones and WiFi Calling. I was hoping to make WiFi Calling work since the microcell had limitations (no WEA delivery, to name one) and since AT&T was reported to be planning to end microcell support within the year. That's when we bought my wife a Pixel 2 and ported back to VZW after a decade away on AT&T. We went back to VZW solely to have our Pixel 2s work with VZW WiFi Calling.

To be clear, I don't think our WiFi Calling problem is because we have nonVZW Pixel 2s. (Most VZW Support I've worked it with didn't seem to think so either.) I think it's just something convenient for flumoxed Support people to blame when all else fails.

I also don't think it's defective Pixel 2 hardware.

I think it's because some VZW network side change, or change they pushed to the phones, or some Google System Update or Play Store "app" update of something like Play Store services or "Phone" or "Carrier Services", changed something that, in our environment and/or location breaks WiFi Calling.

It's funny you should mention Satellite Internet. We do not have that kind of latency. But we are located in the middle of the North Pacific and our Internet latencies for connections to out-of-state hosts are higher, always, on all connections, than they would be if we lived in, say, Los Angeles. Could that be the source of this issue? How could I possibly determine this?

(We will be going to Phoenix later this week. In addition to continuing our Google Fi trial run, I will certainly test VZW WiFi Calling while we are there. If our Pixel 2s and VZW WiFi Calling make happier there than at home, sensitivity of the VZW/Pixel 2 WiFi Calling protocol stack to our relatively higher latency at home would become a prime suspect in my mind. What I could do about it with that knowledge, besides move back to the mainland, is not clear.)

[NewOldcustomer]

Your willingness to trouble shoot (aka tolerate) exceed mine.  I would have harassed Google for a warranty replacement.   

[dwatson808]

If I had ANY evidence that the problem was broken hardware, I surely would have.

Oh, and FWIW, yesterday morning, for an hour or so, we popped back to VZW. We both had the absolute best WiFi Calling functionality we've ever had from them. By last evening, we were back to none at all.

[NewOldcustomer]

---

@dwatson808 wrote:

If I had ANY evidence that the problem was broken hardware, I surely would have.

Oh, and FWIW, yesterday morning, for an hour or so, we popped back to VZW. We both had the absolute best WiFi Calling functionality we've ever had from them. By last evening, we were back to none at all.

---

A defect in software is still a defect.  Factory reset might resolve it.  So might replacement.  🤷🏼‍♀️