Develop Bugs

Make "Disable HW Overlays" permanent

Hi. Does anyone know how to make the "Disable HW Overlays" option found on some ROMs permanently checked / persistent after reboot? I'm using JellyTime R13 on my DHD. Thanks.

I don't think that there's an option to do that. But ticking the option every boot isn't all that hard.
Sent from my Desire HD using xda app-developers app

Agreed...but if there is a better way then I'd be very keen to learn of it.

tedrogers61 said:
Agreed...but if there is a better way then I'd be very keen to learn of it.
Click to expand...
Click to collapse
+1 same question on Jellytime R15 !

jean019 said:
+1 same question on Jellytime R15 !
Click to expand...
Click to collapse
On the JT R15 developer thread, someone has noted that it is a known issue.
I'm not sure whether they mean it is a known issue that the HW Overlay box is unchecked after reboot, or whether the graphical issues with checking Disable HW Overlays solves is an issue.
However, people are talking about it, and that pleases me.

tedrogers61 said:
Hi. Does anyone know how to make the "Disable HW Overlays" option found on some ROMs permanently checked / persistent after reboot? I'm using JellyTime R13 on my DHD. Thanks.
Click to expand...
Click to collapse
+1 :'(

Also looking for a permanent solution for my Inspire 4G, is frustrating to run the camera or play a video and have the phone restart cause I forgot to switch the setting last boot.

This will work!
http://forum.xda-developers.com/showthread.php?t=1904827

Sorry wrong place
sorry wrong place
please remove

Anyone try this ?

Permanent Disable Hw overlays Enjoy Script
Disable Hardware Overlays permanently Using This Script Put into init.d Folder or else use Script manager or something like that which will run this script on boot
Code:
#!/system/bin/sh
(while :
do
sf=$(service list | grep -c "SurfaceFlinger")
if [ $sf -eq 1 ]
then
service call SurfaceFlinger 1008 i32 1
break
else
sleep 2
fi
done
) &
:fingers-crossed: enjoy

sgatechwork said:
Disable Hardware Overlays permanently Using This Script Put into init.d Folder or else use Script manager or something like that which will run this script on boot
Code:
#!/system/bin/sh
(while :
do
sf=$(service list | grep -c "SurfaceFlinger")
if [ $sf -eq 1 ]
then
service call SurfaceFlinger 1008 i32 1
break
else
sleep 2
fi
done
) &
:fingers-crossed: enjoy
Click to expand...
Click to collapse
Always make sure you give credit to the original dev. I wrote this script

titanic_fanatic said:
Always make sure you give credit to the original dev. I wrote this script
Click to expand...
Click to collapse
:laugh: opps!! Credit Goes To @titanic_fanatic :silly:

script didn't work on my TX 4.3. please help

shaktishekhar said:
Disable Hardware Overlays permanently Using This Script Put into init.d Folder or else use Script manager or something like that which will run this script on boot
:fingers-crossed: enjoy
Click to expand...
Click to collapse
Thanks man! i was just looking for the shell cmd but this works ! *on android 7.1.2 initd. d needed to be emulated....i dont beleive its the default "load on boot" protocol any longer but emulation via kernel auditor seems to do the trick. Doesnt matter as long as i dont have to manually set check the option. Appreciate the work.

titanic_fanatic said:
Disable Hardware Overlays permanently Using This Script Put into init.d Folder or else use Script manager or something like that which will run this script on boot
Always make sure you give credit to the original dev. I wrote this script
Click to expand...
Click to collapse
Dear @titanic_fanatic, can I kindly ask you if you can adapt your script to make the Skia GPU renderer on Android Oreo applied on boot without it resetting every time? Thank you for the original idea anyway, it was brilliant, I use always your script

Why should I do that? Can you please explain it? ?

remained said:
Why should I do that? Can you please explain it? ?
Click to expand...
Click to collapse
Please how can I enable 4x MSAA using a shell script on android?

