Android 17 Beta 3 Is Here: Everything You Need to Know

In This Article

AI Summarize

Google has officially rolled out Android 17 Beta 3 (build CP21.260306.017) to all eligible Pixel devices, and it’s a big one. With update packages ranging from 2.93 GB to over 3.5 GB depending on your device, this is one of the largest beta drops in recent memory. But size aside, Beta 3 is a genuinely important milestone in the Android 17 development cycle. Here’s a deep dive into everything that’s changed, what’s been fixed, and whether you should install it on your daily driver.

The Android beta program has rolled out its latest update, Android 17 QPR3 Beta 3, based on Google’s March 2026 Feature Drop for Pixel devices, bringing platform improvements, performance optimizations, and several user-requested features that have been years in the making.

Android 17 Beta 3 Is Here: Everything You Need to Know About Build CP21.260306.017

What Is Android 17 Beta 3, and Why Does It Matter?

Android 17 Beta 3 represents a critical stage in Google’s pre-release development pipeline. According to Google’s latest release notes, Beta 3 has reached Platform Stability. This means the core APIs and system behaviors are now locked in for developers to build against. If you’ve been on the fence about running a beta on your primary device, this is generally the build where that becomes a more reasonable proposition.

Android 17 has reached Platform Stability with Beta 3. The API surface is now finalized — this is the time to complete compatibility testing and publish your Android 17-targeted apps to the Google Play Store.

If you maintain an SDK, library, tool, or game engine, releasing your updates promptly is critical to ensure downstream developers aren’t blocked from adopting the latest SDK features.

Below is a summary of new capabilities, behavior changes, and improvements introduced in Android 17 Beta 3.

That said, it’s still a beta, and there are known issues that haven’t been resolved yet. More on that below.

Release Notes
- Release date: March 26, 2026
- Builds: CP21.260306.017
- Emulator support: x86 (64-bit), ARM (v8-A)
- Security patch level: 2026-03-05
- Google Play services: 26.02.35

Media and Camera

Photo Picker Customization: The PhotoPickerUiCustomizationParams API now lets you adjust the photo picker’s grid view aspect ratio — switching from the default 1:1 square to a 9:16 portrait layout for better UI integration.
RAW14 Image Format: Professional camera apps can now capture 14-bit-per-pixel RAW images using the new ImageFormat.RAW14 constant, unlocking maximum detail and color depth on compatible sensors.
Vendor-Defined Camera Extensions: Hardware partners can now define custom camera extension modes (such as “Super Resolution” or AI-based enhancements), queryable via the isExtensionSupported(int) API.
Camera Device Type APIs: New APIs let you identify whether a camera is built-in hardware, an external USB webcam, or a virtual camera.
Bluetooth LE Audio Hearing Aids: A dedicated device category (AudioDeviceInfo.TYPE_BLE_HEARING_AID) enables apps to distinguish hearing aids from generic LE Audio headsets, supporting tailored UI icons.
Granular Hearing Aid Audio Routing: Users can now independently route system sounds — notifications, ringtones, and alarms — to either connected hearing aids or the device speaker. This is handled at the system level and requires no API changes from developers.
Extended HE-AAC Software Encoder: A new system-provided encoder (c2.android.xheaac.encoder) supports both high and low bitrates, delivering significantly better audio quality under low-bandwidth conditions. Mandatory loudness metadata support ensures consistent playback volume.

Performance and Battery

Reduced Wakelocks for Idle Alarms: A new callback-based variant of AlarmManager.setExactAndAllowWhileIdle accepts an OnAlarmListener instead of a PendingIntent. This lowers power consumption and reduces long partial wakelocks for apps requiring precise callbacks during Doze or Battery Saver modes — particularly useful for medical monitors and messaging services.

Privacy and Security

Post-Quantum Cryptography (PQC) Hybrid Signing: The new v3.2 APK Signature Scheme combines classical signatures (RSA/Elliptic Curve) with ML-DSA signatures, al

System-Provided Location Button: A secure, system-rendered location button can now be embedded via Jetpack. Tapping it grants your app one-time precise location access for the current session, with no system dialog required. The USE_LOCATION_BUTTON permission is needed.

Discrete Password Visibility: The “Show passwords” setting is now split between touch input (briefly echoing the last character) and physical keyboards (hidden immediately by default). Standard framework components handle this automatically; custom input fields should migrate to the ShowSecretsSetting API.

User Experience and System UI

Widget Support on External Displays: Widget rendering is now more visually consistent across varying pixel densities. RemoteViews.setViewPadding now accepts complex units (DP/SP), and widgets can retrieve display-specific metrics via OPTION_APPWIDGET_DISPLAY_ID.
Desktop Interactive Picture-in-Picture (iPiP): Apps can request placement in a “pinned” windowing layer during desktop mode (enabled by default on external displays). Pinned windows are always-on-top and remain fully interactive. Requires both USE_PINNED_WINDOWING_LAYER and PiP permissions.
Hidden Home Screen App Labels: Users can now hide app labels on the home screen — make sure your app icon is distinctive and easily recognizable.
Redesigned Screen Recording: A new floating toolbar streamlines recording controls and capture settings. The toolbar UI is automatically excluded from the final recorded video.
Bubbles: The windowing mode feature introduced in Beta 2 is now fully enabled.

Core Functionality and Health

VPN App Exclusion Settings: VPN apps can use the ACTION_VPN_APP_EXCLUSION_SETTINGS intent to open a system-managed screen where users can select specific apps to bypass the VPN tunnel (split-tunneling).
Dynamic System Font Fallback: Android now supports runtime updates to the font fallback chain, enabling emoji and typography improvements to be delivered without a full OS update.
OpenJDK 21 & 25 Updates: Integration of modern OpenJDK features brings updated Unicode support and enhanced SSL handling for named groups in TLS.
Health Connect Device Data Providers (DDPs): Health Connect can now distinguish between app-generated data and data originating directly from system-verified hardware sources, such as Wear OS watches or the device itself.

Known Issues: Google still has an extensive list of open issues or bugs. See top open issues that have been reported by developers and users.

Eligible Devices

Android 17 Beta 3 is available for a wide range of Pixel hardware via over-the-air (OTA) update. The eligible device list includes:

Pixel 6, 6 Pro, 6a
Pixel 7, 7 Pro, 7a, Pixel Fold
Pixel 8, 8 Pro, 8a
Pixel 9, 9 Pro, 9 Pro XL, 9 Pro Fold, 9a
Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a
Pixel Tablet series

If you were already enrolled in the Android 17 Beta program and haven’t opted out, you’ll receive Beta 3 automatically. New enrollees can sign up at google.com/android/beta. Note that as of this writing, the Pixel 10a hasn’t yet appeared on the beta enrollment page for some users, though it is listed as eligible.

How to Install Android 17 Beta 3

Getting the update is straightforward for those already enrolled in the beta program. Users who previously enrolled in Android 17 Beta will automatically receive this update over-the-air. New users can enroll their eligible Pixel devices through the Android Beta Program to receive immediate access.

How to Enroll in the Beta Program

Joining the Android beta program requires just a few steps:

Visit the official Android Beta Program website
Sign in with the Google account associated with your Pixel device
Select your eligible device from the list
Confirm enrollment and accept program terms
Wait for the over-the-air (OTA) update notification
Download and install the beta update

Once enrolled, your device automatically receives all subsequent beta updates until you manually opt out. The initial update size varies depending on your current Android version, with some users reporting downloads ranging from 555MB to over 2GB.