Here's what's new in Android 13 Developer Preview 1
(thread)
There are Quick Setting tiles for toggling one-handed mode and color correction
A Quick Setting tile to launch a QR code scanner is here. It's grayed out by default, but you can enable it w/
'cmd device_config put systemui default_qr_code_scanner {component}'
where {component} is the component of a QR code scanner activity (can be anything really)
The taskbar on large screen devices can now show up to 6 icons compared to 5 on 12L.
The media output picker UI has been redesigned. The volume slider for each connected device is larger and prettier.
It seems Themed App Icons aren't yet enabled in DP1. I added a monochromatic icon to a test app and <monochrome android:drawable="@drawable/ic_test_mono" /> in ic_launcher.xml, but the icon isn't themed.
The Launcher3 feature flag/boolean pref are likely not set to true yet.
This build is quite old, by the way. If it seems like there aren't many new features in Android 13, it's because the Developer Preview 1 build is way behind the current internal code.
New foreground service manager w/ a Quick Setting tile. Tapping it opens a dialog that shows the currently running apps.
This is disabled by default in 13 DP1.
When creating a guest user, you can choose which apps to install to that profile.
The Android Resource Economy (TARE) has been added to Developer Options. TARE manages how apps queue tasks by delegating "credits" to apps that they can "spend" on queuing tasks.
Seems runtime permissions for notifications is here, even if Google didn't announce it. The new android.permission.POST_NOTIFICATIONS permission has a protection level of 'dangerous'. It's pre-granted to certain apps and will only be enforced on apps targeting the new API level.
Under Settings > System > Gestures > System navigation, a new submenu has been added for the 3-button navigation that lets you disable "hold Home to invoke assistant".
Privacy dashboard is testing a new "show 7 days" mode that lets you see which apps have accessed "dangerous"/runtime permissions in the last 7 days as opposed to the last 24 hours. This is not enabled by default.
Android 13 adds a smart idle maintenance service, which intelligently determines when to trigger filesystem defragmentation without hurting the lifetime of the UFS storage chip.
Going to publish my deep dive now on @Esperdev with all the surface-level stuff I've found. Will continue to dig around to see what Google added but hasn't enabled.
Setting your phone to silent will also disable all haptics - even ones for gesture nav. Already heard a few complaints about this change.
The split screen button in PiP windows is here, but I suspect that's because this build was built before the code change that disabled this feature by default was merged. So it's possible it'll be disabled by default in future previews, and only enabled on large screen devices.
For some reason, per-app language preferences - one of the features Google announced in the Android 13 DP1 blog post - isn't enabled by default. However, it is there.
Android 12L Beta 3 introduced the 6x5 app grid size for large screen devices, but it seems that in Android 13, this is the *only* grid size available on large screen devices.
AppSearch experimental flags has added "Google Suggest" as an option. Haven't investigated what it's supposed to do yet.
Android 13 has a hidden "clipboard auto clear" feature. This feature clears the primary clipboard item after a set amount of time. Yes, Gboard does this, but this feature works with all input methods. You can learn more about it here: blog.esper.io/android-13-dee…
This is disabled by default, but Android 13 can show the user profile switcher on the lock screen keyguard (ie. the place where you enter your PIN/password/pattern). Probably intended for large screen devices.
The UI demo for the Media Tap To Transfer feature reported by @AndroidPolice is present in Android 13 DP1. However, there are still few hints about how it'll actually work.
Last post for tonight. Google is testing a redesign of the media player UI. It doesn't seem finished yet as there's no album art, but it hints at what's coming.
Thanks to @kdrag0n for his help w/ this and the previous feature!
I have a couple of more things I found that I plan to talk about tomorrow, so keep an eye out on this thread + the @Esperdev blog!
I'm back with more! Today, I've added two new sections to my deep dive that cover the BIG changes that Google is preparing to make to the tablet experience in Android 13.
The first one is hub mode, also called communal mode. This feature is intended to let users share apps between profiles on a common surface, which could be a revamped screen saver (!)
The second one is, as I've just alluded to, a screen saver revamp. Google is preparing to introduce "complications" (think watches/Wear OS) to screen savers. Couple this w/ the dock-related changes, and it's clear that hub tablets are getting some love!
Yes, it's true: Google is introducing Material You dynamic color styles that adjust the hue and chroma values when monet generates the 5 MY tonal palettes.
Surprise! Google hasn't even released Android 12L yet, but they're already moving on to Android 13. Today, Google released the first Developer Preview of Android 13, available for manual installation on Pixel (Pixel 4 or later), Android Emulator, or GSI.
Based on the release timeline that Google shared, there will be 2 Developer Previews and 4 Betas before the final release (likely in Q3). Platform Stability (finalized APIs/behaviors) will be reached in June 2022 with the third beta.
Since Android 12L or Sv2 is being released alongside framework API level 32, Android 13 should be released alongside framework API level 33. The dessert name for Android 13, as you may have heard already, is Tiramisu (TM).
Google has announced that Material You dynamic color will soon be available on more Android 12 phones globally, including on devices from OEMs like Samsung, Xiaomi, OPPO, OnePlus, and more.
Google is working with OEMs to ensure that design APIs, especially around dynamic color, work consistently across devices so developers won't have to worry about different implementations.
This announcement is consistent with the recent revelation that Google will tie GMS approval of Android 12+ software builds to implementation of a dynamic theming engine.
The Material You revolution won't be televised: According to an article from @AndroidPolice, GMS requirements will soon force device makers to implement a Material You dynamic theming engine such as Google's own "monet."
Apparently, starting March 14, 2022, Google will require that Android 12-based software builds submitted for GMS approval implement a dynamic theming engine that generates the five dynamic color tonal palettes - each comprised of a set of 13 colors - from a single source color.
Google's "monet" was exclusive to Pixels when Android 12 launched, but the source code for it is in the upcoming 12L release, so OEMs can either rebase on 12L or cherry pick the patches for monet to their 12 builds.