Android 17 QPR2 Beta 1 Fixes Gemini Crash Bug

Google has released Android 17 QPR2 Beta 1 for Pixel devices, and the headline fix is a crash that rebooted phones whenever someone tried to open Gemini.

Build CP41.260701.005, released July 20, previews the Q4 2026 update scheduled for December. It carries the July 5 security patch and marks the start of the QPR2 beta cycle — the third quarterly release since Android 17 launched in June.

Gemini Crash and Seven Other Fixes

The most disruptive bug squashed in this build caused Pixel devices to unexpectedly reboot when invoking Gemini. That alone justifies the beta for anyone who uses the assistant regularly. Google also addressed notifications randomly turning invisible in the shade until a system restart — a bug that left users missing alerts without realizing they were gone.

The full fix list covers eight tracked issues: Bluetooth re-pairing failures after a remote bond loss, media player controls briefly flashing on the lock screen even with app notifications disabled, drag-and-drop gestures breaking multi-touch input, ML-DSA key generation failures when using the wrong digest constant, accessibility debugging data logging incorrect window bounds, and window-level blur effects resetting after a reboot.

None are individually dramatic beyond the Gemini crash, but the notification visibility bug and Bluetooth re-pairing fix address complaints that surfaced shortly after Android 17's rough first week.

Pixel 6 and 6 Pro Left Behind

The beta is available for the Pixel 6a through the entire Pixel 10 lineup, including the Pixel 10a. Missing from the list: the Pixel 6 and Pixel 6 Pro. Both devices reach their five-year end-of-life in October 2026, and Android 17 QPR1 will be their last update. Anyone on those phones looking for the Gemini crash fix will need to wait for a stable QPR1 patch or upgrade to a newer device.

Minimal Impact for Developers

Google describes QPR2 as a minor SDK release with no planned behavior changes and no app-impacting API modifications. Developers already targeting Android 17 should not need compatibility testing for this build. Enrolled Pixel owners can grab the OTA now through the Android Beta Program, or flash the factory image manually from the Android developer site.