Android 17 QPR2 Beta 2 Lands With a New Settings Icon and a Quiet Codename Switch
Google is keeping its quarterly beta cadence right on schedule. Android 17 QPR2 Beta 2 has started rolling out to eligible Pixel devices, arriving exactly two weeks after Beta 1 and carrying build number CP41.260717.006. On the surface, this looks like one of the quieter beta drops of the cycle – Google didn’t publish a changelog again – but testers digging into the build have already turned up a handful of real, if modest, changes.
No Changelog, Again – But Testers Found Things Anyway
Google has now skipped official release notes for two QPR2 beta builds in a row, which is a mild departure from how thorough the notes were during the earlier QPR1 cycle. That absence hasn’t stopped the usual community of Android beta testers from combing through the build and reporting back what’s actually changed:
- A redesigned Settings app icon is now rolled out system-wide. This isn’t entirely new territory – some users had already glimpsed the updated icon earlier, after performing clean installs during the QPR1 beta cycle – but Beta 2 is the point where it becomes standard for everyone running the update.
- An internal codename shift, moving away from Android 17’s long-running “CinnamonBun” internal name to something far more generic: simply “DEV.” This kind of change carries no functional impact for end users, but it’s the sort of small internal-process detail that beta trackers tend to flag because it can hint at organizational shuffling behind the scenes.
- Background stability fixes, targeting touch response hiccups and notification shade display bugs that had been reported in earlier builds – unglamorous, but exactly the kind of polish a beta cycle exists to catch before a feature reaches stable release.
Who Gets It, and Who Doesn’t
The rollout covers a wide swath of Pixel hardware: 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, alongside the Android Emulator. The build carries a July 2026 security patch level, consistent with prior QPR2 beta releases.
Conspicuously absent, as expected: the original Pixel 6 and Pixel 6 Pro. Both devices officially reached their End of Life support window during the QPR1 cycle, and Google’s own release notes were direct about it at the time – the Android 17 QPR1 beta series was confirmed as the last software update either device would ever receive. If you’re still running one of these two phones, QPR2 (and everything after it) simply isn’t coming your way.
How to Get It
If you’re already enrolled in the Android Beta Program, the update should arrive over-the-air automatically – check under Settings > System > System update on an eligible device. If you prefer a manual install, factory images and OTA zip files are available directly for flashing, including through Google’s web-based Android Flash Tool. As with every beta cycle, bugs can be reported directly through the pre-installed Android Beta Feedback app, accessible from the app drawer or Quick Settings, which files reports straight into Google’s public issue tracker. The Android Beta community on Reddit remains an active secondary channel for comparing notes with other testers.
What This Fits Into
QPR2 is part of Google’s ongoing Quarterly Platform Release program, and this specific cycle is on track to reach stable release in December 2026, arriving alongside a Pixel Feature Drop as usual. That timeline places QPR2 firmly as the next meaningful software milestone after this month’s Made by Google event and Pixel 11 launch – meaning most of the excitement around Android 17 in the near term will center on hardware rather than software, with QPR2’s more substantial feature set likely to reveal itself gradually across the remaining beta builds between now and December.
For most Pixel owners not enrolled in the beta program, none of this changes anything today. But for the subset of testers and enthusiasts tracking Android 17’s evolution build by build, Beta 2 is a useful data point: modest on features, but a clear signal Google is treating this cycle’s polish and stability work seriously even without headline features to show for it yet.