Direct answer
For the Google Pixel Watch 2, satellite lock, assisted data, phone-connected mode, environment and wrist settings should be separated. First, wait outdoors for a confirmed GPS lock before starting.
What this covers
- Google Pixel Watch 2 (G4TSL/GC3G8)
- Google Pixel Watch; Wear OS version, LTE versus Wi-Fi model, watch-face complications and paired-phone account state vary.
- The specific fault this record addresses: GPS distance or route is inaccurate
What it does not cover
- ×The same symptom on a different Google product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The workout started before a solid GPS lock
What separates it The route is wrong or wandering at the start and settles later, or distance is short.
How to confirm Wait outdoors, still, until the watch confirms a full GPS lock before starting; a workout begun on a partial fix records a distorted opening.
- 2
The environment is degrading the fix
What separates it Errors cluster in cities among tall buildings, under heavy tree cover, or in canyons.
How to confirm Compare the same route in the open against the problem area; multipath from buildings and signal loss under cover are environmental, not a watch fault.
- 3
The watch is using connected (phone) GPS, or the wrong GPS mode
What separates it Accuracy differs depending on whether the phone is carried, or a multi-band/accuracy mode is off.
How to confirm Choose the intended GPS source and, where available, the higher-accuracy/multi-band mode; connected GPS depends on the phone's location, and single-band is less accurate in hard environments.
- 4
Satellite prediction data is stale
What separates it Locks are slow and inaccurate after the watch has not synced in a while.
How to confirm Sync the watch so it refreshes its downloaded satellite prediction data, which speeds and sharpens the fix.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Whether the watch had a confirmed lock before the workout started.
- Whether errors cluster in a specific environment (city, forest, canyon).
- Which GPS source/mode is set, and when the watch last synced.
Wait outdoors for a confirmed GPS lock before starting
ReversibleA workout begun on a partial fix records a wrong opening segment.
Compare standalone GPS and phone-connected mode where supported
ReversibleIsolates a connected-GPS dependency from the watch's own receiver.
Sync to refresh satellite prediction data and set the accuracy mode
ReversibleStale prediction data and single-band mode both hurt the fix.
Repeat the same open-sky route to confirm
ReversibleVerifies against a route without environmental interference.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- G4TSL/GC3G8. Google Pixel Watch; Wear OS version, LTE versus Wi-Fi model, watch-face complications and paired-phone account state vary.
- Model — Pixel Watch 2
- Google's Wear OS smartwatch with Fitbit health sensors (heart rate, skin temperature, cEDA stress), a speaker/mic for calls, in Wi-Fi or LTE versions. All wearable symptoms apply, cellular on the LTE model.
- Cellular is optional (a variant)
- Wi-Fi or LTE — cellular applies only to the LTE model with a carrier plan. A Wi-Fi model relies on the phone/Wi-Fi.
- Pairs with Android
- Wear OS pairs with Android only; health data via the Fitbit app. Pairing issues are often the Android/Fitbit/Google-account step.
- Backup path
- Carries a cellular backup path for alarm signalling. Backup carries signalling, not bandwidth — so the system can report itself online and monitored while everything that needs broadband fails, and can stay in that state for weeks unnoticed.
- Symptom boundary
- This record covers Google Pixel Watch 2 when it GPS distance or route is inaccurate. A different symptom on the same hardware, or this symptom on a different Google product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Do not rely on a malfunctioning wearable as your only navigation or emergency locator — carry a phone or dedicated device for safety-critical routes.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Pixel Watch Help publishes this as "Google Pixel Watch Help". Official Pixel Watch setup, charging, sync, health-sensor and Wear OS support. What that article does not carry is the model boundary — it is written for a product line, and G4TSL/GC3G8 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My Pixel Watch 2 won't pair with my phone.+
First confirm your phone is Android — Wear OS (and the Pixel Watch) does not pair with an iPhone. Then update the phone, the Pixel Watch and Fitbit apps, sign in to the same Google account, keep both devices charged and close together with Bluetooth on, and follow the in-app pairing. If it was paired to another phone, factory-resetting it may be required, but understand that erases it — so resolve the account/app steps first. Most pairing failures are the account or an out-of-date app.
My watch gets my running distance wrong.+
The most common cause is starting before the watch has a solid satellite lock. Wait outdoors, standing still, until it confirms a full GPS fix before you begin — a workout started on a partial fix records a wandering, short first segment. Tall buildings and heavy tree cover also degrade the signal, and if the watch relies on your phone's GPS in connected mode, its accuracy depends on the phone being with you. Syncing the watch refreshes its satellite prediction data and speeds up the lock.
Does this answer apply to every Google model?+
No. It is scoped to G4TSL/GC3G8. Google Pixel Watch; Wear OS version, LTE versus Wi-Fi model, watch-face complications and paired-phone account state vary.
What should I record before troubleshooting GPS or distance?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing GPS, distance. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not rely on a malfunctioning wearable as the only navigation or emergency locator.
Answer for the exact device and software version shown above.