Watch 4 dies and reboots while doing hike and listening to music

[catnap]

Today while hiking and listening to music, music app stopped playing, watch became unresponsive and eventually rebooted. Of course I lost the rest of the hike. It started a new hike.  Then it happened again when back at my car. Was not playing music - screen went black and I held down both buttons to reboot.

The music app is the play music app in the app selection and the music is my own which I transferred from my Note 8. No streaming involved.

This had happened before on another hike. Screen went black, eventually rebooted.

The battery was not low - it was at 40%

[tunit]

Myn too

[Tiadinky]

Has this been since the update as mine is only keeping a charge for about 10hrs since the uodate

[catnap]

This had nothing to do with battery life. The battery was fine at 40%. The problem occurred on a hike before the update and on a hike after the update. I've had no problems with battery life since the update.

[catnap]

So I get an email from Samsung community asking if my reply to  Tiadinky's reply (whose reply did not even address my post) to my original post is an acceptable solution.  No it's not a solution.

Why do I even bother?

[NovinoDragon]

Started happening to me as well since last week, however the last update was done over a month ago. I did start using the Spotify app about two weeks ago but not sure if the problem arose from that.

[catnap]

Since this happened I sent my watch to Samsung for repair for various other issues. They could not repair it, they would not return it to me, they would not send me a replacement watch (said they had none in stock).  Eventually after weeks of hassle they did return my money.  I ended up buying a new watch from Amazon.  I will never buy anything from Samsung again.

I have not tried hiking and music on the new watch yet.

[NovinoDragon]

Thank you for the update. I reset my watch and now the problem went away. Fortunately a reset does not remove esim info(took backup before reset) so I just had to copy the tracks again to the watch (which is very slow and another problem with this hardware). And now I haven't seen the issue for a good 24 hours, will report back here if I see it again.