Related
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.
Hi, I've seen where some users have reported success getting VoLTE to work on the OP 6 on AT&T, but I have not had the same success in the OP 6T. I followed the same steps and enabled it on the phone, which now shows that it should use VoLTE when available. I have also spent many (painful) hours in the phone with AT&T trying to resolve this issue, all without success. Has anyone else been able to get this to work, and confirmed that LTE data is still presented when in a call?
Thanks in advance!
I have the McLaren version and with TMobile and I can confirm that it is using VoLTE see picture below.
"technically" I'm using at&t, but it's a tracfone sim via Straight Talk. I enabled it for both VoLTE & VoWifi, and the LTE one took off but the wifi version did not.
I DID notice the difference in call quality. Much better audio response.
Yeah. I'm on AT&T and I got VoLTE working. I just made a call and did a speed test while on the call. Everything indicated it was still on LTE.
sharksfan7 said:
Yeah. I'm on AT&T and I got VoLTE working. I just made a call and did a speed test while on the call. Everything indicated it was still on LTE.
Click to expand...
Click to collapse
What steps did you perform to make it work?
nictabor said:
What steps did you perform to make it work?
Click to expand...
Click to collapse
I had issues with VoLTE when I first got phone. Read my post from another thread. Basically had to wait for AT&T to get my line provisioned correctly. Don't know exactly what needed to be changed/activated.
sharksfan7 said:
I got my 6T on Friday. Used @crowsnestitsupport's instructions for the *#800# trick to get the VoLTE & WiFi calling settings to show. Popped in my sim. Had LTE data but didn't get VoLTE & couldn't get AT&T's VVM app to activate. Called support, ended up giving them my IMEI and not surprisingly it came up as Unknown Device. Guy basically said until the system can recognize the device there was nothing he could do to get VoLTE & VVM working. However after I got off the phone, I quickly realized I no longer had any mobile data at all. Called back, spoke to another rep, and she tried for an hour to get my data back. She wasn't able to. She had to escalate the issue and said it could take 24 hours or more to resolve. I figured out that if I changed APN from ATT Nextgenphone to ATT Phone I could at least have some mobile data, albeit only 3G. Wasn't until Sunday afternoon that LTE came back online including VoLTE. I don't know what had to change to get it all working. Just glad that it is now. Still no WiFi calling but I don't expect to get that.
Click to expand...
Click to collapse
sharksfan7 said:
I had issues with VoLTE when I first got phone. Read my post from another thread. Basically had to wait for AT&T to get my line provisioned correctly. Don't know exactly what needed to be changed/activated.
Click to expand...
Click to collapse
Thanks. I did all of that, and I've called AT&T, but I still haven't had any luck.
sharksfan7 said:
I had issues with VoLTE when I first got phone. Read my post from another thread. Basically had to wait for AT&T to get my line provisioned correctly. Don't know exactly what needed to be changed/activated.
Click to expand...
Click to collapse
It's well documented that that doesn't work, doesn't change anything. I spent two years with the OP5 and 5t trying to get them to enable VOLTE, in about 12 different ways and it never worked. Either you were on WIFI or just really, really special.
xgerryx said:
It's well documented that that doesn't work, doesn't change anything. I spent two years with the OP5 and 5t trying to get them to enable VOLTE, in about 12 different ways and it never worked. Either you were on WIFI or just really, really special.
Click to expand...
Click to collapse
Yeah, OK. Whatever you say.
@nictabor Disregard everything I said. Gerry says it doesn't work. All the indicators on my phone that show VoLTE working must be wrong.
sharksfan7 said:
Yeah, OK. Whatever you say.
@nictabor Disregard everything I said. Gerry says it doesn't work. All the indicators on my phone that show VoLTE working must be wrong.
Click to expand...
Click to collapse
You can search the bazillion threads on this exact topic that already exist in all of the OP forums if you want. Just telling you my experience and summarizing the other threads. Glad yours works though.
sharksfan7 said:
Yeah, OK. Whatever you say.
@nictabor Disregard everything I said. Gerry says it doesn't work. All the indicators on my phone that show VoLTE working must be wrong.
Click to expand...
Click to collapse
I appreciate the feedback, just wish I could get it working on mine. As much as I hate the experience, I'm thinking it might just be worth going to the AT&T store just to get them to use my SIM in one of their devices just to get VoLTE working on the line (and/or verify it works on one of their with it already activated)
xgerryx said:
It's well documented that that doesn't work, doesn't change anything. I spent two years with the OP5 and 5t trying to get them to enable VOLTE, in about 12 different ways and it never worked. Either you were on WIFI or just really, really special.
Click to expand...
Click to collapse
So, I can now confirm that VoLTE works on the 6T. Basically, the system requires HDVoice to get VoLTE working. The solution? I bought a $25 AT&T Prepaid junk phone and enabled HDVoice and WiFi calling on my SIM. After that, I switched the SIM back in to my 6T and it is now working.
nictabor said:
So, I can now confirm that VoLTE works on the 6T. Basically, the system requires HDVoice to get VoLTE working. The solution? I bought a $25 AT&T Prepaid junk phone and enabled HDVoice and WiFi calling on my SIM. After that, I switched the SIM back in to my 6T and it is now working.
Click to expand...
Click to collapse
Then why didn't you call AT&T to enable both features directly?
Sent from my ONEPLUS 6T using Tapatalk
ma678 said:
Then why didn't you call AT&T to enable both features directly?
Click to expand...
Click to collapse
I did, numerous times. They submitted my IMEI to enable the features, and I was told that everything was set up correctly. Upon their recommendation, I went as far as sending my brand new 6T back and buying another one. It didn't matter how many people I talked to, it didn't work until after I used the junk phone to first get it working on the line.
nictabor said:
I did, numerous times. They submitted my IMEI to enable the features, and I was told that everything was set up correctly. Upon their recommendation, I went as far as sending my brand new 6T back and buying another one. It didn't matter how many people I talked to, it didn't work until after I used the junk phone to first get it working on the line.
Click to expand...
Click to collapse
I can make VoLTE or vowifi calls with my sim on other device, but once I switch to 6T, none of features works.
Sent from my ONEPLUS 6T using Tapatalk
ma678 said:
I can make VoLTE or vowifi calls with my sim on other device, but once I switch to 6T, none of features works.
Click to expand...
Click to collapse
When I first swapped it worked and then stopped. I had to put the SIM back in the AT&T phone and again enabled VoWiFi. I then pulled the battery, turned on the 6T, and inserted the SIM. It's been working on the 6T since.
Sorry to revive an old thread, but has anyone found out exactly what to do to get this working?
VoLTE was working perfectly on my 3T, albeit the only way to make the switches appear was with the VoEnabler module in Magisk.. but once they appeared, all I had to do was turn it on, and VoLTE was up and running. I tried the same thing on this phone after putting my SIM in, directly from the 3T; it worked for a few minutes, then the status bar icon disappeared and calls drop my connection to 3G, then go back to LTE once the call is over.. so clearly it has turned itself can off.
I then put my SIM card into my wife's At&t branded Galaxy s9, and after a few minutes VoLTE was working, using my SIM in her phone. I popped my SIM back into my phone, VoLTE was back working... Except, just as before, after a few minutes it stopped.
One thing I've noticed, while working correctly, under the IMS Service Status menu selection in the *#*#4636#*#* dialer menu -> Phone Information, it shows IMS Registration: Registered. Voice over LTE: available... But once it stops working, it says not registered, and unavailable respectively...
Since there are apparently people who seem to have it working, what am I not doing?
Could it be that the phone I put my SIM card into, is currently in use by someone else; someone else who also is provisioned for VoLTE? But what would be the reason it decided to stop working on my 6T and not my 3T? I used the same procedure to trigger VoLTE working on my 3T, and it never stopped working as it is doing on my 6T.
We work opposite shifts, and I used my few minutes we see each other a day to put my SIM in her phone then back into my 6T, I didn't put it in my 3T, which I will do next time I see her.. just to see if the 3T will hold onto VoLTE; that way I'll know for sure if it's something the 6T is doing differently than my 3T, or if I just got lucky before...
Any input or suggestions are welcome..
Edit:
Called AT&T customer service, put my SIM in the S9 and said I was unable to activate either WiFi calling or HD Voice, yet my wife's SIM in the same phone works.. they said that for some reason, my SIM was apparently attached to a non at&t Galaxy s9, she changed the IMEI associated with my SIM card and it's all good now.
With AT&T, If i enable VoLTE, i did not see the "HD" icon when making call. If i disable VoLTE, i see the the "HD" icon. Why is it backward?
ysfk7 said:
With AT&T, If i enable VoLTE, i did not see the "HD" icon when making call. If i disable VoLTE, i see the the "HD" icon. Why is it backward?
Click to expand...
Click to collapse
Opposite for me... The HD icon only appears when I have VoLTE on, as shown.. perhaps something to do with using 2 SIM cards?
I got volte and vowifi enabled and only problem is that i cant see the volte icon on status bar.
Using the phones on Sprint.
Since three weeks or so, while on LTE, the incoming voice calls are going directly to voice mail.
Sprint looked at it and changed the Network to 3G and now getting a ring for the incoming calls.
Basically, I am forced to run the phones on 3G service.
Need to go to a service center (which is very far for me) to have the phone looked at.
Anyone facing similar issue?
PS: 2 of the 3 PH-1 phones I have, are having the issue.
Tom23824 said:
Using the phones on Sprint.
Since three weeks or so, while on LTE, the incoming voice calls are going directly to voice mail.
Sprint looked at it and changed the Network to 3G and now getting a ring for the incoming calls.
Basically, I am forced to run the phones on 3G service.
Need to go to a service center (which is very far for me) to have the phone looked at.
Anyone facing similar issue?
PS: 2 of the 3 PH-1 phones I have, are having the issue.
Click to expand...
Click to collapse
Google have updated the dialer recently several times, could it be a bug that shows on Sprint, or do you have spam settings on, which I know has caught other people out. Check/play with spam settings in her dialer app.
(other areas I might check (if not dialer or network). I assume all phones were working before correctly, right? Are they different sims or the same sim in different phones? New sims, ie not old one you have cut down hat are old spec. Do lte settings match on different phones?)
Tom23824 said:
Using the phones on Sprint.
Since three weeks or so, while on LTE, the incoming voice calls are going directly to voice mail.
Sprint looked at it and changed the Network to 3G and now getting a ring for the incoming calls.
Basically, I am forced to run the phones on 3G service.
Need to go to a service center (which is very far for me) to have the phone looked at.
Anyone facing similar issue?
PS: 2 of the 3 PH-1 phones I have, are having the issue.
Click to expand...
Click to collapse
Same issue. Did you get it fixed?
I also have this problem on Sprint.
Sometimes restarting the phone fixes the issue, sometimes it doesn't.
Between this and no longer being able to use Google Voice without using a separate number, I think it's time for me to bail on Sprint.
My wife had this issue a bit back. Only happened when the phone was using VoLTE (verified by a debug menu, *#*#4636#*#*, showing both voice/text and data marked as LTE).
Fix was to disable the Enhanced 4G LTE communications option, which forced the phone too fallback to nonVoLTE while still using LTE for data. Again confirmed using the phone information menu which showed voice as 1xRTT and data as LTE.
Hope this help and that we can get a better fix soon.
serenesilence said:
My wife had this issue a bit back. Only happened when the phone was using VoLTE (verified by a debug menu, *#*#4636#*#*, showing both voice/text and data marked as LTE).
Fix was to disable the Enhanced 4G LTE communications option, which forced the phone too fallback to nonVoLTE while still using LTE for data. Again confirmed using the phone information menu which showed voice as 1xRTT and data as LTE.
Hope this help and that we can get a better fix soon.
Click to expand...
Click to collapse
Has this fix worked for anyone?
jhill110 said:
Has this fix worked for anyone?
Click to expand...
Click to collapse
Dude... His post says this fix worked for him... And it has worked for others...
Sent from my PH-1 using Tapatalk
rignfool said:
Dude... His post says this fix worked for him... And it has worked for others...
Click to expand...
Click to collapse
Didn't work for me.
I turned off the advanced and re provisioned everything is good.
You are the type that likes to belittle people.... Thanks for your non help post.
jhill110 said:
Didn't work for me.
I turned off the advanced and re provisioned everything is good.
You are the type that likes to belittle people.... Thanks for your non help post.
Click to expand...
Click to collapse
Any time...
I love sharing my time with ungrateful idiots that can't bother to read or need the red carpet rolled out for them...
Good luck with your device... Hope you drop it in the river
Sent from my PH-1 using Tapatalk
rignfool said:
Any time...
I love sharing my time with ungrateful idiots that can't bother to read or need the red carpet rolled out for them...
Good luck with your device... Hope you drop it in the river
Click to expand...
Click to collapse
Frustrating isn't it.
autosurgeon said:
Frustrating isn't it.
Click to expand...
Click to collapse
Nah...
I just wish him ill and send him on his way...
Maybe he will learn to read... And realize his device is no more valuable than anyone else's...
But probably not...
Google Voice Essential Phone NO Ring Ring Fix
jhill110 said:
Didn't work for me.
I turned off the advanced and re provisioned everything is good.
Click to expand...
Click to collapse
Didn't work for me either but I figured it out... what I had to do is change a setting under Google Voice in Settings under the tab CALLS change to "Use carrier only" and I did have to turn VoLTE off. I left the Preferred network type as LTE. Phone is working well now, with T-mobile and Google Voice I have been testing it all morning.
:highfive:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Any chance it solves LTE problems with stock OS as well?
Renovatio33 said:
Any chance it solves LTE problems with stock OS as well?
Click to expand...
Click to collapse
IDK about what problems your talking about, but it definitely won't as the stock OS already has the necessary ims.apk.
In my case, even after installing this, (I use verizon) it won't even detect the sim no matter what rom I use...
CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
So are you able to receive text messages on LTE now?
Tredah212 said:
So are you able to receive text messages on LTE now?
Click to expand...
Click to collapse
Yes, I'll usually have to reboot and it starts working properly
I'm using Havoc 2.9 on Verizon, and even with this app installed, I'm not receiving incoming texts. Any suggestions on what to do?
Edit: Never mind. After multiple attempts, it finally started working.
Reznor7 said:
I'm using Havoc 2.9 on Verizon, and even with this app installed, I'm not receiving incoming texts. Any suggestions on what to do?
Edit: Never mind. After multiple attempts, it finally started working.
Click to expand...
Click to collapse
Really, you got everything working on GSI on Verizon?? What steps did you use? Is Volte working?
jal3223 said:
Really, you got everything working on GSI on Verizon?? What steps did you use? Is Volte working?
Click to expand...
Click to collapse
Yup. LTE seemed a bit spotty on staying connected though, and it seemed like sometimes texts didn't come through promptly compared to stock. I installed the ims.apk and selected TD-SCDMA/CDMA/UMTS in the Phone info menu (*#*#4636#*#*). Volte worked, but again, the overall stability of the connection didn't feel quite right. Unfortunately, the lack of Bluetooth media ability pushed me back to stock again.
Does anyone have the knowledge to make a Magisk Module making these changes? It would make it much easier to switch between different builds to test.
CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
I tried this with Android Q variants and wasnt able to access Phone Info any more. Is this only intended for Pie based GSIs?
Thanks
DarkestSpawn said:
I tried this with Android Q variants and wasnt able to access Phone Info any more. Is this only intended for Pie based GSIs?
Thanks
Click to expand...
Click to collapse
I have yet to get an Android 10 rom to work on my phone AND my phone is currently out for repairs, so I haven't been able to test it for Android 10.
CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
Quick Question, since you are on tmobile..
Are you able to use WiFi Calling with GSI ROM?
I am thinking of going to GSI Q ROM but need to have WiFi calling working since coverage at my home is weak.
Thanks,
RJR
My carrier just enabled VoLTE for me today and I gave it a try.
While VoLTE works on Havoc 2.9 with this apk, I couldn't properly hang up the phone call and I have to reboot the phone.
By the way, I'm also having the issue of being unable to access the Phone Information menu. Nothing happens after typing *#*#4636#*#* on the dialpad.
EDIT: Turned out I set the default dialer to something else (Emerald Dialer) and the system would refuse to send secret code from non-default dialer for security reasons. However, it appears third party dialers may not be able to handle such codes correctly as when I typed the code on Emerald Dialer, it crashed. I set the system default dealer back to the stock one and now I could enter the Phone Information menu.
However, I'm yet to figure out what might have caused VoLTE to get stuck when hanging up...
Reznor7 said:
Yup. LTE seemed a bit spotty on staying connected though, and it seemed like sometimes texts didn't come through promptly compared to stock. I installed the ims.apk and selected TD-SCDMA/CDMA/UMTS in the Phone info menu (*#*#4636#*#*). Volte worked, but again, the overall stability of the connection didn't feel quite right. Unfortunately, the lack of Bluetooth media ability pushed me back to stock again.
Click to expand...
Click to collapse
I just applied this fix on Havoc OS, and it works! However after about 2 minutes reliably, my phone changes to "No Service, Emergency Calls Only" mode. Verizon totally disappears. It appears IPv4 still passes the ping test, however IPv6 fails(2). I'm not sure how to fix this problem
GalacticGLI said:
I just applied this fix on Havoc OS, and it works! However after about 2 minutes reliably, my phone changes to "No Service, Emergency Calls Only" mode. Verizon totally disappears. It appears IPv4 still passes the ping test, however IPv6 fails(2). I'm not sure how to fix this problem
Click to expand...
Click to collapse
I could never get Verizon to work at all on any Gsi. Have you gotten it to work on 9.0 Gsi roms?
I'm running Havoc (latest Pie version)
For the first 2-3 minutes after boot, I see 'Verizon 4G' as my carrier info. After that, the signal in the status bar changes to have a little x on it, and all branding disappears. It says No Service and Emergency Calls Only.
I'm not sure what I'm doing wrong
rrusek said:
Quick Question, since you are on tmobile..
Are you able to use WiFi Calling with GSI ROM?
I am thinking of going to GSI Q ROM but need to have WiFi calling working since coverage at my home is weak.
Thanks,
RJR
Click to expand...
Click to collapse
You can see if the Tmobile DIGITS app will work on your phone. I think it basically forces WiFi calling. I'm using an Android 10 ROM and DIGITS circumvents the no-texting on 3G issue. You can also set up RCS on Messages if you change your data to 3G, reboot the phone and wait for it to finish setting up. That doesn't exactly fix the SMS issues, but it at least is a band-aid solution, combined with DIGITS will effectively solve SMS issues altogether. And again, I am not sure, but I suspect that DIGITS is WiFi calling the app, but I could be very wrong on that. You can also force WiFi calling using adb, though I don't know if that actually works yet since I have not received or placed calls since manually setting it to on. Will report back.
EDIT: Forcing WiFi calling in ADB seems to have turned it on for good. I have the WiFi calling symbol even though I have no option in Settings.
Straum said:
You can see if the Tmobile DIGITS app will work on your phone. I think it basically forces WiFi calling. I'm using an Android 10 ROM and DIGITS circumvents the no-texting on 3G issue. You can also set up RCS on Messages if you change your data to 3G, reboot the phone and wait for it to finish setting up. That doesn't exactly fix the SMS issues, but it at least is a band-aid solution, combined with DIGITS will effectively solve SMS issues altogether. And again, I am not sure, but I suspect that DIGITS is WiFi calling the app, but I could be very wrong on that. You can also force WiFi calling using adb, though I don't know if that actually works yet since I have not received or placed calls since manually setting it to on. Will report back.
EDIT: Forcing WiFi calling in ADB seems to have turned it on for good. I have the WiFi calling symbol even though I have no option in Settings.
Click to expand...
Click to collapse
Has anyone figured out the sms issue on Q gsis yet? It's the only thing holding me back, and I'd rather avoid the Digits app.
tried to install. installed. did not change anything.
edit: tested also from phone info - no IMS menu and no buttons for enable VoLTE.