Versa connected GPS issues

[ironcream]

FitBit Versa won't connect to a "Connected GPS" when I want to record my runs.

Keeps showing "Connecting...." animation indefinitely whenever I want to start my run.

Animation stays there throughout my run.

Doesn't seem to connect IN the run.

In rare cases when it connects, it drops that connection pretty fast.

GPS data is garbage.

Example photo while I was trying to record "a run" walking my dog just today:

My gear:

• Android 8.1.0
• FitBit app 2.77
• Versa firmware 32.32.10.15

Somehow it works with my old tracker, but not the Versa

Same exact smartphone, same app and same locations I do run and record GPS data flawlessly with my Charge 2. It's the Versa which is at fault.

Workarounds that don't help

I have read forum here and there and here are the workarounds I have tried (none worked):

• making sure I have un-paired and removed my old Charge 2 from the fitbit account and phone settings
• removing all the bluetooth devices paired to a phone
• removing and adding Versa to my fitbit account and phone again
• factory reseting my Versa and setting it up again (TWICE!)
• restarting my Versa (3+ times every time)
• disabling all the bluetooth related music functionality on my Versa
• somebody said that removing/altering autolap function on run setting would help, so I tried this as well
• I have also seen somebody managed to fix things by setting up Strava integration. So I did that as well.

NONE of the above managed to fix Connected GPS issue.

Versa still fails to connect to my Phone's GPS which my old Charge2 has no issues with whatsoever!

Next workaround I am going to try

Somebody reported that downgrading FitBit app to a version 2.74.2 * or below seems to help.

I will try to do that next and will update this post.

Some thoughts on Versa-to-phone connectivity

It looks like Versa maintains connection with my phone otherwise as it keeps pushing me notifications and such. Emails, calendar, WhatsApp.... all that works.

But Connected GPS.... dammit. IT DOES NOT WORK!

Please acknowledge the bug/issue and give us single thread to track or something.

This piece of functionality is why I bought this device and for these money it should be working smoothly!

[WillowOz]

How did you go with the roll-back for cycling, rwheatla33?  

The only solution for the Fitbit with all updates I've found is to NOT use the manual or auto stop feature on the watch at all.  I went for a couple of 50km rides over the weekend, and found if I paused Strava on my phone, the watch tracked fine, but if I stopped tracking on the Fitbit, our favourite message "connecting...." appeared.  Not great if you're really worried about your speed/BPM averages so I'm still trying to decide if I should roll-back or not (mainly because I'm not really IT savvy so it'll take some research and hope for me to actually get the rollback working)

Willow

[rjglaw]

I experience the same problem and a possible solution just hit me, like a thunderbolt out of the California sky:  Run the Fitbit app on your/our cellphone concurrently with using the Versa.

Here's my thinking:  The cell phone does a fine job of capturing location data, and apps running on the cellphone, like Google Fit, Strava, MapMyRun, whatever, all show good data.  It's how you know the Versa data is off.  And of course cell phone apps have no connection problem.  All the other appss do a great job.  I though of just switching to those.

But I remember using the Fitbit app on my cellphone before I got a Fitbit device, just to check it out.  You can do that.  And the app worked fine that way.

Then I got my Versa and figured it would just display what the cell phone app did, but the app is sort of manual - you have to click it on to record an activity.  I seem to remember it got different data than the Versa, which Fitbit had to correlate and I think it took the higher numbers, which were always the ones on the phone app.

It's been a while since I've worked that way, with both running, but I'm going to give it a try this coming week and report back.

It's not the most elegant of solutions, even if it works.  You've got to click things on in the app, and the device, and I'm not sure what exactly the device will display.  Probably the device will be uncorrected until you're done, at which time everything will sync within the Fitbit death star.  So while you're working out, your data will be a bit off.  And I'm not sure all features are the same on both.  I'm not sure about autopause, for example.

But, still.  It may get good data into the Fitbit ecosystem.  

[fueledbycoffee]

I want the watch to display accurate data while I am running otherwise then
watch is useless. If I just wanted post run info I could.use strava or
other better than Fitbit apps for tracking purposes.

[rjglaw]

Yup, this is certainly sub-optimal.  I suppose the Versa will display some things correctly:  heart rate, time, for example.  But yesterday my distance was off by about 12%, or over a mile in under 10 mile walk.  I don't know if that is representative or not, but it was enough to get my attention.  

I still have to test out this approach.  It may be better or worse than I suppose.  Unfortunately, I may not be able to do that for a couple of days.  But I will report back.

[fueledbycoffee]

