12-09-2019
10:01
- last edited on
12-09-2019
15:39
by
SilviaFitbit
12-09-2019
10:01
- last edited on
12-09-2019
15:39
by
SilviaFitbit
I did the firmware updated today and everything is working great except for my notification still. When I have one come in it still isn't popping up or even showing up. I checked the fitbit app and it says that Notification service not running. A phone restart is required. I have restarted and turn my phone completely off and on with no luck. I have an S9 so I know that isn't the problem.
Moderator edit: Updated subject for clarity
12-09-2019 10:53
12-09-2019 10:53
@Kitsune99 Probably the process is getting killed by the Android. Please make sure Fitbit mobile app is not being optimized by Android (Android settings>Battery>Optimization>Fitbit needs to be marked as not optimized). Also, make sure Always Connected and Keep Alive Widget in the Fitbit mobile app are on.
12-09-2019 11:44
12-09-2019 11:44
I have the app already on not optimize along with everything else you said and it still says no notifications are allowed. I have also made sure that my notifications on the watch is turned on also.
12-09-2019 12:44
12-09-2019 12:44
@Kitsune99 Actually it is a knows issue for Samsung. See for instance this thread. There are several solutions mentioned. Perhaps you could try them, for example this one:
Settings -> Device care -> Battery -> Settings -> Sleeping apps -> Add -> Make sure Fitbit is unchecked -> Add -> Restart phone
12-09-2019 13:26
12-09-2019 13:26
Did everything the link told me and it didn't help at all. It actually made it worse as I wasn't getting phone call notifications on the watch as I was before. I turned everything back the way it was and my phone notification came back.
12-11-2019 19:13
12-11-2019 19:13
I finally just contacted Fitbit Support about this after going through everything and saying it was all correct this is what I got back: “We appreciate your cooperation in working on this. We’re aware of this issue and working to identify a resolution as quickly as possible. Thanks for your patience while we work to get you back on track, and let us know if you have any other questions.”
So it’s basically a known problem and they just haven’t gotten to fixing it yet because they want to get updates done on firmware first I guess.