Pixel 7 Security Update

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! 

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:

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.

I sure hope tmobile isn't doing it for greedy purposes. Like they don't like visual voicemail built in. Or hold for me or clear calling.

I'm %100 sure when we do get a update. It's going to be a specific build for tmobile, fi, mint. 

If you go and look at the Android release list for Nexus and pixel phones. You'll see the first build is usually for all providers. Then at the end of the version. You'll see it branched out at some point. With carrier specific builds.

But I never seen it do this. Usually they release all the builds at the same time.

I have a Pixel 7 bought directly from the Google Store (unlocked).  I am using it on the T-Mobile network with an eSIM.  Like many others on T-Mobile, I had not yet received the January 2023 update (tried to force the OTA update again this morning using the 'Check for update' button) and was stuck on the December 5 2022 update.  I also have a physical SIM in my phone from a provider in Europe, which I use when traveling.  Most of the time this physical SIM is deactivated.

I did the following:

• Activated the European SIM and waited until it established a roaming connection to a local US mobile network (I think it even connected to the T-Mobile network)
•     Deactivated the T-Mobile eSIM and waited a couple of minutes to ensure the deactivation was complete (I did NOT erase the eSIM)
•     Went to System Update in settings and used the ‘Check for update’ button to see if the update would load
•     Immediately the January security update started downloading and installing.  It automatically paused (since I was using the phone) and I hit the 'Resume' button to continue the update.
•     After about 2 hours the installation process finished (I have a lot of installed apps, about 250, so the optimization takes forever)
•     Rebooted the phone and confirmed that under System Update the Android security update was showing as January 5 2023
•     Under SIMs I reactivated the T-Mobile eSIM and deactivated the physical SIM, T-Mobile connection appears to work fine, I am connected to 5G and I am receiving text messages

My conclusion is that there is a relationship between being connected to T-Mobile and not getting the January 5 2023 update. I cannot say if this is caused by T-Mobile or Google.

I was contacted by a T-Mobile customer support manager today regarding a complaint I had filed related to this issue.

He confirmed that T-Mobile has indeed delayed the roll-out of the January Andriod Security-Feature update due to a “bluetooth” issue. 

He anticipates a fix may be available in the February Android Security-Feature Update.   So there probably won't be a January Update for Pixel owners.

I suggested he post an annoucement or note on T-Mobile's website announcing the roll-out delay and reason why so Pixel customers will stop guessing and becomng upset.   He agreed…. but I'm not holding my breath if we'll ever see anything posted.

That's what I suspected , would have thought Verizon would have been the culprits as they are always slow to the game. Thanks for the info!

It looks like it's been pulled.

https://www.droid-life.com/2023/01/11/pixel-6-pixel-7-january-update-on-t-mobile-said-to-be-delayed-because-of-issue/

It's a staggered release for ALL devices. Doesn't matter the carrier involved when it boils down to the Pixel devices. It's not like the Nexus 6 and older devices. 
 

initially there will be a fork specific to a carrier for bug fixes which may affect other devices but it'll eventually come down to 1 source code when they find a better fix or see the fix won't break other devices. If you look at the factory images for an example. 

I have a 7 from Google and I don't hVe the January update and I am not bothered by it as I understand it's a staggered release. If I really wanted to I can install the OTA by side loading. 
 

tidbits wrote:

It's a staggered release for ALL devices. Doesn't matter the carrier involved when it boils down to the Pixel devices. It's not like the Nexus 6 and older devices. 
 

initially there will be a fork specific to a carrier for bug fixes which may affect other devices but it'll eventually come down to 1 source code when they find a better fix or see the fix won't break other devices. If you look at the factory images for an example. 

 

I have a 7 from Google and I don't hVe the January update and I am not bothered by it as I understand it's a staggered release. If I really wanted to I can install the OTA by side loading. 
 

 

Not true. Pixels can get the update OTA on demand as soon as it's released by Google as long as it's not being blocked by the carrier. I've had Pixels for years and this has always been the case. It's pretty clear from the discussions going on elsewhere that tmo has a problem with this build and is blocking the update. That being said, my P7 is on the December update and I'm fine with it staying that way until they work out whatever's wrong. If you're not, you can sideload the OTA from Google's site at your own risk. I'd rather not because I kinda need my phone to not be borked right now.