Pixel 6 and Pro November Update Bugs/Fixes

[mustang7757]

It was a typo. The point stands though. If you updated your phone and have the world wide November 5 build, that's 0.36, you won't get 0.37.A1.

Google pushed the update to all the phones in November, but us unlocked Verizon folks are back to square 1.

This phone update has been a giant headache. I can't, for the life of me, understand how Google is letting this happen.

On the pixels Verizon was usually the first with software updates , if i learned anything through the years on the forums all carriers run into this where they drop off in updates then get back into the grove , i seen it with TMobile/Att so dont sweat it much they will get back in the grove .

 

[slave]

Remains to be seen. It's radio silent again. It's a dumb problem, it shouldn't happen. I am 100% sure folks got their unlocked phones in the last few days/week, and are stuck on the world build because Google can't get it's **** in a group.

 

[firebirder]

@slave, thank you. I figured it was a typo, but wanted to double check. Is it really worth sideloading the mid month update? I've heard some people say that the fingerprint scanner works better but I don't use that, so that's nothing to me. Anything else worth it? Also, maybe no one knows this for sure, but will those of us on VZW get the normal update come December? Will we be back on track?!

 

[slave]

@slave, thank you. I figured it was a typo, but wanted to double check. Is it really worth sideloading the mid month update? I've heard some people say that the fingerprint scanner works better but I don't use that, so that's nothing to me. Anything else worth it? Also, maybe no one knows this for sure, but will those of us on VZW get the normal update come December? Will we be back on track?!

The only reason I was going to side load was to fix the updates, so I would get them. This whole thing has really pissed me off.

 

[Maljunulo]

This phone update has been a giant headache. I can't, for the life of me, understand how Google is letting this happen.

Google isn't "letting it happen" Verizon, with their incessant screwing around with things, has made a mess of it what Google released.

 

[anon(40376)]

Years ago, when I had service via Verizon, I got so pissed off, I left, but only after I studied MVNOs and found some reliable ones that used Verizon towers. Have not looked back; and never had a problem with their service.

 

[fuzzylumpkin]

Google isn't "letting it happen" Verizon, with their incessant screwing around with things, has made a mess of it what Google released.

And who is it that's letting Verizon get away with that?

Lol

 

[slave]

And who is it that's letting Verizon get away with that?

Lol

Kind of like how Google pushed that November update out. You get it, these folks don't seem to understand that Google has the power to stop this from happening, just like Apple already does.

 

[slave]

Google isn't "letting it happen" Verizon, with their incessant screwing around with things, has made a mess of it what Google released.

Of course they are. They demonstrated that they can fix it, about two weeks ago. Apple also doesn't tolerate it. Google can and already did push out the update to fix it. This is 100% on Google.