In this article, we’ll dive deep into Android 12L, the Android update that Google describes as the feature drop for tablets and foldables. Although the bulk of these changes apply to large screen devices, a few changes also apply to smartphones and other small screen devices.
Apart from handheld devices, cars running Android Automotive will see many benefits from upgrading to Android 12L. Google has not announced any Android 12L-specific changes to its other Android-based platforms, including Android TV, Google TV, and Wear OS. These platforms will instead gain new features from the Android 13 platform update.
To navigate this article, we recommend starting at the table of contents below to quickly skip to a part you want to learn more about. The ToC links to each section of the article, so you can quickly navigate without scrolling. On desktop, you can return to the ToC by clicking the link in the sidebar on the left. On mobile, you can return to the top of the page by tapping the arrow on the bottom right of the screen.
What is Android 12L?
Android tablets and Chromebooks have exploded in popularity over the past few years due to the COVID-19 pandemic boosting remote work and online education. Most of the new Android tablets and Chromebooks in circulation are on the lower end of the price spectrum. On the other end of that spectrum are foldables, devices whose displays can fold and unfold. To accommodate the growing number of these large screen devices, Google started on a multi-year project to improve Android for large screen devices. That’s why they made Android 12L.
Google announced Android 12L on October 27, 2021, mere weeks after the release of Android 12 to AOSP on October 4, 2021. The announcement of Android 12L took many by surprise as it’s not only the first “point update” since Android 8.1 but also the first major update aimed at Android tablets since Android 3.0 in 2011. But Android is on more than just tablets these days, which is why Android 12L also features changes that are applicable to other large screen devices like foldables and Chromebooks, small screen devices like smartphones, and other form factors like cars.
If you’re wondering why I called Android 12L a “point update,” it’s because it’s literally known internally as Android 12.1. Android 12L is just Google’s marketing name for it, with the “L” presumably standing for “large.” If you dig through AOSP, you’ll also see Google refer to Android 12L as Android Sv2 or Android SC-V2. This is because Android 12L is technically also the second Quarterly Platform Release (QPR) of Android 12, which was known internally as Android S(now Cone).
After a major OS version is released to AOSP, Google isn’t done developing it. The company pushes a QPR once a quarter for three quarters following the initial release of a major OS version. These QPRs are intended to fix any outstanding bugs that couldn’t be fixed in time or were discovered after the initial release. They may on occasion even add new (but minor) features. Android 12 QPR1, for instance, addressed nearly 100 issues in the initial Android 12 release and also added features like support for dynamic color boot animations. Android 12 QPR2 (AKA Android 12L) just happens to be a much more significant QPR than usual, because Google wanted to show that it was taking Android tablets and foldables seriously again (without waiting for Android 13 to show off their work).
(Google only releases three QPRs because a fourth one would coincide with the release of the next major OS version. After the next major OS version is released to AOSP, the cycle begins again.)
QPRs usually don’t add, change, or remove any APIs, nor do they typically affect any system behavior that might impact apps. Android 12L is special in that sense because it does do these things. That’s why Android 12L has a framework API level of 32 whereas Android 12’s was 31. Google bumps the API level whenever they make any changes that impact apps, because they want developers to be sure that whenever they build an app for a particular API level, the interfaces and behaviors they rely on won’t suddenly break.
Regardless of the API level bump, developers shouldn’t be too worried about their apps breaking on Android 12L, as Google states that it has “been careful not to introduce any breaking changes.” Even so, Google says it will not update Google Play’s target API level requirement to mandate targeting API level 32.
However, there are still several notable changes that app developers need to account for, especially if they plan to build applications that target tablets, foldables, or Chromebooks. Device makers that design or manufacture tablets or foldables should also look at what Google is building for Android 12L, even though there aren’t any changes to the Android compatibility requirements, as the update includes many UI changes and features that Google recommends be adopted or extended.
The final QPR of Android 12, AKA Android 12 QPR3, is a far more minor update than Android 12 QPR2 AKA Android 12L. It fixes a few bugs and adds some minor features like a toggle to show the vibrate icon in the status bar as well as a new “Battery” widget category in Launcher3. Android 12 QPR3 also has a framework API level of 32 since it’s built on top of Android 12 QPR2/12L, but Google doesn’t publicly refer to it as 12L. Most OEMs don’t distinguish between Android 12 and 12L either, so you’ll have to check manually if your device is running Android 12 or 12L.
What is the difference between Android 12 and 12L?
Truth be told, there aren’t many differences between Android 12 and Android 12L. I’ve tried to document as many differences as I could possibly find for this article, but most users and even most developers will struggle to tell the difference on a smartphone. The differences between Android 12 and 12L only become really apparent when using a tablet or another large screen device, as Android 12L adapts Material You design changes to larger screens, adds a taskbar, and enables embedding activities.
On smartphones, Android 12L brings minor features such as dynamic color support to the boot animation, new emojis, the ability to customize the press & hold duration for Assistant, and scrolling screenshots in WebViews. Android 12L also adds Google’s dynamic color engine ‘monet’, once a Pixel exclusive, as a standard feature, though many OEMs have backported the feature to their Android 12 builds, meaning the 12L update isn’t necessarily needed to use the feature.
Android 12L is a notable update for Android Automotive, the Android OS designed to run on car head units. Android Automotive 12L adds features like quick controls, device management support, and better flash memory management.
How do I know if I have Android 12L?
If you check Settings > About phone, the Android version will likely say “12” even if your device is running Android 12L. It’s not enough to simply check whether your device has a certain feature like dynamic color support, as features like these can be backported to Android 12. The only way to know for sure whether your device is running Android 12L is to check the API level/SDK version of the build.
If you’ve set up ADB, you can run the following command to get the API level/SDK version:
adb shell getprop ro.build.version.sdk
If this command returns ‘32’, then your device is running Android 12L. If it returns ‘31’, then your device is running Android 12.
You can also run this command in a terminal emulator app on the device if you exclude ‘adb shell’ from the command.
When was Android 12L released?
Google released Android 12L on March 7, 2022. On that day, Google published Android 12L’s source code to AOSP. Any company that builds AOSP — including ourselves — can incorporate all of the improvements 12L brings to large screen devices.
Android 12 QPR3 — which as previously mentioned is also based on Android 12L — was released on June 6, 2022. Its source code is also available in AOSP.
Device makers looking to test Android 12L can obtain signed, prebuilt Generic System Images (GSIs) straight from Google. These can be obtained for x86_64 or ARM64 targets with or without GMS. Compatibility Test Suite (CTS) packages for Android 12L are also available and will be released quarterly.
What devices run Android 12L?
Although there are many devices running Android 12, there are relatively few running Android 12L. Most devices running Android 12 won’t be updated to Android 12L, as OEMs will largely focus on migrating to Android 13. That being said, a couple of devices have been updated to Android 12L, a few are launching with it, and some are planned to get updates to it in the future.
All of Google’s Pixel phones from the Pixel 3a onward are running Android 12L, while newly launched devices with Qualcomm’s Snapdragon 8+ Gen 1 are shipping with Android 12L out of the box. Microsoft confirmed that it will bring Android 12L to the Surface Duo and Surface Duo 2. Samsung launched its Android 12L-based One UI 4.1.1 OS with its latest foldable smartphones, the Galaxy Z Fold4 and Galaxy Z Flip4. Lenovo is running a 12L beta program for its Tab P12 Pro.
As I previously mentioned, the only way to confirm if an Android device is running Android 12L is to check the API level/SDK version. Instead of manually checking every Android 12 device, though, you can refer to the Google Play Console’s device catalog to see which devices are running Android 12L. However, the Google Play Console only lists devices that are running GMS Android, so AOSP builds based on Android 12L, like the one used in the Windows Subsystem for Android, are not included.
What are the UI changes in Android 12L?
Material You for large screen devices
Material You is the third major version of Google’s Material design language, first introduced with Android 5.0 Lollipop in late 2014. Google’s updated design language embraces personalization, adaptive layouts, and accessible styles. Through a new theme engine that dynamically recolors parts of the system, Material You is personal. Through new APIs and user interface changes that make Android look better on tablets and foldables, Material You is adaptive. And finally, through a contextually aware system that customizes the text and size, Material You is accessible.
Material You, also referred to as Material Design 3 or Material Design “Next” in public documentation, made its product debut with Android 12. However, the personalization, adaptability, and accessibility improvements that Material You brought to Android 12 were designed with the smartphone form factor in mind. With the Android 12L release, Google is expanding its redesign efforts to cover large screen devices like tablets and foldables*. Devices with a screen width greater than 600dp have enough real estate to show two panes of content, which is the impetus behind the user interface changes in Android 12L.
Indeed, Android 12L adjusts the layout of multiple system interfaces to take advantage of the wider screens of tablets and foldables. The redesigned elements include the always on display (AOD), lock screen, home screen, notification shade, recent apps overview, power menu, settings, and several system applications.
*Although the term “foldables” typically refers to mobile devices with a foldable display, Google’s definition also covers dual-screen devices (where a hinge physically divides the screen). Thanks to Windows Central for pointing this out.
In Android 12, Google tweaked the lock screen layout to put the clock front and center when all notifications are cleared. By default, AOSP uses a digital clock style, which has been made substantially larger and separated into two rows (one for the hours and one for the minutes). The same is true for large screen devices running Android 12L, though there's an option to choose the clock layout.
To the top left of the clock is the smart space widget, for which a very basic implementation has been provided as part of AOSP. (A more feature complete implementation can be seen in Google’s Android 12 release for Pixel devices, though the “At a Glance” widget is proprietary to Google.) When there are visible notifications, the clock shifts to the left half of the screen to make room for the notifications column on the right. After 3 notifications are shown, any further notifications will be collapsed in an overflow card. (This configuration is controlled by the integer keyguard_max_notification_count in SystemUI.)
Additional buttons may be shown on screen depending on the user’s settings. First, if there are multiple profiles on the device, the user account switcher button will appear at the top right. Next, if the user has enabled “show wallet” and “show device controls” in lock screen settings, floating buttons to access the Quick Access Wallet and Device Controls modules will be shown on the bottom right and left, respectively. (In Android 12 and higher, the Wallet UI is part of SystemUI rather than being provided by a separate QuickAccessWallet application. The default package for handling Device Controls remains SystemUI. For more information on implementing Quick Access Wallet and/or Device Controls, please refer to Google’s documentation.)
If the user sets a PIN or pattern to unlock the keyguard, the entry UI will be shown on the left or right half of the screen depending on the side the user swiped from. If the user taps on either the left or right side, the PIN/pattern entry UI will then shift to that side of the screen. This behavior enables one-handed keyguard dismissal on large screen devices. The password entry UI remains centered, with the input method entering its full screen mode.
The lockscreen PIN/pattern can shift to the left or right side on Android 12L. Credits: Esper
Always on display
AOSP’s always on display (AOD) implementation does not feature substantial UI differences from the lock screen, as users expect to see a smooth transition between the AOD and lock screen. Like the lock screen, the AOD puts the clock right in the middle of the screen, and it takes up a substantial portion of the viewing area to make the time easy to view at a glance. Beneath the clock, in a much smaller font, is the current battery level. To reduce the number of pixels lit up on the screen on OLED panels, and visual clutter when viewing at a distance, notification previews remain hidden on the AOD in favor of icons.
On large screen devices, Launcher3 is capable of showing two home screen pages simultaneously. This is currently controlled by the Launcher3 flags ENABLE_TWO_PANEL_HOME and ENABLE_TWO_PANEL_HOME_IN_PORTRAIT, however, this feature does not work in current builds.
The launcher's widget picker now covers more of the screen when browsing through widgets for a particular application. It also now supports grouping widgets together into categories instead of just by package. In AOSP, the Conversation widget is placed under the Conversations category, for example. Meanwhile, Google’s Pixel Launcher fork places weather widgets under their own widget category in Android 12L; in QPR3, Pixel Launcher added a dedicated "Battery" section for the Android System Intelligence-provided Bluetooth accessory battery widget. Launcher developers can define their own custom categories to place widgets into by editing widget_sections.xml.
The app drawer ("AllApps") interface has added support for two-line labels in Android 12L. Currently, this feature is gated behind the "ENABLE_TWOLINE_ALLAPPS" feature flag.
Lastly, a new launcher flag called “ENABLE_BULK_ALL_APPS_ICON_LOADING” has been added. When enabled, the launcher loads all icons in the app drawer in a series of bulk SQL queries, reducing the cost of SQL lookups and thus improving the loading time.
In Android 12, and by extension Android 12L, Google significantly revamped the user interface of the notification panel. The brightness slider and Quick Settings tiles have been made substantially larger than before, leaving room for only 8 tiles to be displayed at a time in a 4x2 grid. (On large screen devices, Quick Settings is shown in a 3x3 grid when the device is in portrait orientation.) Text and background color clearly describe the purpose of the tile and its status, though the tile’s description is still shown in the notification panel’s “expanded” state. Expansion of the shade also reveals the build number and allows the user to swipe between pages of Quick Settings tiles.
Beneath the Quick Settings tiles is a row of up to 4 buttons: Edit, Profiles, Power Menu, and Settings. The Edit and Settings buttons perform the same actions as before, that is launch the Quick Settings edit flow and the Settings app respectively. Meanwhile, the Power Menu button launches the new compact power menu of Android 12+ in place of the full-screen power menu that integrated the Device Controls and Quick Access Wallet modules of Android 11.
Google has also introduced a new animation for expanding the notifications panel. The height of the Quick Settings tiles expand as the notification panel expands downward.
The new, more compact power menu of Android 12+ features up to 2 rows of buttons. The visibility of this new power menu, known internally as “PMLite”, is set to true by default in AOSP. The power menu is no longer shown by default when the user performs a long-press gesture on the device’s power button; rather, the component set as the default Assistant service is launched when the user long presses the power button. This behavior can be overridden, however. Device makers can also choose whether to surface the setting to change the long press on power button behavior.
Settings is one of the key system applications updated to support a two pane layout. This interface is enabled by default for large screen devices.
The left pane will always show the top-level Settings page, while the right pane will show any Settings subpages that the user opens. If the application supports it, Settings can also embed the Activity specified by the application.
Google made multiple UI changes to the recents overview in Android 12L to accommodate large screen devices. First, the preview card for the app currently in use is much larger. Second, the “split” button to launch the app in split-screen mode is now prominently displayed rather than tucked away behind the context menu that appears when long-pressing the app’s icon. Third, the preview cards for all the previously used apps have been made much smaller to fit within two rows. These UI changes make Android’s multitasking system more discoverable and make switching between recent tasks easier. Coupled with the new taskbar feature, it’s clear that multitasking is a key focus for Google in Android 12L.
Whenever two apps have been paired in split-screen mode, their icons are placed side by side in the recents overview. To create an app pair, simply launch both apps in split-screen mode. Tapping on an app pair in the recents overview will reopen both apps in split-screen mode.
One subtle UI change is the redesign of the "clear all" button that appears all the way at the end of the recents list. The button now has an opaque, pill-shaped background to make it stand out against the background.
An even subtler UX change in the recents overview is the addition of haptic feedback when scrolling through apps.
New AOSP wallpaper
AOSP includes a default wallpaper cropped to fit all supported display densities. This wallpaper typically isn’t changed every release, but with Android 12L, Google decided to change it. Thus, the Android 12L wallpaper is Android’s new default and will appear on all devices running AOSP.
Miscellaneous UI changes
- When exiting an app through the back gesture/button, the icon now gracefully animates towards its home screen location. In Android 12, this animation only occurred when exiting an app through the home gesture/button.
The new animation in Android 12L when exiting an app to the homescreen through a back swipe gesture/back button press. Credits: Esper
- The Internet panel and screen recorder panels now appear anchored at the center of the screen rather than at the bottom.
- When resizing windows in split-screen mode, Android will no longer show a live preview of the windows being resized. Rather, Android replaces the window contents with the app's icon centered on an opaque light or dark background.
- The multi-user switcher UI has been revamped. When tapping the user switcher button in the notifications panel, the multi-user switcher now opens in a centered pop-up window that floats above other system interfaces. The old UI comes from the days of Android 5.0 Lollipop, while the new UI is more in line with modern Android design. When tapping the user switcher on the lock screen, a semi-transparent dropdown menu lets you switch between users.
- Settings > Display > Colors now has additional sample photos to showcase how screen mode changes affect color reproduction.
- The screen cast Quick Setting tile now has a chevron indicating it opens a menu rather than acts as an on/off toggle.
- The default position of the slider in audio adjustment settings is now properly centered.
- The Internet panel now shows a "turn off airplane mode" button when the panel is expanded and airplane mode is enabled.
- A new 6x5 grid option for the Launcher.
- A new fingerprint unlock animation.
These UI changes, while beneficial for large screen consumer hardware, may not be appropriate for enterprise or fleet devices. Because Esper builds Android from source, we can customize, extend, or strip many of these changes. Contact us if you have any requests.
What are the new features in Android 12L?
A staple of desktop operating systems, the taskbar finally makes an appearance in AOSP with Android 12L. Android’s taskbar, like the aforementioned UI changes, only appears on devices with a screen above 600dp. The taskbar is built into Launcher3 and is integrated with the application dock at the bottom of the home screen.
The user’s selection of applications will appear on the taskbar at the bottom of the screen in every application. Google chose an opaque gray color for the taskbar’s background to visually distinguish it from the application window. When the user returns to the home screen, the taskbar’s background becomes transparent to show the wallpaper. The taskbar will automatically minimize when viewing a full-screen application or entering the launcher’s app tray, but it can also be minimized by long-pressing on any part of the taskbar.
A demo of the taskbar in Android 12L. Credits: Esper
The taskbar in Android 12L is rather simple in current builds. Users can tap on an app to quickly switch to it, or they can long-press and drag an app’s icon to either half of the screen to quickly launch that app in split-screen mode.
The taskbar currently does not support showing recently launched applications, more than 6 applications at a time (unless apps are placed in a folder), or a context menu when long pressing an app. The feature flag "ENABLE_TASKBAR_POPUP_MENU" enables long pressing the taskbar icons to show the context menu, but it is currently disabled by default.
The taskbar also does not integrate any elements currently found in the status bar, such as the date and time, but it does integrate the 3-button navigation keys which are shown on the right edge.
If you wish to test split-screen mode behavior in Android 12L, you can use the new Window Manager shell commands accessed through:
dumpsys activity service SystemUIService WMShell <command>
Here is the documentation for this CLI:
Window Manager Shell commands:
Print this help text.
Dump Window Manager Shell internal state
Pairs/unpairs tasks with given ids.
Move a task with given id in split-screen mode.
Remove a task with given id in split-screen mode.
Sets the position of the side-stage.
Notification to window
In addition to the taskbar, Google is testing another method in Android 12L to quickly launch an app in split-screen mode. Called notification to window, the feature allows a user to start an app’s PendingIntent (ie. an Activity from a notification) through a notification drag-and-drop gesture. The user can launch an app Activity to a pop-up or split-screen window by long-pressing on a heads-up notification or a notification in the notifications panel and then dragging it to the left or right side of the screen.
A demo of the ‘notification to window’ feature. Credits: Esper
This feature is not currently enabled by default in Android 12L, but it can be by setting the SystemUI configuration value config_notificationToContents to true. With superuser access, this value can be quickly set to true by creating an overlay through the Fabricated Overlay API or CLI. For example:
cmd overlay fabricate --target com.android.systemui --name NotificationToContents android:bool/config_notificationToContents 0x12 0x01
The generated overlay can then be enabled by running:
cmd overlay enable com.android.shell:NotificationToContents
Note that this feature does not work properly without additional patches; oftentimes, a long press of a heads-up notification will expand to show that notification’s settings rather than pop out as intended. This gesture will likely be optimized in future preview releases.
Dynamic colors in AOSP
Although Google markets its dynamic coloring theme engine as a marquee feature of Android 12, the company did not provide a fully open-source implementation of its theme engine with the AOSP Android 12 source code release. However, that has changed with AOSP Android 12L, as not only is the theme engine fully open source, but it is enabled by default in AOSP builds. (This feature is controlled by a SystemUI configuration value called flag_monet.)
Material You’s wallpaper-based theming engine, code-named “monet,” generates a rich pastel color palette from the user’s wallpaper. A color extraction engine employing a clustering algorithm with Material color targets determines the dominant and less dominant colors of the user’s wallpaper. A palette generation algorithm then creates a rich palette of 5 colors — 2 neutral and 3 accent colors — and 12 shades of Material color that are used to determine the hues closest to the user’s wallpaper. Finally, these color values are stored in an index that apps can call through an API. (For more information on dynamic color, visit Google’s Material Design 3 documentation.)
With the Android 12L source code release, monet’s palette generation algorithm has been included. The core color extraction algorithm, color appearance model (CAM), and a post-processing/filtering algorithm were already included in the current AOSP Android 12 release, thus many device makers are already moving forward with implementing dynamic colors using their own palette generation algorithm.
For developers looking to test dynamic colors, Android’s “paint chips” widget, which can be added after viewing Android 12’s Easter egg, offers a quick glance at every color generated by the dynamic coloring system.
AOSP does not provide a user affordance to opt out of palette generation once “monet” is enabled, thus every wallpaper change will trigger a change in colors*. This has the added side effect of recreating the activities of every application, akin to a normal configuration change. However, AOSP does not provide a new configuration change type to account for this, so third-party applications cannot opt out of having their activities be destroyed and recreated, as pointed out by CommonsWare. Repeated background wallpaper changes can thus be abused to create a denial-of-service attack, as pointed out by XDA-Developers. Fortunately, this issue has been resolved in Android 12L as theme changes are no longer permitted to occur when an app changes the wallpaper while in the background.
01-18 19:11:04.847 2793 2793 I ThemeOverlayController: Wallpaper changed from background app, keep deferring color events. Accepting: true
*Although Android does not allow the end-user to opt-out of theme changes when the wallpaper updates, Esper can disable ‘monet’ at the platform level if your business decides it needs to remotely update the wallpaper from our Console.
Dynamic colors in boot animation
Android 12L enables support for dynamic color boot animations, a feature that has since been backported to the first Android 12 Quarterly Platform Release (QPR1). As boot animations are traditionally a sequence of static PNG images, dynamic color is applied to them in a rather clever way. Rather than directly rendering the PNG images contained within the boot animation file, the new dynamic coloring render mode treats the R, G, B, and A channels of each image as area masks, interpolating between the start and end colors based on the progression of the animation.
Device makers can enable dynamic colors for the boot animation by adding the following line as the second line to desc.txt:
dynamic_colors PATH #RGBHEX0 #RGBHEX1 #RGBHEX2 #RGBHEX3
where PATH is the file path of the part to apply the dynamic color transition to, RGBHEX0 is the first start color masked by the R channel, RGBHEX1 is the second start color masked by the G channel, RGBHEX2 is the third start color masked by the B channel, and RGBHEX4 is the fourth start color masked by the A channel.
The end colors, meanwhile, are read from the following four system properties: persist.bootanim.color1, persist.bootanim.color2, persist.bootanim.color3, and persist.bootanim.color4.
Device makers should prepare their PNG images so that the R, G, B, A channels indicate the areas to draw color1, color2, color3 and color4 respectively.
Sample video demonstrating the boot animation using dynamic colors. Credits: Esper
The bootanimation-dark.zip file in Android 12L for Pixel devices contains an implementation of this feature. More sample videos can be viewed here.
Press & hold duration for the long-press power button gesture
If the device maker chooses to surface the setting to change the long press on power button gesture, then the user will have the ability to adjust the gesture’s sensitivity in Android 12L. A new “press & hold duration” slider has been added to the “Press and hold power button” settings page, which lets the user “adjust [the] sensitivity [of the gesture] by choosing how long to press & hold the power button.” The slider ranges from “short” (250ms) to “long” (750ms), with three intermediary values (350, 500, or 650ms). AOSP defaults to a duration of 500ms for triggering this gesture. This feature was backported to Android 12 QPR1.
Esper can customize the behavior of the power button to meet your needs, whether that’s to disable the assistant invocation, hide the power menu, or do something else.
Quick wallpaper picker
Launcher3’s Developer Options added a new feature flag called “QUICK_WALLPAPER_PICKER.” Its description reads: “Shows quick wallpaper picker in long-press menu.” When enabled on AOSP, the feature does not seem to function, as the implementation is missing from Launcher3 and WallpaperPicker. In Google builds of Android 12L, however, support for the feature is present, and it is enabled by default.
Google’s implementation stores the 5 most recent wallpapers in an array of JSON objects, with the wallpaper’s id, collectionId, thumbnail uri, component, and color. When the user opens the context menu by long-pressing anywhere on the home screen, a carousel containing the thumbnails of these 5 wallpapers is shown at the top.
Google Emoji 14.0
In September, the Unicode Consortium released version 14.0.0 of the Unicode Standard. The updated standard brings 37 new emoji characters. As part of the Android 12L release, Google has updated its Noto Emoji fonts to include the new Emoji 14.0 characters. For a thorough look at the new emoji in Google’s Emoji 14.0 library, we recommend reading Emojipedia’s changelog.
App developers should be aware that as of February 2, 2022, Google Play requires apps running on Android 12 or later to support the latest Unicode Emoji library within 4 months of its release, as pointed out by Android Police. Developers have a few options to remain compliant with this policy update: Enable emoji if AppCompat is in use, use an existing EmojiCompat library across all surfaces within the app, or update the handling and font/images for emoji based on the latest Unicode version. You can read more about Google Play’s upcoming policy changes here, and more specifically about the new Android Emoji policy here.
Merging the home screen and app drawer search boxes
A feature flag called "ENABLE_ONE_SEARCH" was added to the developer options of Launcher3 during Android 12L's development, but it was removed before launch. When this flag was enabled, tapping the Google search box on the home screen would launch the new, much faster on-device search interface introduced in Android 12 for the app drawer. This feature can be seen in action in this video. Note that the search provider is handled by a proprietary Google app and is not a part of AOSP, which is also the case for the Google search box.
Quickly launch an app in split screen mode from its PiP window
When an app is put into picture-in-picture mode, Android 12L can show a split screen button in the PiP window whenever another app is open. Tapping this button will launch both apps in split screen mode as an app pair.
This button is not shown by default. To enable it, the SystemUI flag config_pipEnableEnterSplitButton must be set to true.
Opportunistic switching between 5G and 4G network stacks
For devices that don’t support simultaneous 5G connections on both SIMs, operators can use Android 12L’s new opportunistic switching capability. One new configuration lets operators decide how long to wait before the opportunistic 4G network stack goes out of service before switching to the primary 5G network stack. Another configuration lets operators control how long to wait to scan after switching back to the primary 5G network stack. The idea is to minimize the ping-ponging effect of the device constantly switching back and forth between the primary and opportunistic stacks.
Voice over 5G
A new carrier configuration lets operators show a VoNR (Voice over New Radio) toggle in settings. This is intended for devices that support routing voice calls over 5G. The toggle’s visibility defaults to true.
Toggle to show vibrate icon in status bar
In previous versions of Android, the OS shows an icon in the status bar when the sound mode is set to either “vibrate” or “silent.” However, this was changed in Android 12, as the OS no longer showed an icon when the device was set to “vibrate.” Following Android 12’s release, users petitioned Google to bring the icon back, and the company obliged by adding a toggle in Android 12 QPR3.
Tucked away under Settings > Sound & vibration is a toggle called “always show icon when in vibrate mode.” When enabled, an icon will be shown in the status bar when the device is set to vibrate.
- Android 12L removes code related to “Content Push”, which placed a button labeled “Push” in the recents overview. This button, when pressed, would have likely started mirroring that app to a connected PC. While this button has been scrapped, Google’s app mirroring plans live on.
- Another feature that has been removed from Launcher3 in Android 12L is proactive chips in the recents overview. For a brief period, Google used this feature to surface Google Lens-powered translation hints in the recents overview.
- The screen recorder built into SystemUI no longer shows the “show touches on screen” option. Google says this option was removed “because the touch points currently cannot be recorded due to changes in how the cursor is drawn.”
What are the behavioral changes in Android 12L?
Broader support for multi-window mode
According to Google’s documentation, Android 12 and later releases make multi-window mode standard behavior.
On larger screens (≥ 600dp), Android will force all applications to be resizable regardless of the value they set for the android:resizeableActivity attribute. However, if this attribute is set to false, then the platform will launch the app in screen compatibility mode to conform to display dimensions. Compatibility mode has been around since the early days of Android, but it has been significantly improved in Android 12L.
On smaller screens (< 600dp), Android will check an activity’s minWidth and minHeight to determine if it can run in multi-window mode, assuming that the android:resizeableActivity attribute is set to true. If it’s false, then Android will not allow the app to run in multi-window mode.
Device makers can override these behaviors by changing the values of config_supportsNonResizableMultiWindow and config_respectsActivityMinWidthHeightMultiWindow respectively. These values both default to ‘0’ in AOSP. Developers can override these behaviors at runtime through the ‘wm’ shell command, or by toggling the “force activities to be resizable” and “enable non-resizable in multi window” features in developer options.
Here are the new multi-window shell commands accessed through ‘wm’:
Sets options to determine if activity should be shown in multi window:
Whether the device supports non-resizable activity in multi window.
-1: The device doesn't support non-resizable in multi window.
0: The device supports non-resizable in multi window only if
this is a large screen device.
1: The device always supports non-resizable in multi window.
Whether the device checks the activity min width/height to determine
if it can be shown in multi window.
-1: The device ignores the activity min width/height when determining
if it can be shown in multi window.
0: If this is a small screen, the device compares the activity min
width/height with the min multi window modes dimensions
the device supports to determine if the activity can be shown in
1: The device always compare the activity min width/height with the
min multi window dimensions the device supports to determine if
the activity can be shown in multi window.
Prints values of the multi window config options.
Resets overrides to default values of the multi window config options.
Developers are encouraged to build responsive layouts for their apps that adapt to large screen devices. For those apps that have not yet been optimized, such as those that maintain a fixed size or orientation, Android 12L’s screen compatibility mode can letterbox the app and tweak the window frame to provide the best experience on large screens. Apps will be letterboxed if their minimum or maximum aspect ratio is incompatible with the aspect ratio of the display.
Android supports the following UI enhancements to letterboxing:
- Android 12
- App windows can be configured to have rounded corners
- Status bars can be configured to be semitransparent
- An app’s aspect ratio can be configured
- The background type can be configured
- Android 12L
- The default horizontal position of an app window center can be configured
- The restart button UI can be configured
Device makers are responsible for configuring the letterboxing effects, which can be done by overlaying the values config_fixedOrientationLetterboxAspectRatio, config_letterboxActivityCornersRadius, config_letterboxBackgroundType, config_letterboxBackgroundColor, config_letterboxBackgroundWallpaperBlurRadius, config_letterboxBackgroundWallaperDarkScrimAlpha, config_letterboxHorizontalPositionMultiplier, and config_letterboxDefaultPositionMultiplierForReachability in the framework. By default, AOSP positions the letterboxed app in the center, does not apply rounded corners to letterboxed app windows, and uses the color #ff76757f for the background (an opaque dark gray).
On Android 12L, device makers and app developers can override these behaviors at runtime through the new ‘wm set-letterbox-style’ command.
Here are the new letterboxing shell commands accessed through ‘wm’:
Sets letterbox style using the following options:
Aspect ratio of letterbox for fixed orientation. If aspectRatio <= 1.0
both it and R.dimen.config_fixedOrientationLetterboxAspectRatio will
be ignored and framework implementation will determine aspect ratio.
Corners radius for activities in the letterbox mode. If radius < 0,
both it and R.integer.config_letterboxActivityCornersRadius will be
ignored and corners of the activity won't be rounded.
Type of background used in the letterbox mode.
Color of letterbox which is be used when letterbox background type
is 'solid-color'. Use (set)get-letterbox-style to check and control
letterbox background type. See Color#parseColor for allowed color
formats (#RRGGBB and some colors by name, e.g. magenta or olive).
Color resource name of letterbox background which is used when
background type is 'solid-color'. Use (set)get-letterbox-style to
check and control background type. Parameter is a color resource
name, for example, @android:color/system_accent2_50.
Blur radius for 'wallpaper' letterbox background. If radius <= 0
both it and R.dimen.config_letterboxBackgroundWallpaperBlurRadius
are ignored and 0 is used.
Alpha of a black translucent scrim shown over 'wallpaper'
letterbox background. If alpha < 0 or >= 1 both it and
R.dimen.config_letterboxBackgroundWallaperDarkScrimAlpha are ignored
and 0.0 (transparent) is used instead.
Horizontal position of app window center. If multiplier < 0 or > 1,
both it and R.dimen.config_letterboxHorizontalPositionMultiplier
are ignored and central position (0.5) is used.
Whether reachability repositioning is allowed for letterboxed
fullscreen apps in landscape device orientation.
Default horizontal position of app window when reachability is.
Resets overrides to default values for specified properties separated
by space, e.g. 'reset-letterbox-style aspectRatio cornerRadius'.
If no arguments provided, all values will be reset.
Prints letterbox style configuration.
Letterboxing can provide the best experience possible without needing to update an app, but it should not be used as a crutch. If your hardware has an uncommon aspect ratio and the app you want to run cannot be updated, consider tweaking the letterboxing effects to display the app in the best light.
New scaling method for media projection
Google is improving the screen casting experience in Android 12L. When an app uses the media projection API to project the real device’s display onto a virtual display, the system will scale the virtual display to maximize the size of the image on the application-provided Surface while maintaining the proper aspect ratio, in a process similar to ImageView’s centerInside scale type.
Device makers can override an app’s preferred orientation
Through the screenOrientation Manifest attribute, app developers can specify the orientation that their applications should run in, regardless of the orientation of the device. This lets developers present their app in a fixed aspect ratio, but it results in usability issues on foldable devices that can be oriented based on their fold.
In Android 12 and above, device makers can configure individual device screens to ignore the screenOrientation attribute, overriding an app’s request for a preferred orientation.
This behavior can be controlled at runtime through the ‘wm’ shell command:
fixed-to-user-rotation [-d DISPLAY_ID] [enabled|disabled|default]
Print or set rotating display for app requested orientation.
set-ignore-orientation-request [-d DISPLAY_ID] [true|1|false|0]
get-ignore-orientation-request [-d DISPLAY_ID]
If app requested orientation should be ignored.
Re-enable volume adjustment for remote media sessions
Casting audio to an external device is a common feature of many media player apps, and for user convenience, most media players also support remote volume adjustment. After configuring a media session to use remote volume handling through MediaSessionCompat.setPlaybackToRemote(VolumeProviderCompat volumeProvider), apps can receive volume key events. However, this was not the case in the initial release of Android 12, as the platform no longer passed the volume key event to remote sessions.
Fortunately, in early January, Google released android-12.0.0_r26 with a patch that tweaked the volume adjustment behavior to re-enable volume adjustment for ungrouped remote media sessions. Esper analyzed this patch to explain how Google tweaked Android's media framework in response to its patent dispute with Sonos. This new volume adjustment behavior is now present in Android 12L.
Thus, in Android 12L, the platform supports sending the volume key event to remote media sessions regardless of how many routes are in the session. On Pixel devices, however, the volume key event cannot be passed to remote media sessions contained speaker groups as the framework configuration value 'config_volumeAdjustmentForRemoteGroupSessions' is overridden to false.
Developer option to toggle monitoring of phantom processes
Android 12 quietly introduced a new mechanism to monitor forked child processes started by apps and kill them off if they consume too much CPU while their parent process is in the background. Android also limits how many child processes can be spawned in total across the system (32), which has proven to be a headache for advanced users of terminal emulator applications.
Fortunately for power users, Google has added a toggle in developer options to disable the monitoring of these so-called "phantom processes". The toggle is available under the "feature flags" page of Developer Options which is only populated if the build type is userdebug or eng. Users can override the flag by running the following shell command:
settings put global settings_enable_monitor_phantom_procs [false|true]
Scrolling screenshot support for WebViews
Android 12 introduced scrolling screenshots so users can take full page screenshots. AOSP’s scrolling screenshot implementation follows a different approach than most third-party implementations, which usually automatically scroll the page and take multiple screenshots to stitch together. Instead, AOSP’s works directly on Views, making it faster and more reliable. However, this approach also makes it less versatile, because it may not work out of the box with apps that use a non-View-based UI or a heavily customized UI. It also doesn’t work on WebViews, which are views that display web content.
Late last year, Google Chrome added support for Android 12’s ScrollCapture API which is how apps can give the scroll capture system information on the view to be captured. However, this only made scrolling screenshots work in browsers based on Chromium but not in WebViews. Android 12L, however, enables scroll capture support for WebViews, letting users take full page screenshots of any content embedded in a WebView.
Backing up and restoring home screen layouts across form factors
In order to accommodate foldable devices, Launcher3 now supports backing up and restoring the home screen layout. This means that the user can set up two different home screen layouts, one for when the device is folded and one for when it’s unfolded, and easily swap between the two without having to recreate the layout each time.
Bubbles are now hidden when entering focus mode
Bubbles that are created before an app is suspended (eg. via Digital Wellbeing’s “Focus Mode”) are now hidden in Android 12L.
What are the new APIs in Android 12L?
As a feature update, Android 12L does not include many new APIs. There are, however, a few notable additions to the platform, which we’ll summarize in this section.
Activity embedding for two-pane browsing
Activity embedding is one of the key ways that apps can take advantage of the larger screens of tablets, foldables, and Chromebooks. As its name suggests, activity embedding enables showing multiple activities at once, usually side by side. The app task window is split into two containers (primary and secondary) that hold activities launched from the main activity or from other activities already in the containers. Activities in the secondary container are stacked as they’re launched. Note that only system and pre-installed apps holding the permission android.permission.LAUNCH_TWO_PANE_SETTINGS_DEEP_LINK can show their activity in the secondary container of the Settings app.
As the feature handles device orientation and foldable state changes seamlessly, it will be useful for providing an enhanced user experience on large screen devices. Support for activity embedding is baked into Android 12L, but Google says that it will be available on some devices running earlier versions of Android. App developers can check whether activity embedding is supported on a device by calling SplitController.isSplitSupported() method.
Rather than calling the new platform API directly, Google has added support for activity embedding in the latest Jetpack WindowManager release. Version 1.0.0-beta03 includes experimental support for activity embedding. The initial release allows for showing two activities side by side, though only the activity that created the split can occupy the primary container, while the secondary container can contain a stack of activities.
For more information, including how back navigation is handled, how to build a multi-pane layout, how to proportion the task window, how to configure split rules, and what the current limitations are, read Google’s documentation on activity embedding.
Audio spatialization with dynamic head tracking
Spatial audio is a feature that has existed for years, but thanks to new consumer hardware from the likes of Sony, Apple, and Oculus, it has never been more popular. The feature creates the effect of 3D audio, “[simulating] sounds originating around the listener as if they were coming from virtual speakers placed around the listener,” as explained by Google in its documentation for the new Spatializer API in Android 12L.
The new Spatializer API lets developers query the capabilities and behavior of sound spatialization on the device. Google says that support for audio spatialization is optional, and if supported, the AudioManager#getSpatializer() method will return a handle to the platform’s Spatializer instance. Developers can also query whether the device supports multichannel spatialization, whether audio of a particular AudioFormat can be spatialized, and more.
The following shell command reveals the spatial audio capabilities of the device:
dumpsys audio | grep -A 4 Spatial
The system property ro.audio.spatializer_enabled should be set to true if the device ships with a spatializer effect. Settings.Secure.SPATIAL_AUDIO_ENABLED and Settings.Secure.SPATIAL_AUDIO_ENABLED_DEFAULT hold the current state of the feature.
While the developer documentation doesn't mention it, AOSP code commits reveal that Android 12L includes head tracking support for spatial audio. Dynamic head tracking is a feature that’s available on the latest iPhone and iPad when paired to Apple’s latest audio accessories. Head tracking builds upon spatial audio by tracking the position of the user’s head to virtually reposition the sound channels accordingly, providing an even more immersive audio experience. Head tracking is handled by the headphones worn by the user; the accelerometer and gyroscope within the paired accessory determine the position of the user’s head, while additional data from the mobile device determines the position relative to the screen. Like iOS, Android 12L appears to include support for full screen-to-head tracking. There are three head tracking modes: static (ie. no head tracking), world relative (no screen tracking), and screen relative (full screen-to-head tracking).
Another aspect that's undocumented is the supported spatialization modes. In Android 12L, there will be two supported modes: binaural and transaural. The former means that the spatializer supports producing spatial audio over headphones, while the latter means that it supports it over the loudspeaker.
Accessibility actions for drag-and-drop
Android’s Accessibility API lets developers build services that help users with accessibility needs. Users who find it difficult to interact with a touchscreen may be unable to perform certain gestures, such as a drag-and-drop. In Android 12L, a drag-and-drop gesture is used to launch an app in split-screen mode from the taskbar. To accommodate those users who may have trouble performing this gesture, which is also used to share data between apps in split-screen view, the Accessibility API has added the following three actions: ACTION_DRAG_DROP, ACTION_DRAG_START, and ACTION_DRAG_CANCEL.
Android’s shared “external” storage contains media files, some application data, and other files that are readable by other applications or the user. Before Android 10, applications could gain broad read/write access to the external storage through the READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE runtime permissions. With the introduction of Scoped Storage in Android 10 (API level 29), however, Google began to restrict access to external storage. As a consequence, two widely used external storage APIs — Environment.getExternalStorageDirectory() and Environment.getExternalStoragePublicDirectory() — were deprecated. The former returned the primary external storage root directory, while the latter returned the public external storage directory for saving files of a particular type. With API level 32, Google has decided to undeprecate these two APIs. The reason is that while Android 10 did not support file path operations for apps restricted by Scoped Storage, Android 11 largely restored read access to external storage.
As noted by CommonsWare, however, this does not change storage access rights. Scoped Storage rules still apply, which means that apps cannot read or write to content created by other apps in public directories unless given proper permissions.
Another API that has been undeprecated is the DATA constant in MediaStore.MediaColumns. This field was also deprecated with API level 29 when Scoped Storage was first implemented.
More contextual assistant with VoiceInteractionSession updates
Android, through the VoiceInteractionSession API, lets virtual assistant applications receive data from the application that the user is currently viewing when the assistant was invoked. That information can come in the form of a screenshot of what the user is currently viewing, which can then be analyzed via OCR. The Assistant can even request a list of supported actions from within an app. Google’s own Assistant app utilizes this API to obtain contextual information about the app the user is viewing, and in Android 12L, the API is getting even more powerful.
VoiceInteractionSession has added two new callbacks: registerVisibleActivityCallback and unregisterVisibleActivityCallback. The former will let the assistant app register a callback to be notified when there’s a change in the visible activity, while the latter simply unregisters the callback. This will enable more powerful uses of the assistant service, as the service can track what activities are opened within an app. This lets the assistant listen to changes in the visible activity, providing actionable context on what the user is actually doing within an app. The “new” Google Assistant, a faster version of the Google Assistant that’s exclusive to select Pixel devices, will likely make use of this new capability, according to the commit description adding these callbacks.
Hidden DevicePolicyManager APIs to end the current user session
Two hidden methods have been added to DevicePolicyManager: getLogoutUserId() and clearLogoutUser(). Android Automotive’s SystemUI will use these methods to end the current user session.
Drop input events on SurfaceControl
Android 12L has added a new setDropInputMode API under SurfaceControl. This API can be used to drop input events on SurfaceControl and its children. According to the commit description, this API is used to “enable features that allow for a less trusted interaction model between apps.”
What's new in Android Automotive 12L?
The new features in Android Automotive 12L are summarized in the official release notes page. However, when cross-referencing that page with the one for Android Automotive 12, it’s revealed that many of the changes listed for 12L were first introduced in 12. Therefore, this section will not mention any of the changes listed on both pages. However, there are a few features introduced with Android Automotive 12L that aren’t listed on either page, which this section will include.
According to Google, The AudioControl HAL for Android Automotive has been migrated from HIDL to AIDL. Google has been migrating HALs from HIDL to AIDL for quite some time now, as they plan to define all new HALs introduced in Android 13 and later in AIDL.
Android Automotive 12L also enables power handling functionality for the car audio service. This includes disable and enable focus requests as well as mute and unmute volume groups on power policy changes for audio.
Automotive App Host
Unlike on other Android platforms, third-party apps on Android Automotive (and Android Auto) don’t render their UI natively. Instead, third-party apps use well-defined UI templates that are optimized for usability and safety in vehicles; these UI templates are provided by a system app called the App Host which renders the UI of third-party apps on their behalf.
Alongside the release of Android Automotive 12L, Google released the AOSP Automotive App Host. By open sourcing the Automotive App Host, Google is enabling OEMs to style UI templates and components to fulfill their needs. In addition, since the AOSP Automotive App Host is part of the Car App Library used by third-party app developers to create apps for Android Automotive (and Android Auto), third-party apps can visually integrate with the rest of the UI on both Android Automotive with GAS (Google Automotive Services) and AOSP Android Automotive builds.
Google explains on this page how car infotainment developers can generate and integrate the AOSP Automotive App Host. One of the permissions the AOSP Automotive App Host is required to hold is android.car.permission.TEMPLATE_RENDERER, which Google warns is only available after API level 32 (ie. Android 12L). This permission “allows an application to render template-based UI metadata on behalf of another application” according to its description in AOSP, and it can only be held by system apps given it has a protection level of “signature|privileged.”
Android Automotive 12L is the first version of AAOS that supports enterprise device management. However, the only enterprise management solution supported by Android Automotive is a fully managed device as work profiles aren’t supported. Previous versions of Android Automotive did not support enterprise device management as the requisite feature (android.software.device_admin) was not declared on AAOS builds. This, however, changes with Android Automotive 12L, as the android.software.device_admin feature is declared by default on new Automotive builds.
By declaring the android.software.device_admin feature, Android’s Device Management APIs are enabled, allowing device policy controller (DPC) apps to control local device policies and system applications on Automotive devices. The DPC API is commonly used by Mobile Device Management (MDM) solutions to manage Android devices, typically smartphones and tablets. However, for the automotive use case, DPC apps must consider the drive-state of the car, as certain actions will be unavailable while the car is being driven (for safety).
Although Android Automotive doesn’t support work profiles, it does have multi-user support, hence there may be multiple profiles on the device. As such, Android Automotive provides support for managing multiple users. However, because Automotive builds are typically set up with a headless system user as the default user, DPC apps will be set as the device owner (DO) of the system user and the profile owner (PO) of every other user. This means remote admins should consider which DPC to use based on whether the action is associated to the device or user. They may also need to affiliate all PO users in order to use certain APIs.
At Esper, we support enterprise device management of fully managed devices through our in-house DPC app. Get in touch with us at Esper.io if you’re interested in managing Android Automotive devices, whether it’s a fleet of rental or company cars.
Android Automotive also supports personal device management through a handful of new device management APIs that are integrated with drive-state restrictions. These APIs can be called by any system app with the right permissions and include the following:
- CarDevicePolicyManager.createUser() - Creates a new user on the device in the background, regardless of drive-state.
- CarDevicePolicyManager.RemoveUser() - Removes an existing user on the device, but only if the target user is in the background or the car is parked or idling.
- DevicePolicyManager.lockNow() - Locks an existing user on the device. If the user has existing lock screen credentials, the display stays on. This applies regardless of the state of the target user or drive-state.
- DevicePolicyManager.resetPassword() - Locks an existing user on the device by setting a lock screen credential, if the user didn’t already set one. The display stays on. This operation fails if the car is moving.
- DevicePolicyManager.wipeData() - Triggers a factory reset. A notification will appear informing the driver that a factory reset is required. When the car is parked, the driver can choose to reset the device immediately or later (when the car is next started).
Android Automotive 12L adds a separate location toggle to control device location access for the preloaded advanced driver-assistance system (ADAS) app. An ADAS app exchanges info between the in-vehicle map database, ADAS features and functionality, and other automated driving features outside Android. In previous versions of Android Automotive, toggling location access would impact the ability of an ADAS to perform its core functionality. In Android Automotive 12L, however, users can turn off general location access for apps while allowing an ADAS app to retain location access.
However, Google has strict requirements about which ADAS apps can bypass the general location switch. Only apps that meet these strict requirements can be added to Android Automotive’s location bypass allowlist.
Since consumers expect to keep a car for far longer than they keep a mobile device, Android Automotive includes measures to limit wear on the flash storage, thereby prolonging its lifespan. Android Automotive 12L includes a new car watchdog service for flash memory management, which “manages system flash memory by limiting the amount of data written to storage.” OEMs can define the write thresholds for OEM, media, and maps packages and collect statistics for OEM apps. The watchdog will disable and terminate non-critical apps and service that exceed defined thresholds.
The updated SystemUI in Android Automotive 12L brings improvements and bug fixes to rotary controllers, a visual overhaul to notifications, improvements to grouped notifications, Quick Controls, and UI plugin support.
Quick Controls is a feature that lets OEMs add select settings (eg. Bluetooth toggles) to SystemUI elements like the status bar. This way, users have quick access to key settings while they’re driving, so they don’t have to open the Settings app.
Car UI Plugins are a more powerful alternative to RROs for customizing SystemUI components, as they aren’t limited to changing XML resources like RROs are. A Car UI Plugin is an APK with classes implementing a set of Plugin APIs located in packages/apps/Car/libs/car-ui-lib/oem-apis in AOSP, and they can be compiled into a plugin as a static library. To learn more about developing Car UI Plugins, visit this page.
What security vulnerabilities does Android 12L fix?
Every new Android release contains fixes to the OS framework patching security vulnerabilities, and Android 12L is no exception. The list of CVEs addressed by Android 12L, which has a default security patch level of 2022-03-01 as released to AOSP, can be found on the Android 12L Security Release Notes page. Note that, where applicable, security patch backports are available for any currently supported, older version of Android also affected by a vulnerability.
At Esper, we support Android on a variety of form factors, including large screen devices like tablets and POS terminals. Although the release of Android 12L is several months away, we’re diligently monitoring the update to see which large screen UI changes to pick, what behavior changes we need to account for, and what features we’ll support. Android is a constantly evolving operating system, so it’s easy to fall behind given the rapid pace of development. Let Esper manage the software that runs on your device fleet; we care about the nitty-gritty implementation details so you don’t have to.