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:xblackvalorx wrote:JNavas wrote:No, without the SIM, T-Mobile is not in the update path. The connection is directly to Google over Wi-Fi and the Internet without T-Mobile. It's Google that's not providing the update. That might be due to a T-Mobile request, but it's still Google doing the updates.
"The updates might be held at t mobile request but it's title that does the updates"
So if t mobile makes Google block it, we still call it a Google issue?
Nah seriously all you guys defending this sound paid. Just making up weird reasons to take the blame off t mobile when nobody is asking for that. Nobody in this thread who's actually trying to get to a fix for their problem cares to sit here listening to randoms defend t mobile and not contribute.
So again, please, to everyone, if you are just here to try to get people not to blame t mobile for what they're doing just save it. We don't care. Nobody cares. Y'all are just disrupting this forum coming in to defend a giant corporation for no reason when nobody asked. It's weird and annoying.
I agree but this is a tmo forum. So we should only expect some defending of tmo. I have been with tmo since 2003. Back when bring your own phone was something you had to ask about in the store. Just to get special pricing. Tmo is the better of the 3 by far.
But I'm 100 percent sure this block is at tmo request. And tmo requested it as the december update was going out. That's why some are stuck on november. So it couldn't be because of the supposed bluetooth bug. That didn't pop up until the January update. If this was a issue with network interference or e911 incompatibility. We would see bug issues on the android developer site. It would be a work in process to get it fixed. Its quite on the android developers forum. Just unrelated bug discussions in progres for february update
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.
For what it's worth the beta is solid, and largely takes tmo out of the update process for real. I'm very happy I updated and have a fully featured build because I share the same suspicion
