How do I disable the unsafe volume warning?

After a long search for rescue from the automatic hearing protection (in a wrong way that drives people like me and you nuts), I finally found Hearing Saver app, which you can set a certain volume level for your media and another one for your ringtone either when you plug or unplug headphones. This would override the manufacture's annoying hearing protection which lower the volume down automatically, even though the warning message still shows. This was actually answered by dannyd86 (thank you for the post) but he didn't give the name of the app but instead gave a link so those who haven't registered for this forum would not be able to see it. I hope this would help you.

You are a hero. I have been pulling my hair trying to fix this problem. THANK YOU!
 
There is a reason why they did it though. As an industrial mechanic I deal with injury causing noise levels all the time. When you talk to somebody who does the hearing testing, they see kids in elementary school with damaged hearing more and more every year. Its from headphones. One rule of thumb they say is if you can hear the music in somebody elses earphones they are damaging their hearing.

Or how it is a federal law that driver's must to wear a seatbelt?

Since when did people lose their right to hurt themselves if the so choose?
 
The correct answer seems to be if you use a headset with the "correct" impedance, you will not get this warning.
It's not the "correct" impedance. I have Beyerdynamics DT 770 Pro 250 OHm and Nexus7, so even though I don't like to listen too loud, Nanny Android 4.2 + knows better what's good for me and I have to struggle with this warning quite often which ruins my user experience. Everything was fine up to 4.1.2, before they decided to introduce this feature. I hate to be treated like an id.ot, but it could be worse - they could use gyro to detect if I'm walking and turn the music off completely as it could be dangerous to walk on a street with headphones on. Thanks google!
 
Not everyone is using headphones. Some of us are in our cars, driving, with our phones plugged into the stereo. Which means we want to control the volume from the stereo but have the phone all the way up. Requiring those of us who utilize this method to remove our eyes from the road in order to touch the screen so we may proceed with or audio pleasures.

Not everyone is like you, nore do they fit into your perception or presumption of what you think we are or should be doing, so leave us to our own devices and stop trying to control the situation with what you think we should or should not be aloud to do. If someone is stupid enough to continue past your warning once while wearing headphones and damages there hearing, then they deserve it.
But at least give us the OPTION to disable it.
 
Since when did people lose their right to hurt themselves if the so choose?

Example. Kid uses headphones at extreme volume damaging hearing. Parents get lawyer and sue for the company not taking steps to prevent this.

Posted using Nexus 4 via Android Central App
 
First of all, control your kids. Second, give an option to never warn me again.
this becomes a hazard when trying to turn your phones volume up after plugging it into the cars stereo, and you have to look at the screen to disable it. That sounds like a bigger lawsuit to me.
 
It is here in the good Ole USA too....Sorry but I don't know how to stop it either . It started after Kit Kat FORCED update and then the SNEAKDATE that same night.
 
Just go into settings then into choose volume for music, etc. Move the volume back one notch from full volume. The warning will not appear anymore when you plug in an earphone or mini speaker. Your podcast will be reset back to pause though and you will have to press play again.
 
My phone has just updated to 4.4.3 and I am STILL getting the "raise volume above recommended level" popup. Now Google might think they are trying to look after our safety but I must point out that when plugging into the car stereo this popup could in fact be dangerous. If I plug in the stereo, start the music app and drive away, then can't figure out what's wrong with the volume, the distraction of this could cause an accident. Come on Google, do you really think I'm going to sue you because I chose to turn up the volume? Honestly I would be more likely to sue you because you messed with my volume control while I'm driving and caused an accident.
 
the only thing you can do, is ti get cyanogen mod for your nexus. it has the feature "turn volume warning off". if you don't want this, you can't do nithing for this. this feature is active just for europeans and Australians. There's no such feature in America.

Sent from my Nexus 4
 
Only Europe and Australia? Not US? Is this turning into spite for the "Right to be forgotten" ruling? No, seriously, I'd like to hear from Google WHY they are making things difficult for us. Especially when it's perfectly OK in the highly litigious US.
 
Is there something wrong with me and my Nexus 5. Just because I don't want to use a mod? Am I the only one in the whole world getting bugged by this issue?
 
I can tell you this is not limited to the Nexus, *and* happens in the USA. On the Nobis NB7022 you get the very same warning message, and there is no option to disable it. This is especially irritating as the audio in this tablet sucks as it is; it has one tiny (or tinny, either one fits) "speaker", pretty much inaudible with any other noises in the room. The fact that you have to get Nanny-droid's permission to make the thing listenable with headphones just reminds me how much we need to FORK android ("r-daneel", anyone?).
 
