Related
Last Friday I noticed that I stopped receiving texts on my unlocked DE running stock rooted 4.4.4. Sending texts works fine. This phone has never had any problems with anything since I started using it 18 months or so ago, and out of the blue it stopped receiving texts. I have checked Verizon's side on another phone (moved sim card to old Gnex and texts are received fine) and it is definitely a problem with my phone. I have deleted all texts, wiped caches, tried Safe Mode nothing has fixed it. Seems like some odd radio problem. I have read about the 4.4.4 issues others have had, but as I mentioned, this phone has been fine on 4.4.4 since I set it up.
In any event, I am here looking for some answers or some suggestions of what else to try. I would like to keep the total wipe and restore as a last resort, as this phone is mission critical to me for work, and being too stupid to do regular backups, resetting everything back to the way it is now would be a hardship. I do have a nandroid backup from when I originally set up the phone, and was thinking of trying that. If I wipe everything though, does that wipe the SD card too? I thought a factory reset wipes the SD card, so if so I need to back it up first.
(So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...)
Thanks in advance for anything you guys can offer!
In my case, and others, this problem was solved as indicated in post #25 by qtonic (thanks to you, qtonic!). In my case, VVM was not an issue as I did not use that feature, so I can't vouch for whether or not that problem is solved. No "factory reset" was involved, nor any "upgrade" to Lollipop was necessary, so no worries there. One important note is to backup your texts if you want to restore them after you clear the data. I did that and I am back up and running with all my old texts in place. Hopefully this fix works for everyone experiencing this issue.
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
cnoevl21 said:
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
Click to expand...
Click to collapse
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
I am dealing with the same issue. Don't want to upgrade to lolly or do i want to factory reset. I will stay tuned to this thread and hopefully get a fix.
Sent from my XT1060 using XDA Free mobile app
amajamar said:
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
Click to expand...
Click to collapse
i just wiped cache and dalvik. then went to lollipop. it then dawned on me that i should have tried to wipe kitkat, but when u switch to LP it screws everything up so idk if you can go back to kitkat. i may try to at some point, maybe over the weekend.
right now im just running a debloated stock LP rom and i used xposed to customize.
I just added the following to my OP.
So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...
Can you guys duplicate this?
Any solutions other than factory wipe?
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
I went up several levels of tech support at Verizon and eventually ended up getting the same story. I need a factory reset and then all will be fine. They said it was due to some voicemail interface version not being supported anymore and my phone is trying to use the old one and it's keeping the phone from provisioning and that's why texts stopped working.
I've been putting off applying the Lollipop update because I knew it was going to have undesired consequences, but I went ahead and applied it. Text work again but of course I had to re-root (Developer Edition so no sweat there) and even with root WiFi Tether for Root Users (which had been working great under KitKat) bit the dust and no longer works. Under KitKat I had to use the special version that had some added binaries to make up for pieces that were missing from the kernel and I guess those binaries don't work with the Lollipop kernel.
So I'm using the stock tether app now (with provisioning check disabled) but I hate it. You can't turn on access control lists (to "approve" users), you can't see who's connected, you can't define an inactivity timeout, blah blah blah. It sucks so bad compared to WiFi Tether for Root Users.
Oh yeah, in the process of troubleshooting they removed voicemail from my line and put it back on. So I had to set up my voicemail from scratch and lost a bunch of voicemails I'd been saving for years including one from a friend who's dead now. Not happy.
Eh, at least SMS works again.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
Yes, for me it was last Thursday that it was working as well. So, that being said, I take it a factory wipe is required. A couple of questions for you guys: Since I have a Developer Edition (running Xposed) too, do I have anything to worry about about doing a factory wipe? I am currently on 4.4.4, rooted, do I need to prep anything to do the factory wipe so I don't brick? Can I stay on 4.4.4 and just re-root and reinstall my apps from TiBU? I haven't messed around with anything since setting it up over a year ago, and not really thrilled with starting from scratch...
Anyway, great sleuthing MotoCache1, seems that you got to the bottom of things. At least we can be sure it was not some other app or something causing this.
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
mlucht said:
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
If you're rooted edit your /system/build.prop file, add this line to the end, reboot the phone, and then use the factory hotspot tethering:
Code:
net.tethering.noprovisioning=true
More information here if you want it.
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
ray4jc said:
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
Click to expand...
Click to collapse
That's what they told me as well. They said "take it in to a Verizon store and they will back it up and do a factory reset and then restore your data".
I decided against that and instead opted to use the VZW Software Repair Assistant tool. When you use that there are 2 options - Software Repair Assistant (which is supposed to "repair" your currently installed software) and Software Upgrade Assistant (which is supposed to update your device to the latest available software for it).
I didn't particularly want to go to Lollipop so I chose the "repair" option, chose the phone, and clicked "Repair". And it "repaired" it by upgrading it to Lollipop. Lol. Maybe it's because I had previously told the phone to go ahead and try to apply the Lollipop OTA. The OTA failed to install. Not sure why - possibly due to root and/or other changes to the system partition. I was using stock recovery.
So anyway, I ended up on Lollipop even though that's not really what I wanted to do, and that did fix the problem - though, as previously bemoaned, I can't use WiFi Tether for Root Users anymore and have to use the piece of crap that's built into the OS. I guess I should be grateful that works because I'd be in a pickle if I had to do without tether.
Back to what you posted -- I don't think anybody here has yet posted that the factory reset actually fixed the problem for them. Honestly I don't understand how it would. A factory reset isn't going to suddenly make your phone start using a newer version of anything and what I was told was that the phone was using an old, no longer supported version/protocol to access voicemail and that was the root of the problem.
I suspect that if you take it into a VZW store for a "factory reset" what you're really going to get is an upgrade to Lollipop. Lol.
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
I chatted with Motorola and did a bunch of troubleshooting with them, they suggested trying a new sim card.
ray4jc said:
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
Click to expand...
Click to collapse
Wow. Talk about a lame answer. Nothing on the phone changed. Nothing on the phone broke. Obviously Verizon changed something on their side and rather than back out, or fix it, they want to shift the problem to the device owners.
At least you know you can probably fix it by going to Lollipop (so far that seems to have fixed everyone that has posted here) but that comes with some negatives. I'd rather still be on KitKat personally, but I put too much time into it already so I'm just going to be satisfied that it's working and try to forget how much I hate the factory tether piece of crap.
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
domenci said:
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
Click to expand...
Click to collapse
Were you rooted prior to factory reset? Did you need to re-root? Did the factory reset wipe the SD card? I want to fix this without upgrading to lollipop if possible
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
domenci said:
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
Click to expand...
Click to collapse
I did try a factory reset and it didn't work. Of course I'm running the eclipse 4.4.4 ROM not sure if that matters.
Looking in TiBU I've only got a few Verizon apps, none of them appear to be for voicemail the only thing that says voicemail is the phone 4.4.4-26 (19) app.
I'd love to stay on 4.4.4 if possible.
Otherwise I need to figure out which ROM to go to next.
Galaxy S9 software update 9-17-2018
G960U1UEU3ARH7 Verizon
1. Fixes an issue that could prevent the camera from responding or launching under certain scenarios.
10:22 AM
2. Addresses an issue that could prevent Android Pay? from working.
10:22 AM
3. Fixes an issue preventing the face unlock feature from working properly.
10:22 AM
4.Improves the Bluetooth® connection performance.
Yep I'm getting one now on my unlocked version. Looks like it addresses slo-mo recording plus a security update. Nothing on Samsung Pay or Bluetooth, although I'm not having any problems.
Nothing yet for me on Verizon.
Funny, since I have an unlocked phone, wifi calling isn't an option with AT&T and in fact has never even shown up in the settings. After this update, the option is now there but it fails when I try to enable it. I had to turn off notifications for phone because it was notifying me constantly to turn on wifi calling. Another new setting turned up though and was by default enabled, Volte calling.
Finally any update for the unlocked version after 3 freaking months!!!
Nothing yet for T-Mobile units.
Any reason I shouldn't install this?
Guatiao said:
Nothing yet for T-Mobile units.
Click to expand...
Click to collapse
Same here. I've been having an issue with Google Pay where it just stops working and requires a reboot to fix it. That being said, isn't Android Pay apart of Google Pay?
Android Pay is now Google Pay, they are one thing now. Rebranded and everything. Also, nothing here on my TMO S9 either yet.
After this update I see a few people reporting(including myself) that upon phone locking the s9/s9+ will just down. Any other people getting this issue?
Update Broke Bluetooh
After this update my Bluetooth randomly disconnects. I have contacted Samsung with no resolution. I have reset and cleared cache and data on the Bluetooth app, and I have done a network, wifi, and blueTooth systems settings reset.
This is very discouraging, especially since I am diabetic and use my phone to monitor my Dexcom G5 glucose sensor.
Airstream25 said:
Galaxy S9 software update 9-17-2018
G960U1UEU3ARH7 Verizon
1. Fixes an issue that could prevent the camera from responding or launching under certain scenarios.
10:22 AM
2. Addresses an issue that could prevent Android Pay? from working.
10:22 AM
3. Fixes an issue preventing the face unlock feature from working properly.
10:22 AM
4.Improves the Bluetooth® connection performance.
Click to expand...
Click to collapse
cdmcmillon said:
After this update my Bluetooth randomly disconnects. I have contacted Samsung with no resolution. I have reset and cleared cache and data on the Bluetooth app, and I have done a network, wifi, and blueTooth systems settings reset.
This is very discouraging, especially since I am diabetic and use my phone to monitor my Dexcom G5 glucose sensor.
Click to expand...
Click to collapse
Flash back to the previous firmware
If I flash back to a previous build through Odin, do i I have to factory reset?
Juice3250 said:
If I flash back to a previous build through Odin, do i I have to factory reset?
Click to expand...
Click to collapse
No, just make sure you use HOME_CSC and not CSC
CSC = Reset
HOME_CSC = No reset
*Detection* said:
No, just make sure you use HOME_CSC and not CSC
CSC = Reset
HOME_CSC = No reset
Click to expand...
Click to collapse
Awesome! Thanks.
After this update persons who i called hear buzzing sound from my bluetooth headset...
Is there anybody have this problem???
*Detection* said:
No, just make sure you use HOME_CSC and not CSC
CSC = Reset
HOME_CSC = No reset
Click to expand...
Click to collapse
Question about these...what is the difference?
If it resets will it not go back?
Also is this related to the "new sim" setup screen when you pop in a new carrier?
JaY iZz BaKk said:
Question about these...what is the difference?
If it resets will it not go back?
Also is this related to the "new sim" setup screen when you pop in a new carrier?
Click to expand...
Click to collapse
It will still go back, but it will wipe your whole phone back to factory settings in the process if you use CSC
Nothing to do with SIM setup, it will completely wipe your phone as if it was new out of the box
*Detection* said:
It will still go back, but it will wipe your whole phone back to factory settings in the process if you use CSC
Nothing to do with SIM setup, it will completely wipe your phone as if it was new out of the box
Click to expand...
Click to collapse
I used Home_csc and when I booted up, settings wouldn't open. I flashed back to ARG8 from BR19. I had to go into recovery and factory reset. Then I took the OTA update from Verizon. I realized that I hate having to re-enter all my passwords that aren't stored in the cloud.
Juice3250 said:
I used Home_csc and when I booted up, settings wouldn't open. I flashed back to ARG8 from BR19. I had to go into recovery and factory reset. Then I took the OTA update from Verizon. I realized that I hate having to re-enter all my passwords that aren't stored in the cloud.
Click to expand...
Click to collapse
That's bad luck, did you not try clearing CACHE from recovery first?
Either way managing to flash back should not have broken anything, sorry you had issues
My phone is the VOG-L29 10.0.0.178(C605E19R1P3) and I'm in the U.S. does anyone know how to fix mobile data not working after updating to 10.0.0.178(C605E19R1P3) from 9.1?
*Downloaded the update through the phone UI*
To verify that it was an OS issue I reverted back to 9.1 and the problem went away. So I updated again and it broke. My carrier is AT&T but the signal is fine as I can see the connection strength in the network settings and the SIM is registered. Plus I can see the cell information on the top left of the phone so the sim is definitely recognized. Bought a new sim anyway but the problem persists. Huawei support recommended I just not update my phone and keep it on 9.1 without security patches.
Already did a factory reset after updating to 10 and wiped the cache but that still didn't solve it.
So basically when simply looking at the phone, it appears to be working, until I try to do anything on mobile data. I can even see the send and receive icons being displayed to the right of the AT&T logo at the top left but I can't access the internet. everything else works including Wi-Fi.
This same thing happened when I tried to install 10.0.0.173 over 9.1.
Any ideas on a fix would be great, thank you in advance.
pseriesjim said:
My phone is the VOG-L29 10.0.0.178(C605E19R1P3) and I'm in the U.S. does anyone know how to fix mobile data not working after updating to 10.0.0.178(C605E19R1P3) from 9.1?
*Downloaded the update through the phone UI*
To verify that it was an OS issue I reverted back to 9.1 and the problem went away. So I updated again and it broke. My carrier is AT&T but the signal is fine as I can see the connection strength in the network settings and the SIM is registered. Plus I can see the cell information on the top left of the phone so the sim is definitely recognized. Bought a new sim anyway but the problem persists. Huawei support recommended I just not update my phone and keep it on 9.1 without security patches.
Already did a factory reset after updating to 10 and wiped the cache but that still didn't solve it.
So basically when simply looking at the phone, it appears to be working, until I try to do anything on mobile data. I can even see the send and receive icons being displayed to the right of the AT&T logo at the top left but I can't access the internet. everything else works including Wi-Fi.
This same thing happened when I tried to install 10.0.0.173 over 9.1.
Any ideas on a fix would be great, thank you in advance.
Click to expand...
Click to collapse
Re-enter the passwords on the APNs, it corrupts them, they're supposed to be ******* or something but it enters BLANK, something along those lines, but that's the fix
*Detection* said:
Re-enter the passwords on the APNs, it corrupts them, they're supposed to be ******* or something but it enters BLANK, something along those lines, but that's the fix
Click to expand...
Click to collapse
That fixed it, I can't thank you enough.
I don't think VOLTE is working for me. Maybe I'm not sure how voLTE works, but on my Nokia 9 and OnePlus 7 Pro I have an icon that says VOLTE.
When I place a call my signal goes from LTE/LTE+ to either 3G/H+. Which I don't think it's supposed to do on VOLTE.
I have:
XQ-AT51
Build Number: 58.0.A.3.170
Google Play System: September 30th 2020
Baseband version: sdx55.rmtefs-00068-13
Carrier: T-MOBILE USA
In Network & Internet > Mobile Network: Enable VoLTE is enabled
In About Phone > SIM Status: Mobile Voice network type is LTE. However, when I'm on a call it says UMTS and HSPA+ for voice and data
In *#*#4636#*#* VoLTE is also enabled.
So, I'm not sure if I'm missing something, but I've never had this issue before on my other phone.
EDIT: Spoke with a technician at T-Mobile and they said everything is fine on my account. Did say to get a new sim card, which didn't fix the issue.
tjk639 said:
I don't think VOLTE is working for me. Maybe I'm not sure how voLTE works, but on my Nokia 9 and OnePlus 7 Pro I have an icon that says VOLTE.
When I place a call my signal goes from LTE/LTE+ to either 3G/H+. Which I don't think it's supposed to do on VOLTE.
I have:
XQ-AT51
Build Number: 58.0.A.3.170
Google Play System: September 30th 2020
Baseband version: sdx55.rmtefs-00068-13
Carrier: T-MOBILE USA
In Network & Internet > Mobile Network: Enable VoLTE is enabled
In About Phone > SIM Status: Mobile Voice network type is LTE. However, when I'm on a call it says UMTS and HSPA+ for voice and data
In *#*#4636#*#* VoLTE is also enabled.
So, I'm not sure if I'm missing something, but I've never had this issue before on my other phone.
EDIT: Spoke with a technician at T-Mobile and they said everything is fine on my account. Did say to get a new sim card, which didn't fix the issue.
Click to expand...
Click to collapse
Yeah bro i have two Xperia 1 IIs and i didn't update the other one but the one i updated seems to have the same issue i even switched carries VOLTE is enabled and not working I'm thinking of factory resetting as last resort I'm contacting Sony first you should do the same. I have same build number as you.
tjk639 said:
I don't think VOLTE is working for me. Maybe I'm not sure how voLTE works, but on my Nokia 9 and OnePlus 7 Pro I have an icon that says VOLTE.
When I place a call my signal goes from LTE/LTE+ to either 3G/H+. Which I don't think it's supposed to do on VOLTE.
I have:
XQ-AT51
Build Number: 58.0.A.3.170
Google Play System: September 30th 2020
Baseband version: sdx55.rmtefs-00068-13
Carrier: T-MOBILE USA
In Network & Internet > Mobile Network: Enable VoLTE is enabled
In About Phone > SIM Status: Mobile Voice network type is LTE. However, when I'm on a call it says UMTS and HSPA+ for voice and data
In *#*#4636#*#* VoLTE is also enabled.
So, I'm not sure if I'm missing something, but I've never had this issue before on my other phone.
EDIT: Spoke with a technician at T-Mobile and they said everything is fine on my account. Did say to get a new sim card, which didn't fix the issue.
Click to expand...
Click to collapse
I software repaired the phone and volte is working again sadly I found no other way that doesn't involve that , I too thought it was my sim card/service and switched carriers only to find the same issue but it's fixed now sucks I wasted my time looking for a solution all this time since November
charlie313 said:
I software repaired the phone and volte is working again sadly I found no other way that doesn't involve that , I too thought it was my sim card/service and switched carriers only to find the same issue but it's fixed now sucks I wasted my time looking for a solution all this time since November
Click to expand...
Click to collapse
What did you do exactly?
bbot3k said:
What did you do exactly?
Click to expand...
Click to collapse
I plugged my phone into my laptop and it installed the xperia companion and I picked software repair which I thought wasn't gonna erase my data but it turned out it's basically like factory reset and then I just reinstalled everything . I then updated my apn settings manually from the TMobile apn settings and it was working like it was before the dumb update but sadly wasted reinstalling but I guess I should've just done this from the beginning instead of wasting all my time fiddling with secret menus, customer service and crap so if you want it fixed definitely give it a try if not hopefully the next update fixes, I'm hoping it doesn't happen again, major time wasted searching the internet for a solution
charlie313 said:
I plugged my phone into my laptop and it installed the xperia companion and I picked software repair which I thought wasn't gonna erase my data but it turned out it's basically like factory reset and then I just reinstalled everything . I then updated my apn settings manually from the TMobile apn settings and it was working like it was before the dumb update but sadly wasted reinstalling but I guess I should've just done this from the beginning instead of wasting all my time fiddling with secret menus, customer service and crap so if you want it fixed definitely give it a try if not hopefully the next update fixes, I'm hoping it doesn't happen again, major time wasted searching the internet for a solution
[/QUOTE
charlie313 said:
I plugged my phone into my laptop and it installed the xperia companion and I picked software repair which I thought wasn't gonna erase my data but it turned out it's basically like factory reset and then I just reinstalled everything . I then updated my apn settings manually from the TMobile apn settings and it was working like it was before the dumb update but sadly wasted reinstalling but I guess I should've just done this from the beginning instead of wasting all my time fiddling with secret menus, customer service and crap so if you want it fixed definitely give it a try if not hopefully the next update fixes, I'm hoping it doesn't happen again, major time wasted searching the internet for a solution
Click to expand...
Click to collapse
But yeah definitely back up to a computer or something and/or Google all your stuff before you decide to software repair. If you don't have one maybe factory reset it because I honestly think they're same thing I could be wrong though but I couldn't find any difference on the internet between the two.
Click to expand...
Click to collapse
I am SO glad I found this thread and it's not just me having this issue.
I originally thought it was Google Voice messing with my phone, since I make calls and texts from Google Voice, and have my incoming TMobile calls and outgoing TMobile calls redirect to be to/from my Google Voice number. But even after removing Google Voice and completely unlinking it from my phone, my phone refuses to do VoLTE calls.
When receiving a call, the phone will drop down to HSPA+ and sometimes, it takes so long for it to do this, my phone only rings once before I just end up getting a missed call notification. Meanwhile, the caller says they were ringing for the full 30 seconds. Similarly when I make a call, the phone drops down to HSPA or even EDGE to make a call. When I hang up, or get off a call, boom, back to LTE or LTE+.
I went to a TMobile store and they gave me a new SIM and fiddled with my APN settings, to no avail. I haven't bothered contacting Sony, since I figure they will just blame TMobile. The only thing I haven't tried is the factory reset, which is something I very much wanted to avoid, but I'll try it with the Xperia Companion software and keep my fingers crossed. I'll update with my results.
In the meantime, I'm attaching some screenshots of my device info showing the VoLTE is indeed enabled, as well as my APN settings. Maybe they'll help someone here. (WiFi calling is apparently not a thing on this phone, which is disappointing, but I also have Google Voice under normal circumstances, so that hasn't been a problem for me).
GrumpyFox said:
I am SO glad I found this thread and it's not just me having this issue.
I originally thought it was Google Voice messing with my phone, since I make calls and texts from Google Voice, and have my incoming TMobile calls and outgoing TMobile calls redirect to be to/from my Google Voice number. But even after removing Google Voice and completely unlinking it from my phone, my phone refuses to do VoLTE calls.
When receiving a call, the phone will drop down to HSPA+ and sometimes, it takes so long for it to do this, my phone only rings once before I just end up getting a missed call notification. Meanwhile, the caller says they were ringing for the full 30 seconds. Similarly when I make a call, the phone drops down to HSPA or even EDGE to make a call. When I hang up, or get off a call, boom, back to LTE or LTE+.
I went to a TMobile store and they gave me a new SIM and fiddled with my APN settings, to no avail. I haven't bothered contacting Sony, since I figure they will just blame TMobile. The only thing I haven't tried is the factory reset, which is something I very much wanted to avoid, but I'll try it with the Xperia Companion software and keep my fingers crossed. I'll update with my results.
In the meantime, I'm attaching some screenshots of my device info showing the VoLTE is indeed enabled, as well as my APN settings. Maybe they'll help someone here. (WiFi calling is apparently not a thing on this phone, which is disappointing, but I also have Google Voice under normal circumstances, so that hasn't been a problem for me).
Click to expand...
Click to collapse
Yeah someone explained to me that Software Repair is different from Software Reset . It's what i did to fix this issue i hope it fixes it for you as well. I know how much of a hassle and time wasted on this is
charlie313 said:
Yeah someone explained to me that Software Repair is different from Software Reset . It's what i did to fix this issue i hope it fixes it for you as well. I know how much of a hassle and time wasted on this is
Click to expand...
Click to collapse
I also couldn't find anything to help me and as soon as i posted on here and reddit out came people like you with the same issue. Glad i posted and hope everyone who's done a software repair has fixed the issue. Happy Holidays
charlie313 said:
I also couldn't find anything to help me and as soon as i posted on here and reddit out came people like you with the same issue. Glad i posted and hope everyone who's done a software repair has fixed the issue. Happy Holidays
Click to expand...
Click to collapse
I'm in the process of doing the "Repair" now. Hopefully this fixes it. If it does, 1- Awesome! 2- Hopefully it doesn't get borked again when Android 11 rolls around. It's supposedly making its way to the 1ii, but I personally haven't gotten it yet.
GrumpyFox said:
I'm in the process of doing the "Repair" now. Hopefully this fixes it. If it does, 1- Awesome! 2- Hopefully it doesn't get borked again when Android 11 rolls around. It's supposedly making its way to the 1ii, but I personally haven't gotten it yet.
Click to expand...
Click to collapse
Yeah that's what I'm afraid of too i don't want to be reinstalling all my stuff again. If it happens to get stuck on you while you're doing the process just try again. Mine froze during the restarting part of the repair i just held the volume and power button at same time to hard reset it
charlie313 said:
Yeah that's what I'm afraid of too i don't want to be reinstalling all my stuff again. If it happens to get stuck on you while you're doing the process just try again. Mine froze during the restarting part of the repair i just held the volume and power button at same time to hard reset it
Click to expand...
Click to collapse
Yup. My device appears to be bricked. The repair failed on my PC and now when attempting to turn the phone on, I'm met with "Your device is corrupt. It can't be trusted and may not work properly. It will shut down in 5 seconds."
I'm attempting to get it to boot into recovery.
I never imagined my first experience with a Sony phone would be so bad.
GrumpyFox said:
Yup. My device appears to be bricked. The repair failed on my PC and now when attempting to turn the phone on, I'm met with "Your device is corrupt. It can't be trusted and may not work properly. It will shut down in 5 seconds."
I'm attempting to get it to boot into recovery.
I never imagined my first experience with a Sony phone would be so bad.
Click to expand...
Click to collapse
Yeah just horrible luck. Still prefer a software problem over a house fire like that samsung fiasco but still . Yeah just keep trying I'm sure there are ways to factory reset it and then software repair it.
R
....and Never forget its
"Enable VoLTE when available"
There might be the network issue too.
I'm in Nepal and the carrier has started VoLTE few days ago but they haven't listed my phone for VoLTE supporting device . They just have iPhone, Samsungs, Xiaomi etc and not SONY but you know what... Its working for me.
HD voice and LTE while in a call too.
Glad I found this thread. I've got an Xperia 10+ doing the same thing under Lineage 18.1 (Mermaid). Will give this a shot and see what happens. Hopefully I don't brick it.
I have a Pixel 5. I was trying to turn on wi-fi calling. It is no longer on my menu. I searched settings, I did a bunch of "Googling". Everything I read says it should be in the Phone app under Settings and then Calls. It is not. Searching the menu brings nothing up either. I have an old Pixel 2 on the same network. I found the wi-fi calling option and turned it on pretty easily.
Any idea what is going on here? I am clueless.
Stock ROM?
Rooted?
Carrier?
----------------------------------------------------
I am stock ROM, Rooted, Verizon, and it is in Settings > Network & Internet > Mobile network > Advanced > Wi-Fi calling
andybones said:
Stock ROM?
Rooted?
Carrier?
----------------------------------------------------
I am stock ROM, Rooted, Verizon, and it is in Settings > Network & Internet > Mobile network > Advanced > Wi-Fi calling
Click to expand...
Click to collapse
Stock, unrooted, originally AT&T, now TING (Verizon). Is there any reason to root a Pixel? (If there is, I will)
draexo said:
Stock, unrooted, originally AT&T, now TING (Verizon). Is there any reason to root a Pixel? (If there is, I will)
Click to expand...
Click to collapse
That's an entirely different question with various threads debating the points. But to your OP it is also in the phone settings, calling accounts, <click> the account and Wifi calling can be enabled there. If it's not there then perhaps it's not available on your dialing network.
The carrier (Ting/Verizon) turned it on. Magically, wifi calling appeared in my settings!
Now the Pixel 2 is using wifi calling fine. The Pixel 5 allows me to attempt to turn it on, but, alas, it fails. I contacted support again and they confirmed wifi calling is on for both devices. So, they did the "default" troubleshooting thing of asking me to do a factory reset on the Pixel 5 to see if that would make it use wifi calling.
I do not want to do a factory reset.
draexo said:
The carrier (Ting/Verizon) turned it on. Magically, wifi calling appeared in my settings!
Now the Pixel 2 is using wifi calling fine. The Pixel 5 allows me to attempt to turn it on, but, alas, it fails. I contacted support again and they confirmed wifi calling is on for both devices. So, they did the "default" troubleshooting thing of asking me to do a factory reset on the Pixel 5 to see if that would make it use wifi calling.
I do not want to do a factory reset.
Click to expand...
Click to collapse
The only time I'd do a factory reset was when I wanted to for some reason or another. Never when a CSR tells be to do one to troubleshoot. Most I'd do is a reboot which I'm sure you've done. As for Wifi calling it's not all it's cracked up to be. I get dropped calls, crumby audio and overall a bad experience so I turned it off. Is there a demanding reason you need it? I'd also try to troubleshoot on your own and maybe check out Reddit for some insights. Good luck.
bobby janow said:
The only time I'd do a factory reset was when I wanted to for some reason or another. Never when a CSR tells be to do one to troubleshoot. Most I'd do is a reboot which I'm sure you've done. As for Wifi calling it's not all it's cracked up to be. I get dropped calls, crumby audio and overall a bad experience so I turned it off. Is there a demanding reason you need it? I'd also try to troubleshoot on your own and maybe check out Reddit for some insights. Good luck.
Click to expand...
Click to collapse
I switched from AT&T because of lack of coverage at my home about 2 weeks ago. TING/Verizon covers both. Last night, I lost service. Something happened to the Verizon tower for about 2/3 hours. If I had wi-fi calling, it would not have been an issue. Will this be something that happens on occasion? Most likely not. I never used wi-fi calling before (I had a microcell @ home for AT&T).
Reddit? I thought XDA was the place for all things cell phone related!
I went to clear the system cache... but apparently Android 11 does not have one!!
It just bugs me that I can not get it to turn on.
4 months until Pixel 6.... I guess I can wait for that and THEN do a factory reset.
draexo said:
I switched from AT&T because of lack of coverage at my home about 2 weeks ago. TING/Verizon covers both. Last night, I lost service. Something happened to the Verizon tower for about 2/3 hours. If I had wi-fi calling, it would not have been an issue. Will this be something that happens on occasion? Most likely not. I never used wi-fi calling before (I had a microcell @ home for AT&T).
Reddit? I thought XDA was the place for all things cell phone related!
I went to clear the system cache... but apparently Android 11 does not have one!!
It just bugs me that I can not get it to turn on.
4 months until Pixel 6.... I guess I can wait for that and THEN do a factory reset.
Click to expand...
Click to collapse
Yes, stick with XDA,
What do you mean that "Android 11 doesn't have one" - You mean Android 11 doesn't have system cache?
What did you try that leads you to think this?
go to dialer and type *#*#4636#*#*
then Phone information
then check that Wifi calling Provisioned is checked.
Hopefully help from users here can help you get it turned on.
I do feel a factory reset may be needed, however. but NOT sure at all.
Make sure My Verizon Services is turned on in app settings. (search system apps to find it). Allow it to Modify system settings, reboot
I remember having to jump some hoops like factory reset and clearing certain things in fastboot on the HTC 10 with Verizon in regards to WI-FI Calling/VoLTE.
Let me ask, did you switch from AT&T to TING while you owned this Pixel 5.
If so, was it working with AT&T?
When did you switch (which update of the Pixel)
WiFi Calling at Verizon FAQs | Verizon
Learn how to use Verizon Wi-Fi calling if cellular service isn't available.
www.verizon.com
3 Ways To Fix Verizon Unable To Activate WiFi Calling - Internet Access Guide
Verizon unable to activate WiFi calling? We have enlisted the most helpful ways and expect that these methods will remove the problem for you.
internet-access-guide.com
draexo said:
I switched from AT&T because of lack of coverage at my home about 2 weeks ago. TING/Verizon covers both. Last night, I lost service. Something happened to the Verizon tower for about 2/3 hours. If I had wi-fi calling, it would not have been an issue. Will this be something that happens on occasion? Most likely not. I never used wi-fi calling before (I had a microcell @ home for AT&T).
Reddit? I thought XDA was the place for all things cell phone related!
I went to clear the system cache... but apparently Android 11 does not have one!!
It just bugs me that I can not get it to turn on.
4 months until Pixel 6.... I guess I can wait for that and THEN do a factory reset.
Click to expand...
Click to collapse
@andybones Lol, I'm not saying ditch XDA it's my go to. But... Reddit has some pretty good content for phone issues along with cute animal pics (subreddit r/aww) and all kinds of stuff to get lost in.
As for this issue I did a cursory search in the GooglePixel sub and there have been some issues going back over the years with Ting and ATT and wifi calling. One post said use the dialer code you mentioned above and provisioning. Also factory resets did not help at least one frustrated user. Factory resets are so laborious even with Google cloud but I guess if it's needed then worth a try.
OP keep us posted if you do happen to get it fixed. Then I'll link it to the subreddit. lol
andybones said:
Yes, stick with XDA,
What do you mean that "Android 11 doesn't have one" - You mean Android 11 doesn't have system cache?
What did you try that leads you to think this?
Click to expand...
Click to collapse
When I get into recovery, the option to wipe cache partition is simply not there. All the other normal recovery options are there.... reboot, reboot to bootloader, apply update from ADB... even factory/data reset, but wipe cache partition is gone.
Here is a thread regarding the system cache.
https://www.reddit.com/r/oneplus/comments/j8ohht
andybones said:
go to dialer and type *#*#4636#*#*
then Phone information
then check that Wifi calling Provisioned is checked.
Click to expand...
Click to collapse
WiFi calling Provisioned IS checked.
andybones said:
Hopefully help from users here can help you get it turned on.
I do feel a factory reset may be needed, however. but NOT sure at all.
Make sure My Verizon Services is turned on in app settings. (search system apps to find it). Allow it to Modify system settings, reboot
Click to expand...
Click to collapse
I have no "My Verizon Services" APP
andybones said:
I remember having to jump some hoops like factory reset and clearing certain things in fastboot on the HTC 10 with Verizon in regards to WI-FI Calling/VoLTE.
Let me ask, did you switch from AT&T to TING while you owned this Pixel 5.
If so, was it working with AT&T?
When did you switch (which update of the Pixel)
Click to expand...
Click to collapse
I switched about 2 weeks ago. I was on the June update with AT&T. No idea if wifi calling worked as I had an old AT&T microcell I used at home instead. I am now on the July update. I bought the phone from the Google store, not a carrier.
andybones said:
WiFi Calling at Verizon FAQs | Verizon
Learn how to use Verizon Wi-Fi calling if cellular service isn't available.
www.verizon.com
3 Ways To Fix Verizon Unable To Activate WiFi Calling - Internet Access Guide
Verizon unable to activate WiFi calling? We have enlisted the most helpful ways and expect that these methods will remove the problem for you.
internet-access-guide.com
Click to expand...
Click to collapse
bobby janow said:
@andybones Lol, I'm not saying ditch XDA it's my go to. But... Reddit has some pretty good content for phone issues along with cute animal pics (subreddit r/aww) and all kinds of stuff to get lost in.
As for this issue I did a cursory search in the GooglePixel sub and there have been some issues going back over the years with Ting and ATT and wifi calling. One post said use the dialer code you mentioned above and provisioning. Also factory resets did not help at least one frustrated user. Factory resets are so laborious even with Google cloud but I guess if it's needed then worth a try.
OP keep us posted if you do happen to get it fixed. Then I'll link it to the subreddit. lol
Click to expand...
Click to collapse
I made a comment about sticking with XDA. Meaning stick with XDA, literally. If he finds the answer someplace else, GREAT! Just stick with XDA, and come back and post what fixed it.
Roll your eye all you want though. Useless as it is, roll on.
draexo said:
I cant not find it. Where is it? Do I need to go into recovery? Everything I try ends up with the dead android image.
Here is a thread regarding the system cache.
https://www.reddit.com/r/oneplus/comments/j8ohht
WiFi calling Provisioned IS checked.
I have no "My Verizon Services" APP
I switched about 2 weeks ago. I was on the June update with AT&T. No idea if wifi calling worked as I had an old AT&T microcell I used at home instead. I am now on the July update. I bought the phone from the Google store, not a carrier.
Click to expand...
Click to collapse
That thread is for OnePlus phone..
Also I'm guessing it was for when Android 11 came out and updating from Android 10 to Android 11. Yes, wiping cache for all apps will cut down on errors.
Maybe not having the My Verizon services app is leading to the issue.
I bought mine from Google store.. not Verizon (or I'd not have root)
Are you selecting in settings - Apps - "show system"?
andybones said:
You can post to Reddit, I was just saying don't ditch XDA..
That thread is for OnePlus phone..
Also I'm guessing it was for when Android 11 came out and updating from Android 10 to Android 11. Yes, wiping cache for all apps will cut down on errors.
Maybe not having the My Verizon services app is leading to the issue.
I bought mine from Google store.. not Verizon (or I'd not have root)
Are you selecting in settings - Apps - "show system"?
Click to expand...
Click to collapse
You are correct, when I select "show system" My Verizon Services shows up. It has same permissions as yours.
I was able to get into recovery, but wipe cache partition is not an option anymore. Very strange.
I also deleted some AT&T apps that were still hanging around.
draexo said:
You are correct, when I select "show system" My Verizon Services shows up. It has same permissions as yours.
I was able to get into recovery, but wipe cache partition is not an option anymore. Very strange.
I also deleted some AT&T apps that were still hanging around.
Click to expand...
Click to collapse
What about when you select Advanced and then is "modify system settings" allowed for the My Verizon services?
Also how were you able to delete AT&T apps? were they not system apps? or do you have root? I recall your post up above saying unrooted.
IIRC, stock recovery never had option to wipe cache, but rather to wipe data/factory reset
I would check the Playstore for an app to wipe cache, I'd link but the one I use requires root.
A suggestion is to root the device, try wiping the cache, and if things get working remove root.
Let me ask this, did you flash the July Factory image since switching to TING?
Try removing -w (to not lose data) and flash the latest July again. Can't hurt.
andybones said:
What about when you select Advanced and then is "modify system settings" allowed for the My Verizon services?
Click to expand...
Click to collapse
Yes, it is.
andybones said:
Also how were you able to delete AT&T apps? were they not system apps? or do you have root? I recall your post up above saying unrooted.
Click to expand...
Click to collapse
I installed them manually myself when I got the phone. I deleted them.
andybones said:
IIRC, stock recovery never had option to wipe cache, but rather to wipe data/factory reset
I would check the Playstore for an app to wipe cache, I'd link but the one I use requires root.
A suggestion is to root the device, try wiping the cache, and if things get working remove root.
Click to expand...
Click to collapse
I can root it. I just have not had a need for root in years. I will try this and report back.
From the images I saw on the Verizon website, the stock pixel recovery does have wipe cache, but no harm in rooting.
andybones said:
Let me ask this, did you flash the July Factory image since switching to TING?
Try removing -w (to not lose data) and flash the latest July again. Can't hurt.
Click to expand...
Click to collapse
Is there no one-click root? Maybe Magisk? I am not needing a custom ROM.
Spent quite a bit of time searching the net for answers. Seems like a common issue across all the Pixel devices, and yet, no one has ever managed to get it working except in instances where the carrier's provisioning was incorrect.
andybones said:
I made a comment about sticking with XDA. Meaning stick with XDA, literally. If he finds the answer someplace else, GREAT! Just stick with XDA, and come back and post what fixed it.
Roll your eye all you want though. Useless as it is, roll on.
Click to expand...
Click to collapse
I'm sorry, what exactly do you mean by that?
I contacted Google Support.
Here is what they had me do:
1 Settings > System > Advanced > Reset Options > Reset Wi_Fi, mobile & Bluetooth. MAKE SURE TO UNCKEC ERASE DOWNLOADED SIMS
2 Settings > Apps & Notifications >(see all apps) Phone App > Clear Cache, Force Stop
3 Update all PlayStore Apps
4 Reboot
5 Attempt to enable Wi-Fi
FAIL
Insist the problem is with the carrier.
draexo said:
Is there no one-click root? Maybe Magisk? I am not needing a custom ROM.
Click to expand...
Click to collapse
I use and suggest Magisk for rooting. But you will need a PC to fastboot flash the modified boot.img
draexo said:
Spent quite a bit of time searching the net for answers. Seems like a common issue across all the Pixel devices, and yet, no one has ever managed to get it working except in instances where the carrier's provisioning was incorrect.
Click to expand...
Click to collapse
draexo said:
I contacted Google Support.
Here is what they had me do:
1 Settings > System > Advanced > Reset Options > Reset Wi_Fi, mobile & Bluetooth. MAKE SURE TO UNCKEC ERASE DOWNLOADED SIMS
2 Settings > Apps & Notifications >(see all apps) Phone App > Clear Cache, Force Stop
3 Update all PlayStore Apps
4 Reboot
5 Attempt to enableReboot but
FAIL
Insist the problem is with the carrier.
Click to expand...
Click to collapse
I think if it's anything like how VZW is, it is the carrier. Possibly factory reset needed after turning on, or something else like wiping cache on the Phone and Settings apps.
andybones said:
I use and suggest Magisk for rooting. But you will need a PC to fastboot flash the modified boot.img
I think if it's anything like how VZW is, it is the carrier. Possibly factory reset needed after turning on, or something else like wiping cache on the Phone and Settings apps.
Click to expand...
Click to collapse
Going to try a different SIM card from another carrier over the weekend. I will report back.