Welcome to Android 12 Developer Preview! Please give us feedback early and often, and help us make Android 12 the best release yet!

Release notes

Android 12 Developer Preview 1

Release date: February 18, 2021
Build: SPP1.210122.020.A3
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: February 2021
Google Play services: 21.02.12
API diff:

About Android 12 Developer Preview 1

Welcome to Android 12 Developer Preview! This release is for developers only, to help with early development, testing, and feedback. Android 12 Developer Preview 1 is an early baseline build that’s still in active development, so the Android system and apps running on it might not always work as expected.

As with previous versions, Android 12 includes behavior changes to help improve performance, battery life, security, and privacy. In some cases, these changes can affect apps until they are updated to support Android 12, so you might see impacts ranging from minor issues to more significant limitations. In general, most apps will work as expected, as will most APIs and features, but please review the known issues listed on this page to get a better idea of what to expect.

You can install this release on the following Google Pixel devices for development and testing:

  • Pixel 3 and 3 XL
  • Pixel 3a and 3a XL
  • Pixel 4 and 4 XL
  • Pixel 4a and 4a (5G)
  • Pixel 5

See Get Android 12 for details on how to get started. Developers can also use the Android Emulator to aid with development and testing.

General advisories

Please be aware of these general notes about the release:

  • This release might have various stability, battery, or performance issues on supported devices.
  • 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 includes Google’s apps as well as other apps.
  • Android 12 Developer Preview builds are not 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 12 Developer Preview builds.

Get support

Two primary support channels are available to you when developing and testing with the Android 12 Developer Preview. 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 Developer Preview 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 below 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 12 Developer Preview, join the android_beta community on Reddit.

Known issues

Based on our testing, you might encounter the following issues when using Android 12 Developer Preview 1. These issues are already known, so there’s no need to file additional reports for similar issues.

Apps

  • In some scenarios, users of apps that have been granted the Display over other apps permission and render full screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.

Android platform

  • Due to an issue affecting WebView, developers currently can't enable or test the Schemeful Same-Site changes on Android 12. We've resolved this issue internally, and it will be included in a future developer preview release. In the meantime, you can still test your app for the other SameSite changes on Android 12. For more information, see Modern SameSite cookie behaviors in WebView.
  • On some devices, the device intermittently disconnects from Wi-Fi even when the Wi-Fi signal is strong. To work around this issue, toggle the device's Wi-Fi off and then back on.
  • Upgrading from a production build without wiping data might lose HID controls for previously-paired Bluetooth devices. To work around, unpair the device and re-pair, or perform a factory reset.
  • On some devices, the device displays a "System UI keeps stopping" message if the user tries to take a screenshot by pressing Power + Volume Down from the Lock screen.

Android Jetpack

Android Studio and tools

  • When installing an app that has a targetSdkVersion of 'S' from Android Studio, developers might see the following error:

    Installation did not succeed.
    The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
    List of apks:
    [0] '.../build/outputs/apk/debug/app-debug.apk'
    Installation failed due to: 'null'
    

    The likely cause is that one or more of the app's activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest canary release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.

Android Enterprise

  • After setting app restrictions on Chrome, the app will crash upon launching it. To fix, update to Chrome version 89 or above.
  • If you toggle the work profile on and off repeatedly, you might find that your screen lock pattern isn’t accepted and you are unable to unlock the device. Restart the device to unlock.
  • A device can have a device-wide password and a work profile security challenge. When you tap a work app’s notification on the lock screen, you are first prompted to unlock the device, and then prompted to unlock the work profile. If the work challenge does not prompt you to unlock, swipe away the task from the recent apps or Overview screen, and then open the work app again.

Android Auto

  • When toggling the dark mode on the phone, the night mode on Android Auto might get toggled as well.
  • When running the Android Auto projection, the top status bar that shows time, weather, and system details might not be transparent.

Android TV

  • Setup using the Google Home App is not supported on this build.
  • Hotplugging the HDMI cable might cause video playback to fail on some display sinks.
  • Some pages in the TV Settings app contain empty placeholders in this release.