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.

[Gizjones]

Thank you, @BamIAm, for the tips!
My Wifi was turned off during my run. I will turn off bluetooth scanning and change my GPS setting from High Accuracy to GPS only next time. I currently have version 2.7 on my Samsung S8. Hopefully your suggestions will work!

Thanks again!!

[A-A-Ron]

I tried turning off the Wifi completely on my Iphone 6s.  The versa connected and tracked my bike just fine.  Problem solved.  

[blu-steel]

Are these GPS problems with the phones? I wonder how much better the GPS signal is with the Ionic compared to the phones you all are using. I have the Ionic and I tell you it is a good watch for a man. THe only reason why my wife got the Versa was because her wrist is too small. I love the Ionic as IMO its the best smart watch fitness tracker out there on the market at this time. 

[BamIAm]

If you have a good GPS lock on the phone and a solid bluetooth connection to the tracker, it works fine.

I went with the Versa vs. the Ionic because I've tried a Surge.  The GPS tracking on the Surge was less reliable than my phone's GPS and MobileRun.  Was afraid the Ionic would work no better than the Surge, not worth the extra $100.  So far, Versa + phone GPS is as good as MobileRun + phone GPS for me.

[kcronin]

@BamIAm  It's that solid bluetooth connection between the phone and the Versa that I think is my problem. How do I troubleshoot this? I even moved the arm band I use to hold my phone from my right arm to my left so my body wasn't between the phone and the tracker.

The GPS on my phone seems solid and Strava (running from my phone) never disconnects. I tracked yesterday and it was better. Instead of the distance being off by 35%, it was only off by 10%.

[BamIAm]

Mine wasn't working well until recent app updates, but here's how I run it now.

Wifi off

GPS only on the phone location, bluetooth and wifi scanning off.  I check my GPS lock on my phone with the "GPS Test" app, if I don't get a "3D lock" I restart my phone and check it again.

I run the Fitbit app before starting, if I see real-time heartbeat on it, the bluetooth connection is working.

Wait until you get a bluetooth connection confirmation on the Versa.  It usually takes me 15 seconds or so.

If it drops the bluetooth connection during your walk or run, the results will be wonky.  Try MobileRun (without pausing!) for the same loop to get a benchmark.  MobileRun also shows you the route map real-time.  Would rather use it instead of connected GPS for this feature, but it has its own problems with the "pause / resume" button.  See the massive thread on this for more info.

[kcronin]

Thanks @BamIAm for your guidance.  I'll try as you suggest today and report back my results.

[BamIAm]

Short answer, if it breaks contact during the activity, there's still
connectivity problems.

Latest few versions of the app fixed this issue for me (with a Blaze and
now a Versa). Earlier versions disconnected multiple times during a 1 hour
session, so I was using MobileRun instead. Currently running V 2.70, all
is good.

Almost, make sure you've got "always connected" and the "keep-alive" widget enabled.  

[kcronin]

@BamIAm  I followed your instructions and my run was no better.  My distance for my run was still off by 27% which amounted to slightly less than a mile. 

I changed my location settings in my phone to Phone Only instead of High Accuracy.  I have Always Connected and Keep-Alive Widget on (I always have, this is no different).  I turned off my WiFi.  I loaded GPS Test onto my phone and confirmed GPS Fix and a green dot before starting.  I waited for "connected" to appear when initiating the run from my Versa.  The Versa repeatedly said "connecting" during my run but with my phone open to GPS Test, at that same time, GPS Test indicated GPS Fix and a green dot.  I do NOT believe this has to do with the GPS in my phone.  Testing and retesting the GPS connection has become a bunch of red herrings in my search for a resolution.

I DO believe this has to do with the BT in my Versa.  During my run I received a number of notifications to my phone.  I received to my Versa about 80% of them.  I know I have a notification to my phone because I have BT headphones running and the notifications make a tone in my ear.  Sometimes I received the notification and my Versa said "connecting" and other times when the Versa was trying to connect I wouldn't get the notification.  All the same app, btw.

If I have to use MobileTrack, I might as well use Strava.  I really wanted to start and stop my run from my wrist.  That's what I did with my Charge2.

Maybe I'm paranoid but I believe there is something small and particular about the BT connection between the Versa and the phone that FitBit isn't sharing here.  Maybe the Moderators just don't get such technical information.  Maybe it's propriatory and can't be shared.  Maybe my issue is intermittant.

