Go to the Google page with pixel images, you’ll see for April/may some “A2” releases specifically for vzw and tmo.
These were created because the original releases had some sort of incompatibility with the networks.
If you weren’t affected it’s because of staged roll outs working as expected. Once google saw devices being affected the stopped the rollout. That’s why back in April people were complaining about late releases.
Can I get a cite, because I’m on ATT+Tmo and this is the first I’m hearing of it. Family too, 3 pixels all on tmo with no issues…
Go to the Google page with pixel images, you’ll see for April/may some “A2” releases specifically for vzw and tmo.
These were created because the original releases had some sort of incompatibility with the networks.
If you weren’t affected it’s because of staged roll outs working as expected. Once google saw devices being affected the stopped the rollout. That’s why back in April people were complaining about late releases.
Google: Verizon pixel update and you get a ton of threads for it. Here’s one example acknowledging it but not fully talking about it https://support.google.com/pixelphone/thread/270770116/2nd-pixel-april-update-needs-to-fix-all-cellular-network-issues-for-each-pixel-affected?hl=en
It’s the first thing I pulled up I don’t have time to go backwards on a known topic.