Update: February 19, 2021 (04:53 PM ET): The first Android 12 developer preview is now available. We’ve updated this article to include a list of confirmed (and rumored) Android 12 features.
Android 12 has hit its first major milestone. Google has now released the first Android 12 developer preview to the public, giving us access to the initial build of the OS. With this initial build, users can now install the OS on compatible devices. We can also finally get a glimpse of the confirmed Android 12 features.
Google is improving and introducing a host of facets in its latest iteration of Android. Tweaks to media handling and notification support, improvements to privacy and haptic feedback, and more polished notifications UI all make the cut. We’re barely brushing the surface here. For a deeper dive detailing these confirmed Android 12 features and more, read on!
Confirmed Android 12 features
Easier Wi-Fi sharing
In stock Android 11, if you want to share your current Wi-Fi connection with someone, you can create a QR code easily. However, in Android 12, you can avoid the barcode scanning and just hit the “Nearby” button you see underneath the QR code in the image above. That will use Android’s Nearby Share feature to transmit the Wi-Fi credentials to whomever you like.
While scanning the QR code is pretty easy, this new feature allows you to share the connection info with multiple people without handing your phone around for everyone to scan. That’s definitely more convenient!
More screenshot markup options
With a Pixel device, if you capture a screenshot, you are easily able to markup that shot with paintbrush-like tools. With Android 12, though, you can add text, Emoji, and stickers to your screenshots using the same tool. This isn’t a revolutionary change, but it might prevent folks from needing a third-party app to do the same thing.
AVIF image support
The days of JPEG as the de facto compressed image format on mobile are numbered. Android 12 introduces support for AVIF — an image format that promises improved image quality over JPEG without the penalty of larger file sizes. The format makes use of the open-source video codec AV1, which was first introduced to Android 10.
Compatible media transcoding
Although HEVC is growing in popularity, the video compression standard isn’t supported by all apps. Now, Google is set to introduce a transcoding layer to Android 12 that will let unsupported apps also take advantage of video compression. Video capture apps that don’t support HEVC can now request Android 12 to transcode that file in AVC — a more available video compression format.
Read more: The best camera phones you can buy
Google notes that this is a stop-gap solution and urges developers to include HEVC support for their apps. The performance of this feature is also largely dependent on a device’s processing power. For instance, a one-minute 1080p video takes nine seconds to transcode on a Pixel 4, suggesting that it may not be suitable for budget devices. Still, the feature will be available for all Android 12 devices with video capture capabilities.
Haptic-coupled audio effect
Google is allowing developers to mate haptic feedback patterns with audio in Android 12. The strength and duration of vibrations are derived from audio cues, which adds a more immersive layer to media playback or alerts. “For example, a video calling app could use custom ringtones to identify the caller through haptic feedback, or you could simulate rough terrain in a racing game,” explains Google.
Enhanced cookie handling
Android 12 is bringing support for SameSite cookie behaviors to WebView. The SameSite attribute allows developers to declare if a cookie should be limited to a specific website. This addition should improve Android 12’s handling of cookies across the OS and various apps. Notably, major Android browsers already support the attribute.
Rich content insertion
Google is giving users more control over rich media through the keyboard, clipboard, and drag and drop. A new API will let users insert and move media from any of these sources. Supported formats will include “plain and styled text to markup, images, videos, audio files, and more,” per Google. For users, it should speed up the process of sharing files or styled text to others or across apps.
Android 12’s notification system will be redesigned to improve aesthetics, usability, and functionality. Google’s tweaking the drawer and controls and freshening up transitions and animations.
Responsiveness is also being targeted. Android 12 will prompt developers to ditch “trampolines” — middle-man broadcast receivers or services — that bounce users from the notification to the app. In Android 12, Google wants notification taps to take users directly to the app itself. The company’s also “delaying the display of some foreground service notifications by up to 10 seconds,” which will give short tasks a brief window to complete before pinging the user.
Android updates via Google Play
The Android Runtime (ART) will be added to Project Mainline — Google’s Play system updates program. This will let the firm push key updates to ART and other essential Android 12 services through Google Play, negating the need for full system updates to tweak these facets. Google also notes that more module updates will be pushed through Project Mainline in the near future, including its aforementioned transcoding improvements.
More confirmed Android 12 features
- Hide the selfie camera on Pixel 5: Spotted by Android Police, Google is now giving Pixel 5 users the option to hide the punch hole in Android 12. When the setting is enabled in the Developer menu, the selfie camera is hidden by a black bar. Notably, the status bar will also be displayed in this bar.
- Slightly redesigned Settings pages: The Settings panel has seen a slight redesign with a smaller search bar with rounded corners. Some toggles littered throughout look a bit different as well. It is now much easier to tell if a setting is on or off.
- Multi-channel audio: Android 12 is gaining support for MPEG-H in passthrough and offload modes, while audio mixers, resamplers, and effects can now support up to 24 channels.
- Easy audio source selection: The media player that appears in your Quick Settings section in Android 11 is now more customizable. By long-pressing the notification and heading into its specific settings, you can turn on or off the apps with which the player should work. This would allow you to turn off YouTube, for example, so it doesn’t appear in that player — but Spotify will.
- Foreground services: In Android 12, Google will block background apps from launching foreground services. Instead, a new expedited job in Android’s JobScheduler will allow developers elevated process priority for their apps.
- Restricted Netlink MAC: In Android 11, only privileged apps could access a device’s Netlink MAC address. Now, Google is restricting all apps from accessing it, regardless of privileges.
- Immersive mode tweaks: Gesture navigation within immersive mode will be “easier and more consistent” in Android 12.
- System variability performance improvements: Google’s improving Android 12’s latency and workload distribution, which should yield performance improvements to key system processes.
- Optimizations to larger display devices: Google’s finally taking tablets, foldable, and TVs more seriously. Android 12 developer preview will be available for Android TVs, too.
- Toggleable changes for debugging: Google’s making it easier for developers to debug their apps by making opt-in changes toggleable. These options will be available from the Developer settings page within Android or via ADB.
These are the confirmed Android 12 features as showcased by the first developer preview. Read on for a look at the rumored features heading to Android 12.
Rumored Android 12 features
Android 12 code-name
If you are wondering what the “sweet treat” name of Android 12 could be, we have an idea for that. However, do note that two years ago Google did away with officially naming Android versions after a sweet treat. It does continue to use treats as internal code names, though. This year, our best guess (with help from XDA-Developers) is that the codename could be “snow cone.” This would follow up the internal codename for Android 11, which was “red velvet cake,” and the internal codename for Android 10, which was “quince tart.”
Smarter app storage management
Sick of apps occupying storage but don’t necessarily want to uninstall them? App Hibernation could play a pivotal role in how Android 12 manages the footprint of these apps. The feature’s already included in the Android Open Source Project (AOSP). It will effectively allow the OS to clear an app’s cache if it’s labeled as “hibernating.”
It’s unclear what constitutes a hibernating app, however. We don’t know if that status is determined by the OS or the user. Additionally, we don’t know if the feature will sport other storage management tricks like compressing unused apps or clearing the system cache.
It won’t really be felt by those using phones with heaps of storage. However, it will likely be a huge addition to entry-level Android devices or older phones in line for the OS upgrade.
Manage two apps as a single task
Google hasn’t turned its back on fervent multitaskers in Android 12. Evidence suggests the company is working on a feature called App Pairs. It would allow users to manage two opened applications in Android’s Recents menu as a single task.
Its name is reminiscent of Samsung’s App Pair feature on One UI. It allows users to simultaneously open two apps onscreen via the Edge panel. Microsoft’s Surface Duo has a similar feature as well, which lets users open the app pair directly from a home screen shortcut. It’s unclear if Android’s native solution would include either of these abilities.
However, the feature would be a boon for larger phones, foldables, and tablets. It would simplify toggling between split-screen and full-screen apps in the Recents menu.
Restricted network mode
A revised networking management mode could arrive on Android 12. It would give the OS more control over which apps can access the internet.
According to XDA, the feature will take the form of a blocklist activated by a setting toggled in the OS. This toggle will likely be accessible by the user, but it’s unclear if the actual blocklist can be user-tweaked. Judging by commits merged to AOSP, the feature will only allow certain apps with the CONNECTIVITY_USE_RESTRICTED_NETWORK permission to utilize the network. All other apps will be barred from communication with the outside world.
Android 11 already features one-time location permissions on a per-app basis. A restricted networking mode would be a valuable addition to improving user privacy. We would love to see a more granular implementation should it arrive in time for Android 12, though.
Scrolling screenshot support
It’s been a long-running rumor even before Android 10 made its bow. Yet, Android 11 disappointed by not included scrolling screenshot support. Could this be one of Android 12’s baked-in features?
So far, it appears it could be a reality. According to XDA, the code to make this work is in Android 12. It’s just not turned on yet.
You can take scrolling screenshots in Android already via third-party apps, but default support would be a welcome addition.
Pixel double-tap actions
When Android 11’s Developer Preview arrived, it packed a nifty double-tap feature that could be enabled with some work on the user’s end. It let users of Pixel phones control hardware or launch apps with a double-tap of the back of the phone. While it wasn’t an essential control method, it was a useful way to access important features without touching the screen. Unfortunately, it never made it to Android 11’s stable build. Now, it’s possible that this feature may make a return in Android 12, as exposed by 9to5Google.
The feature, codenamed Columbus, will let users snag screenshots, open the notification shade, or launch Google Assistant. Google may also allow users to adjust the sensitivity of double-taps or disable them entirely if they’re not to their liking.
More expansive theming support
Android 11’s native customization options are pretty limited. Users can only switch between a light and dark mode in the UI. However, this could change according to a new report.
Spotted by 9to5Google, Android 12 may let users select from a swathe of primary and accent colors for custom OS themes. This won’t just affect the Quick Settings menu and other UI elements. It could affect apps that are built to support it, too. For those who can’t choose a color, the theming system is also said to adopt the primary colors of the system wallpaper, similar to Windows 10.
Android 12 UI tweaks
Enhanced theming support may not be the only major UI tweak coming to Android 12. Per this report, the new OS may wear an entirely new look compared to Android 11.
However, the first developer preview of Android 12 didn’t feature any of the elements in these screenshots. It’s possible that these will make it into the OS somewhere down the line. For now, though, Android 12 looks very much like Android 11.
In the leaks, the home screen itself resembles Android 11 in layout, but widgets and key icons seemingly take on the color gradients of the active wallpaper. In this case, icons and widgets wear tinges of brown, cream, and beige. This may be the first demonstration of Android 12’s rumored enhanced theming support.
XDA was able to capture screenshots of the new UI once again, this time without the heavy beige tone. In the screenshots, you can see a redesigned lockscreen, always-on display, quick settings panel, and more.
Improved privacy features
The screenshots also suggest Android 12 will take privacy and app access to critical sensors more seriously. A pill button in the top right of the status panel alerts users to which apps have access or are currently using the camera and microphone. Tapping it will also tell users if an app recently accessed these features.
Another screenshot suggests users will have access to a dedicated privacy page with easy access for managing app permissions and killswitches to the camera, microphone, and location. However, it’s not overtly clear how users can gain quick access to this page.
As phones get bigger, it gets more and more difficult to use them one-handed. Just try to reach your thumb to the top of your phone’s screen with only one hand, and you’ll see the problem. Over the years, OEMs have used apps and Android skin design to make it easier for one-handed use. Now, though, it’s possible a one-handed feature could land within Android 12.
According to XDA, Google is pushing the framework for a one-handed mode to AOSP. This would allow any OEM using AOSP to have access to this feature. However, it is unclear if Google will require OEMs to include this feature in Android 12 builds. As such, it’s possible this won’t make it to the stable launch of the OS.
9to5Google was able to get Android 12’s one-handed mode up and running, though it’s clear this isn’t a feature ready for prime time. It functions just like iOS’ Reachability: swipe down on the gesture navigation bar to bring all the contents of your screen down to a reachable level. When you want it to return to normal, you can tap outside of the shrunken screen or swipe up on the navigation bar.
Material Design “3.0”
In 2014, Google announced Material Design, a design language meant to unify all its products, including Android. Eventually, it launched an updated version of Material Design that developers colloquially referred to as Material Design 2.0 (even though Google never named it that officially). Now, according to documents obtained by XDA, it looks like a new iteration of Material is on the way.
In the leaked information, Google refers to this new Material as “Material NEXT.” That is probably not the official name for it either, but a significant change to the design language does line up with the leaked Android 12 mockup screenshots you saw earlier in this article.
Unfortunately, we only have inklings for what these changes could be. Whatever they are, they could have a large impact on the layout of Android, as previous Material updates have. Check out the full rumor roundup from XDA for more.
When you rotate your phone to landscape mode, it will often auto-rotate the contents of your display for you. This could be based on gyro sensors within the phone (depending on your settings). It could also happen through manual button presses or even through settings in particular apps.
As first seen by 9to5Google, though, a new method for auto-rotate sensing could land with Android 12 as an exclusive for Pixel phones. According to the leaked intel, this new feature would use the orientation of your face to determine whether landscape or portrait mode is more appropriate. Theoretically, this would happen through your phone’s front-facing camera and, for privacy reasons, happen on-device rather than in the cloud.
It’s unclear how this would be faster or more efficient than using gyro sensors. It’s also unclear if this would be an exclusive feature for Pixel phones. Stay tuned, as this will likely get more information as we get closer to the launch of Android 12.
Other rumored Android 12 features:
- One UI-esque Settings revamp: If you enable a hidden flag in Android 12 DP1 called “silky home,” the various Settings pages look wildly different. To be blunt, they look very much like Samsung’s designs within One UI. You can see what they look like at XDA‘s site.
Which rumored Android 12 features would you like to see make the cut? Let us know in the comments down below.