Release notes

Android 12 Beta 2

Beta 2

Release date: June 9, 2021
Build: SPB2.210513.007
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: June 2021
Google Play services: 21.18.16
API diff:

About Android 12 Beta 2

Beta 2 is now available, with the latest features and changes to try with your apps. This release is suitable for development, testing, and general use. Android 12 is still in active development, so the Android system and apps 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.

How to get Beta 2

You can install this release on any Pixel 3, 3a, 4, 4a, or 5 series device.

If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 2. Remember to update your Android 12 SDK and the Android Emulator as well before you continue trying the latest features and changes. The best way to do this is using the SDK Manager in the latest preview version of Android Studio.

If Beta 2 is the first Android 12 release that you're trying, see Get Android 12 for details on how to get started.

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 Beta 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 Beta builds.

Get support

Two primary support channels are available to you when developing and testing with the Android 12 Beta. The channel you should use to get support depends on where you are encountering your issue.

Support for issues with Pixel devices, system issues, and issues with Google apps

Use the Android Beta 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 non-Pixel devices

To report issues with eligible devices from our device-maker partners, see the Android 12 Beta devices page to find a link to the device-maker's Android 12 Beta site.

Support for issues with other apps

Contact the app developer directly.

To discuss issues or ideas with other developers working with the Android 12 Beta, join the android_beta community on Reddit.

What's new in Beta 2

Android 12 Beta 2 includes several new features and changes to try out:

Top resolved issues

The following issues have been resolved in Android 12 Beta 2:

Developer-reported issues

  • Fixed various issues that could cause devices to crash and restart. (Issue #188608172)
  • Fixed an issue that caused the Settings app to crash when accessing the Accounts screen. (Issue #188572264)
  • Fixed issues that caused the gesture navigation indicator to be displayed in the wrong place on the screen after switching the device's screen orientation. (Issue #186487188, Issue #186203723)
  • Fixed issues that caused live wallpapers to crash and revert back to another wallpaper. (Issue #188636390, Issue #186092946)
  • Fixed an issue that caused the one-handed mode overlay information to remain even after the user exited one-handed mode. (Issue #188809589)
  • Fixed an issue that prevented notifications from being cleared when a user tapped Mark as read or Done on a notification. (Issue #183140902)
  • Fixed issues that caused no haptic feedback to occur when using certain gestures or performing certain actions. (Issue #188643385, Issue #188647132)
  • Fixed an issue that caused the system volume bar to appear larger than intended. (Issue #188865157)
  • Fixed an issue that prevented Always On Display mode from working in certain cases. (Issue #189298635)
  • Fixed an issue that caused a NullPointerException to be thrown when calling the setDeviceAddress() method using a device Bluetooth address that was null. (Issue #186574846)

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

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

All apps

  • Due to an issue with WebView, users who install Android Beta 2 on a device that is currently running a public release version of Android may experience intermittent app crashes. To work around this issue, disable and then re-enable Android System WebView by going to Settings > Apps > All apps > Android System WebView > Disable > Disable app > Enable.
  • 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.
  • When a user attempts to add another account to the device under Settings > Passwords & accounts, the UI turns black and the back button becomes unresponsive.

Google apps

  • In some cases after updating a device to Beta 2, Google Maps crashes whenever it is launched by a secondary user.

Android platform

  • When using the SplashScreen API, app icons are sometimes cut off.
  • When using the SplashScreen API, after setting an Animated Vector Drawable and a setOnExitAnimationListener(), the vector drawable's animation stops when the callback is called.

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.

  • The latest preview version of the Android SDK Build Tools (31.0.0 rc5) is not compatible with Android Studio versions prior to Android Studio Arctic Fox.

Android Enterprise

  • 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 playing music on Youtube Music on Android Auto, some users may experience audio playing out of the phone instead of the vehicle speakers or no audio at all in Toyota Cars.
  • When using Google Maps navigation on Android Auto, some users may experience issues with text being blurry.
  • Users may face issues while selecting a destination in Waze.
  • Phone may become unresponsive or stuck on the lock screen after starting Android Auto.
  • In some scenarios, Google Maps might not be able to provide different route options while using Android Auto.
  • Music may get paused when the phone is locked.
  • Users might hear Music audio while trying to reply to an SMS using the Google Assistant.
  • Automatic Day and Night switching may not work.

Android TV

  • 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.

Previous Beta releases

Android 12 Beta 1

Beta 1

Release date: May 18, 2021
Build: SPB1.210331.013
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: May 2021
Google Play services: 21.12.13
API diff:

What's new in Beta 1

Android 12 Beta 1 includes several new features and changes to try out:

Top resolved issues

The following issues have been resolved in Android 12 Beta 1:

Developer-reported issues
  • Fixed an issue that caused extra space to remain in the app drawer interface after a user disabled app suggestions. (Issue #186096754)
  • Fixed an issue that prevented Pixel phones from detecting when they were placed on a Pixel Stand. (Issue #186184469)
  • Fixed an issue that caused the Google app to crash when opening Discover or tapping an article in the Discover feed. (Issue #187540137)
  • Fixed an issue that prevented some devices from being able to boot after applying an OTA image. (Issue #180636356)
  • Fixed an issue that caused the system to prompt a user to turn off their mobile carrier connection when they were navigating advanced mobile network settings. (Issue #181585057)
  • Fixed that issue that prevented a device's display cutout from being hidden using the developer options. (Issue #183342310)
  • Fixed issues with RenderEngine that caused jankiness and, in some cases, caused a device to crash and restart. (Issue #183873177, Issue #184544726)
  • Fixed an issue that caused some devices to crash and fail to boot after the device was manually restarted. (Issue #184760958)
  • Fixed an issue that could cause CompatibilityChangeReporter log messages to be erroneously printed when calling SensorManager.registerListener(). (Issue #184660151)
Other resolved issues
  • Fixed an issue where, when Android Auto was set up for the first time on a vehicle and a user invoked Google Assistant, some users experienced a crash with Assistant.
  • Fixed an issue where, when playing Google Podcast on Android Auto, some users experienced a crash with Google Podcast.
  • Fixed an issue where, when connecting to a wireless compatible head unit, users sometimes had wireless connectivity issues if they were using Android Auto version 6.2 or lower.

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

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

Android platform
  • When using the SplashScreen API, app icons are sometimes cut off.
  • When using the SplashScreen API, after setting an Animated Vector Drawable and a setOnExitAnimationListener(), the vector drawable's animation stops when the callback is called.
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 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
  • 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 playing music on Youtube Music on Android Auto, some users may experience audio playing out of the phone instead of the vehicle speakers or no audio at all.
  • When using Google Maps navigation on Android Auto, some users may experience issues with text being blurry.
  • Users may face issues while selecting a destination in Waze.
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.