Bluetooth Disconnect when phone locks

[IanSF]

I've just started having an issue with my Charge 3 and Android 9 (Nokia HMD 6). 

If the Fitbit application is open (I usually also have Endomondo running at the same time, but this is another issue), then the Fitbit will connect after selecting an exercise (eg: running, biking) after about 10-20 seconds. If I then lock the screen the connection drops.

Latest firmware on the Fitbit, similarly on the phone side. Fitbit is about 4 weeks old. GPS and Bluetooth are working perfectly on the phone - at least with other devices.  In the above case, the Fitbit is the only device connecting to the phone.

[JEG62]

Android uses aggressive battery optimisation. Try this it worked for me https://youtu.be/Z0iqx-l3cMg

[IanSF]

Doesn't help. Everything described in that video has been done and even the additional packages for battery management etc have been removed from the operating system. 

Support call now in progress with HMD/Nokia.

[maciek_b]

Same issue here. Please post an update if you get a solution from Fitbit.

[irishgirlce]

I've been having a similar problem with Android 9 & Versa 2.  I found that as long as I keep the Fitbit app open/on screen that the Versa 2 stays connected in Bluetooth & syncs properly.  Android, Versa 2 & Fitbit app have the latest updates installed.  The Fitbit app is not optimized.  It appears that something is preventing the app from running in background.

[ZeeSK]

I started having this problem when I switched to a new Android phone (Galaxy S20 Plus 5G) and I think I made a crack in the case: check your location permissions on your Fitbit app in your phone, make sure its set to "allow all the time" instead of "when app is in use".

After doing this, my Charge 3 remains connected for a few minutes on a run, but drops the connection afterwards. However, the second I look at my Charge 3 and have the screen light up, the connection is re-established. Screen goes dark again, connection drops off again. This must be some annoying battery saving feature, there has to be a way to turn it off.

Can someone try enabling all the time access to their Fitbit location permission and see if they get different results?

Thanks