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!

[ACG]

@ironcream

I believe you have checked out the user manual, next thing I would do is call headquarters, here is the link. 

customer support

[ironcream]

---

@ACG wrote:

I believe you have checked out the user manual, next thing I would do is call headquarters, here is the link. 

customer support

---

Hey @ACG!
Thanks for suggesting an answer in this topic.

Sure thing I did check all the manuals.

I am also familiar with the "Connected GPS" function very well as it worked perfectly on my Fitbit Charge 2. I know how it should work, but I am saying it simply does not work on my new Fitbit Versa 🙂

The store I got my Versa from confirms that people do return them saying that connected GPS is not working as expected. I am clearly not an exception.

So in the end I have just returned it. After owning it for 2-3 days.

Above in my original post you can see all the workaround-wannabes I have tried to no avail. Most of them are based on random assumptions which people (real life users!) had to make themselves, as there is no support from Fitbit on this issue.

Best explained solution I have seen so far in forums around comes from @kcronin who analyzed the sequence of android app releases and pinpointed one which works and one which did (presumably) introduce a bug.

Sadly, I will not be trying that workaround as I have now switched to another tracker brand.

Also sadly: some users, e.g. @Hotlush report that downgrading does not necessarily help.

Being a technical person myself it's easy to understand what a bug is and how they make their way to the production code. What I'm not getting is why FitBit would not acknowledge a bug and do the rollback while they work on a more permanent fix. I probably could have stayed with fitbit if I'd knew they were working on a fix.

The user @StarkRaven reported this issue back in May and no acknowledgment and/or ETA for a fix as of yet.....

