Versa 2 connected GPS wildly inaccurate.

[cbloyer81]

My wife had a Versa for a week, and now a Versa 2. Below is the results of her connected GPS run. It's wildly inaccurate. I wear a surge, and the GPS is pinpoint accurate. Is this the best she can expect from connected GPS? It's garbage if it is.

After doing some research, I'm wondering if it is because she is using bluetooth earbuds and interrupting the connection with the GPS?

Moderator edit: Updated subject for clarity 

[SunsetRunner]

Hi @Asub0 what do you mean by low power mode?

[Asub0]

The best answer for this post by cbloyer81 says “I figured it out, she was on low power mode. It works great now! Low power mode was shutting the app down.” I have the same issue and would like to know how to do that.

[SunsetRunner]

What phone do you have, Android or iPhone? It sounds like they mean battery saving mode which prevents apps from running all the time in order to save battery.

If on Android, long press the Fitbit icon and tap on the 'i' which is usually in a circle, then tap on advanced and then battery.  Make sure battery optimisation says 'not optimised' which it should be default but if different, tap on it, scroll down and select Fitbit and ensure 'Don't optimise' is selected.  Mine also says that 'background usage cannot be restricted' and also cannot be changed.  For iPhone i'm not sure as I don't own one.  Hope this helps.

[Asub0]

Thanks Mark. I have pixel 4 and battery is not optimized for Fitbit. When I use the exercise - walk mode on my Versa2, there gps saiys connecting all the time unless I manually open the Fitbit app. When I open the app it says connected and as soon as I close it, the status goes back to connecting. The walking path is inaccurate since it doesn't connect to gps unless I keep the app open during my walk.

[Sabby150]

Hi, what is low power mode?

On the device, or on the cell phone? please explain

[Asub0]

If you are asking me, the reason I asked is because the best answer for this post had this "I figured it out, she was on low power mode. It works great now!" I wanted to know what he meant by low power mode. My Versa2 GPS always says connecting unless I manually open my Fitibt app on my Pixel phone. My app on my phone is not optimized for the battery, so it's running all the time. I am not sure why Versa won't connect to my phone GPS automatically.

[JoanWR]

How do you know if you are set on low power mode?  My Versa 2 is not calculating distance correctly. It is 20% off. Do I need to carry my phone with me?

[Asub0]

I do carry my phone with me and after I changed the location to "always allow" instead of "allow only while using the app" , the GPS connects without any issues and is accurate.

[lsmlsm]

Hi, certainly disappointing to learn that two years on, the same issue of wildly inaccurate GPS remained. I stopped using Fitbit 10 months ago (partly because of GPS unreliability) and moved to Strava which then had no GPS hitches ever since, on same run routes. It was a leap of faith, but 2 weeks in from taking up the Versa 2, frustrations of my records going haywire are restarting all over. Now with the Versa 2 having to rely on the same phone GPS, I couldn't understand why - despite activating GPS at all times, allowing the Fitbit app on my phone to run in the background, deactivating low batt mode - the GPS records were totally off consecutively just this week alone. Once with the start and end point simply connected in a ridiculous single straight line (???), and others with these "straight lines" appearing mid-runs till end point, cutting across the middle of non-linear paths. My Versa 2 is running on firmware 72.1.15; Fitbit app on iphone 7 is running on version 3.15. If you could point me in a feasible solution to overcome these issues, I would truly appreciate your help.