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.

[Courtenay_06]

I'm actually hoping the app update will help me, too. This is going to be
the deciding factor in whether or not I keep the watch! Fingers crossed, as
I'm going for a run later.

[kcronin]

Mine was spot on today too. I did see "connecting" at one point when a call came in. I know that my Versa had disconnected from my phone because I couldn't reject the call as I have been able to do in the past. When the Versa finally reconnected, the distance was updated and correct and the missed call notification finally came through. I wasn't hopping over people's houses and yards when I looked at my map at the end. Too bad Fitbit doesn't discuss this in the app update notes. Just bug fixes and female health. I think many could be more tolerant if we thought Fitbit was being honest and forthcoming about this issue.

⁣Sent from BlueMail ​

[pixbuf]

This is a promising development, but I'm not going to start celebrating until I get several days in a row with correct distance and time measures.

[pixbuf]

No such luck for me. My regular 20.3 KM ride clocked in at 18.78 KM. That's about 7.5% less than actual, and very close to my 30-ride standard deviation of 1.6 KM. 

The weird thing is that I seem to lose the connection often around the same place.

[Courtenay_06]

I just took a run.... nope, not fixed. I ran 3.1 miles and my Fitbit clocks
in at 2.51 miles, and the map is super wonky again.

I think this was my last straw. I'm going to switch to Garmin. Sorry,
Fitbit, I've loved you for three years now, but I did not pay $200 for a
simple pedometer.

[charge2fan]

---

@Courtenay_06 wrote:
I just took a run.... nope, not fixed. I ran 3.1 miles and my Fitbit clocks
in at 2.51 miles, and the map is super wonky again.

I think this was my last straw. I'm going to switch to Garmin. Sorry,
Fitbit, I've loved you for three years now, but I did not pay $200 for a
simple pedometer.

---

That is not good to  hear. I was hoping it was a simple software fix but appears not to be.

I don't understand how they could have gone backwards with implementing 'Connected GPS' in the Versa when they had it working well with the Charge 2.

Very disappointed.

[swim4lifekac]

It has connected and accurate for me since I updated my Galaxy S6 to a S9+.  It connects within 15 seconds and no longer disconnects.   Today it even uploaded to Stava for the first time. 

[Courtenay_06]

I have a Note 8, which was just released a half year ago. It shouldn't be
having issues with it.

[kcronin]

I don't know what to say.  After struggling with Connected GPS since launch day when I got my Versa, the past couple of days it's worked perfectly.  With the firmware update and the software update to 2.72 everything has been perfect.  I'm running an "older" phone, Samsung S7 with Android 7.0 OS.  I've previously played around with tons of settings but now, besides having my phone location settings to "Phone Only" and not "High Accuracy", I don't bother to turn of my WiFi, I don't have the Keep Alive Widget running (it ate my phone battery), I don't have on All-day Sync (again my phone battery issue) and when I sync after my walk, no jaggy route.  I am wondering if perhaps the fix is only for Walk.  If I tried Bike would I have a different result?  I'll have to test it out.  BTW, initiating a Walk on my Fitbit app manually now isn't working.  However, I'm not going to worry about that one.

[Sheldoreo]

My partner took her Versa out for a Walk using the connected GPS.  It did seem relatively accurate, however it was only a 1.2km walk.  It didn't work at all well the other day for a cycle so I still don't hold out much hope for it.

I think any more issues with it and it'll be returned permanently.  After coming from Garmin at least she has a solid backup ready for when it's gone for good.

[Courtenay_06]

Yeah, I finally got tired of it, and I sold my Fitbit Versa today (it was
too late to return it). I purchased a Garmin Vivoactive 3, and I hope I
like it more. It's too bad, I love Fitbit, but as the accuracy of exercise
tracking is one of its main sellings points for me, I just find it
inexcusable that it's $200 and it works so poorly.

