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.
tidbits wrote:xblackvalorx wrote:Update notifications are staggered but you can pull manually with the check for updates button. "I've had every pixel" cute, I've been developing aosp roms and kernels since the HTC G1.
Yes carriers can block updates, have some control etc but they are typically available simultaneously across Google devices.
Oh ya I also have 3 in the house right now. Been around this block a time or two. Also, if you look through every forum, Reddit post and even articles all saying reports are only from T mobile users it's probably a carrier side thing. This is basics.
Now that that's out of the way, the 15th has come and go. I definitely plan to contact t mobile tomorrow and ask why my phone is months behind on security updates. I do banking and other things on my phone which I'd like regular security updates for. Part of why I bought a pixel.
As I said before there's a reason why you have the OTA file. That's is what Google meant by day one if you don't want to wait you can install the OTA on your own. There's no different whether if you get it from "T-Mobile", Google, or Jesus himself it's all the same file. If you actually do rom development I don't see someone waiting for an update they deemed important.
I can tell you it's Google's own code that is causing problem if you looked at it. IF you actually notices since 4.0 Google head office AND lead developers have never blamed carriers for delays. You only here it from people AND Google customer service reps who have no workings in other departments. Of course you don't have to believe me. It's how Google doesn't want all the traffic on their servers vs Apple willing to take all traffic regardless of bricked devices that can and do happen.
Ok but then why is it only effecting t mobile devices? And why are some still on the November update? Only t mobile? Literally every reputable Android News site is reporting on this. You work for t mobile or something? Lol
