Device / OS
Laptop: Clevo laptop with an up-to-date Windows 10 Pro 1809
Phone: Samsung Galaxy S8 with Android 9
Receiver: Denon AVR-X3500H with latest Firmware (2600-9174-8102-0025)
Spotify version on Windows: 188.8.131.523.geb9254e9
Spotify version on Android: 184.108.40.2067
My Question or Issue
While writing this I'm still shaking. After opening Spotify on my Android device I selected a song I would like to hear like I normally do, and pressed play. The song started to play on my phone. I clicked the 'Connect to a device' button and selected the Denon receiver. After a short delay the song starts to play on Denon receiver on MAX volume. I've never set the volume of the receiver even near max in my entire live and I instantly knew why. Apparently max volume equals instant shock and permanent ear damage. In the moment I accidentally pressed the Samsung Bixby button which made the unbearable moment even longer. Once I could stop the music and set the volume to zero I was dazedly looking around while the smell of fried electronics from my B&W speakers filled the air.
One week earlier I had a similar incident from my laptop. I was working in the living room and I've been playing music from Spotify on my receiver for a while and on a random moment the volume switched to MAX. I didn't touch Spotify or my local system audio at that time because I worked in a remote desktop session. I don't know if this is related to the Spotify Android incident but they both happened within one week time span and never before. On the Windows system it looked like the Windows volume (which was on 100%) was synced with the Spotify volume, which synced this volume to the receiver. After setting my Windows volume around 20% I had twice the 'incident' that my spotify volume jumped to a lower volume. Which I had to set higher manually.
I have no clue why this happened. I do know I don't want this ever to happen again. Please look into this issue Spotify.
Thanks for your patience while we looked into this issue.
We’re happy to say that this should now be fixed for everyone!
If you’re still experiencing this issue, let us know and we’ll look into it.