November Security Update (Also Saturation/Nav Bar Fade Update)

[Nauga]

According to this article from Android Police, there wasn't a KRACK fix in the update that is rolling out:

Google posts system images and OTA files for Pixel 2 XL November update, plus new builds for Pixel 2 [Update: No KRACK update]

A little more information about the "missing" KRACK fix and why it's not a BF deal, from Ron Amadeo @ Ars Technica:

https://arstechnica.com/gadgets/201...until-december-but-is-that-really-a-big-deal/

 

[cbreze]

Still waiting for the update, Verizon sim but unlocked P2. Since there is no Krack fix I'm not as concerned as I continue waiting. Curious why Verizon locked devices have gotten it sooner than unlocked Google devices tho. Would have thought it would be the other way around. Be interesting to see how future updates roll out.

 

[cyndie1030]

Still waiting for the update, Verizon sim but unlocked P2. Since there is no Krack fix I'm not as concerned as I continue waiting. Curious why Verizon locked devices have gotten it sooner than unlocked Google devices tho. Would have thought it would be the other way around. Be interesting to see how future updates roll out.

I agree. It's the main reason I chose an unlocked version since I don't root devices.

 

[Chex313]

Thanks for that link! That should be required reading for all Pixel owners.

There is no mention of why the carrier's approval, allow themselves to be circumvented if you are on the Beta..I would like to know that.

 

[nelamvr6]

Still waiting for the update, Verizon sim but unlocked P2. Since there is no Krack fix I'm not as concerned as I continue waiting. Curious why Verizon locked devices have gotten it sooner than unlocked Google devices tho. Would have thought it would be the other way around. Be interesting to see how future updates roll out.

It's just the normal roll out process. If Google allowed all of the devices that want the update to get it at the same time their servers would be swamped. It's not that all verizon devices got it, or that none of the non-branded devices got it. It's been a mix so far.

It's been posted before, but it bears repeating. Please read this, it will explain it better than I ever could: https://www.androidauthority.com/how-android-updates-roll-out-force-clear-gcf-318744/

You'll get it, no worries.

 

[nelamvr6]

A little more information about the "missing" KRACK fix and why it's not a BF deal, from Ron Amadeo @ Ars Technica:

https://arstechnica.com/gadgets/201...until-december-but-is-that-really-a-big-deal/

Thanks for the link!

 

[Nauga]

Woo-hoo! Finally, an update makes it through that steaming wall of Wuh? otherwise known as Project Fi! No lie, this is the first OTA I've received since November 2016. And I only had to spend $850 on a phone to get it!

And it's taking a full 15 minutes to install 59MB. Whatever happened to that malarkey about the Pixels having two partitions so no more waiting for updates to download & install?

 

[pstellato73]

I'm on Verizon version and have the beta 8.1 build. No November security patch so far.

 

[Torisen1]

On Project Fi and I have not received the update yet, not on the beta.

 

[firebirder]

That does make sense (the link provided), but it seems like we should be nearing the 100%. Still no update for me.

 

[dsignori]

That does make sense (the link provided), but it seems like we should be nearing the 100%. Still no update for me.

Well, that has always been the case. Though recently Google has said they CHANGED that for folks who actually hit the button ( "Update button actually works now") . But, they actually haven't changed anything. So it is like it always was

 

[Way out west]

Nothing here yet either! Unlocked xl2

 

[cyndie1030]

No update here either. Unlocked Pixel 2 with Verizon sim card I inserted from my Pixel XL.

 

[Ca_lvn]

I wonder why my unactivated Verizon sim allowed the November update when there was nothing with Cricket.
I kind of think it wouldn't have if it was a active Verizon account, that the sim wouldn't have worked

 

[gabbott]

It's just the normal roll out process. If Google allowed all of the devices that want the update to get it at the same time their servers would be swamped. It's not that all verizon devices got it, or that none of the non-branded devices got it. It's been a mix so far.

It's been posted before, but it bears repeating. Please read this, it will explain it better than I ever could: https://www.androidauthority.com/how-android-updates-roll-out-force-clear-gcf-318744/

You'll get it, no worries.

One thing I just want to point out, I can't imagine it has anything to do with server load. The number of Nexus and pixel devices is eclipsed by iOS devices yet those releases are all at once. Or Windows updates from Microsoft.

 

[nelamvr6]

One thing I just want to point out, I can't imagine it has anything to do with server load. The number of Nexus and pixel devices is eclipsed by iOS devices yet those releases are all at once. Or Windows updates from Microsoft.

It has everything to do with server load, and also like the article I posted says, they will release a small numbers of updates to make sure they're not bricking people's phones inadvertently... Windows updates absolutely do roll out over time. I can't comment on Apple, though I would be absolutely gobsmacked if Apple didn't roll out over time. It's simply the sensible thing to do. That's why all the big software players do it that have, have since forever.

 

[Mike Dee]

It has everything to do with server load, and also like the article I posted says, they will release a small numbers of updates to make sure they're not bricking people's phones inadvertently... Windows updates absolutely do roll out over time. I can't comment on Apple, though I would be absolutely gobsmacked if Apple didn't roll out over time. It's simply the sensible thing to do. That's why all the big software players do it that have, have since forever.

Exactly

 

[gabbott]

It has everything to do with server load, and also like the article I posted says, they will release a small numbers of updates to make sure they're not bricking people's phones inadvertently... Windows updates absolutely do roll out over time. I can't comment on Apple, though I would be absolutely gobsmacked if Apple didn't roll out over time. It's simply the sensible thing to do. That's why all the big software players do it that have, have since forever.

I'm not arguing the reason they do staged rollouts , I've been with nexus phones since the early days. My point is the length of their staged rollouts is a much longer rollout than iOS or windows or a Samsung phone.

It's a matter of policy not a matter of technical limitation of server capacity.

Go to the Samsung forums or Apple forums... For Pixel and Nexus devices when there are updates you hear much more complaining about not receiving updates sooner. On the other forums you won't.

Though some of this is because they never allowed you to manually check for updates and get them. That is supposed to be changing. On all those other systems when there is an update you could always get it by manually checking for update and it would download.

 

[husslord]

Windows did a big software update across their phones I remember yrs ago and it was a cluster bleep!

 

[eak1570]

If any one want to try to force November update. This is work for me.
https://youtu.be/0KkNoyIh6Hs