Solved

Android Native Visual Voicemail Trouble

Show first post
This topic has been closed for comments

115 replies

N
Userlevel 1
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.

N
Userlevel 1

Thanks. I knew she was blowing smoke up my @$$ when she made those claims. I even asked if I got the phone from Google, she claimed it still wouldn't work because it was designed for Verizon. I told her it wasn't designed for Verizon, and she stuck to her guns that it wasn't designed to T Mobile services. She even went as far to say that T Mobile's VVM app was specifically designed for these reasons. Really? I thought it was because older OS versions of Android dialers didn't have VVM built in. I'm going to put T Mobile on blast and try to reach out to some of the media outlets (Android Police, The Verge, Engadget, etc.) so they can spread the word out and light a fire. I'm to the point of reporting them to BBB.

It's obvious this is a backend issue that they are ignoring.

C
Userlevel 1

Hey @tmo_amanda

This issue should NOT be marked as "answered". It's not even remotely answered. For people still having this issue, and those searching because they're having the same problem, seeing the thread marked as "answered" is highly misleading.

C
Userlevel 1
nokisme wrote:
This is my 3rd call to T-Mobile. I had the 1st rep check and she said she just enabled VVM to my account. I do have the One Plus so I assumed it was already enabled. Either way, I stopped the app, cleared cache, restarted phone but it's still not working. She escalated to the tech, who said that this feature doesn't work on T-Mobile and reiterated that the device is a "Verizon" phone so the T-mobile's VVM feature won't work. I asked if I bought a T Mobile device, such as one of the Samsung's they sell or even the OnePlus 6T, she continued to say that those devices will work. But looking at this thread and others I've found on the internet, this doesn't always hold true.
So in the end, the tech claims I won't be able to use my Pixel 2 XL's native VVM because it's not a fully supported device through T Mobile. The only way this phone can get VVM is to use the app. So why was T Mobile touting they were the superior carrier for the Pixel? Unleash the Pixel 2 for Half Off – No Verizon Required | T-Mobile Newsroom

It's all apparently marketing and lies. I've put more work into solving this than T-Mobiles "engineers" have. 

Does my Pixel 2 XL not work because I got it from Verizon instead of Google? Would this work on Google Fi which uses T Mobile's service as one of the supported carriers?

No, Verizon doesn't put any specific software on the Pixel that can't be removed. If you are so inclined, you can even flash the "non-Verizon" image to your Pixel and it will be indistinguishable from a "Verizon" Pixel. (OG/XL, 2/XL, 3/XL) Images can be found here: https://developers.google.com/android/ota

Your native vvm app would (and does) work on Google Fi, even using T-Mobile's network, because they actually bothered setting up omtp compliant vvm services. (I came to T-Mo from Fi. In retrospect, maybe not such a great idea...)

---- snip ----
12-14 11:31:03.225 2229 12844 I Dialer : VvmActivationTask - Subscriber not ready but provisioning is not supported
12-14 11:31:03.225 2229 12844 I Dialer : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_SERVICE_NOT_AVAILABLE
---- snip ----

This is the same error everyone else is seeing - even those that have T-Mobile "branded" OnePlus 6T phones. (Which, incidentally also don't work... great work there, T-Mobile.) At this point, it's clearly T-Mobile that's screwed up. They are outright refusing to acknowledge the issue, hiding behind the weak "You should buy our branded phones" argument. Frankly, it's shameful.

S
Userlevel 1

Nokisme: That rep is full of sh1t.  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 service I couldn't use any mobile data on my Pixel 2.  They had to go deep into the settings and reconfigure some things to get it to work.  I think something similar needs to happen with VVM.

N
Userlevel 1

This is my 3rd call to T-Mobile. I had the 1st rep check and she said she just enabled VVM to my account. I do have the One Plus so I assumed it was already enabled. Either way, I stopped the app, cleared cache, restarted phone but it's still not working. She escalated to the tech, who said that this feature doesn't work on T-Mobile and reiterated that the device is a "Verizon" phone so the T-mobile's VVM feature won't work. I asked if I bought a T Mobile device, such as one of the Samsung's they sell or even the OnePlus 6T, she continued to say that those devices will work. But looking at this thread and others I've found on the internet, this doesn't always hold true.

So in the end, the tech claims I won't be able to use my Pixel 2 XL's native VVM because it's not a fully supported device through T Mobile. The only way this phone can get VVM is to use the app. So why was T Mobile touting they were the superior carrier for the Pixel? Unleash the Pixel 2 for Half Off – No Verizon Required | T-Mobile Newsroom

Does my Pixel 2 XL not work because I got it from Verizon instead of Google? Would this work on Google Fi which uses T Mobile's service as one of the supported carriers?

12-14 11:31:02.081  2229  2229 I Dialer  : OmtpVvmSyncReceiver - Unactivated account ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} found, activating

