Google released Android 17 QPR2 Beta 7 on October 9, 2026, and its release notes list a fix for idle battery drain tied to Flip to Shh plus a fix for HTTPS downloads that failed instantly. If you have a Pixel enrolled in the QPR2 beta, this is the build that targets two of the most annoying everyday bugs: a phone that loses charge overnight and a download that dies the moment you tap it.
TL;DR: Android 17 QPR2 Beta 7 (build CP41.260831.016) fixes idle battery drain when Flip to Shh stops deep sleep and HTTPS downloads failing through the system DownloadManager. It carries the 2026-10-05 security patch and supports 23 Pixel models. Pixel 11 Pro Fold owners may need to set up Face Unlock again.
What Android 17 QPR2 Beta 7 fixes
Google lists two headline fixes in the Android Developers release notes. The first is excessive battery drain while the phone sits idle, which happened when Flip to Shh kept the device from entering deep sleep. The second is HTTPS downloads that failed immediately when an app started them through the system DownloadManager.
Picture the first bug in daily life. You flip the phone face down on a nightstand, go to sleep, and find the battery noticeably lower in the morning with no obvious culprit.
| Detail | Android 17 QPR2 Beta 7 |
|---|---|
| Release date | October 9, 2026 |
| Build | CP41.260831.016 |
| Security patch level | 2026-10-05 |
| Google Play services | 26.28.33 |
| Known issue | Pixel 11 Pro Fold: Face Unlock may need re-enrolling |
That small table hides a useful detail. The security patch level jumped from 2026-08-05 in Beta 6.1 to 2026-10-05 here, so this beta moves you onto a much newer patch level.
The Flip to Shh battery drain
Flip to Shh is the Pixel gesture that silences the phone when you lay it screen down. Google’s notes spell it that way, and they say the bug stopped the device from reaching deep sleep, which is the low power state a phone should settle into when nobody is touching it.
The notes reference issue tracker entries #560036427 and #569079944 but publish no drain figure, so how bad it was for any one person is unknown. The same fix also appears in the QPR3 track, which we covered in our QPR3 Beta 1 fixes piece.
The gap between a quiet phone and a phone that never quite sleeps is the kind of thing nobody notices until they check the battery graph. That is why a fix like this matters more than its one line in the changelog suggests.
Download failures and two developer changes
The DownloadManager bug (issue #562833711) hit any app that handed an HTTPS download to the system service. The download simply failed at once, which is the sort of thing that looks like a flaky connection until it keeps happening.
Two platform changes in this QPR2 release matter mostly to app developers. Call-forwarding USSD codes such as *21# are no longer run by TelephonyManager.sendUssdRequest() when an app holds only the CALL_PHONE permission, and those requests return USSD_ERROR_NOT_ALLOWED. Google points developers to the ACTION_DIAL intent so the user confirms the change in the dialer, a restriction we explained in our call forwarding fraud report.
The second change affects broadcasts whose receivers all run inside the sending process. They no longer keep that process alive or stop it from being frozen, and anything undelivered is lost if the process is killed. Google recommends WorkManager or AlarmManager for background work instead.
Which Pixels can install it
Google’s QPR2 beta image page lists 23 supported devices, from the Pixel 6a and Pixel 7 through the Pixel 11 Pro Fold, including the Pixel Tablet and Pixel Fold. The Pixel 10a, Pixel 11, Pixel 11 Pro and Pixel 11 Pro XL are on the list as well.
One honest caution: the Pixel 11 Pro Fold has a known issue where Face Unlock may need to be set up again before it works properly. If you rely on it daily, expect a minute of re-enrolling after the update.
The same Google page is explicit about the images it hosts. They are meant for recovering a device that failed to boot after a beta over-the-air update, unlocking the bootloader triggers a full reset that deletes user data, and going back from a preview build to a public build also wipes the phone. Back up first, and use Google’s Get QPR beta builds page if you only want the update.
QPR2 or QPR3: what to keep in mind
Google is running two beta tracks side by side. QPR3 Beta 1 arrived on October 2, 2026 with builds DP11.260918.005 and DP11.260918.006, a security patch level of 2026-08-05 and Google Play services 26.32.34, according to the QPR3 release notes.
Beta 7 carries the newer security patch of the two, and both release notes list the same Flip to Shh fix. Not a dramatic change, but an honest one.
If your Pixel runs fine today, there is no urgency to switch tracks. If you have been watching your overnight battery number and suspected the beta, the release notes now name a specific cause and a fix on both tracks.
