Android 17 QPR2 Beta 1: New Fixes for Pixel Phones
By Inflix Google has released Android 17 QPR2 Beta 1 for supported Pixel phones. The update focuses on system stability, notification reliability, Bluetooth connections and several interface problems reported by beta testers.
Most importantly, the update fixes a system crash that could restart a Pixel phone when Gemini was opened. It also addresses notifications that disappeared from the notification shade until the device was restarted.
However, this remains beta software. Therefore, users should understand the risks before installing it on their main phone.
Android 17 QPR2 Beta 1 Release Details
Android 17 QPR2 Beta 1 was released on 20 July 2026. Google lists the following technical details for the update:
| Detail | Information |
|---|---|
| Release date | 20 July 2026 |
| Build number | CP41.260701.005 |
| Security patch | 5 July 2026 |
| Google Play services | 26.23.34 |
| Release type | Quarterly Platform Release Beta |
| Supported emulators | x86 64-bit and ARM v8-A |
QPR means Quarterly Platform Release. These updates allow Google to test fixes and improvements before they are included in future stable Pixel updates and Feature Drops.
In addition, Google says Android 17 QPR2 contains a minor SDK release. It does not include planned behaviour changes that should require major compatibility work from app developers.
Android 17 QPR2 Beta 1 Fixes Gemini Reboots
The most important consumer-facing fix addresses unexpected Pixel restarts.
According to Google’s official release notes, a system crash could cause Pixel devices to reboot when Gemini was invoked. Android 17 QPR2 Beta 1 fixes that problem.
This fix may be especially useful for people who regularly launch Gemini through the power button, voice commands or other shortcuts. As a result, Gemini should no longer trigger the specific system crash identified by Google.
Nevertheless, the update is still being tested. A fix listed in the release notes does not mean every unrelated Gemini or performance issue has been resolved.
Invisible Notifications Have Been Fixed
Some Android 17 users found that notifications randomly disappeared from the notification shade. The notifications could remain invisible until the phone was restarted.
Android 17 QPR2 Beta 1 includes a fix for this problem.
This issue could have caused users to miss messages, reminders or app alerts. Therefore, the correction should improve the reliability of one of Android’s most frequently used areas.
After installing the update, users should monitor the notification panel for a few days. They can submit feedback through the Android Beta Feedback app if notifications disappear again.
Bluetooth Re-Pairing Should Work More Reliably
Google has also fixed a Bluetooth problem involving remote bond loss.
Previously, Bluetooth re-pairing could fail silently after the saved connection information was removed by the other device. In simple terms, a Pixel phone could appear to reconnect to an accessory without completing the pairing process correctly.
The Android 17 QPR2 Beta 1 fix should make pairing more reliable for devices such as:
- Wireless earbuds
- Bluetooth headphones
- Smartwatches
- Car audio systems
- Portable speakers
- Game controllers
However, users may still need to remove an accessory from the Bluetooth settings and pair it again if old connection data remains on either device.
Lock-Screen Media Controls No Longer Flash Unexpectedly
Android 17 QPR2 Beta 1 fixes an issue that caused media controls to appear briefly on the lock screen.
The controls could flash when the device was awakened, even when notifications for the media app had been disabled. Although the problem was brief, it could reveal the name or artwork of recently played content.
Following the update, those controls should respect the app’s notification settings more consistently.
Multi-Finger Touch Input Has Been Corrected
Google has fixed a touch-input issue involving drag-and-drop gestures.
When users started a drag-and-drop action with multiple fingers, the source app could stop receiving later touch events. Consequently, the app might appear unresponsive until the gesture or activity was reset.
This improvement may be particularly helpful on the Pixel Fold and Pixel Tablet, where drag-and-drop tools are commonly used for multitasking.
It may also improve app testing for developers who design interfaces for foldable phones and larger screens.
Window Blur Effects Work Again
Another fix restores window-level blur effects.
In the affected build, blur effects could fail to appear. Moreover, the Allow window-level blurs option in Developer Options could reset after the phone was restarted.
Android 17 QPR2 Beta 1 addresses both behaviours. Therefore, apps and interface elements that rely on supported blur effects should render more consistently.
This change mainly affects developers and advanced users. Still, it may also improve the appearance of menus, backgrounds and other interface layers.
Accessibility Debugging Information Is More Accurate
The update fixes incorrect information produced by AccessibilityNodeInfo.toString().
Window bounds were being logged with screen-bound values, which could create misleading accessibility debugging data. Google has now corrected the reporting behaviour.
Most Pixel owners will not notice this change directly. However, it should help developers diagnose accessibility problems more accurately and create better experiences for users who rely on accessibility services.
Android 17 QPR2 Beta 1 Supported Pixel Phones
Google provides Android 17 QPR2 Beta 1 downloads for the following devices:
- Google Pixel 6a
- Google Pixel 7
- Google Pixel 7 Pro
- Google Pixel 7a
- Google Pixel Fold
- Google Pixel Tablet
- Google Pixel 8
- Google Pixel 8 Pro
- Google Pixel 8a
- Google Pixel 9
- Google Pixel 9 Pro
- Google Pixel 9 Pro XL
- Google Pixel 9 Pro Fold
- Google Pixel 9a
- Google Pixel 10
- Google Pixel 10 Pro
- Google Pixel 10 Pro XL
- Google Pixel 10 Pro Fold
- Google Pixel 10a
Notably, the Pixel 6 and Pixel 6 Pro are not included in Google’s official QPR2 Beta 1 device list. The Pixel 6a remains supported.
How to Install Android 17 QPR2 Beta 1
The easiest installation method is Google’s Android Beta Program.
- Back up important photos, messages and files.
- Visit the official Android Beta Program.
- Sign in with the Google account used on the Pixel phone.
- Find the eligible device.
- Select the option to join the Android 17 QPR2 beta.
- Open Settings on the Pixel phone.
- Go to System > Software updates.
- Check for the new update.
- Download and restart the phone.
Once the device is enrolled, future compatible beta updates should arrive over the air.
Alternatively, experienced users can use Google’s Android Flash Tool or download an official system image. Manual flashing carries additional risks and may erase the phone, depending on the method and device state.
Should You Install Android 17 QPR2 Beta 1?
Android 17 QPR2 Beta 1 may be worth installing if you are already running Android beta software and experiencing one of the fixed problems.
For example, the update is relevant if your Pixel has experienced:
- Reboots while launching Gemini
- Missing notifications
- Failed Bluetooth re-pairing
- Unexpected media controls
- Multi-finger touch problems
- Broken window blur effects
However, most users should avoid installing the beta on a primary phone. Beta builds may contain battery, connectivity, app compatibility or performance problems that Google has not yet documented.
Therefore, the safest choice is to wait for the stable Android 17 QPR2 release unless you need to test apps or are comfortable troubleshooting beta software.
Back Up Your Pixel Before Installing
Google recommends backing up the device before joining the beta programme.
Although enrolment usually does not require an immediate factory reset, leaving the beta at the wrong stage can erase all local data. In addition, manual flashing may require an unlocked bootloader and a complete device reset.
Before updating, users should check that the following items are safely backed up:
- Photos and videos
- Messages
- Authenticator accounts
- WhatsApp data
- Downloaded documents
- App login details
- Home-screen settings
Users can also read our guide to checking battery health on Android and iPhone before testing a major beta update.
What to Do If the Update Causes Problems
First, restart the Pixel phone after the installation has finished. Then, update all apps through the Google Play Store.
If a specific app stops working, clear its cache or contact the app developer. In addition, users can report operating-system problems through the Android Beta Feedback app included with preview builds.
Google also provides an official Android 17 QPR2 release notes page with confirmed fixes and build information.
For more troubleshooting advice, see:
- Install This Pixel Update Now to Fix Android 17 Problems
- Android 17 New Features You Should Try First
- Why Is My Phone Overheating? Causes, Risks and Fixes
Android 17 QPR2 Beta 1 Is Mainly a Stability Update
Android 17 QPR2 Beta 1 does not introduce a long list of major consumer features. Instead, it improves the parts of the system that Pixel owners use every day.
The Gemini reboot and invisible notification fixes are particularly important. Meanwhile, the Bluetooth, lock-screen and touch improvements should make Pixel devices more reliable.
Overall, existing beta users should consider installing the update. People using a Pixel as their main phone should wait for the stable release unless they accept the risks of unfinished software.
Frequently Asked Questions
What is Android Beta update?
Android 17 QPR2 Beta 1 is the first test build of Android 17’s second Quarterly Platform Release. It includes fixes and improvements that Google may later deliver through a stable Pixel Feature Drop.
When was Android 17 QPR2 Beta 1 released?
Google released on 20 July 2026.
What is the Android 17 QPR2 Beta 1 build number?
The official build number is CP41.260701.005.
Which security patch is included?
The update includes the Android security patch dated 5 July 2026.
Does Android 17 QPR2 Beta 1 fix Gemini reboots?
Yes. Google says the update fixes a system crash that could unexpectedly reboot a Pixel phone when Gemini was invoked.
Does the update fix missing notifications?
Yes. It fixes an issue that caused notifications to become invisible in the notification shade until the phone was restarted.
Is Android 17 QPR2 Beta 1 safe for a main phone?
It may work well enough for some users, but it remains pre-release software. Therefore, unexpected bugs, battery drain and app compatibility problems are still possible.
Will leaving the Android beta erase my phone?
It can. Google provides limited opportunities to leave after installing a stable release without wiping data. Leaving at another stage may require a factory reset, so users should always back up their phones.
