Forum Discussion
Pixel 7 Security Update
My Pixel 7 will not receive the January 2023 security update . Tried doing it manually and no luck, have heard it's a T-Mobile issue but that's just hearsay. Heard you can just pull your sim out and...
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:Bobaloo wrote:Spoke with a technical rep from T-Mobile and was told they do not block updates and that December is the latest update that they have. So my guess now is that it's a Google issue as they tried to connect me to Google and they were closed. Must have MLK day off so really nothing more to add to the story!
The updates come from Google. So tmobile doesn't need it. From what I have read. Google doesn't waite for approval each month. But they do allow carriers to request to block the update. Google won't send it to phones on that network. But I'm pretty sure Google wants a good reason. Like it causes issues with e911. Or some other network interference issue.
But you can see that the update was blocked right after the December update. That's why some people on TMobile are still on the November update.
Also the update button was never really broken. It would still check for updates. But would only see the update. If your device was eligible. Google always released the update over a few weeks in batches. So if your device wasn't in the batch for the day. Your check now button wouldn't see it.
And until either Google or tmobile makes a statement. We won't know anything.
This is pretty much my understanding as well, however if t mobile is requesting the block I feel like they could issue a statement to their customers before it's a huge issue every one is reporting on and such. I don't think Google is gonna have much to say, there's the known Bluetooth issues but that's being addressed and has definitely been publicly addressed, but it doesn't seem like whatever is holding this up is on their end given there was never a pull of the actual downloadable file, the beta is fine and it's only one carrier.
It's their CS playing hot potato with the blame and us being left in the dark that's so bothersome.
