Google has confirmed that the Pixel 6 and Pixel 6 Pro have reached end of life, and Android 17 QPR1 — expected as a stable release around September 2026 — will be the last major software update either phone ever receives. The confirmation came alongside today’s release of Android 17 QPR2 Beta 1 (July 20, 2026), from which both 2021 flagships are now excluded.
Pixel 6 end of life: what Google said
Google’s Android Beta Program said today that Pixel 6 and Pixel 6 Pro owners won’t receive the new beta because the devices are reaching end-of-life status, with the Android 17 QPR1 beta series being the last for these two phones (as reported by Droid-Life, which sourced the note from a post in the r/android_beta community). This isn’t a formal press statement — it’s a beta-program communication tied to the rollout — but the practical upshot is unambiguous.
The two phones being left behind are the notable exclusions from an otherwise wide beta list. In plain terms:
- No longer eligible / reaching end of life: Pixel 6, Pixel 6 Pro
The timeline: when your Pixel 6 support actually ends
Here’s what the remaining year looks like, based on Google’s own support commitments:
- Around September 2026: Android 17 QPR1 arrives as a stable release — the Pixel 6/6 Pro’s final quarterly feature update.
- Around October 2026: The devices were originally covered for security updates through October 2026, so there could be one last standalone security patch here.
- After that: Nothing. No feature drops, no security patches, no beta access.
That October 2026 security window is itself the result of Google extending Pixel 6-series support by an extra two years back in December 2024, on top of the original commitment. Android Authority’s Stephen Schenck notes these phones hit their five-year birthdays this October — so the wind-down lands right on schedule, not early.
Promise vs. reality: a slow fade, not a sudden cutoff
When the Pixel 6 and 6 Pro launched in October 2021, the pitch was ambitious. We covered the leaked specs at the time in a piece headlined around how the pair could offer five years of OS updates — and, credit where due, the December 2024 extension broadly delivered on that, carrying these phones from Android 12 all the way to Android 17.
The honest asterisk is in how the final stretch has been handled. Over the past year, Droid-Life has tracked the Pixel 6 and 6 Pro being quietly moved to an irregular, quarterly-only update cadence — rather than the monthly security patches most current Pixels still get. So today’s end-of-life confirmation isn’t a shock cutoff; it’s the formal close on a gradual downgrade that was already visible to anyone watching their update screen.
What that means for you: if you’re on a Pixel 6 or 6 Pro, start budgeting for a replacement now. Expect no more feature updates after roughly September 2026, likely one last security patch around October 2026, and then you’re on your own. A phone with no security patches isn’t unusable, but it does quietly become a bigger risk the longer you hold onto it — that’s the cost to weigh, not Google’s calendar.
Android 17 QPR2 Beta 1: what’s new and who gets it
The release that surfaced all of this is Android 17 QPR2 Beta 1, out July 20, 2026. It ships as build CP41.260701.005 with a security patch level of 2026-07-05, and it’s a fairly light beta — per Google’s official Android developer release notes, it carries a minor SDK bump to API 37.1 with no app-breaking behavior changes.
Eligible devices this round run from the Pixel 6a through the Pixel 10 series, plus the Pixel 10a — with the Pixel 6 and 6 Pro being the only exclusions. You can enroll through the Android Beta Program for an over-the-air update, or manually flash the OTA/factory images. The broader QPR2 update is expected to reach stable around December 2026.
The fixes, in brief
Google lists eight fixes in this beta:
- Bluetooth re-pairing failures after a bond is lost
- Notifications randomly disappearing from the notification shade
- System crashes when invoking Gemini
- Drag-and-drop gesture problems when using multiple fingers
- Window-level UI blur that failed to render
- Media player control display issues
- ML-DSA key generation failures
- Accessibility debugging data issues
Sources: Droid-Life, Android Authority