titanic_fanatic said:
Always make sure you give credit to the original dev. I wrote this script
Click to expand...
Click to collapse
Still works on Galaxy S5 Lineage OS 16 SmartPack kernel (oc to 2.6gHz btw) and manager. Thanks! Bookmarked this notably good post .. :good:

Works fine on a Poco M3 running A11. I've attached a basic Magisk module with titanic_fanatic's script, since that'd probably be easier to use for most people.

[HOW-TO] Enable MultiWindow on EMUI 4.1 / Android 6 (like EMUI 5)

Hello!
This morning i was just looking in build.prop when ive seen a line regarding multi-window.
On EMUI 5 / Android 7, we can enable MultiWindow by pressing for few seconds the multitasking/recents icon in the navigation bar.
This feature is available on EMUI 4.1 as well.
REQUIREMENTS:
- EMUI 4.1
- Unlocked bootloader
- Rooted phone
- a file manager with root support ( im using the good old version of ES File Explorer)
Click to expand...
Click to collapse
[HOW-TO] Huawei Nova:
1) Grant root access to the file manager.
2) Go to /system and open build.prop.
3) Search for ro.huawei.multiwindow and change it from false to true.
ro.huawei.multiwindow=false becomes ro.huawei.multiwindow=true.
4) Save and reboot. After reboot, you can use MultiWindow by pressing for few seconds the multitasking / recents icon from navigation bar.
Click to expand...
Click to collapse
[HOW-TO] Other Huawei phones:
If you have followed the instructions for Huawei Nova and it didnt work, then check if you have HwMwLauncher folder in /system/app or /system/priv-app.
If it is missing, then check this post. People reported that MultiWindow is working after they got HwMwLauncher.
CONFIRMED DEVICES:
- Huawei Honor 8
If your phone isnt on this list, then it doesnt mean that it doesnt work. Just try and report back. I think it should work on all Huawei phones which are running EMUI 4.1.
Click to expand...
Click to collapse
EDIT: I just seen that you can use MultiWindow by swiping up two fingers on navigation bar too.

When you are in Multiwindow with 2 apps open, press HOME button.
I have a big bug!
The Home is in half screen.
VNS-L21C432B170
Emui 4.1.2
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk

millo1978 said:
When you are in Multiwindow with 2 apps open, press HOME button.
I have a big bug!
The Home is in half screen.
VNS-L21C432B170
Emui 4.1.2
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk
Click to expand...
Click to collapse
I have no issues. When I press home button it just disable MultiWindow.
Nova CAN-L11 running EMUI 4.1 CANC432B100.

Maybe this is my firmware problem... I don't know.
But only with home button.
With back button all is ok.
Screenshot:
http://cloud.tapatalk.com/s/58ff90231cc85/Screenshot_2017-04-25-20-02-43.png?
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk

I enabled this on my mate 7 with emui 4 marshmallow quite a while ago. If I try to use it I just get a pop up message saying this application does not support dual windows. Haven't found a practical use for it yet.

RobboW said:
I enabled this on my mate 7 with emui 4 marshmallow quite a while ago. If I try to use it I just get a pop up message saying this application does not support dual windows. Haven't found a practical use for it yet.
Click to expand...
Click to collapse
It's same for me.
When you press the "+" on homescreen after you enable MultiWindow I think it shows only the apps which support it.
Personally, I'm not using MultiWindow. I just wanted to share the small trick I've found.

Strange - it doesn't seem to have any effect on my rooted Honor 8 (still on MM with EMUI 4.1).
I used BuildProp Editor to set ro.huawei.multiwindow=true and rebooted. Holding the "recents" button does nothing apart from a quick burst of haptic feedback after about half a second or so.
Any ideas?
Thanks.

