Pixel 7 Security Update

I just downloaded my wife's Pixel 7 update. Did my update on my Pixel 6 yesterday.

Checked for updates on 7 February for unlocked Pixel 7 T Mobile and downloaded and installed February 5 update successfully - no swapped SIM or sideload, just standard update.

I have a Pixel 6 with the December update I bought my wife a Pixel 7 in November that stuck on the November update. That phone replaced a Pixel 5a5g that's also stuck on the November update and it was purchased through Google while the other 2 were bought through Tmobile.

If you don't mind bugs enroll in the Google developer program, the updates are there but beware if you decide you don't like it and you roll back the OS it will wipe your phone.

Yes it does but if the data breach was causing the delay of the Pixel update don't you think every phone on

gramps28 wrote:

wsb_cal wrote:

Doesn’t Google Fi also use T Mobile’s network, among others? Were there Bluetooth issues with the December update causing it to be pulled? I have that update installed and have  had no problems with either headphone or automobile Bluetooth connectivity….

Yes it does but if the data breach was causing the delay of the Pixel update don't you think every phone on the Tmobile network would have their updates delayed as well.

Very good point. At this late date in January let’s hope the February 2023 update will materialize for Pixel phones (although if it’s a single update it may be huge and complex)...

wsb_cal wrote:

Doesn’t Google Fi also use T Mobile’s network, among others? Were there Bluetooth issues with the December update causing it to be pulled? I have that update installed and have  had no problems with either headphone or automobile Bluetooth connectivity….

Yes it does but if the data breach was causing the delay of the Pixel update don't you think every phone on the Tmobile network would have their updates delayed as well.

Doesn’t Google Fi also use T Mobile’s network, among others? Were there Bluetooth issues with the December update causing it to be pulled? I have that update installed and have  had no problems with either headphone or automobile Bluetooth connectivity….

wsb_cal wrote:

Could be a security issue. There was a major T Mobile data breach around 25 November 2022 (https://www.theverge.com/2023/1/20/23563825/tmobile-data-breach-api-customer-accounts-hacker-security). It probably took them a while to discover the breach, thus accounting for pulling the December update midstream.

They could be busy fixing the security infrastructure on their hardware and/or making sure the phone security updates don’t propagate/expose the flaw. 

No wonder they’re so close-mouthed...

It has nothing to do with the security breach but more to due to Bluetooth connectivity. It's also occurring on the Google Fi network.

Could be a security issue. There was a major T Mobile data breach around 25 November 2022 (https://www.theverge.com/2023/1/20/23563825/tmobile-data-breach-api-customer-accounts-hacker-security). It probably took them a while to discover the breach, thus accounting for pulling the December update midstream.

They could be busy fixing the security infrastructure on their hardware and/or making sure the phone security updates don’t propagate/expose the flaw. 

No wonder they’re so close-mouthed...

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!

JNavas wrote:

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.

1. It’s more likely the time necessary to modify and fully test code, which is significant,
2. It won’t be a specific T-Mo build for factory unlocked phones (like mine).
3. It’s more likely a functional issue specific to the T-Mo network than something T-Mo wants removed or blocked.

The problem is there are countless of T-Mobile pixel 6 and 7 owners who haven't received the November update. Who's holding that back? If you opt into the QPR2 beta you'll receive the January 5th update including the spatial sound for Pixel Pro buds. If you're an AT&T customer you already have the entire January 5th update. You always have been able to opt out of a Beta except this one if you're carrier is TMobile. You should all check out Reddit and YouTube to find out who's stopping the update.