Related
I have been trying to get wifi calling with AT&T is working on my International S7 edge. I have made headway.
1. First of all I told AT&T I had their branded S7 edge and gave them an IMEI that will show up that phone. So I can activate my phone.
2. I have narrowed down the required apks to the following, but some are obviously for the Wifi Calling, and other's I am not sure. If people know what some of these apks do, please let me know.
3. I have used the Note 7 Port and flashed TTKG CSC selection and chosen the ATT CSC, we are still working on getting it working in the S7 and Edge CSC.
4. The following APK's I feel are related to Wifi Calling are.... If you can help me eliminate some that aren't. They are deodexed, and I have uploaded them, you will need to change the permissions to match the ones in the system folder.
atfwd
ATTVoWifiSPG
com.quicinc.wbcserviceapp
NSDSWebApp
VolteSettings
vsimservice
WAPPushManager
Wispr_ATT
AppSelect_ATT
5. I am unsure if I need to make Buildprop changes or I am missing other system files. I was able to activate wifi calling and turn it on, but it doesn't work.
Psyscope said:
I have been trying to get wifi calling with AT&T is working on my International S7 edge. I have made headway.
1. First of all I told AT&T I had their branded S7 edge and gave them an IMEI that will show up that phone. So I can activate my phone.
2. I have narrowed down the required apks to the following, but some are obviously for the Wifi Calling, and other's I am not sure. If people know what some of these apks do, please let me know.
3. I have used the Note 7 Port and flashed TTKG CSC selection and chosen the ATT CSC, we are still working on getting it working in the S7 and Edge CSC.
4. The following APK's I feel are related to Wifi Calling are.... If you can help me eliminate some that aren't. They are deodexed, and I have uploaded them, you will need to change the permissions to match the ones in the system folder.
atfwd
ATTVoWifiSPG
com.quicinc.wbcserviceapp
NSDSWebApp
VolteSettings
vsimservice
WAPPushManager
Wispr_ATT
AppSelect_ATT
5. I am unsure if I need to make Buildprop changes or I am missing other system files. I was able to activate wifi calling and turn it on, but it doesn't work.
Click to expand...
Click to collapse
Did you ever get this resolved? So far I can not for the life of me, get WiFi Calling working on my S7 Edge exynos. Basically throws an error stating the activation failed, and never brings up the screen to enter in my emergency contact address like AT&T is supossed to re-direct you to.
The activation fails because AT&T doesn't have an AT&T wifi capable phone on your account which then allows you to activate the wifi. I have two imei's that are linked to AT&T s6 and s7. I can give you the imei. Go to att tech support give them the imei and tell them to update your account to be able to get visual voice mail and wifi calling. After you do this, they will alow you to activate it. However I gave up after a while. If you flash the custom csc, you must do it before your phone boots up after a factory reset and flash a custom rom. I am waiting as I am on Nougat now, so until ATT updates it's apps again.
Psyscope said:
The activation fails because AT&T doesn't have an AT&T wifi capable phone on your account which then allows you to activate the wifi. I have two imei's that are linked to AT&T s6 and s7. I can give you the imei. Go to att tech support give them the imei and tell them to update your account to be able to get visual voice mail and wifi calling. After you do this, they will alow you to activate it. However I gave up after a while. If you flash the custom csc, you must do it before your phone boots up after a factory reset and flash a custom rom. I am waiting as I am on Nougat now, so until ATT updates it's apps again.
Click to expand...
Click to collapse
Thanks, although I'm a bit confused on the steps your outlining here. I assume you're stating that I'll need to somehow modify a ROM (in this case SAC's N7 ROM for S7 Edge Exynos), and inject an IMEI? I'm not entirely sure how to do that to change the IMEI (this would be my first time attempting to do that). Then I would reflash that image, and then re flash the CSC update to AT&T? Maybe I'm not understanding, but my iPhone 6 is on my account and fully capable of wifi calling. In fact we have 2 iPhone 6s on the account. What exactly did you give up on?
Hate to sound like a newb here (although in a way... I am), but can you step me through the process so I can follow your line of thought? Appreciate the help!
So first of all an Android WiFi Calling and IPhone Android WiFi calling are different you will need to tell at&t you have an AT&T branded Android phone that has WiFi calling. This will lead at&t to add the ability to add wifi calling on your account.
Have you rooted your phone and installed a custom rom? If so then you would flash ttkg84's csc package and choose att. Which will flash most if not all the files. I got all the way to confirm my address and enable wifi calling, but it never worked.
Do not insert another phones imei into your phone, you will brick it and will have a expensive paper weight.
I have given up for now and am waiting for a full release of Nougat.
PM my I can give you am imei to give AT&T to enable video calling, visual voice mail and give the ability to activate WiFi Calling, but it's not likely to work. Some things are still missing.
You may never get wifi calling working because at&t uses a slightly different method then everyone else. I think they will standardize with Nougat.
Psyscope said:
You may never get wifi calling working because at&t uses a slightly different method then everyone else. I think they will standardize with Nougat.
Click to expand...
Click to collapse
That's what I thought.... So what about the King of Nougat ROM that's lingering out there currently? I realize Nougat is still beta, but have you tried the beta?
I haven't tried King of Nougat. I am currently using Nougat? Are you on telegram?
Psyscope said:
I haven't tried King of Nougat. I am currently using Nougat? Are you on telegram?
Click to expand...
Click to collapse
So... Interestingly enough. I just got WiFi Calling to work this morning...
Basically, I did the following steps:
1. No SIM Inserted into Galaxy S7 Exynos - SD Card only
2. Reboot to Recovery
3. Wipe
4. Download and Install SAC23's Full n7 ROM located here: http://forum.xda-developers.com/s7-edge/development/rom-n7-rom-port-romcontrol-t3430358 - I did the V8 Debloated version
5. When prompted - Wipe Dalik
6. Insert SIM Card from AT&T iPhone (ensured WiFi Calling was turned OFF on the iPhone prior to removing from iPhone)
7. Reboot first time into N7 ROM
8. Go through the setup and connect to a WiFi location that you know WiFi calling works at.
9. Download a browser (Chrome or whatever) at a minimum
10. Eat a Bacon, Lettuce, and Tomato Sandwich :good:
11. Reboot to Recovery
12. Flash CSC for the N7 located here --> http://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911 - Grab the CSC snapdragon the Exynos zip
13. Reboot
14. Status bar will indicate VoLTE enabled up at top eventually.
15. Try going to the pull down from the top, and clicking WiFi Calling option a couple times.... no dice.
16. Try going to the phone app --> Click Settings --> Note WiFi Calling is off --> Try clicking it on a few times.... you'll get an adroid app stopped working.
17. After sitting on this sceen for a few minutes, note the VoLTE dissapears, and the icons on the phone app screen (The Call Start Button and the Call End button) switch to WiFi magically.... Try making a call with 0 zero cell reception, and indeed, the call is being made through WiFI on AT&T's network.
Now.... I have absolutely zero idea what's going on with the VoLTE icon disappearing.... and the WiFI calling suddenly working. If you reboot the phone, the same thing occurs. It starts in VoLTE.... and then eventually disappears, and eventually after a couple of minutes being connected to a WIFI connection, switches auto-magically to WifFi calling.
I'll take some screenshots.
Usaf-lt-g said:
So... Interestingly enough. I just got WiFi Calling to work this morning...
Basically, I did the following steps:
1. No SIM Inserted into Galaxy S7 Exynos - SD Card only
2. Reboot to Recovery
3. Wipe
4. Download and Install SAC23's Full n7 ROM located here: http://forum.xda-developers.com/s7-edge/development/rom-n7-rom-port-romcontrol-t3430358 - I did the V8 Debloated version
5. When prompted - Wipe Dalik
6. Insert SIM Card from AT&T iPhone (ensured WiFi Calling was turned OFF on the iPhone prior to removing from iPhone)
7. Reboot first time into N7 ROM
8. Go through the setup and connect to a WiFi location that you know WiFi calling works at.
9. Download a browser (Chrome or whatever) at a minimum
10. Eat a Bacon, Lettuce, and Tomato Sandwich :good:
11. Reboot to Recovery
12. Flash CSC for the N7 located here --> http://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911 - Grab the CSC snapdragon the Exynos zip
13. Reboot
14. Status bar will indicate VoLTE enabled up at top eventually.
15. Try going to the pull down from the top, and clicking WiFi Calling option a couple times.... no dice.
16. Try going to the phone app --> Click Settings --> Note WiFi Calling is off --> Try clicking it on a few times.... you'll get an adroid app stopped working.
17. After sitting on this sceen for a few minutes, note the VoLTE dissapears, and the icons on the phone app screen (The Call Start Button and the Call End button) switch to WiFi magically.... Try making a call with 0 zero cell reception, and indeed, the call is being made through WiFI on AT&T's network.
Now.... I have absolutely zero idea what's going on with the VoLTE icon disappearing.... and the WiFI calling suddenly working. If you reboot the phone, the same thing occurs. It starts in VoLTE.... and then eventually disappears, and eventually after a couple of minutes being connected to a WIFI connection, switches auto-magically to WifFi calling.
I'll take some screenshots.
Click to expand...
Click to collapse
Followed the method above using Superman 1.16 and CSC selector 1.86.
Haven't been able to test wifi calling since I haven't found an area with wifi and no cell reception, but so far everything looks like it's working.
Important to note that the AT&T account probably does need to be provisioned for a G935A rather than G935F, which is done by reporting a G935A IMEI to AT&T (and not changing it on the device itself) as mentioned previously.
aramisathei said:
Followed the method above using Superman 1.16 and CSC selector 1.86.
Haven't been able to test wifi calling since I haven't found an area with wifi and no cell reception, but so far everything looks like it's working.
Important to note that the AT&T account probably does need to be provisioned for a G935A rather than G935F, which is done by reporting a G935A IMEI to AT&T (and not changing it on the device itself) as mentioned previously.
Click to expand...
Click to collapse
Hmmm, gotcha.... but if you report a G935A they typically want you to power off and power on the phone to check the provisioning while on the phone with them. And what happens if someone calls in and then tries to re-provision the same IMEI on another account? What happens to my SIM in my G935FD? Thanks!
Usaf-lt-g said:
Hmmm, gotcha.... but if you report a G935A they typically want you to power off and power on the phone to check the provisioning while on the phone with them. And what happens if someone calls in and then tries to re-provision the same IMEI on another account? What happens to my SIM in my G935FD? Thanks!
Click to expand...
Click to collapse
Far as I can tell they don't check IMEIs against different accounts.
I can't say for sure, but I haven't had an issue as my phone has a different IMEI (or IMEIs--G935FD) than the one listed on my account (which reads as a G935A).
In short, asking AT&T to change the IMEI on the account hasn't affected or changed the IMEIs on my phone, or caused any problems.
As far as provisioning, I told them I was on the phone, so they called me back a few minutes later and didn't report any issues or discrepancies to me.
It'd be just as easy to tell the rep the phone isn't available though, so just ask them to change the IMEI and you can call them back later if there are issues if that's a concern.
Looks like great news. I was happy I was able to activate my 935F via AT&T (I gave them the actual IMEI and they activated it). I'm on Superman ROM and flashed ATT CSC. I get visual voicemail and the WiFi calling button, but it doesn't actually work. I'll see if I can get a valid 935A IMEI and ask them to activate again. Hopefully that will do the trick. I get a horrible signal at home, and the 4G/LTE icon is constantly flickering on and off... AT&T Video call option shows up in settings, but won't turn on... no wifi calling setting in the settings menu, just the quick settings button.
Any guidance appreciated!
mike
aramisathei said:
Far as I can tell they don't check IMEIs against different accounts.
I can't say for sure, but I haven't had an issue as my phone has a different IMEI (or IMEIs--G935FD) than the one listed on my account (which reads as a G935A).
In short, asking AT&T to change the IMEI on the account hasn't affected or changed the IMEIs on my phone, or caused any problems.
As far as provisioning, I told them I was on the phone, so they called me back a few minutes later and didn't report any issues or discrepancies to me.
It'd be just as easy to tell the rep the phone isn't available though, so just ask them to change the IMEI and you can call them back later if there are issues if that's a concern.
Click to expand...
Click to collapse
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
BLUF:
If your Verizon account does NOT have HD Voice enabled and the essential phone has "Enhanced 4G LTE Mode" enabled (which is a default setting) you may not be able to make/receive phone calls.
I had an older phone running a lineage fork that did NOT support HD Voice. For whatever reason that also means it isn't enabled on my Verizon account. It doesn't cost anything extra and isn't plan specific but until you enable on a phone (says VZW Tech) the setting stays off.
When I put my SIM into the new Essential phone I could make calls but it would NOT find a new tower. IF i was driving any distance I had to reboot the phone completely to get data or make calls.
As of a few days ago my data was always working (LTE+) but suddenly I could not make or receive any calls. Again, texting, internet, etc. was fine. (yes wifi was off to test this =)
I was on with VZW support trying to fix this when my essential trouble ticket was answered with:
Given that you are getting the LTE+ icon already, can you try this step and see if it helps:
Go to Settings -> More -> Cellular Networks
Disable "Enhanced 4G LTE Mode"
Make a phone call
Return to the Settings menu and re-enable Enhanced 4G LTE Mode
Click to expand...
Click to collapse
VZW said give it a try lets see. With it "off" I could suddenly make calls. With it back on I couldn't again.
VZW said I bet that's what we call "HD Voice" and I see its not enabled on your phone. He enabled it. I rebooted. Everything works again with that setting on or off.
I emailed this back to essential just to let them know what I did with VZW and got reply:
My understanding was "HD voice" was enabled on all smartphone accounts with Verizon, but I will add that as a step to check in the future.
Click to expand...
Click to collapse
I've been troubleshooting this with VZW and Essential for a while so very happy to find fix. I also went out and got a brand new SIM but that also didn't help. Both new and old sim worked in old phone fine but in essential no luck.
I had at first though unlocking bootloader / rooting had done something . I wiped and reflashed this thing 4 times yesterday trying different things to no avail.
I know some other Verizon uses were having weird issues so wanted to share.
I'll prolly never get so lucky with tech support synergy again in my life... but at least this one time they were quickly helpful.
MODs: If this should be in "guides" instead please move or I can repost
-dt
@DHO
Sent from my PH-1 using Tapatalk
Funny.. i just enabled hd voice before switching to this phone.... Glad i did
Sent from my PH-1 using Tapatalk
rignfool said:
@DHO
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tag, but unfortunately that didn't do it
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.
I have enabled Wifi Calling on my PH-1 and I know for a fact that my carrier supports it. It works fine too, but it's set to "Mobile Preferred". I chose this setting because my Wifi isn't too reliable. However, whenever I call, it uses Wifi even though I am getting LTE+? Is there any way to fix this?
Does anyone have any idea? I have looked all over the internet but have not found any solution? Could it possibly be my carrier?
When I try to enable wifi calling, my launcher crashes. So you are one step ahead of me
Sent from my PH-1 using Tapatalk
yqazi27 said:
I have enabled Wifi Calling on my PH-1 and I know for a fact that my carrier supports it. It works fine too, but it's set to "Mobile Preferred". I chose this setting because my Wifi isn't too reliable. However, whenever I call, it uses Wifi even though I am getting LTE+? Is there any way to fix this?
Click to expand...
Click to collapse
Is your phone a Sprint Variant?
I have a Sprint variant and wifi calling is working perfectly fine for me, I am rooted as well and also using Nova
mexicandroid said:
Is your phone a Sprint Variant?
Click to expand...
Click to collapse
I'm not sure. I have seen 3 Sprint system apps though under "Apps and Notifications", but I don't know if that counts. I got it straight from Amazon, if that helps.
yellk20 said:
I have a Sprint variant and wifi calling is working perfectly fine for me, I am rooted as well and also using Nova
Click to expand...
Click to collapse
yqazi27 said:
I'm not sure. I have seen 3 Sprint system apps though under "Apps and Notifications", but I don't know if that counts. I got it straight from Amazon, if that helps.
Click to expand...
Click to collapse
I finally got it working by installing the Open Market Oreo firmware, setting up WiFi calling them updating to Pie firmware
mexicandroid said:
I finally got it working by installing the Open Market Oreo firmware, setting up WiFi calling them updating to Pie firmware
Click to expand...
Click to collapse
Is there any way to do this without rooting or unlocking the bootloader? I want to preserve my warranty for as long as possible.
yqazi27 said:
Is there any way to do this without rooting or unlocking the bootloader? I want to preserve my warranty for as long as possible.
Click to expand...
Click to collapse
Not that I know of. I don't think they would look at your WiFi calling settings if sent out for repairs. Once you install Oreo open market firmware just relock the bootloader, setup your phone including TMobile WiFi calling settings. Once you update to Pie they shouldn't be able to tell anything because all different variants use the same firmware and your bootloader will be locked encase you send your phone out for repairs.
The other option is to use Google Voice. WiFi calling works great on it.
spotmark said:
The other option is to use Google Voice. WiFi calling works great on it.
Click to expand...
Click to collapse
But does it use your carrier phone number or are talking about the Google appointed number?
mexicandroid said:
But does it use your carrier phone number or are talking about the Google appointed number?
Click to expand...
Click to collapse
You do have to use your GV number. In my case it's irrelevant because I ported my number over to GV some time ago.
spotmark said:
You do have to use your GV number. In my case it's irrelevant because I ported my number over to GV some time ago.
Click to expand...
Click to collapse
So your carrier number and Google number are the same?
mexicandroid said:
So your carrier number and Google number are the same?
Click to expand...
Click to collapse
No, your carrier number will change. The port to GV takes approximately 24 hours. So you have to deal with a GV assigned number for a day. After that though you have your regular old number. I barely even know my new Verizon number as I don't give it to anybody. I figure this way, I'll never have to worry about WiFi calling or who my carrier is again.
spotmark said:
No, your carrier number will change. The port to GV takes approximately 24 hours. So you have to deal with a GV assigned number for a day. After that though you have your regular old number. I barely even know my new Verizon number as I don't give it to anybody. I figure this way, I'll never have to worry about WiFi calling or who my carrier is again.
Click to expand...
Click to collapse
I like having a different number for when I do mechanic work, don't want to get calls for every little thing at different times of the night, specially when it's unrelated to what I fixed lol
I have the same problem. Set my wifi calling to Mobile preferred but sometimes my calls use wifi calling even when I have cellular reception. Please let me know when you find a solution.
and I think it's funny that nobody addressed your original issue.
spotmark said:
No, your carrier number will change. The port to GV takes approximately 24 hours. So you have to deal with a GV assigned number for a day. After that though you have your regular old number. I barely even know my new Verizon number as I don't give it to anybody. I figure this way, I'll never have to worry about WiFi calling or who my carrier is again.
Click to expand...
Click to collapse
I also use this same setup and it works great.
coolmaster121 said:
When I try to enable wifi calling, my launcher crashes. So you are one step ahead of me
Click to expand...
Click to collapse
I have the same issue. It was working fine on Oreo. I tried flash.all fastboot using the stock firmware without success. Let me know if you have a solution. Ty
Edit: I got it fixed by flashing flashall back to stock Oreo 8.1 open market from Essential website then let it updated OTA to Pie and my WiFi calling still working fine.
Updated 10/22
My WiFi stopped working again after I turned it off but I can't turn it back on just like before. Any time I tried to turn it on the phone app forced close.
Considering thanks to T-Mobile's wonderful coverage (says I have good signal strength, but it's not) I have Wi-Fi calling enabled all the time and it works well on the 5Ghz ac side of the router...not so well on the 2.4Ghz b/g which is fine. Again something carrier specific. I went to Pie and kept the WiFi calling running.
Caltinpla said:
I have the same issue. It was working fine on Oreo. I tried flash.all fastboot using the stock firmware without success. Let me know if you have a solution. Ty
Edit: I got it fixed by flashing flashall back to stock Oreo 8.1 open market from Essential website then let it updated OTA to Pie and my WiFi calling still working fine.
Updated 10/22
My WiFi stopped working again after I turned it off but I can't turn it back on just like before. Any time I tried to turn it on the phone app forced close.
Click to expand...
Click to collapse
Updated 11/5
Surprisingly, my WiFi calling is now working after updated my phone to today's November security update.