Skip to content

[Android][WHOOP 4.0] Background sync stalls for days; bond-loop pauses auto-reconnect, opening NOOP restores history downloads #2908

Open

Description

@reckor-usa

NOOP version

NOOP 12.1.0-staging (full), build 558a

Platform

Android

OS version

Android: 17 (SDK 37)

WHOOP strap / Oura ring model

WHOOP 4.0

Where the data is coming from

Live Bluetooth (WHOOP strap connected)

Test Centre profile

Connection & Sync

What happens

Background synchronization sometimes works initially, then stops.
The persistent synchronization notification can remain visible even though no history is being downloaded.
Automatic Bluetooth reconnection may enter a bond-loop pause and stop recovering without intervention.
Sleep and recovery results can remain several days behind.
Opening NOOP restores synchronization and allows the backlog to download.
Download sessions can also time out with zero frames while live heart-rate updates continue.

What you expected instead

NOOP should maintain or automatically restore synchronization while running in the background, without requiring the user to open the app.
If the Bluetooth connection or historical transfer becomes unresponsive, NOOP should automatically recover where safe, without remaining indefinitely in a paused state.
The background notification should also distinguish between an active synchronization process and a disconnected or stalled one.

Steps to reproduce

Connect the WHOOP through NOOP and allow historical synchronization to begin.
Leave NOOP using the Home gesture, without force-stopping it.
Keep Bluetooth enabled and the strap near the phone.
Leave NOOP in the background for several hours or days.
Return to NOOP and check the latest synchronized data and pending historical backlog.

noop-strap-log-261107-1556.txt

Strap log

Attached as zip

Before you submit

  • I attached my exported NOOP .zip (not a screenshot of the Live screen). If my bug is a clearly reproducible UI issue I described exactly how to see it instead.
  • I attached or pasted a strap log above — or my bug is a clearly reproducible UI issue that doesn't need one (e.g. a typo, a button that does nothing) and I've described exactly how to see it.
  • I checked the Troubleshooting guide — especially "history syncs but no data" (most often the strap isn't banking history to flash; charge it to 100% and reconnect).
  • I checked the FAQ and — if I'm on a WHOOP 5.0 / MG — the 5.0/MG status page, or — if I'm on an Oura ring — the Oura ring support table, and this isn't an already-known limit (e.g. SpO₂, recovery/sleep on the 5/MG, or no Recovery / HRV on a ring-only day).
  • I've left out anything personal (strap serial, account email, raw export).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions