Related
I'm gonna make a post here since NOTHING seems to be working. I'm a T-Mobile customer. Yesterday, I purchased a great condition nexus 6P from someone because my LG G5 is cracked and I was getting tired of it anyway so I opted to just buy a nexus instead of using my insurance on that phone. Everything is all good except for one major issue. VOLTE and WiFi calling just refuse to work with my sim in the Nexus.
I've called T-Mobile twice. I've factory reset from back up and reset settings twice. I've hard reset from stock recovery once. I've wiped network settings and restored default apns. I've manually changed the apns from what I see on Google, reddit and here. I've copied my apns from my LG G5 where VOLTE and wifi calling work perfectly fine. I've cleared cache. I've cleared the cache of the project fi and hangouts apps just in case there's something left over from the previous owner. I've gone into the *#*#4636 menu and tried a bunch of different stuff several times but no matter what I absolutely can not get wifi calling or VOLTE to work with TMobile on my nexus 6P. LTE it's self works perfectly fine for data.
Yes, all settings for wifi calling and enhanced LTE calling and VOLTE are turned on lol. I've tried the trick where you toggle wifi preferred on and off and restart the phone. Nothing happens. I don't even get a wifi calling reg error. It never shows as active in the data toggle in the quick settings are nor the status bar or dialer. It just isn't active. Same for VOLTE. I AM getting band 12. I can see it in the LTE discovery app. VOLTE just isn't working though. Whenever I make a call I can see LTE switching off and it switches to HSPA therefore making calls really difficult in my shoddy signal area at my house which is why I really need it to work.
I'm fairly certain I can root and install a ROM which will fix these problems but I don't own a PC. . I thought MAYBE the previous owner had previously had the phone rooted and tinkered with something somewhere that may have messed something up but that doesn't appear to be the case. Bootloader is locked and recovery is stock.
Can anybody help and tell me what in the world is going on here? I don't want to have to sell this nexus and revert back to my cracked screen G5. I would just switch carriers but I still owe money on the G5 so I was just gonna ride it out til I payed it off.
O and one last thing, after scowling google and forums for hours on end yesterday and today I did see one post mentioning something about this stuff being related to IMS provisioning and settings which are tied to a phones IMEI on T-Mobile and not the sim card and how that person simply called T-Mobile and got a hold of wifi calling technical support who was clueless but created a ticket for him and within 72 hours the issue was resolved. OK well I did the same exact thing and they refuse to create a ticket for me because it's not a T-Mobile phone and because according to them they are not allowed to create a ticket because wifi calling works fine in my G5 and therefore it's the phone and not them or their network lol. What a crock. I'm willing to bet if I put the sim in another unlocked phone with 7.1.1 and wifi calling fully available that it isn't going to work either. There's some sort of communication error going on between the sim being in this phone and their network it appears.
Check these screenshots out. T-Mobile is clueless
http://imgur.com/5MuO34s
http://imgur.com/XVd8CdA
http://imgur.com/uUGN3ae
http://imgur.com/cfYxfqh
I can only suggest;
1) Find a PC and re-flash the latest factory images from Google. Both "fastboot flashing unlock" and "fastboot flashing lock" will wipe all data, so backup first. Also confirm it fully boots correctly after flashing before you re-lock the bootloader.
2) Get a new 3-in-1 SIMM from T-Mobile. You can use their web site to switch cards and give it 24 hours to be fully provisioned.
3) Confirm your E911 address is correct on T-Mobile's site and wait 24 hours after any changes for Wi-Fi calling to actually start working.
I HAVE THE SAME EXACT PROBLEM AS YOU POSTED!!! GONE THRU THE SAME PAIN. LOL I'll attempt the ticket thing to see if I get anywhere. Did you ever get it resolved?
EDIT:
My theory is that since the phone was used in Project FI, they specifically turn off this feature in the back end for the specific phones, by Imei or something since project FI uses T-Mobile as well.
EDIT 2:
they wont' create a ticket for me either. I guess I will just have to ride it out.
EDIT 3: I FIXED IT!! NEXUS 6P VOLTE AND WI-FI CALLING FIX T-MOBILE
I flashed back to android 6.0 Build#: MMB29N (I used the Nexus ToolKit 2.1.9: google it. BTW, your phone will be wiped, so backup first) VOLTE just started working with this version of android 6.0. Then I upgraded using the OTAs and now i'm on 7.1.1 build#: N4F260 with VOLTE and Wifi calling working as it should! I hope this helps someone out there!
For what it's worth, reverting to the build you mentioned fixed it for me on my two Nexus phones coming from Project Fi to T-Mobile as well! Thanks for the help!
You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.
banancanard said:
You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.
Click to expand...
Click to collapse
wish I had seen this sooner. cheers!
Had the exact same issue and this fix worked for me. Wasted a couple of hours with T-mobile (they were actually very helpful and debugged everything on their end to confirm the provisioning was good) and then 2+ hours with Google support. Actually had already filed for a device replacement which I canceled after finding this post.
I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?
k2kevink2 said:
I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?
Click to expand...
Click to collapse
Flashing the radio -sadly- requires an unlocked bootloader.
Did you resolve your problem?
In android 7.1.2 did you notice in Set preferred network type is set at " LTE/GSM/CDMA auto (PRL) "? 7.1.2 has been giving me issues with sms/mms. I noticed Android 6.0 has this set to correct T-mobile bands.
All works for me in 7.1.2. Make sure you don't download the Verizon version of the stock ROM. That was my issue why I couldn't have volte and Wi-Fi calling
Neither on wifi nor cellular will it check for update. I get the error "sorry, we are having trouble authenticating your device"
Any idea how to fix this ?
wondering the same :/ anyone have anything?
see my post here. besides flashing the t-mobile ummm rom I guess over it, you won't be able to update. I've tried samsung and t-mobile and the only thing that will work besides that is to borrow a sim from a friend and use that... https://forum.xda-developers.com/galaxy-s8/help/best-buy-screw-t3594359/page2
try it today. it should work. the servers were having issues last night and this morning.
lotreaglesfan said:
try it today. it should work. the servers were having issues last night and this morning.
Click to expand...
Click to collapse
will not work because system updates are coming from carrier and having a tmobile sim in a verizon phone means verizon will not allow you to connect to their update server...
insomnia said:
will not work because system updates are coming from carrier and having a tmobile sim in a verizon phone means verizon will not allow you to connect to their update server...
Click to expand...
Click to collapse
Thats not the case. I am using vzw GS8 on att and I receive updates fine
Well I'm confused then. I was able to do the last update with a t-mobile Sim in the phone? Right now when I try checking for updates it errors out saying it couldn't be authenticated. Anyone have any clue?
Hope I can help you!
How to update your system if you're not using the carrier from your S8(+) version.
insomnia said:
Neither on wifi nor cellular will it check for update. I get the error "sorry, we are having trouble authenticating your device"
Any idea how to fix this ?
Click to expand...
Click to collapse
you wont be able to updated through wifi or LTE unless you use a verizon SIM but you can do it easily using your computer and samsung smart switch.
eoga said:
you wont be able to updated through wifi or LTE unless you use a verizon SIM but you can do it easily using your computer and samsung smart switch.
Click to expand...
Click to collapse
Are you able to update using your computer?
insomnia said:
Neither on wifi nor cellular will it check for update. I get the error "sorry, we are having trouble authenticating your device"
Any idea how to fix this ?
Click to expand...
Click to collapse
Try to get at least an inactivated Verizon sim card from any Verizon store or you can also try a normal working Verizon sim. I had AT&T Galaxy S5 and it needed the carrier's sim card to even check for update. I took the sim, put it in, checked for update and was able to install it.
Fix to your issue
Hey guys so I do also share the same situation, I have a Verizon s8+ yet I have T-Mobile One as my coverage
Because it's not authenticated as a Verizon provided account it simply won't update
Now.. the solution to updating isn't directly on your device.
It's within the Samsung Smart switch App for either Mac or windows, you can run an update through there with little to no problems at all and finally keep your device up to date without having to return it for an unlocked one.
Just a brief note regarding the smart switch App, keep in mind that sometimes the update will freeze at a certain percentage on the computer so just be sure to close the app out only if your Samsung device hasn't received the green upload screen yet.
Hopefully this helps out alot of you guys ?
Best regards
lotreaglesfan said:
see my post here. besides flashing the t-mobile ummm rom I guess over it, you won't be able to update. I've tried samsung and t-mobile and the only thing that will work besides that is to borrow a sim from a friend and use that... https://forum.xda-developers.com/galaxy-s8/help/best-buy-screw-t3594359/page2
Click to expand...
Click to collapse
I'd like to flash mine to t mobile, I'm begging you to help me with this!!!
Sent from my SM-G955U using Tapatalk
I've seen a bunch of info on the forums on how to flash the T-Mo ROM on an s8 - as well as flashing the Samsung Unlocked ROM on the s8 but frankly, almost all the threads are from back at the phone launch - and it is unclear to me which roms & programs to search for.
In a similar vein - I'm a noob to the whole process using oden - which I think is what i would need to use. I have experience from years ago running cyanogen mods on a nook tablet and messing with windows phones - but nothing recent and things have changed a lot.
I've read conflicting reports throughout the forums on doing this...
I'm running a VZW Branded (but it's now "unlocked")
Model: s8 SM-G-950U
Build #: NRD90M.G950USQS2BQL1
Baseband #: G950USQS2BQL1
What I'm looking for (really the right word is "NEED"):
Access to lower 700 A block (full band 12 use)
Ability to get OTA Updates
Mobile Hotspot Functionality
WiFi Calling
VoLTE
Bixby
If I could have these all running the Samsung Unlocked ROM - then that would be preferred...
If not - I would want to flash the T-Mobile ROM.
I need to know ASAP as I only have 14days from today (2/14/18) to figure this out or go back to VZW
Many thanks!
~chris
Hi, I just picked up on those Amazon Prime phones, LG V35 unlocked. I was sure it would work with project fi and even project fi said it would work. Well, it really does mostly work. I was able to activate it and do just about everything, but I noticed 2 things:
1. No option to enable wifi calling
2. No access to visual voicemail.
I figured I could just install the regular google phone app to gain access to those things, but the google phone app doesn't enable that stuff. And when you make a call, it appears to switch over the LG phone app.
I don't see why this shouldn't work with Project Fi, but I have no clue how to enable those things. Calling on Tmobile and sprint work, texts etc work, it's just those two things that don't work
Would really love to use this version since it's quite a bit cheaper than buying the Fi version.
bytemare said:
Hi, I just picked up on those Amazon Prime phones, LG V35 unlocked......
Click to expand...
Click to collapse
I don't have this device but, the following thread looks like the same/similar discussion than your question for the same device. It may be helpful for you.
https://forum.xda-developers.com/showthread.php?t=3813572
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Same exact situation here...times three. I bought three of them for family members hoping there would be some way to make the Amazon V35 fully-functional on Project Fi. No visual voicemail would be acceptable, but lack of wi-fi calling is a deal-breaker for me. Any idea if it's even possible to get that working on this phone?
Ironically, wi-fi calling IS installed on the phone (visible by viewing installed system apps), and when I am in an area *with* wi-fi but *without* cellular service, it is trying to connect to wi-fi calling but can't with an "ER081 - Unable to Connect" error.
Any options here?
Thanks much!
Thanks ! It looks like it's just a matter of removing a couple of the lg apps and replace them with Google apps, like the dialer. I don't know if this is even possible or not so I may just return the phone. It would seem like just replacing the dialer would make a big difference though....
bytemare said:
Thanks ! It looks like it's just a matter of removing a couple of the lg apps and replace them with Google apps, like the dialer. I don't know if this is even possible or not so I may just return the phone. It would seem like just replacing the dialer would make a big difference though....
Click to expand...
Click to collapse
I have the At&t V35 and I was able to install the Google Dialer directly from the Play Store. This is the first non Google device I've ever used that let me install the official Google Dialer from the Play Store. It really does make a big difference.
Can you remove the Amazon stuff?
Ok, so I made some project on this -- I got visual voicemail working. All I did was download the phone app, made it default for phone , gave it some permissions and I got all of my visual voicemail.
As for wifi calling, I can't get it to work. I downloaded google connectivity services (strangely, you can't search for it in the play store, but if you do a web search, you'll get a link to it in the play store), I gave it all permissions, etc, and actually I got ONE wifi call to work, but after that I just keep getting "ER081, Unable to connect." So wifi calling doesn't work and I'm not sure what the trick is to make it work. Everything else SEEMS to work, but since wifi calling doesn't work, I wonder if there is anything else that is broken that I'm not seeing.
I don't think you can remove the Amazon apps but they aren't intrusive at all. I got this on prime day and I'd keep it if I could get that wifi calling to work :/
How do I test Wi-Fi calling. Have the same V350ULM on verizon.
I have been playing with hidden settings but really don't know what I am not I am doing and seems like a lot of damage can be done in there using the "Nova Launcher" using the activities widget.
Warning: can really mess up the phone. Be careful and let me know what you find. I am also looking to enable video calling on Verizon.
Thank you
So I got this device from Amazon, and I've had nothing but issues with it.
Originally got it for Verizon, as it says on the Amazon page that it supports the Verizon network, which is partially true. I can make calls and texts and use data on the Verizon network, but literally don't get ANY of the advanced calling features, such as Premium voicemail, or WiFi calling, which is what I needed.
After looking into it, I determined that it was becuase it was an unlocked phone, and I am just not going to get those services to work on the Verizon network.
So my thinking was to switch carriers to Google Fi, since all they do is service unlocked phones. I got the SIM card yesterday, downloaded the Project Fi app, activated and ported over my number from Verizon. All seemed good, except as soon as I finished activation, I kept getting hit with this WiFi Calling Error: ER081 "Unable to Connect".
I first attempted to use only WiFi to do stuff on the phone. I turned on airplane mode, then turned on WiFi, and started testing. I first sent and received SMS and MMS using the standard Android Messages app, and that worked fine.
I then attempted to make a call, and it failed. The phone app wont even attempt to dial out, as it states that 'Airplane Mode' is enabled. That Error: ER081 keeps popping up.
I've been dealing with Project Fi support for the past 12+ hours now trying to figure this out, going through all the BS, they wanted me to install the Hangouts App and Hangouts Dialer, and that works over WiFi, so they were trying to say problem fixed (only if I use that app). That is not a solution.
Has anyone had any better luck with this device on any other carrier, with ALL advanced services and calling features functioning 100%?
I feel like this is a carrier service issue, and not a device hardware issue.
robdarftw said:
So I got this device from Amazon, and I've had nothing but issues with it.
Originally got it for Verizon, as it says on the Amazon page that it supports the Verizon network, which is partially true. I can make calls and texts and use data on the Verizon network, but literally don't get ANY of the advanced calling features, such as Premium voicemail, or WiFi calling, which is what I needed.
After looking into it, I determined that it was becuase it was an unlocked phone, and I am just not going to get those services to work on the Verizon network.
So my thinking was to switch carriers to Google Fi, since all they do is service unlocked phones. I got the SIM card yesterday, downloaded the Project Fi app, activated and ported over my number from Verizon. All seemed good, except as soon as I finished activation, I kept getting hit with this WiFi Calling Error: ER081 "Unable to Connect".
I first attempted to use only WiFi to do stuff on the phone. I turned on airplane mode, then turned on WiFi, and started testing. I first sent and received SMS and MMS using the standard Android Messages app, and that worked fine.
I then attempted to make a call, and it failed. The phone app wont even attempt to dial out, as it states that 'Airplane Mode' is enabled. That Error: ER081 keeps popping up.
I've been dealing with Project Fi support for the past 12+ hours now trying to figure this out, going through all the BS, they wanted me to install the Hangouts App and Hangouts Dialer, and that works over WiFi, so they were trying to say problem fixed (only if I use that app). That is not a solution.
Has anyone had any better luck with this device on any other carrier, with ALL advanced services and calling features functioning 100%?
I feel like this is a carrier service issue, and not a device hardware issue.
Click to expand...
Click to collapse
For me it worked if I reset the phone back to stock, and turned it off. Put the Fi SIM in, went through setup, installed the Fi APP, let it do it's config thing, THEN tried to make a call. For me it then worked on WiFi.
bytemare said:
Hi, I just picked up on those Amazon Prime phones, LG V35 unlocked. I was sure it would work with project fi and even project fi said it would work. Well, it really does mostly work. I was able to activate it and do just about everything, but I noticed 2 things:
1. No option to enable wifi calling
2. No access to visual voicemail.
I figured I could just install the regular google phone app to gain access to those things, but the google phone app doesn't enable that stuff. And when you make a call, it appears to switch over the LG phone app.
I don't see why this shouldn't work with Project Fi, but I have no clue how to enable those things. Calling on Tmobile and sprint work, texts etc work, it's just those two things that don't work
Would really love to use this version since it's quite a bit cheaper than buying the Fi version.
Click to expand...
Click to collapse
Man, I just bricked mine last night trying to flash Google Fi variant to my new phone ATT and I htink it has wifi calling on it sighhh...
Any one know how to unbrick it ? I've searched but so far it's only for the V20 or V30 but havn't seen one for V35 yet.
KennynGGG said:
Man, I just bricked mine last night trying to flash Google Fi variant to my new phone ATT and I htink it has wifi calling on it sighhh...
Any one know how to unbrick it ? I've searched but so far it's only for the V20 or V30 but havn't seen one for V35 yet.
Click to expand...
Click to collapse
KennynGGG, just want to confirm something. You flashed a ROM onto your LG V35 ThinQ? How did you unlock the bootloader - has some kind of exploit been discovered?
Toxeia said:
KennynGGG, just want to confirm something. You flashed a ROM onto your LG V35 ThinQ? How did you unlock the bootloader - has some kind of exploit been discovered?
Click to expand...
Click to collapse
I never got to that partt...using this tool I was able to dump then it bricked.
https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23
KennynGGG said:
I never got to that partt...using this tool I was able to dump then it bricked.
https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23
Click to expand...
Click to collapse
Well, being a noob and all I wasn't sure but are you saying that the bootloader has to be unlocked in order to flash any rom in cluding the same Rom Albeit different carrier ?
I just got me a V40 ThinQ thanks to Sprint. It's full of bloated stuffs though, I've never had a branded phone before or may be other company aren't as bad.
Anyway, I want to take a rom dump from the V40 and see if I can give my V35 a run before I send it in to LG for warranty repair. But when I tried uppercut to launch LGUP it still says the dll is out dated. I've tried it with my dll from V35 extraction. still not taking it. Any suggestion ?
KennynGGG said:
Well, being a noob and all I wasn't sure but are you saying that the bootloader.........
Click to expand...
Click to collapse
I don't have either devices but, Regarding the LG V40, the following area of the forum is specific to that device.
https://forum.xda-developers.com/forumdisplay.php?f=7911
The following thread is regarding the Debloating of the V40 as well.
https://forum.xda-developers.com/showthread.php?t=3857801
Regarding the V35, the following is the Enhanced Tag link that's specific to that device.
https://forum.xda-developers.com/t/lg-v35
I'm not sure which thread within the V35 ET would possibly fit what you're looking for but, you can always take a look and see if there's anything there that's helpful to you.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
I just finished flashing the Project Fi firmware to my Amazon V35 and it all went fine. Going to assume it's a simpler flash since the 2 are practically the same, even the firmware share the same version number. Before doing a factory wipe I tested WiFi calling by turning airplane mode on, wifi back on and made a call. Worked perfect. Did a factory reset on the phone to clear all the Amazon bloat and noticed that when the Project Fi app was activating service, it auto downloaded a sprint file/profile which I had never seen before.
I pulled the LGUP dll from the firmware and also modded it and LGUP for developer options. I only had to pick upgrade for it to work and was surprised how quick the flash actually was. I won't ramble anymore, but if anyone wants I can upload the modded dll and lgup exe that I used to flash.
metal409 said:
I just finished flashing the Project Fi firmware to my Amazon V35 and it all went fine. Going to assume it's a simpler flash since the 2 are practically the same, even the firmware share the same version number. Before doing a factory wipe I tested WiFi calling by turning airplane mode on, wifi back on and made a call. Worked perfect. Did a factory reset on the phone to clear all the Amazon bloat and noticed that when the Project Fi app was activating service, it auto downloaded a sprint file/profile which I had never seen before.
I pulled the LGUP dll from the firmware and also modded it and LGUP for developer options. I only had to pick upgrade for it to work and was surprised how quick the flash actually was. I won't ramble anymore, but if anyone wants I can upload the modded dll and lgup exe that I used to flash.[/QUOTE
I'd appreciate it if you could upload the moded LGUP Dev version....btw what version did you upgrade to ? and where did you download it from ?
Click to expand...
Click to collapse
KennynGGG said:
I'd appreciate it if you could upload the moded LGUP Dev version....btw what version did you upgrade to ? and where did you download it from ?
Click to expand...
Click to collapse
No problem, hopefully the zip file with the modded files is attached correctly to this reply. It's for LGUP 1.14
My phone was listed as V350ULM10f after the latest OTA update last month (I think it was just a security update). But that's the same version I used for the KDZ. I grabbed the firmware from here:
Firmware
Hopefully it works for you too.
Edit: Also forgot to mention, I had to put the phone into download mode for it to work correctly. Power the phone off, plug the cable into the PC, while holding volume up plug the usb cable into the phone and once you see download mode, release volume up. Then launch LGUP and it should find the phone and be good to go.
Ibuprophen said:
I don't have either devices but, Regarding the LG V40, the following area of the forum is specific to that device.
https://forum.xda-developers.com/forumdisplay.php?f=7911
The following thread is regarding the Debloating of the V40 as well.
https://forum.xda-developers.com/showthread.php?t=3857801
Regarding the V35, the following is the Enhanced Tag link that's specific to that device.
https://forum.xda-developers.com/t/lg-v35
I'm not sure which thread within the V35 ET would possibly fit what you're looking for but, you can always take a look and see if there's anything there that's helpful to you.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Thanks Ibuprofen...I'll definitely check those out this weekend....I noticed the V40 Dev mode has "OEM Unlock" an option to turn on or off but that's probably isn't going to do any good without fastboot.
Bloatcrap
I currently have the Amazon 35.... Are you telling me I can get rid of all this bloatware just by flashing the original firmware?
If this is true I could kiss you on the mouth.
All,
I have a Xfinity mobile service. I got myself a 6T which I am trying to get it work with Xfinity mobile.
Currently there are no problem except for incoming messages
Tested my SIM-Card with a
1) LG-X-Charge (from Xfinity)
2) S7+, flashed with custom ROM compatible with xfinity.
3) Essentials PH-1 (out of the box)
None of the above have any problem. I just pop the sim into any of the above phones, I have all the services without any problem even the incoming text messages.
I called into the Tier-2 advanced support spoke to a gentleman, who tried his best to make things good. He removed the "PREMIUM MESSAGE BLOCK" and tried enabling CDMA-less feature. But at the I figured we made no progress but make my APN stick to wrong address(VZINTERNET, compared to COMCAST.RSLR.VZWENTP). He has created a ticket to register my IMEI manually with Verizon to provision incoming text messages
I noticed (via *#*#4636#*#*) in s7+ and PH-1 the preferred network type get set to "unknown" when the phone reboot, as to "TD-SCDMA/CDMA/UMTS" in 6T. I tried changing the type to unknown in 6T, but no luck there.
After these trial and errors, I believe its not the network that is causing the Issue but the device itself.
Any network/software gurus here can you help regarding the same?
I can upload whatever logs you may want to see.
sresam89 said:
All,
I have a Xfinity mobile service. I got myself a 6T which I am trying to get it work with Xfinity mobile.
Currently there are no problem except for incoming messages
Tested my SIM-Card with a
1) LG-X-Charge (from Xfinity)
2) S7+, flashed with custom ROM compatible with xfinity.
3) Essentials PH-1 (out of the box)
None of the above have any problem. I just pop the sim into any of the above phones, I have all the services without any problem even the incoming text messages.
I called into the Tier-2 advanced support spoke to a gentleman, who tried his best to make things good. He removed the "PREMIUM MESSAGE BLOCK" and tried enabling CDMA-less feature. But at the I figured we made no progress but make my APN stick to wrong address(VZINTERNET, compared to COMCAST.RSLR.VZWENTP). He has created a ticket to register my IMEI manually with Verizon to provision incoming text messages
I noticed (via *#*#4636#*#*) in s7+ and PH-1 the preferred network type get set to "unknown" when the phone reboot, as to "TD-SCDMA/CDMA/UMTS" in 6T. I tried changing the type to unknown in 6T, but no luck there.
After these trial and errors, I believe its not the network that is causing the Issue but the device itself.
Any network/software gurus here can you help regarding the same?
I can upload whatever logs you may want to see.
Click to expand...
Click to collapse
so fun fact xfinity isnt compatible for text incoming on the 6t i know cause i had them lol and its an issue with their system and they dont have the "cdma-less" option like verizon does which is stupid as they share the network
Alpha_wolf said:
so fun fact xfinity isnt compatible for text incoming on the 6t i know cause i had them lol and its an issue with their system and they dont have the "cdma-less" option like verizon does which is stupid as they share the network
Click to expand...
Click to collapse
So you say there is no way around it or breaking my head/time for it rather change network?
Also as they share network, if 6T is recognized in verizon network, should that not be enough to provision incoming texts?
Another thing I wonder is, how every other device other than 6T is receiving texts? (PH1/S7+....)
sresam89 said:
So you say there is no way around it or breaking my head/time for it rather change network?
Also as they share network, if 6T is recognized in verizon network, should that not be enough to provision incoming texts?
Click to expand...
Click to collapse
thats what i thought but it wasnt the case at all xfinity has a set amount of devices they support and thats why they dont support byod for android for that reason
Alpha_wolf said:
thats what i thought but it wasnt the case at all xfinity has a set amount of devices they support and thats why they dont support byod for android for that reason
Click to expand...
Click to collapse
I kind of disagree there, they do support a lot of devices which are not in their list out-of-the-box (for e.g PH1)
Not sure you read my update
Why is every other BYOD android does not have a problem except 6T
sresam89 said:
Not sure you read my update
Why is every other BYOD android does not have a problem except 6T
Click to expand...
Click to collapse
i did and i had that question too cause i used a z3play unlocked and multiple other unlocked devices that worked with verizon but they told me it was the reason i said earlier so that all i had to go on so i changed carriers given they had bad services where i live as does verizon so ya
Alpha_wolf said:
i did and i had that question too cause i used a z3play unlocked and multiple other unlocked devices that worked with verizon but they told me it was the reason i said earlier so that all i had to go on so i changed carriers given they had bad services where i live as does verizon so ya
Click to expand...
Click to collapse
so may be with time 6T will also be supported by XM?
I have T-Mobile since 9.12 ota I had issues all I did was wipe data on messages force closed rebooted and its working so far
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.