stooby said:
Strange - it doesn't seem to have any effect on my rooted Honor 8 (still on MM with EMUI 4.1).
I used BuildProp Editor to set ro.huawei.multiwindow=true and rebooted. Holding the "recents" button does nothing apart from a quick burst of haptic feedback after about half a second or so.
Any ideas?
Thanks.
Click to expand...
Click to collapse
Exactly the same phone and software here but it shows the toasts messages and the MultiWindow interface but doesn't work. I think EMUI 4.1 is simply Nougat ready and that is the reason why it has the option to enable or disable MultiWindow but the system (MM) has not this function and that is why it doesn't work. So the result is only the GUI of MultiWindow being shown but is only EMUI trying to do something as layer that system in fact isn't capable.
I was wrong follow @#Henkate instructions here here

stooby said:
Strange - it doesn't seem to have any effect on my rooted Honor 8 (still on MM with EMUI 4.1).
I used BuildProp Editor to set ro.huawei.multiwindow=true and rebooted. Holding the "recents" button does nothing apart from a quick burst of haptic feedback after about half a second or so.
Any ideas?
Thanks.
Click to expand...
Click to collapse
carmeloamg said:
Exactly the same phone and software here but it shows the toasts messages and the MultiWindow interface but doesn't work.
Click to expand...
Click to collapse
1) Do you have HwMwLauncher.apk in /system/app/HwMwLauncher or /system/priv-app/HwMwLauncher ? I don't think it matter if it is in app or priv-app, but it must exist. I have it in /system/app.
2) After you enable MultiWindow, do you see the process named HwDualWindowLauncher at Settings > Developer Options > Running services (check also cached processes there)?
3) In build.prop I have the following line: ro.config.hw_multiscreen=true. I think it might be related to MultiWindow as well, but I'm not sure. I didn't try yet to set it to false and see what happens.
carmeloamg said:
I think EMUI 4.1 is simply Nougat ready and that is the reason why it has the option to enable or disable MultiWindow but the system (MM) has not this function and that is why it doesn't work. So the result is only the GUI of MultiWindow being shown but is only EMUI trying to do something as layer that system in fact isn't capable.
Click to expand...
Click to collapse
Well, it works for me on Nova CAN-L11 running EMUI 4.1
MultiWindow has been introduced in Android 6. Why Huawei hid this option in EMUI 4.1 (Android 6) and introduced it as a new feature in EMUI 5 (Android 7)? That's what I'm asking too.

#Henkate said:
1) Do you have HwMwLauncher.apk in /system/app/HwMwLauncher or /system/priv-app/HwMwLauncher ? I don't think it matter if it is in app or priv-app, but it must exist. I have it in /system/app.
2) After you enable MultiWindow, do you see the process named HwDualWindowLauncher at Settings > Developer Options > Running services (check also cached processes there)?
3) In build.prop I have the following line: ro.config.hw_multiscreen=true. I think it might be related to MultiWindow as well, but I'm not sure. I didn't try yet to set it to false and see what happens.
Click to expand...
Click to collapse
1). I don't have HwMwLauncher.apk in either location (or anywhere, in fact).
2). No, I don't see the HwDualWindowLauncher process running.
3). I tried that, but it doesn't appear to have any affect.
Thanks anyway.
I'm not too bothered whether this works or not, but if it can be enabled, I will just for the fun of it!

stooby said:
1). I don't have HwMwLauncher.apk in either location (or anywhere, in fact).
2). No, I don't see the HwDualWindowLauncher process running.
3). I tried that, but it doesn't appear to have any affect.
Thanks anyway.
I'm not too bothered whether this works or not, but if it can be enabled, I will just for the fun of it!
Click to expand...
Click to collapse
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
1) Download HwMwLauncher.zip from HERE and extract it.
2) Copy HwMwLauncher folder to system/app.
3) Set the correct permissions for folders and files (.apk and .odex). I've attached screenshots with the permissions as well. The permissions of oat and arm64 folders must be same as the one for HwMwLauncher folder. And the permission of .odex file must be same as .apk one.
4) Reboot. Now I'd say that it should work. Make sure that ro.huawei.multiwindow=true in build.prop, but also ro.config.hw_multiscreen=true (just in case, I still don't know the purpose of this line as I didn't try to set it to false yet).
@carmeloamg :
If you don't have HwMwLauncher neither, then follow the same steps I've wrote in this post and report if it works.

