F76 Screenless Band: Purchase & App Evaluation

For buyers prioritizing a compact screenless main unit. Review F76 fit, clear model identification and measured runtime under your intended sync schedule before approving an OEM sample.

Compact fit, model identity and measured runtime

Reviewed 13 November 2026 using the supplied F76 product pack. The values below are supplier references; the approved sample and written quotation define the delivered configuration.

Purchase itemF76 reference / decision
Supplier modelF76
Main unit dimensions37.2 × 18.9 × 8.7 mm; supplier reference includes the sensor module
Listed total weight11.5 g; verify the supplied strap configuration
Controller / heart-rate sensorAB5691 / TYHX3602
Reference battery75 mAh polymer lithium-ion
Listed companion appJoeme Fit; confirm firmware pairing and current phone compatibility
Own-app routeModel-matched package, supported fields and permitted use to be agreed before development

What should a F76 sample demonstrate?

Order identity

The supplied pack and model field identify F76, while the source sheet contains an F75 heading. Match the quotation, sample, label and firmware identity before approving the order; do not silently substitute either model.

Fit and sensor contact

Record strap adjustment and stable sensor contact on the intended wearers. Compare its 37.2 × 18.9 × 8.7 mm main unit with F73/F74 using actual fit, not dimensions alone.

Runtime under your workflow

The reference capacity is 75 mAh. Record sensing settings, sync frequency, phone behaviour, charge endpoints and start/end battery. A smaller main unit or battery does not establish a tested runtime.

Phone compatibility

The source includes inconsistent operating-system wording. Verify pairing, permissions, background sync and history retrieval on the actual target iOS/Android versions instead of treating the printed compatibility text as a completed test.

Choose the app route before quoting engineering

The supplied Joeme Fit workflow and a buyer-owned app are different routes. For an own-app project, list the required fields and obtain confirmation of a package compatible with this model and firmware. An SDK, Bluetooth document, cloud API, app source code and watch firmware are separate deliverables. Specify what your team will build and which, if any, extra engineering services are requested.

A proposed package must be checked on your sample. SDK access does not automatically include every raw sensor stream, recovery algorithm, unrestricted redistribution rights or recurring services.

From sample to pilot order

  1. Confirm F76, the configuration and the sample quantity. Provide the destination and complete recipient details for a shipping quotation.
  2. Agree sample hardware, included documents, app route and any separately quoted engineering work before payment.
  3. Record delivery, the document/package version and the actual test results. Tell Galax which required test passed or remains blocked.
  4. For a pilot or branded order, confirm the next quantity, timing, artwork, packaging and model-specific production conditions. A sample quantity is not a promise of low-MOQ custom hardware.

Does the compact F76 have the same runtime as F73?

That is not established. The supplier references list 75 mAh for F76 and 110 mAh for F73; runtime also depends on firmware, sensing and phone sync. Compare measured results under the same usage profile.

These are proposed acceptance checks, not completed tests. Supplier-listed wellness metrics do not establish clinical accuracy. Water-resistance, runtime, data access, document coverage and exact firmware functions should be checked for the quoted configuration.