Fitbit app draining phone battery

[ultravista]

Samsung Note 8 (One UI 1.0 / Android 9) with the Fitbit application installed is having problems with bluesleep wakelocks.

In 17 hours, bluesleep wakelocks occurred 22,910 times. The Fitbit application is the culprit. The phone doesn't deep sleep because of these wakelocks.

Without the Fitbit application installed, bluesleep is nearly measurable. I can get 3 days from my Note 8 without the Fitbit application and maybe 1 day with it installed.

This is absolutely attributed to the Fitbit app.

All day synch and always connected are disabled in the Fitbit app. Disabling bluetooth of course stops the wake locks too. On the Fitbit, I turned off 'use phone GPS' for all device applications.

What can I do to stop the Fitbit application from causing so many wakelocks? Allow background data is also turned off for the app ...

Moderator edit: Subject for clarity

[RicardoFitbit]

Hi @ultravista, welcome to the Community Forums! 

Thanks for bringing this to my attention, I understand your situation and how frustrating this matter can be for you. I'd like to let you know that we are always striving to improve the Fitbit experience with our products and services, therefore, the feedback that's shared here in the Community Forums is always appreciated and really helpful for us to evaluate our procedures and make sure that we are delivering what our users want and need. We are aware of this situation and working to resolve it in a timely manner, please keep your Fitbit app up to date.

Let me know if you have any additional questions.

[tlab12]

I have the same issue with a Fitbit Charge 3 and Samsung Galaxy S8 running Android 9.  Since installing the Fitbit app my battery drain has significantly increased.  I have All-Day Sync and Always Connected turned off. 

When my phone is sitting on my desk not being used it drained less than 3%/hr before installing the Fitbit app and linking my Charge 3, and ~8%/hr after.  If I disable Bluetooth on my phone, the battery consumption is again <3%/hr.  If I enable Bluetooth and uninstall the Fitbit app it is again <3%/hr.  From the battery monitor software I have installed it appears to be nonstop bluesleep wakelocks from the Fitbit app.

Please fix this!  For now I need to keep Bluetooth disabled most of the day and am missing out on receiving phone notifications on my Charge 3.

[ultravista]

I confirmed that the Fitbit app is creating the bluesleep wakelocks.

If I only force stop the Fitbit application, the bluesleep wakelocks continue despite the Fitbit application not running. 

If I remove location permissions, the bluesleep wakelocks continue.
When I remove the Charge 3 as a bluetooth device, the bluesleep wakelocks stop.

The Firbit application permissions (all permissions ~Android) has non-configurable permissions to 'prevent phone from sleeping', 'access bluetooth settings', and much more.

I believe the Fitbit application is constantly seeking the Fitbit regardless of the settings and therefore won't allow the phone to deep sleep. The bluesleep wakelocks are Fitbits way of preventing the phone from sleeping.

--

With the Fitbit application disabled and the Charge removed from Bluetooth devices, my battery is normal. With the Fitbit application running, no continuous synch, the battery drain is very apparent.

--

My phone and Fitbit application are up to date ...

[tlab12]

@ultravista  Thanks for the additional details and confirmation that it is the app creating the bluesleep wakelocks.  I hope the developers fix this soon.

Another way I found to stop the wakelocks is to simply log out of the Fitbit app.  This doesn't require removing the Charge 3 as a bluetooth device.  What I've been doing lately is just logging into the Fitbit app once in a while to sync my data, then logging out as soon as I'm done. 

[ultravista]

Thank you for this fix. I tried it and it worked. Who knew logging out was
the easy way to get the job done.

[tlab12]

@ultravistaare you by chance using GSAM battery monitor to debug the bluesleep wakelocks?  I am too, and after the latest GSAM app update 2 days ago, it no longer is reporting bluesleep wakelocks.  The battery drain is now being reported as "Kernel (Android OS)" time held awake.  I'm not sure how to dig any deeper than that. 

I did a test where I left my phone logged into the Fitbit app one night, and then logged out the next night.  When logged in my phone lost 34% over just under 8 hours, and when logged out my phone lost 12% in just under 8 hours.  The difference was held awake time.  When logged in to the Fitbit app my phone was in Deep Sleep 37% of the time and Kernel (Android OS) held my phone awake 4h 58m.  When logged out of the Fitbit App my phone was in Deep Sleep 91% of the time and Kernel (Android OS) held my phone awake 37m.

Fitbit developers, please fix this!  I'd like to be able to stay logged in to the app so that I can receive phone notifications, which was one of biggest selling points of a Fitbit device for me.

[leowood]

thousands wakelocks a night, fitbit sense with latest app,  20% battery drain 1 night, if kill the process of fitbit in backround ,then 3% battery drain for 1 night.