#Henkate said:
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
1) Download HwMwLauncher.zip from HERE and extract it.
2) Copy HwMwLauncher folder to system/app.
3) Set the correct permissions for folders and files (.apk and .odex). I've attached screenshots with the permissions as well. The permissions of oat and arm64 folders must be same as the one for HwMwLauncher folder. And the permission of .odex file must be same as .apk one.
4) Reboot. Now I'd say that it should work. Make sure that ro.huawei.multiwindow=true in build.prop, but also ro.config.hw_multiscreen=true (just in case, I still don't know the purpose of this line as I didn't try to set it to false yet).
Click to expand...
Click to collapse
That's fixed it!
Thanks for your help.

#Henkate said:
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
1) Download HwMwLauncher.zip from HERE and extract it.
2) Copy HwMwLauncher folder to system/app.
3) Set the correct permissions for folders and files (.apk and .odex). I've attached screenshots with the permissions as well. The permissions of oat and arm64 folders must be same as the one for HwMwLauncher folder. And the permission of .odex file must be same as .apk one.
4) Reboot. Now I'd say that it should work. Make sure that ro.huawei.multiwindow=true in build.prop, but also ro.config.hw_multiscreen=true (just in case, I still don't know the purpose of this line as I didn't try to set it to false yet).
@carmeloamg :
If you don't have HwMwLauncher neither, then follow the same steps I've wrote in this post and report if it works.
Click to expand...
Click to collapse
I didn't have it. Placed and fixed but it only allows to use three system apps as second window even having some other multi window ready apps. For instance I've got WhatsApp and Telegram I can use multi window each one separately with gallery, files and videos but not both together. Snapshot attached. Same for you @stooby ?
Thanks @#Henkate !

very easy and smart! working very well without problems ...thanks

carmeloamg said:
I didn't have it. Placed and fixed but it only allows to use three system apps as second window even having some other multi window ready apps. For instance I've got WhatsApp and Telegram I can use multi window each one separately with gallery, files and videos but not both together. Snapshot attached. Same for you @stooby ?
Thanks @#Henkate !
Click to expand...
Click to collapse
Yes, same for me. When I had my Note 4, there was an Xposed module that enabled all apps for multi window use. Unfortunately, it's not working on these devices. I'll keep investigating.

stooby said:
Yes, same for me. When I had my Note 4, there was an Xposed module that enabled all apps for multi window use. Unfortunately, it's not working on these devices. I'll keep investigating.
Click to expand...
Click to collapse
HONOR 8: Installing this version of HwMwLauncher makes the multi window natively supported apps to be selectable and the multiwindow_whitelist_apps.xml file placed in /cust/hw/normal/xml make it usable from many other apps that before says not compatible. Only two issues, sometimes launcher (nova launcher) gets stuck on half of it size buy as it comes it goes. The other issue is that you can not use two apps that not appear in HwMwLauncher, just able to open one that is not and then launch another that is on it. See screenshots (example using chrome and instagram).

#Henkate said:
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
...
Click to expand...
Click to collapse
VNS-L21C432B170 Emui 4.1.2 (P9 lite)
I tried now again...
and now it works good!
tested in Portrait and Landscape.
No issues at the moment!
Thanks a lot

working here to
wishing for a fix for Knuckle Sense too...ive searched for that app everywhere with root explorer and just cant find it...
Knuckle sense is renamed branded Qeexo Finger Sense... double knock for screenshot/draw a letter to open an App. ect.
its activated in Intelligence Assistant but not working ...
looks like its disabled by root
---------- Post added at 04:11 PM ---------- Previous post was at 03:55 PM ----------
I have found in /system...
knuckle_gesture.bin...
but cant open it

Redmi Note 5 Kernel auditor forgets settings after +/- 10 minutes

I changed a few things in kernel auditor on my redmi note 5 like intensity of screen saturation or headphone gain (because xiaomi lowers the volume in Europe because of European Union regulations) and phone forgets settings after a few minutes. MIUI 10 9.1.3 from miuipolska(dot)pl kernel InsigniuX. How to fix it?

