Urgent.News

What's breaking now, across thousands of outlets.

Tech

What is the ‘Android Pulse’ app that just appeared in Google Play Store updates?

On Saturday morning, you might have noticed an app called “Android Pulse” appearing in the list of available Google Play updates.

What is the ‘Android Pulse’ app that just appeared in Google Play Store updates?

On Saturday morning, some users may have noticed a new app called “Android Pulse” appearing in the Google Play updates list. The app has no icon and is a first-party Google app aimed at "Defining anomalies for debugging" rather than posing any threat. Google explains that the app aids in the distribution of rules for anomaly detection in critical system resource consumption by the Android operating system and installed applications.

This service, which doesn't have an accessible interface, is designed to help with software diagnostics for the OS and any installed apps. The "critical system resource consumption" could pertain to battery, CPU, or memory usage.

The app is pre-installed on Pixel devices and is simply labeled as "Pulse" in system settings. The app icon resembles a heart rate monitor, displayed in green. APKMirror indicates that this app has been around since March, with seven previous versions. The app has been downloaded over 10 million times on the Play Store. However, today marks the first appearance of the update as a manually installable option.

It's intriguing that Google opted not to employ its dedicated System Services method to update this kind of app. In summary, "Android Pulse" is a Google app that is safe to have on your phone.

Written by urgent.news from 9to5Google's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at 9to5google.com →

More in Tech

The Crash That Only Happened in Production

The crash was intermittent, production-only, and invisible to every test I ran locally. It turned out to be a data race in code a free coding model wrote for me, and the fix was a single lock.

  • Crash discovered only in production, not during local testing
  • Intermittent data race in code generated by free coding model
  • Fix involved adding mutex to ensure safe map access

More from Saturday 22 August →