where's the June OTA update?

[maverick7526]

sideloaded mine by 11:30 CDT yesterday. Sideload people, sideload........https://developers.google.com/android/ota

you shouldn't have to sideload. That's the whole point of them "fixing" the check for update button. Now that it's broken, again, I'm getting shades of Dec when the OTA was killing cellular reception. Some people on reddit are saying OTA's are breaking the FPS, and some other features. Google really can't get out their own way with this phone. We should all get a discount code for a Pixel7 at this point since we all paid to be in the Beta for Tensor.

 

[Zedd]

No 13 beta for me, but no update either. Odd that they borked the update button again. Frustrating since Samsung had already gotten the June update out, but Google can't seem to get it right.

No beta tester here either, I just read the Galaxy 22 is getting the June update now. Why isn't Google's flagship phone, Pixel 6 Pro not the first phone getting any updates?
Google's Tensor chip is my guess.
I've owned the 2XL and the 4XL, both got their updates first Monday of the new month, not so with my Pixel 6 Pro. I'm not seeing what's PRO about this phone anyway. They have been buggy since they came out and still are. This will probably be my last Pixel phone for some time to come!

 

[Zedd]

I 100% agree!!

 

[cache11]

I have the 6, 5a and 4a and no update yet.

 

[Tool_Belt]

Correct, you should not....have to........but it is an easy option nonetheless and is much quicker than doing it OTA.

 

[rvbfan]

My 6 updated yesterday also my son's 4a. Both only took one press of the update button. Nothing as far as I can tell so far is broken in fact, FPS may be working as well as in 13 beta 2.

 

[maverick7526]

Correct, you should not....have to........but it is an easy option nonetheless and is much quicker than doing it OTA.

I guess, but last time this happened it was because Google broke something, then was disingenuous about it until the end of the month when they finally pulled the OTA/Factory images. It looks like they broke something again, from all the hubub on reddit.

 

[gendo667]

Nothing here. Pixel 6 purchased through T-Mobile.

 

[Tool_Belt]

My P6 unlocked is working fine with the update.

 

[maverick7526]

My P6 unlocked is working fine with the update.

That was the same kind of issue with the Dec update. It didn't break everyone's phone, however a lot of the OTA people had issues. Most who sideloaded did not. You sideloaded June if I remember right? Barely anyone in the US seems to have received the OTA, unless they were in the Beta for 13. It's another kerfuffle from Google. I would say I'm shocked but.....

 

[Tool_Belt]

I have side loaded all but two updates. The first one, then I spaced out and let May do an OTA....geesh....took for ever...

 

[Davidoo]

Correct, you should not....have to........but it is an easy option nonetheless and is much quicker than doing it OTA.

Yes, but there must be a problem with it or it would be released. Do you really want to update to something that is probably causing a problem and the reason it isn't released?

 

[Tool_Belt]

If it was funked up wouldn't they take it down off this site?

https://developers.google.com/android/ota

Mine is working fine.

 

[dmpaul77]

It was not taken down in the last borked release.

 

[Tool_Belt]

Let us know when you get it in the next day or two and see that it runs fine.

 

[Davidoo]

It was not taken down in the last borked release.

Your right, it wasn't. Was that in December? They pulled the OTA but left the bad version available on their website for several days before finally pulling it and announcing the delay.

 

[Tool_Belt]

So, the update is bad because 10 people on this thread have not got it, yet doing a web search there are no reports of the update being bad. What am I missing?

 

[Deleted member 2609113]

So, the update is bad because 10 people on this thread have not got it, yet doing a web search there are no reports of the update being bad. What am I missing?

It's a staggered rollout. I may be wrong but I'm guessing the A12 Pixels in the US and possibly Canada will get it tomorrow, Wednesday the 7th.

 

[maverick7526]

So, the update is bad because 10 people on this thread have not got it, yet doing a web search there are no reports of the update being bad. What am I missing?

No it's bad because they won't let you pull the ota like you have been able to do for the last 5+years by using check for update button.

The same thing happened in Dec. They left the files up on the developers site but disabled the update button. Then literally the 2nd to last day of the month pulled the files and announced something was wrong with the update.

I would check Reddit. People are reporting problems there after updating. Some say the FPS is now broken and nothing besides maybe factory resetting will fix it. Some say wireless charging is broken now. I wouldn't say it widespread, but there has to be a reason the check for update button is disabled.

Plus those that side loaded Dec didn't experience as many issues as the few that got ota's. Maybe there's something in the ota process that's bricking features that doesn't happen if you side load. It's Google, they won't be forthcoming with any information anyway

 

[Davidoo]

It's a staggered rollout. I may be wrong but I'm guessing the A12 Pixels in the US and possibly Canada will get it tomorrow, Wednesday the 7th.

Not trying to be argumentative, but it's never been a staggered rollout before for Pixels, and I've had them since the OG 1XL. The day it is released and people verify they are receiving it, then you can manually push the update button and there it is. There must be a reason they have disabled the update button. I haven't seen a report of any person with a Verizon P6 or Pro that got it, and TMobile users say they don't have it either.