Google Pixel users are in for both relief and a note of caution as Android 14 QPR3 Beta 2 rolls out. This latest beta aims to address a host of bugs that emerged in last month’s release, promising to stabilize the user experience. However, early reports indicate that sideloading the update carries a significant risk of bricking your device.

What’s getting fixed

Android 14 QPR3 Beta 2 is all about patching up the issues that made their way into the previous beta. Here’s the complete changelog that Google shared on Reddit.

  • Fixed an issue that sometimes caused a device to crash or restart unexpectedly.
  • Fixed an issue that sometimes caused a device to crash or restart unexpectedly while updating apps after the device was flashed.
  • Fixed issues that caused a device to display a blank, black screen after booting from flash.
  • Fixed an issue that caused a device to crash and display a blank, black screen after switching to a secondary user.
  • Fixed issues when always-on display mode was enabled that interfered with the “Double tap to wake” gesture and prevented the device from unlocking if the user tried to use their fingerprint to unlock the device.
  • Fixed an issue that sometimes caused battery information to not display correctly in the system settings, status bar, and on the lock screen.
  • Fixed issues that prevented device-to-device transfers and backup and restore from working.
  • Fixed various issues that were impacting system stability, performance, and camera.

The sideloading dilemma

While the fixes are tempting, be aware that manual sideloading of this update has resulted in several bricked Pixel devices, including flagships like the Pixel 8 Pro. The folks over at 9to5Google experienced the same with multiple devices. A Redditor also made the same claim. This seems to be an unwelcome trend, as a similar situation occurred with the release of the Android 15 Developer Preview 1.

If you’re absolutely determined to update right away, the Over-the-Air (OTA) patch seems to be working without issue. However, it may take longer to arrive compared to a sideload.

Unless you’re a developer or someone who thrives on the bleeding edge of software (and is comfortable troubleshooting unexpected problems ), it’s probably wise to hold off on sideloading the update. Stick with the stable release for now, or wait for the slower-but-safer OTA update. If you absolutely must try the beta, take precautions by enabling OEM Unlock on your device beforehand.

While Android 14 QPR3 Beta 2 delivers much-needed stability improvements, the risks associated with sideloading might outweigh the benefits for most users. If you value the uninterrupted use of your Pixel device, waiting for the official OTA update is the more prudent course of action.

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.

Dwayne Cubbins
2649 Posts

I cover fast-moving stories across apps, online platforms, and everyday tech — phones, wearables, consoles, and whatever else people are fighting with this week. Bugs, rollouts, scams, policy enforcement, and the occasional internet-culture rabbit hole are all fair game. My goal is simple — make confusing tech news readable. When I'm not working, I'm working out or chilling with my dog. Got a tip? You can find me on X @dcubbins.

Next article View Article

[U: It's finally here] Fitbit app still missing dark mode support, but you can enable it on Android using this workaround

Update 21/08/25 - 5:55 pm (IST): After making users wait a long time, Google has finally introduced native dark mode support on the Fitbit app. This new eye...
Aug 21, 2025 4 Min Read