Google released Android 17 QPR3 Beta 2 on October 20, 2026, as build DP11.261002.005. Google’s changelog lists 21 issue categories as fixed. QPR means Quarterly Platform Release; the lock-screen connectivity option described by technology outlets is a separate reported change, not one of those listed fixes.

9to5Google reported that eligible devices range from Pixel 6a through Pixel 11 Pro Fold, including Pixel Tablet and Pixel Fold models. NeoTeo previously covered Android 17 QPR2 Beta 5, an earlier release in the QPR series.

What Google lists among the 21 fixes

Google groups the fixes across system reliability, connectivity, interface behavior, and app and developer issues. The release notes date Beta 2 and identify its build, security patch level of 2026-10-05, Google Play services version 26.36.33, and emulator support for x86 (64-bit) and ARM (v8-A). The official release notes list these issue categories:

Reliability and display

  • Intermittent crashes and reboots during normal use.
  • Unexpected shutdowns during WhatsApp video calls.
  • Lock-screen notifications overlapping and panel animations stuttering.
  • Screen recording freezing and stopping frame capture after the display rotates.
  • System UI, fonts, and apps appearing abnormally small despite display-size settings.
  • A black, unresponsive display after a phone call ends.
  • Excessive idle battery drain after Face Unlock or camera use, caused by motion sensors remaining active.

Connectivity and Quick Settings

  • Persistent text on the Internet Quick Settings tile when mobile data is active without Wi-Fi.
  • Cellular data, MMS, and hotspot connection failures on Dish Network.
  • Wi-Fi Aware failing to establish later data paths after an accept-any responder network request is released during connection confirmation.
  • A misaligned Bluetooth subtitle in Quick Settings.
  • Bluetooth pairing failures caused by connection timeouts.
  • VoLTE, VoNR, and Wi-Fi calling being unavailable on the IT&E network.
  • Wi-Fi Calling being unavailable on the OXIO network.

Apps, interface, and developer tools

  • The monochrome system theme not applying to the media-output dialog when external audio devices are connected.
  • A misplaced pin icon beside pinned apps in the share sheet.
  • Unexpected API lint and source-compatibility errors triggered by internal PublishedApi declarations.
  • The Terminal app failing to launch the Linux development-environment virtual machine after installation.
  • A paired watch continuing to ring after an incoming call is answered on the phone.
  • Airbnb failing to connect when sending messages.
  • The app drawer closing unexpectedly when the keyboard language changes.

What QPR means for Android apps

Google describes QPRs as quarterly releases delivered to AOSP and Pixel devices as Feature Drops. Google says these updates do not include API changes that affect apps, and it provides beta images so developers can test their apps against QPR builds. That makes the beta relevant to app teams as a test build for a quarterly platform release, as well as to Pixel users following system fixes.

Wallpaper and other interface changes

In Depth Tech Reviews walks through Android 17 QPR3 Beta 2’s wallpaper, lock-screen, and app-bubble interfaces

9to5Google also described Wallpaper & Style options for theme packs, custom icons, shape effects, animation, and weather effects. A walkthrough by In Depth Tech Reviews covers these customization menus, lock-screen settings, and app bubbles.

A reported lock-screen control for connectivity

Android 17 QPR3 Beta 2 lists 21 bug-fix categories

Android Central and La Razón reported a Lock Quick Settings connectivity option that requires unlocking the phone before changing Wi-Fi, Bluetooth, Airplane mode, or mobile data from Quick Settings. They also describe Flashlight, Auto-rotate, and Battery Saver as remaining accessible without unlocking.

The option restricts access to those connectivity controls from the lock screen. A person holding the phone can still power it off or let its battery run down, so the setting cannot guarantee that the device stays online or is recovered.