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.
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.