11-20-2018 07:46 - edited 11-20-2018 07:47
11-20-2018 07:46 - edited 11-20-2018 07:47
I wanted to post that with 2.83 I received last night and my Pixel 2, and my Versa notifications are working better then ever. They are actually clearing from my watch when cleared from my phone! At least in the short testing I've had this morning.
I did noticed, again, that my FitBit app was set to not-optimized. I turned this back to optimized. Also, I'm surprised you can have the notification listener service running without a notification. Is there a more optimized method for notification listening as it consumes a lot of RAM in the background.
Ted
Answered! Go to the Best Answer.
11-21-2018 06:51
11-21-2018 06:51
@JustPlainTed Welcome to the Fitbit Community! It's great to have you here! Thank you for sharing your experience with your new Fitbit app version and your Versa and happy to hear that it has been a positive one. Knowing this may help other members who update the app or are thinking about doing so. Also the app does require for it to be running in the background so it can manage the notifications.
I'll be around!
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
11-21-2018 06:51
11-21-2018 06:51
@JustPlainTed Welcome to the Fitbit Community! It's great to have you here! Thank you for sharing your experience with your new Fitbit app version and your Versa and happy to hear that it has been a positive one. Knowing this may help other members who update the app or are thinking about doing so. Also the app does require for it to be running in the background so it can manage the notifications.
I'll be around!
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
11-21-2018 06:55
11-21-2018 06:55
I thought I was the only one who is experiencing this, but my Fitbit app keeps reverting to "Not optimized" in the battery settings. Any ideas how to make it Optimized permanently?
11-21-2018 07:14
11-21-2018 07:14
Nope. I believe Fitbit is allowed to make this declaration on their own https://developer.android.com/training/monitoring-device-state/doze-standby#whitelisting-cases based on the "need" to always be allowed to run in the background without restrictions. However, I usually turn this to Optimized and find nearly no issues with functionality. This too seems to imply Fitbit might be "allowed" to make the Not Optimized declaration without user interaction. https://developer.android.com/training/monitoring-device-state/doze-standby#support_for_other_use_ca...
11-21-2018 07:57
11-21-2018 07:57
Thanks for the info. So you need to keep reverting it manually to optimized every few days?
11-21-2018 10:10
11-21-2018 10:10
I am not sure what triggers it. System updates, app updates both seem to be times I check.