Hands-on: I finally got this fully working, so here's a full demo of Android 14's new partial screen recording feature.
This feature lets you record a single app without any System UI elements or notifications appearing in the video! A useful feature to have when you need to screen record something to share with others!
(In the app selector dialog, you can swipe up to show the full app list. You can also swipe left or right on the carousel to show more apps from your recents app list.)
EDIT:
If you leave the app you selected to record, then Android will continue screen recording but the content will be black. If you open the app again, the contents will once again be captured in the same recording.
The recording doesn't end unless you swipe down and end it manually.
This feature lets you record a single app without any System UI elements or notifications appearing in the video! A useful feature to have when you need to screen record something to share with others!
(In the app selector dialog, you can swipe up to show the full app list. You can also swipe left or right on the carousel to show more apps from your recents app list.)
EDIT:
If you leave the app you selected to record, then Android will continue screen recording but the content will be black. If you open the app again, the contents will once again be captured in the same recording.
The recording doesn't end unless you swipe down and end it manually.
๐ฅ59โคโ๐ฅ10๐8โค3๐ฅฐ2๐2
Android 14 Beta 2 continues to improve on the "app cloning" feature I first revealed in DP1. A new launcher flag called ENABLE_APP_CLONING_CHANGES_IN_LAUNCHER has been added that, when toggled, hides cloned apps from the work profile tab, as illustrated below.
However, the home screen icons are still not differentiated yet, even though in Settings, the cloned apps have a unique icon badge. This will hopefully be remedied in a future build!
For more details on this in-development app cloning feature, refer to this article.
However, the home screen icons are still not differentiated yet, even though in Settings, the cloned apps have a unique icon badge. This will hopefully be remedied in a future build!
For more details on this in-development app cloning feature, refer to this article.
โคโ๐ฅ30๐14โค5๐1
If your app uses the SafetyNet Attestation API, heads up that the deprecation timeline has been adjusted!
Now, you have until the end of January 2024 to migrate to the Play Integrity API. If you migrate by then, SNet Attestation will continue to work on older versions of your app.
SNet Attestation will fully stop working at the end of January 2025.
Visit this page to see the full SafetyNet Attestation deprecation timeline.
Now, you have until the end of January 2024 to migrate to the Play Integrity API. If you migrate by then, SNet Attestation will continue to work on older versions of your app.
SNet Attestation will fully stop working at the end of January 2025.
Visit this page to see the full SafetyNet Attestation deprecation timeline.
๐16
Mishaal's Android News Feed
Android 14 is adding a new safety feature to protect your hearing: Headphone loud sound alert. Android will alert you if you've been listening to audio at a volume above the recommended level for long periods over your headphones. You can keep listeningโฆ
This feature is indeed live in Android 14 Beta 2! User Nick Cipriani shared this image from their Pixel. Oddly, they received this message while playing audio from their Bluetooth speaker and not headphones.
๐41๐4
If you connect a physical keyboard to a large screen device running Android 14, under Settings > System > Keyboard > Physical keyboard, the "keyboard shortcuts" menu will now show a MUCH more comprehensive list of available keyboard shortcuts, as shown above!
The more comprehensive list of keyboard shortcuts only appears on large screen devices, and it was added in Android 14 Beta 2. On phones/earlier versions of Android, the keyboard shortcuts dialog contained much fewer items.
This is one of several improvements Google is making in Android 14 to improve the use of physical keyboards + trackpads, as I previously talked about in this article.
The more comprehensive list of keyboard shortcuts only appears on large screen devices, and it was added in Android 14 Beta 2. On phones/earlier versions of Android, the keyboard shortcuts dialog contained much fewer items.
This is one of several improvements Google is making in Android 14 to improve the use of physical keyboards + trackpads, as I previously talked about in this article.
๐37
Google has added a new Vulnerability Reward Program (VRP) called the Mobile VRP that focuses on its first-party Android apps.
Security researchers that disclose qualifying vulnerabilities impacting Android apps developed or maintained by Google can be rewarded depending on the type of vulnerability, the scenario in which the vulnerability can be exploited, and the importance of the app that's affected.
Full details on the new Google Mobile VRP can be found here.
Security researchers that disclose qualifying vulnerabilities impacting Android apps developed or maintained by Google can be rewarded depending on the type of vulnerability, the scenario in which the vulnerability can be exploited, and the importance of the app that's affected.
Full details on the new Google Mobile VRP can be found here.
๐20๐ฅ11
A few days ago, I asked y'all (on Twitter) if you've enabled Android's Themed Icon feature and which apps haven't implemented it. Some of you recalled that Google is working on a feature to generate a themed icon for ANY app.
How good is the forced Themed Icon feature? Here's a comparison!
Okay, so first of all, attached to this post is an image showing the apps I'm working with. On the left we've got apps that support the Themed Icon feature (ie. they supply a monochrome icon). On the right we've got apps that don't support the feature.
For this little experiment, I applied 3 different wallpapers and noted what the background & foreground colors of each icon should be. (I looked at Launcher3's source to find out exactly which R.color values it pulls from to theme icons.)
Attached to this post is an image showing what it looks like when you theme icons of apps that DO supply a monochrome icon. As expected, it looks fine because the developers themselves created a monochrome icon rather than an algorithm doing it.
Also attached to this post is an image showing what it looks like when Android generates a monochrome icon for apps that don't supply one, ie. forcing themed icon support. I'll let you be the judge about whether this is shippable.
How good is the forced Themed Icon feature? Here's a comparison!
Okay, so first of all, attached to this post is an image showing the apps I'm working with. On the left we've got apps that support the Themed Icon feature (ie. they supply a monochrome icon). On the right we've got apps that don't support the feature.
For this little experiment, I applied 3 different wallpapers and noted what the background & foreground colors of each icon should be. (I looked at Launcher3's source to find out exactly which R.color values it pulls from to theme icons.)
Attached to this post is an image showing what it looks like when you theme icons of apps that DO supply a monochrome icon. As expected, it looks fine because the developers themselves created a monochrome icon rather than an algorithm doing it.
Also attached to this post is an image showing what it looks like when Android generates a monochrome icon for apps that don't supply one, ie. forcing themed icon support. I'll let you be the judge about whether this is shippable.
๐21๐ญ3๐2
Mishaal's Android News Feed
A few days ago, I asked y'all (on Twitter) if you've enabled Android's Themed Icon feature and which apps haven't implemented it. Some of you recalled that Google is working on a feature to generate a themed icon for ANY app. How good is the forced Themedโฆ
For a bit of context, when Google released Android 13 QPR2 Beta 2, I spotted a new launcher flag named "ENABLE_FORCED_MONO_ICON" that "enable[s] the ability to generate monochromatic icons, if it is not provided by the app.
The existence of that launcher flag got quite a few people excited, because many popular Android apps have yet to implement Themed Icon support, as shown by the replies to my previous tweet.
So many were wondering: Will this feature be available to users in Android 14? While it's true that the launcher flag has carried over from the QPR betas, there's no evidence Google will expose it to users.
This feels more like a one-off experiment, something a few OEMs (and custom launcher/ROM developers, it's open source) might expose to users in developer options, if we're lucky.
The existence of that launcher flag got quite a few people excited, because many popular Android apps have yet to implement Themed Icon support, as shown by the replies to my previous tweet.
So many were wondering: Will this feature be available to users in Android 14? While it's true that the launcher flag has carried over from the QPR betas, there's no evidence Google will expose it to users.
This feels more like a one-off experiment, something a few OEMs (and custom launcher/ROM developers, it's open source) might expose to users in developer options, if we're lucky.
X (formerly Twitter)
Mishaal Rahman (@MishaalRahman) on X
WOW! Google is testing letting you generate themed icons for ANY app, even if it doesn't provide its own monochromatic icon! This is currently disabled by default and hidden behind the "ENABLE_FORCED_MONO_ICON" flag.
๐21๐ฑ1
Mishaal's Android News Feed
If you're planning to manually install Android 14 Beta 1 using the factory image for your Pixel when it's released, do not upgrade platform-tools right now. Version 34.0.0 and newer currently have a bug that prevents them from rebooting to userspace fastbootโฆ
Google has released platform-tools_r34.0.3, fixing the issue described above.
The SDK Platform Tools release notes page hasn't yet been updated to reflect this update, but you can download the latest tools directly (I got the update through Android Studio).
The SDK Platform Tools release notes page hasn't yet been updated to reflect this update, but you can download the latest tools directly (I got the update through Android Studio).
โค18๐8๐ฑ4
Google is preparing to add a Thread network stack for Android, and it could become a modular system component (AKA Project Mainline module) as soon as the next release, ie. Android 15 Vanilla Ice Cream.
A "ThreadNetwork" repo was added to AOSP a few months back, though no code has been added to it yet. The code change listing the owners of the project described it as the "ThreadNetwork mainline project."
The ThreadNetwork repo is now being added to the AOSP platform manifest. And a new PackageManager API is being added that apps can use to see if a particular device supports Thread (android.hardware.threadnetwork).
By making Android's new Thread network stack part of Project Mainline, it would be more easily updatable through Google Play System Updates. Would also improve quality and interoperability.
Android's Bluetooth, WiFi, and UWB stacks are already Mainline modules, and soon NFC will be too.
AFAIK, there aren't yet any Android devices that support Thread. According to The Verge, not even the new Pixel Tablet supports it, which is disappointing.
Devices need radio hardware to support the IEEE 802.15.4 protocol that Thread is based on.
A "ThreadNetwork" repo was added to AOSP a few months back, though no code has been added to it yet. The code change listing the owners of the project described it as the "ThreadNetwork mainline project."
The ThreadNetwork repo is now being added to the AOSP platform manifest. And a new PackageManager API is being added that apps can use to see if a particular device supports Thread (android.hardware.threadnetwork).
By making Android's new Thread network stack part of Project Mainline, it would be more easily updatable through Google Play System Updates. Would also improve quality and interoperability.
Android's Bluetooth, WiFi, and UWB stacks are already Mainline modules, and soon NFC will be too.
AFAIK, there aren't yet any Android devices that support Thread. According to The Verge, not even the new Pixel Tablet supports it, which is disappointing.
Devices need radio hardware to support the IEEE 802.15.4 protocol that Thread is based on.
๐15๐ฅ4๐คก2
Here's another look at the lock screen shortcut customization feature Google announced at I/O!
The available shortcuts include:
* QR code scanner
* Flashlight
* Video camera
* Notetaking (see below for explanation)
* Mute
* Wallet
* Camera
* Do Not Disturb
* Device Controls
The attached screen recording shows the lock screen shortcuts feature in action. Note that you can only place a single shortcut on both the left and the right, and that you have to long-press a shortcut to activate it.
Most of the lock screen shortcuts are pretty self-explanatory. Wallet is greyed out because I haven't added a card yet, while notetaking is greyed out because I don't have an app set as the "default notes app."
As I explained in an earlier thread, Android 14 adds support for a default notes app. The default notes app can use the new AppClips API/feature to trigger a screenshot to be taken that the user can edit before inserting into a note.
Given that the Pixel Tablet supports USI styli, I'm guessing this whole notetaking feature is intended for that device. Though Google hasn't announced a 1P stylus accessory yet, and it doesn't seem like Google Keep supports this feature either for now.
Lock screen shortcuts aren't exclusive to Pixel, unlike the new wallpaper features. The shortcut code is available in AOSP (it's called "keyguard quick affordances") as is the documentation.
Hopefully most OEMs enable this in their Android 14 builds!
The available shortcuts include:
* QR code scanner
* Flashlight
* Video camera
* Notetaking (see below for explanation)
* Mute
* Wallet
* Camera
* Do Not Disturb
* Device Controls
The attached screen recording shows the lock screen shortcuts feature in action. Note that you can only place a single shortcut on both the left and the right, and that you have to long-press a shortcut to activate it.
Most of the lock screen shortcuts are pretty self-explanatory. Wallet is greyed out because I haven't added a card yet, while notetaking is greyed out because I don't have an app set as the "default notes app."
As I explained in an earlier thread, Android 14 adds support for a default notes app. The default notes app can use the new AppClips API/feature to trigger a screenshot to be taken that the user can edit before inserting into a note.
Given that the Pixel Tablet supports USI styli, I'm guessing this whole notetaking feature is intended for that device. Though Google hasn't announced a 1P stylus accessory yet, and it doesn't seem like Google Keep supports this feature either for now.
Lock screen shortcuts aren't exclusive to Pixel, unlike the new wallpaper features. The shortcut code is available in AOSP (it's called "keyguard quick affordances") as is the documentation.
Hopefully most OEMs enable this in their Android 14 builds!
๐42โคโ๐ฅ6โค4๐1
One of the features I was expecting to see in Android 14 was the ability to turn your phone into a USB webcam for your PC. Google hasn't talked about this feature yet, but I hope they still plan to ship it!
Here's some tidbits about Android 14's USB webcam feature ๐
So back in February, I discovered code changes in AOSP that hinted at a new "DeviceAsWebcam" service (which upon re-reading the code changes I now believe to be a separate system app) that "turns an Android device into a webcam."
Android devices that support the UVC gadget mode (ie. the kernel is compiled with CONFIG_USB_CONFIGFS_F_UVC=y) can be set up to send camera frames to a /dev/video* node that a host device supporting UVC webcams can read from.
A dedicated DeviceAsWebcam app - which I should note has not yet been shipped on any Pixel builds - is what, I believe, would be responsible for actually using Android's Camera API to forward frames.
Only system apps-like DeviceAsWebcam-would have permission to R/W data to the /dev/video* node. In fact, the USB configuration file for all Tensor & Tensor 2-based (but not SM7250) Pixels already sets up the UVC function. Attached to this post is a snippet from init.gs101.usb.rc/init.gs201.usb.rc.
But since the DAW app is not present in current Android 14 beta builds, we can't actually use this functionality, though we can surface the "Webcam" option in "USB Preferences" as shown in the first post. The "Webcam" option appears when the system property ro.usb.uvc.enabled is set to true. Settings calls UsbManager#isUvcSupportEnabled(), which reads this property, to decide whether to show this option.
When you select "webcam", UsbDeviceManager sets the USB config to "uvc" and the android.hardware.usb.action.USB_STATE broadcast is sent with the USB_FUNCTION_UVC boolean extra. DAW presumably listens for this broadcast to know when to start forwarding frames.
Here's some tidbits about Android 14's USB webcam feature ๐
So back in February, I discovered code changes in AOSP that hinted at a new "DeviceAsWebcam" service (which upon re-reading the code changes I now believe to be a separate system app) that "turns an Android device into a webcam."
Android devices that support the UVC gadget mode (ie. the kernel is compiled with CONFIG_USB_CONFIGFS_F_UVC=y) can be set up to send camera frames to a /dev/video* node that a host device supporting UVC webcams can read from.
A dedicated DeviceAsWebcam app - which I should note has not yet been shipped on any Pixel builds - is what, I believe, would be responsible for actually using Android's Camera API to forward frames.
Only system apps-like DeviceAsWebcam-would have permission to R/W data to the /dev/video* node. In fact, the USB configuration file for all Tensor & Tensor 2-based (but not SM7250) Pixels already sets up the UVC function. Attached to this post is a snippet from init.gs101.usb.rc/init.gs201.usb.rc.
But since the DAW app is not present in current Android 14 beta builds, we can't actually use this functionality, though we can surface the "Webcam" option in "USB Preferences" as shown in the first post. The "Webcam" option appears when the system property ro.usb.uvc.enabled is set to true. Settings calls UsbManager#isUvcSupportEnabled(), which reads this property, to decide whether to show this option.
When you select "webcam", UsbDeviceManager sets the USB config to "uvc" and the android.hardware.usb.action.USB_STATE broadcast is sent with the USB_FUNCTION_UVC boolean extra. DAW presumably listens for this broadcast to know when to start forwarding frames.
๐ฅ31๐19
Here's a look at potentially all of the custom clock options Pixel users will get in Android 14, courtesy of Kamila Wojciechowska (Za_Raczke on Twitter)!
Google said at I/O that lock screen clock customization will be available "next month", so expect to see these in Android 14 Beta 3.
For comparison, I've also attached the screen recording Google shared at I/O that shows off some of the lock screen clock options. (Google's is the higher resolution one). Kamila's video shows more of the clocks that will likely be available to choose from.
Google said at I/O that lock screen clock customization will be available "next month", so expect to see these in Android 14 Beta 3.
For comparison, I've also attached the screen recording Google shared at I/O that shows off some of the lock screen clock options. (Google's is the higher resolution one). Kamila's video shows more of the clocks that will likely be available to choose from.
๐ฅ42๐คฎ16๐9๐ฅฐ1