User Profile
nokisme
Transmission Trainee
Joined 6 years ago
User Widgets
Contribuciones
Re: Android Native Visual Voicemail Trouble
The suggested off and on isn't working for me at all. I tried over 20x's and still nothing. I paid off the phone so I'm probably gonna jump ship and try Google Fi at this point. My hopes were high after reading your posts about it suddenly working but I'm thinking of upgrading to the pixel 3 xl and I'm worried that I'll go through this same headache all over again if I do.2Visto0likes0Comentarios- 1Ver0likes0Comentarios
Re: Android Native Visual Voicemail Trouble
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...) I'm waiting for from my credit to pay off my phone. If this isn't resolved by then, I will be hopping carriers till I'm happy. Google Fi is next on my list.2Visto0likes0ComentariosRe: Android Native Visual Voicemail Trouble
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.2Visto1like0ComentariosRe: Android Native Visual Voicemail Trouble
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.2Visto0likes0ComentariosRe: Android Native Visual Voicemail Trouble
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 voicemail1Ver1like0ComentariosRe: Android Native Visual Voicemail Trouble
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.2Visto1like0ComentariosRe: Android Native Visual Voicemail Trouble
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.1Ver0likes0Comentarios