Why does my smartwatch keep disconnecting or missing notifications?
The watch is rarely the problem. Nearly every dropout and missing alert comes from a setting on the phone — battery optimisation, a focus mode, notification permissions, or a Bluetooth radio with too much to do.
- Difficulty
- beginner
- Time
- 20 min
- Read
- 7 min
Short answer
Check the phone before the watch. The companion app needs to be allowed to run in the background and be exempted from battery optimisation, which is the single commonest cause on Android. Notifications have to be enabled for the app you are missing alerts from, on the phone, before the watch can ever relay them. And a phone juggling headphones, a car, a speaker and a watch on one Bluetooth radio will drop the least important connection, which is usually the watch.
A watch that keeps losing its phone feels like a hardware fault and almost never is. The connection is a Bluetooth link maintained by a companion app on the phone, with a wifi fallback on some models, and everything that governs whether it stays up is a phone-side setting. Modern phones are also extremely aggressive about stopping background apps to save battery, and the companion app is exactly the kind of always-running app they target. The result is a watch that works perfectly for a fortnight, then starts missing messages after a system update quietly restored a battery setting — which is why the fix is a checklist rather than a repair.
Step by step
- Establish whether it is disconnecting or only missing notifications.They are different faults. A watch showing a disconnected symbol has lost the link. A watch that is connected but silent has the link and is not being given anything to show. Check the connection status on the watch face before troubleshooting, because it sends you down completely different paths.
- Exempt the companion app from battery optimisation.On Android this is the fix more often than everything else combined. Manufacturers apply their own background restrictions on top of the standard ones, and they are frequently more aggressive than the settings screen suggests. Find the watch's companion app in the battery settings and set it to unrestricted, then check any manufacturer-specific power management screen as well.
- Check notifications are enabled on the phone first.A watch relays what the phone receives. If an app's notifications are off, muted, or set to silent delivery on the phone, nothing reaches the watch no matter what the watch settings say. Go through the phone's per-app notification list for the apps you are missing.
- Look at focus modes and do not disturb on both devices.Both have their own version, and on Apple devices they synchronise, so a focus mode set on the phone silences the watch too. This is deliberate and it is the explanation for a watch that goes quiet at the same time every evening. The catalogue's guide on focus modes covers setting them up so the things you need still get through.
- Understand the deliberate suppression rule.Most pairings send an alert to only one device: while the watch is on your wrist and unlocked, the phone stays quiet, and when it is not, the phone alerts instead. So a watch that seems to be missing notifications may be working exactly as designed while the phone has them. Check whether the alert arrived anywhere before treating it as a fault.
- Reduce what the phone's Bluetooth radio is doing.One radio serving headphones, a car, a speaker, a keyboard and a watch will drop connections, and the watch is a low-priority one. Disconnect what you are not using, and remove old paired devices you no longer own from the phone's Bluetooth list — a long list of stale pairings genuinely causes trouble.
- Check permissions the companion app needs and is often not given.Location and nearby-devices permissions are required by most companion apps for Bluetooth scanning, and denying them produces intermittent connection failures rather than an obvious error. Go through the app's permission list and grant what it asks for, or accept that it will not stay connected.
- Update both, in the right order.Update the phone's companion app first, then the watch's own software through it. A mismatch after a phone system update is a common cause of a pairing that suddenly becomes unreliable, and the fix is usually an app update that has been waiting.
- Re-pair properly if nothing else works.Remove the watch from the phone's Bluetooth list and from the companion app, restart both devices, then pair again from scratch. Be aware of what a re-pair costs on your model — some watches reset entirely, losing settings and any data not already synced, so check whether it has synced recently first.
- Know what wifi and mobile connectivity change.Many watches fall back to wifi when the phone is out of Bluetooth range, and some have their own mobile connection. If yours does, saving your home and work wifi networks to the watch keeps notifications flowing when you leave the phone in another room, and it is worth setting up deliberately rather than discovering by accident.
Common mistakes
- Factory resetting the watch first — It is the most disruptive step and it is almost never the cause. The setting responsible is on the phone in the great majority of cases, and a reset loses watch-side settings and unsynced data.
- Assuming missing alerts mean a broken link — Most pairings deliberately send an alert to one device only. Check whether the phone got it before concluding anything is wrong.
- Leaving a dozen stale Bluetooth pairings on the phone — Old cars, sold headphones and previous watches all stay on the list and the radio keeps looking for them. Removing them measurably improves reliability.
- Denying the companion app location permission on principle — It is used for Bluetooth scanning rather than for tracking you, and denying it produces exactly the intermittent connection faults people then spend hours diagnosing. If you object, the honest choice is not to use the watch.
If it doesn't work
Disconnects several times a day and reconnects on its own
Cause: Background restrictions on the companion app — Fix: Set the app to unrestricted in battery settings and check the manufacturer's own power management screen separately. This is the answer most of the time on Android.
Connected but no notifications at all
Cause: Phone-side notification settings, or a focus mode — Fix: Check the phone's per-app notifications for the apps concerned, then check do not disturb on both devices. Nothing on the watch can override an alert the phone never generated.
Some apps come through, others never do
Cause: Per-app notification mirroring is off for those apps — Fix: The companion app has its own list of which apps mirror to the watch, separate from the phone's list. Both have to allow it.
Drops whenever headphones connect
Cause: Bluetooth contention — Fix: Expected on phones with a busy radio. Disconnect unused devices and prune the paired list. It is more noticeable on older phones.
Notifications arrive late in a batch
Cause: The phone suspended the companion app and released it later — Fix: The same battery optimisation fix applies. Batched delivery is the classic signature of a background app being frozen.
Stopped working after a phone update
Cause: The update reset battery or permission settings — Fix: Re-check background permission, notification access and nearby-device permission after any major phone update. Updates routinely restore defaults on exactly these settings.
Works at home, not at work
Cause: The watch is using a saved wifi network at home — Fix: Add the work network to the watch if it supports it, or accept that it will rely on Bluetooth range there.
Questions people ask
Does the watch need mobile data of its own?
Not for notifications, which come from the phone over Bluetooth or wifi. A watch with its own mobile connection is for using it without the phone nearby — running, swimming, leaving the house without it — and it costs an additional line on your mobile account.
Why do I get the notification on the watch and not the phone?
That is deliberate. Most pairings suppress the phone's alert while the watch is on your wrist, so you are not buzzed twice. It reverses when the watch is off.
Will an Android watch work with an iPhone, or the reverse?
Apple's watches work only with iPhones. Some Android watches work with an iPhone in a reduced form, with notifications but not the full feature set, and support has narrowed over time. Check the specific model against your phone before buying — this is the compatibility question that catches people out.
Does keeping Bluetooth on all day drain the phone?
Very little on a modern phone. Low-energy Bluetooth is designed for exactly this kind of persistent low-rate link, and the companion app's background activity costs more than the radio does.
Is it worth having a watch just for notifications?
For people who want to know what has arrived without picking up a phone, genuinely yes — it reduces how often the phone comes out. If the intention is to be interrupted less, a watch is the wrong tool and the catalogue's guides on reducing notifications are the right ones.