Database Users

VoIP over mobile network problem

The details:
So I recently acquired my Nexus 4 on the T-Mobile $30 plan, coming from it's brother the Optimus G on Sprint.
It is rooted and running CM11 and I have been using Spare Phone and GrooveIP for VoIP calls with no problems whatsoever. I finally decided to pull the trigger and use the Play Store app to add LTE support since my area supports it. Got that working too so I'm feeling good, but I realized shortly after that I cannot make a VoIP call over data now. WiFi still works perfectly, but on data it will ring and connect but there is no audio sent or received from either party.
I reverted back to my working backup with no luck so I did the adb/fastboot method of returning the phone to the stock image and then rerooting, reinstalling the rom and then testing VoIP over data and still no luck. I then proceeded to reinable LTE and it works again.
So in short, I tried to revert to stock modem and APN settings with no luck, but I am currently on the .98/.33 hybrid modem with the fast.t-mobile apn settings again. Also not sure if something in the *#*#INFO#*#* menu could have messed it up, but that's why I reverted to stock...
The question:
Is there any other reason all of my VoIP apps would stop working over mobile data, but still work on WiFi?

highnoteuser said:
The details:
So I recently acquired my Nexus 4 on the T-Mobile $30 plan, coming from it's brother the Optimus G on Sprint.
It is rooted and running CM11 and I have been using Spare Phone and GrooveIP for VoIP calls with no problems whatsoever. I finally decided to pull the trigger and use the Play Store app to add LTE support since my area supports it. Got that working too so I'm feeling good, but I realized shortly after that I cannot make a VoIP call over data now. WiFi still works perfectly, but on data it will ring and connect but there is no audio sent or received from either party.
I reverted back to my working backup with no luck so I did the adb/fastboot method of returning the phone to the stock image and then rerooting, reinstalling the rom and then testing VoIP over data and still no luck. I then proceeded to reinable LTE and it works again.
So in short, I tried to revert to stock modem and APN settings with no luck, but I am currently on the .98/.33 hybrid modem with the fast.t-mobile apn settings again. Also not sure if something in the *#*#INFO#*#* menu could have messed it up, but that's why I reverted to stock...
The question:
Is there any other reason all of my VoIP apps would stop working over mobile data, but still work on WiFi?
Click to expand...
Click to collapse
A few people including myself have been discussing this issue in the thread I linked below. We haven't really found much out, though it seems that it is T-Mobile at fault when you consider all of the variables. Here is an argument by user Ztone:
"What helped me was arguing that I know five other users who's issue started happening exactly at the same time and only on T Mobile's network. There are only 4 components to this: the phone, groove IP, Google and T Mobile. It cannot be the phone or groove IP if many others are experiencing the same thing at the same time (not to mention the fact that I had wipe the phone and reinstalled everything clean). It can't be Google because then it wouldn't work on wifi. This leaves T Mobile. My Tech troubleshooter from t-mobile had me delete the data from Google IP and restart the phone. While I had the phone off she did something on her end to refresh something on T Mobile's network regarding data coming to my phone, then after I restarted the phone. It still didn't work, then she asked me to try on wifi and then it worked perfectly. That seemed to be the tipping point, when she escalated it to engineering. Whatever that means. But I was told to give it 72 hours. Yeah, I think we need to make some noise to T Mobile."
http://forum.xda-developers.com/nex...30-prepaid-plan-users-thread-t2001290/page322
So did you say when you re-enabled LTE the calls worked again? If so that would be a good temporary fix.

jjflemin said:
A few people including myself have been discussing this issue in the thread I linked below. We haven't really found much out, though it seems that it is T-Mobile at fault when you consider all of the variables. Here is an argument by user Ztone:
"What helped me was arguing that I know five other users who's issue started happening exactly at the same time and only on T Mobile's network. There are only 4 components to this: the phone, groove IP, Google and T Mobile. It cannot be the phone or groove IP if many others are experiencing the same thing at the same time (not to mention the fact that I had wipe the phone and reinstalled everything clean). It can't be Google because then it wouldn't work on wifi. This leaves T Mobile. My Tech troubleshooter from t-mobile had me delete the data from Google IP and restart the phone. While I had the phone off she did something on her end to refresh something on T Mobile's network regarding data coming to my phone, then after I restarted the phone. It still didn't work, then she asked me to try on wifi and then it worked perfectly. That seemed to be the tipping point, when she escalated it to engineering. Whatever that means. But I was told to give it 72 hours. Yeah, I think we need to make some noise to T Mobile."
http://forum.xda-developers.com/nex...30-prepaid-plan-users-thread-t2001290/page322
So did you say when you re-enabled LTE the calls worked again? If so that would be a good temporary fix.
Click to expand...
Click to collapse
Thanks for pointing me to that thread, I'll read up shortly. This all started for me between Saturday night and Sunday morning.
Re-enabling LTE does not fix it. I actually thought that broke it at first, but since reverting to factory settings didn't fix it I figured I might as well continue to enjoy LTE even if VoIP is broken.

