When your Wear OS smartwatch displays a repeating “Bluetooth keeps stopping” or “Bluetooth Has Stopped” system pop-up, the core background Bluetooth service has crashed. Because the Android-based operating system relies on this service for everything from syncing notifications to managing sensors and offloading data, an active crash loop makes the watch practically unusable. It drains the battery rapidly and causes the display to freeze as the error dialog constantly re-appears.
Quick Answer
To stop the crash loop immediately, restart the watch into safe mode or quickly navigate to Settings > Apps & Notifications > App Info > Show System Apps > Bluetooth, tap Storage, and select Clear Data and Clear Cache. Then, restart the watch to rebuild the local connection database.
Device & Signal Snapshot
- Applicable Systems: Wear OS 4, Wear OS 5, Wear OS 6 (Galaxy Watch, Pixel Watch, TicWatch, Fossil)
- Affected Service:
com.android.bluetooth(Bluetooth System Daemon) - Severity Level: Critical (breaks phone sync, audio streaming, and Wi-Fi handoffs; rapidly drains the battery)
- Common Indicators: A modal error box appears every 2 to 5 seconds, watch vibrates constantly with crash reports, battery percentage drops quickly
What Is Actually Happening?
On Wear OS, the Bluetooth stack runs as a root system process named com.android.bluetooth. This process manages communication between the watch hardware, the kernel, and user-facing apps:
[Incoming Data / Corrupt GATT Packet] ──> Passes to com.android.bluetooth
│
▼
[Internal Database Check] ──> Encounters corrupted SQLite entry / bad bonding record
│
▼
[Unhandled System Exception] ──> Daemon terminates (Process Crash)
│
▼
[Android Init Daemon] ──> Detects crashed service, attempts instant restart
│
▼
[Crash Loop Established] ──> "Bluetooth keeps stopping" dialog appears repeatedly
The service crashes when it encounters data it cannot parse. This is typically caused by:
- A Corrupted Link Key: A paired phone sent an incomplete encryption key update, corrupting the watch’s internal SQLite database.
- A Malformed GATT Cache: A third-party fitness app, custom watch face, or sideloaded APK wrote invalid data directly to the Generic Attribute (GATT) storage buffer.
- Dirty OS Updates: A major Wear OS system update was applied over an existing configuration without rebuilding the device’s local Bluetooth services.
How to Tell Which Problem You Have
Before resetting your watch, look at how the crash behaves to pinpoint the trigger:
- Instant Loop (Unusable UI): The pop-up re-appears the exact millisecond you dismiss it. The Bluetooth service is crashing on initial boot, usually due to a corrupted core database file.
- Triggered Loop (Occurs When Connecting): The watch operates smoothly while away from your phone, but begins crashing the moment it comes into range and tries to establish a link. This points to a malformed pairing record on the phone.
- App-Specific Crash: The pop-up only appears when you open a fitness tracker, music app, or external sensor monitor. This means that specific app is overloading the Bluetooth buffer.
Step-by-Step Diagnostic Resolution
Work through these progressive steps to clear the error without resorting to a full factory reset if possible.
[Reboot into Safe Mode] ──> [Clear System Bluetooth Cache & Data] ──> [Restart Normal Mode]
│
▼
Fails? ──> [Wipe Cache Partition]
│
▼
Fails? ──> [Recovery Factory Reset]
1. Boot Into Safe Mode to Stop the Pop-Up Loop
If the error dialog re-appears too fast for you to tap through menus, safe mode disables all third-party services so you can navigate the settings:
- Press and hold the Power Button (or home key) until the power options menu appears.
- Tap and hold down the Power Off icon on the screen until the “Reboot to safe mode” prompt appears.
- Tap the checkmark to confirm. The watch will reboot with “Safe mode” displayed at the bottom of the screen.
- If your touch screen is frozen, check Pixel Watch 4 “Input Lag”: Fixing the 3-Second UI Freeze on Wake for button-only workarounds.
2. Clear the Bluetooth Service Data and Cache
With the watch stabilized in Safe Mode, you can safely wipe the corrupted service files:
- Swipe down and open Settings (the gear icon).
- Tap Apps & Notifications > App Info.
- Scroll to the very bottom and tap System Apps (or toggle on system processes).
- Locate and tap on Bluetooth (or
com.android.bluetooth). - Tap Storage & Cache.
- Tap Clear Cache, then tap Clear Storage (or Clear Data).
- Confirm the prompt. This resets your watch’s local wireless table without deleting your installed apps or health history.
- Restart the watch normally to exit Safe Mode.
3. Forget the Device on Your Phone
Because the watch just cleared its Bluetooth database, your phone’s pairing records are out of sync:
- Open your phone’s Settings > Bluetooth.
- Locate the name of your Wear OS watch.
- Tap the gear or info icon and select Unpair or Forget.
- Restart your phone.
- Open the Wear OS / Galaxy Wearable companion app on your phone and re-establish the connection.
If your phone’s Bluetooth system starts throwing matching errors, review Fixing the “Bluetooth Keeps Stopping” System Error on Wear OS for broader system-level troubleshooting.
4. Clear the System Cache Partition via Recovery Mode
If clearing the app storage does not fix the crash, corrupted temporary update files may be lingering in the hardware cache:
- Power the watch completely off.
- Hold the Power Button and Back Key simultaneously until the manufacturer logo appears, then release.
- Rapidly tap the power key to open the Fastboot / Recovery Menu.
- Use the physical buttons to highlight Recovery Mode, then press the power key to select it.
- When the Android robot appears with an open chest, hold the power button and swipe up on the screen to reveal the recovery options.
- Select Wipe Cache Partition and confirm.
- Once finished, select Reboot System Now.
For step-by-step navigation instructions on stock recovery screens, see Pixel Watch 4 “No Command” Screen: Accessing Recovery Mode.
What to Check If That Doesn’t Work
If the Bluetooth service continues to crash after clearing the cache:
- Audit Third-Party Watch Faces: Poorly coded watch faces frequently poll Bluetooth channels incorrectly. Switch back to a pre-installed default watch face.
- Corrupted Companion App Sync: If the issue started immediately after updating your phone’s software, see Samsung One UI 8 Watch: Fixing the “Wrist Detection” & PIN Entry Loop for permission conflicts that disrupt background syncs.
- System UI Failures: If other Android services begin throwing similar errors (such as “System UI Has Stopped”), the core firmware is unstable. Consult Wear OS 6: Fixing the “System UI Has Stopped” Persistent Error.
When It’s Actually a Hardware Problem
If the “Bluetooth keeps stopping” message appears on a clean factory installation without any restored apps or connected phones, the problem is hardware-based:
- The watch fails its initial setup wizard because Bluetooth will not stay active long enough to discover a phone.
- The MAC address for the Bluetooth adapter displays as “Unavailable” or
02:00:00:00:00:00under Settings > System > About > Connectivity. - The watch body gets hot directly beneath the motherboard processor within two minutes of booting.
These symptoms mean the integrated Wi-Fi/Bluetooth system-on-chip has suffered an internal voltage fault or physical trace failure. In this state, software fixes will not resolve the issue, and the watch requires a warranty repair or motherboard replacement.
Closing
The “Bluetooth keeps stopping” loop on Wear OS is caused by corrupted data packets trapped inside the system Bluetooth daemon; booting into Safe Mode and clearing the storage for com.android.bluetooth wipes out the bad data records and restores normal system operation.