Can't stay connected to GPS

[FoleyM]

Connection has worked flawlessly until recently.  Now bike rides track the first .75 miles then done.  I just got a new Galaxy S20 and not positive but think this issue started with the new phone.

Not sure which Versa i have..I think Versa 2.

[Gorbs]

Versa for me with a Pixel 4, hasn't been staying connected for a week or so since I applied a firmware upgrade on the Versa

[ChasPro716]

Versa 2, Android 11

Until recently, connection occured by starting exercise from watch, and maps in connected gps walks were correct.

For the past few days, I've seen Connected GPS notification banner but versa didn't say it was connected, until I launch the Fitbit app itself. Then only a few yards are mapped ... as if the screen turning off on the phone also kills the connection ... with no failures or status on the versa that the connection is dropped.

All walk stats are correct and even the short 10 ft map line is labeled as 1.25 mi.

[jmchin]

I have updated to Android 11 and I have found when starting an activity from my Charge 2 it picks up the location without an issue. As soon as the Fitbit app is in the background or I turn the screen off, my Charge 2 no longer is connected. I have changed the Permissions to allow Location all the time for Fitbit but it didn't fix the issue.

I have contacted Fitbit Support as I believe it is an Android 11 issue but I get the standard response of resetting device, reset phone, uninstall/install, etc. I need to start the Bike activity from my Fitbit device as the Bike option is not available in the Fitbit app.

[ChasPro716]

I proved today that as long as the Fitbit app is active in the foreground, with the screen on, the connection is maintained and the map tracks that whole time. A few seconds after the screen is turned off, or the app is put in the background, everything stops tracking.

We need detailed configuration instructions for getting the Connected GPS services to work on Android 11.

[jmchin]

@ChasPro716 Good to hear that I'm not the only one that can replicate the issue. I'm lodging a ticket with support and they mentioned they have not received similar reports. Could you also lodge a ticket with support as well. I believe it is an Android 11 issue and starting the activity from the Fitbit device and not the Fitbit app.

[FoleyM]

That sounds right to me. Do you think this is as a result of a Fitbit
firmware update or an issue with the latest Android OS?

[FoleyM]

How do you lodge an issue with Fitbit tech. support?

[Ramzi]

I have the same issue with an S9. It started in mid September. 

[jmchin]

@FoleyM I think the issue is with Android 11. I haven't received a Fitbit firmware update on my Charge 2 for a while.

Having said this, you mentioned you have an S20, what Android version are you on? Usually only Pixel devices would be on the latest version of Android at this stage.

Lodge a ticket here: https://myhelp.fitbit.com/s/support?language=en_US

@Ramzi What version of Android are you running? It might be a different issue to the Android 11 issue that I'm reporting.

[ChasPro716]

I have solved the problem and tested it today. I read a post that provided detailed instructions, but now I can't find it again (I will continue looking and post again if found).

Basically ... Yes, this is a Fitbit App on Android 11 configuration issue that can be fixed by users. When the Fitbit App is granted its basic privileges, including Location services, the default setting is "only while I'm using the app". You have to go in through the Settings, to Apps. Find Fitbit, and visit its list of privileges. Under Location, review the options. Select the "allow all the time" option.

There are also Android 11 battery saver options that need to be changed to "do not optimize" for the Fitbit App specifically. Under the same App info for the Fitbit App, select the Battery item. Change the Battery Optimization setting to "not optimized".

That should do it.

Best of Luck everyone.

[ChasPro716]

@jmchin, see my solution posted today.

[jmchin]

@ChasPro716 Thanks for the details solution. I actually tried both settings earlier.

Changing the Location Service to allow all the time is definitely required. However, changing the Fitbit app to "Do not optimise" is a workaround solution and needs to be fixed properly by Fitbit and/or Google.

But I found that my Fitbit would not maintain a connection to my phone for my entire bike ride. I checked my Fitbit every now and then and could see it would lose connection. This can be confirmed by the distance travelled was shorter for my usual ride (1km shorter for a 4km ride). I do not think the Do not optimise solution fully works. Did find this problem as well?

[jmchin]

I just got an update for the Fitbit app, a short test looks like it may have fixed the issue. I'll need to go for my regular bike ride to see if it does not lose connectivity. I changed my setting back to Optimise the Fitbit app.

[ahancoc86]

I'm replying to the issue saying it's with Android 11. I have Android 10 on my Moto Z4 and this started occurring recently to me. Based on this thread I went in and changed permissions to allow all the time, so I guess I'll see on my walk this afternoon if that fixes it. Because for now it shows I walked 2 miles in my driveway, which is only 50 feet or so.

[jmchin]

Fitbit App Version 3.31.1 doesn't fix the issue.

[eagle1007]

Mine has been showing the distance and information is all there like distance ran but no map and gps loses connection several times during the run.  I've already tried Uninstalling the watch from the app and from my Bluetooth as well and no changes.  

[FoleyM · Accepted solution]

I think my solution was that Fitbit didn't automatically fully pair with my
new Galaxy S20. It appears that it stayed paired to my old S7. When I
removed that pairing and re-paired to my new phone it appears that the
problem is solved. I have only taken a short bike ride to test but GPS
stayed connected and fully reported the ride. I'll be taking a longer ride
today to confirm.

[Ajruss]

I get that same issue. At certain points in my run I've been pulling my phone out and syncing.  I'll get gps data points, but it doesn't log the full map. I've tried allowing gps to be on on the background from the fitbit app and that didn't fix the issue.  I had updates to both versa lite and my Samsung s10 about a month ago and that's when the problems started.