Connected GPS Run Inaccurate Distance (Screenshots)

[mynameisnick4]

I have done two runs with the Versa so far using the connected GPS to my phone and both runs have been extremely inaccurate. The first run was a 4 mile run, fitbit had it as a 3. The second run was another 4 mile run and at the half way point it had it at 1.4 miles instead of two.

I am coming from a Blaze and while it didn't match Google Fit 100% (normally off by .1 of a mile or so) it was never off by this much. Here are screenshots below showing it:

Completed run in Google Fit:

Complete run with Versa connected GPS:

The same run but with the Blaze and connected GPS:

And here today different location at the two mile mark in Google fit:

Versa connected GPS:

This is completely unacceptable. If this can't be permanently resolved (and I DO NOT considered constantly rebooting the device/my phone, pairing re-paring, etc a fix) then it will be going back. Add this to it deciding to give me an extra 3k steps while I was sitting on my computer doing nothing last night I am not that happy so far.

EDIT: Just noticed on today's run that the GPS line doesn't start until half way down the run but it was tracking from the start. Where it has the first mile marked isn't even a mile from the point the line starts. Just add it to the list I guess.

[SunsetRunner]

@kcronin  What did you change in the Versa Bluetooth connection settings?

[kcronin]

On your Versa go to Settings>Bluetooth Connection Options >Music Via Bluetooth >ON/PAIR/OFF. It works best for me as OFF. Seems to remove interference from my BT headphones which aren't playing from my Versa but are playing from my phone. Another individual finds ON works better for him. Different phones, different headphones. You'll need to try different settings to see what works best for you. 

It's been suggested to me from Support (I've been emailing with them for 2.5 weeks regarding this) that this problem will likely be resolved with the new firmware update  I haven't received it yet but should by June 1. If you can't get the Connected GPS feature to work before then, I suspect the update will resolve it. 

[kcronin]

I replied in the Screenshots thread. Sorry. Check there for the settings.

⁣Sent from BlueMail ​

[BamIAm]

I got the new firmware installed on Friday.  Still getting dropped Bluetooth connections, a couple on a 3 mile walk today.  They were brief, but shortened the results by .04 mile or so, a couple of hundred feet.

These are seriously not precision devices.  They sure charge for them like they are though.

[kcronin]

@BamIAm  I worked in medical research and pharmaceutical testing for decades.  Trust me $200 is nothing as compared to precision instrumentation used in the science and health field.  I spent 4 times that amount for my phone. 

Sometimes I think we need to remember what's the main purpose here, to get ourselves moving more and live healthier lifestyles.  It still counts as a full run to our bodies even if our Versas don't measure it as such.  What did we do before these devices were invented?  I'm disappointed too that not all the advertised features work as described.  My Charge2 was great.  I bought it months after the initial release.  Maybe if I had waited to buy my Versa my experience would have been a little different but I'm still getting out there, exercising, moving every hour, trying to get the best sleep I can and just trying to make healthier choices.

[SunsetRunner]

Thank you @kcronin. That setting is off by default, so I turned it on. We will see what happens on tonight's walk. I have an S7 Edge.

[BamIAm]

The point that I was trying to make about Fitbit's price is that there are functionally equivalent units for sale for about $30 - $50 without all the marketing hype.  If Fitbit can't provide a reliable, consistent tracker they won't be around for long.

[Runnerforlife]

I do have it set to always connected. During my run however I would notice
it connecting. I also found out this morning for my workout that an
elliptical is not an option under exercise. I set it as treadmill and it
had my heart rate at over 200. I also wore my Surge today just to compare
things and my heart rate was never over 160 which was comparable to the
heart rate on the elliptical.

[kcronin]

@Runnerforlife  Elliptical is an exercise on Fitbit.  Your Versa can display up to 7 exercises but there are 20 to choose from.  If you already have 7 exercises displaying on your Versa, to add Elliptical you will need to delete one of the exercise shortcuts you currently have.  When you do, you can add Elliptical.

[walkingcarolina]

