Android 12 Developer Preview 3
Release date: April 21, 2021
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: April 2021
Google Play services: 21.12.12
About Android 12 Developer Preview 3
Developer Preview 3 is now available, with the latest features and changes to try with your apps. This release is for developers only, to help with early development, testing, and feedback. Android 12 Developer Preview 3 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.
How to get Developer Preview 3
You can install this release on any Pixel 3, 3a, 4, 4a, or 5 series device.
If you’re already running a Developer Preview build, you will automatically receive an over-the-air (OTA) update to Developer Preview 3. 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 Developer Preview 3 is the first Android 12 release that you're trying, see Get Android 12 for details on how to get started.
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.
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 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 12 Developer Preview, join the android_beta community on Reddit.
What's new in Developer Preview 3
Android 12 Developer Preview 3 includes several new features and changes to try out:
- Changes in backup and restore
- Android App Links verification changes
- Provide apps direct access to tombstone traces
- Improved refresh rate switching
- Video encoding improvements
- Splash screen API
- Exact alarm permission
- Enable screen off for NFC payments
- Vendor-supplied native shared libraries
- Web intent resolution
- Restrictive App Standby bucket
- New phone call notifications allowing for ranking importance of incoming calls
- Enriched image support for notifications
- Quad bayer camera sensor support
- Device chipset information
- Companion Device Manager profiles
- Android playlists (using the
MediaStore.Audio.Playlistsclass) are now deprecated. If your app currently uses Android playlists, we recommend migrating to alternative methods.
Top resolved issues
The following issues have been resolved in Android 12 Developer Preview 3:
- Fixed an issue that caused
MediaStylenotifications to be cut off if they didn't have a
MediaSessionattached. (Issue #183034467)
- Fixed an issue that could prevent files from being copied from a USB drive. (Issue #183625563)
- Fixed an issue that could cause custom layout notifications to not be shown. (Issue #182630774)
Other resolved issues
- Fixed an issue on Android Auto where night mode on Android Auto was sometimes toggled when toggling dark mode on the phone.
- Fixed an issue on Android Auto where the top status bar that shows time, weather, and system details was sometimes not transparent and appeared as a black bar when running Android Auto projection.
- Fixed an issue on Android Auto where the bottom rail sometimes appeared as a black bar.
- Fixed an issue on Android Auto where the phone sometimes became unresponsive and required a reboot.
- Fixed an issue for Android Enterprise where a device with a work profile was unable to change the system UI style.
Top open issues
See top open issues for the latest list of top open issues that have been reported by developers.
Other known issues
Based on our testing, you might encounter the following issues when using Android 12 Developer Preview 3. These issues are already known, so there’s no need to file additional reports for similar issues.
- When using the
SplashScreenAPI, app icons are sometimes cut off.
- When using the
SplashScreenAPI, after setting an Animated Vector Drawable and a
setOnExitAnimationListener(), the vector drawable's animation stops when the callback is called.
- In some scenarios, users of apps that have been granted the
Display over other appspermission 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
"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:  '.../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
<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.
- 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.
- When Android Auto is set up for the first time on a vehicle and if a user invokes Google Assistant, some users may experience a crash with Assistant. A workaround for this issue is to unplug and replug the USB connection to restart Android Auto. Google Assistant should then work correctly.
- When playing music on Youtube Music on Android Auto, some users may experience audio playing out of the phone instead of the vehicle speakers.
- When playing Google Podcast on Android Auto, some users may experience a crash with Google Podcast.
- When using Google Maps navigation on Android Auto, some users may experience issues with text being blurry.
- Users might face wireless connectivity issues using Android Auto version 6.2 or lower when connecting to a wireless compatible head unit. A fix for this issue is to upgrade Android Auto to version 6.3 or higher.
- 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.