Clippy may be a joke, but my phone actually does this (and yours likely does too).
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.
The worst is newer versions of android. You turn it up full, suddenly it's down to 3/4's full again and you have to acknowledge you want to turn it up, then turn it up again. If the headphones unplug, you gotta turn it up again.
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.
The first couple documented solutions for the volume warning on my new rooted Android phone didn't appear to have any effect.
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.
As far as I know, the audio functionality gained by rooting is no longer possible in newer android versions.
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 can understand why root is not enabled by default. Anybody who had to fix Windows PCs owned by average consumers a decade or so ago probably does too. The situation on Nexus and Pixel devices was about right: it requires the use of the command line (or third-party software), but doesn't try to resist. At least, it didn't until the introduced Safetynet so that apps can resist running on rooted devices.
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.
> The volume warning is required by EU regulations
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.
I sometimes wonder how much of a computer setup is actually legal from a regulatory perspective?
I have tinnitus in one ear so I usually set the volume balance on a system to 40-60 to spare it.
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.
I have this cheap small Bluetooth speaker that's not very loud but it's fine enough to use in the bathroom when I'm showering and doing stuff. I just need to keep it at 100% to actually hear it properly. However, at some point Apple decided that this speaker was actually a pair of headphones and there's a "feature" in iOS that can't be disabled that automatically lowers your headphone volume from 100% to 50% if it thinks you've been listening to music too long for too loud. It doesn't actually know what volume the speaker is outputting and it will do it even if the Bluetooth speaker is in another room behind a closed door.
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.
I have a USB speaker that apparently does some sort of volume mapping on the mixer level. Unfortunately my OS does the same thing and they get multiplied together, so the effect is volume level 0-97: complete silence. Level 98: loud. Level 99: deafening.
My iPhone (SE 1st gen, so I still have a headphone jack...) is constantly nagging at me that my average headphone volume is too loud; the reality is that when I use the headphone output I'm nearly always in my car using its line input, which requires me to max out the volume on the phone to get reasonable volume out of the amp.
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.