highnoteuser said:
Thanks for pointing me to that thread, I'll read up shortly. This all started for me between Saturday night and Sunday morning.
Re-enabling LTE does not fix it. I actually thought that broke it at first, but since reverting to factory settings didn't fix it I figured I might as well continue to enjoy LTE even if VoIP is broken.
Click to expand...
Click to collapse
Yeah, unfortunately we have no solution yet. I'm in the same boat as you. I'm just glad it works over WiFi.

jjflemin said:
Yeah, unfortunately we have no solution yet. I'm in the same boat as you. I'm just glad it works over WiFi.
Click to expand...
Click to collapse
Tonight I'll test Spare Phone on my wife's (my old) Optimus on Sprint. I expect it will work normally and will report back to rule out the app itself since I will be using my same Google account.

highnoteuser said:
Tonight I'll test Spare Phone on my wife's (my old) Optimus on Sprint. I expect it will work normally and will report back to rule out the app itself since I will be using my same Google account.
Click to expand...
Click to collapse
Confirmed that VoIP on data works with Spare Phone and GrooveIP on other networks.

It appears that I am back in business with no change on my part...

[Q] Verizon apps + Root + Move to TMo

I upgraded my unrooted Galaxy S5 to lollipop and it was bad, slow, freezing a lot. I disabled many Verizon-bloatware apps and lollipop is now a buttery smooth beautiful thing!
What pros & cons would rooting a phone generally give me for an average user's experience?
Most importantly, I'm looking to take & convert this S5 phone (and my daughter's Galaxy S3) to T-Mobile this weekend and want to make it all T-Mobile ready. Any insight, thoughts, suggestions, especially if I wanted to root or factory reset my phone but keep app data (such as Kung Fu Pets )?
I've been told by friends and cell providers these phones are already unlocked and can easily switch networks, no worries of voice or data settings on my part, TMo's WiFi calling will work as if I bought the phone from TMo, etc.
Thanks all!

KCSamerica said:
I upgraded my unrooted Galaxy S5 to lollipop and it was bad, slow, freezing a lot. I disabled many Verizon-bloatware apps and lollipop is now a buttery smooth beautiful thing!
What pros & cons would rooting a phone generally give me for an average user's experience?
Most importantly, I'm looking to take & convert this S5 phone (and my daughter's Galaxy S3) to T-Mobile this weekend and want to make it all T-Mobile ready. Any insight, thoughts, suggestions, especially if I wanted to root or factory reset my phone but keep app data (such as Kung Fu Pets )?
I've been told by friends and cell providers these phones are already unlocked and can easily switch networks, no worries of voice or data settings on my part, TMo's WiFi calling will work as if I bought the phone from TMo, etc.
Thanks all!
Click to expand...
Click to collapse
This is my opinion only, with that being said for the average user there is no advantage to being rooted. The average user is not interested in flashing new roms or freezing apps beyond what Verizon allows. The average user wants to turn on their phone and go on their merry way. If something goes wrong they want to call Verizon and have they fix it for them. They would never touch Odin.
With that being said, because your in this forum your more than the average user. If you wan to freeze or uninstall more Verizon/Samsung bloat you need to be rooted.
As for moving to a different carrier I'll let some one who has done that chime in.

jrv331 said:
This is my opinion only, with that being said for the average user there is no advantage to being rooted. The average user is not interested in flashing new roms or freezing apps beyond what Verizon allows. The average user wants to turn on their phone and go on their merry way. If something goes wrong they want to call Verizon and have they fix it for them. They would never touch Odin.
With that being said, because your in this forum your more than the average user. If you wan to freeze or uninstall more Verizon/Samsung bloat you need to be rooted.
As for moving to a different carrier I'll let some one who has done that chime in.
Click to expand...
Click to collapse
Thanks! It won't be a Verizon phone for long, so I guess with rooting it and installing a known stable release be a good idea to get rid of Verizon's bloatware (and maybe some of Samsung's) while keeping a good, hard-working phone? I noticed a big difference disabling what I'm allowed to with Verizon's apps and maybe that's enough, I don't know - any place to research which Verizon and/or Samsung apps are safe to disable (if rooting it & installing a stable release doesn't already remove them)?
Oh, also, is there where I'll go to get future updates since I'll no longer be part of Verizon, and T-Mobile will probably not update my phone since I didn't buy it from them?
Thanks again!

