What you need to know

• Google is rolling out Loss of Pulse Detection to Pixel Watch 3 owners in the U.S. starting today.
• The feature, which is opt-in, will automatically check if your pulse is detected and call emergency services if it can’t be found.
• This life-saving tool will take a couple of weeks to become available for all Pixel Watch 3 users.

Google is now rolling out Loss of Pulse Detection, a new safety feature for the Pixel Watch 3, to U.S. users. The feature was originally marketed as a Pixel Watch 3 feature last year, and became available in other regions, but required FDA approval before it could work in the U.S.

Google earned that approval in February 2025, and Loss of Pulse Detection will become available in the country starting today, with a full rollout lasting a few weeks.

After earning FDA approval, the company announced Loss of Pulse Detection for U.S. users as part of the March Pixel Feature Drop. Originally, Google said it would “begin rolling it out in the U.S. at the end of March.” That deadline passed, but now the feature is shipping as of April 8, 2025.

Loss of Pulse Detection is a critical safety feature that Google explains can “detect when you’ve experienced a loss of pulse” and “automatically prompt a call to emergency services for potentially life-saving care if you’re unresponsive.” It adds a new element to Emergency SOS, which can be used to call emergency services quickly from your smartwatch.

Image 1 of 3

Loss of Pulse Detection is opt-in, so you’ll need to manually enable it when the feature becomes available on your device. To do so, open the Google Pixel Watch app on your phone and tap Safety and Emergency. Then, press Loss of Pulse Detection, and follow the on-screen prompts to enable the safety tool. After that, the feature will monitor your heart rate and try to detect when and if your pulse can’t be found.

Prior to launching in the U.S., Loss of Pulse Detection has been available in 14 countries. The feature first arrived on Pixel Watch 3 for users in the EU last year.

It’s rolling out starting today, but may take “a couple” of weeks before it arrives on all U.S. Pixel Watch 3 devices. The announcement comes as Google releases the April 2025 update for all Pixel Watch models.

BECH32 detects up to 4 errors (in the sense that creating up to 4 replacement errors guarantees that the resulting string has an incorrect checksum). However, error detection is not the same as error Positioning: Just knowing that BECH32 is wrong does not mean you can’t know where the error was made.

Bech32 is also allowed Correction Up to 2 replacement errors. This means that if you know that no more than two replacement errors have been created, you can calculate what the original valid string was for a given string. The JavaScript code on the website you link to has the code to do this, but for safety reasons it will not be revealed intentionally what Errors discovered, where.

The reason is that corrections are dangerous. If the user creates two or more replacement errors, the error correction algorithm may still find two errors to “fix” in the sense that it constructs a valid address, but It is not the user’s address. Inadvertent users may make corrections suggested by the algorithm and send funds to void. Instead, the correction algorithm is still used under the hood, but only the location of the error is revealed, forcing the user to check if it is the primary resource that received the address, but perhaps forces the algorithm to focus specifically on the specific location where the location error is likely to have occurred.