TL;DR: The WearOS 5.1 update deployed to Pixel Watch 3 in early 2026 broke sleep tracking for a large number of users — sessions either fail to record, cut off mid-night, or never sync to the Google Health app. The most consistent fix involves re-granting Health Connect permissions and exempting Google Health Services from battery optimization, both of which WearOS 5.1 silently resets during installation.

• Affected hardware: Pixel Watch 3 (41mm and 45mm)
• Problematic update: WearOS 5.1 (rolled out early 2026)
• Primary symptom: Sleep sessions missing entirely, truncated, or showing no SpO2 and REM stage data
• Root cause: Health Connect sleep permissions revoked and battery optimization re-enabled by the update’s permission reconciliation pass
• Secondary symptom: “No sleep data” in Google Health app despite wearing the watch overnight

The overview above captures the scope of the problem: it isn’t just one sleep metric that breaks, but the entire chain from sensor collection to app display. Reports surfaced on Google’s support forums and the r/WearOS community within days of the WearOS 5.1 rollout, describing everything from completely blank sleep history to nights that show only 45 minutes of “awake” time despite wearing the watch. The consistency of the failure pattern across different users and configurations pointed quickly to a systemic permission or process-scheduling change rather than isolated hardware problems.

What exactly broke in Pixel Watch 3 sleep tracking after WearOS 5.1?

Sleep tracking on Pixel Watch 3 stopped working after WearOS 5.1 because the update’s installation routine reset Health Connect permissions and re-enabled battery optimization for Google Health Services — the two conditions the sleep tracking system depends on most. Without the correct permissions, sensor data can’t be written to Health Connect. Without unrestricted battery access, the monitoring process gets suspended by Doze mode mid-night.

Sleep tracking on the Pixel Watch 3 is not a single monolithic feature — it’s a layered stack. The Health Connect API acts as the central data broker between the watch’s on-device sensors and the Google Health app on your paired phone. When WearOS 5.1 performs its permission reconciliation pass during installation, the sleep session write permission for Google Health Services frequently gets dropped. Without that write permission, the watch’s sensors can still collect data locally, but nothing flows through to the Health app you check in the morning.

The SpO2 problem runs deeper. The Pixel Watch 3’s blood oxygen sensor requires the Body Sensors permission at two separate layers: at the watch OS level, and within Health Connect on the paired Android phone. WearOS 5.1 tightened background sensor access as part of its Android 15-derived battery management changes, which means Body Sensors permission now needs explicit re-granting post-update even if it was correctly configured before. Many users didn’t realize they needed to touch phone-side settings to restore a watch feature.

The REM and sleep stage breakdown is the third failure point. Sleep staging relies on continuous accelerometer and heart rate data processed by an on-device model. If Health Services is battery-optimized and Android’s Doze mode suspends it during a long stretch of stillness — which describes every normal sleep session — the model doesn’t accumulate enough samples to classify stages. You get a session boundary recorded (start time, end time, total duration) but the interior is blank.

The Reddit thread snapshot above shows how uniform the user experience was: nearly every top comment describes the same sequence — update completes, wake up, open Health app, see nothing. The upvote distribution on proposed fixes is useful data in itself: re-granting Health Connect permissions consistently draws the highest engagement as a confirmed solution, while suggestions to reinstall the Pixel Watch app attracted much lower counts, signaling it doesn’t reliably address the root issue.

What causes the WearOS 5.1 sleep tracking bug specifically?

The pixel watch 3 wearos sleep tracking bug is caused by two independent changes in WearOS 5.1 that compound each other: the OS update resets battery optimization settings for health services to “optimized” (from the previously configured “unrestricted”), and it clears sleep-related write permissions in Health Connect without notifying the user. Either issue alone would degrade tracking; together they reliably break it.

WearOS 5.1 inherited Android 15’s stricter approach to background process management. During a major OS update on WearOS, the platform performs a permission audit — it checks every app’s declared permissions against the new policy baseline and revokes entries that don’t match updated requirements without prompting the user. This behavior is by design for security; the problem is that Health Connect permissions for health data types like sleep sessions are treated as sensitive enough to require explicit re-consent after certain OS-level changes, and users have no way of knowing this happened unless they go looking.

The battery optimization reset is the more insidious piece. Android’s Doze mode is aggressive: when the screen is off and the device is stationary, it progressively suspends background processes. For most apps, this is fine. For a health monitoring process that needs to sample heart rate and accelerometer data every 30 seconds across an 8-hour sleep window, even a 5-minute Doze suspension can create gaps that break stage detection. Google Health Services was previously configured as unrestricted on most Pixel Watch 3 units because Google’s own setup flow exempts it. WearOS 5.1’s update process doesn’t preserve that exemption.

The breakdown chart above quantifies which failure mode is most prevalent across affected users. Missing sleep sessions entirely is the dominant outcome — around half of affected users see nothing in the Health app the morning after the update. Incomplete sessions (present but missing REM/deep stage data) account for the next largest group. The SpO2-only failure, where total sleep records fine but overnight blood oxygen readings are absent, affects a smaller but still significant portion. Knowing which failure you’re experiencing helps you confirm that your fix actually worked rather than just partially fixed the issue.

How do you fix Pixel Watch 3 sleep tracking after the WearOS 5.1 update?

Re-granting Health Connect permissions and setting Google Health Services to unrestricted battery use resolves the pixel watch 3 wearos sleep tracking bug for most users. Work through the steps below in order — each one addresses a distinct layer of the failure stack, and you may find an earlier step resolves things fully without needing the later ones.

