Pixel 6 and Pro November Update Bugs/Fixes

[B. Diddy]

First, go to the google Maps settings menu and select Navigation Settings, then Voice Selection. What do you have selected there?

You can also go to the Google app's settings, then Google Assistant>Assistant Voice, and try different voices there.

 

[harbinger007]

Thank you. I had three English choices there and they all sound fine. I have no idea what it was on, somewhat robotic, neither masculine or feminine.

 

[kjharrison]

On Cricket. Got the first November update, but not the second.

 

[kjharrison]

Cricket isn't on the November list, I'll have to wait for the December update.

 

[anon(40376)]

Isn't Cricket just an MVNO? Or, since it is owned by ATT it is handled differently than a privately owned MVNO? Just curious...

 

[sulla1965]

Still no face unlock?

 

[mustang7757]

Still no face unlock?

Not yet

 

[scribe4food]

I got the update and don't know if I'm in the placebo group, but the finger print sensor does seem faster.

 

[fuzzylumpkin]

Google did push the 0.36.A1 to every one on C2, last week. If you had updated with no SIM to 0.36 before that, then won't get that 0.36.A1 update, so you won't get this update either.

Google has really screwed up these updates catering to Verizon Wireless

Hold on, what?

So because my pixel is on .036 (an update pushed by Google) it isn't going to receive OTAs unless I sideload an update, because Google are entirely incompetent? Is this correct

Or were you just talking about Verizon phones? It's hard to know without context...

 

[firebirder]

Google did push the 0.36.A1 to every one on C2, last week. If you had updated with no SIM to 0.36 before that, then won't get that 0.36.A1 update, so you won't get this update either.

Google has really screwed up these updates catering to Verizon Wireless

I don't understand this post either. What is 0.36.A1? I'm on VZW, updated before SIM inserted and am showing build SD1A.21080817.036. This is not the build, I know, after the mid November update, but still no update for me. Did @slave have a typo? Do I need to sideload to get back to OTA updates? Is 0.36.A1 something beside the build number?

 

[bkdodger2]

SD1A.210817.037.A1 is the latest November Verizon with fingerprint update ..small update

 

[dleavins]

I have a p6pro I bought through Verizon. I have not yet received a mid November update. Just checked and it says last update to my phone was Nov 5 security update.

 

[Deleted member 2609113]

I have a p6pro I bought through Verizon. I have not yet received a mid November update. Just checked and it says last update to my phone was Nov 5 security update.

The new update will still indicate Nov.5.

 

[Tool_Belt]

Check the build number, then sideload it if you want. There is a good guide over on XDA.

 

[dleavins]

Thanks, smokeaire and tool build -- I checked the numbers and I did already get the update.
Thanks again.

 

[anon(49997)]

Sure glad I canceled my order, and I stopped using Verizon years ago. I have never owned a Locked device and never will as long as there is an option. I have been rooting and romming since the Motorola Droid then to the Galaxy Nexus.

I lost my head and pre-ordered this one but came back down to earth.

I have learned later on that being an early adopter of a new release it a PITA and acting as an unpaid beta tester. All these issues could have been resolved before production but the dollars they can save and make. Getting a new release Google Phone and being on Verizon has to be horrific.

 

[Ben_70]

I have a Verizon 6 Pro and am really enjoying the device. Yes there are still a few small bugs in A12 like not showing the vibrate icon up in the status bar but that's hardly ruining my experience. I got the mid Nov patch and the FPS is working just fine.

 

[Davidoo]

Sure glad I canceled my order, and I stopped using Verizon years ago. I have never owned a Locked device and never will as long as there is an option. I have been rooting and romming since the Motorola Droid then to the Galaxy Nexus.

I lost my head and pre-ordered this one but came back down to earth.

I have learned later on that being an early adopter of a new release it a PITA and acting as an unpaid beta tester. All these issues could have been resolved before production but the dollars they can save and make. Getting a new release Google Phone and being on Verizon has to be horrific.

Not at all. You do realize that after 60 days Verizon purchased devices automatically become unlocked? I've never had a problem with the many Verizon purchased phones over 20 years. And if I have a problem they are much easier to deal with for a replacement if I walk into the store than by calling Google.

 

[kjharrison]

Isn't Cricket just an MVNO? Or, since it is owned by ATT it is handled differently than a privately owned MVNO? Just curious...

Not sure. I figured they would get the update since they're owned by AT&T, but no update came. I guess they're not considered AT&T.

 

[slave]

I don't understand this post either. What is 0.36.A1? I'm on VZW, updated before SIM inserted and am showing build SD1A.21080817.036. This is not the build, I know, after the mid November update, but still no update for me. Did @slave have a typo? Do I need to sideload to get back to OTA updates? Is 0.36.A1 something beside the build number?

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.