12-14 11:31:02.082  2229  2229 I Dialer  : VvmTaskReceiver - task received

12-14 11:31:02.082  2229  2229 I Dialer  : VvmTaskReceiver - scheduling new job

12-14 11:31:02.083  2229  2229 I Dialer  : TaskSchedulerJobService - scheduling job with 1 tasks

12-14 11:31:02.083  2229  2229 I Dialer  : TaskSchedulerJobService - running job instantly.

12-14 11:31:02.084  2229  2229 I Dialer  : TaskSchedulerJobService - job 51 scheduled

12-14 11:31:02.086  2229  2229 I Dialer  : TaskSchedulerJobService - starting 51

12-14 11:31:02.087  2229  2229 I Dialer  : VvmTaskExecutor - onStartJob

12-14 11:31:02.087  2229  2229 I Dialer  : Task.createTask - create task:com.android.voicemail.impl.ActivationTask

12-14 11:31:02.087  2229 12844 I Dialer  : VvmTaskExecutor - executing task com.android.voicemail.impl.ActivationTask@e703973

12-14 11:31:02.088  2229 12844 I Dialer  : PreOMigrationHandler - ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} already migrated

12-14 11:31:02.101  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:02.102  2229 12844 I Dialer  : VvmActivationTask - VVM content provider configured - vvm_type_cvvm

12-14 11:31:02.102  2229 12844 I Dialer  : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_ACTIVATING

12-14 11:31:02.104  2229  2229 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false

12-14 11:31:02.104  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:02.109  2229  2229 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false

12-14 11:31:02.110  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:02.115  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:02.119  2229  2229 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false

12-14 11:31:02.121  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:02.127  2229  2229 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false

12-14 11:31:02.128  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:02.136  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - 1 status

12-14 11:31:02.136  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:02.137  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:02.137  2229  2229 I Dialer  : MainCallLogHost.enableFloatingButton - enabled: true

12-14 11:31:02.137  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Activating visual voicemail

12-14 11:31:02.154  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - 1 status

12-14 11:31:02.154  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:02.154  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:02.155  2229  2229 I Dialer  : MainCallLogHost.enableFloatingButton - enabled: true

12-14 11:31:02.155  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Activating visual voicemail

12-14 11:31:02.155  2229  2229 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched

12-14 11:31:02.155  2229  2229 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1

12-14 11:31:02.159  2229  2229 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true

12-14 11:31:02.163  2229  2229 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched

12-14 11:31:02.163  2229  2229 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1

12-14 11:31:02.167  2229  2229 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true

12-14 11:31:02.170  2229  2229 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched

12-14 11:31:02.170  2229  2229 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1

12-14 11:31:02.174  2229  2229 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true

12-14 11:31:02.178  2229  2229 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched

12-14 11:31:02.178  2229  2229 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1

12-14 11:31:02.182  2229  2229 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true

12-14 11:31:02.413  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:02.463  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - 1 status

12-14 11:31:02.464  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:02.464  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:02.465  2229  2229 I Dialer  : MainCallLogHost.enableFloatingButton - enabled: true

12-14 11:31:02.465  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Activating visual voicemail

12-14 11:31:03.203  2229  2229 I Dialer  : VvmOmtpService - onSmsReceived

