🙏 The data we need to push NOOP forward — grab one you can help with

[NoopApp]

NOOP moves at the speed of the data you share. Almost every recent feature — the v25 sleep unlock, the workout re-score, the data-loss fix — came from someone posting a strap log. This is the running list of exactly what we need right now, from "2 minutes on your phone" to "you happen to own the right hardware." Grab one. 🙏

🛌 1. Confirm WHOOP 4.0 sleep on v25 firmware (v1.95)

The biggest one. We just shipped a decoder for the "v25" firmware layout that previously gave no sleep/recovery on WHOOP 4.0. We've validated the decode against real records, but we haven't yet watched a full banked night come through to a finished Sleep score on someone's device.

If you had a 4.0 with no sleep: update to v1.95, wear it through a night, sync, and reply here with — does the Sleep card now show stages? Does Recovery appear? A fresh strap log (below) seals it.

📡 2. WHOOP 5.0 / MG raw history captures

On 5/MG, live HR works today, but the deeper scores (recovery, strain, sleep) are still being reverse-engineered from the strap's offload — the historical record layout is different from 4.0 and we're still mapping it. We need raw historical captures from 5/MG straps to crack it.

If you have a 5.0 or MG: enable Debug logging (below), wear + sync it (ideally across a night), and attach the log to a new issue. Every 5/MG capture moves the recovery/strain/sleep work forward.

👟 3. Calibrate the step counter (#139 / #78)

Steps (5/MG only) run high because we read WHOOP's internal motion counter but don't know, from any spec, how many ticks = one real step. One data point fixes it for everyone: walk a known number of steps (count ~100, or use a treadmill), then tell us (a) how many you actually took and (b) how much NOOP's step total went up. That single ratio is the missing piece.

🍎 4. iOS field reports

iOS just landed as a build-from-source target. The analytics are shared code (so the numbers match Mac), but live Bluetooth pairing on a real iPhone is the one thing we can't test in a simulator. If you build it (see docs/IOS.md) and pair a strap: does live HR flow? Does history offload? Tell us what you see.

🧬 5. Unusual firmware / "no history" cases

If your strap completes a sync but no history lands, or you see "rejected frame" lines, your log might contain a firmware layout we haven't mapped. These are gold — they're how v25 got decoded. Post the log.

---

How to grab a strap log (it contains no personal data)

• Android: Settings → Strap → "Share strap log (for bug reports)"
• macOS: Live screen → Strap log card → Copy / Save…

Strap logs are biometrics + timestamps only — no account, no serial, no name. Redact anything you're unsure about; partial logs still help.

Where to post: a quick result or question → reply here. A log for a specific bug → open an issue (there's a template). Either way, thank you — this is genuinely how NOOP gets built.

(Want to support the time + tooling behind all this? See the Announcements post — even a few dollars in crypto helps keep it going.)

[NoopApp]

🔓 New top priority: help unlock WHOOP 5.0 / MG

We just got the best lead yet on why WHOOP 5.0/MG only gives NOOP live heart rate — no recovery, strain, sleep or history. A Bluetooth capture one owner shared (#174) shows the official app stores a set of enable_r22_*_packets config keys on the strap, and those switch on the deeper data streams that third-party apps never receive. ("R22" is just the strap's hardware generation.)

What would crack it open — if you own a 5.0/MG: a Bluetooth HCI snoop log of the official app — one while pairing the strap fresh, and one while it syncs a night's history. It's your own device and your own data; takes a few minutes on Android (or iPhone + Mac).

Full step-by-step + exactly what we're looking for: Capturing Bluetooth Logs.

If even one person captures the official app setting that config, there's a real shot at taking 5.0/MG from HR-only to fully working — for everyone. Drop captures on #174 or a new issue. 🙏