First i talked about what is being discussed here. And yes, my smartphone is a Samsung (S23 Ultra), and no, it doesn’t happen with any other app. 
I stopped chiming in, but I keep secretly hoping this gets fixed in a future version Really love this app – just this one annoying bug.
Since this thread got brought back up - I guess my question for @Tolriq is: I know you say this isn’t a bug in Symfonium. Are you suggesting that every other app with media resuming has done some specific coding to support new Samsung devices?
Clearly there’s a fix for this since no other app has this issue and whether Symfonium or Samsung is to blame doesn’t really matter.
Are you open to the idea of maybe adding a few lines of code to better support Samsung phones? Samsung accounts for a large portion of the Android user base and any way you look at it, a cleaner bug-free experience makes the app better for everyone (even if it’s not your bug) 
Also, for what it’s worth – I am a developer and I sincerely appreciate all you’ve done. I know certain Android APIs can be a bit messy. You’re the person with the power here since none of us work for Samsung to fix any issues on their end.
1 Like
As I said I do not own a Samsung device and won’t purchase one for this considering that this is Android and I barely make money with the app.
And again this is not really a bug it’s the documented wanted behavior of apps supporting resuming to have the media session there for resuming and when the app is started with a queue. The solution is to unpin the media session but Samsung have removed that.
So what you consider a bug, is how Google wants things to happens for modern apps targeting the very last Android SDKs.
If you are able to tell me what Samsung breaks and how to workaround with proper details I can add it, but I won’t purchase every broken devices that exists to workaround all the OEM issues that exists.