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.
Related
It appears to be a new feature (based on a search the Galaxy S 4 from Sprint is having the same problem) that you can not disable the data and voice roam guards. They are checked and greyed out.
Can anyone on 4.3 uncheck these and if so what ROM are you on?
I can check/uncheck all, running ElipticOne 4.3 v2
bigdaddy619 said:
I can check/uncheck all, running ElipticOne 4.3 v2
Click to expand...
Click to collapse
Strange I am on BadBoy and it is greyed out... Galaxy S 4 users are having the same problem.
I was able to disable them before my phone provisioned... looks like that may be where it is locking it.
I can't use any previous backups (which kinda sucks) but atleast I got them turned off.
numus said:
I was able to disable them before my phone provisioned... looks like that may be where it is locking it.
I can't use any previous backups (which kinda sucks) but atleast I got them turned off.
Click to expand...
Click to collapse
I am sitting 100% stock (un-rooted for now), and I can remove the roaming guards, you may want to check with others using the same ROM as you.
I am also able to toggle them off and on, completely stock and unrooted. I read somewhere if you toggle data mode to CDMA only you can change them, then change it back to CDMA/LTE and they stick. Might wanna give that a try.
I'm on SwG 2.02 and can also check/uncheck all roaming guards.
Perhaps there is an incorrect build.prop edit.
I'm on BadBoy and I can check/uncheck it.
Sent from my HTCONE using Tapatalk now Free
As of 4.3 I can't uncheck them. No one in my house can, all 3 of us are on HTC Ones that have been updated to 4.3 completely stock.
Switching to CDMA Only did not change it, still grayed out.
kwolf said:
As of 4.3 I can't uncheck them. No one in my house can, all 3 of us are on HTC Ones that have been updated to 4.3 completely stock.
Switching to CDMA Only did not change it, still grayed out.
Click to expand...
Click to collapse
I think it is a problem with having old settings on the phone... If I use the HTC restore then I lose the ability to uncheck them, when I do a clean flash without the restore I have no problem unchecking them.
Try a clean wipe (and don't use any restore programs like HTC) and see if you can uncheck them
numus said:
I think it is a problem with having old settings on the phone... If I use the HTC restore then I lose the ability to uncheck them, when I do a clean flash without the restore I have no problem unchecking them.
Try a clean wipe (and don't use any restore programs like HTC) and see if you can uncheck them
Click to expand...
Click to collapse
If I have to choose between installing and re-configuring all my apps again, or having the irritating data roaming message... I'll probably just deal with the message. I don't have time to re-do my phone all over again :/
kwolf said:
If I have to choose between installing and re-configuring all my apps again, or having the irritating data roaming message... I'll probably just deal with the message. I don't have time to re-do my phone all over again :/
Click to expand...
Click to collapse
If you have bluetooth integration in your vehicle, it is more than just an "irritating" message. It actually prevents you from using your car's bluetooth to dial your phone in roaming (the call will always fail unless you manually select the dismiss on the roam notification from the phone). This is more than just irritating. Also will prevent you from streaming music during trips (atleast when you pop in and out of roaming locations) because each time you enter a roaming location you will have to dismiss the guard before it will let you get data on the roaming network.
numus said:
If you have bluetooth integration in your vehicle, it is more than just an "irritating" message. It actually prevents you from using your car's bluetooth to dial your phone in roaming (the call will always fail unless you manually select the dismiss on the roam notification from the phone). This is more than just irritating.
Click to expand...
Click to collapse
I guess I'll just chalk this experience up to HTC's notoriously amazing QA. Maybe I'll re-do my phone this weekend then. We are also having problems where all of our phones are having received SMS timestamps that are 1 hour behind (but only on sprint towers, and only in the tri cities - works fine roaming, in knoxville, or on airave...). Wonder if it's also related to restoring the backup or just Sprint being Sprint.
kwolf said:
I guess I'll just chalk this experience up to HTC's notoriously amazing QA. Maybe I'll re-do my phone this weekend then. We are also having problems where all of our phones are having received SMS timestamps that are 1 hour behind (but only on sprint towers, and only in the tri cities - works fine roaming, in knoxville, or on airave...). Wonder if it's also related to restoring the backup or just Sprint being Sprint.
Click to expand...
Click to collapse
... How close are you to the next timezone?
numus said:
... How close are you to the next timezone?
Click to expand...
Click to collapse
About 3 hours freeway driving. Knoxville is closer and I don't have the problem there. All 3 of our Ones are affected (and we aren't even on the same Sprint plan) but my buddy's iPhone is not. Also, the clock on my phone is always correct and it is set to get the time from the tower. It is only received SMS timestamps that are wrong. A conversation will look like this: Sent message 10:40AM Received message 9:41AM Sent message 10:42AM Received message 9:44AM etc.
I will just reset the phone this weekend, maybe it will be happy again.
kwolf said:
About 3 hours freeway driving. Knoxville is closer and I don't have the problem there. All 3 of our Ones are affected (and we aren't even on the same Sprint plan) but my buddy's iPhone is not. Also, the clock on my phone is always correct and it is set to get the time from the tower. It is only received SMS timestamps that are wrong. A conversation will look like this: Sent message 10:40AM Received message 9:41AM Sent message 10:42AM Received message 9:44AM etc.
I will just reset the phone this weekend, maybe it will be happy again.
Click to expand...
Click to collapse
Did you try toggling the data mode to cdma only and then changing them?
TriBeard said:
Did you try toggling the data mode to cdma only and then changing them?
Click to expand...
Click to collapse
kwolf said:
Switching to CDMA Only did not change it, still grayed out.
Click to expand...
Click to collapse
Posted earlier, no it did not work.
kwolf said:
Posted earlier, no it did not work.
Click to expand...
Click to collapse
Oops. Got that one by me.
I recently got a new phone from AT&T. I haven't contacted them as I haven't felt it necessary yet. After recently switching from an iPhone 4, I love Android. I quickly rooted it with the Ping Pong method and installed apps such as Busy Box, Greenify, Nova Launcher, Clock Sync Adblock Plus, System Tuner, SD Maid, Titanium Backup, Uninstall, and etcetera. I listed almost all root applications due to it may being a problem with that. My phone worked fine for a while. I noticed it stopped working after some calls stopped coming through as well as texts. Randomly, I see that my texts don't go through, but after a quick restart it seems to work fine. I was wondering if there is any way of getting logs to help someone out there figure this out for me. If unrooting via SuperSU and then factory wiping my device would work please let me know. If there is any information I can provide you I will. The phone worked for the first week fine. Restarts seem to fix the issue until around ~6 hours of time using the device. It mainly sits next to me at my desk.
SMS doesn't go through or receive. Phone calls are not received (Have not tried outgoing). Cellular Data (4G/LTE) does not work.
--Edit:
I have frozen the OTA notifications from wsync. I also remove some bloatware thanks to System app remover (ROOT) by Jumobile. It gives you things that are not CRUCIAL to your system to remove. I removed a few things. Nothing relate to Samsung.
I'd make a backup backup of the phone using your favorite method (I seem to remember that titanium can do this), and try a factory reset to see if that fixes your problem. AoN
anneoneamouse said:
I'd make a backup backup of the phone using your favorite method (I seem to remember that titanium can do this), and try a factory reset to see if that fixes your problem. AoN
Click to expand...
Click to collapse
Well... Umm. dm-verify verifaction failed... So I'm guessing that I "bricked" my device. Guessing I have to plug it into my pc and do a flash somehow. Any info?
--Edit: Booted into my device with same settings. However I cannot do a factory restore as it always says dm-verify verification failed.
Beyond my knowledge. If the phone still functions, un freeze / restore all the system stuff you disabled, try again? But I'm just guessing. AoN
Use Odin to flash the factory OE2 firmware via PC.
If you're still having issues it may be a faulty SIM card.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
MrBaltazar said:
Use Odin to flash the factory OE2 firmware via PC.
If you're still having issues it may be a faulty SIM card.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Click to expand...
Click to collapse
Alright, I flashed everything. Re-rooted (I tested before root if the Cellular Data/Messages worked. Cellular data did not, but messages did (and haven't had issues after root). The cellular data still DOES NOT work. I live in a location where LTE is supported. Any info?
LordNature said:
Alright, I flashed everything. Re-rooted (I tested before root if the Cellular Data/Messages worked. Cellular data did not, but messages did (and haven't had issues after root). The cellular data still DOES NOT work. I live in a location where LTE is supported. Any info?
Click to expand...
Click to collapse
This may be s silly question but have you tried toggling the 2 switches under mobile networks/mobile data off then on? One of them is enhanced 4G LTE services. I read somewhere that this might help.
Message center using the right number? 13123149810
jondroid2 said:
This may be s silly question but have you tried toggling the 2 switches under mobile networks/mobile data off then on? One of them is enhanced 4G LTE services. I read somewhere that this might help.
Click to expand...
Click to collapse
Tried every single tab under that
LordNature said:
Tried every single tab under that
Click to expand...
Click to collapse
Call AT&T tech support and have them provision your data on the back end again. Just explain that everything works except your data. This can happen if there is a data block on your line or if someone used the my AT&T app to turn off data for lines on the account.
Are you able to make phone calls?
Do you see the 4G LTE logo at the top when wifi is turned off?
Sent from my Galaxy S6 on AT&T
MrBaltazar said:
Call AT&T tech support and have them provision your data on the back end again. Just explain that everything works except your data. This can happen if there is a data block on your line or if someone used the my AT&T app to turn off data for lines on the account.
Are you able to make phone calls?
Do you see the 4G LTE logo at the top when wifi is turned off?
Sent from my Galaxy S6 on AT&T
Click to expand...
Click to collapse
4G LTE logo does not display when wifi is off.
Phone calls work.
LordNature said:
4G LTE logo does not display when wifi is off.
Phone calls work.
Click to expand...
Click to collapse
Call at&t. I'm almost sure it's not on your end.
Sent from my Galaxy S6 on AT&T
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.
My phone is constantly being interrupted by this annoying popup: (I can't post links being a new user, but the image is at imgur FN7uUhL )
"Alert
Sorry, we're having trouble connecting. Make sure you have a good signal and try again. If you still can't connect, call us at 800-922-0204.
Error code 1001"
It doesn't say what app it is, but I suspect it's from Verizon because the phone number is theirs.
My phone is unlocked and I use it on Personal in Argentina. I've used this phone for years and this only started happening last Thursday out of nowhere. No new apps, no system upgrade.
Rebooting the phone doesn't help either, and I wouldn't want to factory reset if it can be avoided. Any ideas what this might be?
Thanks!
same, just today noticed this on an older LG G4
Alert Message - Same thing here...
Same thing here have had Moto E4 Plus on Metro PCS for the last few years and just started receiving this message in the last week. The phone was a Verizon phone that I unlocked and has been working great on Metro...until now. What's going on?
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
bump
Greenguru said:
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
Click to expand...
Click to collapse
bump...
Same here on my note 4, using T-mo prepaid. Just started a week ago. Also the verizon splash screen still displays on power up. My understanding is the V boot loader is locked.
Greenguru said:
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
Click to expand...
Click to collapse
SOLVED I had the same problem as well but I found a way to get rid of it, you gotta disable the My Verizon app and then 1 settings then mobile networks then network mode and set the global off to LTE/GSM/UMTS and then it will not pop up anymore, your welcome.
by Myles Tecomba
Good news, I found the locations since I don't have "my verizon apps" Bad news, the fix does NOT work at all.
Solved
I actually got online with Motorola because I knew that the app causing this nightmare was Verizon Login . The problem is that I debloated all my Verizon and the problem still occurred. But then by going through Settings | Apps | ... |Show System, I say the bugger was still there. I disabled it and the problem was solved. Of course this worked for me because I'm on an unblocked phone and note using Verizon.
My husbands Samsung Galaxy S7 has been doing this for over a month. He tried disabling anything Verizon related and even a factory reset and it's still doing it.
XCutecakeX said:
My husbands Samsung Galaxy S7 has been doing this for over a month. He tried disabling anything Verizon related and even a factory reset and it's still doing it.
Click to expand...
Click to collapse
Yes, I did same with my note 4, still there. IGNORE those solved posts, this problem is NOT solved. I use T-mobile prepaid with this phone and since verizon locks the boot loader, there is not yet a rooting solution for this phone and since it's a note 4 there will not be one forthcoming.
fixed it permanently
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
In addition, disable permissions of My Verizon: SMS, phone and GPS location, your welcome
gobearsltl said:
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
Click to expand...
Click to collapse
So I have an old Verizon tablet that is running android 5.1.1. I don't have options for "show system" or "Verizon login" that I can find. Anybody familiar with this 5.1.1 that knows where it would be or if I'm overlooking. Thanks.
Awesome! I'm using an unlocked Verizon LG G5 in Canada and I've been trying for quite some time to get rid of this problem. I've tried all the suggested fixes I could find on the net and this is the solution! Thanks so much buddy. Much appreciated eh!
This problem started recently for me on Samsung S6 unlocked Verizon phone that I use with foreign SIM cards when traveling. I tried restoring settings to default, but that didn't work. Then I tried resetting network settings and that appears to have worked. it was popping up every couple minutes and so far it has not.
don't work
i know this is a old post but i changed the network it didnt fix it it made me not have signal and still popped up so i had to change it back to global and its still doing it , it only started last month i have a s6 unlocked verzion its so annoying
Solved - BIG TIME!!
joshswife1992 said:
i know this is a old post but i changed the network it didnt fix it it made me not have signal and still popped up so i had to change it back to global and its still doing it , it only started last month i have a s6 unlocked verzion its so annoying
Click to expand...
Click to collapse
I had the same problem on my unlocked S6 Edge and knew that the Verizon Login app was the issue but the damn phone wouldn't let me disable it; grayed out. I bought an app in the Play Store named "Package Disabler Pro (Samsung)" for $2.99. The thing will let you disable ANY software whether built in or not. So once you launch, disable Verizon Login with it and the problem is gone. If you disable "Setup Wizard", you also won't get the stupid message about the SIM not being VZW card when you boot. I disabled all the other Verizon software too. Problem was so aggravating that I got an account here just to share the answer since I figure it has to be driving people CRAZY!!!!
- Bob
Help!!!
Still having this issue, I’ve disabled all those apps, force stopped them, and it continues to haunt the phone. I’ve called Verizon and they don’t know anything about it, and I’m really about to throw the phone away and buy a new one. It’s an s7 so it’s still a decent phone, but I don’t know what else to do
So Close, but Disable is Disabled
gobearsltl said:
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
Click to expand...
Click to collapse
This definitely got me closer. Using this method I was able to revoke permissions which forces VZ SpyLogin to fail so it isn't running, BUT, the "Disable" button is disabled, even if I force stop the app. It's most certainly this application causing the issue. Thanks for the closest solution.
**EXTRA info
This wasn't happening at all on my phone ever, and this is an old one (I need the IR blaster in the Samsung G6). It's an unlocked Verizon branded phone running on ATT network. I factory reset it yesterday and now I am getting this annoying Verizon Login nonsense.
Let me preface this with this issue began with the February security update. I cannot say for certain that they are related, however it’s difficult to believe that they are not. Tuesday after installing the February security update my phone and lost the ability to connect to Tmobile’s data network. It can still call, text, send MMS, and run speed tests. I’ve been working with one of the engineers at Tmobile corporate in Bellevue Washington. They have gone above and beyond looking at the switch, refreshing my account By suspending and reactivating it. They have had my Sim card swapped multiple times. When I put my Sim card into my old phone I have data connectivity like normal. Does anybody hear have any insight or anything to try on a pixel five to possibly undo whatever the February security update did.
Update. Best Buy replaced the phone outside of normal warranty. As soon as it got the February security update the problem is back.
Clear system cache.
Do a network reset.
Double check all related settings.
Now you know why I don't update...
blackhawk said:
Clear system cache.
Do a network reset.
Double check all related settings.
Now you know why I don't update...
Click to expand...
Click to collapse
Done, done, and done. This is phone number 2 now. Problem does not follow my sim. Works fine in iphone 10s and a Samsung Note 20.
b0gman said:
Done, done, and done. This is phone number 2 now. Problem does not follow my sim. Works fine in iphone 10s and a Samsung Note 20.
Click to expand...
Click to collapse
Ouch. That sucks.
Try a factory reset if you haven't.
Most likely it was the update.
If a reload doesn't get it, reflash the firmware.
It may be a hardware failure if a reflash to the last known good rom doesn't get it.
blackhawk said:
Ouch. That sucks.
Try a factory reset if you haven't.
Most likely it was the update.
If a reload doesn't get it, reflash the firmware.
It may be a hardware failure if a reflash to the last known good rom doesn't get it.
Click to expand...
Click to collapse
Don't have time for any of that anymore sadly. Best buy does kick ass they swapped me into a S20 FE. Did get an email from google acknowledging that this is a known bug since January.
Go into settings and check your APN settings. I had to delete one and switch to another to get my data working again.