Google quietly pushed Android 17 QPR1 Beta 2 to Pixel testers on May 6, just two weeks after the first QPR1 preview. The update—build CP31.260423.012.A1 with the April 2026 security patch—doesn't parade new consumer-facing toys. Instead, it feels like a damage-control release: a compact, surgical set of bug fixes that address a handful of annoying and potentially serious issues.
What changed
The headline here is stability. Across coverage from multiple outlets the same fixes keep turning up, so you can be confident this is a polish-focused update. Notable resolved problems include:
- Terminal app failing to launch, showing an endless error dialog. (Issue #501751748)
- Date and weather overlapping the fingerprint area on the lock screen. (Issue #498106709)
- Incorrect disconnect when terminating a third active call from a car head unit (a concern for people who use Android Auto / head-unit integrations). (Issue #481492536)
- Mobile signal bars displaying as empty or greyed out despite active connectivity. (Issue #488358813)
- Custom themed app icons appearing enlarged after returning to the home screen. (Issues #453458883, #452939724, #473509945)
- A bug in the F2FS file system that could cause data corruption or system instability. (Issue #498762380)
- Visual glitches when moving apps in the recent items screen. (Issues #485468312, #496828676, #498193454)
- Navigation bar swipe gestures failing to switch between recent apps. (Issue #494847234)
- Bluetooth tethering toggle resetting to off after restarts or Bluetooth cycles, forcing users to re-enable tethering manually. (Issue #371660785)
That list covers the bulk of the public fixes. System images are available for Pixel 6 through Pixel 10 families, Pixel Fold and Pixel Tablet, and the Android Emulator; testers can enroll through the Android Beta Program or flash the images directly.
Why this matters (and why Google shipped it fast)
A couple of the fixes are more than mere UI polish. The F2FS file system patch stands out because of its potential to cause data corruption—something that warrants a quick follow-up build. The Terminal app crash and issues that affect phone call behavior in cars are also the kind of bugs that break workflows for power users and commuters, respectively.
Most of the outlets that dug into Beta 2 found no significant new features compared with Beta 1. That's expected: this QPR1 line is the path toward the Android 17 September Feature Drop rather than a feature-packed major OS bump. If you were hoping for the floating app bubbles, native app lock, or the new contact picker teased in earlier Android 17 betas, those are part of the broader Android 17 beta story rather than this quick QPR1 maintenance update—see our previous coverage of Android 17 Beta 3 for more on those additions.
If you use your phone with your car frequently, the head-unit call bug is an example of how mobile updates can ripple into in-car experiences—something we've seen before when Android Auto updates behaved oddly on some phones and cars. For background on how car integration issues can affect users, check this earlier look at Android Auto’s rough patches and fixes: Android Auto’s wobble.
Should you install it?
If you rely on your Pixel as a daily driver and can't tolerate the issues above, Beta 2 is worth installing—especially for the F2FS fix and the Terminal crash resolution. But remember: this is a beta build. Expect the normal instability and rough edges that come with pre-release software. If you don't like surprises, wait for the stable QPR1 roll-out later in the year.
In short: Beta 2 is a tidy, pragmatic update focused on reliability. It won't radically change how your phone looks or behaves day-to-day, but it aims to stop a few obvious things from breaking while Google readies the fuller September Feature Drop.
