09-20-2024
07:46
- last edited on
12-20-2024
08:02
by
LizzyFitbit
09-20-2024
07:46
- last edited on
12-20-2024
08:02
by
LizzyFitbit
For the past few months my watch does not accurately track my distance. I tried setting my watch to internal GPS, Phone only and dynamic at different times and nothing helps. While walking on a marked trail it said I went under a half a mile when I walked over a mile. I noticed my pace was over @22' to 25' while my husbands was @14' to 16' . Today again my friend who also has a Fitbit, her pace was @16' to 17' and mine again was over 20'. I tried using the app on my phone to track and it was registering 95' so I shut it off. Her app said we walked 4 miles mine said we walked under 3.5 and I walked to her house before she started tracking. Additionally, my watch continually connected to phone through dynamic GPS ad now it does not connect at all. I have already uninstalled and reinstalled the app, force stopped the app, restarted the watch, resynced my watch to the phone after uninstalling and reinstalling the app. Nothing has helped. My watch is still under warranty and I want a new one. They responded to me saying it is a known problem and are working on resolving it. That said I think my watch is defective and should be replaced while under warranty. If it does not do what I bought it to do it is useless to me. When they fix the bug, if my watch still is inaccurate, will they still honor the warranty if it is out of warranty by then?
Moderator Edit: Clarified subject
09-23-2024 07:32
09-23-2024 07:32
same proble - I posted my issue in this forum but so far no reply
https://community.fitbit.com/t5/Charge-6/Running-stats-not-accurate/m-p/5665200#M12923
01-02-2025 01:32
01-02-2025 01:32
I have the same issue while using the Walk function. The workaround appears to be to set stride length manually. Forum search indicates that the problem is known for at least half a year to the Devs, but it is telling that they haven’t been able to fix it yet. Honestly, the Charge 6 has too many issues for an allegedly 6th iteration of a device.
@support any news when the bugfix will finally be released?