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.
So, I get that things happen and sometimes there is a delay. However, I don't get the lack of communication from T-Mobile and\or Google. Someone, somewhere knows something. And without communication, how will we know if it's just an issue with our phones? What if it turns out that some flag got set on our phones that tells Google's servers that our phones are up to date? We would have waisted a month waiting for them to fix something that isn't broken and they aren't working on...and we just needed to manual side-load the update to reset the flag. Within communication, there's no way to be sure we should wait or we should side load it. Very frustrating, IMO!
Contenido relacionado
- Hace 3 meses
- Hace 18 días
- Hace 20 días