Related
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
im betting that is what my issue is, can you give me the settings so I can make this apn?
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 leak and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
BarryH_GEG said:
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
Click to expand...
Click to collapse
Yes. This is what started me on his quest lol. My s voice has been working and then quit which rendered the watch pointless. So I have been trying to fix it for a few days now
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
raiu said:
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
Click to expand...
Click to collapse
It's an odd problem and not easy to isolate. When S Voice first died I thought it was related to the S Voice app itself. I tried the SGS5 update in your link right before the problem started and thought that was it. So I cleared data in the app via Settings and went back to the factory version and the N3-specific S Voice update that came out a few months ago. Didn't solve the problem - S Voice was fine over Wi-Fi but borked on AT&T data.
I remembered I was in a VoLTE market and tried the nxtgenphone APN and that solved the problem. All three versions of S Voice worked; original, N3 update, and SGS5 update. Everything was fine until I had to use the "phone" APN in a non-VoLTE market. S Voice worked fine until I got home to my VoLTE market and it stopped working again. This time, the nxtgenphone APN didn't help. I cleared data on S Voice again and tried all three versions and S Voice still wouldn't work.
Thinking it might be Gear related I deleted the Gear from BT settings, uninstalled Gear Manager from my phone, hard reset my Gear by long pressing the power button and using recovery, and rebuilding it via reset rather than using "restore" to reinstall my previous apps/settings. For some reason, the original and N3 update of S Voice wouldn't work. The SGS5 version did. At some point in the second "S Voice is broken" repair S Voice started to work on my phone but not the Gear.
So some combination of playing with the APN's, installing different versions of S Voice, and resetting the Gear, S Voice is working reliably again. What a pain in the ass. I'm guessing it's AT&T network related because its the only common denominator in both times S Voice started to fail and using the nxtgenphone APN fixed it the first time.
Same issue here (Samsung Note 3), ATT & Samsung are clueless
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Avi-J said:
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Click to expand...
Click to collapse
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
raiu said:
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
Click to expand...
Click to collapse
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
BarryH_GEG said:
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
Click to expand...
Click to collapse
mine works with the s5 svoice app update
raiu said:
mine works with the s5 svoice app update
Click to expand...
Click to collapse
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
BarryH_GEG said:
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
Click to expand...
Click to collapse
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
raiu said:
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
Click to expand...
Click to collapse
Thanks for that. I saw the security update yesterday but didn't think it would solve the problem so didn't play with S Voice after I installed it. AT&T must have done something security permissions wise on their network otherwise all carriers would have had S Voice issues which we know isn't the case. The S Voice app in Galaxy Apps is the one and only update the N3 received in January so that's not what fixed the problem.
Is hotspot/tethering option missing on all us carrier in the settings I'm using sprint version & it's not here at all...this phone is useless 2 me if I can't find a way to fix this.
https://www.xda-developers.com/thre...ickbaity-tricks-for-your-new-galaxy-s8-or-s8/
Hey man did this work? I haven't gotten my S8 in the mail yet so I can't test it...
Mobile Hotspot and Tethering is available on the T-Mobile version by default, both in the settings menu and in quick launch
I have the verizon model and the hotspot option is available and working. Was not hidden.
Available in the settings and quick settings in the AT&T S8
ITNV said:
Available in the settings and quick settings in the AT&T S8
Click to expand...
Click to collapse
This was a pleasant surprise for me, since AT&T had it removed from the quick settings on my S6.
Tethering Switch
by the way, if you want a really good "Hotspot Widget" that ACTUALLY works...and I literally tried probably 90% on the Play store and ONE did finally work...
Tethering Switch
https://play.google.com/store/apps/details?id=jp.gr.java_conf.taketake.tethering&hl=en
DID work. It doesn't bring you to the HotSpot Settings first, and then you would have to turn on the HotSpot manually...this does it quickly, shows that it is enabled.
...
thevirgonian said:
https://www.xda-developers.com/thre...ickbaity-tricks-for-your-new-galaxy-s8-or-s8/
Click to expand...
Click to collapse
thevirgonian said:
by the way, if you want a really good "Hotspot Widget" that ACTUALLY works...and I literally tried probably 90% on the Play store and ONE did finally work...
Tethering Switch
https://play.google.com/store/apps/details?id=jp.gr.java_conf.taketake.tethering&hl=en
DID work. It doesn't bring you to the HotSpot Settings first, and then you would have to turn on the HotSpot manually...this does it quickly, shows that it is enabled.
Click to expand...
Click to collapse
This didn't work for me the link, the missing hotspot seems to be a sprint thing are you using sprint?
thevirgonian said:
by the way, if you want a really good "Hotspot Widget" that ACTUALLY works...and I literally tried probably 90% on the Play store and ONE did finally work...
Tethering Switch
https://play.google.com/store/apps/details?id=jp.gr.java_conf.taketake.tethering&hl=en
DID work. It doesn't bring you to the HotSpot Settings first, and then you would have to turn on the HotSpot manually...this does it quickly, shows that it is enabled.
Click to expand...
Click to collapse
I tried this but didn't work for me with AT&T. I have a Tethering shorcut, but it takes you to the hotspot settings to turn it on manually like you mentioned. So I was excited to try this app out, however after I installed it, it just says it's Enabled (but it's not) and then when I tap it again it says Enabled again, not Disabled. Unless I go into my settings and turn it on, then the app will say Disabled (but doesn't really). So I guess I'll stick with what I have for now.
Hey I ended up returning my S8. I apologise for putting this info out about the Tethering app. It works perfectly on all my other ROMS. It is the only "widget" type app that worked on my LG G5 on stock rooted FW on MM. Anyway, I am not sure if you guys got Tethering to work on Verizon or whatever, but I had no issues with it on T-Mobile... However this app didn't work on T-Mobile on my S8 even.
Buy from Samsung?
Daddy43205 said:
Is hotspot/tethering option missing on all us carrier in the settings I'm using sprint version & it's not here at all...this phone is useless 2 me if I can't find a way to fix this.
Click to expand...
Click to collapse
You didn't by any chance purchase the phone directly from Samsung did you? I had the exact same problem with an S8 purchased directly from Samsung (got the free Gear VR promo) and I have Sprint.
There was no hotspot option anywhere in the setup menus. And of course, I did not notice this until 2 weeks later when I was on a trip. The hotel WiFi was messed up and I needed to use hotspot. It's not that it did not work, there was no option at all in Setup for Hotspot and Tethering.
I talked to Sprint, took it to a Sprint store for help, and talked to Samsung tech support. Nothing they all tried fixed it. Both Sprint and Samsung suggested the phone might be defective and I should pursue getting a replacement. That didn't make sense to me because WiFi and Cell Data were working fine, and hotspot is just software.
My fix was to do a full Factory Reset and then set it all up again. Tedious, but when it came back up, the Hotspot and Tethering option were there and it works perfectly now.
Recent update messed it up again?
Tried the adb method of Get/Push revealing Hotspot via Quick Tiles. Didn't work.
Any other ideas for regaining hotspot on the device? Without rooting?
Current date: Jan 7 2018.
i have same problem too, waiting for update
I tried that https://www.xda-developers.com/thre...ickbaity-tricks-for-your-new-galaxy-s8-or-s8/ but I cant even try itcoz I get "because an app etc about some permission", I tried to disable so many cant figure it out
So how does one Quick Toggle Tether? I use it all the time in my car
Hi, I have Verizon and after updating to Android 10 today (official Verizon OTA update), when I check the SIM status it will sometimes say "Sprint". It'll also sometimes say "Sprint" when I swipe down from top and look in upper right hand corner. Has anyone seen this? Any idea why? SIM card came from Verizon when I switched over from Sprint to VzW a number of months ago.
Thanks.
ayoldguy1 said:
Hi, I have Verizon and after updating to Android 10 today (official Verizon OTA update), when I check the SIM status it will sometimes say "Sprint". It'll also sometimes say "Sprint" when I swipe down from top and look in upper right hand corner. Has anyone seen this? Any idea why? SIM card came from Verizon when I switched over from Sprint to VzW a number of months ago.
Thanks.
Click to expand...
Click to collapse
When you switched to Verizon, were you still just accepting OTAs? It kinda sounds like you still getting Sprint OTAs.
I bought a used Sprint phone, then fastboot flashed the Essential image, which prompts for the Essential OTA.
Same. When I look up Mobile network in settings it shows Verizon, but when I look from pulldown notification, it says Sprint. Tried network reset and no change.
ktmom said:
When you switched to Verizon, were you still just accepting OTAs? It kinda sounds like you still getting Sprint OTAs.
I bought a used Sprint phone, then fastboot flashed the Essential image, which prompts for the Essential OTA.
Click to expand...
Click to collapse
I was just accepting OTAs. But the SIM is a Verizon SIM? Also, it seems like I have data and can make calls... how is that possible? I've gotten OTAs before (Android Pie) and didn't have this issue.
dark_isz said:
Same. When I look up Mobile network in settings it shows Verizon, but when I look from pulldown notification, it says Sprint. Tried network reset and no change.
Click to expand...
Click to collapse
Do you feel that you're actually using the Sprint network? I can't see hotspot toggle anymore in Settings, I can't see a way to navigate there.
I'm the same but I feel I'm on Verizon network and not Sprint. APN says Sprint though. As long as I use Verizon Messages app, MMS/SMS work fine though. 4G and calls work fine.
If you (y'all) go to the APN settings (settings -> Network & Internet -> Mobile Network -> Advanced -> Access Point Names), are they Verizon? Have you looked up the Verizon APNs and compared to what you have?
I'm having the same exact issue. Before update, all APNs were Verizon. Post update, they'll be Verizon at first then randomly change to being all of Sprint's... How weird.
Mobile Network says Verizon, APNs say Sprint, SIM status says Sprint, and Sprint's OMADM updates setting appears under about phone as well. For some reason, the phone states its brand as Sprint too, even though the device is unlocked.
jffwarner0 said:
I'm having the same exact issue. Before update, all APNs were Verizon. Post update, they'll be Verizon at first then randomly change to being all of Sprint's... How weird.
Mobile Network says Verizon, APNs say Sprint, SIM status says Sprint, and Sprint's OMADM updates setting appears under about phone as well.
Click to expand...
Click to collapse
When the phone was switched off of Sprint's network into Verizon's, was the firmware switched from the Sprint dedicated releases to the Essential generic release? Basically you'd have to fastboot flashed a factory image downloaded from Essential's developer page.
I'm not saying this definitely fixes the problem, but the Sprint phones have firmware specific to them.
ktmom said:
When the phone was switched off of Sprint's network into Verizon's, was the firmware switched from the Sprint dedicated releases to the Essential generic release? Basically you'd have to fastboot flashed a factory image downloaded from Essential's developer page.
I'm not saying this definitely fixes the problem, but the Sprint phones have firmware specific to them.
Click to expand...
Click to collapse
This one was never on Sprint's network. Maybe mine just got the wrong Android 10 OTA pushed to it then? I'm assuming a factory reset will probably be my only hope then.
jffwarner0 said:
This one was never on Sprint's network. Maybe mine just got the wrong Android 10 OTA pushed to it then? I'm assuming a factory reset will probably be my only hope then.
Click to expand...
Click to collapse
No, I doubt that the wrong releases got pushed. It dawns on me that I haven't been seeing separate images on Essential for the Sprint, and everyone else for at least a year. Maybe they merged the releases and something in the build prop is whacked.
ktmom said:
No, I doubt that the wrong releases got pushed. It dawns on me that I haven't been seeing separate images on Essential for the Sprint, and everyone else for at least a year. Maybe they merged the releases and something in the build prop is whacked.
Click to expand...
Click to collapse
So I guess I'll have to wait for the October OTA. Fun times.
Are you using the latest version too?
jffwarner0 said:
So I guess I'll have to wait for the October OTA. Fun times.
Are you using the latest version too?
Click to expand...
Click to collapse
No [emoji854] it's my daily driver, rooted with a few mods. I typically wait until the release after a major version upgrade to do the upgrade. That gives me time to see if there are problems that will affect my use case.
ktmom said:
No [emoji854] it's my daily driver, rooted with a few mods. I typically wait until the release after a major version upgrade to do the upgrade. That gives me time to see if there are problems that will affect my use case.
Click to expand...
Click to collapse
That's what I typically do too. I saw that this was the second one for 10 put out, so I figured I was all good. Especially since the subreddit had been positive all of yesterday about it. I'm now wishing I could revert back without losing my settings, non-play store apps, and data.
jffwarner0 said:
That's what I typically do too. I saw that this was the second one for 10 put out, so I figured I was all good. Especially since the subreddit had been positive all of yesterday about it. I'm now wishing I could revert back without losing my settings, non-play store apps, and data.
Click to expand...
Click to collapse
It's the first of the "stable" releases. Everything else has been beta releases.
ktmom said:
It's the first of the "stable" releases. Everything else has been beta releases.
Click to expand...
Click to collapse
It is? I could've sworn I had one pop-up before this one and this one was being billed as a "hotfix" for service issues from the first "stable" release. Oh well, guess I get Sprint service speeds for a month.
Also having same issue
Hi, all. I'm so happy I found this thread. I have an Essential that was purchased from Sprint and unlocked immediately in November of 2017. It has worked almost flawlessly since on Verizon (lousy battery life some months and some odd camera stuff going on here and there).
I have always taken the OTA updates and never had an issues. I took the Android 10 update as soon as it showed available in September. A few days later my phone was showing "roaming". I reset it a few times, pulled the SIM, etc. and got it working again but the SIM continued to show Sprint. A few more restarts and it showed Verizon.
This kept happening every few days. A few restarts and it was back on Verizon. I even had the Verizon store put a new SIM in when restarts weren't fixing it.
Now I am stuck in Sprint mode for several weeks and cannot get it back on Verizon.
The issue is you cannot send/receive MMS when in Sprint mode AND I cannot receive voicemails.
I am no longer up for flashing firmware, etc. I got that out of my system years ago and just want phones that work and don't cost a fortune. I'm hoping I can recover this thing without major surgery, because my old Moto G4 is a really bad phone at this stage in its life. I finally switched last week when my wife got mad that I wasn't responding to her MMS messages. First time I plugged the Moto into my car, Android Auto nearly killed it! LOL
Is there a fix for this? I can't live without MMS (or rather, my colleagues and family can't) so I may have to buy a Pixel soon.
Thanks!
mkempton said:
Hi, all. I'm so happy I found this thread. I have an Essential that was purchased from Sprint and unlocked immediately in November of 2017. It has worked almost flawlessly since on Verizon (lousy battery life some months and some odd camera stuff going on here and there).
I have always taken the OTA updates and never had an issues. I took the Android 10 update as soon as it showed available in September. A few days later my phone was showing "roaming". I reset it a few times, pulled the SIM, etc. and got it working again but the SIM continued to show Sprint. A few more restarts and it showed Verizon.
This kept happening every few days. A few restarts and it was back on Verizon. I even had the Verizon store put a new SIM in when restarts weren't fixing it.
Now I am stuck in Sprint mode for several weeks and cannot get it back on Verizon.
The issue is you cannot send/receive MMS when in Sprint mode AND I cannot receive voicemails.
I am no longer up for flashing firmware, etc. I got that out of my system years ago and just want phones that work and don't cost a fortune. I'm hoping I can recover this thing without major surgery, because my old Moto G4 is a really bad phone at this stage in its life. I finally switched last week when my wife got mad that I wasn't responding to her MMS messages. First time I plugged the Moto into my car, Android Auto nearly killed it! LOL
Is there a fix for this? I can't live without MMS (or rather, my colleagues and family can't) so I may have to buy a Pixel soon.
Thanks!
Click to expand...
Click to collapse
Have you looked at the APN that is being used? Settings -> network & internet -> mobile network -> advanced -> all the way down
ktmom said:
Have you looked at the APN that is being used? Settings -> network & internet -> mobile network -> advanced -> all the way down
Click to expand...
Click to collapse
Thanks for the quick reply.
"Mobile Network" in the primary menu shows Verizon, but the APNs look like Sprint names.
OTA
otasn
SPCS Global
cinet.spcs
Sprint
sprint
Sprint MMS
n.ispsn
mkempton said:
Thanks for the quick reply.
"Mobile Network" in the primary menu shows Verizon, but the APNs look like Sprint names.
OTA
otasn
SPCS Global
cinet.spcs
Sprint
sprint
Sprint MMS
n.ispsn
Click to expand...
Click to collapse
Look up the correct APNs for Verizon and create the correct ones. Once they work, delete the sprint ones.
Edit:
I know you said your over the days of flashing, but I think I would sideload the first A10 OTA from Essential's Developer's site. You can do that in stock recovery, just using ADB.
Hopefully that will get you off the Sprint software. It's what I did back when I got a sprint version (used). I always start with the first release of the current version on the device. Often the first major release has specific stuff that doesn't get passed on in future updates. Or, that may just show how old school I am [emoji4]
Has anyone gotten RCS officially activated by Google, not the manual hack using action launcher?
I never got around to manually activating RCS and now I'm curious how quickly it's actually rolling out
atlp99 said:
Has anyone gotten RCS officially activated by Google, not the manual hack using action launcher?
I never got around to manually activating RCS and now I'm curious how quickly it's actually rolling out
Click to expand...
Click to collapse
I had mind activated through the hack. When I saw it was officially rolling out I uninstalled messages and reversed the hack. When I reinstalled messages the option wasn't there.
I chose not to bother with the work around option. But yesterday, my wife and I both received the RCS activation notification in our Messages apps. I enabled it on both phones and it's been working flawlessly.
FWIW, We both have Unlocked Pixel 4's and we're using them on T-Mobile.
Still waiting. Unlocked on Verizon
Got it working using the hack. Reversed it and am still waiting for the official rollout. Unlocked, Verizon.
So I was rooting my Google store bought pixel 4 and missed a step. Needless to say I had to sideload a full ota to recover it. But I'm pretty sure I accidentally loaded the verzion version. I got all the verizon apps that showed up when I rebooted the phone. I went back and wiped everything in recovery mode and tried sideloading QD1A.190821.007.A3 and it keeps erroring out. This is the firmware that Im 90% sure what was on my phone. Is there a way to get back to factory google store firmware or am I screwed now? I am on a verizon sim but phone was bought on launch day from the google store. Its also noted that I am currently on QD1A.190821.014 firmware. This doesn't appear to be the verizon firmware.
The Verizon apps appear not based on which ROM version you load, but instead based on whether you have a Verizon SIM in the phone during setup.
If you loaded the wrong ROM onto the phone, you may not be able to recover by sideloading an OTA. You should be able to recover by doing a complete reflash of the image you want (the image version, not the OTA version).
What error is it giving you?
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
BubbaGumprc said:
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
Click to expand...
Click to collapse
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Jon8RFC said:
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Click to expand...
Click to collapse
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
bobby janow said:
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
Click to expand...
Click to collapse
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Jon8RFC said:
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Click to expand...
Click to collapse
My wife has a Verizon device Pixel 3 locked bl and I have a Pixel 4 and they both have MVS disabled and both can call on wifi. I just tested again to make sure. Really, I'm the only one? Gotta love that. I hate that they can get into my device without my knowing and see what and when I installed stuff.