After a clean reset, my Galaxy Watch 4 Classic worked perfectly — no rebooting when placed on the charger. But after Samsung Health and Samsung Pay updated, the reboot-on-charger issue came back. I’ve tested this multiple times and can reproduce it consistently.
I’ve tried:
Clean reset without restoring backup
Avoiding Samsung Health and Wallet
Testing with basic watch face and minimal apps
The issue only returns after those system apps update or reinitialize. It seems tied to background services or firmware bugs.
Additional symptom: Each time I place the watch on the charger, it disconnects from the phone. Sometimes it reconnects quickly, other times it struggles to reestablish the connection. This happens even when the watch shows “connected” before charging.
Watch model: Galaxy Watch 4 Classic Model Name: SM-R890
Software version: R890XXS1IYE9
Would appreciate confirmation if this is a known issue or if a fix is coming. Thanks.
Update: I just discovered another consistent behavior. If I manually power off the watch while wearing it, then remove it and place it on the charger, it automatically boots up — even though I turned it off. It flashes the Samsung logo multiple times before showing the Galaxy logo, then finishes booting in a disconnected and locked state.
Each time this happens, the watch disconnects from the phone. Sometimes it reconnects quickly, other times it struggles. This confirms the reboot is triggered even from a powered-off state, and it breaks Bluetooth continuity.
This seems tied to background services or firmware-level behavior, possibly linked to Samsung Health or Wallet updates.
I just did another clean reset to use the watch while waiting for advice. After setup completed, I adjusted the display brightness (it was extremely dim). I did not update any apps or restore anything. Then I placed the watch on the charger to get a full charge — and it rebooted again. This confirms the issue happens even before Samsung Health or Wallet are installed or updated. The reboot-on-charger behavior appears to be tied to the base firmware itself, not just app-level triggers. This makes it a deeper system-level bug.
When you next replicate the issue, send an error report to the programmers and include the logs (the watch logs are embedded in the phone logs), within an hour after the replication. https://us.community.samsung.com/t5/Tips-Tricks/How-to-Send-Feedback/ba-p/3001692 This is the only way it's going to get acknowledged or fixed.
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
I followed the instructions in the link you posted. I put the explanation, but it didn't ask for any logs to be attached. Is that automatically done by the app? Does it know where the locate the correct information?
The logs are collected automatically when you begin the feedback report. Unless you check the box not to, they ate uploaded automatically. You should have received a notification not to close the app until the upload is complete and then received a notification that your report has been sent. If the log is incomplete, the programmers will respond, asking you to resend it. A copy of the log is saved to your phone. It's in downloads/log
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
The same thing is happening to me, it is downloading very quickly and disconnecting continuously, I think I will wait to see what solution they give, probably with a system update.
You should put in your own error report. The more reports they get, the likelier a general patch will be issued.
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