Through a couple phone calls, T-Mobile reassured me both my S3 and S5 would work just fine, everything just the same except I'll have to make sure the phone is unlocked. They also said on both calls that their WiFi calling would most definitely work. Verizon, though a half dozen calls, gave me a different "unlock" story each time. So much for trying to be prepared...
Neither the S3 or the S5 work as expected. The S3 uses the far inferior network speeds and takes about 3 minutes just to send a pic text, and that's only if we're using Hangouts - stock Messages or Verizon's Messages+ don't work on the S3. The S5, I get a lot of "Data (Network) connection lost", setting the time errors, I can't access my voicemail or change my voicemail phone number (not sure if that is a new issue).
So with all this in mind:
1) is the S3 using an inferior data speed network due to hardware limitations or settings I can change?
2) would rooting my S3 and S5 alleviate a lot or all of these issues?
3) any way to get TMo WiFi calling to work on a Verizon phone? Would rooting it allow me to install a TMo version Android?
4) how do I go about updating Android on these phones now that they're off Verizon and not officially TMo phones?
5) any suggestions to fix any or all of these other issues?

KCSamerica said:
Through a couple phone calls, T-Mobile reassured me both my S3 and S5 would work just fine, everything just the same except I'll have to make sure the phone is unlocked. They also said on both calls that their WiFi calling would most definitely work. Verizon, though a half dozen calls, gave me a different "unlock" story each time. So much for trying to be prepared...
Neither the S3 or the S5 work as expected. The S3 uses the far inferior network speeds and takes about 3 minutes just to send a pic text, and that's only if we're using Hangouts - stock Messages or Verizon's Messages+ don't work on the S3. The S5, I get a lot of "Data (Network) connection lost", setting the time errors, I can't access my voicemail or change my voicemail phone number (not sure if that is a new issue).
So with all this in mind:
1) is the S3 using an inferior data speed network due to hardware limitations or settings I can change?
2) would rooting my S3 and S5 alleviate a lot or all of these issues?
3) any way to get TMo WiFi calling to work on a Verizon phone? Would rooting it allow me to install a TMo version Android?
4) how do I go about updating Android on these phones now that they're off Verizon and not officially TMo phones?
5) any suggestions to fix any or all of these other issues?
Click to expand...
Click to collapse
1) probably, but I haven't checked the specs.
2) probably not. The APN in your phone needs to be changed to the right settings for your mobile carrier. It's under Settings/More Networks/Mobile Networks. You should be able to google the settings for TMo.
3) The APN may resolve the issue, if the phone allows for it.
4) If you root, you can do it. You may be able to get OTAs with the new sim, but I can't for Consumer Cellular.
5)Again, the APN will solve a lot of issues. The voicemail number needs to be changed to your carrier's voicemail number under Phone Settings.
5)

Rapunzl said:
1) probably, but I haven't checked the specs.
2) probably not. The APN in your phone needs to be changed to the right settings for your mobile carrier. It's under Settings/More Networks/Mobile Networks. You should be able to google the settings for TMo.
3) The APN may resolve the issue, if the phone allows for it.
4) If you root, you can do it. You may be able to get OTAs with the new sim, but I can't for Consumer Cellular.
5)Again, the APN will solve a lot of issues. The voicemail number needs to be changed to your carrier's voicemail number under Phone Settings.
5)
Click to expand...
Click to collapse
1) probably hardware limitations or probably settings I can change?
2 & 3) the APN was already set by the TMo in-store rep, and google search confirms it's the correct setting.
5) voicemail number just won't change! Ug, I've google searched this issue too, no luck, and it seems many Android 5.0 users have this issue unless they factory reset - an option I'm hoping to avoid for a last resort.
I have noticed by disabling Verizon apps, much is working better, but I'm wondering if Verizon made these apps imperative for the system to run properly...?

