You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
0.11.3 + 0.9.29 - wear time will randomly halt in spite of syncing being up to date and band has not left arm #450
Randomly over the past few days, wear time will just halt all of the sudden (even though the band is still on my arm, live bpm is still coming through, and syncing is up to date.) This will in turn halt the breakdown of the day for the rest of the day.
Expected: wear time continues since band is still on arm, live bpm is coming through, and syncing is up to date.
Steps to reproduce
Wear band for a while
Notice some days experience wear time halting
App version
0.9.29
Platform
Android (APK)
Phone model and OS version
Moto G power 2022 - Android version: 12 S3RQS32.20-42-10-9-12
Which band?
WHOOP 4.0
Screenshots
No response
Quick checks
The official WHOOP app is not also connected to this band
I'm not sure if it ties into this but I noticed some 'data decay' when going back through breakdowns; in this example it recorded sleep data starting at 11:58 PM but in the breakdown we see it only starting much later in the morning
This is not reflected in the sleep data, just the breakdown:
These occur fairly regularly starting less than a week earlier than the current day
changed the title [-]0.9.29 - wear time will randomly halt in spite of syncing being up to date and band has not left arm[/-][+]0.11.3 + 0.9.29 - wear time will randomly halt in spite of syncing being up to date and band has not left arm[/+]on Oct 19, 2026
This issue is still present in 0.11.3, seams like if the data processing hasn't finished by midnight then it just cancels it and starts processing the next days data:
Activity
cb0806151 commentedon Sep 24, 2026
I'm not sure if it ties into this but I noticed some 'data decay' when going back through breakdowns; in this example it recorded sleep data starting at 11:58 PM but in the breakdown we see it only starting much later in the morning
This is not reflected in the sleep data, just the breakdown:
These occur fairly regularly starting less than a week earlier than the current day
Sync ledger: per-chunk rows, archived count and record-time range on …
[-]0.9.29 - wear time will randomly halt in spite of syncing being up to date and band has not left arm[/-][+]0.11.3 + 0.9.29 - wear time will randomly halt in spite of syncing being up to date and band has not left arm[/+]cb0806151 commentedon Oct 19, 2026
This issue is still present in 0.11.3, seams like if the data processing hasn't finished by midnight then it just cancels it and starts processing the next days data: