GPS

[Kersa]

GPS will not stay connected on the Versa.  I've attempted to chat with no results.  Customer service did not know one product from another and suggested I send the Versa back, rather than give me suggestions or solutions.  

The GPS may take a bit to connect, but it will eventually connect.  Moments after leaving my driveway (for running, biking, etc) it becomes unconnected.  No tall buildings, etc.  Has anyone else had this issue?  I've followed some of the suggestions in the forums with no luck.

[ozianscott]

I have been having the same issue.  I try to connect for rides, even short commuter rides, and there's nothing to indicate that it had connected or not.  I go on faith, basically.  Sometimes it works, sometimes not.  It logs the miles and other stats, but no map and no auto sync with Strava.  

I wish I knew what to do to avoid this.  

[Marrrmaduke]

@ozianscott @Kersa Phone model, OS?

A few ideas:

1. Make sure Fitbit mobile app is not being optimized by Android. Go to your phone's battery settings and disable battery optimization for Fitbit app.

2. Lock Fitbit mobile app in the background, so it doesn't get killed by Android. Please take a look at this thread.

3. In the Fitbit mobile app, tap on Versa icon in the top right corner, and scroll down to Keep Alive Widget. Enable it. Also, enable Always Connected.

[ozianscott]

I'm on iOS.  I'll try #3 and see if helps.  If you have an iOS version of the first two that would be great.  I'll try a workaround on those too.

Thanks for the help!

[Marrrmaduke]

@ozianscott Yes, set #3. Re #1&2 as long as you have Background App Refresh for Fitbit app enabled in your phone Settings along with Location Services (which you for sure have per Fitbit app requested permissions), that should cover it. You can try keeping the app open during your rides as well and see if display going off kills GPS connection. As a side note, you start your rides manually on your Versa right?

[Kersa]

Thank you for your reply. I'm using Android and will try your suggestions
shortly.

[ozianscott]

Great!  I think I saw that the Background App Refresh is enabled but I'll double check.  I star the rides manually from the Versa.  It worked perfectly on a long ride last Saturday.  What's tricky for me is knowing if it's actually connected to the GPS - the device doesn't tell me.  It keeps showing "connecting" before I hit the "start" icon, but also displays "Let's Go!" I'll be sure to watch that it syncs with the phone app before heading out.

Thanks again so much for the help!

[Marrrmaduke]

@ozianscott it should show the km as the top stat if it's connected. Otherwise it keeps saying connecting. 

[Marrrmaduke]

@Kersa Great. Also, please share your phone model and Android version. Unless you already have and I missed it somehow... 🙄

[Kersa]

Hi there, yes I am Android, Samsung J7

[Marrrmaduke]

@Kersa Great! Let me know if the tips worked for you. 😊

[TK71]

Hello all,

I have chatted with support with no luck. I have an S8+ phone. I tried all the settings spoken about previously. sometimes it stays connected and other times it doesn't . even on the same run routes. mileage can be off as much as 2 miles on a 6 mile run. very frustrating.

my wife and son have same issue with the Google Pixel 3 phone.

we had the surge with built in GPS and was great. didn't realize the versa was not built in when I bought 4 new ones for the family. expensive mistake. 

nothing worse then being on a run, trying to push yourself, look down to see your mileage to inspire yourself to push harder and see "connecting". ugh.. 

[Kersa]

I've had the same experience and understand your frustration. I've given
up trying to use it as an exercise tracker with GPS. Lesson learned and
based on the experience(s) I had with customer service, doubtful I'll every
purchase another Fitbit product.

[TK71]

on with support now again. they blame the phone. interesting because it seems to happen on every phone looking at all the community posts. I want my surge back!

[Kersa]

Yes, I had the same issue. They blamed the phone or assumed I was in an
area with either tall buildings or heavy forest. Not the case.

Good luck!