12-14 11:31:03.225  2229  2229 I Dialer  : OmtpMessageReceiver - Received message on non-activated account

12-14 11:31:03.225  2229  2229 I Dialer  : LegacyModeSmsHandler - processing VVM SMS on legacy mode

12-14 11:31:03.225  2229 12844 I Dialer  : VvmActivationTask - Subscriber not ready but provisioning is not supported

12-14 11:31:03.225  2229 12844 I Dialer  : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_SERVICE_NOT_AVAILABLE

12-14 11:31:03.234  2229  2229 I Dialer  : RetryPolicy - com.android.voicemail.impl.ActivationTask@e703973 completed successfully

12-14 11:31:03.234  2229  2229 I Dialer  : RetryPolicy - committing deferred status: configuration_state=4

12-14 11:31:03.247  2229  2229 I Dialer  : VvmTaskExecutor - no more tasks, stopping service if no task are added in 5000 millis

12-14 11:31:03.249  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:03.256  2229  2229 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false

12-14 11:31:03.257  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:03.264  2229  2229 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false

12-14 11:31:03.265  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:03.279  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - 1 status

12-14 11:31:03.279  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:03.279  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:03.280  2229  2229 I Dialer  : MainCallLogHost.enableFloatingButton - enabled: true

12-14 11:31:03.280  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Can't activate visual voicemail

12-14 11:31:03.296  2229  2229 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched

12-14 11:31:03.297  2229  2229 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1

12-14 11:31:03.303  2229  2229 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true

12-14 11:31:03.307  2229  2229 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched

12-14 11:31:03.308  2229  2229 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1

12-14 11:31:03.313  2229  2229 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true

12-14 11:31:08.254  2229  2229 I Dialer  : VvmTaskExecutor - Stopping service

12-14 11:31:08.255  2229  2229 I Dialer  : VvmTaskExecutor - finishing Job

12-14 11:31:08.256  2229  2229 I Dialer  : TaskSchedulerJobService - finishing job

12-14 11:31:08.269  2229  2229 I Dialer  : JobFinishedPoller.run - Job finished

12-14 11:31:08.270  2229  2229 I Dialer  : VvmTaskExecutor - terminated

12-14 11:31:15.711  2229  2229 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status

12-14 11:31:15.762  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - 1 status

12-14 11:31:15.763  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:15.763  2229  2229 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated

12-14 11:31:15.764  2229  2229 I Dialer  : MainCallLogHost.enableFloatingButton - enabled: true

12-14 11:31:15.764  2229  2229 I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Can't activate visual voicemail

C
Userlevel 1

Long and detailed post incoming.

