User Profile

carrierlost

Transmission Trainee

Joined 6 years ago

15 Publicaciones6 Likes

View All Badges

User Widgets

Contribuciones

Re: Android Native Visual Voicemail Trouble
I'm now also in the "magically started working" camp. Go figure. We put up enough data and evidence, TMo finally seems to have gotten it SORT OF fixed.
6 years ago Place Android
2Visto
1like
0Comentarios
Re: Android Native Visual Voicemail Trouble
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.
6 years ago Place Android
1Ver
1like
0Comentarios
Re: Android Native Visual Voicemail Trouble
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.
6 years ago Place Android
2Visto
1like
0Comentarios
Re: Android Native Visual Voicemail Trouble
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.
6 years ago Place Android
1Ver
1like
0Comentarios
Re: Android Native Visual Voicemail Trouble
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.
6 years ago Place Android
1Ver
1like
0Comentarios
Re: Android Native Visual Voicemail Trouble
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!
6 years ago Place Android
6Visto
1like
0Comentarios

Grupos