If your smartwatch suddenly stops showing texts, calls, or app alerts, the cause is almost always one of a few things: a dropped Bluetooth connection, a companion-app permission that got switched off, or a Do Not Disturb / focus setting that’s silencing everything. The good news is that notifications are handled by software, so nearly every case is fixable in a few minutes without a factory reset. Work through the steps below in order, from the most common fixes to the rare ones.
- Notifications travel from your phone to your watch over Bluetooth, so a stable connection is step one
- Do Not Disturb, Focus, and Sleep modes silence alerts on the phone or watch even when everything is "connected"
- Battery-saver and background-data restrictions on the phone quietly block the companion app from pushing alerts
How smartwatch notifications actually work
Your watch does not receive texts or app alerts on its own (unless it has its own LTE plan and the app supports it). In almost all cases your phone receives the notification, then relays it to the watch over Bluetooth through the companion app — Apple Watch app, Samsung Wearable, Garmin Connect, Fitbit, and so on. If any link in that chain breaks, alerts stop. Knowing the chain tells you exactly where to look.
Step-by-step fixes
1. Confirm the watch and phone are connected
Open your companion app and look for a “Connected” status near the top. If it says “Disconnected” or “Searching,” no notifications can get through. Make sure Bluetooth is on, the phone is within about 30 feet, and airplane mode is off on both devices. If the connection keeps dropping, that’s a separate problem worth solving first — our guide to fixing Bluetooth connection issues walks through it in detail.
2. Turn off Do Not Disturb, Focus, and Sleep modes
This is the single most common cause of “silent” watches. Check for a moon or crescent icon on the watch face — that means Do Not Disturb is active. Also check:
- Do Not Disturb on both the watch and the phone (each has its own toggle).
- Focus modes (iPhone) or Modes/Bedtime (Android) that can auto-enable on a schedule and mute alerts.
- Sleep mode or a scheduled bedtime routine that dims the screen and holds notifications until morning.
- Theater or Cinema mode on Apple Watch, which silences and dims the display.
3. Re-check app notification permissions
Alerts only mirror to the watch if the app is allowed to notify on the phone first. Open your phone’s Settings → Notifications and confirm the specific app (Messages, WhatsApp, Gmail, etc.) has notifications turned on. Then open the companion app and find its notification list — most let you toggle each app individually for the watch. A single app that was accidentally switched off is a frequent culprit.
On many Android watches, apps installed after pairing are muted by default until you enable them in the wearable app.
4. Disable battery-saver and background restrictions
Aggressive power saving can stop the companion app from running in the background, which quietly kills notification relay:
- On Android, set the companion app (Galaxy Wearable, Garmin Connect, Fitbit) to Unrestricted battery usage and allow background activity.
- On both platforms, disable low-power/battery-saver mode temporarily to test — it can throttle Bluetooth and background data.
If you rely on battery-saver to get through the day, our battery-life tips cover ways to save power without sacrificing alerts, and our battery-life comparison shows which models last longest on a charge.
5. Confirm the phone isn’t unlocked or in active use
By default, many watches only send a notification when the phone is locked or asleep, on the assumption that you’ll see it on the phone otherwise. If you get alerts only when your phone is away, this is expected behavior — look for a “notify when phone is unlocked/in use” setting to change it.
6. Restart, then re-pair as a last resort
If everything looks correct but alerts still don’t arrive, restart both the watch and the phone — this clears the temporary Bluetooth glitches that cause most stubborn cases. If that fails, remove the watch from the companion app and pair it again. Re-pairing rebuilds the notification bridge from scratch and resolves the majority of remaining problems. For Apple Watch owners, our first-time setup guide covers pairing cleanly.
Model-specific quirks to check
| Platform | Common notification setting to check | Where to find it |
|---|---|---|
| Apple Watch | “Mirror my iPhone” vs. custom per-app rules | Watch app → Notifications |
| Samsung Galaxy Watch | Apps enabled for alerts; “show on watch” toggle | Galaxy Wearable → Notifications |
| Garmin | Bluetooth alerts and “Smart Notifications” on | Garmin Connect → Device → Smart Notifications |
| Fitbit / Pixel Watch | App notifications toggled per app | Companion app → Notifications |
Frequently asked questions
Why is my smartwatch not receiving notifications even though it’s connected?
A “connected” status only confirms the Bluetooth link. If alerts still don’t arrive, the cause is usually an active Do Not Disturb/Focus mode, a disabled app permission in the companion app, or a battery-saver setting blocking the app in the background. Work through steps 2 through 4 above.
Do I need a data plan for my watch to get notifications?
No. Standard notifications relay from your phone over Bluetooth, so no cellular plan is needed. An LTE plan only matters if you want the watch to work away from your phone. See our guide on LTE vs. Wi-Fi watches for the difference.
Why do I only get notifications when my phone is locked?
That’s a default setting on many watches, designed to avoid duplicate alerts. Look in your companion app’s notification settings for an option to send alerts even when the phone is unlocked or in use.
Could water damage stop notifications?
Rarely, but a soaked speaker or haptic motor can make you miss the buzz even if the alert arrived. If you swim with your watch, confirm it’s rated for it — our overview of water-resistance ratings explains what each rating covers.