How do I disable the unsafe volume warning?

[SebastianSt]

I wrote a Xposed mod to disable the safe media volume check, see [Xposed][MOD] Unsafe Volume - disable safe media volume popup/check - xda-developers . The Xposed framework can be installed on any rooted device and rom. Cheers

 

[MINISTRO]

Hey Seb... I am using a GS4 running 4.2.2 and Installed the Xposed framework. and the module ''unsafe volume xposed mod 1.0'' and it still does it. how come ?

 

[SamsungUser1234]

I have successfully removed this warning message completely from my android 4.2.1 stock TF300T ROM. I can remove it from anything. Just hit me up over on xda developers. Not sure if this is important over here. But just figured i would share.

It is important enough that you could post it here. I am unsure how to use this forum and contacting you is not very apparent.....
So maybe just post it here

 

[stArTHf773192]

WOW, i cannot believe just how this issue is being handled here. I believe Android is an Java-based open-source OS, so if anything happens, it only takes SOMEBODY to write up a code to fix it, especially when these Java related vulnerability is pervasive. I'm serious, out of millions of Android smartphone users, NOBODY has this issue? Ever? It doesn't matter where the phone is sold, (US, UK, Australia and what not) this kind of issue would be solved in a day or week in a PC arena. Unbelievable community support, let me just say that.

Back to the issue, in detail, it happens when you plug in "headset", "headphone", "earphone" or whatever you wanna call it to the phone. Very quietly, (or just silently), the OS sets or decrease the MEDIA volume to a "safe" level (around 9/15). And if you mess with it, such as opening Play Music app and cranking up the volume, the Sammy Nanny will nag you to turn it down EVERY TIME you get on her nerves. This includes repetitively going from 15/15 to 0/15 (full vol to silent), plugging in and out that headset, etc. And i don't give a damn about WHY they implemented this stupid feature, so don't ask me about that.

I can testify that i have US Galaxy S4 (SGH-M919), Android 4.2.2 (ROOTED) and it does display the parannoying message, but it does not force me to choose between OK or Cancel to keep increasing the volume.

Here's the SUGGESTED solution. I'm saying this because i couldn't find any source code to flash for you, which will directly remove or disable this kind of parannoying feature. Goto Play Store, and look for apps about "volume control", "volume equalizer", or "headset volume control". I personally recommend "Volume Control +" (yes, the plus sign is part of the name). You can play with it yourself or read more to get in details.

VC+ controls volumes for the phone: Ring, Notifi, Media, Voice Call, System. What's good about this app is that you can lock the volumes. What this means is, for example, you set the Ring vol to max, and after that, if you press volume keys, the volume will be set back to max. You can also set up a separate profile for headset/bluetooth connection.

So, to tackle the issue, you can lock the Media vol only, but this might give you profanity-rampage since you cannot "change" volume. (You have to pause the song or video to really silence it) In other method, you can set the headset/bluetooth profile, and the volume will be set to the profile's level every time you plug in the headset. This way, you can quiet it down for any reason, plug off the headset for any reason, and when you plug it back on, VOILA! the vol will be reset to the profile's level. The downside is that every time you plug-off the headset, Media volume will be restored to 9/15, regardless of whether you locked the Media vol prior to plug in the headset.

Again, this is not a perfect solution, but at least a functional way to tackle this parannoying nanny-y feature.

UPDATE: VC+ has gone dark for about 2 years now...:-\

UPDATE: "Volume Booster" by lovekara can fix the issue. If you plug in the headset, app will automatically change to headset profile.

 

[dv8info]

Just updated my N7 to 4.3 hoping that the developers have been listening to us, but the annoying nanny warning is still there. Why doesn't Google listen to us users?! Are they simply letting the NSA do the listening for them?

 

[Bryan Ramos]

I have xperia sp and i have this problem before,,i cannot scroll up to the max volume whenever my headphones were plugged in. but the thing is i don't get any ****ty message after rooting my phone,, so what i did was i installed root explorer (total commander) from play store,,search for SoundLevelAlert.apk path is: /system/app then re-install the file. long press then click properties, set it to rw-r-r then click apply,,reboot phone..after doing this, the ****ty pop-up message appeared but the good thing is i can now put the volume to max level..the annoying message still pops-up though whenever i open my music player..hope this helps...

 