Digging through the android source code, checking into how the process works. (Code available here: https://android.googlesource.com)

What we see in the logs is this, (and I'll break down the bits as the post goes along)

Phone realizes it's not activated, starts task. This can also happen when a user presses the "Try again" button in the failed activation screen.

I Dialer  : OmtpVvmSyncReceiver - Unactivated account ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} found, activating

Activation task created and executed.

I Dialer  : VvmTaskReceiver - task received

I Dialer  : VvmTaskReceiver - scheduling new job

I Dialer  : TaskSchedulerJobService - scheduling job with 1 tasks

I Dialer  : TaskSchedulerJobService - running job instantly.

I Dialer  : TaskSchedulerJobService - job 34 scheduled

I Dialer  : TaskSchedulerJobService - starting 34

I Dialer  : VvmTaskExecutor - onStartJob

I Dialer  : Task.createTask - create task:com.android.voicemail.impl.ActivationTask

I Dialer  : VvmTaskExecutor - executing task com.android.voicemail.impl.ActivationTask@b732577

Activation begins, SMS sent to get config

I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Activating visual voicemail

I QImsService: ImsSmsImpl : sendSms:: token:4 msgRef:0 format:3gpp isRetry:false

I QImsService: ImsSenderRxr : sendSms over IImsRadio with format:3gpp

I QImsService: ImsSenderRxr : [0026]> REQUEST_SEND_IMS_SMS [SUB0]

SMS response received by phone

I QImsService: ImsRadioResponse : Ims sms response received

I QImsService: ImsSenderRxr : [0026]< REQUEST_SEND_IMS_SMS { mMessageRef = 144, mSendSmsResult = 1, mSendSmsReason = 0}[SUB0]

I QImsService: ImsSmsHandler : Message received: what = 1

I QImsService: ImsSmsImpl : onSendSmsResult:: token:4 smsResponse:{ mMessageRef = 144, mSendSmsResult = 1, mSendSmsReason = 0}

I QImsService: ImsSenderRxr : [unsl]< UNSOL_INCOMING_IMS_SMS[SUB0]

I QImsService: ImsSmsHandler : Message received: what = 2

I QImsService: ImsSmsImpl : onSmsReceived:: token:3 incomingSms:{ mFormat = 3gpp verstat = 0}

D GsmInboundSmsHandler: Skipped message de-duping logic

I QImsService: ImsSmsImpl : acknowledgeSms:: token:3 msgRef:0 result:1

I QImsService: ImsSenderRxr : [0027]> REQUEST_ACK_IMS_SMS [SUB0]

I VvmSmsFilter: VVM SMS received

I VvmSmsReceiver: Sending SMS received event to remote service

I RemoteVvmTaskManager: Binding to ComponentInfo{com.google.android.dialer/com.android.voicemail.impl.OmtpService}

Response processed, status returned

I Dialer  : VvmOmtpService - onSmsReceived

I Dialer  : OmtpMessageReceiver - Received message on non-activated account

I Dialer  : LegacyModeSmsHandler - processing VVM SMS on legacy mode

I Dialer  : VvmActivationTask - Subscriber not ready but provisioning is not supported

I Dialer  : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_SERVICE_NOT_AVAILABLE

Here's where it gets fun. Checking the code.

From ActivationTask.java

Task to activate the visual voicemail service. A request to activate VVM will be sent to the carrier, which will respond with a STATUS SMS. The credentials will be updated from the SMS. If the user is not provisioned, provisioning will be attempted. Activation happens when the phone boots, the SIM is inserted, signal returned when VVM is not activated yet, and when the carrier spontaneously sent a STATUS SMS.

    StatusMessage message = new StatusMessage(data);

    VvmLog.d(

        TAG,

        "STATUS SMS received: st="

            + message.getProvisioningStatus()

            + ", rc="

            + message.getReturnCode());

    if (message.getProvisioningStatus().equals(OmtpConstants.SUBSCRIBER_READY)) {

      VvmLog.d(TAG, "subscriber ready, no activation required");

      updateSource(getContext(), phoneAccountHandle, message, helper);

    } else {

      if (helper.supportsProvisioning()) {

        VvmLog.i(TAG, "Subscriber not ready, start provisioning");

        helper.startProvisioning(

            this, phoneAccountHandle, status, message, data, isCarrierInitiated);

      } else if (message.getProvisioningStatus().equals(OmtpConstants.SUBSCRIBER_NEW)) {

        VvmLog.i(TAG, "Subscriber new but provisioning is not supported");

        // Ignore the non-ready state and attempt to use the provided info as is.

        // This is probably caused by not completing the new user tutorial.

        updateSource(getContext(), phoneAccountHandle, message, helper);

      } else {

        VvmLog.i(TAG, "Subscriber not ready but provisioning is not supported");

        helper.handleEvent(status, OmtpEvents.CONFIG_SERVICE_NOT_AVAILABLE);

      }

    }

Bolded section is what failures are generating. That is pulled from the sms response to message.getProvisioningStatus(), which is received from the SMS status message sent by TMo vvm servers. The result should be in the first few lines:

        "STATUS SMS received: st="

            + message.getProvisioningStatus()

            + ", rc="

            + message.getReturnCode());

Which will give you a result like:

    I Dialer  : VvmOmtpService - onSmsReceived

    I Dialer  : OmtpMessageReceiver - Received message on non-activated account

    I Dialer  : VvmActivationTask - STATUS SMS received: st=B, rc=0

