Android 12 developer preview version released by Google

On February 18 (local time), Google unveiled a developer preview version of Android 12, the next major version of Android, and officially announced each function and release schedule of Android 12.

The released Android 12 developer preview version can be used by general users, but it is intended for developers to test applications for the full version. Google says that migrating from the preview version to the previous build from the original build requires a complete reset that deletes all user data from the device, so be sure to back up the data first.

The Android 12 release schedule will release the second and third preview versions in March and April 2021, respectively, and in May, the beta version will be released for general users as well. Beta 2 and 3 will be released in June and July, and the final beta version will be released in August. After the final beta adjustment is over, the full version of Android 12 will appear.

Android 12 updates revealed according to this developer preview version are as follows. Looking at the reliability and stability-related contents, first, the SameSite Cookie operation in WebView. Add new new site cookie behavior with Chrome and other browser updates. It has been strengthened in terms of security and privacy, and users can control the use of cookies with high transparency.

Next, Netlink MAC restrictions added. In Android 11, the Netlink MAC, which was restricted access according to API level 30, can be restricted in all applications regardless of the target SDK level.

Next is the component export stabilization. Revised the default handling of android (exported) to prevent apps from erroneously exporting activities, services and listeners. Then safer intent handling. In order to stabilize the handling of the PendingIntent, the application program explicitly requests a flag (FLAG_MUTABLE or FLAG_IMMUTABLE).

Next is the user experience tool. First is the introduction of compatible media transcoding. Media transcoding compatible for applications that do not support the HEVC format. For applications that do not support HEVC, the platform automatically transcodes the file into AVC.

It also supports AVIF images. For additional high-definition and high-definition, Android 12 supports AVIF as a picture format. Compared to the case of the existing JPEG, the quality of the same file size is greatly improved. For example, if the AVIF file size is 18.2KB, the file size is 20.7KB in JPEG format. The file size is larger than the AVIF format, but the image collapses when enlarged.

Next is the foreground service optimization. For applications targeting a new platform for foreground services where the app manages tasks for users, it blocks the foreground service from starting in the background.

Next, rich content insertion. New integrated APIs such as clipboard, keyboard, and drag and drop are supported so that dynamic content apps such as CG and animation can simply receive. In addition, Android 12 enables audio experience in conjunction with the vibration function built into the smartphone. For example, a video calling app can set custom ringtones with tactile feedback to identify the caller or simulate a racing game experience.

The following are immersive mode API improvements for gesture navigation. It simplifies the immersive mode and makes gesture navigation simple and consistent when viewing videos, reading books, or playing games. Also, the alarm UI was reorganized. The alarm design has been revamped and features are more modern and easy to use. The newly released preview version updates the control template itself and optimizes the system-wide animation to make it smoother.

Next is the alarm rate. While pushing the alarm to perform the activity, rather than performing the activity directly, but through an intermediary system, the execution speed is limited, so this intermediary system is restricted to urge the developer to discharge the intermediary system. Other improvements to Binder IPC calls. Focusing on delays and workload distribution, we implemented optimizations to lower the median.

Finally, application compatibility. When distributing a new platform version, application program compatibility is prioritized to improve the speed and ease of update. In Android 12, to give you more time, we opt out of the changes for most applications and update our tools and processes.

First, expanding the Google Play system update. The Google Play system updates are continuously expanded and a safe and consistent environment is provided that is not dependent on each application device. Android 12 added an Android runtime module that can push updates to the runtime, which is the core of the device, and the core library. This achieved improved runtime performance and accuracy, improved memory management efficiency, and accelerated Kotlin work.

Optimized for tablets, foldable smartphones and TVs. As the number of application users increases in large screen devices such as tablets, foldable smartphones, and TVs, optimization for tablets and construction of applications for foldable devices began. It also released a preview version of Android 12 developers for Android TV.

Next, we added new restrictions on non-SDK interfaces and toggled many changes to help test opt-in changes that could affect your application. You can enable or disable each change separately in Developer Options or Android Debug Bridge. Finally, as in 2020, we will be notifying milestones regarding platform stability in advance so that developers can free up time to work on application compatibility. It notifies the final SDK and native API as well as the system behavior that supports internal APIs and applications. Related information can be found here .