[radgatt]

I have had my update since June 5. Unlocked Pixel XL on Verizon.

[Easton091]

Still nothing here. Must be a issue with project Fi?

[Lilybell2]

I have build NKG47L for Pixel (sailfish) (T-Mobile)

Thanks! NKG47L is also the build listed for the Pixel XL for users of T-Mobile, Fi Carriers, and Rogers. It seems like most of the complaints I've seen from those who have not yet received the June update have come from users on Project Fi. So, if your experience is typical, it would seem that T-Mobile users are not having a problem with that build.

I'm beginning to wonder if there's some sort of glitch with Project Fi. I know this sort of problem has come up before with Fido and with Rogers.

Are there any Pixel/Pixel XL/Project Fi users here who have received build NKG47L? If so, did it come OTA or did you sideload it?

[gsolis31]

Just did a manual check and finally getting the update on Fi.

EDIT: after restart, can confirm the Build number on Fi is also NKG47L.

[Lilybell2]

Thanks! Looks like all of a sudden the dam has burst and build NKG47L is coming to Project Fi users. It's installing on my Pixel XL right now.

[kjharrison]

Finally getting the June update as I type this!!! Project Fi! 58.7 MB Yahoo!

[kjharrison]

Still nothing here. Must be a issue with project Fi?

You should be getting it soon.

[vansmack]

You're all welcome. I finally broke down and sideloaded this morning, so OF COURSE Fi starts sending out the OTA en masse today...

[Easton091]

You should be getting it soon.

Yup someone on fi forums posted that he spoke with fi and all of a sudden the update came. I checked at same time and got it along with a bunch of others.

[vjfratiani]

I'm in the same waiting boat still on June 27.
I switched my unlocked Pixel I bought directly from Google, from Verizon to Project Fi last month.

I'm concerned that because I am running a Verizon build of the OS that the update servers are rejecting my device update requests now that I'm on a different carrier. I hope that's not the case.

Google support and Fi support haven't been able to give me an answer other than refer me to manually flash my phone with the update. My device appears to be one of the batch of Pixels with the intermittent freezing issues. Though support wants me to park my device in safe mode for a few weeks to see what happens.

Nobody has time for that.

Alas, I'm hoping that contacting support will jump start the process.

If all else fails, I can hope I get a massive rollup pushed to my device with the July update...

[Lilybell2]

I wouldn't wait any longer. You're on Project Fi so just sideload build NKG47L. That's exactly what I was going to do if I didn't receive the June update before the end of the month.

[radgatt]

I'm surprised so many people are having issues getting this patch. Is it a Verizon issue or a Google issue? I'm on Verizon but I got my phone from Google. I'm on the latest security patch.

[vjfratiani]

Is sideloading the OTA update a destructive or non-destructive update?
The nice thing about the actual OTA updates is that I don't have to start over from scratch. It's the main reason I've avoided flashing an image manually.

[Lilybell2]

Is sideloading the OTA update a destructive or non-destructive update?
The nice thing about the actual OTA updates is that I don't have to start over from scratch. It's the main reason I've avoided flashing an image manually.

Sideloading the OTA zip file is non-destructive: https://developers.google.com/android/ota

[vjfratiani]

So I updated by sideloading the OTA, but now I get an intermittent issue where the headphone jack stops working. Audio just stops coming through. I have to reboot in order to get headphone audio back. Anyone else experiencing this in the June update? Starting to wonder of that had anything to do with why the update was never pushed to my device.