The same thing happens with brightness too. Turn it up full, suddenly, down to 3/4's again until you acknowledge yes, you really do actually want to turn your brightness up full.
The first time it happened I was outside in the sun and couldn't actually see my screen to figure out why it dimmed again, i kept trying to brighten it and it kept dimming, I finally noticed the popup on the bottom in the brief second of lightness I had after the 4th or 5th try.
I really hate the way devices try to control you rather than allowing you to control them.
On my old rooted android phone from years ago, I had alsamixer installed and could turn the volume up however I pleased, even above the artificial software limits present in all android versions.
I miss those days.
The volume warning is required by EU regulations, so it's hard to blame the OS maker for that. I do, however blame Google for increasingly trying to discourage rooting and providing facilities to app makers to prevent their apps from running on rooted devices.
They could, however have implemented the volume warning in a manner easier to defeat.
I don't understand why the concept of 'rooting'(as it applies to android) exists. I purchased my phone, with money, why in the actual fuck are there hundreds-thousands of folders and files my pocket computer will not let me touch?
I'm really tired of the 'safety before freedom' mentality that seems to exist these days. Humanity's managed to exist this long without being nanny'd and the people trying to do the nannying are also human.
I think the motivation for things like Safetynet is that general-purpose computers aren't good for business. If the user has full control, they might block ads, pirate content, or use content they legitimately paid for in a way a service provider wants to charge extra for.
But the regulations most certainly do not require the warning to pop up when the volume is still to quiet to hear that guy in the video talking, which is the actual complaint. If the warning actually appeared the moment when the volume is about to get really loud, it would be cool.
The underlying problem is, of course, that the volume control only slightly correlates with the actual volume that comes from the headphones.
Which makes concrete regulations about volume levels nonsensical however well-intentioned.
However in Windows this is broken for Bluetooth headsets and it's been a known bug since forever. Last time I checked they didn't fix it and it doesn't seem to be a priority.
It was quite annoying to randomly get your volume cut in half because iOS decided that you'd had enough. Luckily these days you can reclassify Bluetooth devices, so I made this speaker to be recognised as a speaker, which stops it.
In principle, if my headphone volume was actually loud enough to damage my hearing, I'd like to be told about it, but a given reality is the volume setting doesn't produce the same loudness with different headphones, which usually results in an inconvenience when my headphones aren't actually very loud.