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 put another one in and it will update haven't tried that one yet.
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
fireguy_6364 wrote:
xblackvalorx 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!
That's a flat lie from them.
Literally only one carrier and it's connected carriers are having this issue. I can't find one singular t mobile phone that has updated to the January update without outside assistance across here, Reddit and xda. Literally every other carrier anyone who goes to check it's there.
it was also literally mentioned above that it was reported that Google Fi devices were having issues after the update and they run on TMOs network. gonna go out on a limb and say if the Google Fi devices are having issues then so is whatever update variant they have for TMO devices..if this is the case then theres your delay.
If it was the image from Google having issues they'd pull it and we couldn't side load.
Why are you all so desperate to take the blame off t mobile?
Google it. Every Android focused news sources has been reporting it as a t mobile issue for days. Some t mobile phones aren't even updating past November. Stop trying to protect t mobile and hold them accountable
xblackvalorx wrote:
fireguy_6364 wrote:
xblackvalorx 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!
That's a flat lie from them.
Literally only one carrier and it's connected carriers are having this issue. I can't find one singular t mobile phone that has updated to the January update without outside assistance across here, Reddit and xda. Literally every other carrier anyone who goes to check it's there.
it was also literally mentioned above that it was reported that Google Fi devices were having issues after the update and they run on TMOs network. gonna go out on a limb and say if the Google Fi devices are having issues then so is whatever update variant they have for TMO devices..if this is the case then theres your delay.
If it was the image from Google having issues they'd pull it and we couldn't side load.
Why are you all so desperate to take the blame off t mobile?
Google it. Every Android focused news sources has been reporting it as a t mobile issue for days. Some t mobile phones aren't even updating past November. Stop trying to protect t mobile and hold them accountable
I don't see any proof offered.that clearly shows that T-Mobile is to blame. Why are you so insistent on blaming T-Mobile when others have pointed out that it also affects Google Fi?
syaoran wrote:
xblackvalorx wrote:
fireguy_6364 wrote:
xblackvalorx 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!
That's a flat lie from them.
Literally only one carrier and it's connected carriers are having this issue. I can't find one singular t mobile phone that has updated to the January update without outside assistance across here, Reddit and xda. Literally every other carrier anyone who goes to check it's there.
it was also literally mentioned above that it was reported that Google Fi devices were having issues after the update and they run on TMOs network. gonna go out on a limb and say if the Google Fi devices are having issues then so is whatever update variant they have for TMO devices..if this is the case then theres your delay.
If it was the image from Google having issues they'd pull it and we couldn't side load.
Why are you all so desperate to take the blame off t mobile?
Google it. Every Android focused news sources has been reporting it as a t mobile issue for days. Some t mobile phones aren't even updating past November. Stop trying to protect t mobile and hold them accountable
I don't see any proof offered.that clearly shows that T-Mobile is to blame. Why are you so insistent on blaming T-Mobile when others have pointed out that it also affects Google Fi?
Google Fi is t mobile LMAO
And I'm just being factual. If the issue is isolated to t moving devices, yes it's a t mobile issue.
As I've said, there's a reason every single Android media source is reporting it as such. You can track every platform and at this point nearly all other devices have auto updated, and t mobile (and it's smaller carriers) users still have nothing.
Also again, some users are also still stuck on November. T mobile clearly has an issue with updates and it'd help all of us to at least be real about that
if the issue is causing network issues with the TMO variants of this device AND the Google Fi devices then its safe to say whom must be the one to fix it..which isnt TMO..they dont create the patches nor do they fix them..those come directly from Google..
those same security patches get passed from Google to the OEMs so they can adjust them to their devices and then kick them out..no carrier makes those adjustments..
fireguy_6364 wrote:
if the issue is causing network issues with the TMO variants of this device AND the Google Fi devices then its safe to say whom must be the one to fix it..which isnt TMO..they dont create the patches nor do they fix them..those come directly from Google..
those same security patches get passed from Google to the OEMs so they can adjust them to their devices and then kick them out..no carrier makes those adjustments..
Again if this were the case they would have pulled the ota image so people couldn't side load. Also if that were the case there would be issues with the beta on t mobile.
Google is also much more transparent about this stuff. They wouldn't just no comment like this. Lol.
It's a t mobile issue, you don't know more then Android police, phone arena, XDA, Droid life etc etc.
I recently switched from Verizon to T-Mobile. My experience with T-Mobile has been positive until now.
I purchased an Unlocked Pixel 7 Pro and have been waiting for the January Google Security Update. As of 10 minutes ago, Jan 15 at 12:06 PM no January update is available.
I contacted T-Mobile support regarding this issue and they had no answer. One T-Mobile representative stated the issue rests solely with Google and that I should contact them.
I filed two (2) formal written complaints with T-moble management regarding this issue, though I doubt it will make a difference.
If T-Mobile has indeed delayed the January 2023 Google Security Update, then T-Mobile should let their customers know and why the January Update is delayed. Also, they should let customers know when to expect the update to roll-out.
IMHO this is just terrible and crappy customer service by T-Mobile. Now I'm a disappointed customer.
raisinbrann wrote:
I recently switched from Verizon to T-Mobile. My experience with T-Mobile has been positive until now.
I purchased an Unlocked Pixel 7 Pro and have been waiting for the January Google Security Update. As of 10 minutes ago, Jan 15 at 12:06 PM no January update is available.
I contacted T-Mobile support regarding this issue and they had no answer. One T-Mobile representative stated the issue rests solely with Google and that I should contact them.
I filed two (2) formal written complaints with T-moble management regarding this issue, though I doubt it will make a difference.
If T-Mobile has indeed delayed the January 2023 Google Security Update, then T-Mobile should let their customers know and why the January Update is delayed. Also, they should let customers know when to expect the update to roll-out.
IMHO this is just terrible and crappy customer service by T-Mobile. Now I'm a disappointed customer.
Get used to it. T mobile hasn't been the same since legere left as CEO. They'll make stuff up, give you a different answer every time you call and just pass the blame.
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.