(Above results are from when I had customer service remove the vvm add-on from my account. Without having vvm active on the account, the vvm service is (rightfully) setting status to Blocked.)      

VvmActivationTask return comes from this section in OmtpConstants.java:

/** See {@link OmtpConstants#PROVISIONING_STATUS_VALUES} */

public static final String PROVISIONING_STATUS = "st";

/** See {@link OmtpConstants#RETURN_CODE_VALUES} */

public static final String RETURN_CODE = "rc";

A successful return would be from this list, pulled from OmtpConstants.java:

    public static final String SUBSCRIBER_NEW = "N";

    public static final String SUBSCRIBER_READY = "R";

    public static final String SUBSCRIBER_PROVISIONED = "P";

    public static final String SUBSCRIBER_UNKNOWN = "U";

    public static final String SUBSCRIBER_BLOCKED = "B";

    public static final String[] PROVISIONING_STATUS_VALUES = {

        SUBSCRIBER_NEW,

        SUBSCRIBER_READY,

        SUBSCRIBER_PROVISIONED,

        SUBSCRIBER_UNKNOWN,

        SUBSCRIBER_BLOCKED

    };

In this instance, "st" should return N, R, or P (for a working account) with a return code ("rc") in the following values: (also from OmtpConstants.java)

    public static final String SUCCESS = "0";

    public static final String SYSTEM_ERROR = "1";

    public static final String SUBSCRIBER_ERROR = "2";

    public static final String MAILBOX_UNKNOWN = "3";

    public static final String VVM_NOT_ACTIVATED = "4";

    public static final String VVM_NOT_PROVISIONED = "5";

    public static final String VVM_CLIENT_UKNOWN = "6";

    public static final String VVM_MAILBOX_NOT_INITIALIZED = "7";

    public static final String[] RETURN_CODE_VALUES = {

        SUCCESS,

        SYSTEM_ERROR,

        SUBSCRIBER_ERROR,

        MAILBOX_UNKNOWN,

        VVM_NOT_ACTIVATED,

        VVM_NOT_PROVISIONED,

        VVM_CLIENT_UKNOWN,

        VVM_MAILBOX_NOT_INITIALIZED,

    };

