Samsung apps running in the background

[JRStewart]

Galaxy Wearable Music, SOS, etc randomly run in the background on Galaxy Watch 4 even when I don't use the apps. I stop them from running in the background and lo and behold, they show up just minutes later running in the background again. This was never an issue before this one UI 5/Wear OS4 update. Samsung please, please fix this ASAP. 

[David-NYC]

After a couple weeks of running fine on a different watch face, the dreaded Galaxy Wear Music app started launching itself again.  This time I went with adb and developer mode and disabled the package samsung.android.wear.musictransfer   There are instructions over on XDA developers forum on how to remove/disable packages for those who are very technically inclined.  I'm putting the Stretch Time face back on, and will report back if it resolves the battery drain issue.

[David-NYC]

After a few days, here's what I've noticed 1) disabling samsung.android.wear.musictransfer solved the Wear Music app from running in the background. I've had no negative impact on other apps by doing so 2) Stretched Time face seems to be a battery drainer on its own 3) switched to the premium analog face and my battery life is as good, if not better, than before the WearOS/OneUI update.

[Ltd2sport]

I'm having the same problem wearable music, health platform keeps showing up. I also am not using the music app. Help!

[Ellin]

It still continues and doesn't matter what watch face I'm using

[JRStewart]

When I close this app from running in the background on my watch 4 it always mysteriously shows back up again not long after. Why? Started happening after the Wear OS 4 update. Thanks. 

[Members_akYL3BR]

I have the same issue on the Galaxy watch 6. I do not play music on s23 phone or watch but wearable music starts on its own and is a huge battery drain. Samsung customer service was off no help either.

[JRStewart]

Yeah it's pathetic. I just check my recent apps periodically and if it's there I close it. I think that's all we can do until the geniusus in South Korea figure out how to fix this bug