Fixing “Health Connect” Sync Issues on Android 16

When your smartwatch or fitness ring stops sending steps, sleep, or workouts to other apps on Android 16, the bottleneck is almost always Health Connect—Android’s built-in health data hub. Because Android 16 routes wearable data through system-level permissions rather than older legacy app links, a single missing Read/Write toggle, background battery restriction, or outdated Play system component can silently break sync across all your fitness apps. Auditing Health Connect’s access logs and permissions shows you which app broke the chain and gets data flowing again.

Quick Answer

Open Android Settings, search for Health Connect, and check App permissions and Recent access to see which app is failing to read or write. Turn on every required permission toggle, set your wearable app’s battery usage to Unrestricted, and install pending Google Play system and app updates.

What Is Actually Happening on Android 16

Unlike earlier Android setups where apps talked directly to Google Fit APIs, Android 16 uses Health Connect as a central on-device vault built directly into the operating system.

Your wearable app (such as Samsung Health, Fitbit, Oura, WHOOP, or Strava) writes metrics into Health Connect, and your destination apps (such as Google Fit, MyFitnessPal, or calorie trackers) read those metrics out of Health Connect.

Sync fails in this pipeline for four common reasons:

  1. Asymmetric Read/Write permissions: One app has permission to write sleep, yet the receiving app lacks permission to read sleep (or vice versa).
  2. Legacy app setups: An older fitness app or companion app is still pointed at retired Google Fit sync toggles instead of Health Connect.
  3. Android 16 battery restrictions: Adaptive Battery or sleep-app limits put your wearable app to sleep before it finishes writing new batches to Health Connect.
  4. Outdated Health Connect system module or app versions: Health Connect receives updates through Google Play system updates; a mismatch between an updated app and an older system module can stall transfers.

How to Tell Which Side Is Failing (Using “Recent Access”)

Health Connect includes a built-in diagnostic log that takes the guesswork out of troubleshooting:

  1. Open Android Settings and use the top search bar to search for Health Connect (typically found under Security & privacy > Privacy controls > Health Connect or Apps > Health Connect).
  2. Tap Recent access.
  3. Check the timestamps next to your wearable app and your receiving app:
    • Your wearable app hasn’t accessed Health Connect recently: The wearable app isn’t writing data into the hub (check its internal sync, permissions, or battery limits).
    • Your wearable app wrote data minutes ago, yet your destination app shows nothing: The destination app isn’t reading from Health Connect (check its Read permissions or API login).

What to Do First to Fix Health Connect Sync on Android 16

Work through these four steps in order before uninstalling apps or resetting your watch.

1. Audit Every App’s Read and Write Permissions

  1. Inside Health Connect, tap App permissions.
  2. Tap your wearable app (such as Fitbit, Oura, Samsung Health, or WHOOP) and make sure Allow all—or all needed Write categories like Steps, Sleep, Heart Rate, and Exercise—are turned On.
  3. Go back to App permissions, tap your receiving app (such as Google Fit, MyFitnessPal, or Strava), and verify the matching Read toggles are turned On.
  4. Also open your wearable app’s own Settings > Connected Apps / Data Sharing menu and confirm Health Connect is actively linked there.

If permission toggles look stuck or grayed out after an OS update, follow How to Reset the “Health Connect” Permission Hub on Android 16.

2. Force a Manual Foreground Sync

Health Connect does not pull data on a rigid timer if the source app hasn’t written anything yet. Open your wearable app first, pull down to sync your watch or ring, wait a moment, and then open the receiving app. For step-by-step refresh triggers, see How to Manually Force a “Health Connect” Sync for Missing Android Data.

3. Remove Battery Optimization From Your Wearable App

Android 16 aggressively suspends background services when your phone sits idle.

  1. Go to Settings > Apps and tap your wearable’s companion app.
  2. Tap App battery usage (or Battery).
  3. Switch it to Unrestricted so Android does not kill background Health Connect writes.

If your wearable also drops its Bluetooth connection whenever the phone locks, check Why Your Smartwatch Disconnects When Your Phone Screen Turns Off.

4. Update Google Play System and All Connected Apps

  1. Open the Google Play Store and update both your wearable app and your destination fitness apps.
  2. Go to Settings > About phone > Android version > Google Play system update (or Settings > Security & privacy > System & updates > Google Play system update) and install any pending update, then restart your phone.

What to Check If Data Still Won’t Sync—or Duplicates

If permissions are enabled and apps are updated yet numbers still look wrong or incomplete:

When to Escalate

If Recent access shows zero activity from an app even after resetting Health Connect permissions, enabling Unrestricted battery, and reinstalling the companion app, check the app developer’s release notes—some legacy fitness apps temporarily lose Health Connect compatibility right after major Android releases until the developer ships a patch.

Bottom Line

Use Health Connect’s Recent access log on Android 16 to pinpoint which app stopped talking, verify both Read and Write toggles, set your wearable app’s battery mode to Unrestricted, and install any pending Google Play system updates.