Pixel 7 Security Update

Yes, because Google delivers updates, it’s a Google issue.

Has it not occurred to you that there are likely issues in the update that are unique to the T-Mobile network? Because if so, then Google would need to fix the issues and reissue the update, or skip updating until a good later update.

It’s more likely that T-Mobile reported issues to Google than that T-Mobile simply told Google not to update T-Mobile Pixel devices.

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.

Unfortunately once your phone is registered with a sim its tied to that carrier. Google wont update your phone. You'll either have to insert a different sim or factory reset with no sim.

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

xblackvalorx wrote:

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

I usually don't do the developers program till the 14 beta rolls out. Your security updates will be sporadic and updates won't be on the 5th from previous experience. Also if you decide to roll back the update your phone will reset to factory settings.

I usually enroll in June when it's a little more stable. Good luck and let us know how the beta is.

I feel it would be prudent for T-Mobile to release a statement as all the speculation is bad for the T-Mobile brand and Google's for that matter. I rely on my phone, so I hesitate to side load unless I understand the issue. I can wait, but this is not the customer service I expect.

Regards to all 

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. 

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...

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:

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.

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)...