Pixel 11 Android 17 QPR1: Why It's Still Missing in October

The Pixel 11, Pixel 11 Pro, and Pixel 11 Pro XL did not get Android 17 QPR1 in Google's October 2026 Pixel Update. The update that started rolling out on October 6, 2026 moved the Pixel 11 series to build CD1A.261005.003, carrying the October security patch level and two small Pixel 11-specific bug fixes, but it left the phones on the same base Android 17 release they shipped with at launch. Every Pixel from the Pixel 8 through the Pixel 10a, by contrast, has already been running Android 17 QPR1 since mid-September.

What's actually in the October 2026 Pixel Update

Google's Pixel Support Team posted the October 2026 Pixel Update to the Pixel Community forum on October 6, confirming that "all supported Pixel devices running Android 17 will receive these software updates starting today." For the Pixel 11 line, that means a move to build CD1A.261005.003 globally, or CD1A.261005.003.B1 on Softbank-branded units in Japan. The post lists the same three functional fixes Google ships across its current device lineup this month, though not every fix reaches every phone.

The update is also the vehicle for this month's Pixel-wide October security patch, which Google separately detailed in its monthly Pixel Update Bulletin. That bulletin, published October 6 with a security patch level of 2026-10-05, states plainly that "security patch levels of 2026-10-05 or later address all issues in this bulletin," and that firmware images for every eligible Pixel are available through the Google Developer site.

The security side: what 2026-10-05 actually patches

The Pixel-specific patch level sits on top of the broader Android Security Bulletin for October 2026, which Google published on October 5 (with an update on October 8 adding AOSP source links) at a baseline patch level of 2026-10-01. That bulletin resolves 25 unique CVEs: seven rated Critical and eighteen rated High. The Critical issues include a Framework-level remote denial-of-service flaw, CVE-2026-58865, that Google says requires no additional execution privileges and no user interaction, plus six System-component issues, among them CVE-2026-55269, CVE-2026-55280, CVE-2026-58835, CVE-2026-58880, CVE-2026-49933, and CVE-2026-55265. Google's language for the most severe System entry describes a local escalation-of-privilege bug that likewise needs no extra privileges and no user interaction to exploit.

Because the Pixel-specific bulletin's 2026-10-05 patch level supersedes the AOSP-wide Android Security Bulletin's 2026-10-01 level, any Pixel 11 device on build CD1A.261005.003 is current on both bulletins. The security patching here has nothing to do with QPR1 status — it moves forward every month regardless of which quarterly platform release a device is running.

The two fixes Pixel 11 owners actually get this month

Outside of security patches, Google's October post lists three functional fixes under "What's included," each flagged with a footnote showing exactly which devices qualify:

• Apps: "Fix for issue causing the virtual keyboard to occasionally not appear when interacting with search input fields." This one is broad — it applies to Pixel 8, Pixel 8 Pro, Pixel 8a, the entire Pixel 9 family, the entire Pixel 10 family, and the entire Pixel 11 family, including the foldables.
• Audio: "Fix for issue occasionally causing audio noise or distortion in ringtone during certain VoIP calls." Google's footnote caps this one at Pixel 8 through Pixel 10a — the Pixel 11 series is explicitly excluded.
• Sensors: "Fix for issue occasionally causing captured photos or recorded videos to save in the incorrect orientation." This is the Pixel 11 line's own fix, and the footnote restricts it to Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL, and Pixel 11 Pro Fold only.

In practice, that means Pixel 11 owners get two of the three October fixes — the keyboard fix and the orientation fix — while missing out on the VoIP ringtone fix that reaches older Pixels. None of the three is tied to a platform version bump; they're standard monthly maintenance patches layered onto whichever Android release a device is already on.

Why Android 17 QPR1 still hasn't reached the Pixel 11

Android 17 QPR1 — the first Quarterly Platform Release update to Android 17, Google's term for the periodic feature-and-stability updates it ships between annual Android versions — arrived as part of the September 2026 Pixel Feature Drop. Google's own Pixel Community post titled "September 2026 Pixel Drop" describes it as one of the automatic software updates that "send new and upgraded features to your phone," name-checking additions like redesigned Pixel VIP widgets, expanded Scam Detection in Gboard, and themed Harry Potter audiobook packs for that cycle.

The companion monthly security post from the same week, "Google Pixel Update - September 2026," is the more telling document. Its software-versions table lists build CP3A.260905.009 at security patch level 2026-09-05 — but only for Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, and Pixel 10a. The Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL, and Pixel 11 Pro Fold are not in that table at all. Google gave the Pixel 11 series its own, separate September builds instead, without describing their contents in the same post.