KCSamerica said:
1) probably hardware limitations or probably settings I can change?
2 & 3) the APN was already set by the TMo in-store rep, and google search confirms it's the correct setting.
5) voicemail number just won't change! Ug, I've google searched this issue too, no luck, and it seems many Android 5.0 users have this issue unless they factory reset - an option I'm hoping to avoid for a last resort.
I have noticed by disabling Verizon apps, much is working better, but I'm wondering if Verizon made these apps imperative for the system to run properly...?
Click to expand...
Click to collapse
How did you disable the apps? If you used TiBU, there have been discussion of issues in some threads.

Rapunzl said:
How did you disable the apps? If you used TiBU, there have been discussion of issues in some threads.
Click to expand...
Click to collapse
I used the Android's built-in disable feature (since it won't let me uninstall it).

KCSamerica said:
I used the Android's built-in disable feature (since it won't let me uninstall it).
Click to expand...
Click to collapse
The only thing I can think of then, is that one or more of the disabled features are required to make things work properly. I would unfreeze the apps and then freeze them, one-by-one to find out which are causing the issues. Other than that, Kies may be able to repair the install if you don't have luck with unfreezing the apps.

Rapunzl said:
The only thing I can think of then, is that one or more of the disabled features are required to make things work properly. I would unfreeze the apps and then freeze them, one-by-one to find out which are causing the issues. Other than that, Kies may be able to repair the install if you don't have luck with unfreezing the apps.
Click to expand...
Click to collapse
Easiest step is to try the enable/disable apps as you suggested. Have you, or anyone out there, tried loading another's stock software onto a phone before doing a factory reset?
See this page: http://www.andromods.com/download-files/tmobile-galaxy-s5-stock-firmware-sm-g900t.html
It gives me the impression all S5's are the same hardware. If that's true, then why can't I install TMo's stock software in the recovery partition, then do a factory reset? (Another worse case scenario, but possibly more of a thorough cure)

KCSamerica said:
Easiest step is to try the enable/disable apps as you suggested. Have you, or anyone out there, tried loading another's stock software onto a phone before doing a factory reset?
See this page: http://www.andromods.com/download-files/tmobile-galaxy-s5-stock-firmware-sm-g900t.html
It gives me the impression all S5's are the same hardware. If that's true, then why can't I install TMo's stock software in the recovery partition, then do a factory reset? (Another worse case scenario, but possibly more of a thorough cure)
Click to expand...
Click to collapse
If you read toward the end of that post, it says:
Before download check your model number and software version, head to Settings -> About. Confirm that you get the correct firmware that match with the model number of your device, and never use a firmware that isn’t built for your S5, downgrade is also not recommended.
Click to expand...
Click to collapse
I've also seen a thread talking about doing this for a TMo user on the Verizon S5, but I'm on Consumer Cellular, so I'm not sure if it would really work. Even if it does, I'm not sure if that would solve your issues, and I hear you're risking bricking your phone attempting it.

Not sure if I already mentioned, but sadly a couple T-Mobile reps assured me everything would work great. Not. A factory reset did help a lot, but I keep getting these oddities that TMo is now saying I just have to live with, now that my trial period is over. So any ideas and help would be great!
"Data network unavailable" often appears after a phone call and lasts for a few seconds or longer. In that time, I can't get Maps to find anything, among other issues. This error appears at random times otherwise, but most consistently after a phone call.
"SIM error" happens periodically. I'm not sure the pattern yet, but maybe after a couple phone calls in a row, or call swapping. The only way to fix this is to reboot the phone.
The top status bar bounces between "H+" and "3G". I haven't found a pattern as to when or why, but often can't do much with the phone until it settles down, if it settles down.
Everything I've read and originally heard lead me to believe this S5 should work much better than it is, as if some APN or data setting is wrong. I've triple checked and they seem to be set properly, but I don't know anymore...

No VOLTE and no WiFi calling T-Mobile, what gives?

