Related
After updating to 6.0.1 and having LTE issues I noticed that my preferred network type is set to global. Is that right? I would think it should be on LTE/CDMA.
I am too. I already struggled to keep LTE before, but now, it's intermittent. Mine is set to global, which most VZW Samsung and LG phones come these days. Also i went from having 6 APNs to 2.
collinjm01 said:
I am too. I already struggled to keep LTE before, but now, it's intermittent. Mine is set to global, which most VZW Samsung and LG phones come these days. Also i went from having 6 APNs to 2.
Click to expand...
Click to collapse
I aonly have one APN.. I dont think I have any problems though. I wonder how you get more
collinjm01 said:
I am too. I already struggled to keep LTE before, but now, it's intermittent. Mine is set to global, which most VZW Samsung and LG phones come these days. Also i went from having 6 APNs to 2.
Click to expand...
Click to collapse
shawnten said:
I aonly have one APN.. I dont think I have any problems though. I wonder how you get more
Click to expand...
Click to collapse
1 here too. Not sure about before 6.0.1.
Right now (i got 4g on my nexus 6) i am at 1X. It's weird, ill be sitting here and get 4g on my n6p then it'll drop to 3g, then back to 1X...then if i toggle AP mode, it'll go back to LTE then eventually drop back off to 3g...etc.
Same issue here. Wildly fluctuating LTE signal. -82db one minute -108 db and 3g the next. I upgraded to 6.0.1 this weekend and have had no problem till today. I've had great signal ranging from -72 db to -84db. I checked verizon outages and they seem to be having a lot of trouble today. On the map I'm not in an affected area but I'm close (down state Delaware) and the New York to Washington corridor is showing entire outages. Interesting that Comcast had trouble yesterday and today in the same areas.
Yeah I know there's a giant thread here about it with attempted fixes and such. I'll link to it at the bottom. Was worried for a second my preferred network type was wrong but guess not http://forum.xda-developers.com/showthread.php?t=3267270
Well i decided to take a trip over to Nexus Forums and came up with this. Have not tried it yet.
"*SOLUTION
Just got off the phone with Google and they asked me to try a few things.
>take out your SIM card
>go to settings> backup and Reset
>choose Network settings Reset, and select it.
Then power off the device, power on the device and pop the SIM card back in.
I then powered the device off and on one more time with the SIM in it.. And Bingo!
My 6p is now switching from 3G(H) and LTE on its own without needed to refresh Airplane mode.
Try this and let us know of it works for you."
Quoted from: https://productforums.google.com/forum/#!msg/nexus/GUvYO4wGThA/Fwg1TQtZBAAJ
EDIT: I have not tried this. I haven't had time.
If you try this... let me know how it works out.
thanks.
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 have Verizon and after updating to Android 10 today (official Verizon OTA update), when I check the SIM status it will sometimes say "Sprint". It'll also sometimes say "Sprint" when I swipe down from top and look in upper right hand corner. Has anyone seen this? Any idea why? SIM card came from Verizon when I switched over from Sprint to VzW a number of months ago.
Thanks.
ayoldguy1 said:
Hi, I have Verizon and after updating to Android 10 today (official Verizon OTA update), when I check the SIM status it will sometimes say "Sprint". It'll also sometimes say "Sprint" when I swipe down from top and look in upper right hand corner. Has anyone seen this? Any idea why? SIM card came from Verizon when I switched over from Sprint to VzW a number of months ago.
Thanks.
Click to expand...
Click to collapse
When you switched to Verizon, were you still just accepting OTAs? It kinda sounds like you still getting Sprint OTAs.
I bought a used Sprint phone, then fastboot flashed the Essential image, which prompts for the Essential OTA.
Same. When I look up Mobile network in settings it shows Verizon, but when I look from pulldown notification, it says Sprint. Tried network reset and no change.
ktmom said:
When you switched to Verizon, were you still just accepting OTAs? It kinda sounds like you still getting Sprint OTAs.
I bought a used Sprint phone, then fastboot flashed the Essential image, which prompts for the Essential OTA.
Click to expand...
Click to collapse
I was just accepting OTAs. But the SIM is a Verizon SIM? Also, it seems like I have data and can make calls... how is that possible? I've gotten OTAs before (Android Pie) and didn't have this issue.
dark_isz said:
Same. When I look up Mobile network in settings it shows Verizon, but when I look from pulldown notification, it says Sprint. Tried network reset and no change.
Click to expand...
Click to collapse
Do you feel that you're actually using the Sprint network? I can't see hotspot toggle anymore in Settings, I can't see a way to navigate there.
I'm the same but I feel I'm on Verizon network and not Sprint. APN says Sprint though. As long as I use Verizon Messages app, MMS/SMS work fine though. 4G and calls work fine.
If you (y'all) go to the APN settings (settings -> Network & Internet -> Mobile Network -> Advanced -> Access Point Names), are they Verizon? Have you looked up the Verizon APNs and compared to what you have?
I'm having the same exact issue. Before update, all APNs were Verizon. Post update, they'll be Verizon at first then randomly change to being all of Sprint's... How weird.
Mobile Network says Verizon, APNs say Sprint, SIM status says Sprint, and Sprint's OMADM updates setting appears under about phone as well. For some reason, the phone states its brand as Sprint too, even though the device is unlocked.
jffwarner0 said:
I'm having the same exact issue. Before update, all APNs were Verizon. Post update, they'll be Verizon at first then randomly change to being all of Sprint's... How weird.
Mobile Network says Verizon, APNs say Sprint, SIM status says Sprint, and Sprint's OMADM updates setting appears under about phone as well.
Click to expand...
Click to collapse
When the phone was switched off of Sprint's network into Verizon's, was the firmware switched from the Sprint dedicated releases to the Essential generic release? Basically you'd have to fastboot flashed a factory image downloaded from Essential's developer page.
I'm not saying this definitely fixes the problem, but the Sprint phones have firmware specific to them.
ktmom said:
When the phone was switched off of Sprint's network into Verizon's, was the firmware switched from the Sprint dedicated releases to the Essential generic release? Basically you'd have to fastboot flashed a factory image downloaded from Essential's developer page.
I'm not saying this definitely fixes the problem, but the Sprint phones have firmware specific to them.
Click to expand...
Click to collapse
This one was never on Sprint's network. Maybe mine just got the wrong Android 10 OTA pushed to it then? I'm assuming a factory reset will probably be my only hope then.
jffwarner0 said:
This one was never on Sprint's network. Maybe mine just got the wrong Android 10 OTA pushed to it then? I'm assuming a factory reset will probably be my only hope then.
Click to expand...
Click to collapse
No, I doubt that the wrong releases got pushed. It dawns on me that I haven't been seeing separate images on Essential for the Sprint, and everyone else for at least a year. Maybe they merged the releases and something in the build prop is whacked.
ktmom said:
No, I doubt that the wrong releases got pushed. It dawns on me that I haven't been seeing separate images on Essential for the Sprint, and everyone else for at least a year. Maybe they merged the releases and something in the build prop is whacked.
Click to expand...
Click to collapse
So I guess I'll have to wait for the October OTA. Fun times.
Are you using the latest version too?
jffwarner0 said:
So I guess I'll have to wait for the October OTA. Fun times.
Are you using the latest version too?
Click to expand...
Click to collapse
No [emoji854] it's my daily driver, rooted with a few mods. I typically wait until the release after a major version upgrade to do the upgrade. That gives me time to see if there are problems that will affect my use case.
ktmom said:
No [emoji854] it's my daily driver, rooted with a few mods. I typically wait until the release after a major version upgrade to do the upgrade. That gives me time to see if there are problems that will affect my use case.
Click to expand...
Click to collapse
That's what I typically do too. I saw that this was the second one for 10 put out, so I figured I was all good. Especially since the subreddit had been positive all of yesterday about it. I'm now wishing I could revert back without losing my settings, non-play store apps, and data.
jffwarner0 said:
That's what I typically do too. I saw that this was the second one for 10 put out, so I figured I was all good. Especially since the subreddit had been positive all of yesterday about it. I'm now wishing I could revert back without losing my settings, non-play store apps, and data.
Click to expand...
Click to collapse
It's the first of the "stable" releases. Everything else has been beta releases.
ktmom said:
It's the first of the "stable" releases. Everything else has been beta releases.
Click to expand...
Click to collapse
It is? I could've sworn I had one pop-up before this one and this one was being billed as a "hotfix" for service issues from the first "stable" release. Oh well, guess I get Sprint service speeds for a month.
Also having same issue
Hi, all. I'm so happy I found this thread. I have an Essential that was purchased from Sprint and unlocked immediately in November of 2017. It has worked almost flawlessly since on Verizon (lousy battery life some months and some odd camera stuff going on here and there).
I have always taken the OTA updates and never had an issues. I took the Android 10 update as soon as it showed available in September. A few days later my phone was showing "roaming". I reset it a few times, pulled the SIM, etc. and got it working again but the SIM continued to show Sprint. A few more restarts and it showed Verizon.
This kept happening every few days. A few restarts and it was back on Verizon. I even had the Verizon store put a new SIM in when restarts weren't fixing it.
Now I am stuck in Sprint mode for several weeks and cannot get it back on Verizon.
The issue is you cannot send/receive MMS when in Sprint mode AND I cannot receive voicemails.
I am no longer up for flashing firmware, etc. I got that out of my system years ago and just want phones that work and don't cost a fortune. I'm hoping I can recover this thing without major surgery, because my old Moto G4 is a really bad phone at this stage in its life. I finally switched last week when my wife got mad that I wasn't responding to her MMS messages. First time I plugged the Moto into my car, Android Auto nearly killed it! LOL
Is there a fix for this? I can't live without MMS (or rather, my colleagues and family can't) so I may have to buy a Pixel soon.
Thanks!
mkempton said:
Hi, all. I'm so happy I found this thread. I have an Essential that was purchased from Sprint and unlocked immediately in November of 2017. It has worked almost flawlessly since on Verizon (lousy battery life some months and some odd camera stuff going on here and there).
I have always taken the OTA updates and never had an issues. I took the Android 10 update as soon as it showed available in September. A few days later my phone was showing "roaming". I reset it a few times, pulled the SIM, etc. and got it working again but the SIM continued to show Sprint. A few more restarts and it showed Verizon.
This kept happening every few days. A few restarts and it was back on Verizon. I even had the Verizon store put a new SIM in when restarts weren't fixing it.
Now I am stuck in Sprint mode for several weeks and cannot get it back on Verizon.
The issue is you cannot send/receive MMS when in Sprint mode AND I cannot receive voicemails.
I am no longer up for flashing firmware, etc. I got that out of my system years ago and just want phones that work and don't cost a fortune. I'm hoping I can recover this thing without major surgery, because my old Moto G4 is a really bad phone at this stage in its life. I finally switched last week when my wife got mad that I wasn't responding to her MMS messages. First time I plugged the Moto into my car, Android Auto nearly killed it! LOL
Is there a fix for this? I can't live without MMS (or rather, my colleagues and family can't) so I may have to buy a Pixel soon.
Thanks!
Click to expand...
Click to collapse
Have you looked at the APN that is being used? Settings -> network & internet -> mobile network -> advanced -> all the way down
ktmom said:
Have you looked at the APN that is being used? Settings -> network & internet -> mobile network -> advanced -> all the way down
Click to expand...
Click to collapse
Thanks for the quick reply.
"Mobile Network" in the primary menu shows Verizon, but the APNs look like Sprint names.
OTA
otasn
SPCS Global
cinet.spcs
Sprint
sprint
Sprint MMS
n.ispsn
mkempton said:
Thanks for the quick reply.
"Mobile Network" in the primary menu shows Verizon, but the APNs look like Sprint names.
OTA
otasn
SPCS Global
cinet.spcs
Sprint
sprint
Sprint MMS
n.ispsn
Click to expand...
Click to collapse
Look up the correct APNs for Verizon and create the correct ones. Once they work, delete the sprint ones.
Edit:
I know you said your over the days of flashing, but I think I would sideload the first A10 OTA from Essential's Developer's site. You can do that in stock recovery, just using ADB.
Hopefully that will get you off the Sprint software. It's what I did back when I got a sprint version (used). I always start with the first release of the current version on the device. Often the first major release has specific stuff that doesn't get passed on in future updates. Or, that may just show how old school I am [emoji4]
Run the update checker twice back to back.
Yup got it the other day
Lz3807775t said:
Yup got it the other day
Click to expand...
Click to collapse
I checked in the morning and no dice, then just past midnight it allowed it.
No March patch- already got it on other brand phones.
I got it the other day. It is sooo much better than OOS 12. It's like a whole new phone.
I'm still waiting on my update alert to Android 13. Still sitting on Android 12 at the moment T-Mobile variant
info[]box1 said:
I'm still waiting on my update alert to Android 13. Still sitting on Android 12 at the moment T-Mobile variant
Click to expand...
Click to collapse
Did you check your update , it should be there for you to get
Lz3807775t said:
Did you check your update , it should be there for you to get
Click to expand...
Click to collapse
Lz3807775t said:
Did you check your update , it should be there for you to get
Click to expand...
Click to collapse
I finally Android 13 today update came over night.
I got it last night. It killed my mobile data. Wi-fi works fine but not mobile. I've checked the APN settings, I've reset the network options, I've even done a full factory reset. Nothing works.
Why? I think it's because I carrier unlocked the sim and have been running on Verizon through StraightTalk. I think the update is preventing me from connecting to Verizon and there is nothing I can do about it. I also can't downgrade to Android 12. I'm trying to figure out what to do next. It looks like I may can use a tool to change over to the EU version which will then let me go back to 12 or possibly unlock the bootloader without waiting weeks on OnePlus to send me a code.
the Google Voice redirection still broken under OOS13 any variant
Anyone working on a custom recovery for 13 on T-Mobile OnePlus 8 yet?
Its may 2nd and the android 13 update isn't on my phone. are you all sure you're using T-Mobile?
txnari said:
Its may 2nd and the android 13 update isn't on my phone. are you all sure you're using T-Mobile?
Click to expand...
Click to collapse
I'm on T-Mobile with a Rooted one plus 8 5g on stock Android 13. It was an OTA update a couple weeks ago here in Indianapolis.
Jeremynew98 said:
I'm on T-Mobile with a Rooted one plus 8 5g on stock Android 13. It was an OTA update a couple weeks ago here in Indianapolis.
Click to expand...
Click to collapse
I just restarted my phone and check again, and it finally showed up really weird that it didn't show up till now
txnari said:
I just restarted my phone and check again, and it finally showed up really weird that it didn't show up till now
Click to expand...
Click to collapse
Good deal. I didn't even know there was an Android update coming, I had a notification and figured it was a security update. I installed it and was pleasantly surprised.
axeman71 said:
I got it last night. It killed my mobile data. Wi-fi works fine but not mobile. I've checked the APN settings, I've reset the network options, I've even done a full factory reset. Nothing works.
Why? I think it's because I carrier unlocked the sim and have been running on Verizon through StraightTalk. I think the update is preventing me from connecting to Verizon and there is nothing I can do about it. I also can't downgrade to Android 12. I'm trying to figure out what to do next. It looks like I may can use a tool to change over to the EU version which will then let me go back to 12 or possibly unlock the bootloader without waiting weeks on OnePlus to send me a code.
Click to expand...
Click to collapse
Were you able to resolve this? My device was fine on OOS13.0 but had the same issue on OOS13.1.
Fed up with OnePlus and T-Mobile and their shenanigans.
The sim card would be what connects you to the mobile network for any given carrier. Try pulling it and reinserting it. Maybe after a reboot. See if you have options under sim card, mine are greyed out but I think some carriers have more than one option under sim.
I did finally get it to work. I had to call straight talk and work with the support staff. They changed my apn and did some other behind the scenes changes that got it to work.
urover said:
Were you able to resolve this? My device was fine on OOS13.0 but had the same issue on OOS13.1.
Fed up with OnePlus and T-Mobile and their shenanigans.
Click to expand...
Click to collapse