Direct answer
For the Google Pixel Watch 2, watch storage, Bluetooth/internet, app permission, account/cloud and service state should be isolated. First, open the official app and note last sync/error.
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: will not sync activity or data
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 Bluetooth link to the phone has stalled
What separates it The watch is connected but the last-sync time is old, or sync spins and never completes.
How to confirm Toggle Bluetooth off and on, bring the watch close to the phone, and open the app to force a sync; a stalled link is the most common and most harmless cause.
- 2
The app lacks a background or permission it needs
What separates it Data syncs only when the app is open in the foreground, not in the background.
How to confirm Grant the app background-app-refresh, Bluetooth and (where used) location permissions; without them the phone stops the app from syncing in the background.
- 3
The account or cloud service is the block
What separates it The watch reaches the phone but data does not appear in the app or online, or a sign-in is expired.
How to confirm Confirm the correct account is signed in and the service is up; a signed-out or wrong account means the data has nowhere to land.
- 4
The phone has no internet for the cloud step
What separates it Bluetooth sync to the phone works but the app's online history is stale.
How to confirm Confirm the phone has a working internet connection so the app can upload to the account after receiving from the watch.
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.
- The last-sync time and any error the companion app shows.
- Whether it syncs only in the foreground (a background-permission problem).
- Whether the correct account is signed in and the phone has internet.
Open the app and note the last sync time and any error
ReversibleTells you whether the break is at the watch, the phone, or the cloud.
Toggle Bluetooth, bring the watch close, and force a sync
ReversibleClears a stalled link, the most common cause.
Grant background, Bluetooth and network permissions before reinstalling
ReversibleMissing background refresh stops background sync silently.
Create one test activity and confirm it appears in the app
ReversibleVerifies the full path from watch to account.
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 will not sync activity or data. 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.
- !Preserve unsynced health and activity data before any reset or account removal — that data exists only on the watch until it transfers, and a reset erases it permanently.
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 is connected but my activity isn't showing up in the app.+
Start with the simplest cause: toggle Bluetooth off and on, bring the watch next to the phone, and open the app to force a sync — a stalled link is usually all it is. If it only ever syncs while the app is open on screen, the app is missing background-refresh or Bluetooth permission, so grant those. And confirm the right account is signed in and the phone has internet, since the app has to upload to your account after it receives the data from the watch. Do not reset the watch, which would erase any data that has not synced yet.
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 not syncing or activity?+
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 not syncing, activity. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Preserve unsynced health/activity data before reset or account removal.
Answer for the exact device and software version shown above.