05-05-2020
10:13
- last edited on
05-06-2020
19:20
by
RicardoFitbit
05-05-2020
10:13
- last edited on
05-06-2020
19:20
by
RicardoFitbit
Picture says more than thousand words so... picture first.
How can it be that the same lap is measured THAT wrong. It is 1,27 km difference which is BAD. Both lines run on the same road so it can not be just "difference". Step count is the same and also the time. Which one can I trust at all? It isn't the first time it has happened (at least once more).
FitBit app is up to date. My Versa 2 is up to date.
I started my run the same way: opened exercise - choose "run" - wait FitBit to connect with "connected GPS" - start!
Also the settings are the same when I start the run. I activate "do not disturb" and "always on display".
Am I doing something wrong? Is the app so bad that it does not know how to calculate distance? Is it problem with my watch? I looked into it and it seems this problem has been with you for 3.5 years. Is there seriously no fix?
Anyways, I posted this in "App" section because it seems to be problem with an app. If not let me know.
Moderator edit: Subject for clarity
06-12-2020 22:03
06-12-2020 22:03
06-13-2020 06:41
06-13-2020 06:41
It's looking like it's something within the app and watch that's not translating properly. Using GPS on the phone within the Fitbit app works fine. When using the watch it's getting a calculation that makes it go way off tangent even though it's getting the right GPS reading. Not much we can do at the moment but wait for the mods to fill us in. Doubt there's anything we can do at this point as many have tried things like turning the watch and phone on and off and disabling things such as auto stride. I've tried all and they all have failed.
06-13-2020 08:06
06-13-2020 08:06
06-13-2020 08:27
06-13-2020 08:27
Distance is measured at the trail we run at. My wife and I run up to the 2.2 mile mark and the fitbit app gets it at 2.19 or so which is close enough for us. When I run it on my watch it gets the distance of 2.2 miles all the way up to 3 miles which is way off of course.
Went for a walk yesterday thinking maybe that would work and it under shot that one. We got to the 3 mile mark and my walk showed 2.6 which shows that my runs are usually over and the walks are under.
06-13-2020 18:30
06-13-2020 18:30
06-14-2020 00:37
06-14-2020 00:37
Got to be careful what I say here as my last post was deleted! 🙄
I'm not sure whether this is a coincidence, but the last 2 walks I've been on have been pretty accurate. Well, when I say accurate, it's within 100m of the correct distance which is still not accurate but better than it was! All I did was turn off all the auto recognised exercises (in the app under Account/Goals/Exercise). Maybe someone else could try this and see if it's not just me?
I'm still buying a Garmin next time round though. My daughter's is super accurate!
06-14-2020 12:58
06-14-2020 12:58
@SunsetRunner I tried turning off all the auto detect tonight for my run and the Versa went from one extreme to another...rather than 0.5miles short (on a 3miler) it was 0.5miles too far. I thought 10 minute miles were a bit extreme for me haha!! My daughter told me it was wrong...her Apple was correct as usual! 😞
06-14-2020 15:18
06-14-2020 15:18
My wife and I walk about 5 miles together every day and her FitBit Versa 2 almost always shows her distance as .5 to .75 miles less than my FitBit Versa 2. We both use Samsung Galaxy S8+ phones. I have rebooted both the phones and the FitBits multiple times but it has not resolved the issue. Our FitBit map route match but the distances do not.
06-15-2020 15:52
06-15-2020 15:52
Well odd behavior today. Instead of being over the in my distance at the trail I was actually under by .3 miles. I turned on auto-stride to see if anything changed and this was the outcome. Anyone else have this or was it just me?
06-15-2020 16:03
06-15-2020 16:03
I honestly don't understand how this is not fixed yet and even moreso don't understand how we are NOT getting a daily updates from the moderator on this. This should should have taken a couple days to fix max. Total Bush League customer service. Congrats, Fitbit. You have officially taken something i use to alleviate the stress from my day job and turned it into something that further aggravates me. I'm about done. Unless this is fixed in the next few days I'm returning this garbage and getting a Garmin or something comparable. This is just ridiculous.
06-15-2020 23:11
06-15-2020 23:11
I am done too. Looking at alternatives. Been with Fitbit since 2015 but lately just more frustrated than anything with the issues!
06-16-2020 00:49
06-16-2020 00:49
I turned off auto recognition for the exercises as someone suggested, but that did not work either, still well below the distance I did. I am chatting with fitbit almost everyday, everyday they ask me to do something different but nothing seems to be helping. If I start the exercise with the app, no problem, it is pretty much accurate comparing with other apps (like 100 or 200meters difference), but when I start the walk using the watch, then it is always well under, nearly 1km different. So frustrated at the moment.
06-16-2020 03:01
06-16-2020 03:01
Does Strava work through the Fitbit for accuracy? Just using Fitbit for run/walk, it does not work, but Strava on my phone is accurate so I didn't know if I used it with the Fitbit if it would?
Also that shows me it's an issue with the Fitbit or Fitbit software.
06-16-2020 03:26
06-16-2020 03:26
@SnugD So I don't start a workout in the Strava app, I just start it on my Versa. Once I finish it on the versa, the fitbit app sends it to Strava.
But apparently with wrong data.
So I deleted the automatically generated Strava workout, downloaded the tcx from Fitbit and uploaded it as a activity in Strava.
06-16-2020 04:32
06-16-2020 04:32
06-16-2020 09:13
06-16-2020 09:13
@BornClimber Don't know if they are being helpful or really wasting my time because surely they must know about this issue and must know that all those steps they try does not work anything. Once again today, went for a walk after doing a factory reset suggested by them and still the same, watch showing much less distance than what actually is. Let's hope Google fix this whenever they get in charge.
06-16-2020 14:35
06-16-2020 14:35
06-16-2020 19:47
06-16-2020 19:47
06-17-2020 00:06
06-17-2020 00:06
@wayneramp That’s is not true. I was using my Fitbit on my iPhone 7 with exactly these issues. The majority of people here seem to be Android owners but it does affect iPhone users too. The problem is that it is not consistently there.
06-17-2020 04:11 - edited 06-17-2020 04:13
06-17-2020 04:11 - edited 06-17-2020 04:13
@BornClimber i was speaking with them today (and yes, they are only reps, not engineers at all) and apparently now they cannot do anything anymore because my phone is not in their supported devices list, surprise surprise. So i told her i will make sure to get a supported device just to prove my point, because this is an issue that lots of people are having as we can see in this community. So i got my old galaxy s7edge out of the draw, and will start to use it and i am sure it won't change anything.