(Preface: I don't have the versa yet, only the ChargeHR) Did you try only using the stopwatch/activity tracker, if that is still a feature, and not simultaneously using the app to see if that was accurate (like without the wifi side of things)? I know my old one isn't as high tech but its always been spot on with distance/HR/steps so I'm curious if its a mechanical problem or a software problem. 

[SunsetRunner]

@walkingcarolina yes, the stopwatch/activity tracker is on the Versa.  I'm going to try it tomorrow.

[kcronin]

@walkingcarolina  Since the Versa doesn't have an internal gps, you must have your phone with you to have the "Connected GPS" feature.  I've tracked using just the Versa without doing any simultaneous co-tracking with the phone.  That's the preferred method.  That's where the distance discrepancy lies.  The loss of bluetooth communication between the Versa and the phone results in the incorrect distance measurement.

[Runnerforlife]

Thank you, I will definitely look that up.

[walkingcarolina]

That totally makes sense, but I mean as far as without gps/maps/trackers just the step counter alone. The charge HR doesn't have any of those extras, but the step and stride counter calculates a mileage based on steps alone and it's typically pretty accurate. 

[fitnessrealist]

Definitely an issue with the versa losing the Bluetooth connection. Tries it again today and had the same issue. Versa missed about a mile of the run. The strange thing is that the map appears to be mostly right, just the distance is wrong.

[Knytenurse03]

My blaze does the same thing . When I exercise with someone with a blaze or Versa my distance is always behind. And it doesnt connect to GPS or says phone not found. Customer service person told me to calculate my stride and this should fix it. Well it didnt. Now I just rely on my phone. I spent $200 for what

[AndyCyclist]

I've given up for now until I hear it's fixed. It's just too frustrating to look down ten minutes into a ride and see "connecting..." I just record from Strava on my phone.

So, I miss out on being able to start/stop/pause rides from my wrist like I could on my Pebble, and I won't get heart rate data over to Strava. I wish at least that Fitbit would pull the ride GPS trace from Strava, instead of just showing the distance and time on my dashboard.

There is definitely something going on between WiFi and Bluetooth. The last couple of times I recorded from Fitbit, it held connection the whole way to work (~9 miles, 40 minutes) then dropped at the same spot in my work driveway. Probably at that point my phone was trying to connect to the known WiFi network.

Also, yesterday morning I saw this notice on my phone:

I'm not sure what that could possibly mean, but maybe it's related. I found this possibly relevant discussion... from 2013!

https://stackoverflow.com/questions/17870189/android-4-3-bluetooth-low-energy-unstable

...and 2015...

https://issuetracker.google.com/issues/37054253

Again, none of this would matter, though, if the Fitbit Android app recorded the GPS data it was sending to the watch, then merged it with the heartrate data at the end of the activity. There's no reason to send the data over the unreliable Bluetooth connection twice.

[kcronin]

Here's a recently posted review of the Versa.  The interesting thing is the discussion regarding the Connected GPS and the struggle the reviewer had with this feature.  I'll let you read for yourselves.  Deep into the article for those who want to skim through.

https://www.dcrainmaker.com/2018/05/fitbit-versa-review.html

[BamIAm]

@kcronin, great article, thanks!

I'm going to try the stride length override.  The breaks in connected GPS I've been getting have been short, so if it "straight lines" with a correct step count / stride, it should be close.

Made it through a 3 mile walk yesterday connected all the way.  Tried putting the Versa on the same side as my phone, instead of going across my body.  What's weird is that I can get text notifications with the phone way across the room, but I guess the continuous GPS data stream might need to be closer. 

[kcronin]

@BamIAm  My breaks in connection have been very short recently and straight line connections when it happens.  My route is identical most days. The distance FitBit calculates on these days varies from 3.39 to 3.57.  Did I say IDENTICAL?  Clearly I can't watch for pace improvements from day to day. 

I figure that DC Rainmaker had a direct hotline to Support when he was testing the Versa for review and that he had been provided a device that was checked for any manufacturing faults.  Even so, he struggled with Connected GPS and required app and device updates to get it to work.

BTW, it's been suggested that a Factory Reset of the Versa at this point will trigger the firmware update.  Might try this although, for the most part, my Versa is working well right now. Hate to rock the boat so to speak.