You need to make kernel adiutor as system app.

Silverowe Plejsy said:
I changed a few things in kernel auditor on my redmi note 5 like intensity of screen saturation or headphone gain (because xiaomi lowers the volume in Europe because of European Union regulations) and phone forgets settings after a few minutes. MIUI 10 9.1.3 from miuipolska(dot)pl kernel InsigniuX. How to fix it?
Click to expand...
Click to collapse
its been like that ever since RN5 release.
go to settings./ then on apply on boot section press TEST itll apply all settings. i do this everytime i reboot phone.

What's +/-10?

AmoghUpadhyay said:
What's +/-10?
Click to expand...
Click to collapse
sometimes more sometimes less than 10 minutes

Spakainz said:
You need to make kernel adiutor as system app.
Click to expand...
Click to collapse
Thanks i will check if it works

raptorddd said:
its been like that ever since RN5 release.
go to settings./ then on apply on boot section press TEST itll apply all settings. i do this everytime i reboot phone.
Click to expand...
Click to collapse
Its aplying settings but still forgeting after few minutes

Spakainz said:
You need to make kernel adiutor as system app.
Click to expand...
Click to collapse
Not working still forgetting settings

Silverowe Plejsy said:
Not working still forgetting settings
Click to expand...
Click to collapse
THERE is no solutions for that (YET)
on every wake i have to reset Kcal values according to what suites my eyes!

Silverowe Plejsy said:
Its aplying settings but still forgeting after few minutes
Click to expand...
Click to collapse
am on evolution os. miui also used masik and official miui. once i hit test it applies and never resets only after reboot.

YasuHamed said:
THERE is no solutions for that (YET)
on every wake i have to reset Kcal values according to what suites my eyes!
Click to expand...
Click to collapse
This is really bad news write if you find solution

try to go to battery setting, and customize the app to have no restriction see if it helps

yuwilson10 said:
try to go to battery setting, and customize the app to have no restriction see if it helps
Click to expand...
Click to collapse
or go to multi task and lock the app

yuwilson10 said:
or go to multi task and lock the app
Click to expand...
Click to collapse
I did it first but it does not work

Still no solution for this? Its a major PITA having to apply these every time i unlock...

Make kernel autiator as system apps using app systemizer this will solve the problem

Silverowe Plejsy said:
This is really bad news write if you find solution
Click to expand...
Click to collapse
what kernel are you using? you can try AGNI kernel
https://forum.xda-developers.com/re...ernel-20-10-2018-agni-miui-oreo-v3-0-t3856580
i reported this issue to @psndna88
plz check whether its been fixed in 4.9agni or not...

shafee03 said:
Make kernel autiator as system apps using app systemizer this will solve the problem
Click to expand...
Click to collapse
Doesnt work under MIUI apps cant be made system. I've tried both titanium backup and app systemizer both end in a reboot with kernel auditor completely removed.

I found this solution on PureCAF kernel group on Telegram, thanks Kugumin for this!
Using a Root Explorer available on Play Store, navigate to system/etc/device_features. You'll find a file called "whyred.xml".
Search for the string "screen_effect_supported" and comment it, by adding <!-- on the starting line and --> on the end.

thomasginn said:
I found this solution on PureCAF kernel group on Telegram, thanks Kugumin for this!
Using a Root Explorer available on Play Store, navigate to system/etc/device_features. You'll find a file called "whyred.xml".
Search for the string "screen_effect_supported" and comment it, by adding <!-- on the starting line and --> on the end.
Click to expand...
Click to collapse
It works it really works! Cannot thank you enough for posting this and Kugumin for giving the solution. Thank you both of you!

[FIX] Proximity sensor on Redmi Note 7 and Note 7 Pro (NEEDS ROOT)

1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
Code:
ro.lge.proximity.delay = 150
mot.proximity.delay = 150
5) Save the file
6) Reboot

is this a permanent fix or what?
and how did u figure it out?
thx by the way