I'm gonna make a post here since NOTHING seems to be working. I'm a T-Mobile customer. Yesterday, I purchased a great condition nexus 6P from someone because my LG G5 is cracked and I was getting tired of it anyway so I opted to just buy a nexus instead of using my insurance on that phone. Everything is all good except for one major issue. VOLTE and WiFi calling just refuse to work with my sim in the Nexus.
I've called T-Mobile twice. I've factory reset from back up and reset settings twice. I've hard reset from stock recovery once. I've wiped network settings and restored default apns. I've manually changed the apns from what I see on Google, reddit and here. I've copied my apns from my LG G5 where VOLTE and wifi calling work perfectly fine. I've cleared cache. I've cleared the cache of the project fi and hangouts apps just in case there's something left over from the previous owner. I've gone into the *#*#4636 menu and tried a bunch of different stuff several times but no matter what I absolutely can not get wifi calling or VOLTE to work with TMobile on my nexus 6P. LTE it's self works perfectly fine for data.
Yes, all settings for wifi calling and enhanced LTE calling and VOLTE are turned on lol. I've tried the trick where you toggle wifi preferred on and off and restart the phone. Nothing happens. I don't even get a wifi calling reg error. It never shows as active in the data toggle in the quick settings are nor the status bar or dialer. It just isn't active. Same for VOLTE. I AM getting band 12. I can see it in the LTE discovery app. VOLTE just isn't working though. Whenever I make a call I can see LTE switching off and it switches to HSPA therefore making calls really difficult in my shoddy signal area at my house which is why I really need it to work.
I'm fairly certain I can root and install a ROM which will fix these problems but I don't own a PC. . I thought MAYBE the previous owner had previously had the phone rooted and tinkered with something somewhere that may have messed something up but that doesn't appear to be the case. Bootloader is locked and recovery is stock.
Can anybody help and tell me what in the world is going on here? I don't want to have to sell this nexus and revert back to my cracked screen G5. I would just switch carriers but I still owe money on the G5 so I was just gonna ride it out til I payed it off.
O and one last thing, after scowling google and forums for hours on end yesterday and today I did see one post mentioning something about this stuff being related to IMS provisioning and settings which are tied to a phones IMEI on T-Mobile and not the sim card and how that person simply called T-Mobile and got a hold of wifi calling technical support who was clueless but created a ticket for him and within 72 hours the issue was resolved. OK well I did the same exact thing and they refuse to create a ticket for me because it's not a T-Mobile phone and because according to them they are not allowed to create a ticket because wifi calling works fine in my G5 and therefore it's the phone and not them or their network lol. What a crock. I'm willing to bet if I put the sim in another unlocked phone with 7.1.1 and wifi calling fully available that it isn't going to work either. There's some sort of communication error going on between the sim being in this phone and their network it appears.
Check these screenshots out. T-Mobile is clueless
http://imgur.com/5MuO34s
http://imgur.com/XVd8CdA
http://imgur.com/uUGN3ae
http://imgur.com/cfYxfqh

I can only suggest;
1) Find a PC and re-flash the latest factory images from Google. Both "fastboot flashing unlock" and "fastboot flashing lock" will wipe all data, so backup first. Also confirm it fully boots correctly after flashing before you re-lock the bootloader.
2) Get a new 3-in-1 SIMM from T-Mobile. You can use their web site to switch cards and give it 24 hours to be fully provisioned.
3) Confirm your E911 address is correct on T-Mobile's site and wait 24 hours after any changes for Wi-Fi calling to actually start working.

I HAVE THE SAME EXACT PROBLEM AS YOU POSTED!!! GONE THRU THE SAME PAIN. LOL I'll attempt the ticket thing to see if I get anywhere. Did you ever get it resolved?
EDIT:
My theory is that since the phone was used in Project FI, they specifically turn off this feature in the back end for the specific phones, by Imei or something since project FI uses T-Mobile as well.
EDIT 2:
they wont' create a ticket for me either. I guess I will just have to ride it out.
EDIT 3: I FIXED IT!! NEXUS 6P VOLTE AND WI-FI CALLING FIX T-MOBILE
I flashed back to android 6.0 Build#: MMB29N (I used the Nexus ToolKit 2.1.9: google it. BTW, your phone will be wiped, so backup first) VOLTE just started working with this version of android 6.0. Then I upgraded using the OTAs and now i'm on 7.1.1 build#: N4F260 with VOLTE and Wifi calling working as it should! I hope this helps someone out there!

For what it's worth, reverting to the build you mentioned fixed it for me on my two Nexus phones coming from Project Fi to T-Mobile as well! Thanks for the help!

You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.

banancanard said:
You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.
Click to expand...
Click to collapse
wish I had seen this sooner. cheers!

Had the exact same issue and this fix worked for me. Wasted a couple of hours with T-mobile (they were actually very helpful and debugged everything on their end to confirm the provisioning was good) and then 2+ hours with Google support. Actually had already filed for a device replacement which I canceled after finding this post.

I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?

k2kevink2 said:
I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?
Click to expand...
Click to collapse
Flashing the radio -sadly- requires an unlocked bootloader.

