"Notification service not running" error

[Loutay]

I get this message every couple of days "Notification service not running. A phone restart is required to re-enable notifications on your tracker". It can take up to 3 or 4 restarts of my phone before my Fitbit Blaze will sync again. I have a Huawei P Smart.

Moderator edit: subject for clarity

[SteveH]

This seems to be a known issue at the moment. Keep an eye on the following thread which has the latest updates from fitbit:

https://community.fitbit.com/t5/Android-App/quot-Notification-service-not-running-quot-error/td-p/27...

[AlejandraFitbit]

A warm welcome to the Community @Loutay and @SteveH thanks for stopping by.

I just want to let you know that I have moved your post from the Blaze board to the Android App board, since I think that here you will be able to find more related topics about the Fitbit app.

About the issue you are experiencing, as mentioned by our friend, we are aware of the problem and are working to resolve it as quickly as possible, sorry for any inconvenience it's caused and appreciate your patience and look forward to getting you back on track.

You can keep an eye on this post for further updates.

Catch you later. 

[SunsetRunner]

Hi...I have been struggling with this notification service not running error. Restarting phone/tracker several times a day is obviously not a solution. I was lost as I tried all options offered by the app (all day sync, always connected, keep alive widget), and nothing worked. Latest firmware and app (Sept 2018), and still could not maintain a stable bluetooth connection between my Phone (Oppo) and Ionic, therefore SMS/email/call notifications were not coming through.

The solution that worked for my phone (Oppo):

1. Phone Setting -> Battery -> Battery Optimization -> Change Fitbit to not optimized.

2. Phone Settings -> Battery -> Energy Saver -> Turn off "Freeze when in background" option for Fitbit.

As nr. 2 suggests, the Fitbit app kept being suspended when in background.

This seems to work for me, for now.....

[MarekNeo]

I get this message every couple of days "Notification service not running. A phone restart is required to re-enable notifications on your tracker". Synchronization works, only notifications not working. Restart the phone does not help. The problem appeared suddenly. The android application version 2.90 (20213375), the phone Xiaomi mi 6 and Xiaomi mi 9. What's the problem?

[Lindsay21]

I am having the same issue, going on 3 weeks now with multiple phone restarts and a factory reset on my phone. I am so close to ditching Fitbit and going to Apple! This is my 2nd Fitbit in 3 years! With the price we pay for things they should last a lot longer than 1.5 years!

[D159]

I am having this problem too. I have uninstalled fitbit, got the latest version, same frustrating problem.  I can get a test call sometimes.  Then I get the stupid message again.  I am ready to pitch the Fitbit and never buy or recommend again.  It used to work great, but since I got a hauwei phone it doesn't work correctly.

[Loutay]

I have solved this by making sure my phone and fitbit are sync, if you shut down the app on your phone you will need to sync again so leave the app open.

Sent from my Huawei Mobile

[D159]

I do leave the app open

[SunsetRunner]

Hi myself jashwanth from India.. I've been using fitbit iconic from 3months even I am facing the same problem, notification error please restart your mobile.but after I restart it repeats the same..i don't know what to..i checked out setting and everything..but the results are same..even everything is fine I mean Wi-Fi and Bluetooth were on, the sync doesn't work it says "no device found", I've been restarting and refreshing the Cal notification doesn't come to my fitbit iconic. Very dissapointed 

[Lindsay21]

I literally had to buy a new phone, my phone was apparently outdated and
was not running properly.

[D159]

I have up and bought a Garmin.

[witek_1308]

 have same issue with Xiaomi Mi 9 and Mi 8 (I have 2 phones and 2 devices - Charge 3 and Versa) and this is interesting the device vendor has no clue how to help. These are guesses rather than solid solutions 

[witek_1308]

I was able to make it working after playing with battery settings. Interestingly I did it yesterday and notifications started working today suddenly. Because of that, I don't know what exactly which changed caused this but I have a feeling it was putting Fitbit to autostart. Anyways I think the best news is that it is possible to make it eventually working on Android after trying different settings. I hope it will work for good now

[Sholander]

On my Xiaomi Mi 9T Pro (MUI 11) setting Autostart to On, and in battery saver choosing "No Restrictions" and restarting the phone, solved my notification problems. With these settings Notification for Calls and Apps works as it should on my Blaze.

[pgoel6uc]

Thank you! The problem still exists, and your solution still send to be working.

I was getting tired it reinstalling the app every couple of days

[axlneo]

09/09/2020 still an issue and you are still a life saver !!

Thanks for sharing

[Spattrizia]

Hi Alejandra, I saw several posts about this issue since 2018 😱wouldn't it be possible to escalate and get a proper fix once for all? Thank you in advance 

[Cajahach12]

Dieses Problem besteht bei mir ebenfalls. Neu Starten des Telefons hilft auch nicht. Nur wenn ich die App deinstalliere und neu installiere klappt es mit den Benachrichtigungen, allerdings nur für einen begrenzten Zeitraum. Das nervt und ist schade, da diese Funktion schon wichtig für mich ist. Ich habe ein Huawei P30 Lite New Edition.

[Okim_Selim]

Old post, but maybe someone is looking at this now. On Android, you can just go into Settings>Applications>Application Manager and find Fitbit. Tap "Force stop" then for good measure, tap "Storage" then "CLEAR CACHE". Then open your Fitbit app and hopefully you won't have the error message anymore and notifications will work. When you just do a phone restart, some phones may cache the previous state and not actually restart the service but this forces the app to restart without any cached data.