Urgent.News

the world's headlines, one feed

Editions

Tech

Your Wear OS smartwatch could soon show your workout route more accurately

New Google Play Services update aims to make your smartwatch more useful for outdoor workouts.

Your Wear OS smartwatch could soon show your workout route more accurately

Google has unveiled v26.31 of Google Play Services, a software update that promises to enhance the accuracy of workout routes displayed on Wear OS smartwatches. The new version will process location data server-side, potentially providing more reliable route information for users engaging in activities like running, walking, or cycling.

Interestingly, this update also introduces the ability to access app details directly from the Play Store’s “Top Charts” page on Android tablets and foldables. This developer-oriented feature could streamline the process of discovering and exploring new applications.

However, it’s important to note that Wear OS smartwatches without cellular connectivity will primarily benefit from this update once they regain connection to Wi-Fi or the user’s smartphone. This limitation suggests that the improved route accuracy will be most noticeable for users who maintain an active internet connection on their devices.

Written by urgent.news from Android Authority's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.

Read the original at androidauthority.com →

More in Tech

Government Fast-Tracks Honam Semiconductor Cluster

The government has unveiled a detailed blueprint to complete the first phase of a semiconductor fab, the core facility of the Honam semiconductor cluster, by 2029.

  • South Korea aims to complete Honam semiconductor cluster's first fab by 2029.
  • Gwangju military airport relocation and site securing expedite construction timeline.
  • Government invests 5 trillion won in semiconductor ecosystem and infrastructure.

Docker BuildKit Cache Setup That Actually Speeds Up CI

Originally published on kuryzhev.cloud Last month a client asked me why their "cached" Docker builds still took nine minutes on every single pull request.

  • Docker BuildKit cache setup was failing due to stale :latest tag usage.
  • BuildKit cache computes digest based on base image, copied files, and resolved command.
  • Optimize CI cache by ordering Dockerfile layers and using pinned FROM digests.