The hope here would be that it returns st=(N or R) and rc=0 for SUCCESS. (Hint: It doesn't. 😥 )

There's way more here, but this is as far as I'm going tonight.

C
Userlevel 1

I'm in the same boat. SIM works fine in the Pixel 2, but the Pixel 3 won't activate at all. It's definitely a config issue on TMo's end that they can't or won't fix. I've opened multiple tickets and spoken with several support people, even having the issue "escalated to the engineers" a few times, too. Still no change at all, and every person I talk to acts like they've never heard of this issue. I've even referenced this thread in my calls. At this point, it's a waiting game. Wait for them to fix it, or wait until I can reconcile switching providers (again) to someone that doesn't have this issue.

S
Userlevel 1

Don't hold your breath for a fix.  My case was escalated to the engineers 3 weeks ago and I never got a response.  They either don't know how to fix it or don't care to fix it because T-Mobile seems to have faith in their crappy visual voicemail app so why bother with the naitve option.  I put my SIM card back in my pixel 2 just as a test and voicemail activates just fine so it's definitely a per device issue.

R

Yeah I've had a case open for two weeks for my Pixel 3 XL.  They even got Google on the line for an hour to troubleshoot and they deemed it a T-Mobile issue.  They said they'd escalated it last week to engineering but no response.  Every time I call they act like they've never heard of this issue.  Would be great if they read their own support threads.

C
Userlevel 1

Hey @erikswan2​ - Android uses logcat through adb.

Simple instructions:

1. Put your phone into developer mode

2. enable usb debugging

3. install android debug bridge (adb)

4. once you're connected to your phone, run the following:

          adb logcat -c

This will clear the current logs, so you don't get a bunch of stuff you don't need. Now reproduce the issue you're looking for logs on, then run:

(for the vvm logs, I normally open the phone, go to the vvm tab, wait for it to fail, then after I clear the logs, hit the "try again" link.

          adb logcat -d > (filename).txt

M

/u/tmo_amanda, can you please provide an update?

E

@carrierlost​, just curious, what is the location of the log files you are grabbing from the device? I've been wanting to debug VVM in some other situations (e.g. some prepaid carriers), and this would certainly help.

S
Userlevel 1

So I called T-Mobile support again because removing the voicemail to text feature did not fix my issue.  The guy I was transferred to a "tech expert" basically told me they are not able to get the stock android visual voicemail to work on the 6T with their service, but they will gladly sell the phones in their stores.  He then proceeded to tell me it's OnePlus' fault and transferred me to them.  This is just fantastic service!!! 

M

Any progress or leads on this?

This is affecting quite a few people, at least as seen over on Reddit and certainly more.

Not sure why this thread is marked as "answered" if there's no solution, but regardless, please let us know if there's any fix forthcoming.

Thanks.

S
Userlevel 1

So for some reason the TMobile VVM app stopped working after the lasted update.  I have a OnePlus 6T...that I got from...T-MOBILE! WTF is this garbage!!!  Tech support has no idea what's going on and they have said twice they were escalating to their "engineers"  What ever this is beyond ridiculous at this point.

M

Just moved 2 lines to tmobile and brought a new, unlocked pixel 3... same issue with VVM as reported by others.

@tmo_amanda​ what is the ETA on this being resolved. Basically the 3rd largest hardware platform (google android) is not properly supported

N
Userlevel 1

Hopefully, T-Mobile can implement your findings. I have the Pixel 2 XL and I'm currently having this same issue. Their excuse is that I'm a new customer and it takes "some" time to activate...up to 72 hours. I didn't have this issue when I activated my phone on Verizon. I'm excited that T-Mobile has better coverage for my area than Verizon, but this little hiccup puts a bad taste in my mouth. I seriously hope this gets resolved cause I can't settle for that sorry excuse of an app, T-Mobile VVM.

C
Userlevel 1

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.

C
Userlevel 1

Grabbed some logs from the Pixel 3: 

12-04 14:33:01.799  2398  2398 I Dialer  : VvmTaskReceiver - task received
12-04 14:33:01.799  2398  2398 I Dialer  : VvmTaskReceiver - scheduling new job
12-04 14:33:01.799  2398  2398 I Dialer  : TaskSchedulerJobService - scheduling job with 1 tasks
12-04 14:33:01.799  2398  2398 I Dialer  : TaskSchedulerJobService - running job instantly.
12-04 14:33:01.801  2398  2398 I Dialer  : TaskSchedulerJobService - job 34 scheduled
12-04 14:33:01.803  2398  2398 I Dialer  : TaskSchedulerJobService - starting 34
12-04 14:33:01.803  2398  2398 I Dialer  : VvmTaskExecutor - onStartJob
12-04 14:33:01.804  2398  2398 I Dialer  : Task.createTask - create task:com.android.voicemail.impl.ActivationTask
12-04 14:33:01.804  2398 12650 I Dialer  : VvmTaskExecutor - executing task com.android.voicemail.impl.ActivationTask@b732577
12-04 14:33:01.804  2398 12650 I Dialer  : PreOMigrationHandler - ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} already migrated
12-04 14:33:01.824  2398  2398 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status
12-04 14:33:01.825  2421  3702 I VoicemailNotifier: receivers for android.intent.action.PROVIDER_CHANGED :[]
12-04 14:33:01.826  2398 12650 I Dialer  : VvmActivationTask - VVM content provider configured - vvm_type_cvvm
12-04 14:33:01.827  2398 12650 I Dialer  : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_ACTIVATING
12-04 14:33:01.830  2398  2398 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false
12-04 14:33:01.830  2398  2398 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status
12-04 14:33:01.833  2421  3702 I VoicemailNotifier: receivers for android.intent.action.PROVIDER_CHANGED :[]
12-04 14:33:01.837  2398  2398 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status
12-04 14:33:01.844  2398  2398 I Dialer  : MainCallLogFragmentListener - voicemailStatusObserver.onChange selfChange:false
12-04 14:33:01.845  2398  2398 I Dialer  : CallLogQueryHandler.fetchVoicemailStatus - fetching voicemail status
12-04 14:33:01.851  2398  2398 I Dialer  : VoicemailErrorAlert.updateStatus - 1 status
12-04 14:33:01.852  2398  2398 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated
12-04 14:33:01.852  2398  2398 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated
12-04 14:33:01.853  2398  2398 I Dialer  : MainCallLogHost.enableFloatingButton - enabled: true
12-04 14:33:01.853  2398  2398 I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Activating visual voicemail
12-04 14:33:01.856  1583  2368 I QImsService: ImsSmsImpl : sendSms:: token:4 msgRef:0 format:3gpp isRetry:false
12-04 14:33:01.856  1583  2368 I QImsService: ImsSenderRxr : sendSms over IImsRadio with format:3gpp
12-04 14:33:01.857  1583  2368 I QImsService: ImsSenderRxr : [0026]> REQUEST_SEND_IMS_SMS [SUB0]
12-04 14:33:01.869  2398  2398 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched
12-04 14:33:01.869  2398  2398 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1
12-04 14:33:01.873  2398  2398 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true
12-04 14:33:01.883  2398  2398 I Dialer  : VoicemailErrorAlert.updateStatus - 1 status
12-04 14:33:01.883  2398  2398 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated
12-04 14:33:01.883  2398  2398 I Dialer  : VoicemailClientImpl.isVoicemailTranscriptionAvailable - visual voicemail is not activated
12-04 14:33:01.884  2398  2398 I Dialer  : MainCallLogHost.enableFloatingButton - enabled: true
12-04 14:33:01.884  2398  2398 I Dialer  : VoicemailErrorAlert.updateStatus - isModal: false, Activating visual voicemail
12-04 14:33:01.885  2398  2398 I Dialer  : OldMainActivityPeer.MainCallLogFragmentListener - onVoicemailStatusFetched
12-04 14:33:01.885  2398  2398 I Dialer  : OldMainActivityPeer.onVoicemailStatusFetched - hasActiveVoicemailProvider:true, number of active voicemail sources:1
12-04 14:33:01.891  2398  2398 I Dialer  : OldMainActivityPeer.showVoicemail - showing Tab:true
12-04 14:33:02.283  1583  1712 I QImsService: ImsRadioResponse : Ims sms response received
12-04 14:33:02.284  1583  1712 I QImsService: ImsSenderRxr : [0026]< REQUEST_SEND_IMS_SMS { mMessageRef = 144, mSendSmsResult = 1, mSendSmsReason = 0}[SUB0]
12-04 14:33:02.285  1583  1801 I QImsService: ImsSmsHandler : Message received: what = 1
12-04 14:33:02.285  1583  1801 I QImsService: ImsSmsImpl : onSendSmsResult:: token:4 smsResponse:{ mMessageRef = 144, mSendSmsResult = 1, mSendSmsReason = 0}
12-04 14:33:02.756  1583  1712 I QImsService: ImsSenderRxr : [unsl]< UNSOL_INCOMING_IMS_SMS[SUB0]
12-04 14:33:02.757  1583  1801 I QImsService: ImsSmsHandler : Message received: what = 2
12-04 14:33:02.757  1583  1801 I QImsService: ImsSmsImpl : onSmsReceived:: token:3 incomingSms:{ mFormat = 3gpp verstat = 0}
12-04 14:33:02.765  1583  1733 D GsmInboundSmsHandler: Skipped message de-duping logic
12-04 14:33:02.815  1583  1733 I QImsService: ImsSmsImpl : acknowledgeSms:: token:3 msgRef:0 result:1
12-04 14:33:02.817  1583  1733 I QImsService: ImsSenderRxr : [0027]> REQUEST_ACK_IMS_SMS [SUB0]
12-04 14:33:02.858  1583  1733 I VvmSmsFilter: VVM SMS received
12-04 14:33:02.865  1583  1583 I VvmSmsReceiver: Sending SMS received event to remote service
12-04 14:33:02.880  1583  1583 I RemoteVvmTaskManager: Binding to ComponentInfo{com.google.android.dialer/com.android.voicemail.impl.OmtpService}
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
12-04 14:33:02.919  2398 12650 I Dialer  : OmtpVvmCarrierCfgHlpr - OmtpEvent:CONFIG_SERVICE_NOT_AVAILABLE
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 :[]
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.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  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
12-04 14:33:07.950  2398  2398 I Dialer  : VvmTaskExecutor - Stopping service
12-04 14:33:07.950  2398  2398 I Dialer  : VvmTaskExecutor - finishing Job
12-04 14:33:07.950  2398  2398 I Dialer  : TaskSchedulerJobService - finishing job
12-04 14:33:07.956  2398  2398 I Dialer  : JobFinishedPoller.run - Job finished
12-04 14:33:07.957  2398  2398 I Dialer  : VvmTaskExecutor - terminated

From what I can tell, there are a few distinct steps happening here:

  • Task received, job scheduled for immediate run, job starts
  • Checks pre-migration status, checks voicemail status
  • Gets notified provider has changed
  • VvmActivationTask - VVM content provider configured as type - vvm_type_cvvm
  • Begins activating config
  • Fetches status a few times and updates status to 1. This returns "visual voicemail is not activated" and kicks off activation.
  • Attempts activation, calls SMS service to send message with format 3gpp (SMS)
  • SMS response received twice, the second response is marked as unsolicited and ignored as duplicate
  • SMS requests acknowledgement of SMS
  • VVM response SMS received
  • VVM sends SMS to remote service and binds to com.google.android.dialer/com.android.voicemail.impl.OmtpService

This is where it gets interesting.

  • VVM service reports message received on non-activated account
  • LegacyModeSmsHandler processes the response on "legacy mode"
  • VvmActivationTask returns "Subscriber not ready but provisioning is not supported"
  • The carrier config helper returns "CONFIG_SERVICE_NOT_AVAILABLE"
  • Task ends and returns "Can't activate visual voicemail"

I don't have my Pixel 2 with me at work, but I'm going to go back through this when I get home and see if I can catch an "accepted" activation request and find the differences.

N
Userlevel 1

I just got off the phone with support. Even though I was able to install the T-Mobile VVM app on my phone and that tested fine, they couldn't get it working natively stating VVM was not enabled on my account. He stated it was activated today and being that I'm still new to the service, it may take up to 72 hours for all features to work. Not sure if I remember having this issue originally when I first set up my Pixel 2 XL on Verizon. I do remember taking some time to kick in but not this long. I'll see what happens after 72 hours.

N
Userlevel 1

I recently just switched to T-Mobile from Verizon and brought my Pixel 2 XL. Since I had a balance, I had to get the One Plus plan. I too am experiencing the same exact issue. I tried clearing the cache for the dialer app, factory reset my phone, worked with Google Support but still can't get it to work. I installed T-Mobile VVM app and "activated" it and it was working fine. So theoretically, it should work on my native dialer but even after uninstalling it T-Mobile VVM app, the native dialer VVM seems to be stuck at activating.

I will be calling T-Mobile support even though I'm not feeling confident that they'd get it working.

C
Userlevel 1

Same issue, same description. Google Pixel 3, getting the "Can't activate visual voicemail" in the stock Google dialer. The TMobile vvm app works, but frankly it sucks. I have a Pixel to avoid bad carrier apps.

I just joined TMobile, but this could be a deal breaker for me, as this worked perfectly on Google Fi.

Please get this fixed!

M

I can confirm I am experiencing the same problem. I recently upgraded from Pixel 2XL to Pixel 3 and the native Visual Voicemail in Google Phone app stopped working. It was working fine before. I get an error: "Can't activate visual voicemail" when I click on the Voicemail tab.

shelbyfan
Badge +1

As an easy, mostly, and free way around the problem you could switch to Google voice as your voicemail. Fairly straightforward and bypasses any carrier interference.

New badge winners

Show all badges
Terms & Conditions