Google has deleted all code related to Fast Pair from AOSP.
Fast Pair is Google's proprietary standard for simplifying the first time discovery and pairing of nearby devices over Bluetooth Low Energy. It's available on most Android devices through the Google Play Services app.
However, Google Play Services is not available on devices shipped in China, which means that Android devices in China don't support Fast Pair. Some OEMs implemented their own Fast Pair-like pairing process, but this usually only works with audio products from their own brand.
To make Fast Pair ubiquitous on Android, Google aimed to bring Fast Pair to AOSP as part of the Connectivity Mainline module. The code for Fast Pair and the HalfSheet UX (the pop-up UI that appears when a device is discovered) was uploaded to AOSP with the release of Android 13, but this code was just deleted by Google a few days ago.
I'm not entirely sure why Fast Pair was deleted from AOSP, as I don't have access to the Issue Tracker reports linked in the commit. Perhaps it saw low adoption/interest from OEMs? If you know why it was removed, send me a DM!
Fast Pair is Google's proprietary standard for simplifying the first time discovery and pairing of nearby devices over Bluetooth Low Energy. It's available on most Android devices through the Google Play Services app.
However, Google Play Services is not available on devices shipped in China, which means that Android devices in China don't support Fast Pair. Some OEMs implemented their own Fast Pair-like pairing process, but this usually only works with audio products from their own brand.
To make Fast Pair ubiquitous on Android, Google aimed to bring Fast Pair to AOSP as part of the Connectivity Mainline module. The code for Fast Pair and the HalfSheet UX (the pop-up UI that appears when a device is discovered) was uploaded to AOSP with the release of Android 13, but this code was just deleted by Google a few days ago.
I'm not entirely sure why Fast Pair was deleted from AOSP, as I don't have access to the Issue Tracker reports linked in the commit. Perhaps it saw low adoption/interest from OEMs? If you know why it was removed, send me a DM!
😢59👍14🤬11🕊3🫡3🤔2🔥1🤡1
Apparently, Google Play Services does seem to actually be available on many Android devices sold in China. However, there are some caveats to this.
OEMs are not required to bundle GMS (Google Mobile Services) with the Android builds they distribute in China. Google Play Services and Google Play Store are part of GMS and are thus not included with AOSP builds by default. No Chinese build ships the Play Store, of course, but many do include apps like Google Services Framework and even undergo GMS certification, making it easy to sideload the Google Play Store on CN models.
And as it turns out, many OEMs seem to include the Google Play Services app in China as well. This is because while many Google services are blocked in China, not every feature/API provided by Play Services requires connecting to a Google server that can be/is blocked in the country.
CN builds of ColorOS, for example, ship GmsCore under the
As I mentioned before, not every feature/API provided by Play Services is available to users in China. Things like Nearby Share and anything that relies on Google's location services won't work. CN builds declare the
With regards to my previous post on Fast Pair, I don't know if Play Services in China supports Fast Pair. Fast Pair through Play Services connects to a Google server to sync and serve certified Fast Pair device metadata, like the image and device name shown in the HalfSheet UX.
If you live in China and have an Android phone with Play Services, let me know what does/doesn't work for you!
(Thanks to @MlgmXyysd for the heads up and for sharing the unknown tracker alert screenshots!)
OEMs are not required to bundle GMS (Google Mobile Services) with the Android builds they distribute in China. Google Play Services and Google Play Store are part of GMS and are thus not included with AOSP builds by default. No Chinese build ships the Play Store, of course, but many do include apps like Google Services Framework and even undergo GMS certification, making it easy to sideload the Google Play Store on CN models.
And as it turns out, many OEMs seem to include the Google Play Services app in China as well. This is because while many Google services are blocked in China, not every feature/API provided by Play Services requires connecting to a Google server that can be/is blocked in the country.
CN builds of ColorOS, for example, ship GmsCore under the
my_bigball partition (yes, it's really called that lol.) This allows features like Google's unknown tracker alerts to be available for users in China!As I mentioned before, not every feature/API provided by Play Services is available to users in China. Things like Nearby Share and anything that relies on Google's location services won't work. CN builds declare the
cn.google.services PackageManager flag to tell Play Services what features should be enabled on the device.With regards to my previous post on Fast Pair, I don't know if Play Services in China supports Fast Pair. Fast Pair through Play Services connects to a Google server to sync and serve certified Fast Pair device metadata, like the image and device name shown in the HalfSheet UX.
If you live in China and have an Android phone with Play Services, let me know what does/doesn't work for you!
(Thanks to @MlgmXyysd for the heads up and for sharing the unknown tracker alert screenshots!)
👍53😁8🤮3❤2
Google is working on a Thread network stack for Android that will allow an Android device with a Thread radio to create a Thread network and act as a Thread Border Router. The Thread network stack is being added to the Connectivity Mainline module.
What's interesting, though, is that the Thread network service may be supported on some upcoming Android TV 14 devices, whereas for non-TV devices it'll be supported in Android 15.
However, some Googlers are hesitant to add a TV and SDK level check, as removing these checks would allow "Google and partners to enable Thread on U [Android 14] devices (such as tablets) if they backport the Thread HAL service." Apparently, some Android Partners did indeed reach out to Google asking if they can support Thread on older platforms.
Thread, by the way, is an IPv6-based wireless mesh networking technology designed for smart home/IoT devices. Thread-enabled devices join an existing home network through a Thread Border Router. Google's Nest Hub (2nd gen), Nest Hub Max, and Nest WiFi Pro can all act as Thread Border Routers.
(If you want to learn more about Thread, check out this great article on The Verge by Jennifer Pattison Tuohy.)
But with this change, this means that we may soon see devices running Android act as Thread Border Routers. Some upcoming TVs running Android TV 14 may support this, as well as some non-TV devices running Android 14 if the OEM chooses to backport the feature.
What's interesting, though, is that the Thread network service may be supported on some upcoming Android TV 14 devices, whereas for non-TV devices it'll be supported in Android 15.
However, some Googlers are hesitant to add a TV and SDK level check, as removing these checks would allow "Google and partners to enable Thread on U [Android 14] devices (such as tablets) if they backport the Thread HAL service." Apparently, some Android Partners did indeed reach out to Google asking if they can support Thread on older platforms.
Thread, by the way, is an IPv6-based wireless mesh networking technology designed for smart home/IoT devices. Thread-enabled devices join an existing home network through a Thread Border Router. Google's Nest Hub (2nd gen), Nest Hub Max, and Nest WiFi Pro can all act as Thread Border Routers.
(If you want to learn more about Thread, check out this great article on The Verge by Jennifer Pattison Tuohy.)
But with this change, this means that we may soon see devices running Android act as Thread Border Routers. Some upcoming TVs running Android TV 14 may support this, as well as some non-TV devices running Android 14 if the OEM chooses to backport the feature.
❤21👍10⚡2
Interesting: Google Play Protect will apparently soon perform real-time threat detection for newly installed "unknown" apps.
Currently, if you sideload an app that hasn't already been scanned by Play Protect, Google Play will ask you to submit the app to Google for analysis. It seems that soon, Play Protect may also perform some local analysis of the unknown app, though I don't know how/what it'll check for.
Google says that this feature will be rolling out with version 37.5 of the Play Store app. This version hasn't rolled out yet on any of my devices or APK hosting sites, so we can't see what they've bundled.
Currently, if you sideload an app that hasn't already been scanned by Play Protect, Google Play will ask you to submit the app to Google for analysis. It seems that soon, Play Protect may also perform some local analysis of the unknown app, though I don't know how/what it'll check for.
Google says that this feature will be rolling out with version 37.5 of the Play Store app. This version hasn't rolled out yet on any of my devices or APK hosting sites, so we can't see what they've bundled.
🤔45👎14👍13👀4👏3❤2
Find My Device version 3 is rolling out now to prepare for the launch of Android's Find My Device network.
A new line has been added to the page for marking a device as "lost". It reads: "
The app also has a BUNCH of new strings pertaining to new features of the Find My Device network, including the ability to temporarily share the location of devices with other people (for 24h, and optionally with only one other person), editing the contact info of accessories that others can read by tapping their phone (in case they're lost), categories of devices (bag, bike, camera, headphones, keys, etc.), set the ring volume of a device (factory default, high, low, or medium), play a sound on located trackers, view the battery level of an accessory, and more.
Also interesting is the responsible use notice:
"
Reminder: The Find My Device app just provides the UI for seeing the location of devices/sending commands. The actual Find My Device service is handled by Google Play Services. The FMDN is part of a separate Play Services module that has not been marked to roll out to users yet.
So no, updating your Find My Device app to v3 won't enable FMDN support, but it is an important step for its eventual rollout.
A new line has been added to the page for marking a device as "lost". It reads: "
Mark the device as lost to be notified if the Find My Device network locates it." The app also has a BUNCH of new strings pertaining to new features of the Find My Device network, including the ability to temporarily share the location of devices with other people (for 24h, and optionally with only one other person), editing the contact info of accessories that others can read by tapping their phone (in case they're lost), categories of devices (bag, bike, camera, headphones, keys, etc.), set the ring volume of a device (factory default, high, low, or medium), play a sound on located trackers, view the battery level of an accessory, and more.
Also interesting is the responsible use notice:
"
Google’s Find My Device helps you locate the shared device and your devices safely. The app should always be used in a responsible, safe, and legal way.
To maintain a safe experience, you must adhere to the Find My Device Acceptable Use Policy. Using Find My Device to track individuals without their consent may be a crime punishable by law. Law enforcement may request identifying information in these cases"Reminder: The Find My Device app just provides the UI for seeing the location of devices/sending commands. The actual Find My Device service is handled by Google Play Services. The FMDN is part of a separate Play Services module that has not been marked to roll out to users yet.
So no, updating your Find My Device app to v3 won't enable FMDN support, but it is an important step for its eventual rollout.
❤44👍18
The August 2023 Google Play System Update is now rolling out to Android 14 devices.
While the version number for almost every module was bumped, I don't know what's changed, since Google has yet to publish the source code for each updated Mainline release.
The ART version still reports 2.1.0, which is unchanged from before, so I'm not sure if ART 14 is included yet.
While the version number for almost every module was bumped, I don't know what's changed, since Google has yet to publish the source code for each updated Mainline release.
The ART version still reports 2.1.0, which is unchanged from before, so I'm not sure if ART 14 is included yet.
👍49❤9🤡4
Mishaal's Android News Feed
Find My Device version 3 is rolling out now to prepare for the launch of Android's Find My Device network. A new line has been added to the page for marking a device as "lost". It reads: "Mark the device as lost to be notified if the Find My Device network…
Oh neat, Find My Device v3 also finally adds a themed icon!
Left: v2.5
Right: v3
(Yes, the icon itself has been updated as well.)
If you're thinking, "wait, Find My Device already had a themed icon!" No, it didn't, at least not unless you were on a Pixel.
Left: v2.5
Right: v3
(Yes, the icon itself has been updated as well.)
If you're thinking, "wait, Find My Device already had a themed icon!" No, it didn't, at least not unless you were on a Pixel.
❤51👍20🔥7🤡6🤔2
Google has announced new apps and features for Android Auto and Android Automotive.
These include:
* WebEx by Cisco and Zoom are now rolling out with audio-only capability, so you can join scheduled meetings and conference calls from your car display. (The arrival of these apps was announced last week, but the actual rollout begins today.)
* Amazon Prime Video is now available on select cars with Google built-in (ie. cars running Android Automotive with access to Google Play). Look for it on select Renault, Polestar, and Volvo cars.
* Vivaldi browser is now available for all cars with Google built-in. Download it from Google Play.
* You'll soon be able to download the Weather Channel app through Google Play on cars with Google built-in. The app will show hourly forecasts and feature follow-me alerting and a "Trip View" radar.
* Digital car key support is now rolling out on select Hyundai, Genesis, and Kia models in the U.S., Canada, and Korea for drivers with compatible Pixel and Samsung devices such as the Pixel 7 Pro and Galaxy S23+.
These include:
* WebEx by Cisco and Zoom are now rolling out with audio-only capability, so you can join scheduled meetings and conference calls from your car display. (The arrival of these apps was announced last week, but the actual rollout begins today.)
* Amazon Prime Video is now available on select cars with Google built-in (ie. cars running Android Automotive with access to Google Play). Look for it on select Renault, Polestar, and Volvo cars.
* Vivaldi browser is now available for all cars with Google built-in. Download it from Google Play.
* You'll soon be able to download the Weather Channel app through Google Play on cars with Google built-in. The app will show hourly forecasts and feature follow-me alerting and a "Trip View" radar.
* Digital car key support is now rolling out on select Hyundai, Genesis, and Kia models in the U.S., Canada, and Korea for drivers with compatible Pixel and Samsung devices such as the Pixel 7 Pro and Galaxy S23+.
👍39❤5🔥3🤔1🤩1
Google plans to let third-party apps read the measured battery state of health, ie. the remaining estimated full charge capacity relative to the rated capacity in %, in Android 15.
Currently, this value can't be queried through the public Android SDK, as it is gated by the system-only BATTERY_STATS permission (though as I discovered a few months back, this permission can actually be granted manually through ADB).
Android 14 introduced the API for reading the measured battery state of health, but it was restricted "not due to privacy but [due] to eng[ineering]" as there weren't any "usecases [sic] where an application would require this permission." However, it seems things have changed, as there are now use cases planned for it, so they're making it publicly accessible.
Note that even if Android 15 opens it up as a public API, the data likely won't be available on every device. It may be the case that the device's battery charging IC has to be set up to report this data to Android's health HAL, which in return is read by the OS and subsequently apps calling this API.
Currently, this value can't be queried through the public Android SDK, as it is gated by the system-only BATTERY_STATS permission (though as I discovered a few months back, this permission can actually be granted manually through ADB).
Android 14 introduced the API for reading the measured battery state of health, but it was restricted "not due to privacy but [due] to eng[ineering]" as there weren't any "usecases [sic] where an application would require this permission." However, it seems things have changed, as there are now use cases planned for it, so they're making it publicly accessible.
Note that even if Android 15 opens it up as a public API, the data likely won't be available on every device. It may be the case that the device's battery charging IC has to be set up to report this data to Android's health HAL, which in return is read by the OS and subsequently apps calling this API.
👍44❤6🤡4