If the app is really a reason and is "beyond repair" probably it's time to re-write it finally from the ground up 🙂 It doesn't even sync every time I pull-refresh it. Other brands` Android software does it reliably, for example. Somehow they got it, but Fitbit didn't.

Even though I have switched to another tracker now, I will be showing up here from time to time to see if this issue is (ever) going to get resolved.

Cheers.

[fueledbycoffee]

I feel like my versa connecting is worse n 2.77 - I am rolling back (again!) to 2.74.2

today i did 4.91 miles.. my versa thought I only did 4.08 and all my 5 minute lap paces are totally wackadoo

of course all the correct info is there in the app but fitbit has decided that the faulty watch should be the data that is kept instead of the GPS data there in the app (i run my tcx file through map my run when things get wackadoo)

[ironcream]

---

@fueledbycoffee wrote:

I feel like my versa connecting is worse n 2.77 - I am rolling back (again!) to 2.74.2

---

Hey @fueledbycoffee!

So you also say downgrading solves the issue for you?

Just trying to confirm here and narrow down the possible source of the issue.

[fueledbycoffee]

I think it was better today?  but today was a short run (20 min) so hard to say.  It was slow to connect but then stayed connected and final distance was reasonable (its a route I do frequently)

I am hoping rolling back fixes the issue (well really I am hoping Fitbit releases a version of software and firmware that actually work as advertised but that might be expecting too much)

[Kenatrex]

Did rolling back work?

I have this issue quite badly. One day it will work just fine. The next day, it will cut out 5 or 6 times over the hour-long run leading to a useless map. I have resorted to just running Strava on my phone instead of using the watch. Frustrating to not see pace on the fluand to miss out on the heart rate data for the run.

[fueledbycoffee]

Rolling back worked for me (mostly... today the watch was on crack... it
was misty so I wonder if that effect the BT connection? GPS was fine on
the phone bc I was running samsung health and it behaved just fine)

I always run a back up on my phone. Recently samsung health but planning
to try runkeeper

[topspin]

You know you are right when none of the "Fitbit" company people appear in your question thread. I have the same problem, forever "connecting". IMO Fitbit firmware is buggy and unstable. I did not know they have a list of phones that are supported devices, that's a favorite reason by the mods on these threads for all your problems. I have never heard of such a thing, my Moto phone running Android 8 is not supported,

they should have this info on their front page so I can NOT BUY the band and not go through weeks of wasting time to figure a solution.

[paul_bikesd]

I'm having the same problem with intermittent connected GPS on my bike rides. Sometimes I have trouble connecting. Other times I connect right away but get dropped about half-way through my 12 mile (40 min) bike ride.

This seems to have started after Android OS 9 update.

Pixel 2 XL Android 9.0

Fitbit App 2.81

Firmware 32.32.10.15

Very frustrating.

[WillowOz]

Same for me using a Samsung J5 Pro. I'll regularly cycle 40-50km but am lucky to have 4km show on the versa. It still decides I've exceeded my daily step quoter though- neat trick when my hands are stable on the handle bar and it's a pretty smooth ride on a road bike.

Guess the next thing is to roll back the versa firmware and app - but how do you do that?

[kcronin]

@WillowOz  While it is possible to rollback the Fitbit App version, it is against the rules of posting to provide the details here.  An internet search may help you.  It is not possible to rollback the firmware version you have.

You can try to improve your chances of a decent connection by ensuring that the Fitbit app is given permission to run in the background on your phone at all times and making sure that the "Always Connected" and "Keep-Alive" are turned on.  I agree that the Biking exercise is the worst for maintaining the connection for Connected GPS.  If you don't need to see the current stats on your wrist, you could choose to track your ride through a phone app like MayMyRide or Strava until Fitbit can sort out this issue.  

[solenkoliad]

Same here. N-O-T-H-I-N-G helps. 

What Fitbit want us to do now? 

Versa

Pixel 2

Android 9

Fitbit App ver. 2.83

[WillowOz]

Hi Kathy,

All permissions are enabled as is keep connected but I'll try the always on for the period of my next ride.  I track my rides with Strava and have the Versa app (which seems to record the rides only,  not track them live) but I don't like to keep the phone screen on in its cradle especially during our Aussie warmer months as the phone really heats up. 

Thanks for the reply though.  Do you think Fitbit take any notice of the faults which are obviously affecting lots of people?

Willow

[kcronin]

@WillowOz  I think Fitbit is fully aware of the issue.  I've had my Versa since its launch and I had a Charge2 prior to that.  There were occasional times when the Fitbit app version update would cause a Connected GPS glitch with my Charge2 and that was (usually) quickly settled.  The Connected GPS feature for the Versa has been an issue since the beginning with minor ups and downs since then but no solid improvement.  I suspect that's it's quite difficult to program for so many different phones and there are bound to be some that just won't work.  However, I think that this fitness device with its color screen, apps, smartwatch features etc just have too many things going on to then also make a strong, consistent connection to the GPS in your phone and maintain that.  So, while I did believe initially that Fitbit would find a solution for this issue, I've lost faith that it can happen.  If one needs accurate stats on one's wrist while exercising, best to get a fitness watch with a built-in GPS.  I don't care for the style of the Ionic and I don't have an iPhone so the Versa is really my only option.  I'm not training for a competitive event.  For what I need, general performance feedback, calorie burn combined with some nice smartwatch features, the Versa works just fine.  YMMV.

BTW, I mostly use Walk and Hike as connected gps exercises.  Mine works about 85% of the time for those exercises.  Bike is a dismal failure, imo.

[WillowOz]

Thanks again Kathy.  Like you I don't use iBricks. Phones are a handy necessity this days but nothing I'm going to pay top dollar for so the price and ease of using basic Android phones is ideal.  Otherwise after a rocky start (little things like not know about the "Versa v Versa Classic" Bluetooth differences for audio control) I'm pretty happy with the Versa after starting with a Pebble watch so whilst it's a shame,  I'll write the fitness tracking off I guess.  

[rwheatla33]

Like many I had a charge 2 and most of the time the connected GPS worked ok with my android phone (Xiaomi Redmi Note 4). Since I purchased my versa in September the connected GPS has been a problem and the issue where the GPS drops when the phone screen goes off despite the setting it to run in the background just compounds the issue. I have even tried installing an app to force the GPS to remain active however this has no effect.

Recently my versa wouldn't connect for more than 10 seconds and after reading through the forums etc I contemplated returning it as faulty and/or getting an Ionic. As a last throw of the dice I installed a previous version of the Fitbit app (as mentioned by a previous poster) and the early results are promising. I will continue testing over the next week or so and let you know how it goes. 

[rwheatla33]

An update on pay previous post - so far its been working very well, several walks and runs upto 9km and the GPS remains connected. In addition I've noticed that the WhatsApp notifications are working which was also an issues with the later app versions. Hope to test on a bike asap

[rwheatla33]

An update - upgraded to 2.84 and the same problems with the GPS disconnecting within 15-30 seconds occurred. Going back 2.74.2 which seems to work OK for running, walking and hiking. 

[fueledbycoffee]

Thanks for updating I was just wondering if I should dare update... guess
not