Versa 2 is connecting to GPS but not logging data after updating to Android 11

[J-Bone]

Since updating my pixel 3a to Android 11 I've been having issues with my Versa 2.

It's not been recording GPS with my runs, and the Fitbit app itself has become unstable and sometimes refuses to start and gets stuck on the Fitbit logo, or refuses to load data e.g. an exercise or a daily heart rate page.

The no gps is a killer for me as it was a feature I made almost daily use of.

I've tried reinstalling the Fitbit app which hasn't made a difference.

Moderator Edit: Clarified subject

Poster Edit: Rectified subject; moderator's change was inaccurate.

[MarreFitbit]

Hi there @J-Bone, welcome to the community forums. I'm sorry to hear that your Versa 2 stopped connecting to GPS and your Fitbit app is not loading your data after upgrading your Pixel 3A to Android 11. I totally understand how you must be feeling as you rely on GPS for your daily routines. Thank you for the details provided in your post and for your efforts in trying to resolve this issue, I will be happy to continue to assist you.

As a first approach, please verify the following requirements; then try the troubleshooting steps if necessary:

• Make sure that you have a clear view of the sky when you start the exercise. Environmental factors, including tall buildings, dense forest, steep hills, and even thick cloud cover, can interfere with your phone’s ability to connect to GPS satellites. If the signal is blocked—either because you're indoors, underground, or due to another reason—GPS won't work.
• Confirm that Bluetooth on your phone is turned on, and your device is connected under your phone’s Bluetooth settings.
• Make sure that phone is within 30 feet of your device.
• Make sure that your device can sync with the Fitbit app. For more information, see How do Fitbit devices sync their data?
• Confirm that the Fitbit app can use your phone's GPS sensors. For more information, see How do I allow my Fitbit device to use my phone's GPS sensors?

If you continue to have issue, please see if GPS connects after each step:

1. Force quit, and reopen the Fitbit app to refresh the connection with your device.
2. On your phone, go to Settings > Bluetooth and turn Bluetooth off and back on.
3. Restart your phone.

If the Fitbit app is still not properly working when you try to sync your data, please see: Why won't my Fitbit device sync? 

Let me know if you need further help, I'll be around. 

[J-Bone · Accepted solution]

I've now rectified my problems (though irritatingly my usual route is now being logged as 200m shorter than before 😞 )

For anyone else seeing this issue with Android 11: The default behaviour for GPS permissions in this version of Android is to only allow access to apps when the app is explicitly in use (i.e. In your hand with the the screen on).

For Fitbit devices without an on-board GPS (i.e. my Versa 2), the app requires access to GPS the background, so you must go to the GPS settings to allow access to Fitbit app all the time. YOU MUST DO THIS AS AN ADDITIONAL STEP - ANDROID 11 WILL NOT LET YOU SELECT THIS WHEN YOU'RE PROMPTED TO GRANT ACCESS.

Granting a host of other permissions has also rectified my issue with the app freezing on the Fitbit logo at startup.

[Aro8787]

Hi J bone thanks so much for this. I'm actually on Android 10 but I think the latest Xiomi MIUI 12 had this added. 

Could you clarify how you turn this setting on?

Thanks. A

[J-Bone]

Hi Aro,

Steps as follows for stock Android (may be a little different on MIUI):

1. Go to the Settings app.

2. Select Apps and Notifications.

3. Select "All Apps" to get a list of everything installed.

4. Select the Fitbit app.

5. Select "Permissions"

6. Select "Location"

7. Select "Allow all the time" (rather than "Allow only while using the app")

There may be some other denied permissions too, I've blocked things like Camera and Microphone but enabled Phone and SMS so I get the notifications to my watch.

[KLCWEST]

thank you! I was having the same issue, heading out for a run now, hope it works!

[tkelli]

Thanks, J-Bone! I've been trying to figure this out for a while now. It was these last instructions that did the trick!

[marcin84]

Thanks. Looks like it also suddenly affected Samsung Note 10+ with September update to Android 10.

The app should detect such situations and warn users!