A new Google Assistant tile that lets you add commands as shortcuts is rolling out on Wear OS!
This is part of the Google Assistant app on Wear OS and is rolling out to Galaxy Watch and Pixel Watch users. You may need version 1.8.22.561 480068.release of the Google Assistant app.
Thanks to Lance Adams and winner00 for the tip/screenshots!
This is part of the Google Assistant app on Wear OS and is rolling out to Galaxy Watch and Pixel Watch users. You may need version 1.8.22.561 480068.release of the Google Assistant app.
Thanks to Lance Adams and winner00 for the tip/screenshots!
๐46๐ฅ4โค2๐1๐1
The FCC has permitted "very low power device operations in [the] 6GHz band", which the Google Pixel account on Twitter praised as "a win for Pixel users and American consumers, as this band will now be available for high-speed peer-to-peer WiFi communication."
6GHz P2P WiFi should allow for things like even faster device-to-device transfers (those of you who set up the Pixel 8 will have noticed they really discourage wired D2D transfers) and screen mirroring (though The Wi-Fi Alliance doesn't certify Miracast operation in 6GHz it seems, plus Pixel doesn't even support Miracast).
6GHz P2P WiFi should allow for things like even faster device-to-device transfers (those of you who set up the Pixel 8 will have noticed they really discourage wired D2D transfers) and screen mirroring (though The Wi-Fi Alliance doesn't certify Miracast operation in 6GHz it seems, plus Pixel doesn't even support Miracast).
The Verge
FCC greenlights superfast Wi-Fi tethering for AR and VR headsets
The decision opens up new possibilities for wireless devices.
๐ฅ37๐13๐ค3โค1
Google is disabling Nearby Share in work profiles, according to the "what's new in Google System Updates" changelog for October 2023. This is rolling out through Google Play Services version 23.41.
Nearby Share is part of Play Services, which is installed onto work profile, so presumably the Nearby Share component simply gets disabled so it doesn't appear as an option when invoking the share sheet from a work profile app.
H/T @AssembleDebug
Nearby Share is part of Play Services, which is installed onto work profile, so presumably the Nearby Share component simply gets disabled so it doesn't appear as an option when invoking the share sheet from a work profile app.
H/T @AssembleDebug
๐42๐5โค2๐2
Android's platform QR scanner, available on Android 13+ devices with GMS, is getting support for adding passes & IDs with QR codes to Google Wallet. These include things like boarding passes, driver's license, COVID cards, etc.
The platform QR scanner currently supports the following QR code types:
* App links
* Call phone number
* Connect to Wifi
* Contact cards
* Events
* Geo location
* Nearby Share
* Opening a PDF
* Passkeys
* Payments
* Sending an email
* Setting up Matter devices
* View text
* Web links
Other new additions coming to the QR scanner, according to a source, include QR filtering in the photo picker, more QR actions, automatic torch enabling in low-light conditions, and a history for scanned QR codes!
(Image credits: @AssembleDebug)
The platform QR scanner currently supports the following QR code types:
* App links
* Call phone number
* Connect to Wifi
* Contact cards
* Events
* Geo location
* Nearby Share
* Opening a PDF
* Passkeys
* Payments
* Sending an email
* Setting up Matter devices
* View text
* Web links
Other new additions coming to the QR scanner, according to a source, include QR filtering in the photo picker, more QR actions, automatic torch enabling in low-light conditions, and a history for scanned QR codes!
(Image credits: @AssembleDebug)
๐50โค4
Here's how Google (actually) addressed the spike in false 911 calls placed by Android phones.
Earlier this year, law enforcement and emergency service operators around the world saw a spike in false emergency calls being placed by Android phones.
This was blamed on Android's Emergency SOS feature, which provides a fast way to call emergency services by quickly tapping the power button 5 times.
Since Android 12, Google made it a requirement for (phone) builds to include the emergency SOS feature. It's up to OEMs whether it's on by default, though. (It's enabled by default in AOSP.)
Since Android 13, OEMs can ship either Google's Personal Safety app or their own emergency info app. Some OEMs like Nothing and Sony use Google's app, others like ASUS and Samsung do not. Emergency SOS is required either way.
The benefit of preloading Google's Personal Safety app is that it provides additional actions on top of dialing emergency services when the Emergency SOS gesture is performed. Eg. it can share info with select contacts and even record a video.
To reduce accidental activations of emergency SOS, Google pushed an update to its Personal Safety app sometime in late June that added an extra "touch & hold" confirmation step after you press the power button 5+ times. The "touch & hold" screen asks users to tap and hold the button for three seconds to initiate emergency SOS, as shown in the above image.
This "touch & hold" confirmation step is now the default experience for users setting up emergency SOS. Users who previously set up emergency SOS can switch to this mode if they want.
Remember that not every OEM uses Google's Personal Safety app, so the steps taken to address this problem will differ by device.
Earlier this year, law enforcement and emergency service operators around the world saw a spike in false emergency calls being placed by Android phones.
This was blamed on Android's Emergency SOS feature, which provides a fast way to call emergency services by quickly tapping the power button 5 times.
Since Android 12, Google made it a requirement for (phone) builds to include the emergency SOS feature. It's up to OEMs whether it's on by default, though. (It's enabled by default in AOSP.)
Since Android 13, OEMs can ship either Google's Personal Safety app or their own emergency info app. Some OEMs like Nothing and Sony use Google's app, others like ASUS and Samsung do not. Emergency SOS is required either way.
The benefit of preloading Google's Personal Safety app is that it provides additional actions on top of dialing emergency services when the Emergency SOS gesture is performed. Eg. it can share info with select contacts and even record a video.
To reduce accidental activations of emergency SOS, Google pushed an update to its Personal Safety app sometime in late June that added an extra "touch & hold" confirmation step after you press the power button 5+ times. The "touch & hold" screen asks users to tap and hold the button for three seconds to initiate emergency SOS, as shown in the above image.
This "touch & hold" confirmation step is now the default experience for users setting up emergency SOS. Users who previously set up emergency SOS can switch to this mode if they want.
Remember that not every OEM uses Google's Personal Safety app, so the steps taken to address this problem will differ by device.
๐51๐3โค2
Here's why Google walked back Android 14's work profile changes.
Back in July, I reported that Android 14 tweaked the behavior of the work profile so that when you press "pause", the OS actually pauses the profile instead of turning it off.
Google told me they made this change for 2 reasons:
1) Your notifications will be ready for you to view when you unpause the work profile (rather than getting a flood of notifications as apps sync).
2) It's easier to stay compliant with a company's update policy as apps can continue to get updates when the work profile is paused (they couldn't under the previous behavior as the work profile was off).
Some users were concerned about the potential battery implications, to which Google told me that although the work profile technically continues running in the background, apps are suspended using the same method that Digital Wellbeing uses.
Also, some users were concerned that work profile apps would continue seeing them as online, to which Google told me that the burden lies with individual app developers in determining a user's online status through the
(1/2)
Back in July, I reported that Android 14 tweaked the behavior of the work profile so that when you press "pause", the OS actually pauses the profile instead of turning it off.
Google told me they made this change for 2 reasons:
1) Your notifications will be ready for you to view when you unpause the work profile (rather than getting a flood of notifications as apps sync).
2) It's easier to stay compliant with a company's update policy as apps can continue to get updates when the work profile is paused (they couldn't under the previous behavior as the work profile was off).
Some users were concerned about the potential battery implications, to which Google told me that although the work profile technically continues running in the background, apps are suspended using the same method that Digital Wellbeing uses.
Also, some users were concerned that work profile apps would continue seeing them as online, to which Google told me that the burden lies with individual app developers in determining a user's online status through the
PM.isPackageSuspended() API or the ACTION_MY_PACKAGE_SUSPENDED broadcast.(1/2)
๐34โค1
Mishaal's Android News Feed
Here's why Google walked back Android 14's work profile changes. Back in July, I reported that Android 14 tweaked the behavior of the work profile so that when you press "pause", the OS actually pauses the profile instead of turning it off. Google told meโฆ
This change seems like a win for users and enterprises, but then with the release of Android 14 Beta 5.3, Google quietly reverted it and took down any documentation related to it. I asked Google why last month, but I never got an answer.
Apparently, though, the reason they scrapped these changes is because some third-party apps were incorrectly surfacing notifications to users when the work profile was paused. For example, a user with a Garmin watch told me that they were getting notifications forwarded to their watch even when the work profile was paused.
This is obviously problematic since in previous versions of Android, this didn't happen. In previous versions, since the work profile would fully shut down, no notifications would ever be posted, hence apps had no notifications to even intercept/forward. However, because Android 14's planned changes to the work profile mean the profile is always running, apps have to correctly implement the notification listener API to actually account for this and prevent work profile notifications from being surfaced.
(2/2)
Apparently, though, the reason they scrapped these changes is because some third-party apps were incorrectly surfacing notifications to users when the work profile was paused. For example, a user with a Garmin watch told me that they were getting notifications forwarded to their watch even when the work profile was paused.
This is obviously problematic since in previous versions of Android, this didn't happen. In previous versions, since the work profile would fully shut down, no notifications would ever be posted, hence apps had no notifications to even intercept/forward. However, because Android 14's planned changes to the work profile mean the profile is always running, apps have to correctly implement the notification listener API to actually account for this and prevent work profile notifications from being surfaced.
(2/2)
๐35๐คก2
Here's a look at the Pixel 8 Pro's temperature sensor, courtesy of iFixit's teardown of the phone.
In case you're curious, Google locked down the temperature sensor so that only trusted apps can get data from it. Apps have to hold the permission
Developer mikagetsangry decompiled the Thermometer app in an attempt to force enable the body temperature feature (which is pending FDA approval), but upon recompiling, the app becomes unable to read data from the sensor.
Digging through the app, we can see what the preset emissivity values are for each supported object type.
The
In case you're curious, Google locked down the temperature sensor so that only trusted apps can get data from it. Apps have to hold the permission
com.google.sensor.permission.FAR_INFRARED_TEMPERATURE, which is defined in the Pixel Display Service app with the protection level preinstalled|signature, so only preinstalled or Google-signed apps can hold it.Developer mikagetsangry decompiled the Thermometer app in an attempt to force enable the body temperature feature (which is pending FDA approval), but upon recompiling, the app becomes unable to read data from the sensor.
Digging through the app, we can see what the preset emissivity values are for each supported object type.
The
FOOD_ORGANIC and BEVERAGE_WATER options are set to 0.95, which are the closest to the accepted value of human skin emissivity (0.98), so if you pick either option, you might get skin temperature readings that are relatively close to accurate. Of course, it's best to wait until the sensor gets FDA approval so they can roll out the proper body temperature mode.๐44๐ฅ8
If you have an Android phone with the Personal Safety app paired with a Pixel Watch or Pixel Watch 2 running Wear OS 4, you can now turn on "multi-device location sharing".
From Google's support page: "When multi-device location sharing is turned on for your device, we will use that deviceโs location as a backup in the case you start an Emergency Share on another device, but that device can no longer share its location."
On Pixel, this toggle can be found by opening the Personal Safety app then going to Features > Emergency Sharing. You'll also need to toggle this on your watch as well.
Thanks to Telegram user anticringeclub for the tip!
From Google's support page: "When multi-device location sharing is turned on for your device, we will use that deviceโs location as a backup in the case you start an Emergency Share on another device, but that device can no longer share its location."
On Pixel, this toggle can be found by opening the Personal Safety app then going to Features > Emergency Sharing. You'll also need to toggle this on your watch as well.
Thanks to Telegram user anticringeclub for the tip!
๐36๐16๐ฅ4โค1
Instagram has finally added a themed icon on Android! This is available in version 307.0.0.0.30.
Now the only app that's missing support for this in my "Social" folder is Facebook.
H/T Omar Tosca on Threads
Now the only app that's missing support for this in my "Social" folder is Facebook.
H/T Omar Tosca on Threads
โค104๐33๐ฅฑ10๐คฎ8๐ฉ6๐ฅ4๐4๐1