I agree that earlier versions of the app were a problem for connected gps.  I'm one of the people who backed up my downloaded version and waited until a fix seemed present.  Now I'm back to the same issues with the current app version, v2.7.  *sigh*

Thank you for your help anyway.  I'll keep looking and testing.

[BamIAm]

Unless you get the continuous bluetooth connection during the activity,
connected GPS is pretty much useless.

If mine goes back to that I might consider an Ionic for the built-in GPS.
I had mixed results with a Surge but my understanding is that the Ionic is
improved, uses GLONASS along with GPS. Surge was GPS only.

I saw a decent looking used Ionic on Ebay today for $180.

[BamIAm]

One last thing worth trying, I started using wired earbuds vs. bluetooth.  Could help with the phone / watch connection.

[kcronin]

I'm not really interested in an Ionic because it's bulky and too masculine looking, imo. I do wish the Versa had a built-in GPS but then it might have been quite a bit bulkier which would be a negative for me.  I can try the wired headphones.  Not as comfortable.  If I have to choose, I'll choose using Strava for the correct mileage vs wired headphones.  Just want my Versa to work as advertised.

[BamIAm]

I like Strava, the GPS results I got from it were dead on. The only
problem I had with it was that it exaggerates calories burned in comparison
to Fitbit.

MobileRun's GPS tracking works OK too, but the "pause" "lose all your
activity data" bug is pretty bad. The bug's been around for more than a
year now, who knows when they'll get it fixed?

[MBwalkingMB]

When I unpaired MobileTrack from my device list on the Fitbit app my GPS walks worked perfectly. I don't know if that did it or the app update but something changed and my GPS connects and stays connected now and for several walks (daily). I'm using an LG phone (Fiesta, Tracfone - nothing fancy) and it is not on the Fitbit approved list.  I also use the 'Keep Alive' widget.  Hoping you all connect soon -

[Gizjones]

@BamIAm,

Thank you for all your suggestions! I went on a hike today on some mountain
bike trails in the woods. I turned GPS to phone only, turned off Bluetooth
scanning and checked my phone's GPS signal. All good. I checked my phone
regularly throughout my hike and it stayed connected! I even answered a
phone call and stopped to the my shoe. (the workout paused and then resumed
with no problem) The only problem was the mapped hike... It's the second
map. The mileage is accurate. It just didn't trace my hike for the first
bit. Mile #1 is where it's supposed to be though. Not a horrible problem.
The first map was my run yesterday. You can tell what a difference changing
those settings made!! Thank you!!

[mynameisnick4]

The connection/GPS lock on the phone didn't matter. This is proven by Strava and Google Fit having accurate distance tracking AND my bluetooth headphones working just fine during my runs. The problem is the fitbit app and/or the hardware. And no, all these crazy steps of disabling wifi, rebooting, resetting up, etc are not solutions. They make fix it for a little bit but it never lasts.

I did however fix my problem. The versa went back and I got a garmin watch instead. My runs have been tracking perfectly, granted it's using the watches GPS. I'm sad that all my fitbit data is going to be stuck there (minus all my runs, I exported those) but this new watch seems to be my solution.

[Sacul]

Exact same issue here. Absolutely unacceptable for the price paid. Did they not even bother testing this?

I kept the screen on the Versa and it says "connecting" half of the time. This is after I wait for the initial connected message before I start my run.

Please fix this issue. I have been a long time customer of Fitbit products and jogging with my Versa was something I was looking forward to.

Run #1

MapMyRun Distance = 3.19

Fitbit Distance= 2.67

Run #2

MapMyRun Distance = 3.22

Fitbit Distance = 2.77

Run #3

MapMyRun Distance = 3.19

Fitbit Distance= 2.78

[Ashley1984]

Which Garmin did you get? 

Does the phone app sync data well?

[mynameisnick4]

I went with the vivoactive 3. I'd said it's comparable to the Ionic. It tracks my runs perfectly and also provides advance data that fitbit doesn't like cadence. The screen isn't as nice as the fitbit screens but it's serviceable. The app is nice and syncs with strava perfectly. Most people would probably see fitbit's options as more "fashionable" and "attractive" as well.

In my short time with it I'd say garmin is better for people that want more out of their watch when it comes to running, biking, etc where fitbit is better as a standard activity tracker for the average person. If they can fix the issues with the versa it would be a really awesome device.

[Abeachgirl]

Same here!  Phone with me on run, and versa constantly shows connecting. Total run miles off by 1/2 mile or more and pace off by over 1 min mile. So frustrated!