Related
My rooted Nexus 6 and my sons stock Nexus 6 are having a lot of trouble connecting to LTE on Tmobile. I have to go to APNs, reset to default and reboot every hour or so. I did no changes to my phone.
Apparently, this is happening on other networks too.
Can anyone shed light on this? Some back door google update.
tMobile says no changes on their end. Also, other carriers are having this issue, ONLY Nexus 6.
PS - apparently , this has happened before too
http://www.idigitaltimes.com/nexus-6-problems-how-fix-mobile-data-connection-failure-issue-440151
flash a different radio/modem.
Same here. Just spoke to T-MOBILE and rep said it is an issue with a lot Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Edit: change all to a lot
wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
I got the same answer.
I did flash the 5.32 and 5.34 modems. No dice.
Then I tried Developer preview 5.39. It's been working for 15 minutes, which is a long time since the issue cropped up.
What a pain!
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
JimSmith94 said:
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
Click to expand...
Click to collapse
That is probably the same issue. I can receive texts, but can't send without a reboot.
So far.. the 5.39 developer modem has kept connection for an hour. Which is good considering how intermittent it was.
What really blows is that my phone and service was perfect until this event.
Even in the mountains of the Philippines last year, my phone worked perfect.
You may try dp5 my WiFi and Mobil got a lot better, but I'm not on t mobil. Flashing only the radio is maybe not enough, if you are on stock anyway you have nothing to loose
Check out Reddit for the growing thread on this issue. Happening with Nexus 6 users on different carriers around the world. Some GPS connected apps like Pokemon Go & Lyft will bork LTE connectivity. Probably a Google play services issue. Will be using my OnePlus one today just in case.
tmicrd68 said:
Check out Reddit for the growing thread on this issue. Happening with Nexus 6 users on different carriers around the world. Some GPS connected apps like Pokemon Go & Lyft will bork LTE connectivity. Probably a Google play services issue. Will be using my OnePlus one today just in case.
Click to expand...
Click to collapse
Interesting.. I hit the speedtest app right after a reboot to check, and it immediately borked my connection several times in a row. I like your theory..
wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
its NOT an issue with all n6 users on tmobile. i have a nexus 6, since nov 2014, and have never ever had that issue on tmobile. been on tmobile since the early 2000's..
Jeff_in_LA said:
My rooted Nexus 6 and my sons stock Nexus 6 are having a lot of trouble connecting to LTE on Tmobile. I have to go to APNs, reset to default and reboot every hour or so. I did no changes to my phone.
Apparently, this is happening on other networks too.
Can anyone shed light on this? Some back door google update.
tMobile says no changes on their end. Also, other carriers are having this issue, ONLY Nexus 6.
PS - apparently , this has happened before too
http://www.idigitaltimes.com/nexus-6-problems-how-fix-mobile-data-connection-failure-issue-440151
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
Jeff_in_LA said:
I got the same answer.
I did flash the 5.32 and 5.34 modems. No dice.
Then I tried Developer preview 5.39. It's been working for 15 minutes, which is a long time since the issue cropped up.
What a pain!
Click to expand...
Click to collapse
JimSmith94 said:
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
Click to expand...
Click to collapse
You guys have a lot of company... > http://www.androidpolice.com/2016/08/04/some-nexus-6-owners-report-data-outages-on-t-mobile/
I'm running stock N6, not rooted; bootloader locked; on T-Mo. While on WiFi, with WiFi calling enabled, I would get out of range of WiFi and cel data would not return without full reboot. If I disable WiFi calling before leaving WiFi service, cel data flipped as normal. I tested again with manual WiFi disable and if WiFi calling was on before the cut out, cel data never flipped on.
[Edit] I did notice though that when it does flip like it's supposed to, I'm connected at 3G. LTE doesn't kick on.
simms22 said:
its NOT an issue with all n6 users on tmobile. i have a nexus 6, since nov 2014, and have never ever had that issue on tmobile. been on tmobile since the early 2000's..
Click to expand...
Click to collapse
Stated what T-Mobile told me.
Ok, I did flash the beta radio 5.39.
It might be coincidence, but my phone has a solid connection for three hours now.
Hopefully they fixed it on their end.
I am not seeing this on my N6. Still on 5.1.1 LVY48H.
toastgodsupreme said:
I am not seeing this on my N6. Still on 5.1.1 LVY48H.
Click to expand...
Click to collapse
what radio can work on 5.1
Cause i have flyme rom, but have calls issue, ian not receiving any call. The other end saids it rings but my phone does not ring at all on calls.
It seems to be affecting some people, but not others. It also doesn't seem to be related to ROM, carrier, kernel, or radio versions. There are people all over the world on different carriers having the problem.
The symptoms I see are that I can't connect to any type of cellular data. Voice and SMS seem to work though. WiFi data works fine. GPS use seems to make it more likely to fail. Speedtest.net, Pokemon Go, Ingress, and Google Maps have been used to reproduce it.
The only thing I've found that seems to help is to freeze "Google Connectivity Services" using Titanium Backup. You might also try uninstalling updates, though it will just re-install. If it is related to that, it would make sense as the rollout of updates via Play Store are staged, so people would get the update at different times. I froze it about 4 hours ago and data has been solid with GPS use, LTE and HSPA tested. I also tested switching between WiFi and Cellular without issues on Tmobile-US. That's the only SIM I have, so I can't test other services. I couldn't seem to get a data connection for more than a few minutes before, so it's a huge improvement in my case.
ttabbal said:
It seems to be affecting some people, but not others. It also doesn't seem to be related to ROM, carrier, kernel, or radio versions. There are people all over the world on different carriers having the problem.
The symptoms I see are that I can't connect to any type of cellular data. Voice and SMS seem to work though. WiFi data works fine. GPS use seems to make it more likely to fail. Speedtest.net, Pokemon Go, Ingress, and Google Maps have been used to reproduce it.
The only thing I've found that seems to help is to freeze "Google Connectivity Services" using Titanium Backup. You might also try uninstalling updates, though it will just re-install. If it is related to that, it would make sense as the rollout of updates via Play Store are staged, so people would get the update at different times. I froze it about 4 hours ago and data has been solid with GPS use, LTE and HSPA tested. I also tested switching between WiFi and Cellular without issues on Tmobile-US. That's the only SIM I have, so I can't test other services. I couldn't seem to get a data connection for more than a few minutes before, so it's a huge improvement in my case.
Click to expand...
Click to collapse
T-Mobile acknowledges the issue. The one universal is that it's with the N6, not with other phones. There are a bunch of carriers around the world that are having the problem.
When mine breaks, SMS fails. The only mobile connectivity available to me is phone calls.
The Reddit thread mentioned above has people saying that disabling Location Services works. Far from ideal over time, but if it's true, it's something. I tried that. We'll see how it goes. Freezing Google Connectivity Services is nice, if it works without introducing other problems, because it would allow us to keep using whatever connectivity we like without data breaking.
I had a Bluetooth connectivity problem a year or more ago that surfaced literally out of nowhere and on every device I tested, a little more than ten of them. This was independent of ROM, root status, device, anything. The feature in question worked on every Android device we had tried one day (and for more than a year prior) and failed on every one the next. Sounds crazy, but it's what happened. Google barely paid attention to my bug reports and ran me in circles when they did. Never got fixed.
I trust this matter will.
Both my nexus6s are doing this with heavy GPS aps, data will shut down.
Sent from my Nexus 6 using XDA-Developers mobile app
I've had GCS frozen for a long time, running 5.39 radio & it happened to me. There is definitely something occurring substantially with our devices/network be it software or hardware based. Apparently T-Mobile & Google are working on it but the fix might not come until next week. I'll probably install latest N preview when I get home.
Hi All, I'm trying to make my T-Mobile Note 9 work on AT&T. Using odin I put on the latest ATT version on my phone that I could find -- N960USQU1ARG6. It boots and works fine, but it shows Android 8.1, I don't get wifi calling or there's no place to turn on VOLTE, and when I say update software it says "software up to date." So, I'm assuming that ATT still doesn't think this is their phone.
Any ideas on how to fix this?
Thanks!
Nasty64 said:
Hi All, I'm trying to make my T-Mobile Note 9 work on AT&T. Using odin I put on the latest ATT version on my phone that I could find -- N960USQU1ARG6. It boots and works fine, but it shows Android 8.1, I don't get wifi calling or there's no place to turn on VOLTE, and when I say update software it says "software up to date." So, I'm assuming that ATT still doesn't think this is their phone.
Any ideas on how to fix this?
Thanks!
Click to expand...
Click to collapse
Att has Pie firmware for the Note 9. Just do a search for the newest Pue update and flash it using Odin.
Jammol said:
Att has Pie firmware for the Note 9. Just do a search for the newest Pue update and flash it using Odin.
Click to expand...
Click to collapse
Thanks for the response. That will fix the Wifi calling and VoLTE too?
Nasty64 said:
Thanks for the response. That will fix the Wifi calling and VoLTE too?
Click to expand...
Click to collapse
That I do not know for sure. It doesn't hurt to try though.
Jammol said:
That I do not know for sure. It doesn't hurt to try though.
Click to expand...
Click to collapse
Well, it might. I'd really like to understand what's wrong with it before I flash more.
Nasty64 said:
Well, it might. I'd really like to understand what's wrong with it before I flash more.
Click to expand...
Click to collapse
Well the first thing you could do is do a factory reset, or verify with At&t if it's a feature on your account. Not sure how theirs is setup compared to T-Mobile's Wi-Fi calling. It won't hurt to flash unless you've got stuff you need to backup and have no way to do so.
I don't think anything is wrong with your device. All of the N960U devices are the exact same. The only difference is the software. You don't even need to flash a different firmware for it to put the carrier bloat on the device based on the sim card inserted. It's already included in the Software package on the device, just dormant.
I can't see AT&T Mobility (or any carrier, really) willingly remaining in the trailing position vs. the UnCarrier (who has offered Wi-Fi Calling as a feature (even to their MVNO customers) for over a year - yes, I have had it that long personally) - the only time I don't use it is due to support of the *router* being iffy (some residential routers have issues with Voice over Wi-Fi; the same applies to some business routers).
I went to ATT as well and it took some time for me to see the update to 9. Not sure, when I was with T-Mobile it always showed updates right away. For ATT, I was able to find the ARJA firmware with a CSA7 update that expedited the process. It also took around a day for wifi calling to show up. ATT is just slow to enable things perhaps?
I recently flashed Lineage OS 16 onto my Nexus 6 (Shamu) installed Magiskv19 successfully and I have also flashed the latest radio.img (radio-shamu-d4.01-9625-05.51+fsg-9625-02.118) and everything seems to work perfectly fine until I attempt to make a call. I receive an error saying "Mobile Network Unavailable" I have attempted rebooting my phone and also wiping the device from TWRP. I cannot send/receive texts. I have also flashed a few different radio.img files to see if they would work but they have all ended with the same result. My mobile data and hotspot work perfectly fine so I'm sure that it isn't a SIM issue
I see that the Radio version you posted and the Radio version posted under Lineage OS 'Important Info' section doesn't match.
Please double check the descriptions clearly before flashing.
Edit: If you are a Verizon user. Then its the correct one.
But there is already some issues with Calls / Messages with Verizon users and Lineage 16. You can check out the posts
Agree with @Donz7733.
It is probably not the radio, just stick with the newest .51.
But our Pie-roms don't support VoLTE, and that means that phone calls will only work if you have 2G or 3G coverage. Some phone companies are closing the old networks and moving to only 4G.
Donz7733 said:
I see that the Radio version you posted and the Radio version posted under Lineage OS 'Important Info' section doesn't match.
Please double check the descriptions clearly before flashing.
Edit: If you are a Verizon user. Then its the correct one.
But there is already some issues with Calls / Messages with Verizon users and Lineage 16. You can check out the posts
Click to expand...
Click to collapse
I am a Verizon user. I made sure I flashed the correct one
runekock said:
Agree with @Donz7733.
It is probably not the radio, just stick with the newest .51.
But our Pie-roms don't support VoLTE, and that means that phone calls will only work if you have 2G or 3G coverage. Some phone companies are closing the old networks and moving to only 4G.
Click to expand...
Click to collapse
Will there be a point it time when VoLTE is supported?
Noah Duley said:
Will there be a point it time when VoLTE is supported?
Click to expand...
Click to collapse
npjohnson, who is one of the big guys in LineageOS, wrote on Reddit:
"IMS (VoLTE/VoWi-Fi) can't work on Pie ever on platforms before 8996." (8996 refers to the Qualcomm 820 chip, which is ~2 years newer than ours).
So that's a very probable no.
runekock said:
npjohnson, who is one of the big guys in LineageOS, wrote on Reddit:
"IMS (VoLTE/VoWi-Fi) can't work on Pie ever on platforms before 8996." (8996 refers to the Qualcomm 820 chip, which is ~2 years newer than ours).
So that's a very probable no.
Click to expand...
Click to collapse
Okay. Looks like I'm switching back to 15.1
Hello All,
I posted this in Samsung Community, but unfortunately none was able to help. I am hoping XDA members could help fix this issue.
I am facing a strange problem with my S21 Ultra Unlocked which was directly bought from Samsung. I had enrolled into OneUI 4.0 beta when I was in the US. I was using Sprint connection then.
I had to travel back to my home country (India) and I am using an Airtel sim card (LTE) here. Now, the strange problem is that LTE (data) works here fine. But, VoLTE is not working. The network changes to 2G for phone calls. I am assuming that the auto-switching bands which was introduced in OneUI 4.0 is causing the problem.
Using Smart Switch PC, I rolled back to One UI 3.1. VoLTE and WiFi calling started to work again. But, soon after I got update notification for One UI 4 beta. To confirm that it is indeed an issue with One UI 4, I installed it again. And as expected, I am not getting VoLTE or WiFI calling again.
Since I changed from Sprint to Airtel, I am not able to withdraw from the Beta program as well. I am getting the error "One UI beta features aren't available because your service provider has changed".
Also, I am not sure what the final One UI 4 will offer. For the first time in my life, I am seeing an Android upgrade causing my phone to not able to connect to VoLTE.
I am also attaching the screenshots of Phone Information. As you can see, in OneUI 3.1, VoLTE and WiFi calling are provisioned. But in OneUI 4, both are not available. I am assuming the issue is because IMS is not registered. But, I am not able to find how this can be fixed.
Thanks in advance for your help.
Thanks,
APS
#volte #samsung #s21ultra #oneui #oneui4 #imsservice #ims #airtel #oneuibeta
A quick update - I updated to final version One UI 4 and the issue is still there. I am still not able to get VoLTE or WiFi calling in India.
I am having similar issue. Were you able to figure out anything?
dp1989 said:
I am having similar issue. Were you able to figure out anything?
Click to expand...
Click to collapse
No. I have started a new thread in Samsung US Community. Let's see if it reaches the right team who needs to fix this issue.
Since the issue was previously in the Beta version, I didn't get much support. Now, I can see more people facing the same issue since OneUI 4 final version is out.
Can you please provide Samsung members thread link here (or subject line which will help me find it).. I will reply with same issue
dp1989 said:
Can you please provide Samsung members thread link here (or subject line which will help me find it).. I will reply with same issue
Click to expand...
Click to collapse
Try this "DON'T BUY S21 Series Phones if you want use it outside US".
aps99 said:
Try this "DON'T BUY S21 Series Phones if you want use it outside US".
Click to expand...
Click to collapse
I searched Samsung members app and didn't find any thread like that. May be if you can post a link.
dp1989 said:
I searched Samsung members app and didn't find any thread like that. May be if you can post a link.
Click to expand...
Click to collapse
It's in the US community. Did you search there?
Yes, I searched in US Community.
dp1989 said:
Yes, I searched in US Community.
Click to expand...
Click to collapse
Not sure if URL can be posted here. Let me try anyways.
Samsung account
us.community.samsung.com
Yes. I've noticed this since the beta started, was hoping it would be fixed by the time stable is released, but looks like it isn't.
VoLTE/VoWiFi worked fine in Qatar with One UI 3.1 (US unlocked model) but is unable to activate on One UI 4.
It's a shame, but they probably won't fix it since it still works alright with US sims. Maybe it will be fixed in One UI 5 accidentally next year the same way it broke now, but don't hold your breath.
I would once again rollback to One UI 3.1 and wait for a stable Android 12 One UI 4.0 however it may never work with that device in your region. I won't be updating until they release a better version, still too many bugs. Your best option is sell it and buy your Service Provider's device, that's a permanent fix.
varcor said:
I would once again rollback to One UI 3.1 and wait for a stable Android 12 One UI 4.0 however it may never work with that device in your region. I won't be updating until they release a better version, still too many bugs. Your best option is sell it and buy your Service Provider's device, that's a permanent fix.
Click to expand...
Click to collapse
I am on stable One UI 4.0 now. Still it doesn't work.
I cannot sell a device that has such an issue now that I am in India. I will probably sell it once I am back in US if Samsung doesn't fix this issue before then.
Go to settings -->general> reset ----> reset network settings
And reboot after
Volte shou´d work again
Hey i was having this same problem, but seems to have disappeared since I installed SM-G998U rom. I didn't install Userdata and seems I didn't get any bloatware plus activation is still on. You can try.
SOGKush420 said:
Go to settings -->general> reset ----> reset network settings
And reboot after
Volte shou´d work again
Click to expand...
Click to collapse
That won't work, and is completely irrelevant to the issue at hand. This only applies to the unlocked US model (U1) - the OneUI 4 update misconfigures VoLTE for international SIMs.
U will work, but the branded firmware shouldn't be required, U1 is currently broken.
lui0703 said:
Hey i was having this same problem, but seems to have disappeared since I installed SM-G998U rom. I didn't install Userdata and seems I didn't get any bloatware plus activation is still on. You can try.
Click to expand...
Click to collapse
Did you lose the data? I already factory reset my phone trying to fix this issue, rolling back etc.
aps99 said:
Did you lose the data? I already factory reset my phone trying to fix this issue, rolling back etc.
Click to expand...
Click to collapse
I did a full backup before. And just restored the data via Smart Switch after.
lui0703 said:
I did a full backup before. And just restored the data via Smart Switch after.
Click to expand...
Click to collapse
Just to confirm. Are you having a US phone which is being used outside US? What is your current carrier?
SOGKush420 said:
Go to settings -->general> reset ----> reset network settings
And reboot after
Volte shou´d work again
Click to expand...
Click to collapse
Will you please elaborate the whole procedure how did you installed this rom roll back to one UI 3.1 safely..
I have USA unlocked variant of S21 ultra and i am on stable One UI 4.0. Facing the issues.
..VOLTE AND WIFI CALLING FEATURE NOT WORKING ..
YOUR HELP WOULD BE HIGHLY APPRECIATED
So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.
robertkjr3d said:
So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.
Click to expand...
Click to collapse
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.
robertkjr3d said:
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.
Click to expand...
Click to collapse
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!
Agreed, I didn't know such a thing was possible, but I'd love to hear more about this!
skrapmetal said:
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!
Click to expand...
Click to collapse
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.
KennyG123 said:
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.
Click to expand...
Click to collapse
I appreciate you getting back to me. Unfortunately I am still on android 11 with a custom ROM and also this is a global phone so that app didnt work for me. I dont receive OTA updatez. I'll update to a new ROM and see what happens. Thanks