Step 1 — Re-grant Health Connect permissions on your phone. Open the Health Connect app on your Android phone. You can find it under Settings > Health Connect, or search for it directly in Settings. Tap “App permissions”, locate Google Health Services in the list, and verify that “Sleep” and “Body measurements” both show as Allowed. If either shows as Not Allowed, tap it and grant full permission. Repeat this check for the Google Health app if you use it as your primary sleep dashboard.

Step 2 — Disable battery optimization for Google Health Services on your phone. Go to Settings > Apps > See All Apps, find Google Health Services, tap “Battery”, and set the usage to “Unrestricted”. This is distinct from the Health app itself — it’s the background service that coordinates data collection. Without this, Doze mode will suspend the very process that writes sleep data overnight.

Step 3 — Check watch-side permissions independently. On the Pixel Watch 3 itself, navigate to Settings > Privacy > Permissions. Confirm “Body sensors” is granted to Health Services. WearOS 5.1 separates watch-side permissions from phone-side permissions, so both need to be correct. It’s easy to fix only one and wonder why tracking is still broken.

Step 4 — Set battery to unrestricted on the watch as well. On the watch: Settings > Apps, locate Health Services, tap Battery, and set to Unrestricted. The watch has its own power management that’s independent of the phone’s settings. Both sides need to be exempted from Doze.

Step 5 — Restart the watch before your next sleep session. Hold the crown button, select Restart. Give the watch about 10 minutes after restarting before putting it on so background services can re-initialize fully. Don’t pair this step with a phone restart unless you’ve done steps 1–4 first — restarting without fixing permissions achieves nothing.

If tracking is still broken after two nights: Clear the cache for Google Health Services on your phone (Settings > Apps > Google Health Services > Storage > Clear Cache). A corrupted cache from the update process occasionally prevents the service from writing new data even with correct permissions. A factory reset of the watch is rarely necessary and should only be attempted if cache clearing also fails.

How to confirm the fix actually worked

Don’t wait until morning to discover whether the fix took. After restarting the watch and confirming permissions, put the watch on and keep it on for at least 30 minutes while sitting still. Open the Google Health app and check whether “Today’s activity” is updating with heart rate readings. If heart rate is recording in near real-time, Health Services has the permissions and battery access it needs — sleep tracking will work overnight. If heart rate shows no recent data despite wearing the watch, one of the permission or battery steps above didn’t apply correctly and needs to be revisited.

The radar chart above compares Pixel Watch 3 sleep tracking across six performance dimensions before the WearOS 5.1 update, immediately after the update (broken state), and after applying the permission and battery fixes. Session detection and sleep stage accuracy recover to near pre-update baseline after the fix. SpO2 overnight readings show the slowest recovery — the blood oxygen sensor’s baseline calibration needs one or two full sleep cycles to re-establish accurate readings after Health Services restarts cleanly. If your first post-fix night shows slightly off SpO2 numbers, that’s expected and self-corrects.

Which Pixel Watch 3 sleep features are most affected?

The sleep staging algorithm is the most fragile feature under the WearOS 5.1 regression because it requires continuous background sensor access across the entire sleep window. A single Doze suspension during a deep sleep phase can break the model’s ability to classify that phase correctly, since the accelerometer and heart rate data streams are interrupted. Users often see a total sleep duration that looks plausible while every stage breakdown shows zero.

SpO2 overnight monitoring ranks second in fragility. The Pixel Watch 3 samples blood oxygen at intervals through the night rather than continuously (to balance accuracy against battery drain). If Health Services is suspended, those sampling intervals are skipped entirely. A night with only 3–4 valid SpO2 readings instead of 15–20 will either show no SpO2 data in the Health app or display an “insufficient data” message.

Sleep session boundaries — the start and end times — are the most resilient part of the system. Detection relies on a combination of movement drop, heart rate decrease, and device orientation that can sometimes complete even with background restrictions in place. This explains the common user report of seeing a sleep session recorded but with no staging data inside it: the session shell exists, but the content never populated.

Snore detection and sleeping heart rate trend are lower-priority features that depend on the same background access as staging. Both break in the same scenario, though most users notice absent stages before they notice absent snore data.

Is this a known issue Google has acknowledged?

Google has not published a formal advisory naming the WearOS 5.1 sleep tracking regression as of April 2026. User-filed reports on the Google Issue Tracker for Wear OS document the pattern in detail, and the Pixel Watch community forum contains multiple threads confirming the same fix sequence. Google’s official support responses in those threads recommend re-granting permissions and adjusting battery settings — which is consistent with the permission-reset root cause — without explicitly calling it a regression in the update.

There is no confirmed patch release date. The permission reset behavior appears tied to WearOS 5.1’s installation-time reconciliation logic rather than an ongoing runtime issue, so a fix would need to address either how the update migrates existing permission states or add a post-update prompt asking users to reconfirm health data access. Until a patch ships, the manual five-step fix above addresses the issue for the vast majority of affected devices. If you want to track whether a patch is in progress, searching the Google Issue Tracker for “Wear OS sleep health connect” surfaces the active threads where status updates from Google occasionally appear.

References

• Health Connect permissions and data types — Android developer documentation — Covers how Health Connect manages per-data-type permissions including sleep sessions and body sensors; directly explains the permission model that WearOS 5.1 resets.
• Wear OS Help Center — Official documentation for WearOS features, battery management settings, and troubleshooting steps referenced in the fix steps above.
• Google Issue Tracker — Google’s public bug tracker for Android and WearOS; searching “Wear OS sleep tracking” surfaces user-filed regressions and any official Google responses confirming acknowledgment of the issue.
• Google Pixel Watch Help Center — Official device support documentation including health tracking setup, permission requirements, and known issues for the Pixel Watch 3.