Pixel Watch 3 Sleep Tracking Broken by WearOS 5.1: Fix Guide
The WearOS 5.1 update that rolled out to Pixel Watch 3 owners earlier this year broke sleep tracking for a large number of users, and Google had not published a formal advisory or confirmed a patch timeline as of last month, Android Digest reported. The fix, confirmed across user reports, is straightforward: re-grant Health Connect permissions and remove battery optimization restrictions on both the phone and the watch.
Both the 41mm and 45mm Pixel Watch 3 models are affected. The failure pattern is consistent enough that Android Digest described nearly every top comment in user discussions as following the same sequence: update completes overnight, user opens Google Health in the morning, sleep record is gone.
Three distinct failure modes are documented. Around half of affected users see no sleep session at all. A smaller but still significant group finds sessions present but stripped of REM and deep-stage breakdowns. A third group sees total sleep recorded normally but overnight SpO2 readings missing, per Android Digest. Which symptom you have determines where to start the fix.
The reporting below draws from Android Digest's investigation published last month. Google has not confirmed the root cause, and the technical explanation that follows reflects the best working theory from available evidence, not a confirmed postmortem.
The fix: matching your symptom to the right starting step
Re-granting Health Connect permissions and setting Google Health Services to unrestricted battery use resolves the issue for most affected devices, Android Digest reported. Both the phone and the watch need to be checked; users who address only one side frequently find the problem returns.
Start at the step that matches your symptom:
- No sleep session recorded at all: start at Step 1
- Session recorded but REM and deep-stage data are missing: start at Step 2
- Sleep records appear normally but overnight SpO2 readings are absent: start at Step 3
Step 1: Restore Health Connect permissions on your phone
Open Health Connect, tap "App permissions," find Google Health Services, and confirm that both "Sleep" and "Body measurements" show as Allowed. If either shows Not Allowed, tap it and grant full permission. Re-granting this permission draws the highest engagement as a confirmed fix across user discussions, Android Digest found.
Step 2: Remove battery optimization for Google Health Services on your phone
Go to Phone Settings, then Apps, then Google Health Services, then Battery, and set it to Unrestricted. Left on the default Optimized setting, Android's Doze mode suspends the monitoring process mid-session. That suspension is what produces truncated records rather than fully missing ones, according to Android Digest.
Step 3: Check Body Sensors permission on the watch
On the watch, open Settings, then Apps, then Health Services, then Permissions, and confirm Body Sensors is granted. This is a separate permission from the Health Connect settings on the phone, and it needs to be verified independently.
Step 4: Remove battery optimization on the watch
On the watch, go to Settings, then Apps, then Health Services, then Battery, and set it to Unrestricted. This step is independent of Step 2. Completing only the phone-side battery setting and skipping the watch-side equivalent is a common reason the fix doesn't hold.
Step 5: Let the watch recalibrate before your next sleep session
Wear the watch for at least 30 minutes while sitting still after making these changes, per Android Digest. This gives the sensors time to resume normal operation before the next overnight session.
If permissions revert after a day or two, the next step before considering a factory reset is clearing the app cache for both Google Health Services and Health Connect. A factory reset is rarely necessary and should only be attempted if cache clearing also fails, Android Digest noted.
Why Pixel Watch 3 sleep data goes missing after the WearOS 5.1 update
What follows is the reported explanation for how the update produces these failures. It fits the observed behavior closely, but it has not been confirmed by Google.
During installation, WearOS performs a permission audit: it checks every app's declared permissions against the new policy baseline and revokes entries that no longer match, without alerting the user. Sleep session write access for Google Health Services is one of the permissions frequently dropped at this stage, Android Digest reported.
WearOS 5.1 also tightened background sensor access as part of changes inherited from Android 15's stricter battery management approach. Body Sensors permission now requires explicit re-granting after the update, even when it was correctly configured before the installation, per Android Digest.
The Health Connect API sits between the watch's on-device sensors and the Google Health app on the paired phone, acting as the single data broker for everything the watch records. A revoked permission at that layer cuts off everything downstream: full sessions, stage breakdowns, and SpO2 readings all route through it. That architecture is also what makes the three failure modes distinct rather than random. Each one maps to a different break point in the same permissions chain.
The sensors themselves appear to be working. What the update disrupted is the software layer that carries their data through.
Understanding why these breaks are separate matters for the fix. A user who sees complete sessions but missing REM data has a different problem from one who sees no session at all, even though both trace back to the same update. Treating them identically, and running all five steps regardless of symptom, wastes time and sometimes introduces new issues. Starting at the step that matches the specific failure mode is more reliable, which is why the symptom map above exists.
Google's response: no advisory, no patch timeline
Android Digest reported last month that Google had not published a formal advisory naming the WearOS 5.1 sleep tracking regression, and no patch release date had been confirmed. The volume of affected users reporting the same experience made the absence of any official acknowledgment notable.
The closest thing to a public record is the Google Issue Tracker. Searching "Wear OS sleep health connect" surfaces active threads where occasional status updates from Google staff appear, per Android Digest. Those threads are not a support commitment, and none has produced a fix timeline.
For now, Pixel Watch 3 owners who depend on sleep data are manually restoring what the update quietly removed. If a patch does arrive, it would presumably automate that process: restoring the Health Connect permissions and battery settings that WearOS 5.1's installation routine reset without notice. Until then, checking Health Connect permissions after any major WearOS update has become practical maintenance for anyone who relies on the watch's health tracking features.
Comments
Be the first, drop a comment!