Persistent "Connected GPS is Running" message on Android

[acookie1]

Just FYI -- Fitbit App Version 2.89 does not fix this issue.  I have version 3.8 installed onto my Samsung Galaxy S9+ phone and I was still getting the "Connected GPS is Running" permanent message on my device.  I just tried turning off Location in the app settings, so we'll see if this does the trick.  Thanks!

[RicardoFitbit]

Hi @acookie1, welcome to the Community Forums! Sorry for the delay in responding.

Thanks for bringing this to my attention, the details shared in your post are appreciated. Please keep me posted and let me know if after turning off the location services on your Samsung Galaxy S9+ the issue gets resolved. If not, please try the following steps:

1. Force quit the Fitbit app.
2. Uninstall the app from your mobile device.
3. Make sure that the Android version is up to date.
4. Reboot your mobile device.
5. Reinstall the Fitbit app.
6. Login using your account credentials.
7. Let me know if the issue persists.

Let me know if you have any additional questions.

[acookie1]

Hello,

I did all of that and issue persisted.  I turned off my location via the following on my Samsung Galaxy S9+:   Settings >> Apps >> Fitbit >> Permissions >> Then turn off Location.  However, when I turn it off, I then get another message saying 'Location Permission Required to Sync'.  I do not like having this message on all the time in order to sync to my Inspire HR.

Furthermore, I noticed a new issue w/ the Sleep tracking.  So in the daily display, the hours I've slept are correct. However, when I tap the Sleep "app" to go into the trending screen with only the Sleep details, the time doesn't match that on the dashboard display.  So for instance, I slept 8hr 15min the other night, but when I click it, it only shows that I slept 4hr 20min.  Why don't the 2 views match up.  This has happened twice now and it's skewing my historical resutls and sleep scores.

[acookie1]

Disregard the sleep item.. I see what it's doing.  It broke out my sleep into 2 separate parts, which is strange.  So daily view shows total and the detailed view shows the actual 2 sections of sleep.  Sorry about that... getting used to new display for this fitbit device.

[caseyby]

I have the latest version of Android and the app updated 3 days ago to version 3.10.1 I have been having this issue ever since. I tried your suggestions but did not help. I guess I just won't charge it until I can find a way to fix this. It is running constantly and using of more of my battery than any other app.

[Woobus]

I've also followed all these steps.  I'm on a Samsung Galaxy S9, unrooted.  I have the latest Android updates.  I have the latest version of the app.

I'm just keeping location services disabled. 

In other words, the issue is most definitely persisting.

Any updates on your end would be appreciated.

[Woobus]

Ever since my phone updated to the most recent version of the app (version 3.13), I am getting the "Connected GPS is Running" message in Notifications.  Which is depleting my phone's battery like nobody's business.

I already went over to the thread over here:
https://community.fitbit.com/t5/Android-App/Persistent-quot-Connected-GPS-is-Running-quot-message-on...

I followed all the moderator's instructions.  It did not fix anything.  So I figured I'd start a thread over here as well.

It's really disappointing that the only fix is to turn off location services, which for all intents and purposes disables the app.

Little help?

[caseyby]

I keep checking periodically after updates etc but the problem isn't
remedied. I just don't use the fitbit anymore, the drain on my battery was
too significant to be worth continuing to use it, unfortunately.

[mafpdx]

There are two threads on this issue; see https://community.fitbit.com/t5/Android-App/Constant-Connected-GPS-is-Running-Message/m-p/3535701#M1....

The message has ceased for me for now, but it took reinstalling the app twice, and repeatedly disabling location services.  So far today, location services are enabled and the message hasn't returned.  We'll see if that lasts.