Wear OS phone GPS workouts: battery savings explained
Wear OS watches can now track outdoor workouts using a paired phone's GNSS receiver instead of burning through the watch's own, according to a Google Play Services v26.45 update reported this week (The Verge; Digital Trends). The feature runs on a simple trade: the watch switches off its own satellite receiver and leans on the phone's, which has a much bigger battery to spend on the job (The Verge).
Two conditions are already confirmed. The phone has to physically go with you on the workout, and the feature only works when the phone isn't in Battery Saver mode (Digital Trends; TechRadar).
What's less settled is just as important: which Wear OS watches actually support phone-assisted GNSS tracking hasn't been published anywhere yet. Here's what's locked in about this Wear OS phone GPS workout feature, and what still needs verification before anyone builds a routine around it.
How Wear OS watches use your phone's GPS during workouts
The capability showed up in Google Play Services v26.45, dated November 16, 2026, and was reported as live the following day (Digital Trends; TechRadar). Play Services updates are typically installed automatically, though Google hasn't said which devices are eligible for this specific feature or on what timeline (TechRadar).
Google calls it GNSS rather than GPS on purpose. GNSS is the umbrella term for satellite positioning generally, covering GPS, Galileo, GLONASS, and NavIC rather than just the U.S.-built GPS constellation (Digital Trends; TechRadar).
This isn't a new idea industry-wide. Fitbit already runs a comparable feature called Dynamic GPS on select trackers, so Wear OS is catching up to an approach Google's own fitness brand has used for a while (Digital Trends). The bigger point for current owners: this arrives as a software update, not a new watch model or a hardware refresh you'd need to buy into.
When Wear OS phone GPS workouts save battery, and when they don't
Keeping a watch's onboard GNSS receiver running for a full outdoor session is one of the most power-hungry things a smartwatch does, which is a real problem given how small watch batteries are next to phones (TechRadar). For a sense of scale, one Android Central reviewer testing the Pixel Watch 4's own onboard GPS, before this update existed, measured roughly 7.5% battery used per hour on standard runs, climbing to nearly 12% per hour over a 19-mile run (Android Central). That's a single reviewer's result on one watch model using onboard GPS only, not a benchmark for what phone-assisted GNSS will save, but it shows the scale of the problem Google is trying to solve.
The people most likely to benefit are runners, hikers, and endurance athletes on long GPS-heavy sessions who already carry their phone and want their watch to have something left for the rest of the day (Digital Trends). Anyone who deliberately leaves the phone at home to go phone-free gets nothing from this: the feature simply can't run without the phone present (TechRadar).
This is a battery trade, not a battery discount. The GNSS workload moves from the watch to the phone, and the phone's battery absorbs that added drain instead of the drain disappearing entirely (TechRadar; Digital Trends).
Wear OS phone GNSS requirements and compatibility: what's confirmed, what's not
Confirmed:
- The phone must be carried during the workout (TechRadar; Digital Trends)
- The feature only works when the phone isn't in Battery Saver mode (TechRadar)
- The feature is part of Google Play Services v26.45 (Digital Trends)
Not yet documented:
- Which specific Wear OS watches support it, a list Google hasn't published (Digital Trends)
- How widely it's supported across different manufacturers and models (Digital Trends)
- Whether it activates automatically or needs a manual toggle, and whether behavior differs between Google Fit, Fitbit, and third-party workout apps
None of the reports covering this launch address that last point, so it's not safe to assume a specific app is covered just because Play Services is current. Having v26.45 installed confirms the capability exists somewhere in the system. It doesn't confirm it's active on a given watch or inside a given app.
What to check before you rely on it
Play Services updates generally install on their own, but owners can use Settings > Google > All services > System services > Google Play services to check for and manually trigger an update if needed, keeping in mind that menu paths can vary slightly by phone (TechRadar).
Beyond that, the reports covering this rollout don't include independent test numbers: no measured watch-battery savings per hour, no figure for the added drain on the phone, and no accuracy comparison against onboard GNSS (TechRadar; Digital Trends). Words like "substantial" and "noticeable" in the early coverage describe the concept's potential, not a stopwatch-and-battery-meter result.
There's also no word on what happens if the watch and phone briefly lose their Bluetooth connection mid-run. The sources covering this launch don't say whether the watch automatically switches back to its own onboard GNSS or just stops tracking until the link returns.
What to do now
The reported facts are specific enough to act on carefully: Play Services v26.45 adds phone-assisted GNSS for Wear OS outdoor workouts, it requires carrying the phone with Battery Saver off, and it mirrors the logic behind Fitbit's existing Dynamic GPS feature (Digital Trends; TechRadar).
Compatible watch models, how the feature gets activated, and real-world battery numbers haven't been published by Google or tested independently as of this week. Anyone who regularly brings a phone on long runs or hikes can confirm their Play Services version is current and keep an eye out for an official compatibility list, but there's not yet enough evidence to count on this for all-day battery planning or to change a workout routine around it.
Comments
Be the first, drop a comment!