Fitbit refuses to acknowledge that there is clearly a bug that is affecting
many people and instead points to the apps being out-of-date or the phone's
Bluetooth connection being bad. I know in my case and in many cases, the
Bluetooth on our phones are working just fine, and I had the most
up-to-date app that was available to me. I have a Note 8, which should be a
supported device. If they would acknowledge that an update was coming to
fix it, I would have stuck with it.

Good luck, everyone! I hope it begins working for you if you decide to
stick with the Versa.

[Berberis]

For me everything just works now with a Honor 8 phone (android 7) and the 2.72 Android app. The Versa is on firmware .15

I was just about to give up on this thing, but (for me) with the 2.72 andoid app the bluetooth issue is gone.

[pixbuf]

I'm happy for you. Unfortunately, 2.72 didn't do it for me. Last night the app updated to 2.72.1, but it was raining today so I couldn't ride. I'll try it tomorrow. Hopefully, the weather, the app, and the Versa will cooperate.

[mynameisnick4]

The Garmin Vivoactive 3 is what I switched to and I'm loving it. Sure the screen isn't as nice as the versa but in the areas I want out of a fitness watch it excels. Distance tracking is spot on. I ran a marathon in it and it had me at 26.26, basically dead on. Battery life is great and I like the extra info it gives for running such as cadence and stride length.

[fitnessrealist]

Ran a 10K on Saturday and started the GPS tracking on the Versa, which connected quickly, and then started myrunkeeper. I noticed about 0.5mi in that runkeeper wasn't giving me audio cues like it normally does. Then realized that it wasn't tracking like it normally does. However, Versa seemed to be working ok. After the race, Versa logged the 10K at 6.15mi and runkeeper only had 0.5mi (but was running the whole time and logged the correct time). So it seems like the GPS can't run on 2 apps at once. So maybe  @Fitbit needs to work on integrating the connected GPS with a third party app like runkeeper and all our GPS problems will be solved!

[TheGrouch]

A)  Agreed, I would absolutely love it if I could just run Strava from the Versa and have it collect ACCURATE distance, along with HR Data.  That's 90% of the reason I bought the Versa.   

B)  You can run both the Versa exercise app in Connected GPS mode and a GPS exercise app on the phone simultaneously.  I'm forced to do this pretty much every bike ride because Fitbit's distance calculation sucks.  I review the HR data from the Versa ride, but I use Strava for real numbers.  I've run the Versa bike app without Strava running on my phone.  It's not any more accurate, in my experience.  The Versa is commonly short by 10-15%.

As many have said, this is BS.  Versa needs to fix the crap distance tracking, whatever the cause.  I like the form factor and many of the features, but I can't justify sticking with the Versa when I doesn't do the one thing I bought it for (accurately track bike rides with HR data).

[Courtenay_06]

Update: so far I love the Vivoactive 3. If you can return your Versa and are willing to switch over, I'd do it. I ran 4 miles the other day and it was right on point with my MapMyRun GPS.

I can't believe they still haven't addressed this issue! 

[Ethanchan]

Have the same connecting problem and Fitbit does not get the gps for my whole ride

[Ian7]

I just got a Versa, biked with it for first time today.  I love the heart rate and sleep tracking but the mileage and distance were off.  Using iPhone.  Maybe it was because I was using mapmyride at the same time?  I guess I can try it without mapmyride tomorrow with the same route and see if it’s better.  Having mixed feelings about this product.  Wondering if I’ll need a device with built in gps.  If so then Apple Watch seems like the most obvious choice.  Wouldn’t get the most expensive Fitbit because they’ve proven they don’t work well.  We'll see I guess. 

[pixbuf]

@Ian7, have you upgraded the mobile app? I was also having this problem, but since the update to version 2.73, I haven't had the problem. Actually, I can't tell if it was because of the app update or because of the fact that I got a new phone at the same time. The two actions are completely confounded.

In any case, I don't think it's due to running mapmyride simultaneously. I run Strava on my phone while I track my ride with the Versa and don't see any problem.