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
Mishaal's Android News Feed
Photo
Facebook also now has a themed icon on Android, starting with version 439.0.0.0.30 (alpha)!
Thanks to White_Eagle_ on Telegram for the tip!
Thanks to White_Eagle_ on Telegram for the tip!
👍87🤯20🤡15🤮9❤7🆒4😱3🤬2👎1
Call Screen on Pixel is rolling out a new dialer chip that let you quickly respond to phone calls to see if they're urgent, without having to actually answer the phone.
eg. here, a tipster got a call from their mom, and the dialer screen showed a "ask if urgent" chip that would initiate Call Screen to ask if the call is urgent (always answer calls from your mother, folks)
This seems to have rolled out with the launch of the Pixel 8 series, based on user reports, but my tipster (Anh on Discord) saw this on their Pixel Fold.
My guess is that you'll get "ask if urgent" when you receive a phone call from a contact, otherwise the standard "screen call" will appear.
eg. here, a tipster got a call from their mom, and the dialer screen showed a "ask if urgent" chip that would initiate Call Screen to ask if the call is urgent (always answer calls from your mother, folks)
This seems to have rolled out with the launch of the Pixel 8 series, based on user reports, but my tipster (Anh on Discord) saw this on their Pixel Fold.
My guess is that you'll get "ask if urgent" when you receive a phone call from a contact, otherwise the standard "screen call" will appear.
👍57🔥13🤡10👏3❤2
Google has announced that Play Games on PC now has over 3,000 games, which now includes the massively popular Clash of Clans and Clash Royale.
Also new is:
* An "All Games" section with a search bar
* Support for game controllers including Xbox Series S|X, Xbox One, PS5 DualSense, and PS4 DualShock. Requires game support.
* 4K screen resolution support, along with the ability to select from a list of supported screen resolutions in-game by pressing Shift + Tab.
Also new is:
* An "All Games" section with a search bar
* Support for game controllers including Xbox Series S|X, Xbox One, PS5 DualSense, and PS4 DualShock. Requires game support.
* 4K screen resolution support, along with the ability to select from a list of supported screen resolutions in-game by pressing Shift + Tab.
🔥49👍16🤡8❤4
The Google Play Games on PC developer emulator is now available for anyone to download. This developer-focused build lets you deploy games via ADB sideloading, adjust some graphics and hardware settings, and more. There are two tracks to pick from: Stable and Beta.
The developer emulator build was announced back in March during the Google for Games Developer Summit but was only open to approved developers who filled out a form.
The developer emulator build was announced back in March during the Google for Games Developer Summit but was only open to approved developers who filled out a form.
👍51❤11🤡3