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
Here's the results, the issue, and my recommendation for a solution:
Pixel 3
12-04 14:33:02.888 2398 2398 I Dialer : VvmOmtpService - onSmsReceived
12-04 14:33:02.918 2398 2398 I Dialer : OmtpMessageReceiver - Received message on non-activated account
12-04 14:33:02.919 2398 2398 I Dialer : LegacyModeSmsHandler - processing VVM SMS on legacy mode
12-04 14:33:02.919 2398 12650 I Dialer : VvmActivationTask - Subscriber not ready but provisioning is not supported
Pixel 2
12-04 17:40:31.973 19313 19313 I Dialer : VvmOmtpService - onSmsReceived
12-04 17:40:31.984 19313 19313 I Dialer : OmtpMessageReceiver - Received message on non-activated account
12-04 17:40:31.984 19313 19313 I Dialer : LegacyModeSmsHandler - processing VVM SMS on legacy mode
12-04 17:40:31.986 19313 19537 I Dialer : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_REQUEST_STATUS_SUCCESS /* #### SUCCESS FOR P2 #### */
Both phones initiate the provisioning process in the same manner. Go figure, it's the same software. Seems like an obvious conclusion, but hey, T-Mobile support keeps trying to talk to me like I'm an idiot, so what do I know. In the Pixel 2 request initiation, you'll see that it gets a "CONFIG_REQUEST_STATUS_SUCCESS" returned from the Visual voicemail Carrier Config Helper. This means that there's a usable vvm config at the carrier, and the phone is able to download the config and configure itself with the correct parameters. The Pixel 3 has "Subscriber not ready but provisioning is not supported". This one is an easy one. T-Mobile hasn't configured the vvm provisioning for the Pixel 3 properly or at all.
Moving on:
Pixel 3
12-04 14:33:02.919 2398 12650 I Dialer : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_SERVICE_NOT_AVAILABLE /* #### HERE IS THE FAILURE #### */
12-04 14:33:02.929 2398 2398 I Dialer : RetryPolicy - com.android.voicemail.impl.ActivationTask@b732577 completed successfully
12-04 14:33:02.929 2398 2398 I Dialer : RetryPolicy - committing deferred status: configuration_state=4
12-04 14:33:02.940 2421 11982 I VoicemailNotifier: receivers for android.intent.action.PROVIDER_CHANGED :[]
Here we see the Pixel 3 has accepted the failure status, and the message returned is that "CONFIG_SERVICE_NOT_AVAILABLE". T-Mobile (again) either hasn't set up, or has improperly set up the vvm config for the Pixel 3.
12-04 14:33:02.942 2398 2398 I Dialer : VvmTaskExecutor - no more tasks, stopping service if no task are added in 5000 millis
12-04 14:33:02.943 2398 2398 I Dialer : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status
12-04 14:33:02.950 2398 2398 I Dialer : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false
12-04 14:33:02.950 2398 2398 I Dialer : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status
12-04 14:33:02.968 2398 3428 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
12-04 14:33:02.970 2398 2398 I Dialer : VoicemailErrorAlert.updateStatus - 1 status
12-04 14:33:02.970 2398 2398 I Dialer : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated
12-04 14:33:02.970 2398 2398 I Dialer : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated
12-04 14:33:02.971 2398 2398 I Dialer : MainCallLogHost.enableFloatingButton - enabled: true
12-04 14:33:02.971 2398 3680 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
12-04 14:33:02.971 2398 2398 I Dialer : VoicemailErrorAlert.updateStatus - isModal: false, Can't activate visual voicemail
12-04 14:33:02.976 2398 2398 I Dialer : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched
12-04 14:33:02.976 2398 2398 I Dialer : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1
12-04 14:33:02.981 2398 2398 I Dialer : OldMainActivityPeer.showVoicemail - showing Tab:true
The Pixel 3 finishes the provision request here, and ends with the message displayed, "Can't activate visual voicemail" - This is what users are seeing when they open the voicemail tab in the stock google dialer.
Pixel 2 - Activation complete, messages downloading
12-04 17:40:31.992 16466 16734 I VoicemailNotifier: receivers for android.intent.action.PROVIDER_CHANGED :[]
12-04 17:40:31.994 19313 19313 I Dialer : LegacyVoicemailNotificationReceiver.onReceive - received legacy voicemail notification
12-04 17:40:31.994 19313 19313 I Dialer : LegacyVoicemailNotificationReceiver.onReceive - isRefresh: false
12-04 17:40:31.995 19313 19313 I Dialer : LegacyVoicemailNotificationReceiver.onReceive - clearing notification
12-04 17:40:31.995 19313 19313 I Dialer : LegacyVoicemailNotifier.cancelNotification - enter
12-04 17:40:31.995 19313 19537 I Dialer : SyncGreetingsTask - start
12-04 17:40:32.001 19313 19313 I Dialer : RetryPolicy - com.android.voicemail.impl.ActivationTask@edd041a completed successfully
12-04 17:40:32.001 19313 19313 I Dialer : RetryPolicy - committing deferred status:
12-04 17:40:32.007 16466 16734 I VoicemailNotifier: receivers for android.intent.action.PROVIDER_CHANGED :[]
12-04 17:40:32.009 19313 19313 I Dialer : VvmTaskExecutor - no more tasks, stopping service if no task are added in 5000 millis
12-04 17:40:32.009 19313 19313 I Dialer : VvmTaskReceiver - task received
12-04 17:40:32.009 19313 19313 I Dialer : VvmTaskReceiver - TaskExecutor already running
12-04 17:40:32.009 19313 19313 I Dialer : Task.createTask - create task:com.android.voicemail.impl.sync.SyncTask
12-04 17:40:32.010 19313 19313 I Dialer : VvmTaskExecutor - com.android.voicemail.impl.sync.SyncTask@e631083 added
12-04 17:40:32.010 19313 19537 I Dialer : VvmTaskExecutor - executing task com.android.voicemail.impl.sync.SyncTask@e631083
12-04 17:40:32.011 19313 19313 I Dialer : VvmTaskReceiver - task received
12-04 17:40:32.011 19313 19313 I Dialer : VvmTaskReceiver - TaskExecutor already running
12-04 17:40:32.011 19313 19313 I Dialer : Task.createTask - create task:com.android.voicemail.impl.sync.SyncGreetingsTask
12-04 17:40:32.011 19313 19313 I Dialer : VvmTaskExecutor - com.android.voicemail.impl.sync.SyncGreetingsTask@7882200 added
12-04 17:40:32.016 19313 19537 I Dialer : OmtpVvmCarrierCfgHlpr - OmtpEvent:DATA_IMAP_OPERATION_STARTED
12-04 17:40:32.020 16466 16734 I VoicemailNotifier: receivers for android.intent.action.PROVIDER_CHANGED :[]
The Pixel 2, having received it's config, begins downloading voicemail messages.
The solution to this is that T-Mobile needs to build and deploy a vvm config for the Pixel 3. The easiest solution is just a copy and migration from their Pixel 2 config, as they're both identical. As the OnePlus 6T also uses the stock android dialer, it will likely function with the same config. I don't have one on hand to test with, though.
Solved your problem for you, T-Mobile. You're welcome.
