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.
raisinbrann wrote:I was contacted by a T-Mobile customer support manager today regarding a complaint I had filed related to this issue.
He confirmed that T-Mobile has indeed delayed the roll-out of the January Andriod Security-Feature update due to a “bluetooth” issue.
He anticipates a fix may be available in the February Android Security-Feature Update. So there probably won't be a January Update for Pixel owners.
I suggested he post an annoucement or note on T-Mobile's website announcing the roll-out delay and reason why so Pixel customers will stop guessing and becomng upset. He agreed…. but I'm not holding my breath if we'll ever see anything posted.
Yup. I'm actually currently in the process of installing the QPR2 beta and this is why.
A tiny number of people using Android auto are having music issues so I'm months behind on the security updates that protect my banking info. Not a great priority set and I don't want T mobile controlling my updates. Half the reason to own a pixel
Contenido relacionado
- Hace 3 meses
- Hace 18 días
- Hace 20 días