"Add an intent filter action, which can be used by 3p apps to declare messaging support for Android Auto"
Seems Google's making it easier for messaging apps to work with Android Auto. By declaring androidx.car.app.messaging.action.HANDLE_CAR_MESSAGING in the Manifest, apps can show up in AA's app launcher with the default in-car messaging experience.
Seems Google's making it easier for messaging apps to work with Android Auto. By declaring androidx.car.app.messaging.action.HANDLE_CAR_MESSAGING in the Manifest, apps can show up in AA's app launcher with the default in-car messaging experience.
❤1
The CTS test that validates whether an Android 13 build supports generating dynamic color tonal palettes (AKA the monet theme engine) won't be run on Wear OS watches, as THEME_CUSTOMIZATION_OVERLAY_PACKAGES isn't available on Wear OS.
Wear OS uses watchfaces instead of wallpapers anyway (though monet's seed color doesn't have to be derived from a wallpaper). It's also still possible Wear OS will just pick colors from the user's paired phone (at least I hope so).
The fact that Google's adding Wear OS-specific changes to the Android 13 CTS branches suggests that the next major version of Wear OS will be based on Android 13, not Android 12 or 12L. (There are other AOSP commits hinting at this, too). This wouldn't be too surprising because the current version of Wear OS - Wear OS 3.X - is based on Android 11, while Wear OS 2.x was based on Android 9.
Wear OS uses watchfaces instead of wallpapers anyway (though monet's seed color doesn't have to be derived from a wallpaper). It's also still possible Wear OS will just pick colors from the user's paired phone (at least I hope so).
The fact that Google's adding Wear OS-specific changes to the Android 13 CTS branches suggests that the next major version of Wear OS will be based on Android 13, not Android 12 or 12L. (There are other AOSP commits hinting at this, too). This wouldn't be too surprising because the current version of Wear OS - Wear OS 3.X - is based on Android 11, while Wear OS 2.x was based on Android 9.
👍3
Google's working on a new system service called "background_install_control" that will "detect background installed apps and provide the list of such apps."
Interestingly, a Googler says that they "have an Android U feature (Background Install Control) and several upcoming Android V features depending on this service."
Now, I wonder what this could be used for? 🤔
They've added SELinux policy for this, but nothing else from what I can see in AOSP.I have no idea what this could be used for. The design docs linked in the comments are inaccessible to non-Googlers.
Interestingly, a Googler says that they "have an Android U feature (Background Install Control) and several upcoming Android V features depending on this service."
Now, I wonder what this could be used for? 🤔
They've added SELinux policy for this, but nothing else from what I can see in AOSP.I have no idea what this could be used for. The design docs linked in the comments are inaccessible to non-Googlers.
👍4🔥3🤔1
Google plans to ship Widevine DRM in an APEX module as early as Android 14. Widevine DRM will be a "vendor APEX", which is a new concept introduced with Android 13. Currently, vendor APEXes are non-updatable, but this is set to be changed in Android 14.
For more details on what an APEX module is, refer to this article.
For more details on what an APEX module is, refer to this article.
👍5👏1
Google's likely working on NTFS support for Android! They've added SELinux policy for ntfsfix, a utility to fix some common NTFS problems. We'll still need a functional NTFS implementation and updates to vold (Android's volume daemon) in order to mount NTFS drives, but the existence of this patch suggests they could also be working on adding that.
A kernel driver for NTFS was added in Linux 5.15. I'm hoping that Android devices with GKI kernels android13-5.15 and newer running Android 14 will support mounting NTFS drives (assuming the rest of the work gets done to support that).
Notably, exFAT is natively supported on Android 13 devices with GKI kernels android12-5.10 and newer.
A kernel driver for NTFS was added in Linux 5.15. I'm hoping that Android devices with GKI kernels android13-5.15 and newer running Android 14 will support mounting NTFS drives (assuming the rest of the work gets done to support that).
Notably, exFAT is natively supported on Android 13 devices with GKI kernels android12-5.10 and newer.
👍10🔥2
The Vendor Software Requirements (VSR) for Android 14 (API level 34) will require that the Identity Credential HAL be implemented at feature version 202301 or later.
IC is the framework API enabling the secure storage of mobile driver's licenses in Android. The HAL enables hardware-backed support for storing identity documents, and currently, only Pixels have implemented this HAL.
If you follow my reporting, then you'll have heard this one before. That's because the plan was to require it for VSR-13, but that requirement got punted for VSR-14. I talked about it a bit in this article.
IC is the framework API enabling the secure storage of mobile driver's licenses in Android. The HAL enables hardware-backed support for storing identity documents, and currently, only Pixels have implemented this HAL.
If you follow my reporting, then you'll have heard this one before. That's because the plan was to require it for VSR-13, but that requirement got punted for VSR-14. I talked about it a bit in this article.
👍9
Someone requested I enable comments on these posts. I had to create a separate TG group for that to work, so here it is: https://t.iss.one/AndroidNerdPlayground
👍15