Forum Discussion
Pixel 7 Security Update
- Hace 2 años
pixel12a wrote:
So that only leaves something behind the scenes. Something tmo and google are hashing it out. Its got to be something that the two cant agree on. I highly suspect something feature related. I keep saying I think tmo wants something removed or blocked?
We're just going to have to wait it out. Once we do get a update. I'm pretty sure it will be a specific android build for tmo. We can pick it apart then and look for whats different.
- It’s more likely the time necessary to modify and fully test code, which is significant,
- It won’t be a specific T-Mo build for factory unlocked phones (like mine).
- It’s more likely a functional issue specific to the T-Mo network than something T-Mo wants removed or blocked.
pixel12a wrote:Both my wife and I are on the January update.after forcing it. Pixel 6a and 7. No issues with Bluetooth. Android auto is fine Ford pickup and Honda. And Anker headphones and Anker sound bar.
...
I have a feeling it has to do with visual voicemail. I had lots of issues with this. It always worked fine going all the way back to my Nexus 6. It only stopped when upgrading to the pixel 7. I had to call in many times. To get it to work they finally had to provision my account to a older plan??
...
I forced the January update to my Pixel 7 as well yesterday (see above). Experience thus far:
- No issues with Bluetooth (Volvo, Mazda, Android Auto, office access, smart watch, ear buds, etc.)
- Visual Voicemail (T-Mobile app) has stopped syncing after the update. Last sync is from Monday January 16 before I forced the update. I uninstalled the app and will try to use the Google visual voicemail service. Not that important for me (I get very few voicemails).
Contenido relacionado
- Hace 3 meses
- Hace 18 días
- Hace 20 días