Forum Discussion
Android Native Visual Voicemail Trouble
I'm using a Pixel2XL on T-Mobile and the native Visual Voicemail (built into the Google Phone app) will not activate. The VM tab does show, and I have the option checked in the menu settings for ...
UPDATED 7/13/2021:
For folks wondering if their Native VVM app will work on T-Mobile's network, here's some helpful info. The native VVM app on Non-T-Mobile devices isn't something T-Mobile can guarantee will work with the VVM service. This goes for other native apps as well. We recommend folks download T-Mobile Visual Voicemail app I've linked below and use the VVM service through that app. The second link I posted below is for troubleshooting if you happen to run into any issues.
We have a couple articles that can help with this. Check out the two links below in relationship to the issue.
App de Correo de voz visual de T-Mobile
Solución de problemas del correo de voz
Truth is they have no idea why it isn't working. The naitve VVM on my Pixel 2 from Verizon WILL on T-Mobile but not on my T-MOBILE OnePlus 6T. I think that when a number is ported over to T-Mobile from another carrier something isn't configured right on T-Mobile's end. This error in configuration causes the VVM native in Android to not work in some phones. The guy that got me signed up to T-Mobile is someone I've known for a few years. He has a OnePlus 6T and his native VVM works fine. The error has to be attached to the specific line itself and is not the fault of the phone you have. When I first signed up for serviceI couldn't use any mobile data on my Pixel 2.
I questioned her when she said my phone was "T Mobile issued". I asked if I bought a Samsung, or even the OnePlus 6T from T Mobile, could she guarantee that will work. She hesitated for a minute and not confidently stated that native VVM would work. So I pressed the fact that I know of at least one user in the T Mobile community forums that owns a OnePlus 6T and it doesn't work. That's when she admitted that their was a system push that affected some Samsung and OnePlus 6T users. She couldn't verify if it was working for either now, but that confirms something is wrong. I'm assuming it's an update on their end so she pretty much admitted that they botched something up and can't figure out how to fix it. That's how I see it anyway.