[dannyd86]

problem solved https://forums.androidcentral.com/e...ile.android.hearingsaver&hl=en&token=hlT34Byu

 

[portscan]

Still get the warning after reboot.

 

[Cypher xD]

problem solved https://forums.androidcentral.com/e...ile.android.hearingsaver&hl=en&token=VMzTV2mx

Thank you so much dannyd86! It worked fine for me, just set the standard media volume with head jack plugged to max in the app -> BINGO!

It is really disgusting to slowly see every last bit of human indepenence / freedom of choice being taken from us....as an ex software tester it is especially intersting to see this being sold as "feature"...thumbs down!!!

Hope the future will not bring any further such "freakures", especially without standard options of disabling them.

Hardware / Software :
ASUS MemoPad 7 (ME173X) / Android Version 4.2.2 (Build:4.2.4.06716_20130918), Kernel Version 3.4.5

 

[dannyd86]

Thank you so much dannyd86! It worked fine for me, just set the standard media volume with head jack plugged to max in the app -> BINGO!

It is really disgusting to slowly see every last bit of human indepenence / freedom of choice being taken from us....as an ex software tester it is especially intersting to see this being sold as "feature"...thumbs down!!!

Hope the future will not bring any further such "freakures", especially without standard options of disabling them.

Hardware / Software :
ASUS MemoPad 7 (ME173X) / Android Version 4.2.2 (Build:4.2.4.06716_20130918), Kernel Version 3.4.5

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.

 

[Mark Seedy]

Thanks for the suggestion, but after restart plugging in the headphone jack tries to turn the volume up and triggers the nanny status, freezing the volume at half mast. Really annoying as I'm using a Bluetooth remote and I don't want to have to take the phone out of my pocket. So glad its just once a restart, but perhaps they could save my acknowledgement of loud noises potential to hurt me, on my g+ login?

 

[SeaniB]

I'm having the same notification on a Note 3

Sent from my Notes

 

[Rana89]

I may be too late to answer this and may be running generations behind when it comes to phones
I recently rooted my xperia Neo V and installed CM10.1 (JB 4.2.2). I have been getting this annoying warning message whenever I put headphone jack and increase the volume.
I resolved this issue by going to Settings->Sound->Uncheck "Safe headset volume".

I am not sure if the Stock JB 4.2.2 has the above option.

Thanks,
Rana.

 

[N4Newbie]

I may be too late to answer this and may be running generations behind when it comes to phones
I recently rooted my xperia Neo V and installed CM10.1 (JB 4.2.2). I have been getting this annoying warning message whenever I put headphone jack and increase the volume.
I resolved this issue by going to Settings->Sound->Uncheck "Safe headset volume".

I am not sure if the Stock JB 4.2.2 has the above option.

Thanks,
Rana.

It is not an option in stock Android OS. Not in 4.2.x, not in 4.3.x, nor in 4.4.x.

The correct answer seems to be if you use a headset with the "correct" impedance, you will not get this warning.

 

[AitchKay]

So how can this option be "added" somehow? Surely there must be a fix or a tweak?

 

[bfugett]

So how can this option be "added" somehow? Surely there must be a fix or a tweak?

Confirmed on my AT&T Note 3, I do not get the warning when ear buds are plugged in, but I do when I plug up to an audio device via 1/8" cable. No option in settings to disable that I can find. Annoying.

 

[Hoai Phuong Nguyen]

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.

 

[pre1561]

I'm in the U. S. and I get this pop up on my Note 3. I got it on my S3, my wife got on her S3 & now here S4. It's not just a European thing.

Sent from my SM-N900P using Tapatalk

 

[Kegman]

Note 3 with T-mobile usa, I have it. Dont look like you can turn it off but I found a way around it using an app I already had. The app is called Llama (similar to tasker which should work too). Make a setting to change volume to max (or desired volume above this safety limit) upon detecting headphone jack input. This worked, no more nag screen

 

[asuperpower]

I really wish there was a fix to this... I use relatively high impedance headphones on my Nexus 5, but every time I turn the volume up, this happens... oh well. :/