OK, This issue was posted in 2012, and STILL Google IGNORES their users! And for me this is not because of an old OS or proprietary phone software because this is a Nexus 5! And as for "safety" - it is still confusing when I plug it in the car and expect it to work, whether it is the car stereo source or some problem with the stereo or the fact that Android has locked my volume down again - the safety issue for me is will this cause an accident!? I'm surprised Google isn't facing any lawsuits for something along these lines. I find the prospect of a driverless car produced by this company extremely disturbing. And I find this annoying piece of unusabilty increasingly frustrating and infuriating. Shame on you Google-Android.
 
I do understand where you are coming from, dv8, it annoys me too, but I think that this "feature" of Android is simply off el Goog's radar. It's implemented; and that's that. The developers won't give it another thought.

I don't want to root my phone and use a mod either, for the same reason I don't want to fiddle around extracting more potential out of the engine in my car. I can get a lot more kilowatts quite cheaply but there are ramifications to doing that.

To continue the car analogy, I equate this to seatbelt warning beepers in cars. In Oz the law says we've had to wear seatbelts since the early 1970s. For me it's habit -- I've reversed the car out of the garage into the driveway to wash it and have put the seatbelt on! Duuuhhh... And yet there is an audible seatbelt warning and visual flasher in every car. My point is that some vehicles implement these devices really well: in a Mercedes it doesn't start howling at you until you reach about 5 km/h. In a Mazda it starts immediately you fire up the engine but stops as soon as you fasten the seatbelt. But in a Commodore, even if you buckle the belt immediately after engine start, it will keep on sounding for the programmed time (which seems like 5 minutes but is probably about 10 or 15 seconds); infuriating.

Have you tried Jake Basile's Hearing Saver App? https://forums.androidcentral.com/e...akebasile.android.hearingsaver&token=7_EQG-Pb It hasn't been updated since January 2013 so goodness knows if it will work on Kit Kat but it's a freebie so probably worth a try as a workaround.

And, even though it's nearly 12 months old, I'm still laughing at the comment above "Since when did people lose their right to hurt themselves if the so choose?" Looks like the poster joined AC to leave us with that little pearl. :)
 
Update: So I did try Hearing Saver https://forums.androidcentral.com/e...akebasile.android.hearingsaver&token=9AnQwJRv . Pretty good little app actually, 26 kilobytes and no permissions and it does what it says. Would that they were all like that!

Proviso: It requires you to reset the volume as per el Goog doctrine after a reboot. I only turn my phone off once every couple of weeks on average so I can live with that.

This is on a Nexus 5 with Kit Kat 4.4.4r2 (r2 is for Australia, New Zealand, and India only, I gather it's for certain carriers in those countries e.g. Telstra). So why am I posting in the Nexus 4 forum? Meh, it was my favourite thread on the topic.
 
I am not certain I understand the question.

In my initial round of tests, I plugged in the ear buds, started up an audio source (like PowerAmp), then used the side buttons to run through the full range of volume from low to high without receiving the warning message.

Once you pointed out that there was an additional volume control in Settings, I went there and found that the bar for "Music, video, games & other media" was set at only around 60%. So, I raised it to 100% and then repeated the previous tests. Still no warning message.

Lol why are u even repkying to this thread u are making people think things don't work. But really you are trying to fix a problem u don't even have. Ur name makes total sense.
 
Lol why are u even repkying to this thread u are making people think things don't work. But really you are trying to fix a problem u don't even have. Ur name makes total sense.

Oh brother...

N4Newbie is because at the time I joined AndroidCentral I was new to the Nexus 4.

I am a certified IT professional with 30 plus years experience, currently employed as IT Manager at a large manufacturing facility, and have written code in so many languages I have lost track. I had numerous published apps for PalmOS (that dates me, I know) and have also written apps for both Android OS and Apple iOS. Like it or not, I have a pretty good idea of what I am talking about and rarely contribute to a thread unless I feel I actually have something to contribute.

And, what exactly have you contributed to this thread?
 
You can eliminate this whole problem with an Xposed module. You can eliminate A LOT of problems with the Xposed Framework. Check this link:

lifehacker.com/disable-androids-high-volume-warning-with-an-xposed-t-1565793577 (sorry, haven't posted 10 posts)

You have to install and activate the framework, first, then there are a whole load of scripts/modules that will fix just most imaginable Android annoyances. The link takes you specifically to the volume fix.