Gadgets

Android 17 QPR 2 Beta 1 Begins Rolling Out to Pixel Devices, Focus on Bug Fixes

Android 17 QPR 2 Beta 1 is now available for supported Pixel devices. It includes numerous bug fixes aimed at improving stability. However, the Pixel 6 and Pixel 6 Pro are not supported.

4 min read Reviewed & edited by the SINGULISM Editorial Team

Android 17 QPR 2 Beta 1 Begins Rolling Out to Pixel Devices, Focus on Bug Fixes
Photo by Daniel Romero on Unsplash

On July 20, 2026, Google began rolling out Android 17 QPR 2 Beta 1. According to a report by Timi Cantisano of Android Police, this beta is available for supported Pixel devices and includes numerous bug fixes. However, the Pixel 6 and Pixel 6 Pro are not supported. Android Police reports that this beta “brings new bug fixes to Android 17, offering a more reliable and stable experience.”

Detailed Fixes

QPR (Quarterly Platform Release) betas aim to improve the upcoming public update. QPR 2 Beta 1 includes many fixes focused on enhancing stability and reliability. Based on Google’s published fix list, the main items are organized below.

Bluetooth-related: A fix addresses an issue where re-pairing silently failed after the remote side lost bonding. This bug made it difficult for users to notice a lost Bluetooth connection, hindering reconnection with headsets or car systems.

Notification-related: A problem where media player controls would briefly appear when the device’s lock screen was activated, even though app notifications were disabled, has been resolved. Additionally, an issue where notifications randomly became invisible within the notification panel until a system restart has been fixed. This bug was reported under issue numbers #526139207 and #522657034.

System Stability: A fix addresses a system crash during Gemini calls that caused unexpected restarts on Pixel devices (Issue #505750489). As Gemini, the core of Google’s AI assistant, becomes more widely used, this fix is practically significant.

Touch Interaction: A problem where performing a multi-finger drag-and-drop operation caused the source application to stop receiving subsequent touch events has been resolved (Issue #516836306). This may be related to touch input issues on Pixel devices previously reported in our article “Android 17 Touchscreen Bug on Pixel Devices.”

Security and Cryptography: A fix addresses an issue where ML-DSA key generation failed with an exception when the string “NONE” was used as a digest instead of a class constant (Issue #525612735). ML-DSA is a standard for post-quantum cryptography, making this fix relevant to the future security foundation.

Accessibility: An improvement was made to AccessibilityNodeInfo.toString(), where window bounds were incorrectly logged using screen bounds, leading to misleading accessibility debug data (Issue #520428442). This fix contributes to better debug accuracy for users of screen readers and similar tools.

Other fixes: An issue where window-level UI blur effects failed to render has also been fixed. While network-related issues pointed out in our article “Android 17 Wi-Fi Bug Concentrated in Google Apps” are not directly included in this beta’s fix list, overall stability can be considered improved through QPR 2 Beta 1.

Pixel 6/6 Pro Not Supported

In this beta, the Pixel 6 and Pixel 6 Pro are not supported. This means these devices cannot participate in the QPR 2 Beta program, suggesting a gradual reduction in future QPR update availability. The Pixel 6 series was released in 2021, and Google has promised at least five years of software update guarantees. While excluding these devices from the beta does not immediately mean the end of mainline security updates, it can be seen as a sign that feature updates will eventually be phased out.

Beta Participation Requirements

Android 17 QPR 2 Beta 1 can be installed via OTA by users on supported Pixel devices who are enrolled in the Android Beta Program. As beta versions may contain unresolved issues compared to stable releases, caution is advised when installing on daily-use devices. Google encourages bug reports through feedback to be reflected in future public releases.

Editorial Opinion

In the short term, this beta release directly contributes to the quality improvement of the next QPR update. In particular, the Gemini-related crash fix is significant for promoting daily use of the AI assistant. The simultaneous fixing of multiple notification bugs also helps improve user experience. However, with the Pixel 6/6 Pro being excluded from the beta, users of older devices lose the opportunity to preview new features. It is necessary to monitor whether this decision will also affect support scope for the public release.

Long-term, while Google offers a seven-year update guarantee for the Pixel 8 and later, discontinuing beta support for older models can be interpreted as a gradual phase-out toward the end of software support. For a company that strengthens hardware-software integration, a strategy of gradually reducing feature additions to older devices is two-sided with stimulating demand for upgrades to new products. On the other hand, the user community for the Pixel 6 series remains large, and early termination of support risks negatively impacting brand loyalty.

References

Frequently Asked Questions

Which Pixel devices are compatible with Android 17 QPR 2 Beta 1?
This beta is available for supported Pixel devices excluding the Pixel 6 and Pixel 6 Pro. The specific list of compatible devices can be verified on Google's Android Beta Program website. Pixel 7 series and later are the main targets.
If I install the beta, can I update to a stable version later?
Yes. Devices enrolled in the beta program can transition via OTA update at the next stable release. However, note that downgrading from a beta to a stable version may require data wipe, so caution is advised.
Why are the Pixel 6 series not supported?
Google has not officially disclosed the reason. Since QPR betas are intended for testing new features, it is speculated that hardware constraints or testing resource prioritization are behind this decision. Security updates are expected to continue.
Source: Android Police

Comments

← Back to Home