RESOLVED 06/16/2018: "Notification service not running" error

[AlessFitbit]

Fitbit Update 06/16/2018

Thank you for reporting the error is not longer showing in the Fitbit app. This issue has been resolved with the release of the Fitbit app for Android, version 2.73. If you're still experiencing issues receiving notifications. Make sure to confirming that you're updated to the latest app release and following our notifications troubleshooting tips provided in this help article.

I'm moving forward in closing this thread as the issue has been resolved and there is no need to post future updates. If you have questions regarding the Compatibility of your phone, refer to this help article: Which phones and tablets can I use with my Fitbit watch or tracker?

Thank you for your continued patience as we worked to get this resolved.

_________________________________________________________________________________

Fitbit Update 05/09/2018

Hi, Android users!

Some of you may be seeing the following error message inside of the Fitbit for Android app:"Notification service not running. A phone restart is required to re-enable notifications on your tracker." Even if you perform a restart, the error message persists. 

Thanks for reporting! Our team has been notified and are investigating. We will make sure to update you all if we receive more information. In the meantime, we appreciate your patience. 

[SilviaFitbit]

Hey everyone! 

Thank  you so much for the details that each of you have mentioned. I've seen that some of you have said that are using non compatible devices, the reason why this may be showing is because your phone isn't listed as compatible. 

I've noticed in the past that users are able to sync or receive notifications with non compatible devices. However, since they aren't in the list. I can't confirm they will always sync or completely work with Fitbit. If anyone is using a compatible device and getting this error message, please provide me with the model and app version that you're using. 

Keep me posted! 

[mrforsythexeter]

What a poor response. You want people to use your devices, but you don't support flag ship phones. which tend to be around 6 devices for android, and 3 for apple at any one time.

This is a moving target, and the fragmentation in operating systems on the android side must be a pain, however notification watching permission 'android.permission.BIND_NOTIFICATION_LISTENER_SERVICE' has been a thing since API version 1 also you seem to know this, since you ask for permission. Based on this, you should be able to see and broadcast any message you want to watch.

Also, when was the last time you saw a phone with bluetooth?

Come on guys, if you want people to keep buying your products, then they need to be stable with the features you sell it on, no agros, or high street store is going to be happy checking every phone to see if its compatible.

[mrforsythexeter]

I just wanted to add, I had a little success with the mate 10 pro. It apparently has built in battery optimisation, which I found by searching for 'special access' -> 'Ignore battery optimisation'. Once, I told the phone it was allowed to ignore battery optimisation on this app (fitbit), I started getting notifications (after a restart).

So turns out, this is a "feature" of the phone, that fitbit would have no control over. However if they worked with partners a little closer (which may not be helpful when they have their own products) then we can all continue to enjoy fitbit products.

[Another-problem]

I've a pretty standard phone - Samsung s5 - and I've had no problems with other apps. It's also worked fine for a year or so with my fitbit and it only started the messages recently after a fitbig update.

Get Outlook for Android

[Wilkind1]

I have a Samsung Galaxy J3 which I believe is compatible & I am still facing the same issues

[FredDH]

I think mrforsythexeter may be on to something.  On my ASUS Zenfone 4, it also has a battery optimization feature (either part of Oreo 8.0.0 or ASUS specific UI).  On my phone, on Settings screen, under Battery->Battery Optimization.  I marked the Fitbit app to not use this feature and notification service appears to working.

[RopesNZ]

**ahem** so frustrating! Mine has been receiving notifications for months and now this message is appearing evertime I check the app. Why now? I am using a "non supported device" but that doesn't explain why it was working before.  At this point I'm thinking of selling my ionic had far too many troubles. If it doesn't get sorted in the next two weeks it will be up for sale.

[SilviaFitbit]

Hey everyone! 

I appreciate the information you've provided me. Once you get the app update which now should be 2.69, please download it and this should fix the inconvenient you're experiencing. 

If you're using a non compatible device, I can't confirm this will fix the issue as it hasn't been tested by Fitbit. 

Hope this helps! Keep me posted. 

[invertig0]

Got it this morning and my issue is fixed.

[octupuslau]

Hi,

I have the new version 2.69 installed and the notifications seem to work properly.

Steve

[stefanopoulos]

Mine also working.

Let's see if it stays

Tasos

[theresa71]

I did the update, but the text notification still is not working. How do I
check if my device is compatible? I have a Samsung S5 and it worked
without problem up until about a month or so ago.

thank you.

[ivoferreira]

Hi everyone,

I have the same issue. I have updated the app to v.2.69 but I still get the same error message: "Notification service not running. A phone restart is required...".

The phone restart does not sort the issue.

I have a Xiaomi Mi5s.

Sending a test notification from the app to the ionic seems to work. Don't know if this helps sorting the issue.

[Wilkind1]

I had the same problem but I unpaired from Bluetooth, uninstalled the app & shutdown my device. Then reinstalled the app & paired the device. Seems to have worked 

[djurkash]

 Using Xiaomi Mi Note3 which is"not supported", have updated to 2.69, and restarted many times since, both devices, but no success... Will try tomorrow to unpair and do everything from the beginning, but so far, stupid message always reappear

[octupuslau]

---

@octupuslauwrote:

Hi,

I have the new version 2.69 installed and the notifications seem to work properly.

Steve

---

Hi,

I was wrong, after restarting my phone the  "Notification service not running. A phone restart is required to re-enable notifications on your tracker." still pops up on Fitbit app version 2.69. No matter how many times I restart my cell phone ( Changed to Samsung Galaxy S9+) and my Ionic. No noticfications come up except caller ID. Strongly request fitbit team please look into it.

Steve

[Baronessgogo]

I have a Huawei P Smart, and have the same notification problem.  Apparently I am also not using a supported device.  I am extremely disappointed that this has stopped working, even after trying all steps advised in this thread.

[djurkash]

Don't be immediately disappointed, Ive bought it right after it went official, and suffered many issues so far but I expected so, and slowly they're solving one by one. It's the same with Garmin and Polar, and some other like Samsung, I wouldn't even put in the same context as above, because no matter how good HW they have, SW support is making it BS.

So, to both of you, justy remove ionic, then the app itself, the reinstall the app, and add the watch, and the stupid notification will disappear. Yes, it'll take some time, but it'll gone, trust me 😉

Thisstill doesn't solve call notification delay in my case, but I'll wait to that some day 🙂 

[Another-problem]

Someone suggested unpairing the Bluetooth and reinstalling the app. Now I can't get get it to pair! Time for a Garmin I think I.

[mrforsythexeter]

Please be careful with just removing and reinstalling. As sometimes pairing can be worse than this issue itself.

Also this may give illusion of the issue being fixed (updates, removing and reinstalling) as your device wont have time to learn that the app or service is using to much battery and just killing the service automatically trying to be helpful.

I personally would start with :-

• The first check should be to make sure that fitbit app has access to read your notifications, however this will be different on many phones, so you will need to search how to do this. The fitbit app itself, should detect this and take you a place where you can enable the permission.
• Looking for any apps which are killing the processes (apps or services). It maybe built into your version of android, or you maybe running a ram cleaner for example
• Then try the uninstall, restart the phone, reinstall the app and pair.

Hope this helps