Android 17 QPR2 Beta 5 is the latest pre-release build in Google’s quarterly Android 17 update cycle. Released in Google’s official notes on September 15, 2026, with a public Pixel rollout reported on September 16, it adds a more detailed control surface for Proactive Assistance on Pixel 10 and Pixel 11 series devices and addresses a long list of bugs.
The headline change is not a dramatic visual redesign. It is a settings menu that gives you more say over which app information can feed personalized suggestions. That matters because Proactive Assistance can use screen content, notifications, location and selected app information.
Android 17 QPR2 Beta 5: what changed and who it is for
Beta 5 is a development build for supported Pixel devices and Android Emulator images, not the stable Android 17 release. Google lists builds CP41.260828.004.A8 and CP41.260828.005.A6, a security patch level dated August 5, 2026, and Google Play services version 26.28.33. The emulator images support x86 64-bit and ARM v8-A.
A hands-on walkthrough on a Pixel 10 Pro XL shows a 667 MB update package for that device. The package size is device-specific, so it should not be treated as a universal download size.
The second Proactive Assistance menu is the headline change
On Pixel 10 and Pixel 11 series devices, Beta 5 can show two Proactive Assistance entries in Settings. One uses a blue icon and refers to personalized suggestions from Gemini; the other uses a yellow icon and is labelled “Personalized suggestions at the right time.”
Both entries appear to control the same underlying capability: turning off the original blue switch also turns off the yellow one. Google’s reason for displaying both entries is not stated, but the practical result is clear enough: Beta 5 exposes a new route into the controls that govern proactive suggestions.
New controls for app content, screen data and notifications
The newer settings page includes a Use app content for suggestions option. From there, you can control which applications may share screen content and notifications with Proactive Assistance. The page also lists access categories for what is on the screen, notifications and location, along with a shortcut for changing the default digital assistant.
That is the meaningful change for privacy-conscious users. Instead of treating app content as one giant on-or-off switch, the interface presents per-app controls. The feature remains part of a beta build, but the direction is unmistakable: more granular settings for a system that can draw on several types of contextual information.
The app-level page lists individual applications with separate toggles for sharing content and notifications. It is the sort of unglamorous settings screen that can matter more than a flashy animation: this is where the user’s control actually lives.
The official fixes in Beta 5
Google’s release notes list fixes across several parts of the system, including:
- Bluetooth device icons.
- Unexpected reboots during continuous scrolling in media-heavy applications.
- Missing volume controls while casting.
- Search-field highlight rendering.
- Unlocking Private Space.
- Enhanced HDR behavior.
- Google Wallet touchscreen unresponsiveness.
- Camera crashes during panorama processing.
- Distorted Bluetooth call audio after calls.
These are targeted corrections rather than a promise that every problem reported on earlier beta builds has disappeared. Community reports from Beta 3 and Beta 4 included freezes, heating, delayed notifications, camera-related crashes and inconsistent battery behavior, while individual Beta 5 users described both unchanged battery life and a more sluggish feel. Those experiences vary by device and user, so they do not provide a universal performance verdict.
The Quick Settings layout editor is also absent or rolled back in Beta 5. Its return before the final QPR2 release remains undecided.
Builds, compatibility and the road to stable QPR2
The stable Android 17 QPR2 release is planned for December 2026, but no exact day is available. Until then, Beta 5 should be treated as software for development, testing and feedback. The update screen warns that pre-release software may contain errors and defects that affect normal device operation.
Android 17 QPR2 also introduces restrictions on programmatic USSD requests used for call forwarding, a change intended to reduce fraud. Non-call-forwarding USSD requests are unaffected.