Did you resolve your problem?
In android 7.1.2 did you notice in Set preferred network type is set at " LTE/GSM/CDMA auto (PRL) "? 7.1.2 has been giving me issues with sms/mms. I noticed Android 6.0 has this set to correct T-mobile bands.

All works for me in 7.1.2. Make sure you don't download the Verizon version of the stock ROM. That was my issue why I couldn't have volte and Wi-Fi calling

Verizon Essential stuck in 3G after the upgrade

Before I updated via OTA to 8.1 the Essential was connecting to LTE without issue. Since 8,1 I have to connect to CDMA and 3g in order to user my Dialer, otherwise Server Error is generated. No calls in or out.
I wanted to downgrade Yes rebooted, factory reset, etc.
I searched google up and down with no real answers that work. How do I get Sideload working again? It has to be a simple configuration or driver problem I will assume.
Thanks

Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....

Exxeviant said:
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506

wolfu11 said:
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
Click to expand...
Click to collapse
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.

Bigdny said:
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Click to expand...
Click to collapse
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).

wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached

wolfu11 said:
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
Click to expand...
Click to collapse
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.

wolfhelm said:
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
Click to expand...
Click to collapse
Yeah I've screwed with this phone so much I don't know what I did LOL but now it shows wifi calling even in dialer. I'm not sure if it really works cuz I have a good signal so it never switches. My e911 address is set up from my Moto z and I do have a wear24 watch tied to this phone not sure if that's what triggered it. ? I did get a new SIM card on Monday as well because I was fighting with the vzw crap so I don't know exactly what triggered the WiFi calling.

wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.

Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?

wolfhelm said:
Are you on 8.0 or 8.1?
Click to expand...
Click to collapse
I upgraded to 8.1 via OTA. No root, no rom.

Bigdny said:
I upgraded to 8.1 via OTA. No root, no rom.
Click to expand...
Click to collapse
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.

wolfhelm said:
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
Click to expand...
Click to collapse
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?

tech_head said:
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
Click to expand...
Click to collapse
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.

wolfhelm said:
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
Click to expand...
Click to collapse
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.

tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
That's a good point, I have reported as well.

tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
Doing the same right now. Just glad Im not the only one having the problem.

Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Try turning off Enchanted 4G LTE Mode. It's possible going to 8.1 just reset this setting to on. This should only be on if you have HD Voice enabled on your line on Verizon (you'll have to call Verizon to enable it, it's a free feature).
This should fix server error on 4G, randomly connecting to Sprint is a separate issue.

UPDATE Now working
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.

Bigdny said:
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Click to expand...
Click to collapse
Just wanted to second this post that a new sim card is the key to solving this issue. In my case, I was using Red Pocket CDMA (VZW network), and I ran into the same problem. Red Pocket rep explained to me that my sim got provisioned to 3g only and that I needed a new sim to connect to LTE. As soon as we switched to a new sim, I got LTE. I hope this helps others.

Accidentally sideloaded verizon full image

So I was rooting my Google store bought pixel 4 and missed a step. Needless to say I had to sideload a full ota to recover it. But I'm pretty sure I accidentally loaded the verzion version. I got all the verizon apps that showed up when I rebooted the phone. I went back and wiped everything in recovery mode and tried sideloading QD1A.190821.007.A3 and it keeps erroring out. This is the firmware that Im 90% sure what was on my phone. Is there a way to get back to factory google store firmware or am I screwed now? I am on a verizon sim but phone was bought on launch day from the google store. Its also noted that I am currently on QD1A.190821.014 firmware. This doesn't appear to be the verizon firmware.

The Verizon apps appear not based on which ROM version you load, but instead based on whether you have a Verizon SIM in the phone during setup.
If you loaded the wrong ROM onto the phone, you may not be able to recover by sideloading an OTA. You should be able to recover by doing a complete reflash of the image you want (the image version, not the OTA version).
What error is it giving you?

I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.

BubbaGumprc said:
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
Click to expand...
Click to collapse
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.

Jon8RFC said:
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Click to expand...
Click to collapse
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?

bobby janow said:
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
Click to expand...
Click to collapse
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.

Jon8RFC said:
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Click to expand...
Click to collapse
My wife has a Verizon device Pixel 3 locked bl and I have a Pixel 4 and they both have MVS disabled and both can call on wifi. I just tested again to make sure. Really, I'm the only one? Gotta love that. I hate that they can get into my device without my knowing and see what and when I installed stuff.