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. 

[KiwiDalang]

I don't have an SD card,  so that's not the issue

[octupuslau]

---

@KiwiDalang wrote:

I don't have an SD card,  so that's not the issue

---

Hi,

Sorry to hear that, I think moving the data back to the phone just works for some users only. Is your phone on the compatible device list?

Steve

[PaulHaines]

Me too - no SD card.   So I think it may be the issue for some phone users, but that is not the root cause.

[KiwiDalang]

No, and that’s one reason that I bought a Fitbit rather than an apple or Samsung. I bought it before Fitbit started with this compatible devices script. It seems to work with the Fitbit notifications app. So if some guy writing software on the side can get it going, it seems to me a big outfit should be able to do the same on their own h/w. Especially when they bought out the team from pebble who could get notifications going reliably.

---

[YY2]

I am using charger 2 and huawei mate 10, still getting "notification service not running" after I tried following:

1) reset BT (unpair)

2) reinstall app (2.69)

It is already allowed to run in back ground, it is exempt from battery optimization

I also got this: Fitbit cannot forward Android notifications to your tracker. Restart blah blah. (same message after restarting both app and tracker)

[Chingyq]

Despite removing ionic device and adding it on fitbit app and phone , the error message stating  "notification service not working, restart phone " still persist.

I have also tried uncheck notification app, restart phone and recheck those app again but to no avail.

I believe this is a software bug. The notification service is important for me as my phone is usually in my bag. Hope fitbit could patch this bug asap. 

[RobertoME]

Hi there everyone! My apologies for my absence since my last interaction. Thank you all for trying the previous suggestions and workarounds.

Note that with non compatible devices is not an statement the app won't wok, is just that certain misbehavior like the one discussed here, can occurred due to the app is not optimized to work with the device in question, as I mentioned earlier.

If the issue continues with the new version of the Fitbit app for Android, please feel free to share screenshots of this error and let me know which model of phone are you using. I have seen some of you have done this already. This with the intention to gather all the possible details and investigate further.

See you around, I'll be looking forward to your responses.

[Homegirl]

This message just popped up for me this morning.  After following a bunch of suggestions and nothing working, I just uninstalled and reinstalled the Fitbit app on my phone and now the message is gone and I just received a text message.  So, I would say to try to uninstall.

[djurkash]

We all did that, but after some time, it happens again... You'll see...

Mine notification area is showing "Restart your phone to restore bla bla" Of course I did it many times both watch and phone, and did multiple uninstall and restoring watch to factory settings... It's always coming back...

So, I guess it's time for your move Fitbit...

[RobertoME]

Hi @Homegirl welcome aboard to the Fitbit Community and thank you for sharing your solution against this issue.

@djurkash thank you for sharing additional details on what you have tried so far and the error shows up again. How it goes so far? Is still persisting? I have been unable to replicate this message ion my own, in case the issue persist would you mind to share a screenshot to have a closer look? For more details please refer to this post to upload picture in our Community. Also let me know what mobile device you are using along with the Android OS version.

See you later!

[Bamox]

Or for us to move on. Are they trying to tell us to go away?

[Bamox]

We keep chasing our tails and Fit bit moderators somebody somehow will figure it out and the problem will disappear. In plain English, they are kicking the can down the street. More diappointrd about the attitude than the failing technology.

[mrforsythexeter]

People please remember Fitbit want their business to succeed. I belive this issue is with the phones that we have chosen to buy and not with fitbit.

If you chose your phone and its not supported, its on you, not fitbit.

If your phone manufacture is doing something to stop the service from running, its on them and you as you chose the phone.

If this feature cannot be turned off without root, then its on your phone manufacture.

If you have an 'App' installed to manage / save your battery, then its on you.

Fitbit doesn't have root access to your phone, and they shouldn't. They can only test on so many device's and even then they only have control or access to so much of the phone.

Simple put, there is most likley nothing they can do as its out of their control.

For everyone with a supported phone / device, keep bugging fitbit, for everyone else go and shout at your manufacture for restricting your device and moving too far away from standard android.

[stefanopoulos]

I think that this is not going anywhere.

I have a state of the art phone from huawei the p10 which costs around 500£
and I have to buy a cheep one arround 50 £ used which is supported to make
it work with your device.

Really!!!!

Thank a lot once again from your effort to sort this out.

[mrforsythexeter]

The p10 is know to have aggressive battery management which is killing the service in the background.

I am communicating with Huawei about it. I would recommend you do to. Show them you are angry because you have spent your hard earned money on their hardware and software which is not working for you.

For too long now manufactures are pushing things out into the market without the correct QC. Fitbit is not at fault here, so use your energy in the correct direction.

[djurkash]

Cmon, you're defending them as of you're employee or some evangelist of Fitbit... List is BS, and we all know that... If you'd take all the device from it, you'd cut buyers base to a third, or fourth of all mobile users... Newest models not supported, Vanilla Android not supported... No way...

[YY2]

We are seeing the message in fitbit app which means fitbit is foregrpund. So why ask Huawei? If fitbit couldn't make notification work foreground, it is entirely on fitbit

[mrforsythexeter]

I don't work for fitbit, but I do want all of you to use your energy to fix the problem.

I am a software developer, so I understand what they are up against (on many platforms). Fitbit can show the messages as they know the service (background application) has stopped working. What they can't do, is launch the service again as the phone's software (which they cannot change) is preventing it.

If they did have a way to launch the service again, then the phones background service which is meant to save your battery, would close it time and time again. This would legitimately drain your battery even faster.

So, I beg of you, instead of attacking me, or fitbit, place your frustrations in the right place. So that we can actually get this issue resolved.

[GlenWatkins]

For the record, this happens to me as well but only since the last update (4/2/18). No problems prior to that.

[PaulHaines]

Let me confirm some facts:

* A total uninstall, unpairing, re-install of 2.69 will get notifications running, but only for a day or so.  After that point the "Notification Service Not Running....restart your phone" message re-appears.  See screen shot attached

* A restart of the phone does NOT fix the problem.   I and many other owners have confirmed this.

* Some people have suggested it is related to the phone's battery optimization disabling processes.  I have made sure all Fitbit services and android services are NOT battery optimised.  So that has not fixed it either. 

* I fully understand you saying the phones models may not be on the compatible list.  Reality check here folks - if you limited your sales to those phones, Fitbit would go out of business.  Also - this is the 4th brand of smart watch I have owned.  Fitbit is the only one where notifications fail.  With the same phone as I am using here.