“Notification Service Not Running”: Fixing the Fitbit Android App Bug

The alert reading “Notification service not running. A phone restart is required to re-enable notifications on your tracker” is a common and frustrating Android error for Fitbit users. While restarting your phone may temporarily resolve the problem, the error message often returns within a few hours or days. This occurs because aggressive Android battery-management services kill the Fitbit app’s background notification listener to save power, breaking the system bridge that routes calls, texts, and app alerts to your tracker.

Quick Answer

Go to Settings > Apps > Special App Access > Device & app notifications, toggle the Fitbit service OFF and back ON. Next, navigate to your phone’s App Info > Fitbit > Battery, set usage to Unrestricted, and lock the Fitbit app in your Recent Apps overview to keep Android from killing the background listener.


Device & Signal Snapshot

  • Platform: Fitbit Android Application connecting to all Fitbit devices (Charge, Sense, Versa, Inspire, Luxe)
  • Host OS: Android 12 through Android 16+ (especially common on Samsung One UI, Xiaomi HyperOS, and Google Pixel devices)
  • Primary Symptom: Notification shade displays “Notification service not running” banner; incoming messages and calls no longer vibrate on the tracker
  • Data Risk: Low (step, sleep, and heart-rate tracking continue normally; only incoming phone alerts are affected)

What Is Actually Happening?

To mirror incoming calls, text messages, and app notifications to your Fitbit, the Fitbit app relies on an Android system API called the NotificationListenerService:

The Android Notification Bridge:
[Incoming Phone App Alert] ──> [Android System Notification Center]
                                              │
                                   (System Listener Active)
                                              │
                                              ▼
[Fitbit Tracker] <──(BLE Packet)── [Fitbit Notification Service]
                                              │
                                   *Aggressive Battery Saver*
                                              ▼
                                 [Process Killed / Suspended]
                                              │
                                 "Notification Service Not Running"

This service operates as a continuous background listener. When your phone receives a notification, Android sends the event to the Fitbit service, which translates the text into a compact Bluetooth Low Energy packet and pushes it to your wrist.

The failure loop occurs because modern Android operating systems use aggressive memory and power-saving algorithms. When your phone screen turns off or your device runs low on available RAM:

  1. The Android OS flags the Fitbit background process as an idle consumer.
  2. The operating system kills the background process or revokes its active socket.
  3. The Fitbit app loses its hook into the Android notification center.
  4. When the Fitbit app attempts to verify its background status, it discovers the listener has been terminated, prompting the “phone restart required” error banner.

Because restarting your phone simply launches the service anew without fixing the underlying permission policy, the operating system inevitably terminates the service again later.


Step-by-Step Diagnostic & Resolution Protocol

Permanent Fix Hierarchy:
[Cycle System Access] ──> [Set Battery: Unrestricted] ──> [Disable OS Sleep Rules] ──> [Lock in App Tray]

Step 1: Cycle the Android Notification Access Permission

You do not need to reboot your phone to clear the error. You can restart the listener directly by cycling its system access toggle.

  1. Open your phone’s system Settings.
  2. Navigate to Apps > Special app access (on some phones, this is under Settings > Security & Privacy > Special Access).
  3. Select Device & app notifications (or Notification Access).
  4. Locate Fitbit in the list. You will likely see it marked as “Allowed.”
  5. Tap Fitbit, toggle the permission switch OFF, and tap Turn Off to confirm.
  6. Wait 5 seconds, then toggle the switch back ON.
  7. Tap Allow when the system warns you about access to personal alerts. The error banner in your notification shade should disappear immediately.

Step 2: Grant Unrestricted Battery Usage

By default, Android sets newly installed apps to “Optimized” battery use, giving the operating system permission to kill the app whenever background resources are needed.

  1. Go to Settings > Apps > See all apps > Fitbit.
  2. Tap Battery (or App battery usage).
  3. Change the setting from Optimized to Unrestricted.
  4. Confirm that the toggle for Pause app activity if unused is turned OFF.

Step 3: Prevent Background Bluetooth Drops

Android may disconnect the watch’s wireless communication channel when the screen stays off for an extended period. To stabilize this link, review the diagnostic steps in Why Your Smartwatch Disconnects When Your Phone Screen Turns Off.

Step 4: Device-Specific Background Whitelisting

Manufacturers often layer proprietary battery managers on top of standard Android. Apply these specific adjustments for your device:

  • Samsung (One UI): Go to Settings > Battery > Background usage limits. Ensure Fitbit is not listed under Sleeping apps or Deep sleeping apps. Tap Never sleeping apps, tap the + icon, and add Fitbit.
  • Google Pixel: Go to Settings > Battery > Adaptive Preferences. If alerts continue dropping overnight, turn Adaptive Battery off temporarily to test if it is terminating the listener.
  • Xiaomi / HyperOS / MIUI: Go to Settings > Apps > Manage apps > Fitbit. Enable Autostart, and change the Battery Saver setting to No restrictions.

Step 5: Lock the Fitbit App in Your Recent Apps Screen

To keep Android’s low-memory killer from closing the app when you run demanding tasks (like gaming or navigation):

  1. Open the Fitbit app.
  2. Open your Android Recent Apps / App Switcher screen (swipe up from the bottom of the display and hold).
  3. Locate the Fitbit app card.
  4. Tap and hold the Fitbit app icon at the top of the preview card, or tap the three dots.
  5. Select Lock (or the padlock icon). A small lock badge will appear on the card, preventing the app from being cleared when you use the “Clear All” button.

Step 6: Re-Enable App Notifications Inside the Fitbit App

Once Android’s system permissions are updated, confirm the in-app notification toggles are active:

  1. Open the Fitbit app and tap the Devices icon in the upper-left corner.
  2. Select your tracker model, then scroll down and tap Notifications.
  3. If prompted with a permissions dialog, tap OK and approve any requests.
  4. Tap App Notifications and ensure the specific messaging apps you want alerts from (WhatsApp, Messages, Gmail, etc.) are checked.

The Bottom Line

The “Notification service not running” error is caused by Android’s battery optimizer terminating the background listener, not a bug on your watch. Toggle Fitbit’s permission in “Device & app notifications,” switch the app’s battery profile to “Unrestricted,” and add it to your phone’s “Never Sleeping Apps” list to resolve the issue permanently.