Release notes

Beta 1

Release date May 20, 2025
Build BP31.250502.008
Emulator support x86 (64-bit), ARM (v8-A)
Security patch level May 2025
Google Play services 25.13.33
API diff

About Android 16 QPR1

Building on the initial release of Android 16, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.

Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed (for example, if there are upcoming features that might impact the user experience of your app).

Unlike developer previews and betas for unreleased, major versions of Android, these builds are suitable for general use.

Android 16 QPR1 includes some of the Material 3 Expressive changes covered in last week's announcements, with visual refreshes to notifications, quick settings, the lock screen, and the launcher.

How to get QPR1 Beta 1

You can install Android 16 QPR1 Beta 1 on any of the following Google Pixel devices:

  • Pixel 6, 6a, and 6 Pro
  • Pixel 7, 7a, and 7 Pro
  • Pixel Fold
  • Pixel Tablet
  • Pixel 8, 8a, and 8 Pro
  • Pixel 9, 9a, 9 Pro, 9 Pro XL, and 9 Pro Fold

See Get Android 16 QPR beta builds for details on how to get started. Note: All eligible devices enrolled in the Android Beta for Pixel program will be offered an over-the-air (OTA) update to Beta 1.

General advisories

Be aware of these general advisories about the release: * This release might have various stability, battery, or performance issues. * For users with accessibility needs, this release might not be appropriate for daily use. * Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps. * Android 16 QPR beta builds aren't Compatibility Test Suite (CTS)-approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 16 QPR beta builds.

Get support

Two primary support channels are available to you when developing and testing with Android 16 QPR1. The channel you should use to get support depends on where you are encountering your issue. * Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted. Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue See Where to report issues to find an issue template that best matches the type of issue that you are encountering. * Support for issues with other apps: Contact the app developer directly. To discuss issues or ideas with other developers working with the Android 16 QPR Beta, join the android_beta community on Reddit.