Pixel 7 Security Update

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 

So I have Tmobile with an E-sim and it would not update.  So I plugged an ATT sim in from my work phone and disabled the Tmobile e-sim and did a manual update and it worked.

One consistent theme is, no one has definitive, accurate knowledge. There is a lot of speculation and opinions, and of course, I have my own. I do not think T-Mobile and Google would inhibit an update simply for giggles and grins. What would be the benefit? Yes, you can get around it, and a beta build seems to work, but why would you? Could it be a security issue, a problem with T-Mobile's new 1900 MHz rollout; again no one knows. People seem to be so demanding. Of course, I myself like updates, but I actually appreciate an update held if there is a issue with it. My Pixel 7 Pro is operating just fine. If I would fault Google or T-Mobile, I think a generic statement should have been released. But I am not going to lose sleep over it. It will be known in good time. There is no reason not to be kind to everyone. As I mentioned in the beginning, it is all speculation. Relax and have a great day! 

pixel12a wrote:

Plus the silence speaks volumes. If Tmobile was protecting us or its network. You would think there would be a official response."Hey our Tmo engineers found a issue with E911. Expect a slight delay while we work with google" Or "We noticed that your not getting your updates. Were working with google to get to the bottom of this" Something, anything its just silence.

• Not commenting on reworking a security update is normal. This is no big deal.
• Disclosure is only necessary when there is a widespread problem, which isn’t the case here.

Plus the silence speaks volumes. If Tmobile was protecting us or its network. You would think there would be a official response."Hey our Tmo engineers found a issue with E911. Expect a slight delay while we work with google" Or "We noticed that your not getting your updates. Were working with google to get to the bottom of this" Something, anything its just silence.

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.

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:

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.

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.