• Posted byby Kellen

Pixel 6’s Big December Update is Now Available

After a week delay, it is now time for the Pixel 6 and Pixel 6 Pro to get their big December update from Google. This is the update that not only brings in Pixel Feature Drop goodies, it also fixes dozens and dozens of bugs from Android 12’s initial release. This is a really important update that you’ll want to grab right away.

The update will rollout with a few different builds that will hit your phone depending on carrier or country. For most of our readers, you’ll see SQ1D.211205.017 as the US carrier build. Other builds to be aware of are SQ1D.211205.016.A1 (Canada and TW) and SQ1D.211205.016.A4 (EMEA carriers).

  • UPDATE 12/15: Google added build SQ1D.211205.016.A5 for AU carriers today.

To check for the update, assuming you don’t want to manually flash it with a factory image or OTA file, you’ll head into Settings>System>System update and tap the “Check for update” button.

Pixel 6 December update fixes so many bugs

What’s fixed here? You can see the full list of changes from our post last week, but some big ones to be aware of are:

  • Fix for issue occasionally preventing audio playback from speaker in certain conditions
  • Fix for issue preventing Now Playing to search for unrecognized music
  • General improvements for battery & thermal performance in certain conditions
  • General improvements for fingerprint sensor stability & performance
  • Fix for distorted audio over Bluetooth in certain scenarios
  • General image quality improvements in camera preview/capture
  • General improvements for camera stability & performance
  • General improvements for auto-focus response in certain capture modes
  • General improvements for color consistency in viewfinder preview
  • Fix for issue causing blank viewfinder preview in certain conditions
  • Add additional example images for display color options in Settings
  • General improvements for Adaptive brightness response in certain conditions
  • Fix for occasional screen flicker during brightness adjustment
  • Fix for issue preventing Smooth Display to switch display refresh rate in certain conditions
  • Fix for issue causing Play store app installation to pause indefinitely in certain conditions
  • General improvements for network connection stability & performance
  • Fix for issue preventing lift to wake and double tap to wake in certain conditions
  • Fix for issue preventing Always-on-display from turning on in certain conditions
  • Fix for issue causing unexpected haptics or vibration in certain conditions
  • Improvements for Internet tile in Quick Settings
  • Fix for issue causing persistent app media controls in notification shade in certain conditions

And trust me, that’s only a tiny portion of what Google fixed. The full list of bugs that have been squashed might be the biggest we have ever seen in a monthly update from Google. It’s obvious that Android 12 brought forth major changes to the platform that Google is still trying to get right. This update should help with a good portion of the bugs you have been experiencing.

Pixel Feature Drop too!

As I mentioned earlier, this month’s update also includes Pixel Feature Drop goodies, so that means new features to check out. This is kind of a snoozy feature drop, if I’m being honest, but Snapchat users will like it, Now Playing is getting sweet new controls, Ultra-wideband file sharing is coming to the Pixel 6 Pro, and you might be able to use your phone as car key.

Again, the update is arriving as early as today. If you aren’t seeing it, you could always flash the update manually to get it quicker. It’s not a difficult process, but can be frustrating if you haven’t done it before.

Important links:

Written by

Kellen

It’s not often that you get to merge personal passions into a professional life, but that’s what Kellen did when he launched Droid Life in 2009. After working years of unsatisfying jobs in the medical and property management fields, he took a risk to try and create an online community while playing with the coolest gadgets on the planet each day, a risk that has turned out to be incredibly rewarding. Outside of Droid Life, Kellen is your typical Portlander who drinks way too much good beer, complains often about the Trail Blazers, and can be found out on the streets for a run, rain or shine.

Post navigation

