gps is so unreliable

[keely289]

why is the GPS on the versa so inaccurate? I have to run with my phone usonf map my run app to log the correct distance! it's not just aliitle out I ran 20.49km this morning and the versa only logged 17km! 

[LanuzaFitbit]

Hello @keely289! 

Thanks for bringing this up and for letting us know the comparison to Map My Run.

I'd like to ask you a few questions on the matter:

• What activity did you select on your Fitbit? Run? Walk or Hike?
• Did you track with MayMyRun and your Versa at the same time with the same phone?
• How far was your phone from your Versa during the run? Where was your phone and in which arm do you use the Fitbit?

Look forward to your reply so that I can find the best way to move forward.

[keely289]

I always start both the versa first on a "run" and wait for it to vibrate
to say GPS is connected then start Map my run.
the versa and phone are both on my left arm.
the GPS on the versa is always out no matter weather I walk or run using
it, did a 10 mile/16km run last week and it only recordad 13km.
I do a walk daily that's 8km and it sometimes only records it as a 5km

[LanuzaFitbit]

Hello @keely289! 

Thanks for reaching back to me. 

Has this always been the case with the GPS or did it start recently? Also, could you let me know what phone are you using to connect to GPS? I'd like to take a closer look at the situation.

Look forward to your reply.

[keely289]

I'm using a Samsung j5, I've only had the watch for a little over a month
and yes it's always done it.

[LanuzaFitbit]

Hello @keely289! 

Thanks for letting me know.

In this case this is happening because the Samsung Galaxy J5 is not on the supported devices list. This means that the app is not fully optimized to work with that phone and so issues like this can happen.

As long as the phone fulfills the minimum requirements, Android 4.4 and Bluetooth 4.0, there is a possibility that it will all work. Having said that, we cannot guarantee that it will. Some users have mentioned that following these steps has helped them with their phone that aren't on the list, so maybe you could give it a shot.

Let me know if you have any further questions.

[keely289]

I'm getting really fed up with fitbits response to nearly every fault that
seems to occur
"it's not a supported device "!

[fueledbycoffee]

Are you using 2.75 or 2.76?  2.75 broke gps big time.  Try rolling back.to 2.74.2

Another thing that helped me with earlier versions of the app was to program in a long stride (calculated based on versa steps and distance from.external app)  I have also had good luck importing the run to strava and using the correct distance feature on the strava website (this didn't work for 2.75 bc 2.75 broke the gps for the app too)

[LanuzaFitbit]

Hello @fueledbycoffee and @keely289.

@fueledbycoffee Thanks for coming in to help and letting us know what has worked for you. Have you tried running the GPS on the 2.76 version of the app? 

Let me know if there are any other questions.

[fueledbycoffee]

Nope not going to try 2.76 since it's already been tested by a other user
and they found it was even worse than 2.75. Fitbit needs to start testing
software updates for basic things like will the app sync with devices and
will gps function. Before release. It's ridiculous that you all are
relying on users paying money for the privilege of doing basic testing for
you. If fitbit wants users to test instead of testing themselves then they
should gather a group and provide free devices to them or pay them or
something

[LanuzaFitbit]

Hello @fueledbycoffee.

Thanks for your feedback. Please know that we take all comments into consideration and are always looking for ways to improve the overall Fitbit experience.

Let me know if there is anything else I can help you with.