01-16-2020 06:34
01-16-2020 06:34
Hoping a Fitbit rep could shed some light on this issue. I own an Ionic with the latest firmware. My wife owns a Versa 2 with the latest firmware. We've notice that when we go for our roughly 4 mile walk, my fitbit registers about 1/3 of a mile more than hers by the end of the walk. Her Versa2 stays connected to her phone the entire way, and my Ionic stays connected to GPS. The elapsed time is within a few seconds of each other, but today, her distance registered at 4.05mi and mine was 4.38mi. When we both looked at the generated map of the walk, her trace was nice and straight. Mine looked like I was stumbling home from the pub. Very jagged, sometimes popping the trace out into the street or all the way to the other side of the street, etc. Is this a known issue with the Ionic? If so, any fixes planned? Thanks!
01-16-2020 10:21
01-16-2020 10:21
I am having the exact same problem ever since the last firmware update. Not only that, sometimes during a run it will connect in the beginning, then lose a signal and never connect again. Terribly annoying. The reason I have the Ionic in the first place is the built in GPS. There are lots of complaints about the last update, so I'm hoping that Fitbit can resolve this ASAP.
01-17-2020 09:47
01-17-2020 09:47
Interestingly for me, when we were biking, our fitbits were closer in reporting distance then when we were walking. My route trace for biking was much smoother as well. I havent been on this forum for over a year. The Fitbit Mods used to be pretty quick to respond. Do they still respond to questions? I'd love to hear their take on this problem.
01-17-2020 10:44
01-17-2020 10:44
@NHMike it's because for Bike exercise using steps and stride makes no sense and the distance is computed using only GPS data. It should be done the same way for step-based activities with GPS enabled but for some reason, Fitbit decided to implement it differently and stuck with this design for good.