PUBLIC TEST METHOD
How we test heart-rate monitor compatibility
Every compatibility label has an evidence threshold. The method is designed to keep protocol expectations, user reports and physical Strap Zone tests separate.
What a Lab tested result requires
A lab record identifies the exact sensor, Strap Zone version, phone model, operating-system version and test date. It records both success and failure for connection, live BPM, zone changes, audio behavior and a sustained workout.
- Verify the model, firmware when visible, battery state and manufacturer instructions.
- Record phone model, OS version, Strap Zone version and competing Bluetooth connections.
- Connect from inside Strap Zone and record time to first live BPM.
- Check changing BPM, zone transitions, tones or spoken cues, lock-screen or background behavior, and workout save.
- Run at least 30 minutes, note dropouts and repeat after reconnecting.
- Publish limitations and the complete result, including failures.
The evidence ladder
| Level | Meaning |
|---|---|
| Lab tested | Physically tested with a recorded Strap Zone version, phone model, operating-system version, date and result. |
| Protocol compatible | The manufacturer documents Bluetooth heart-rate broadcasting that matches the standard BLE service read by Strap Zone, but this exact model has not completed our lab protocol. |
| User reported | A named or publicly linkable user reports that the model works, but Strap Zone has not reproduced the result in its own lab protocol. |
| Unknown | There is not enough model-specific evidence to make a compatibility claim. Brand-level assumptions do not change this status. |
| Not supported | The device lacks the Bluetooth Low Energy Heart Rate Service required by Strap Zone, or documented testing shows that the required data is unavailable. |
Protocol review is not a physical test
Strap Zone scans for BLE service UUID 0x180D and subscribes to characteristic 0x2A37. Manufacturer documentation for compatible broadcasting can justify Protocol compatible. It cannot prove phone-specific reliability, firmware behavior, multi-connection limits or background audio.
User reports
A report must identify the exact model and enough environment detail to be useful. Public reports need a link; private reports need permission before attribution. Free access, loan hardware or another incentive must be disclosed. No report is accepted in exchange for a positive rating.
What we do not claim
- Protocol compatible does not mean certified by the sensor manufacturer.
- One successful model does not prove support for a whole brand or family.
- Sensor memory does not provide live Strap Zone alerts when the phone is absent.
- ANT+ support alone does not make a device compatible with Strap Zone.
- A user report is not silently promoted to Lab tested.
Corrections and updates
The public compatibility matrix and its JSON dataset carry a review date. Send corrections with a source, exact model and reproduction details through support.