Pixel October 2026 Update: Fixes, Builds and Pixel 11 QPR1 Delay

A WhatsApp call comes in on your Pixel 9 and the ringtone crackles like a bad radio. That’s one of three bugs the Pixel October 2026 update fixes. Google began rolling it out on 6 October, in phases over the following days and weeks, with security patches for three critical flaws as well.

The patch level is 5 October 2026 on supported Pixels, covering both the Android Security Bulletin and the Pixel Update Bulletin (TechRepublic). Pixel 6 through Pixel 10 get it on the Android 17 QPR1 release. The Pixel 11 gets it on a separate Android 17 branch, and still has no QPR1, which Google hasn’t explained.

The three bug fixes, by model

According to Google’s changelog, as reported by 9to5Google and TechRepublic, each fix applies only to certain models:

The VoIP fix is for crackling or distorted ringtones when a WhatsApp, Signal, Teams or other internet call arrives on a Pixel 8, 9 or 10. Google says it happened “during certain VoIP calls”, so not every app or call was hit.

The keyboard bug meant that tapping a search box in some apps sometimes didn’t bring up the on-screen keyboard. Tapping again, or leaving the app and coming back, usually got round it. After updating you shouldn’t need to.

On the Pixel 11, some new owners found portrait shots saved sideways. Google filed the fix under sensors, which suggests the phone was misreading its orientation at the moment of capture, rather than the camera app being at fault.

Bluetooth, GDMC and GSA: the critical flaws

The Android 17 October patch resolves 28 issues in the platform bulletin, by 9to5Google’s count. On top of that, the Pixel Update Bulletin lists six more vulnerabilities, four of them in Pixel-specific components. TechRepublic’s summary:

• Critical: one flaw each in Bluetooth, GDMC and GSA (the Google app).
• High: two flaws in the kernel.

Google Play system components were updated too (Google Play services 26.39). If you use Bluetooth every day, the critical Bluetooth flaw is reason enough not to put this off.

Which build you should see

Look in Settings › About phone › Build number:

The prefix tells a story. Older Pixels are on CP3A, the Android 17 QPR1 branch. The Pixel 11 is on CD1A, the branch it launched with. That’s the QPR1 gap, visible in a build number.

Still broken after October

The changelog is short, and several of last month’s most-discussed complaints aren’t on it.

QPR1 lag and stutter. In early October, GrapheneOS said it had found and patched a regression in Google-supplied Pixel kernel drivers that causes stuttering and freezes under memory pressure. Google’s October changelog mentions no performance fix, and Google hasn’t publicly acknowledged the problem. Stock Pixel owners hit by slowdowns may have to wait for a later monthly update or QPR2.

Battery and heat. None of the three fixes is about battery life. If drain started after QPR1, check Settings › Battery › Battery usage for one app taking more than its share before blaming the system.

Pixel 11 feature parity. It stays on its own branch without QPR1’s interface changes (more on that below).

If your problem isn’t on Google’s list, send it in with Settings › About phone › Send feedback about this device. It reaches the Pixel team with logs attached.

Where is QPR1 for the Pixel 11?

Google announced Android 17 QPR1 in mid-September 2026 with its September Pixel Drop. Since then, according to Android Authority, a CD1A.260905.001.B1 update reached only Pixel 11 models in early September. Android 17 QPR2 Beta 6 arrived in late September without Pixel 11 support, with Beta 6.1 the week after. And the 6 October update kept the Pixel 11 on its own branch again.

Google hasn’t explained the delay or given a date. Android Authority says it has asked. The Pixel 11 has the new Tensor G6 chip and a MediaTek modem, which might need a separate software track, but that’s informed speculation, not a confirmed reason. Some commenters think Google could skip QPR1 on the Pixel 11 and go straight to QPR2. Also unconfirmed.

What Pixel 11 owners are missing is mostly visual: more blur in the volume panel and power menu, a Quick Settings edit button and Keyboard tile, a media carousel, and Health Connect tracking distance and calories. They are not missing security fixes, because the Pixel 11 gets the same monthly patch level. The hardware differences are in our Pixel 11 Tensor G6 and Titan M3 article.

The Pixel 6’s final month?

Google extended Pixel 6 and Pixel 6 Pro support to five years, and that ends in October 2026. This month’s build includes the Pixel 6 family, but Google hasn’t said whether it’s the last regular update. Unless support is extended again, expect monthly patches to stop for the 6 and 6 Pro. What that means day to day is in our Pixel 6 end-of-support article.

Installing it

For almost everyone, install it now. It fixes three critical security flaws and doesn’t change the Android version on any model, so the risk of new problems is lower than with a quarterly release. If the phone is your only work device you can wait a few days for other owners’ reports, but not weeks.

1. Go to Settings › System › Software updates › System update and tap Check for update.
2. Download and install, then tap Restart now.
3. Open Settings › Security & privacy › System & updates and tap Google Play system update.
4. Check the build number and Android security update date in Settings › About phone › Android version.

Stuck downloading? Restart, free up a few gigabytes of storage, and try again on stable Wi-Fi.

Buying a used Pixel: check the build and the IMEI

A used Pixel’s build number shows whether it’s still updating. If it’s far behind, ask the seller why. Then:

• Confirm the model and warranty with a Google Pixel Info check.
• Find out if it’s carrier-locked. Our Pixel carrier unlock check article explains why the OEM unlocking toggle matters, and a carrier and SIM-lock check confirms the network.
• Run a GSMA blacklist check to make sure it isn’t reported lost or stolen.
• On a Pixel 6 or 6 Pro, price in the end of support.