Mishaal's Android News Feed
Finally get to experience Android 13 on an OEM device in my possession, thanks to ASUS rolling it out to the Zenfone 9 today. It isn't based on the recent Android 13 QPR1 release, but it does have the latest December 2022 security patches! Like I said the…
Let's see what Google thinks are the most important Android 13 features to introduce users to! This "Welcome to Android 13" notification is part of the "Android Upgrade Party" initiative I mention in this article.
1) Runtime permission for notifications
2) Cross-device copy/paste
3) Photo Picker
4) Update media player
5) Per-app languages
1) Runtime permission for notifications
2) Cross-device copy/paste
3) Photo Picker
4) Update media player
5) Per-app languages
👍21🤔2👨💻1
If you're wondering how Android's "Private Compute Core" really works, Google has just shared a technical whitepaper that describes its processes and mechanisms in-depth, complete with helpful diagrams!
Blog post | Private Compute Services sources
Blog post | Private Compute Services sources
👍17
Support for passkeys has been added to the stable version of Google Chrome (M108) for Android, Windows 11, and macOS! Passkeys are a replacement for passwords, which are prone to being leaked or phished.
By the way, the next episode of my Android Bytes podcast will covers passkeys and why you should care. We invited two awesome guests who have done a lot of public outreach on passkeys to come onto the show and explain things at a high level. Give it a listen when it's out!
"Introducing passkeys in Chrome" - Chromium Blog | My Twitter thread on the previous announcement
By the way, the next episode of my Android Bytes podcast will covers passkeys and why you should care. We invited two awesome guests who have done a lot of public outreach on passkeys to come onto the show and explain things at a high level. Give it a listen when it's out!
"Introducing passkeys in Chrome" - Chromium Blog | My Twitter thread on the previous announcement
👍16❤7
The latest Pixel Feature Drop that rolled out earlier this week also brought Android 13 QPR1, which looks like a minor update on the surface. But if you dig deep, there's a LOT of hidden features under the surface! Here are 10+ upcoming features I discovered in QPR1:
1) A revived desktop mode: Google's finally trying to make Android's barebones "desktop mode" experience more usable. There's a rumor of a "Pro" Pixel Tablet in the works according to @nullby so who knows what this could be for 👀
2) You know that taskbar that Google introduced in Android 12L? The one that only appears on tablets (or when you set the screen width to 600dp)? Google's working on letting you use that taskbar on phones WITHOUT needing to change the density!
3) I've already talked about how Android 13 is revamping the screen saver experience, and QPR1 made further improvements. There are new "smartspace", "media entry", and "home controls" complications. This is likely how the Pixel Tablet will act as a Nest Hub when docked😄
4) Android 13 QPR1 updated the ThemePicker app to support a new "custom clock" section, which will let you customize the lock screen clock. You can't customize clocks yet since it requires a separate app providing the clock plugins, though!
5) Google's working on letting you take a "partial screen share"! The feature is partially (heh) implemented in Android 13 QPR1.
6) In prep for the Pixel Tablet (or maybe Pixel Fold?), Android 13 QPR1 adds a special button to the taskbar that can launch Google Keep's drawing mode in a floating window.
7) There's a new "advanced VPN" feature in QPR1. Advanced VPNs don't need a user's consent to appear in the list of VPNs in Settings (that doesn't mean they're always active). Likely related to augmenting the Pixel 7's free VPN by Google One down the road?
8) Android TV is getting a "splitscreen menu". I'd love to run some apps side-by-side on my SHIELD TV (...if it ever gets Android 13)!
9) Immersive mode support is coming to Android Automotive apps!
10) The handling of Pixel's Quick Tap feature is being moved to Android's Private Compute Core. Is it for improved privacy? Potentially opening it up to OEMs? IDK!
There are some other hidden changes I discovered in Android 13 QPR1 that I won't mention here, because you can read about them (and see the code changes/screenshots for yourself) in this article over on blog.esper.io.
1) A revived desktop mode: Google's finally trying to make Android's barebones "desktop mode" experience more usable. There's a rumor of a "Pro" Pixel Tablet in the works according to @nullby so who knows what this could be for 👀
2) You know that taskbar that Google introduced in Android 12L? The one that only appears on tablets (or when you set the screen width to 600dp)? Google's working on letting you use that taskbar on phones WITHOUT needing to change the density!
3) I've already talked about how Android 13 is revamping the screen saver experience, and QPR1 made further improvements. There are new "smartspace", "media entry", and "home controls" complications. This is likely how the Pixel Tablet will act as a Nest Hub when docked😄
4) Android 13 QPR1 updated the ThemePicker app to support a new "custom clock" section, which will let you customize the lock screen clock. You can't customize clocks yet since it requires a separate app providing the clock plugins, though!
5) Google's working on letting you take a "partial screen share"! The feature is partially (heh) implemented in Android 13 QPR1.
6) In prep for the Pixel Tablet (or maybe Pixel Fold?), Android 13 QPR1 adds a special button to the taskbar that can launch Google Keep's drawing mode in a floating window.
7) There's a new "advanced VPN" feature in QPR1. Advanced VPNs don't need a user's consent to appear in the list of VPNs in Settings (that doesn't mean they're always active). Likely related to augmenting the Pixel 7's free VPN by Google One down the road?
8) Android TV is getting a "splitscreen menu". I'd love to run some apps side-by-side on my SHIELD TV (...if it ever gets Android 13)!
9) Immersive mode support is coming to Android Automotive apps!
10) The handling of Pixel's Quick Tap feature is being moved to Android's Private Compute Core. Is it for improved privacy? Potentially opening it up to OEMs? IDK!
There are some other hidden changes I discovered in Android 13 QPR1 that I won't mention here, because you can read about them (and see the code changes/screenshots for yourself) in this article over on blog.esper.io.
www.esper.io
The Hidden Features Revealed by Android 13 QPR1’s Source Code
Android 13 QPR1 was released in December 2022, and its source code hints at a couple of new features coming in later releases.
❤26👍8🔥5🥰1👏1🤝1
The model used by ML Kit's smart reply API can now be dynamically downloaded on user devices through Play Services. This "unbundled model" is now in beta and reduces app download size by ~5.5MB compared to the bundled version.
👍11
Google has released the first beta for the second Quarterly Platform Release of Android 13, in other words Android 13 QPR2 Beta 1!
Here are the release details:
Here are the release details:
👍30❤1
If you want to see what's new in Android 13 QPR2 Beta 1, follow along on Twitter as I share each discovery in real-time!
Twitter
Here's what's new in Android 13 QPR2 Beta 2 (thread)
👍9❤3
YouTube Music is rolling out support for letting you switch playback to Google Cast devices through the Output Switcher on Android 13!
I've seen a few reports of this rolling out tonight, from a few Samsung users but also a couple of Pixel users on Android 13.
For context on what this "Output Switcher" feature is all about and why it's limited to Android 13, read this article I wrote a few months back.
I've seen a few reports of this rolling out tonight, from a few Samsung users but also a couple of Pixel users on Android 13.
For context on what this "Output Switcher" feature is all about and why it's limited to Android 13, read this article I wrote a few months back.
👍20👏2
Mishaal's Android News Feed
YouTube Music is rolling out support for letting you switch playback to Google Cast devices through the Output Switcher on Android 13! I've seen a few reports of this rolling out tonight, from a few Samsung users but also a couple of Pixel users on Android…
I've seen at least two users mention they had Stream Expansion enabled for them, but it quickly disappeared after some time.
Stream Expansion lets you expand audio playback to multiple Cast devices. When enabled, you'll see a radio button next to Cast devices in the output switcher.
Stream Expansion doesn't depend on app support - Google Play Services handles it.
(Screenshot credits: @wodoodporny)
Stream Expansion lets you expand audio playback to multiple Cast devices. When enabled, you'll see a radio button next to Cast devices in the output switcher.
Stream Expansion doesn't depend on app support - Google Play Services handles it.
(Screenshot credits: @wodoodporny)
👍18🥰1👨💻1
There's a neat Android app on Google Play called "Nearby Sharing Windows 10/11" that's both compatible with Windows' Nearby Sharing protocol and supports bidirectional sharing/receiving.
Here's a demo of me sending a link from Android to Windows. The app adds a share target to Android's share sheet, making it easy to share files/links/etc with any PC running Windows. No extra software/server/etc needed on the PC side.
There are other apps that support SENDING files from Android to Windows using Microsoft's Nearby Sharing protocol, but AFAIK, this is the only one that supports RECEIVING files from Windows. Here's a demo.
Some caveats: Receiving functionality is currently only available in the beta version of the app and is buggy/quite limited. It only works via Bluetooth right now, so you can only send small files/links.
Yes, Microsoft offers the Phone Link app, and yes Google is coming out with its own Android <--> Windows sharing functionality. The former does a lot more than just sharing, though, while the latter (Google Nearby Share) isn't compatible with Microsoft's Nearby Sharing.
While this is a neat project, I'll personally wait for Google's Nearby Share to come to Windows. It'll probably be a lot more polished (hopefully lol) considering it's being worked on by a whole team of engineers, etc.
Google's Nearby protocol is open source, by the way, so you can track the progress of its development here. A lot has been done to support Windows recently. Note that Nearby Share is a layer on top (UI, etc.) and that it isn't open source.
Here's a demo of me sending a link from Android to Windows. The app adds a share target to Android's share sheet, making it easy to share files/links/etc with any PC running Windows. No extra software/server/etc needed on the PC side.
There are other apps that support SENDING files from Android to Windows using Microsoft's Nearby Sharing protocol, but AFAIK, this is the only one that supports RECEIVING files from Windows. Here's a demo.
Some caveats: Receiving functionality is currently only available in the beta version of the app and is buggy/quite limited. It only works via Bluetooth right now, so you can only send small files/links.
Yes, Microsoft offers the Phone Link app, and yes Google is coming out with its own Android <--> Windows sharing functionality. The former does a lot more than just sharing, though, while the latter (Google Nearby Share) isn't compatible with Microsoft's Nearby Sharing.
While this is a neat project, I'll personally wait for Google's Nearby Share to come to Windows. It'll probably be a lot more polished (hopefully lol) considering it's being worked on by a whole team of engineers, etc.
Google's Nearby protocol is open source, by the way, so you can track the progress of its development here. A lot has been done to support Windows recently. Note that Nearby Share is a layer on top (UI, etc.) and that it isn't open source.
YouTube
Nearby Sharing app on Android - Sending a link from Android to Windows
👍15🔥9❤1
Not a fan of disjointed Twitter threads?
If you want to read a summary of EVERYTHING I found in Android 13 QPR2 Beta 1 without scrolling through my massive Twitter thread, here it is on Reddit.
If you want to read a summary of EVERYTHING I found in Android 13 QPR2 Beta 1 without scrolling through my massive Twitter thread, here it is on Reddit.
Reddit
From the Android community on Reddit
Explore this post and more from the Android community
👍24❤4👏1
A few weeks ago, Project Zero criticized Pixel and other Android OEMs for failing to ship an updated GPU driver that fixes a vulnerability disclosed months ago. Affected Pixel devices on the Android 13 QPR2 Beta should now have the updated GPU driver!For context on this vulnerability and the "patch gap" called out by the Project Zero team, refer to this blog post.
The vulnerability, tracked as CVE-2022-36449, affects the Arm Mali GPU Kernel Driver. "This affects Midgard r4p0 through r32p0, Bifrost r0p0 through r38p0 and r39p0 before r38p1, and Valhall r19p0 through r38p0 and r39p0 before r38p1."
The Pixel 6's GPU is based on the 2nd gen of Arm's Valhall GPU architecture, while the Pixel 7's GPU on the 3rd gen. Thus, for them to be secure, Google (+ other OEMs w/ vulnerable devices with Valhall GPUs) have to ship the r38p1 or later kernel driver.
The Dec. 2022/QPR1 update ships with the r36 kernel driver for both raviole (Pixel 6, 6a, and 6 Pro) and pantah (Pixel 7 and 7 Pro). In contrast, QPR2 Beta 1 ships with the r38p1 kernel driver for both device families. (The exact commit in question.)
Using the "Hardware CapsViewer for Vulkan" app, we can see the driver version is 36.0.0 on the Pixel 6/7 series running QPR1, and 38.1.0 on QPR2 Beta 1. This app, I believe, reports the userspace driver version, but it should be the same as the kernel driver version.
Google told Engadget: "The fix provided by ARM is currently undergoing testing for Android and Pixel devices and will be delivered in the coming weeks...Android OEM partners will be required to take the patch to comply with future SPL requirements."
So while the patch isn't available for Pixel users on a stable release yet, they may not have to wait for the QPR2 stable release in March. An Android Security Bulletin as early as January 2023 could mandate the inclusion of this patch. That lines up with what Google said.
The vulnerability, tracked as CVE-2022-36449, affects the Arm Mali GPU Kernel Driver. "This affects Midgard r4p0 through r32p0, Bifrost r0p0 through r38p0 and r39p0 before r38p1, and Valhall r19p0 through r38p0 and r39p0 before r38p1."
The Pixel 6's GPU is based on the 2nd gen of Arm's Valhall GPU architecture, while the Pixel 7's GPU on the 3rd gen. Thus, for them to be secure, Google (+ other OEMs w/ vulnerable devices with Valhall GPUs) have to ship the r38p1 or later kernel driver.
The Dec. 2022/QPR1 update ships with the r36 kernel driver for both raviole (Pixel 6, 6a, and 6 Pro) and pantah (Pixel 7 and 7 Pro). In contrast, QPR2 Beta 1 ships with the r38p1 kernel driver for both device families. (The exact commit in question.)
Using the "Hardware CapsViewer for Vulkan" app, we can see the driver version is 36.0.0 on the Pixel 6/7 series running QPR1, and 38.1.0 on QPR2 Beta 1. This app, I believe, reports the userspace driver version, but it should be the same as the kernel driver version.
Google told Engadget: "The fix provided by ARM is currently undergoing testing for Android and Pixel devices and will be delivered in the coming weeks...Android OEM partners will be required to take the patch to comply with future SPL requirements."
So while the patch isn't available for Pixel users on a stable release yet, they may not have to wait for the QPR2 stable release in March. An Android Security Bulletin as early as January 2023 could mandate the inclusion of this patch. That lines up with what Google said.
👍20🔥5
This media is not supported in your browser
VIEW IN TELEGRAM
I mentioned this in my blog post last week, but I've now got it enabled: Here's a look at the new back gesture design in Android 13! As you can see, the back arrow is now surrounded by a bubble (that supports dynamic theming).
This design is being tested separately from the predictive back gesture, but it's likely the two will launch for users in Android 14. (Predictive back gesture is only available as a developer option in A13. This new back design is gated by a hidden flag.)
This design is being tested separately from the predictive back gesture, but it's likely the two will launch for users in Android 14. (Predictive back gesture is only available as a developer option in A13. This new back design is gated by a hidden flag.)
🔥30👍10👎3
The new Photo Picker feature is technically available on devices running Android versions as old as Android 4.4, but there's a good chance you haven't seen it yet. That's because the backported version currently requires developers to do some extra work to support it.
There are two versions of the Photo Picker: the system version and the GMS version. The system version is only available on Android 11+ and is provided through a Project Mainline module. The GMS version is provided through Google Play Services for older Android versions.
The problem is that the system Photo Picker responds to a different intent than the GMS Photo Picker. Fortunately, androidx.activity will soon handle everything for developers. It'll check whether the system or GMS Photo Picker is available and then invoke the correct intent.
If you want to learn how the Photo Picker works, these two blog posts will tell you probably more than you need to know, lol.
There are two versions of the Photo Picker: the system version and the GMS version. The system version is only available on Android 11+ and is provided through a Project Mainline module. The GMS version is provided through Google Play Services for older Android versions.
The problem is that the system Photo Picker responds to a different intent than the GMS Photo Picker. Fortunately, androidx.activity will soon handle everything for developers. It'll check whether the system or GMS Photo Picker is available and then invoke the correct intent.
If you want to learn how the Photo Picker works, these two blog posts will tell you probably more than you need to know, lol.
Esper Blog
Android Photo Picker: How Google is bringing it to older versions
Android's new Photo Picker feature doesn't require the Android 13 update. Here's how Google will bring it to your current phone.
👍15