The Chrome team continues evaluating how they'll implement support for the Android Photo Picker. Recently they added a flag that controls what Picker is launched:
1) ACTION_GET_CONTENT intent
2) ACTION_PICK_IMAGES intent
3) ACTION_PICK_IMAGES "Plus" intent
4) Chrome Picker
(H/T @LanceAdams for pointing out the flag!)
—-
1) GET_CONTENT is currently handled by DocumentsUI (the system file picker). Google is experimenting with having the new Android Photo Picker "take over" handling of the GET_CONTENT intent. This briefly rolled out in December but was reverted.
2) ACTION_PICK_IMAGES intent is the standard way to invoke the framework Photo Picker on Android 11+ (though Chrome stills seems to require Android 13?). Through GMS, Photo Picker is also backported to Android 4.4+
3) ACTION_PICK_IMAGES "Plus" is interesting. The MIME type is set to
I personally think this would be useful; give users the option to open the more feature-rich DocumentsUI, no matter how the Photo Picker is invoked, while still defaulting to the prettier Photo Picker for image/video selection.
4) Chrome Picker, this just launches the old in-app media picker, which means you have to grant Chrome gallery access permissions.
1) ACTION_GET_CONTENT intent
2) ACTION_PICK_IMAGES intent
3) ACTION_PICK_IMAGES "Plus" intent
4) Chrome Picker
(H/T @LanceAdams for pointing out the flag!)
—-
1) GET_CONTENT is currently handled by DocumentsUI (the system file picker). Google is experimenting with having the new Android Photo Picker "take over" handling of the GET_CONTENT intent. This briefly rolled out in December but was reverted.
2) ACTION_PICK_IMAGES intent is the standard way to invoke the framework Photo Picker on Android 11+ (though Chrome stills seems to require Android 13?). Through GMS, Photo Picker is also backported to Android 4.4+
3) ACTION_PICK_IMAGES "Plus" is interesting. The MIME type is set to
*/* (ie. all) which Photo Picker does not handle and instead forwards to DocumentsUI. It seems the Chrome team wants the Photo Picker team to add a way to force the Photo Picker to show the "browse" button in the overflow menu; currently this "browse" button only appears when the Photo Picker is invoked through the GET_CONTENT takeover, and tapping it opens the system file picker/DocumentsUI.I personally think this would be useful; give users the option to open the more feature-rich DocumentsUI, no matter how the Photo Picker is invoked, while still defaulting to the prettier Photo Picker for image/video selection.
4) Chrome Picker, this just launches the old in-app media picker, which means you have to grant Chrome gallery access permissions.
❤18👍1
A couple of more Android 14 (DP2) findings in this thread 👇:
1) A new EXECUTE_APP_ACTION permission that "allows an assistive application to perform actions on behalf of users inside of applications." This permission is granted to the default Assistant. Currently, I don't see any APIs that require this permission.
2) A new LAUNCH_CAPTURE_CONTENT_ACTIVITY_FOR_NOTE permission that "allows an application to capture screen content to perform a screenshot using the intent action." This is intended for the app that holds the ROLE_NOTES role.
ROLE_NOTES is a new role in Android 14. It can only be granted to apps that target SDK 34 and that handle the android.intent.action.CREATE_NOTE intent. The role itself is disabled unless config_enableDefaultNotes = true, and the default holder is defined by config_defaultNotes.
(In case you're wondering, Google Keep doesn't currently qualify to be the holder of ROLE_NOTES.)
Attached is the settings page for setting the "default notes app".
Apps with the permission can use the ACTION_LAUNCH_CAPTURE_CONTENT_ACTIVITY_FOR_NOTE intent action to trigger SystemUI to get a screenshot of the current window on behalf of the app. The user then has a chance to edit the screenshot, which can then be returned to the notes app.
3) Companion Device sync: In Android 13, Google laid the groundwork for syncing certain data when setting up a companion device (like a smartwatch or earbuds) through an app that uses the CompanionDeviceManager API. They added preliminary support for syncing permissions.
I've never seen it in action yet, but what they added was the ability to automatically grant certain permissions to apps you approve the transfer of from your phone to your watch, provided you already granted those permissions on your phone.
Now in Android 14, there's a more generic "system data sync" feature. Right now, it "only supports call metadata sync", which isn't that useful since this is something you already see done (usually through NotificationListeners).
1) A new EXECUTE_APP_ACTION permission that "allows an assistive application to perform actions on behalf of users inside of applications." This permission is granted to the default Assistant. Currently, I don't see any APIs that require this permission.
2) A new LAUNCH_CAPTURE_CONTENT_ACTIVITY_FOR_NOTE permission that "allows an application to capture screen content to perform a screenshot using the intent action." This is intended for the app that holds the ROLE_NOTES role.
ROLE_NOTES is a new role in Android 14. It can only be granted to apps that target SDK 34 and that handle the android.intent.action.CREATE_NOTE intent. The role itself is disabled unless config_enableDefaultNotes = true, and the default holder is defined by config_defaultNotes.
(In case you're wondering, Google Keep doesn't currently qualify to be the holder of ROLE_NOTES.)
Attached is the settings page for setting the "default notes app".
Apps with the permission can use the ACTION_LAUNCH_CAPTURE_CONTENT_ACTIVITY_FOR_NOTE intent action to trigger SystemUI to get a screenshot of the current window on behalf of the app. The user then has a chance to edit the screenshot, which can then be returned to the notes app.
3) Companion Device sync: In Android 13, Google laid the groundwork for syncing certain data when setting up a companion device (like a smartwatch or earbuds) through an app that uses the CompanionDeviceManager API. They added preliminary support for syncing permissions.
I've never seen it in action yet, but what they added was the ability to automatically grant certain permissions to apps you approve the transfer of from your phone to your watch, provided you already granted those permissions on your phone.
Now in Android 14, there's a more generic "system data sync" feature. Right now, it "only supports call metadata sync", which isn't that useful since this is something you already see done (usually through NotificationListeners).
👍18
Google is finally rolling out the "app streaming" feature they first announced at CES 2022!
This won't be a Pixel-exclusive feature, either, though the update today is only available for Pixels. If you have a Pixel, check for an update to the "Cross-Device Services" app on Google Play. The "Cross-Device Services" app has been a stub APK for a while now, but an update brings it to version 1.0.285.1.
(This can't be installed over the app by the same name on OEM devices, though, because it's signed with a different certificate. At least, that's the case with my Zenfone 9.)
After downloading the update on my Pixel 6a and setting up Phone Hub on my Chromebook, I personally don't have the ability to stream apps. However, one user reports that it's working on their Pixel 7 and Chromebook, and that it works with any apps! (This is also reflected in the Play Store listing screenshots).
Full list of devices that are currently expected to support app streaming:
* Pixels
* ASUS Zenfone 9
* Nothing Phone 1
* OPPO A78 5G
* OPPO Find N2 Flip
* Redmi A2
* Redmi Note 12
* Xiaomi 12T
* Xiaomi 12T Pro
Want to know how this feature works and why it requires Android 13? This thread from January goes into detail?
This won't be a Pixel-exclusive feature, either, though the update today is only available for Pixels. If you have a Pixel, check for an update to the "Cross-Device Services" app on Google Play. The "Cross-Device Services" app has been a stub APK for a while now, but an update brings it to version 1.0.285.1.
(This can't be installed over the app by the same name on OEM devices, though, because it's signed with a different certificate. At least, that's the case with my Zenfone 9.)
After downloading the update on my Pixel 6a and setting up Phone Hub on my Chromebook, I personally don't have the ability to stream apps. However, one user reports that it's working on their Pixel 7 and Chromebook, and that it works with any apps! (This is also reflected in the Play Store listing screenshots).
Full list of devices that are currently expected to support app streaming:
* Pixels
* ASUS Zenfone 9
* Nothing Phone 1
* OPPO A78 5G
* OPPO Find N2 Flip
* Redmi A2
* Redmi Note 12
* Xiaomi 12T
* Xiaomi 12T Pro
Want to know how this feature works and why it requires Android 13? This thread from January goes into detail?
❤27👍6🔥4
Mishaal's Android News Feed
Google is finally rolling out the "app streaming" feature they first announced at CES 2022! This won't be a Pixel-exclusive feature, either, though the update today is only available for Pixels. If you have a Pixel, check for an update to the "Cross-Device…
Here are screenshots of the setup process:
Also, the Cross-Device Services update is rolling out now on my ZenFone 9 as well. So today's rollout may not be limited to Pixels after all!
EDIT:
Okay, so how do you know if the feature is *actually* available for you?
- You must update Cross-Device Services to version 1.0.285.1 from Google Play first. The update is only available on Pixels and the select Android devices I mentioned earlier.
- Your device/account must be opted-in to the feature; this part seems to be server-side controlled by Google. I don't know how Google's rolling this out.
- Open your Chromebook settings > Connected devices > tap your Android device to open Phone Hub settings. (If you haven't already set up Phone Hub, first do that.)
- If you see "Apps (Beta)" in the list and a "set up" button, then the feature is available for you. Tap "set up" and you'll see a pop-up on your phone to grant access.
- Once you've done that, you can open Phone Hub on your Chromebook to see your recently opened apps. Click any of them to launch it in a window on your Chromebook.
Also, the Cross-Device Services update is rolling out now on my ZenFone 9 as well. So today's rollout may not be limited to Pixels after all!
EDIT:
Okay, so how do you know if the feature is *actually* available for you?
- You must update Cross-Device Services to version 1.0.285.1 from Google Play first. The update is only available on Pixels and the select Android devices I mentioned earlier.
- Your device/account must be opted-in to the feature; this part seems to be server-side controlled by Google. I don't know how Google's rolling this out.
- Open your Chromebook settings > Connected devices > tap your Android device to open Phone Hub settings. (If you haven't already set up Phone Hub, first do that.)
- If you see "Apps (Beta)" in the list and a "set up" button, then the feature is available for you. Tap "set up" and you'll see a pop-up on your phone to grant access.
- Once you've done that, you can open Phone Hub on your Chromebook to see your recently opened apps. Click any of them to launch it in a window on your Chromebook.
🔥25👍5❤2
I wrote this tweet from a Chromebook that has Twitter for Android streamed to it from a Pixel 6 Pro running Android 13!
Manually enabled the new "app streaming" feature. There was a bug preventing it from working on Android 14 DP2, so I downgraded one of my Pixels to Android 13 and then got it to work 😁
The grid of icons in the "Recent apps" section is actually a shortcut to open an app drawer! That means you aren't only limited to picking from the 5 most recent apps to launch.
Audio is also streamed from your phone to your Chromebook, meaning you can watch videos (or maybe even play some games?) - surprisingly little latency, too!
You can *technically* launch multiple apps onto the virtual display if you have "force desktop mode" and "enable freeform windows" enabled in developer options, but it's not a good idea, obviously.
You can also launch apps directly onto the virtual display, with an app like Taskbar by Braden Farmer that uses the APIs to do so, or through the 'am' shell command (append --display <DISPLAY_ID>).
And thanks to the VirtualAudioDevice API in Android 13, the app streaming feature can inject audio from a remote source (in this case, the mic on my Chromebook) into an app running on the virtual display! This means your phone doesn't have to be next to you to send voice messages.
Manually enabled the new "app streaming" feature. There was a bug preventing it from working on Android 14 DP2, so I downgraded one of my Pixels to Android 13 and then got it to work 😁
The grid of icons in the "Recent apps" section is actually a shortcut to open an app drawer! That means you aren't only limited to picking from the 5 most recent apps to launch.
Audio is also streamed from your phone to your Chromebook, meaning you can watch videos (or maybe even play some games?) - surprisingly little latency, too!
You can *technically* launch multiple apps onto the virtual display if you have "force desktop mode" and "enable freeform windows" enabled in developer options, but it's not a good idea, obviously.
You can also launch apps directly onto the virtual display, with an app like Taskbar by Braden Farmer that uses the APIs to do so, or through the 'am' shell command (append --display <DISPLAY_ID>).
And thanks to the VirtualAudioDevice API in Android 13, the app streaming feature can inject audio from a remote source (in this case, the mic on my Chromebook) into an app running on the virtual display! This means your phone doesn't have to be next to you to send voice messages.
❤29👍9🔥5
Mishaal's Android News Feed
I wrote this tweet from a Chromebook that has Twitter for Android streamed to it from a Pixel 6 Pro running Android 13! Manually enabled the new "app streaming" feature. There was a bug preventing it from working on Android 14 DP2, so I downgraded one of…
Although Google Play currently lets you install Cross-Device Services onto any Android 13 device, the Android-to-Chromebook app streaming feature will NOT work for you unless you the app was already preinstalled in the OS by the OEM.
For example, I could install Cross-Device Services onto my Zenfone 8 running Android 13. It installs fine, but it will never work for one reason: It can't get the permissions it needs!
Problem 1: Priv-app permissions. Cross-Device Services requests several permissions that can only be granted to privileged apps (located in a priv-app directory) through Android's privileged permission allowlisting mechanism. This must be done at build time by the OEM.
Problem 2: COMPANION_DEVICE_APP_STREAMING role. Some of the other important permissions the app needs (like the ability to create a virtual display!) are granted when the app becomes the COMPANION_DEVICE_APP_STREAMING role holder.
This role can only be given to system apps, however. The pop-up that you see when you're setting up app streaming is you making the Cross-Device Services app the role holder.
So how can OEMs bring app streaming to their devices?
1) Include Google's Cross-Device Services stub in their build and implement the priv-app permission allowlist.
2) Declare the "com.google.ambient.streaming" feature.
3) ????
4) Profit!
In all seriousness, Google has only rolled out the app streaming feature to a very small number of people, not including me. I myself had to manually enable it to show it off earlier.
So even if you have one of the devices I mentioned before, you may not have this feature because you need to enable a few flags on the Chrome OS AND Android side. If/when Google announces this, they'll flip those flags for you server-side.
For example, I could install Cross-Device Services onto my Zenfone 8 running Android 13. It installs fine, but it will never work for one reason: It can't get the permissions it needs!
Problem 1: Priv-app permissions. Cross-Device Services requests several permissions that can only be granted to privileged apps (located in a priv-app directory) through Android's privileged permission allowlisting mechanism. This must be done at build time by the OEM.
Problem 2: COMPANION_DEVICE_APP_STREAMING role. Some of the other important permissions the app needs (like the ability to create a virtual display!) are granted when the app becomes the COMPANION_DEVICE_APP_STREAMING role holder.
This role can only be given to system apps, however. The pop-up that you see when you're setting up app streaming is you making the Cross-Device Services app the role holder.
So how can OEMs bring app streaming to their devices?
1) Include Google's Cross-Device Services stub in their build and implement the priv-app permission allowlist.
2) Declare the "com.google.ambient.streaming" feature.
3) ????
4) Profit!
In all seriousness, Google has only rolled out the app streaming feature to a very small number of people, not including me. I myself had to manually enable it to show it off earlier.
So even if you have one of the devices I mentioned before, you may not have this feature because you need to enable a few flags on the Chrome OS AND Android side. If/when Google announces this, they'll flip those flags for you server-side.
👍14❤1
Magisk v26.0 has been announced🎉
(According to topjohnwu, there are some last minute fixes being implemented, so the build is not live yet!)
It's live!
Big thanks to topjohnwu, vvb2060, yujincheng08, and others for continuing to maintain this excellent tool!
Here's the full changelog:
v26.0
* [General] Bump minimum supported Android version to Android 6.0
* [General] New magic mount backend. It supports loading modules into system with overlayfs files injected
* [Zygisk] Release new API version 4
* [Zygisk] Prevent crashing daemon in error
* [Zygisk] Rewrite zygote code injection with new loader library approach
* [Zygisk] Rewrite code unloading implementation
* [MagiskBoot] Support amonet microloader devices
* [MagiskBoot] Always use lz4_legacy compression on v4 boot images. This fixes boot image patching issues on Android U preview.
* [MagiskInit] Support replacing existing *.rc files in overlay.d
* [MagiskInit] Rewrite sepolicy.rules mounting and loading implementation
* [App] Make stub patching 100% offline
* [App] Support patching init_boot.img for Samsung ODIN firmware
* [MagiskPolicy] Fix minor bug in command line argument parsing
* [MagiskPolicy] Update rules to support Android U
Big thanks to topjohnwu, vvb2060, yujincheng08, and others for continuing to maintain this excellent tool!
Here's the full changelog:
v26.0
* [General] Bump minimum supported Android version to Android 6.0
* [General] New magic mount backend. It supports loading modules into system with overlayfs files injected
* [Zygisk] Release new API version 4
* [Zygisk] Prevent crashing daemon in error
* [Zygisk] Rewrite zygote code injection with new loader library approach
* [Zygisk] Rewrite code unloading implementation
* [MagiskBoot] Support amonet microloader devices
* [MagiskBoot] Always use lz4_legacy compression on v4 boot images. This fixes boot image patching issues on Android U preview.
* [MagiskInit] Support replacing existing *.rc files in overlay.d
* [MagiskInit] Rewrite sepolicy.rules mounting and loading implementation
* [App] Make stub patching 100% offline
* [App] Support patching init_boot.img for Samsung ODIN firmware
* [MagiskPolicy] Fix minor bug in command line argument parsing
* [MagiskPolicy] Update rules to support Android U
🥰21👍9❤2🎉2😁1
This media is not supported in your browser
VIEW IN TELEGRAM
Google Play has just announced a new data deletion policy that I welcome 🎉
If your Android app allows users to create an account, then Google Play will eventually require you to offer a way for users to initiate account AND data deletion from within the app and from the web.
Google Play will require that the web link for account/data deletion be provided to users through your app's Data Safety section, as shown in the GIF above. This is so users can request deletion WITHOUT reinstalling your app.
When completing the Data Safety form, there'll be new questions related to this data deletion policy. Google's asking developers to submit answers by December 7, 2023. Sometime in early 2024, users will see the new data deletion badge and area in apps' store listings.
Developers that need more time to comply with this requirement (such as needing to build out account/data deletion tools) can file an extension in the Play Console until May 31, 2024. After that date non-compliant apps may be removed from Google Play.
For more info on this new policy, read Google's blog post and support page.
If your Android app allows users to create an account, then Google Play will eventually require you to offer a way for users to initiate account AND data deletion from within the app and from the web.
Google Play will require that the web link for account/data deletion be provided to users through your app's Data Safety section, as shown in the GIF above. This is so users can request deletion WITHOUT reinstalling your app.
When completing the Data Safety form, there'll be new questions related to this data deletion policy. Google's asking developers to submit answers by December 7, 2023. Sometime in early 2024, users will see the new data deletion badge and area in apps' store listings.
Developers that need more time to comply with this requirement (such as needing to build out account/data deletion tools) can file an extension in the Play Console until May 31, 2024. After that date non-compliant apps may be removed from Google Play.
For more info on this new policy, read Google's blog post and support page.
👍25🔥8❤2👏2
Mishaal's Android News Feed
A couple of more Android 14 (DP2) findings in this thread 👇: 1) A new EXECUTE_APP_ACTION permission that "allows an assistive application to perform actions on behalf of users inside of applications." This permission is granted to the default Assistant. Currently…
Let's continue this thread, shall we?
4) Bluetooth Audio Routing
"Choose whether different types of audio are played on your hearing device or phone speaker"
If you have a hearing aid connected to an Android 14 device, you'll be able to choose where certain sounds (ringtone, call, media, system sounds) will play from by default ("decide automatically", "play on hearing device", or "play on phone speaker").
5) Dual screen:
When an app is using both displays to show content, you'll get a notification that "dual screen is on." When the device gets too warm, you'll be warned that "Dual Screen is unavailable because your phone is getting too warm."
6) SYSTEM_CALL_STREAMING:
Android 14 adds a new SYSTEM_CALL_STREAMING role that only system apps targeting SDK 34 and which have a CALL_STREAMING_SERVICE implemented can hold. This role grants the permissions CALL_AUDIO_INTERCEPTION and RECORD_AUDIO, which can be used to grant access to APIs to stream phone call audio between Android devices.
Following Android 14 DP1's release, Google published documentation for the CallControl and StreamingCall APIs. The latter was removed as presumably it's only intended to be internal.
What I suspect this'll be used for is to stream voice call audio from an Android phone to an Android tablet. Imagine you get a call on your Pixel, but you're near your Pixel Tablet. Tap the output switcher and select the tablet to begin streaming the phone call to your tablet!
There is some evidence behind this, by the way. Back in the Android 12L DP, there was an app that suggested a "Nearby calling" feature was in the works that would let you transfer calls between your phone and Nest Hub.
And in Android 13, Google added some new cross-device calling APIs (the CALL_AUDIO_INTERCEPTION permission was also added in Android 13).
4) Bluetooth Audio Routing
"Choose whether different types of audio are played on your hearing device or phone speaker"
If you have a hearing aid connected to an Android 14 device, you'll be able to choose where certain sounds (ringtone, call, media, system sounds) will play from by default ("decide automatically", "play on hearing device", or "play on phone speaker").
5) Dual screen:
When an app is using both displays to show content, you'll get a notification that "dual screen is on." When the device gets too warm, you'll be warned that "Dual Screen is unavailable because your phone is getting too warm."
6) SYSTEM_CALL_STREAMING:
Android 14 adds a new SYSTEM_CALL_STREAMING role that only system apps targeting SDK 34 and which have a CALL_STREAMING_SERVICE implemented can hold. This role grants the permissions CALL_AUDIO_INTERCEPTION and RECORD_AUDIO, which can be used to grant access to APIs to stream phone call audio between Android devices.
Following Android 14 DP1's release, Google published documentation for the CallControl and StreamingCall APIs. The latter was removed as presumably it's only intended to be internal.
What I suspect this'll be used for is to stream voice call audio from an Android phone to an Android tablet. Imagine you get a call on your Pixel, but you're near your Pixel Tablet. Tap the output switcher and select the tablet to begin streaming the phone call to your tablet!
There is some evidence behind this, by the way. Back in the Android 12L DP, there was an app that suggested a "Nearby calling" feature was in the works that would let you transfer calls between your phone and Nest Hub.
And in Android 13, Google added some new cross-device calling APIs (the CALL_AUDIO_INTERCEPTION permission was also added in Android 13).
👍32❤1👏1
Google Chrome is experimenting with Android 14's new ChooserActions API to display custom actions at the top of Android's share sheet.
This is an important step for Chrome to ditch its custom share sheet on Android, and hopefully other apps follow suit!
Chrome currently uses its own custom share sheet to display these actions (copy link, send to your devices, QR code, print), but Google is trying to move developers away from using custom share sheets.
A new Chrome flag (chrome://flags#share-sheet-migration-android) toggles whether to use the app's custom share sheet or the OS one. When the flag is enabled on Dev or Canary builds on Android 14 devices, the ChooserAction API will be used to display these app actions in the OS share sheet.
Alongside the new row for app-defined actions (powered by the ChooserActions API), Android 14 brings a couple of other improvements to the share sheet experience. You can track the progress of Chrome's share sheet changes here.
This is an important step for Chrome to ditch its custom share sheet on Android, and hopefully other apps follow suit!
Chrome currently uses its own custom share sheet to display these actions (copy link, send to your devices, QR code, print), but Google is trying to move developers away from using custom share sheets.
A new Chrome flag (chrome://flags#share-sheet-migration-android) toggles whether to use the app's custom share sheet or the OS one. When the flag is enabled on Dev or Canary builds on Android 14 devices, the ChooserAction API will be used to display these app actions in the OS share sheet.
Alongside the new row for app-defined actions (powered by the ChooserActions API), Android 14 brings a couple of other improvements to the share sheet experience. You can track the progress of Chrome's share sheet changes here.
👍36👏4❤1🔥1
Mishaal's Android News Feed
In Android 14, Android's dynamic color engine ("monet") seems to be adding better support for users who enable "high contrast" to improve visibility! Apps should look good for everyone, including those who rely on Android's accessibility features! In Android…
Turns out we don't have to wait and see, because contrast level controls are already in Android 14 DP2!
A new "contrast level" slider is buried under Settings > Accessibility > Color and motion. It currently only supports "Standard", medium, and "High" values. This slider controls the value of Settings.Secure.contrast_level (0 for "Standard", 0.5 for the mid setting, and 1.0 for "High") which in turn can be read by apps calling AccessibilityManager's new getUiContrast() method.
SystemUI's ThemeOverlayController class calls that method to read the color contrast value and generate the "dynamic" color scheme accordingly, which is then mapped to the R.color values I mentioned before through the "dynamic" FRRO.
I dumped the values of the "dynamic" FRRO generated based on the AOSP wallpaper and contrast_level values of 0, 0.5, and 1.0. It's evident that as the contrast increases, the tone (lightness) of foreground colors becomes further from the tone of background colors.
Google's official explanation of the dynamic scheme (H/T @kdrag0n):
How this ends up looking in apps depends on how devs choose which tokens to color which UI elements, but in general, devs adhering to Material You guidelines and using the Material components library won't need to worry about the implementation/handling of contrast level changes.
A new "contrast level" slider is buried under Settings > Accessibility > Color and motion. It currently only supports "Standard", medium, and "High" values. This slider controls the value of Settings.Secure.contrast_level (0 for "Standard", 0.5 for the mid setting, and 1.0 for "High") which in turn can be read by apps calling AccessibilityManager's new getUiContrast() method.
SystemUI's ThemeOverlayController class calls that method to read the color contrast value and generate the "dynamic" color scheme accordingly, which is then mapped to the R.color values I mentioned before through the "dynamic" FRRO.
I dumped the values of the "dynamic" FRRO generated based on the AOSP wallpaper and contrast_level values of 0, 0.5, and 1.0. It's evident that as the contrast increases, the tone (lightness) of foreground colors becomes further from the tone of background colors.
Google's official explanation of the dynamic scheme (H/T @kdrag0n):
"Colors without backgrounds do not change tone when contrast changes. Colors with backgrounds become closer to their background as contrast lowers, and further when contrast increases."How this ends up looking in apps depends on how devs choose which tokens to color which UI elements, but in general, devs adhering to Material You guidelines and using the Material components library won't need to worry about the implementation/handling of contrast level changes.
👍25🔥1