Troubleshooting
Galaxy Watch steps not syncing: how to fix it (2026 guide)
Your Galaxy Watch counts steps on the wrist, but Samsung Health or another app doesn't see them? The problem has precise causes — it's not magic. This guide takes you from diagnosis to solution in order of probability, without wasting time on wrong fixes.
Published May 22, 2026
You've walked 8,000 steps today — you can see it on the Galaxy Watch, on the wrist display, everything looks fine. Then you open Samsung Health on your phone and find 2,000 steps, or zero, or yesterday's number that hasn't updated. This is one of the most frequent problems among Galaxy Watch users, and has different solutions depending on exactly where the sync chain breaks. Let's run diagnostics in the right order.
First of all: understand where the chain breaks
The path of steps from Watch to phone goes through multiple steps. Each can be the breaking point:
- The Watch counts steps via accelerometer.
- Watch data is transmitted via Bluetooth to Samsung Health on the phone.
- Samsung Health processes and stores the data.
- (Optional) Samsung Health writes steps to Health Connect.
- (Optional) A third-party app reads steps from Health Connect.
The first question to ask yourself is: are the steps on the Watch but not on Samsung Health, or are they missing from Health Connect too? This distinguishes a Watch→phone sync problem from an app permissions problem.
Cause 1: Bluetooth disconnected or unstable connection
Step synchronization happens via Bluetooth between Watch and phone. If the connection is absent or intermittent, data doesn't arrive in real-time — but usually syncs as soon as the connection is re-established. If steps are completely missing even after the Watch has been near the phone for hours, Bluetooth is almost never the main cause.
- Verify the Watch is paired and connected: in the Galaxy Wearable app, status should be 'Connected'.
- If connection is unstable, try forgetting the Bluetooth device and re-pairing.
- Restart both Watch and phone — fixes most temporary connection problems.
Cause 2: Samsung Health in background is killed by the system
This is the most frequent problem on Android 12+ and Galaxy phones with aggressive battery optimization. The Android system 'suspends' or kills Samsung Health when in background to save battery, preventing it from receiving data from the Watch. Result: the Watch has the data, but Samsung Health never received it.
- Go to Settings → Apps → Samsung Health.
- Tap 'Battery'.
- Select 'Don't optimize' (or 'Unrestricted' on some One UI versions).
- Repeat the same for the 'Galaxy Wearable' app.
- Restart the phone and let the Watch sync for at least 10 minutes with the phone screen on.
Cause 3: Health Connect doesn't receive steps from Samsung Health
If steps are correct in Samsung Health but missing from Health Connect (or apps reading from HC), the problem is in permissions between Samsung Health and Health Connect. This is a separate problem from the Watch→Samsung Health sync.
- Open Samsung Health → Settings (gear icon top right) → Data management → Health Connect.
- Verify that sync with Health Connect is enabled.
- In the data types list, check that 'Steps' (and other data you want) is checked.
- If there's no Health Connect entry in Samsung Health, update Samsung Health from the Play Store — the feature was added around version 6.20.
- Open Health Connect → App permissions → Samsung Health: verify it has write permission for 'Steps'.
Cause 4: third-party app doesn't have permissions in Health Connect
If the problem concerns a third-party app (not Samsung Health) that doesn't see steps, the cause is almost always one thing: the app doesn't have read permission on Health Connect. Each app must receive permission explicitly.
- Open Health Connect → App permissions.
- Find the app in question in the list.
- Expand and verify that 'Steps' has read permission enabled.
- If the app doesn't appear in Health Connect, it means it hasn't yet requested authorization: open the app itself and look in settings for an entry like 'Connect Health Connect' or similar.
Cause 5: historical data isn't retroactively synced
If you've just set up Health Connect or just granted permissions to an app, you might notice that data from the past days or weeks doesn't appear. This is expected: neither Health Connect nor most third-party apps retroactively sync data that predates the authorization. They can only read what was written to Health Connect after permission was granted.
Cause 6: outdated firmware or app version
Samsung has fixed several sync bugs in Galaxy Watch firmware and newer versions of Samsung Health and Galaxy Wearable. If you're using outdated versions, some sync problems may have already been fixed in an update.
- Update Samsung Health from the Play Store.
- Update Galaxy Wearable from the Play Store.
- Check Watch firmware updates: in Galaxy Wearable app → Watch name → Watch software update.
- Update Health Connect from the Play Store (on Android 12-13) or verify it's updated via Settings (on Android 14+).
Emergency fix: clear Samsung Health cache
If none of the above solutions work, a corrupt Samsung Health cache can cause abnormal behavior. Note: clearing the cache doesn't delete historical data (that's in the database), but resets temporary configurations.
- Go to Settings → Apps → Samsung Health → Storage.
- Tap 'Clear cache' (NOT 'Clear data' — that would delete local data).
- Reopen Samsung Health and let it reconfigure.
- Wait 10-15 minutes with Watch connected — recent data should arrive.
Frequently asked questions
Steps on Galaxy Watch are correct but Samsung Health shows a different number: why?+
The most likely causes are two. First: Samsung Health was suspended in the background by the operating system and lost sync data in that window. Solution: disable battery optimization for Samsung Health and Galaxy Wearable (Settings → Apps → battery → Don't optimize). Second: there's a timezone mismatch between Watch and phone — verify both use the same timezone and the Watch is set to automatic time.
Samsung Health isn't syncing steps to Health Connect even after enabling permission: what do I do?+
Try this sequence: 1) In Samsung Health → Settings → Data management → Health Connect, disable and re-enable sync. 2) Revoke all Samsung Health permissions in Health Connect, then go back to Samsung Health → Settings → Health Connect and follow the authorization flow again. 3) Update Samsung Health to the latest available version on the Play Store. If the problem persists, your Samsung Health version might have a bug — check official Samsung forums for version-specific solutions.
After resetting the Galaxy Watch steps no longer sync: how do I restore?+
A Watch reset requires repeating the entire pairing procedure. Open Galaxy Wearable, add the Watch, then re-authorize Samsung Health → Health Connect. After reset the Watch is like new — it has no memory of the previous connection. Let Samsung Health and Galaxy Wearable fully reconfigure (may take 15-30 minutes) before concluding there's a problem.
Data from previous days doesn't appear in Health Connect: can I recover it?+
Generally no, not automatically. Health Connect doesn't retroactively sync data that predates authorization. Historical data remains in Samsung Health's database. Some apps allow manually importing a Samsung Health export (CSV or JSON format), but it depends on the specific app. If you need historical data, Samsung Health remains where it lives.
Galaxy Watch counts steps twice: once in the Watch and once in the phone. How to fix it?+
This happens when Samsung Health detects both the Watch sensor and the phone sensor (accelerometer) as step sources. The solution is to set the Galaxy Watch as the priority source: in Samsung Health → Settings → Connected devices → Galaxy Watch, verify it's set as the primary source for steps. Alternatively, disable direct phone step detection: Samsung Health → Settings → Permissions → Physical activity, and ensure steps are only read from the Watch.
Disclaimer
FitMesh Sync is an independent product. Samsung, Google are trademarks of their respective owners. This article implies no affiliation or sponsorship.
Medical disclaimer
The information in this article is for informational purposes only and does not replace advice from your physician, pharmacist or healthcare professional. FitMesh Sync is a fitness/wellness app, not a medical device, and does not diagnose or treat any conditions. For symptoms, clinical questions or treatment decisions always consult your primary care physician.
Written by
Matteo Pizzi
Founder & Solo Dev, FitMesh Sync · Fosforonero
Italian software developer. I built FitMesh Sync to fill the gap between my smartwatch and a real personal dashboard. Privacy-first, indie, EU servers.
More about the projectKeep reading
Comparison
Health Connect vs Samsung Health: differences and when to use which in 2026
Not competitors. They work together. But it matters to understand who does what so you don't disable the wrong one.
Guide
How Health Connect works: the complete guide for Android
Health Connect is not just an app: it's the data exchange layer that lets all Android health apps communicate. Here's what it actually does, how it manages your permissions, and what happens when something doesn't work.
Guide
The complete guide to wearable sync in 2026
Three standards coexist, ten brands each push their own cloud, one practical rule to save time: pick the data pipe before the gadget.