2.75 seems to have broken GPS connection

[fueledbycoffee]

 My versa was doing really well staying connected to GPS or at the very least the app was tracking the route properly so I could upload to strava and fix the distance (which was usually a minimal fix).   Tuesday, Wed and today connection issues got progressively more and more and its at issue at the app level not the app and watch talking level b/c the map generated by the app is off too  - the app seems to have lost GPS connection as well and then tries to connect the points it does have with a straight line

My best guess is a version update.  the issue did seem to start before 2.75 was pushed out (since I had some issues on Tues) but they were much much worse yesterday and today so maybe tuesday was an unrelated hiccup??

Anyone else finding GPS connection issues at the app level?

[MakMak]

Hi, @fueledbycoffee! I haven't used it since the update, but I didn't have any issues with the previous version when I used it recently for a several hour long hike.

[Drewhosick]

I seem to have the same problem.  Didn't know if it was because I went to Android P DP5 or if it was the update to the Fitbit app, or the rubber case I bought for the Versa but I see it always trying to connect during a gps enabled walk and it works and then doesn't and then works and then doesn't.  I've also noticed the persistent notification about the connection will turn off and on 3 times when it is reconnecting.  Very weird.  Anyways, just installed the older version through another site and I'll see if that fixes it tomorrow.  Otherwise I'll roll back Android and see.

[fueledbycoffee]

last night for a short walk it connected and looked like it was still
connected (showed distance instead of "connecting") but I could tell it
wasn't connected b/c pace was 0 and the distance wasn't moving - this is a
walk I do all the time so I know the distances and it was basically half
the correct distance the entire time.. The exercise imported over into
strava and correcting the distance gave the right distance (maybe a hair
long) so at least the GPS file is right

this is so frustrating b/c I was having issues when I first go the versa,
had to exchange it b/c of it failing in the pool due to defective
waterproofing and when I finally got the replacement back it all seemed to
be great w/ minimal connection issues.. being a hair low and correcting in
strava is fine - if I run further than I think that is great but being off
by 50% kills its usefulness... Please do report back on if rolling back
fixes things. and post the site you use and I will try and bookmark it
before the moderators delete it like they did when people were posting a
site to roll back when there was the awful version that was eating data..
I don't get why fitbit doesn't have the older versions available on their
site - that is standard protocol for all the software I use for work.. you
always leave up older versions so people can roll back if needed or if
there are compatibility issues... Fitbit you are proving yourself to really
really really to clear out and completely replace your software team with
people who actually know how software should be written, tested and shared
- or maybe its just the software team leaders that needs to go (and lets
not talk about the fact that people have been asking for a year to have the
ability to see swim lap times in the app.. the data is there that is a no
brainer, no effort upgrade if one has remotely competent programmers on
staff - or leadership that actually lets them do their job)

[Drewhosick]

I have reverted to an older version and today or didn't disconnect for the 35 or 40 minutes I tracked a walk.  Can't say for sure that it fixed it but I'm guessing that's a clue that it probably is.

[fueledbycoffee]

I just rolled back as well and will report back after my walk tonight

[Drewhosick]

Okay, I'm calling it. I've had no issue on my second walk so far. It has to be the newest update to the Fitbit app

[fueledbycoffee]

My walk tonight was a hair short according to fitbit but no obvious
connection issues and the gps trace was perfect and imported into strava
for correction fine. Definitely back to normal after rolling back the app

It would be nice to have a new release that doesn't break something. Also
I actually had Google play set.to not auto update so I think.fitbit forced
the update through by telling google.play security fix... or something else
that overrides user settings . Annoying..

[ozonep]

Yep. The same problem.

2.75 broke GPS.

Fitbit, do something! 

I have a marathon run next Sunday, I need working connected GPS function!

[LanuzaFitbit]

Hello everyone! 

Thanks for sharing your experiences since the update, I'd like to take a closer look into this situation.

The first thing I'd like to ask is that you all read through, and follow, this help article. If after going through all of those steps, requirements and workarounds you are still experiencing the same issue constantly, let me know right away. 

Let me know if you have any further questions.

[fueledbycoffee]

already rolled back to 2.74 and everything is fine with 2.74 - its definitely 2.75. The issue was at the app level not the app to watch communication level (when its app to watch communication the app still records the GPS properly). I had already restarted both my watch and the phone