It should be permanent. Waiting to see will it stay fixed after rom update tho.
I did a lot of research, tried some apps but it did not work, and finally found this fix on some chinese forum.

mr_techno said:
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
5) Save the file
6) Reboot
Click to expand...
Click to collapse
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know

fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?

mr_techno said:
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
Click to expand...
Click to collapse
PE 10.
AFAIK the instable proximity sensor issue is due to a poor driver released in a Xiaomi firmware, nothing so easy to solve.

Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.

Sentox6 said:
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Click to expand...
Click to collapse
Mine too following the OP instructions ?
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Worked with OP instructions.
Sent from my Redmi Note 7 using XDA Labs

Thanks, it worked perectly on PE 9!

Thanks a lot! Worked wonderfully on PE 9!

if this fix doesnt work and youve tried all kinds of "fixes" you may want to check out this if you have previously changed the screen or frame or had any hardware repair done to your xiaomi redmi note 7, there may be small peices you forgot to install. https://forum.xda-developers.com/redmi-note-7/how-to/fix-xiaomi-redmi-note-7-proximity-t4008965

Did it, seems that solved my problem to hear whatsapp audios outside in the sun. Ty

For now works like a charm in MIUI 11.0.3.0 Global, thanks.
:good:

Just want to say thanks for this fix. Works with PE10 with latest Delta update. For those who don't want root can uninstall magisk after editing build prop no problem at all

CR Droid 6.2 12JAN release. Nothing has changed unfortunately with this trick :crying:

Thanks. I am on Havoc 3.1 and the it fixed it.

Well, this can be included for sure, if y'all can let me know this actually works, I'd add the prop to the device tree. Thanks!

Disable high volume warning

Hi, I want to disable the High volume warning, I already have a solution, right now I use terminal shortcut pro and have created a shortcut to run the command
Code:
settings put global audio_safe_volume_state 0
it work great but doesn't survive a reboot so I have to run the shortcut after every reboot. I found an old thread on reddit that say adding the line
Code:
audio.safemedia.bypass=true
to build.prop can also disable the high volume warning, but the thread was so old, they were talking android 6.0
I plan to try to add this prop on boot using the magisk module MagiskHide Props Config, I know it work great because I already added a prop to reduce the media volume steps to 15 instead of 30, but i dont know if the prop
Code:
audio.safemedia.bypass=true
is still working on android 10
Another solution would be to have an app that run the terminal command
Code:
settings put global audio_safe_volume_state 0
automatically after boot, but I would prefer to add the prop line if anyone can confirm it still work on android 10
Thank you all !

Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk

xe0r said:
Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
After 24 hours testing the audio.safemedia.bypass=true with MagiskHide Props Config, I have not seen the warning yet, but I need to test it longer to be sure it work

Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved !

Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10

memocatcher said:
Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10
Click to expand...
Click to collapse
Only with Magisk module MagiskHide Props Config

jacobyo7 said:
Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved!
Click to expand...
Click to collapse
Hello and thank you for finding a workaround for this stupid issue! Do you know if this is still working on android 11? After installing the module, how can I correctly set it? Thank you so much for your help

I tried setting it with termux but it's not working

addsfsds said:
I tried setting it with termux but it's not working
Click to expand...
Click to collapse
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !

jacobyo7 said:
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !
Click to expand...
Click to collapse
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!

addsfsds said:
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!
Click to expand...
Click to collapse
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com

jacobyo7 said:
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
Click to expand...
Click to collapse
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.

addsfsds said:
Code:
settings put global audio_safe_volume_state 0
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.
Click to expand...
Click to collapse
i can confirm that no app does change the setting of safe volume limit.
All tests on rooted device from LOS14-LOS19. Tried different apps like systemuituner, safevolumelimitdisabler, volumesteps+, jamesdsp etc.
Tried to patch the global variable "safe_media_volume" like described here on a rooted device but no luck.
Just ran
[adb shell] settings put global audio_safe_volume_state 0
via adb, when the message popped up, afterits i had to confirm the nag-screen, to raise the volume. it's so weird..