June Pixel security update delayed

released on the 13th to whom? to carriers to do their test before giving the ok to kick it out? so youre trying to say that carriers create the security patches? so per you TMO is the one that creates the security patch for all the devices on their network?

amd weird that im not the only one that pointed right back at Google in here lol

Even though the update comes from Google. Att tmo and Verizon can say no. It's always been like this. 

The last time tmo had a delay.it wa also for a big feature drop. Just like now. I'm thinking tmo is short staffed and it just takes longer.

Not the way you think. They can't free nilly say we'll delay the update. It has to be something like a bug or security flaw that affects their networks. 

Also it's up to Google to point it out like they did the last time there was a delay because of it. 

pixel12a wrote:

Even though the update comes from Google. Att tmo and Verizon can say no. It's always been like this. 

The last time tmo had a delay.it wa also for a big feature drop. Just like now. I'm thinking tmo is short staffed and it just takes longer.

no arguments on this one.. correct..if an issue is spotted they can shut it down until its fixed. but it’ll depend on what the problem is..the last one with the BT issues i can see having to hold it off.. everyone just thinks “cant listen to music” but in reality..it removes hands free use while driving. it didnt effect every carrier but its still an issue that must be fixed since in most states you must remain hands free while driving or its ticket time.

has to be a big enough issue to halt it..

Yeah. T-Mobile already have a bad reputation in regards to updates with Pixel phones. "If" they are preventing the update they should at least announce it and why. 

I wonder what would happen if you brought your unlocked phone over would they still block the updates?

I have unlocked 7 and 7 Pro. One on Verizon and one on T-Mobile. 

I actually side loaded the update on both of them and I know why it was delayed. It's very obvious and even more obvious if you are in a low reception area. 

At my house I have strong signal and my speeds are 1500+Mbps. After update moderate to weak signal and 300+ mbps. I have to restart to get the signal back up and it'll only last about 15 minutes. 

SeePower wrote:

Yeah. T-Mobile already have a bad reputation in regards to updates with Pixel phones. "If" they are preventing the update they should at least announce it and why. 

Google last delay said what the delay was.  It wasn't because T-Mobile didn't want to give the update…

Google did the same thing when Verizon didn't get an update because of issues.  If it's bad enough Google WILL fork the update and reintegrate it the next update.  It's nothing new.

My cell service sucks right now as sometimes I have to redial a number because no service. Hopefully when they get the update right my service will be better.

I can say this update makes me have worse reception. 

I wish I took screenshots before the update of speeds and reception. Right now I have to turn off the sim then turn it back on to get full reception again and back to my original speeds. After about 15 minutes it'll go back down. To about 1/4 to 1/2 and my speeds drop significantly. If someone has worse than what I have and this is in fact the reason they would not have reception. I reverted back to the May Factory Image and all is normal again. 

I've already sent logs to Google engineers. Note this doesn't happen in Android 14 beta thankfully.