That gap is the real explanation for what's being reported as a missing update: the Pixel 11 family simply was not part of the cohort that moved to the QPR1 branch in September, and the October update — built to patch security issues and a handful of bugs on top of whatever branch a device is already running — did not change that. It's also consistent with how Google has handled newly launched flagships in past cycles: a phone that ships in August, just a few weeks before a September platform update, sometimes needs an extra cycle to pick up a quarterly release cleanly, especially when the new chipset (Tensor G6 in the Pixel 11's case) is still being validated against it.

Pixel update tracks, October 2026: who has QPR1 and who doesn't

Build numbers above come from Google's October 2026 Pixel Update forum post. The letter prefix change — from "CP3A" on Pixel 6 through 10a to "CD1A" on the Pixel 11 line — reflects that the two groups are on different underlying Android source branches this month, which lines up with the Pixel 11 family sitting a release behind the rest of the current lineup.

What this actually changes for day-to-day use

For most Pixel 11 owners, the practical difference is small. Android 17 QPR1 was, by Google's own description in the September Feature Drop post, mostly a bundle of interface refinements and feature additions layered on top of Android 17 rather than a new OS version with its own name. A Pixel 11 running the base Android 17 release still gets the same monthly security coverage as every other current Pixel — this month's 2026-10-05 patch level applies equally across the lineup — and it still gets device-specific bug fixes, like October's photo and video orientation correction. What it's missing, for now, is the specific set of UI and feature additions Google rolled into the September Drop for older models, plus whatever quarterly stability improvements came bundled with QPR1 under the hood.

That's a notably different position than the one Pixel 11 buyers might have expected. Google markets the Pixel 11 line, including in head-to-head comparisons against rival flagships, as its newest and most capable hardware, and shoppers weighing it against other 2026 flagships — including in side-by-side looks at the Galaxy S26 — would reasonably assume the newest phone gets software first, not last.

Will the Pixel 11 skip QPR1 entirely and jump to QPR2?

This is the point where the facts run out and speculation begins, so it should be treated as exactly that — speculation, not confirmed Google guidance. Some outlets covering the October update have floated the possibility that Google will skip a standalone QPR1 release for the Pixel 11 series altogether and instead bring the phones straight to Android 17 QPR2, expected around December 2026 alongside the next scheduled quarterly release. The reasoning offered is that if Google is already a cycle behind on Pixel 11, it may be simpler to align the phones with the next quarterly milestone than to backport a now-superseded QPR1 build.

Google has not said anything to that effect in any of its official Pixel Update or Pixel Drop posts referenced in this article, and the company has not published a statement explaining why the Pixel 11 series missed the September QPR1 rollout in the first place. Until Google confirms a plan one way or another, Pixel 11 owners should treat any specific month named for QPR1 arrival as an estimate from outside reporting, not a Google commitment.

How to check your build and install the October update

The October 2026 update rolls out in phases over roughly a week and a half from its October 6 start, based on carrier and region, so not every Pixel 11 will see it the same day. To check manually, open Settings > System > Software updates > System update and look for an update to build CD1A.261005.003 (or the .B1 Softbank variant in Japan). Google's own instructions for checking your Android version are the most reliable way to verify whether a specific fix has actually landed on your device rather than relying on a model number alone.

What's next for Pixel 11 software

The next meaningful checkpoint is November's monthly Pixel Update, which will show whether Google keeps the Pixel 11 series on its own separate build track again or folds it into the same branch as the rest of the current lineup. The one after that, in December, is when outside reporting expects Android 17 QPR2 to arrive for Pixel phones generally — and whether the Pixel 11 gets it on schedule, gets a combined QPR1-plus-QPR2 jump, or continues on a delayed cadence will be the clearest signal yet of how Google is handling the newest Pixel's software timeline. Until an official Pixel Update Bulletin or Pixel Drop post says otherwise, the only confirmed fact is the one in this month's build: Pixel 11, Pixel 11 Pro, and Pixel 11 Pro XL are patched and bug-fixed as of October 6, 2026, but still one quarterly platform release behind.

Written byNadia Osei

Nadia Osei covers mobile and consumer gadgets for Pandromeda: smartphones, tablets, smartwatches, earbuds and smart-home devices. She tracks launches, software updates and pricing across Apple, Google, Samsung and the rest, and builds comparisons from the manufacturers' published specifications.

More from Nadia OseiAll Mobile & Gadgets coverage