A runtime figure is useful only with its model, configuration and test conditions. Set an agreed sample profile, record what the device actually does, and use comparable results when planning a purchase.
mAh describes charge capacity; it does not guarantee operating time. Workload, configuration and software affect consumption. Display settings, radios and sensors also matter when present. Voltage and device functions can differ, so a capacity comparison alone may not be meaningful.
Separate standby or another stated test profile from runtime under a defined use pattern and from long-term battery health or service life. Ask for available model-specific data and the conditions behind it. Charging duration and procedure should follow the selected model and charger instructions.
Write down the model and configuration, app and firmware, phone, compatible charger, test profile, measurement point and units to test. Use the same conditions for each comparison.
Summarize the observed range, test conditions and sample count. A partial cycle does not establish full runtime, and sample performance is not a guarantee for customers. Do not compare runs with different settings as if they were the same profile.
Share the target market and expected use pattern, requested runtime with conditions, exact model and configuration, per-model quantity, custom features and target date. Firmware or feature changes may require another test and sample approval. Review our sample guide, app compatibility guide and warranty guide; see the ZTFit catalog.
These fields are a working record for buyer and supplier review, not a laboratory report.
No. mAh describes charge capacity, not guaranteed runtime. Model configuration, software and workload matter; display behavior and radios or sensors affect consumption when present. Voltage and device functions also matter when comparing different products.
Ask for available data for the exact model and configuration, plus the test profile, sample count and conditions. Compare results only when the profiles and measurement points are comparable; standby, a defined usage profile and long-term battery health are different measures.
Record model, app, firmware and phone. Use the agreed compatible charger and the model’s full-charge indication, then record start time and percentage. Log supported display settings, alerts, calls or workouts, connection, network and environment. Measure at the agreed low-battery point without forcing the device to shut down.
Repeat comparable cycles and include multiple units where available. Report the observed range, conditions and sample count. A partial cycle does not establish full runtime, and a sample result is not a customer guarantee.
Share the target market and use pattern, requested runtime with conditions, model and configuration, per-model quantity, custom features and target date. Firmware or feature changes may require a repeat test and sample approval.
Share your intended market and use profile, requested runtime and conditions, model, quantity, custom features and target date. We can review available model data and an agreed sample profile.