Related
My 6t is arriving tomorrow and I'm hoping when I pop my Sim in everything will work. But sounds like most people are having to call Verizon.
My question is, for those of you who've done this successfully, what did you ask Verizon to do? Sounds like most of the techs don't really know about this phone so I wanted to see if there were any key words or phrases to try and get everything working.
I did online chat. Explained that I had rebooted, factory reset, deleted app cache and cache partition. They sent me to tier 2 (actually had to call). On hold there now. Told them all my trouble shooting and told them that I needed CDMA-less provisioning. He said that sounded right and is supposed to be working on it now. It's taking forever though.
natypes said:
I did online chat. Explained that I had rebooted, factory reset, deleted app cache and cache partition. They sent me to tier 2 (actually had to call). On hold there now. Told them all my trouble shooting and told them that I needed CDMA-less provisioning. He said that sounded right and is supposed to be working on it now. It's taking forever though.
Click to expand...
Click to collapse
I've seen some people say that they dialed into the phone info and set network type as LTE only and it worked. Did you try that??
No, but I need to. They told me it would be fixed in 3 business days.
Well currently I'm on v20 RN mine 6t will be here tomorrow...hope it work right out box without issue but if not then got to fight with verizon :'))
Textra isn't working either. Any suggestions for 3 days until they get it fixed? My Pixel 2 XL is on swappa and my Pixel 3 XL needs to go back to Google for refund.
natypes said:
Textra isn't working either. Any suggestions for 3 days until they get it fixed? My Pixel 2 XL is on swappa and my Pixel 3 XL needs to go back to Google for refund.
Click to expand...
Click to collapse
What exactly isn't working with Textra? Is it just because of the issues with SMS through Verizon or is there a problem specific to the app?
So what exactly is the issue ? Do I need CDMA- less provisioning ? Or for it to be removed?
handman29 said:
So what exactly is the issue ? Do I need CDMA- less provisioning ? Or for it to be removed?
Click to expand...
Click to collapse
Most of the issues is one plus screwed up. They never gave vzw imei #'s for their Network. Either that, or vzw screwed up, and just didn't do it. Here I have a non working phone, and I'm supposed to wait up to 3 days, for Verizon to HOPEFULLY enter my imei into the system. Not happening, I am sending phone back. What a disaster. I wonder why I'm still on vzw. Nothing but headaches.
Here it is in a nutshell:
The 6T only supports LTE on Verizon's network. Verizon still uses CDMA for things like SMS on most phones. In order for their systems to use LTE for your SMS messages you have to have the "CDMA_LESS" provision added to your SIM card. In order to do this your phone must be registered correctly as a "ONEPLUS 6T" in their systems. It seems that either Verizon or Oneplus goofed and not all 6T's are in their system. If you phone registers as a generic device, they will not be able to add the "CDMA_LESS" provisioning.
For some, like myself, it was a simple call to tech support to add the CDMA_LESS provisioning since my phone registered properly on their network as a "ONEPLUS 6T 8/128". Those who's 6T's do not register properly due to their IMEI not being in Verizon's database will have to wait for it to be added.
clabern said:
Here it is in a nutshell:
The 6T only supports LTE on Verizon's network. Verizon still uses CDMA for things like SMS on most phones. In order for their systems to use LTE for your SMS messages you have to have the "CDMA_LESS" provision added to your SIM card. In order to do this your phone must be registered correctly as a "ONEPLUS 6T" in their systems. It seems that either Verizon or Oneplus goofed and not all 6T's are in their system. If you phone registers as a generic device, they will not be able to add the "CDMA_LESS" provisioning.
For some, like myself, it was a simple call to tech support to add the CDMA_LESS provisioning since my phone registered properly on their network as a "ONEPLUS 6T 8/128". Those who's 6T's do not register properly due to their IMEI not being in Verizon's database will have to wait for it to be added.
Click to expand...
Click to collapse
Unfortunately we are at their mercy. Alot of Imei number will get lost in the shuffle. I am just returning my 6t. Not worth the aggravation.
What happens when you go back to another phone with CDMA? Do you lose the provisions for it forever or do you gain access back?
Sent from my SM-N960U1 using Tapatalk
Verizon will be shutting down their CDMA network sometime in 2019. So in a year, this won't be an issue anymore.
oneandroidnut said:
What happens when you go back to another phone with CDMA? Do you lose the provisions for it forever or do you gain access back?
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
Well, cdma does dtill work, but texts will not work if you only have cdma. Calls do though.
Had the no sms issue on one of my lines called tech asked them to provision cdma less feature they did and within a few second all my texts started flooding in. Been using it all day with zero issues.
Ok here's what I did;
Switch the verizon Sim to sim2 slot.
Call Verizon at 8009220204
Get to customer service option
Tell them about the sms issue and have them add cdma_less option
They will add in 5mins, then they will send sms to test.
All works now. Also, the visual voicemail is intergrated into phone app. No more another app like in Samsung.
Sent from my ONEPLUS A6013 using Tapatalk
I contacted Verizon today and told them "about the sms issue and have them add cdma_less option" like previously posted. She flipped the switch and had me reboot. Texts are working perfectly. Pretty easy fix. As always thanks for the info.
Had zero issues, followed the portion of the article here like a normal upgrade
https://www.droid-life.com/2018/11/06/oneplus-6t-verizon-sms-issues/
"My Verizon>My Device>Activate or Switch Device>Activate On an Existing Line"
punched my 6T imei in, swapped sim from note 9 into 6T and sms/mms sending and receiving working and over 100 mbps on first speedtest! Needless to say I am pretty happy so far!
Yamvmax1 said:
Unfortunately we are at their mercy. Alot of Imei number will get lost in the shuffle. I am just returning my 6t. Not worth the aggravation.
Click to expand...
Click to collapse
Seems I found an easy solution - I enrolled in Verizon Integrated Messaging. After 3 day's I got an SMS (and before that SMS did not work!) :
ZW Free Msg: Welcome to Integrated Messaging! Starting now, your messages will be synced across your Verizon Messages devices-including phone, web & tablet access! Visit www.vzw.com/vzmessages for more info.
And all SMS started to work over LTE!
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]
So I saw an article they were doing an official RCS rollout for Android messages...went and checked my settings today and enabled the chat features/RCS...I check back in the app later and RCS is turned off and the option to enable RCS is no longer there. I tried clearing the carrier services data and force stopping Messages...I was able to turn RCS back on, but then it disappeared again shortly after. I'm in the U.S. on T-mobile using the most recent Android 9 version. Anyone else experiencing a similar issue?
Those issues are universal. It doesn't work well. It seems to stick for me since A10 update.
I don't see the point for now if this as it's only working from Google message to Google message. And everybody has another internet messaging system like WhatsApp or whatever.
It's 5 years too late to have a chance to prevail
Mine says...
"Chat Features unavailable for this device. Your carrier does not currently support this feature."
ojsimpsonn said:
So I saw an article they were doing an official RCS rollout for Android messages...went and checked my settings today and enabled the chat features/RCS...I check back in the app later and RCS is turned off and the option to enable RCS is no longer there. I tried clearing the carrier services data and force stopping Messages...I was able to turn RCS back on, but then it disappeared again shortly after. I'm in the U.S. on T-mobile using the most recent Android 9 version. Anyone else experiencing a similar issue?
Click to expand...
Click to collapse
Scott said:
Mine says...
"Chat Features unavailable for this device. Your carrier does not currently support this feature."
Click to expand...
Click to collapse
I tried this trick here https://www.google.com/amp/s/www.androidcentral.com/how-enable-rcs-chat-features-google-messages?amp
It worked for me
Since the roll out I haven't needed that trick anymore
PapaMag said:
Since the roll out I haven't needed that trick anymore
Click to expand...
Click to collapse
Yeah, I hear you but it still doesn't work for some devices or people outside of the US!
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.
Just wondering if anyone was ever able to get wifi calling feature to work on Verizon? Reps keep saying since its basically not a phone from/through them it wont....but 2 weeks ago had the 6t on Tmobile and it worked(had the option in settings to enable/disable). On verizon there is no option like that in settings, just an option to tick on or off for VoLTE services
fosgate24360 said:
Just wondering if anyone was ever able to get wifi calling feature to work on Verizon? Reps keep saying since its basically not a phone from/through them it wont....but 2 weeks ago had the 6t on Tmobile and it worked(had the option in settings to enable/disable). On verizon there is no option like that in settings, just an option to tick on or off for VoLTE services
Click to expand...
Click to collapse
Guess I should of mentioned Im on Pixen rom(android 10 version)