os-issue-tracker
os-issue-tracker copied to clipboard
GrapheneOS
Cannot Access T-Mobile Visual Voicemail on AOSP and Google Dialers
My Pixel 7 on T-Mobile (newest Graphene version installed) on both Google Dialer and stock with GPS installed prior to installing. Below are my carrier settings and APN info. This has been a problem since I initially installed it. I get the error "Can't update visual voicemail." I have tried resetting carrier settings.
Carrier Settings: tmobile_us-42000000023.10
APN: fast.tmobile.com
Is this still an issue? No one else has reported this bug. Have you followed https://grapheneos.org/usage#carrier-functionality ?
I've got the same issue on my Pixel 7 on T-Mobile USA. The only way I've found to get visual voicemail is by using the T-Mobile Visual Voicemail app. On both the Graphene dialer and the Google dialer, I have the same problem as reported here.
Has anyone gotten this to work on the Pixel 7 on T-Mobile? There are some discussions on Reddit and the Graphene forums about it, and all the replies of "it works for me" seem to be either on other Pixel devices (e.g., 6a or 4a) or on other carriers.
Also, this phone was purchased new by me and I immediately put Graphene on it. It never connected to T-Mobile while running the stock OS. Is it possible that has something to do with it? Is there some sort of activation process that the standard Android release would've done the first time it connected that wasn't done on Graphene?
Edit: I compared my Access Point settings with a Pixel 6 on the same plan. That Pixel 6 is running stock firmware and has working Visual Voicemail. The Access Point settings all matched between the two. The carrier settings version differs between the two, though.
I have a Pixel 7 pro on Spectrum mobile (Verizon network). I too am not able to get any indication of voicemails or visual voicemails. I've reset network settings and even went as far as getting a new sim and having Spectrum reset my voicemail..no luck. Any updates on this issue at all?
Is this still an issue? No one else has reported this bug. Have you followed https://grapheneos.org/usage#carrier-functionality ?
I have seen that link and yes I am still having problems
@theuser18 @texzag @spammerofspam Please provide your carrier settings version from Settings -> Network and Internet -> SIMs -> Operator settings version
@theuser18 @texzag @spammerofspam Please provide your carrier settings version from Settings -> Network and Internet -> SIMs -> Operator settings version
Mine is tmobile_us-43000000026.12
Could you show me your MCC and MNC id in APN settings as well?
tmobile_us-43000000026.12
MCC: 310 MNC: 260
(Same MCC / MNC as in original screenshot)
Not working for Mint Mobile either ultra_us-44000000001 MCC: 310 MNC: 240 MVNO: gid: 756D 2023-03-30
Working by switching to Verizon MVNO USMobile: verizon_us-44000000015 MCC: 311 MNC: 480 2023-03-24
Also not working on my t-mobile pixel 7 Settings: tmobile_us-43000000026.12 MCC:310 MNC:260
Seeing the same behaviour. I see a notification that I have a voicemail, but Phone app shows "Can't activate visual voicemail".
Pixel 7 T-Mobile USA Release: TQ2A.230505.002.2023051600 Settings: tmobile_us-43000000026.12 MCC: 310 MNC: 260
This seems like a pretty widespread issue. Has anyone heard if any project members have their eye on this problem?
I'm also experiencing this issue on T-Mobile. I live in the USA and my phone was purchased from google.
TQ3A.230705.001.2023072600
tmobile_us-44000000029
MCC: 310 MNC: 260
2023-04-14
Having issues as well, on both my lines. I activate visual voicemail in Google Phone's settings. It seems to say it's activated. I then receive a voicemail, it cannot play it back, nor load any transcription. Play Services has Phone, Call Logs, and Network permissions. Same with Google Phone app.
Pixel 6 Pro (Unlocked), T-Mobile for Service GrapheneOS:Version: 2023100300 Dual-Sim (Physical and eSim)
tmobile_us-44000000149 MCC: 310 MNC: 260 2023-04-14
tmobile_us-44000000149 MCC: 310 MNC: 260 2023-04-14
I have the same issue on multiple carriers that use the T-Mobile network. The T-Mobile Visual Voicemail app and My Visual Voicemail app works fine, but not the built-in phone voicemail app. I had the same issue on LineageOS, so the issue appears to be with the default AOSP phone app. Doesn't anyone know where you can report a bug for that app, as this issue has persisted for at least a year. Most people would just say F--- it and get an IPhone after that long with it still not being fixed.
I have this same issue on my Pixel 7 Pro (fresh GrapheneOS installation) with T-Mobile on both AOSP and Google phone apps.
tmobile_us-52000000017
MCC: 310 MNC: 260
2023-09-27
Some US carriers require carrier apps we aren't including.
I'm not saying you are wrong about this requirement, but this VVM integration works fine on the stock Pixel firmware on my phone (purchased from Google) without any (visable) carrier apps.
Not working for Mint Mobile either ultra_us-44000000001 MCC: 310 MNC: 240 MVNO: gid: 756D 2023-03-30
also not working on mint for me with same apn settings.
I have the same issue on multiple carriers that use the T-Mobile network. The T-Mobile Visual Voicemail app and My Visual Voicemail app works fine, but not the built-in phone voicemail app. I had the same issue on LineageOS, so the issue appears to be with the default AOSP phone app. Doesn't anyone know where you can report a bug for that app, as this issue has persisted for at least a year. Most people would just say F--- it and get an IPhone after that long with it still not being fixed.
"My Visual Voicemail" app works fine as well. though, the google phone apps builtin visual voice mail worked as expected for me on LOS :man_shrugging:
I'm having the same issue with a new Pixel 8 Pro using the same T-Mobile SIM card that I had in my Pixel 4 XL (which was able to use Visual Voicemail in the AOSP dialer without any issues up until the day I powered it down and removed the SIM card). I did notice that upon inserting the SIM into the 8 Pro after removing it from the 4 XL I got an automated T-Mobile SMS message stating "There's a new version of the Visual Voicemail app available now." along with what I presume is a download link to said application.
I'm guessing T-Mobile is now forcing a specific application and is blocking new devices from accessing Visual Voicemail with the AOSP Dialer?
It doesn't seem to be working for me on build: UQ1A.240205.002.2024020500 T-Mobile pixel 7
It is not resolved for me. Pixel 7 TMobile on the latest stable release build UQ1A.240205.002.2024020500.
-------- Original Message -------- On Feb 8, 2024, 10:53 PM, Daniel Micay - notifications at github.com wrote:
Is this resolved on the latest release? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID:
DuckDuckGo removed one tracker. More
Is this resolved on the latest release?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Not working for Mint Mobile either ultra_us-44000000001 MCC: 310 MNC: 240 MVNO: gid: 756D 2023-03-30
also not working on mint for me with same apn settings.
I have the same issue on multiple carriers that use the T-Mobile network. The T-Mobile Visual Voicemail app and My Visual Voicemail app works fine, but not the built-in phone voicemail app. I had the same issue on LineageOS, so the issue appears to be with the default AOSP phone app. Doesn't anyone know where you can report a bug for that app, as this issue has persisted for at least a year. Most people would just say F--- it and get an IPhone after that long with it still not being fixed.
"My Visual Voicemail" app works fine as well. though, the google phone apps builtin visual voice mail worked as expected for me on LOS 🤷♂️
im not sure what changed or when but my visual voicemail in googles phone app is working now. still on mint mobile :man_shrugging:
I've been trying to troubleshoot this for my setup (Pixel 8 Pro with T-Mobile USA postpaid plan).
I modified LegacyModeSmsHandler in GrapheneOS' dialer app to log the messages sent for VVM activation.
When sending either the CVVM Activate:dt=6 or Deactivate:dt=6 messages to 122 (T-Mobile's VVM destination number), T-Mobile returns the SUBSCRIBER_BLOCKED status:
2024-04-18 20:34:59.240514 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - eventType=STATUS, data=Bundle[mParcelledData.dataSize=128]
2024-04-18 20:34:59.240779 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=rc, value=0
2024-04-18 20:34:59.240981 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=st, value=B
2024-04-18 20:34:59.241160 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=srv, value=vvm.mstore.msg.t-mobile.com
However, if I send the CVVM STATUS:dt=6 message, T-Mobile returns the SUBSCRIBER_READY status with the IMAP credentials for accessing the voicemails:
2024-04-18 20:35:32.752798 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - eventType=STATUS, data=Bundle[mParcelledData.dataSize=388]
2024-04-18 20:35:32.753213 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=pw_len, value=4-9
2024-04-18 20:35:32.753472 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=vs_len, value=10
2024-04-18 20:35:32.753724 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=u, value=<redacted>
2024-04-18 20:35:32.753925 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=pw, value=redacted>
2024-04-18 20:35:32.754137 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=rc, value=0
2024-04-18 20:35:32.754357 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=st, value=R
2024-04-18 20:35:32.754565 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=ipt, value=148
2024-04-18 20:35:32.754742 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=srv, value=e7.vvm.mstore.msg.t-mobile.com
2024-04-18 20:35:32.754971 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=lang, value=1|2|3|4
2024-04-18 20:35:32.755164 -0400 E/Dialer ( 3615): LegacyModeSmsHandler - data: key=g_len, value=180
I manually tested the IMAP credentials with curl and confirmed that they are valid:
❯ curl -v imaps://<redacted>:<redacted>@e7.vvm.mstore.msg.t-mobile.com/
<...>
* Connected to e7.vvm.mstore.msg.t-mobile.com (2607:fb90:c13f:10b::4) port 993
<...>
* subject: C=US; ST=Washington; L=Bellevue; O=T-Mobile USA, Inc.; CN=vvm.mstore.msg.t-mobile.com
< * OK [CAPABILITY AUTH=DIGEST-MD5 IMAP4rev1 QUOTA UIDPLUS] mStore IMAP4rev1 Server is ready.
> A001 CAPABILITY
< * CAPABILITY AUTH=DIGEST-MD5 IMAP4rev1 QUOTA UIDPLUS
< A001 OK CAPABILITY completed.
> A002 AUTHENTICATE DIGEST-MD5
<...>
< A002 OK login successful
> A003 LIST "" *
< * LIST (\HasNoChildren) "/" "/INBOX"
* LIST (\HasNoChildren) "/" "/INBOX"
< * LIST (\HasNoChildren) "/" "/Greetings"
* LIST (\HasNoChildren) "/" "/Greetings"
< * LIST (\HasNoChildren) "/" "/Trash"
* LIST (\HasNoChildren) "/" "/Trash"
< A003 OK LIST completed.
* Connection #0 to host e7.vvm.mstore.msg.t-mobile.com left intact
If I hack the dialer to send the status CVVM message instead of the activate message, then it successfully persists the credentials and visual voicemail works.
I'm not sure why activation fails on GrapheneOS yet. It seems to work on the stock Pixel OS. The one weird thing I noticed is that when I'm running GrapheneOS, T-Mobile's website reports the device as being a "Galaxy Note9 - Ocean Blue - 512GB". When I'm running the stock Pixel OS, T-Mobile's website correctly reports the device as being a "Pixel 8 Pro - Obsidian". I wonder if this is why T-Mobile is blocking the activation and deactivation messages.
Unfortunately, I'm not super familiar with the telephony stack yet and have no idea how T-Mobile is determining the model. Maybe things will just work if it detects the correct model.
@chenxiaolong great work! Hopefully this will help pinpoint the actual issue 👍