Google released Android 17 QPR3 Beta 2 on October 20, 2026, and its release notes list 21 fixed issues and no known issues. The headline item is a fix for devices that intermittently crash and reboot during normal use, which Google ties to eight separate issue tracker entries.
If your Pixel has ever restarted on its own while you were navigating or halfway through a call, that line is the one to read. The rest of the list is a mix of battery, calling and carrier repairs, and the build reads like a cleanup release.
TL;DR: Android 17 QPR3 Beta 2 is a repair build, not a feature drop. Google lists 21 fixes, led by intermittent crashes and reboots, plus shutdowns during WhatsApp video calls, a black screen after ending calls and idle battery drain from motion sensors. No known issues are listed, but it is still a beta, so think twice before putting it on a phone you cannot afford to lose for a day.
What Android 17 QPR3 Beta 2 changes
Google’s notes give the build as DP11.261002.005, dated October 20, 2026, with a security patch level of 2026-10-05 and Google Play services 26.36.33. They itemize no new features and say QPR releases carry no app-impacting API changes.
Beta 2 lands 18 days after Beta 1, which our QPR3 Beta 1 coverage called mostly a repair job. The same pattern holds here.
| Release | Date | Build | Security patch | Fixes listed |
|---|---|---|---|---|
| QPR3 Beta 1 | October 2, 2026 | DP11.260918.005 and DP11.260918.006 | 2026-08-05 | 20 |
| QPR3 Beta 2 | October 20, 2026 | DP11.261002.005 | 2026-10-05 | 21 |
The patch level moved forward two months between builds, but the fix list is where Beta 2 earns its keep.
The fixes you would actually feel
The line about devices that intermittently crash and reboot points to eight tracker entries, and Google does not say what triggered them. Treat it as a stability fix rather than one patched bug. Eight reports behind a single line item is the detail most coverage will skip, and it suggests the problem was not rare.
Two other fixes hit everyday moments. One covers a device shutting down during WhatsApp video calls, and another covers a display that turns black and stops responding after you end a phone call. Anyone who has hung up and then stared at a dead screen will know why those matter.
Battery gets one entry of its own: high idle drain caused by motion sensors that stayed active after Face Unlock or the camera was used. It is the sort of problem you notice only when the percentage keeps falling on a phone that has been sitting on a desk.
Carrier and single app repairs
A handful of fixes only matter if you are on the right network. Google lists cellular data, MMS and hotspot failures on Dish Network, VoLTE, VoNR and Wi-Fi calling gaps on IT&E, and Wi-Fi Calling gaps on OXIO.
App fixes are just as narrow. The notes include the Airbnb app failing to connect when sending messages, the Terminal app failing to launch its Linux development environment after installation, and a Wi-Fi Aware failure that stopped later data paths from forming. Most readers will never hit these, but the people who do tend to hit them every day.
Smaller interface annoyances
The interface fixes are the least dramatic and probably the most visible. The Internet Quick Settings tile no longer shows persistent text when mobile data is active without Wi-Fi, and the media output dialog now respects the monochrome theme when external audio devices are connected.
Others include system UI and apps rendering at an abnormally small scale, a misaligned Bluetooth subtitle in Quick Settings, a pin icon that glitched next to pinned apps in the share sheet, and the app drawer closing when you switch keyboard language. A paired watch that kept ringing after you answered on the phone is also on the list. The previous cycle’s QPR2 Beta 7 fixes followed the same repair pattern.
Whether this beta belongs on your daily phone
Google lists no known issues for Beta 2, which is a good sign but not a guarantee. A clean known issues section only means nothing has been written down yet.
The release notes page does not name supported Pixel models, so confirm yours before enrolling. If your phone is your only phone, waiting for the stable release is the safer move.