183 Comments

  • Installing the update now. It’s taking FOREVER! ***It took 50 mins total for 215mb..
    I factory reset my phone a couple weeks ago because I used a Verizon sim card and I never received the mid November update. Well, I never put my SIM card back in after the reset and this new update knocked me off the unlocked software and now I’m on 016.A1 software. Very interesting that I’m not on US carrier firmware. Put SIM in and it works fine. Edit: guess cause I didn’t have my phone attached to a carrier. I just assumed the A1 ending was Verizon software. I may have to just side load the us carrier version once new bugs get worked out.

  • Looks like sideloading isn’t an option for those of us with carrier locked models. I have a T-Mo model I got as part of a special they were running and it’s locked to them for now.

  • I still dont have the day one launch update… I’m sitting on the Oct 5 security update.

  • Ended up side loading it – but wondering if I did it right? I have the Verizon P6P, under the OTA images, I saw two – ended up going with the .017 – is that the right one, or should it have been the A1?

    12.0.0 (SQ1D.211205.017, Dec 2021, US carriers)

    or

    12.0.0 (SQ1D.211205.016.A1, Dec 2021)

    ??

  • Pixel 6 pro still no update. I received pixel stand yesterday and it’s useless. Won’t charge my phone because this update is required… Lame.

    • Yes still no update for me. Google Fi here. Makes me wonder if something is off with the update and they are not pushing OTAs. Soon it will be Jan!

  • I wonder if Google has secretly pulled the update to make sure there were no issues? I have yet to get it too. Using a P6Pro unlocked from Google

  • Seems like a lot of people on Reddit are reporting problems with the December update. Patiently waiting for the OTA with fingers crossed cuz the Google Pixel subreddit is a dumpster fire right now haha

  • Ordered a Pixel 6 Pro from Verizon on 10/23 and finally got it yesterday. Yay!
    Went to manually initiate the December update but no dice. WHAH-whah!

    Oh well, not a big deal I guess. I just remember getting those monthly updates on day 1 every month with my 2 XL, just after I saw the update here that they were live. Maybe things will settle in in the coming months.

  • P6 unlocked on Visible, and no luck getting the update pushed to me. Everything seemed a lot smoother with updates with my last Pixel.

    • Same here. Unlocked P6 on Visible in Salt Lake City if region makes a difference. I even tried removing the SIM, rebooting, and trying to pull while on wifi with no SIM inserted and it didn’t make a difference.

  • @iamkellex You should update this post talking about the lack of actual OTA on any carriers.

    • I was just about to post and ask if I’m the only one who still hasn’t received the update. Guess not. Misery loves company, I guess…
      This is my third Pixel, and I don’t remember ever experiencing this — weird…

      • Same. I was beginning to wonder why this post has gone so silent. And i too am on my 3rd Pixel and this is weird. I mean its nothing that i cant live with…. i still have a perfectly awesome phone. but would really love to get this downloaded and installed. Either way, ill survive i think

    • I have a feeling there are issues. I have heard of many people that got it having issues with bluetooth, and many app issues.

  • unlocked P6Pro bought from google on verizon. Didn’t get either the mid november or december updates. I pulled the sim, and factory reset, and there was an update to the global build of the december update, so that’s where i’m at now. Not sure if this will be helpful to others or not.

  • Ok, I got tired of waiting for the update, so I followed your instructions and successfully sideloaded the update. I’m feeling pretty good about myself as a result 🙂

  • Anyone on OTA on GFi? I don’t see much representation in here with this MVNO, but figured I ask.

  • “General improvements for network connection stability & performance” sideloaded on tmo now I get a crap signal where i used to get a great signal.

  • Apparently there is an issue with the Dec update that makes signal much worse than before. It’s been sporadically reported in Europe. Maybe that’s why they didn’t push it out to the US yet?!

  • Nothing here, GOOGLE Fi. I just wished GOOGLE communicated better. I have no problem if they pulled it to fix network issues. Just relay the message

  • Not for me. Still waiting. Unlocked 6Pro with Tmo SIM. I am really starting to get frustrated with Google. Ive been loyal since G1, but they seem to be getting worse, and not better.
    This entire phone launch has been a disaster. From the google store on day 1, to amount of bugs and inconsistencies since I got the phone. Especially the camera. Front camera is the worst I’ve had with Pixel. Unless it has perfect lighting conditions, it completely washes out the colors, it is grainy, just awful. Front facing camera is inconsistent, autofocus is a mess, when it takes a good pic, it is great, but 20% of the time post processing completely ruins the photo or focus is bad. OS is buggy. The fact Dec update (which I still have not gotten) has that many bug fixes clearly shows Google was not ready for launch in October. This truly is an embarrassment.

  • This is lame. I just upgraded from a 2xl to a 6 pro. “check for updates” always forces the update once it’s released. Def not gonna side load

  • some help please, I have an unlocked P6 with verizon SIM. i need to sideload the ORIGINAL update. correct me if i’m wrong here but if i sideload, i am supposed to sideload the version NOT marked as verizon, correct? thanks

    • there is no december package marked for verizon. You want the one marked “US carriers”. Make sure you’re looking at the december one, which is at the bottom of the list for your device

          • While I appreciate your attempt to help, that’s not what I am asking. I’m asking do I use the Verizon update on the unlocked phone since I’m using a Verizon SIM? The answer isn’t an obvious assumption since it’s an unlocked phone. I assume the Verizon update is for the Verizon variant which has mmWave radios.

          • The unlocked regular p6 does not have mmWave unless you bought the Verizon variant. Each update is different. Some months there is a Verizon build. The December update is for all US carriers, no separate build for Verizon. If you side load the update, it shouldn’t matter what build you are currently on, it will take you right up to whatever build you sideload.

          • Yes, you can def do that. I have unlocked P6 using VZW and did that last week and it works fine. I could be wrong, but I think you can also skip the November one and go straight to December build by sideloading that one. I sideloaded the December update last night, but was already on the VZW November build.

  • Nothing for my unlocked P6P. Google is getting as bad as Elon Musk for promising and not delivering!

  • I sideloaded, T-Mobile 6 Pro here. I noticed they messed up the 5G UC icon, maybe that is why they didn’t push it yet.

  • I sideloaded on past with no issue on pixel 4. I cannot seem do it on my 6 pro though. Do the reboot recovery command fine and the phone goes to screen with Android guy and exclamation point. When I type adb devices here though no devices pop up. Obviously I’m doing something wrong

    • Did you hold the power button then the volume up button? You can always just go to fastboot to easily get to recovery as well.

      Believe it or not, I’m actually not able to get the sideload working because ADB is bring up then “cannot read” file error. I just gave up and reckon I wait for the OTA.

  • I am on an unlocked P6P using Visible(Verizon). If I want to sideload it do I just use the “US Carriers” version? It is 1.9GB is that right? I am currently on the .037 build.

  • got impatient and sideloaded it on my 6 Pro. The process is SUPER easy if you know what you’re doing but can be scary if you’re new (I’d actually recommend NOT doing it for your first time on your fancy new phone)

    The file size is almost 2gb if you go the sideload route and it takes about 5 minutes to install and reboot

    • Yeah I sideloaded twice now since I got my pixel 6 and once you get the process down it is simple. It is actually probably faster than installing it from system update. When I did the first November update by checking on the phone, it took like an hour to complete but the whole sideloading process took 10-15 mins

        • Now if I could only figure out how to get Chat verified in Google messages again. I had it enabled but turned it off when I got a encrypted message I could not read and now will not turn back on no matter what. Have been messing with it for the last two days and nothing. Cleared messages app data and cache as well as carrier services data and cache. I do not know what else to do.

    • tons of people. the pixel reddit channel is all over it. But probably a small percentage of overall users at this point in the rollout. From what they’ve been posting, it looks like the staged rollout should finish tomorrow

      • Most of those people are outside the US. As far as I have noticed. Not a lot of US users have been getting the OTA. I’ve never had a problem getting the update on the first Monday, and I still don’t have it yet Tuesday night. Maybe later this week I guess.

    • staged rollout, could take a few days. If you get itchy, you could sideload it but if you’re not really experienced in that, I suggest just being patient, it’s coming

    • I’m not holding my breathe. I haven’t gotten an update for my Unlocked 6P through Verizon yet. I had to borrow a friends t-mobile SIM and put that in the device to get the update. It pulled it right away too. Damn Verizon!

      • Problem with that route though is you still won’t be on the Verizon build, so you’ll have to do that or sideload every month. I sideloaded the Verizon build last month, so I’m trying to wait this one out to see if I’ll actually get an OTA this time. After the sideload, I did actually get 2 security updates pushed a couple weeks ago.

  • Pro tip: if you have a P6P, make sure you don’t download and try to sideload the P6 update (face palm emoji). Luckily it just isn’t able to verify the update and doesn’t do any damage lol

  • Nothing yet 1:32 PST Couldn’t wait: sideloaded. So far so good. Fingerprint scanner DEFINITELY improved!

    • Next month. You’ll get all security updates and feature drops since the last time you got one. That’ll be the last for the 3

  • 10:06PM EST Pixel 6 Pro. No updates for me. When are we gonna get a iOS-like update. Why do we have to go to settings, and check for update manually?! Why do I have to ‘sideload’ an update on 14th year of android!!! Been using Pixel devices for long time now and I don’t remember when I got a notification for updates!! For how many more years Google/Pixel/Android going to be managed by amateurs?

    Sigh…

    • whoa, there. First off, you don’t have to do either of those things, you could just wait. You know how you hear about iOS updates breaking something and them doing a follow-up update to fix it? You hear the same things for pixels but far less, why? Staged rollouts.

      Start at a small percentage, watch out for crashes, errors, etc. If good, increase percentage. Repeat until you hit 100%. As a dev, I do the same on every app I manage.

      You could say “that’s what QA is for” but every developer on the planet will tell you that’s not the case. QA is vitally important but they can’t catch everything. They can’t test every combination of every app and everyone’s unique usage to find every single use case that could result in bugs.

      Even with staged rollouts, things slip through but it would be a bug ridden hellscape without them

      • This has never been the issue in the past. I’ve had nexus 6p, pixel 1, pixel 2, pixel 4xl, pixel 5, and now pixel 6pro. all unlocked but using on vzw network. still not update on my pixel 6 pro. on the previous devices i’d usually get the update before droidlife would even post about it.

        • in staged rollouts, that’s luck of the draw. staged rollouts go out to a randomized percentage of people based on whatever criteria is defined in the rollout

      • “Even with staged rollouts, things slip through but it would be a bug ridden hellscape without them”

        This is the summary of your whole comment. Bugs can’t be eliminated completely. It’s impossible.

        “but it would be a bug ridden hellscape without them”

        May be for some small company with a team of 4-5 QA, not for a company like Google.

        “you don’t have to do either of those things, you could just wait”

        I did, till 10PM and than sideloaded, just like everyone else.

        My complaint was, I never got notified for any Pixel OS updates. I always learned about it from an online article and then checked for it in the Settings. It’s been many years now and this should change.

        • what should change? you would get the notification if you waited. it works as expected. You’re simply checking or side loading prior to the push

          “May be for some small company with a team of 4-5 QA, not for a company like Google.”

          That’s categorically false. Do you think they have thousands of QA resources dedicated to security updates?

        • You did not have to ever do any of that. They will come down, you just need to be patient, if you follow tech blogs. If you don’t, then you won’t know that some people got it yet, and will get notified by the phone when it is ready for everybody.

  • This is my first Pixel. Why is it so much harder to sideload an ota file compared to OnePlus?

    On OnePlus you just download the ota file to your phone, change the ending to .zip and install from the phone. Easy Peezy.

    But on a Pixel you need to connect to a computer.

    • I haven’t tried it but the recovery mode DOES have an option to install from file system. Maybe you can just download on your device and install it from recover?

      As a previous owner of one plus devices and a current pixel owner, I have to give the win to pixel on this one, though. Allowing system packages to be easily installed from the device is a HUGE security risk

        • I tried to install from recovery with the file in the root directory and of course it failed.

          And after a full day of waiting it seems the update would never come, so I finally sideloaded per instructions.

          Easy enough once you get it set up. Here on out it will be quicker.

          P.S. Don’t rename your file “whatever.zip”. Just rename it “whatever”. Or else you will have to enter adb….. whatever.zip.zip to get it installed 🙂 lol yes I did that.

          Typing Amazing for so many years makes your mind soft.

  • Just sideloaded went smooth and fast shows latest build number US version sqd.211205.017 dec 5th sec update not sure what else changed ?

  • Unlocked 6Pro from Google on VZW, just sideloaded, feels peppier (but then again, I didn’t have a lot of the other issues reported)..

      • I don’t know why, but it feels like there’s some downside to sideloading vs downloading it regularly. Partly just the hurdle of learning how to.

        • The downside of waiting for the OTA is WAITING. You have to wait until your device’s IMEI comes up for download eligibility, then you have to WAIT for it to download in the background, then you have to WAIT for the installation to occur in the background, then you have to WAIT for apps to get optimized for the update in the background, then you can finally reboot and enjoy.

          With sideloading, you can simply download the zip file and push it to your phone using ADB and it installs in 10 minutes instead of taking an hour.

        • TBH, it’s not difficult or something you need to learn, you just need to follow instructions. I’m just upset that I have to do it in the first place since I haven’t had to do it since before OG Pixel XL. It’s just sad, with companies with the resources of Google and Verizon, that this is an issues in the first place for their flagship phone. And to top it off, no communication to the group of people that are in this situation on whether or not a fix is coming, or to just sideload. I was holding off out of spite but finally just sideloaded. It was quick and painless and if you follow the instructions that Kellen linked you should have no problem if you go for it.

          • Most people don’t WANT to do that each and every month after spending over $1000 on the phone. I much preferred getting it pushed automatically, with no wait, like clockwork between the 1st – 5th of every month, like I did for the past few years.

          • I get it, I didn’t WANT to do it either, but I’d rather have the patch at this point then not have it. I wanted my $1000 device to be running as it should and didn’t want to get too far behind in security patches. Looks like there’s one build for US carriers, which is what I use (VZW), so I’m hoping that it’s fixed with this latest release and the auto push will start again next month. Some communication from Google on the issue would be really helpful too.

  • I have an unlocked 6 direct from google, and am in the US. anyone know why my phone would get the SQ1D.211205.016.A1 update? I was wondering why I never got the .17 update maybe this has some relation to that?

    • Its because you are on Verizon. Same boat here. They will release their version, which you will get. It’s ridiculous that they have this control over unlocked models too.

      • But I’m on Cricket mobile, I thought they were and AT&T company. And my last phone with cricket was an unlocked t-mobile phone. Also the update that installed when I first got the phone was the .016 update not the verizon one.

      • But do they? I also purchased my phone unlocked from Google and put a Verizon SIM in it. Sideloaded the unlocked and now “all US carriers” OTA image without issue.

        • It’s different every update. The December update .17 is for all US carriers including Verizon. Some updates there is a specific build for Verizon like there was last month.

          • I’m not sure. It wasn’t that way in the past, but it seems like unlocked Google phones on the Verizon network might be a little different this time around.

          • mine did update with the .A1 update and seems to be doing fine, so it may be a non issue. but it is kinda weird. maybe my phone was shipped from canada or TW? I wonder if there’s a way to tell?

    • I have the same thing. I’m on MetroPCS, but my phone downloaded and installed the 016.A1, not the 017 carrier version. Maybe people who use MNVO like Metro, Cricket, etc, don’t get the carrier version?

  • I have not been seeing the SiriusXM controls in the notification area for a while, when the app is playing. Maybe this will fix it?

    • “The update will rollout with a few different builds that will hit your phone depending on carrier or country. For most of our readers, you’ll see SQ1D.211205.017 as the US carrier build. Other builds to be aware of are SQ1D.211205.016.A1 (Canada and TW) and SQ1D.211205.016.A4 (EMEA carriers),”

  • Side loaded here while on break from work p6 on Google Fi hope this fixes the weird connection issues between switching networks of 4g and 5g and just losing signal all together when ending a phone call

    • Which version did you use? The one that specified US Carriers or the one that didn’t specify either way?
      Nevermind actually read what Kellen said

  • Sideloading now. Hope this fixes the bluetooth issues I’ve been experiencing on my Pixel 6.

    • What kind of BT issue?
      I also had BT issue. The connect between my car and Pixel 6 abruptly drops within the first 2 minutes of phone call.

      • I haven’t had call drops in the car but I do have a lot of Android Auto connectivity issues (via bluetooth). No connection, drop connections, no audio. Not sure if this update will fix or is its an Android Auto issue. I hope the update fixes.

      • Left earbud playback issues with my Sony WF-1000XM4s. Many people online are reporting the same problem. It wasn’t fixed with the update.

        • I’m listening to music with WF-1000XM4 right now as I’m typing this. I don’t have the issue you and others are reporting.

          • But do you have Bluetooth connection quality set to priority on sound quality? That is the option that results in issues.

          • Yes. it’s set to priority on sound quality and listening to lossless music via Apple Music.
            The BT codec is set to LDAC.

Comments are closed.

back to top