how about instead of breaking things with updates we get useful things like swim lap times in the app??? you know the data that fitbit is holding captive and refuses to allow users to access???

[Drewhosick]

I had already tried this before.  It's definitely 2.75 cause I rolled back to previous release and everything has been absolutely perfect on the older version

[Crazy-Fritter]

I'm using my backup phone running on wifi only (no sim), and running app version 2.63 to sync my surge, which has been working flawlessly for me since it came out.... I'm guessing maybe a year ago or so? I will NOT be putting the latest app on my new phone...... I never update a good working fitbit app, that's just asking for trouble.

I will continue to manually sync my surge to my backup phone until something quits working...... I'm guessing that'll probably be the surge since my backup phone is in excellent shape and has shown no signs whatsoever of slowing down in the least bit 😉

I do have to say my surge has been working very well itself tho 🙂

[kcronin]

I've previously had great luck with the Connected GPS feature, especially with the most previous Fitbit app version.  I waited to see if there was a proliferation of complaints regarding 2.75 before deciding to upgrade.  Yesterday was my first day tracking with 2.75 and it was a fail.  My Versa connected and disconnected repeatedly throughout my 7 mile walk resulting in a 10% loss of distance.  This route is one I've travelled hundreds of times while tracking and I know where to expect the distance cues.  Cues were off and examining my map after showed multiple jigs and jags indicating all the disconnect points.  Annoyed.

I've reverted to 2.74.2 which worked perfectly for me.  Not clear what advantage 2.75 should be since there is never a full disclosure of the "bug fixes" included in a new update.  But, I'm clear on the disadvantages of 2.75, poor Connected GPS (again).  *sigh*

[LanuzaFitbit]

Hello @kcronin, @Drewhosick, @Crazy-Fritter and @fueledbycoffee.

Thanks for reaching back.

Those running version 2.75, please let me know the following:

• What Fitbit do you have?
• What phone are you using?
• Is the GPS signal being received by your phone constant and strong?

Let me know if you have any further questions.

[kcronin]

@LanuzaFitbit. I have a Versa SE. My phone is a Samsung Galaxy S7 running Android 8.0. My phone's GPS is solid as evidenced by tracking with the Strava app on my phone. I reverted back to Fitbit app version 2.74.2 and I've had constant GPS and good connection between my Versa and my phone. I've traveled this route 100's of times. Phone is quite hot when I'm done after about an hour. Mobile data use seems ok. Weather here is hot and my phone tends to heat up for other CPU intensive apps. Dropouts do not occur in consistent locations that would suggest weak GPS signal.

[SunsetRunner]

I have the same issue since 2.75.

Got my Fitbit about 3 months ago and never had a single issue with connected GPS until now.

Fitbit Versa Special Edition, running the latest firmware.

I'm using a Nokia 8 (Android 8.1), settings for highest GPS accuracy are enabled and Fitbit is allowed to run in background.

Checking Google maps when the GPS connection drops on the watch, reveals that my phone is not the problem, my location is very precise.

Bluetooth is stable as well... Not only am I using a BT headset while running, without issues, but I'm also still getting notifications on the Versa.

The problem usually starts close to, or shortly after 5km of distance (or about 30min into my run).

This issue is very distracting during the run, frustrating and a demotivating afterwards, when trying to see how I did. I've even seen my cardio score drop, because of the missing distance.

[LanuzaFitbit]

Welcome to the Forums @SunsetRunner. Hello @kcronin.

Thanks for bringing this up and answering my questions. 

I'll be passing this information on to the rest of the team. As soon as we have some news on the matter we'll be sure to let everyone know about it.

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

[SunsetRunner]

Thanks for passing it along.

FYI, I've uninstalled 2.75 and re-installed 2.74.2.

Not only has this fixed a lot of the buggy and slow areas of the Fitbit app, syncing my watch is now twice as fast... most importantly of course, is the fact that the GPS connection issue is gone and everything works perfectly now.

I disabled auto-update in the Play Store for now, hopefully you guys release a fix soon (I kinda miss the custom emojis for quick-replies on v2.75).

[LanuzaFitbit]

Hello @SunsetRunner.

Thanks for that update.

The version 2.76 was released on the same day that you posted this. Maybe you could try downloading that version and seeing how it works for you. You can read more about in here.

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