Currently I am just using another app to track my runs (I use it for
intervals) and send them to strava (I used to not send the data to strava
now I do b/c I can't rely on the watch data.. 2.87 also had issues w/ the
app dropping GPS too I found - it was definitely the app not the phone b/c
the other app didn't lose GPS). Its annoying b/c I also track w/ my watch
(so I have something i can look down at even if its not completely
accurate) and that goes to strava and then I have to delete duplicates and
such.. really i just want the versa to do what it advertises it can do and
I really want fitbit to recognize that they made things worse w/ the
firmware update and a number of app updates (2.74.2 was pretty stable -
every release since that has been problematic.. clearly they aren't
interested in fixing the issue)

[rwheatla33]

Currently on v2.89

Was unable to update my clock face settings on v2.74 so started using the latest versions a few months ago.

Sorry never got around to testing it on the bike

On either 2.86/87 the GPS started working well for walks and runs. Notifications were also working well.

v2.88 was installed and everything stopped working (no notifications to GPS) so I had to reinstall and then the notifications worked well but not the GPS.

v2.89 installed ok and notifications work but the GPS connecting issues after 30 secs to 1.5 mins remains.

I really don't believe that its a versa issue and feel that the issue is solely wth the android app.

[daggas66]

Simply put, Fitbit Versa is not fit for purpose.  Connected GPS is an absolute joke on Android, and has been since it's release.  Still not fixed.

Doesn't matter if it's walking, running, or cycling, it is absolutely garbage.

And before some Fitbit "guru" comes on welcoming me to the community, I've tried multiple versas with multiple phones, including "supported" (a joke compared to cheaper brands), and always the same problem.

I've spent more time trying to go from "connecting..." to "connected" than I have exercising for god's sake.

If you want GPS and mapped routes then go with a competitor like Garmin.

Fitbit are still at the juvenile level.  Just look at their challenges that center around steps!!  You can do a trillion steps around the house.  Why is there no option to base challenges around activity minutes???  A little more adult I think.

I've currently got my Versa back out the drawer, to see if fitbit have improved their she!t since last November, and currently my Versa, my android widget, and my Fitbit app all show different steps as I type!!!

It's going back in the drawer tonight where it belongs.

How Fitbit is still in business is anyone's guess, unless it's just a Versa/Android combo.

The missus has a flex 2 (also in the drawer), so I might just give that a whizz, but only maybe in a couple of months when my blood pressure has dropped.  It's even been a joke typing this reply on an Android phone.

[SunnyDay44]

I'm having the same problem with iPhone.  Tried multiple workarounds like OP did and all I see is "CONNECTING...CONNECTING...CONNECTING".  I got it to work twice out of about 20 attempts.  It's very frustrating.

[WillowOz]

I have dared not mention it lest I put the mocker on things (Aussie slang but you'll get it)... it's actually been working for me for over a month.  My versa connects,  the kilometres and times match up to a whisker even over a long ride, (80+km)  and the stats (eventually) sync with my Samsung J5 Pro android,  only a low/ middle spec phone. Using a bit of data,  but i can cope

No more updates,  Fitbit.  Leave well enough alone!

[paul_bikesd]

Thanks to WillowOz for the heads-up!  I had completely given up hope until I saw this post from down under! (unlike the Versa, the Fitbit community board actually works).

GPS connectivity on bike rides has been working for me (for the most part) over the past couple of weeks. Versa connects quickly 95% of the time and hasn't dropped me on a ride yet. So I'm cautiously optimistic. But, hey, I don't want to "put the mockers on" it either...whatever that means.

I'm on v2.95. Android Pixel 2XL running Android 9.

[Dewk]

Agreed. Absolutely ridiculous! Just a  glorified pedometer. Have to use strava to track my runs, don't know why i spent money on the versa when the free strava app does a better job.... 

[BluePhire]

I can say this issue STILL isn't resolved.  I never had this issue with my Surge with sadness passed away ywo months agao after 4 years of service, so the versa was its replacement.  It will initally connect and then lose it and the frustration level is mounting with a company that i sung its praises for a very long time before now.  I will try thw strava app and see if it can save this colossal clusterf*ck that is the the versa.

[Sstjacques]

How do you roll back? I have this problem in my phone too, after 1:30 it still says ive 9nly biked .29km

[tecishere]

Its big known problem that doesn't look like its getting fixed any time soon i'm afraid. There's a big thread here:

https://community.fitbit.com/t5/Versa-Smartwatches/Distance-on-GPS-map-doesn-t-match-with-exercise-s...

[tecishere]

Its big known problem that doesn't look like its getting fixed any time soon i'm afraid. There's a big thread here:

https://community.fitbit.com/t5/Versa-Smartwatches/Distance-on-GPS-map-doesn-t-match-with-exercise-s...