January update

Toggle sidebar Toggle sidebar
PGrey said:
Except on the T-Mobile branded devices, I don't think there's any way for T-Mobile to do that, other than for them to negotiate with Google (who provides the images), to block in the interim, for devices on their network (or Fi, Mint, etc, whichever MVNO).

This would be akin to say Dell asking MS to not release updates to their "XYZ laptops", due to a cache bug in the chipsets. This does happen, in reality, to some degree, but it'd be more along the lines of say Intel, AMD, ASUS, etc., working with MS to fix before deploying, based on the chipsets.

Just wanted to clarify, that T-Mobile can't really "gate" the updates, on phone SKUs they don't deploy (OS) to.

It's an annoyance, but likely a lot better than the alternative...
Click to expand...

Thats not really true. Many more times than I can count since I've had Pixels since the OG 1, I didn't get the update on the first Monday like all other carriers did because Verizon held it for some reason. Multiple times for the Pixel 6 Pro Verizon held the update and added things to it to get their C-band frequencies and finally give us 5G UW. This just happened again in either October or November of 21 when those of us on VZW had to wait a week for it.

So now T-Mobile has their time to hold one up as there are many articles since the January update was released on 1/3 that they found an issue with their network and are holding it up. These updates still have to be vetted by the carriers before anyone can get the OTA. My fiance has an unlocked P7 Pro on T-Mobile and still doesn't have the update for January while I got mine on the same device on VZW on 1/3.
 
Davidoo said:
Thats not really true. Many more times than I can count since I've had Pixels since the OG 1, I didn't get the update on the first Monday like all other carriers did because Verizon held it for some reason. Multiple times for the Pixel 6 Pro Verizon held the update and added things to it to get their C-band frequencies and finally give us 5G UW. This just happened again in either October or November of 21 when those of us on VZW had to wait a week for it.

So now T-Mobile has their time to hold one up as there are many articles since the January update was released on 1/3 that they found an issue with their network and are holding it up. These updates still have to be vetted by the carriers before anyone can get the OTA. My fiance has an unlocked P7 Pro on T-Mobile and still doesn't have the update for January while I got mine on the same device on VZW on 1/3.
Click to expand...
They’ve held up more than one.

My Other Half’s 5a still doesn’t have the December update.

This does not make one think that a fix has a very high priority at TMO.
 
Davidoo said:
Thats not really true. Many more times than I can count since I've had Pixels since the OG 1, I didn't get the update on the first Monday like all other carriers did because Verizon held it for some reason. Multiple times for the Pixel 6 Pro Verizon held the update and added things to it to get their C-band frequencies and finally give us 5G UW. This just happened again in either October or November of 21 when those of us on VZW had to wait a week for it.

So now T-Mobile has their time to hold one up as there are many articles since the January update was released on 1/3 that they found an issue with their network and are holding it up. These updates still have to be vetted by the carriers before anyone can get the OTA. My fiance has an unlocked P7 Pro on T-Mobile and still doesn't have the update for January while I got mine on the same device on VZW on 1/3.
Click to expand...

This is absolutely correct.
 
Last edited:
At this point were getting closer to Feb, so hopefully by then they figure it out. Pretty disappointing really.
 
Can the security parts of the update be split off and sent out by Google, so the providers can’t tinker with them?
 
Maljunulo said:
Can the security parts of the update be split off and sent out by Google, so the providers can’t tinker with them?
Click to expand...
Most likely not because it's rolled all up into one with carrier enhancement and Google security, can it be done probably but it's not how it's done as probably too much work to separate them and send multiple updates for a given device in a month. They do this for apps but not software updates .
 
Not IME, but I'd really like to understand the architecture/flow, if you've got anything.

Say if I take my same phone, and throw a VZW SIM it, tomorrow, and maybe possibly reset it (I doubt this 2nd part is necessary, but I'd have to figure out where the carrier settings are in the tree, or if these are even all public).
Boom - Zip, you have the update, and it came from whom exactly, VZW? :confused: :)
I could also probably sanitize the carrier info (no SIM, just direct to Google distro servers), without the 2nd SIM, and produce the same result, but it'd take a bit of digging, again.
Yes, the carrier has testing going on in-concert with releases, and yes there's some flag they can set, but I still bet they have to negotiate this out. TMo can't just block your updates to the phone they have no stake in, indefinitely, right?

If you have a pointer to some spec/code that explain the depth part here, particularly how a carrier would do this, outside of working w/Google, I'd be very interested to see, truly.
Maybe I'll go dev-docs spelunking a bit tomorrow, depending on time, who knows, maybe I'm way off in the weeds here and using dated release methodology experience.
 
Fiddle sticks! Has to be fiddle sticks.

Sent from my Pixel 6 using Tapatalk
 
X1tymez said:
I guess there's nothing for January.

Sent from my Pixel 7 Pro using Tapatalk
Click to expand...
No update for me. On Fi in California. I think whoever said this before was correct, they pulled it because it was interfering with some people's Bluetooth connections. We probably won't get the update till February.

Sent from my Pixel 7 Pro using AC Forums mobile app
 
Last edited:
Tomster88 said:
No update for me. On Fi in California. I think whoever said this before was cracked, they pulled it because it was interfering with some people's Bluetooth connections. We probably won't get the update till February.

Sent from my Pixel 7 Pro using AC Forums mobile app
Click to expand...
That's what I'm reading too. Oh well...

Sent from my Pixel 7 Pro using Tapatalk
 
You must log in or register to reply here.

Similar threads

mustang7757
January 2nd update
Replies
6
Views
647
Google Pixel 9, Pixel 9 Pro, & Pixel 9 Pro XL
Hardhat Harry
Hardhat Harry
AC News
News OnePlus 13 vs. Google Pixel 9 Pro XL: To buy a Pixel now, or to wait for OnePlus?
Replies
3
Views
645
Android Central News Discussion
Laura Knotek
Laura Knotek
ironass
vivo X Fold3 Pro Global-MAY update
Replies
2
Views
1K
General News & Discussion
ironass
ironass
D
January Update Issue (Maybe?)
Replies
0
Views
508
Samsung Galaxy S24 Series
Dee74
D
ironass
vivo X Fold3 Pro Global-APRIL update
Replies
0
Views
1K
General News & Discussion
ironass
ironass

Latest posts

Trending Posts

Members online

Total: 1,495 (members: 8, guests: 1,487)

Forum statistics

Threads
955,772
Messages
6,965,774
Members
3,163,393
Latest member
Spud12345678

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom