Hi all,
I'm a LeeDroid HD user, and I've spent some time over the last few weeks tweaking the auto-brightness settings to maximise battery life. I've reached a point where I haven't found any problems with my settings for 4 or 5 days now, which I think is a pretty good test. It's on the low side under most light conditions, but I've tried to find a point where I can comfortably read the screen without holding it up to my face, and when outside, this includes wearing sunglasses.
Obviously screen brightness is a very personal thing, so you might not like where I've ended up. When you want to impress your friends with your awesome DHD, you can always override the auto setting and just crank up the brightness control manually
Sharing my settings is also not simple either, since it requires a mod to res-framework.apk, which is used for themes. So ... what I will do is show you a graph of my changes to so you can see what I'm doing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Left side of graph is a dark room, right side is the harsh West Australian sun)
And make a flashable zip available for Lee's default ROM, with no themes installed (Base_LeeDroid_Lower_Auto_Brightness_Patch).
And another flashable zip to use if you've installed the "LeeDrOiD Notification power widget" from the LeeDroid HD OP (LeeDroid-PNW-Lower_Auto_Brightness_Patch).
And I've already had a request to make one for the "Stock 1.84" theme from here, so that's also attached (Stock_1.84-Lower_Auto_Brightness_Patch).
If you have another theme/mod installed, I think that flashing the above will wreck it ... be warned!
If you have a specific theme/mod you're using and want to try my settings, just send me a link to it and I'll cook up a flashable zip for it ... it doesn't take long. Alternatively if you know what you're doing, I can provide my arrays.xml file and you can do it yourself.
ALL files in this post are to be flashed with cwm 2.5.1.3 ... I haven't tested with any other version.
Even though I've tested all these patches myself, I'm not an expert at this, so PLEASE PLEASE PLEASE take a nandroid backup first in case I've done something fundamentally wrong.
If you don't like my settings, you can either restore your nandroid backup, or if it was a theme specific patch, you could just apply the theme again.
If it all goes pear-shaped ... I TAKE NO RESPONSIBILITY!
Hope somebody (other than myself) can benefit from my experimenting
If any themers want to incorporate my settings, it's just a change to arrays.xml inside framework-res.apk, nothing else. I'll also attach my arrays.xml (zipped), feel free to use it. As a courtesy, please credit me for the auto-brightness settings If you use them.
As mentioned above, if anyone would like to patch this on top of a specific theme/ROM you have already flashed, just ask and I can cook it up. If you feel like making it easier for me, all I need is framework-res.apk, so if you have a link to just download that, you'll get your patch quicker than if I have to download the entire theme
If anyone has arrived here from the LeeDroid thread, be aware that these are NEW versions of the files, as the ones in that thread were based on the wrong version (they were too low in the 40-90-160 range).
Cheers all, any feedback is appreciated
I have since put together a DIY guide on how to mod the auto-brightness settings inside framework-res.apk yourself. Thanks to those who contributed. Here's the guide!
This was all done on myWindows XP SP3 machine.
1. Download and install a recent Java Runtime Environment (JRE), if you don't already have one. I won't go through those steps, google it. If you're unsure, you can always come back to this step later if it's not working.
2. Download APK Manager from here: http://forum.xda-developers.com/showthread.php?t=695701 ... there's probably lots of good info in this thread if you have questions later about this tool.
3. Unzip the file wherever you want, mine is just on my desktop.
4. I was advised to replace the version of apktool.exe in the 'other' folder with an earlier version. I don't know if this is necessary, and I don't know what version I now have ... possibly 1.3. ** Multiple people have needed to downgrade to the older apktool.exe that I use, so I have attached it to this post. Just extract apktool.exe from the zip and place it in the 'other' folder, replacing the existing apktool.exe.
5. OK, now you should be ready to go! Grab your framework-res.apk either from your phone, or straight from the ROM you've flashed if you haven't applied any themes. framework-res.apk can be found in /system/framework.
6. Copy your framework-res.apk into the "place-apk-here-for-modding" folder.
7. Run script.bat. If you see a text menu pop up then all is good. If you get an error then you've done something wrong! Probably related to your JRE.
8. Choose Option 9 - Decompile apk. Wait until it finishes. Minimise this window now, we'll come back to it later.
9. Go into your projects folder, and you will have a new folder there called framework-res.apk, double click it.
10. Navigate to res/values
11. Open up arrays.xml in a text editor such as Notepad++. Using Windows built in notepad app could cause issues due to Windows -> Linux compatibility issues.
12. Scroll down to the section where it says "<integer-array name="config_autoBrightnessLevels">". This is the section that defines the steps of the ambient light sensor. You probably won't need to adjust these values for now.
13. The next section down should be "<integer-array name="config_autoBrightnessLcdBacklightValues">", this is where the tweaks really begin. The values here relate directly to how bright the screen is at the steps defined in the section above. Minimum value is 1, maximum value seems to be 249, but that could be incorrect. Would make more sense for it to be 255.
14. Change these values as you wish, but change them to the same thing in all these 3 sections - config_autoBrightnessLcdBacklightValues, config_autoBrightnessLcdBacklightValuesUp, config_autoBrightnessLcdBacklightValuesDown.
15. The next 2 sections - config_autoBrightnessButtonBacklightValues, and config_autoBrightnessKeyboardBacklightValues do the same thing, except for the hardware buttons, and keyboard buttons (if present) respectively. Adjust these if you wish.
16. Save the file.
17. Navigate back to the root of the APK Manager directory.
18. Return to your APK Manager window.
19. Choose option 11 - compile APK.
20. When prompted if this is a system APK, type y. Hit Enter.
21. When prompted if you want to copy additional files, type n. Hit Enter.
22. Choose option 22 - Set Current Project
23. Choose option 2 - unsignedframework-res.apk
24. Choose Option 5 - Zipalign apk
25. Choose Option 24 - Quit. On my script version you have to choose option 24 twice. I assume it's a bug on my version, hopefully you won't have to do the same thing.
26. Congrats! You now have a modded framework-res.apk!! You'll find it in the folder "place-apk-here-for-modding", with the new name "unsignedframework-res.apk". Copy it somewhere else (eg. desktop) and rename it to framework-res.apk.
*** If you know how to copy the modded file into a pre-existing flasheable zip, then by all means go for it. If not, continue following the steps below to create a flashable zip in the UOT Kitchen ***
27. Go to the UOT Kitchen - http://uot.dakra.lt/kitchen/ Hopefully it's not busy and it lets you in! If not, you'll have to wait.
28. Go to the file upload tab and upload your new framework-res.apk file.
29. If this is a FROYO ROM that you're modding, then that's it! If it's a GINGERBREAD ROM, then you also have to grab SystemUI.apk and com.htc.resources.apk from your ROM or phone and upload these also. SystemUI.apk can be found in /system/app and com.htc.resources.apk can be found in /system/framework
30. Go back to the Summary tab, then click "Submit Work to Kitchen".
31. When it's done, download the file, boot into cwm, ***DO A NANDROID BACKUP***, then flash your file!
If you've done it right, you're auto-brightness settings should be applied!
If you get stuck in a boot loop, or it just doesn't boot at all ... lucky you have a nandroid backup!
Please note that as this thread progresses, newer versions of the files get posted which makes these ones in the OP redundant. I'll leave them up for now just in case someone needs them, but in general, you'll want to dig deeper into the thread to get flashable files for newer versions of ROMS.
Excellent post.
I will take a look at your final arrays.xml, but I'm happy (so far) with the one I've cooked up with modified at the dimmer end of the scale.
Over the next day or so, I'm going to try and add extra steps (double) into the array, making a more linear or at least a smoother curve. As you said in Lee's thread, not sure if it's up to the build of the kernel.
Even if I can successfully add the extra values and flash, maybe I won't notice if its really working and the values are applied or they are just ignored by the ROM or kernel? What's the worst that can happen? Backup...........
Using the GPS Status & Lux Meter I was able to double check the phone light sensor invrements in:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
UpInTheAir said:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Click to expand...
Click to collapse
That looks right to me, I've not noticed any others in my testing
UpInTheAir said:
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Click to expand...
Click to collapse
Yep, I believe that's right. New drivers would need to be compiled into the kernel, and then the array modified accordingly. This is still something I'm not 100% sure on though, since their could also be a hardware limitation here.
UpInTheAir said:
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
Click to expand...
Click to collapse
The way it works is, if the light sensor returns a value of 10 (which is < 21), then it returns the first value of the array. If it's 40 ( 40 > 21 and 40 < 42) then it'll use the 2nd value ... and so on. that's why there's one extra value in the backlight values arrays than there is in the brightness level arrays, because it's the in betweens, plus less than the first value, plus greater than the last value.
Does that answer your question? Or did I mis-understand?
Thanks for the reply. Confirmed what I had thought.
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system. I run W7, so that's no an option right now. It still is a little beyond my scope of knowledge, but I'm learning bit by bit and also a lot of reading what others have said and researching Mr. Google.
Another useful app is Sensor List, which can graph the changes in lx, but the values are the same as above.
Looks like I'll be keeping this PC when I eventually upgrade so I can run Linux on it to play around...........
UpInTheAir said:
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system.
Click to expand...
Click to collapse
No need to de-compile it dude ... Lee publishes his kernel source code on github!
https://github.com/LeeDroid-/htc-kernel-ace
As for making changes and then re-compiling it ... I have no idea either
Thanks, will check it out and see if I can find out anything useful.
I don't really want to bother Lee as he's either quite busy or having some well deserved time 'off' before the official GB release.
It's not that big a deal to me (as you said, could be hardware limitation, so no chance anyway), but more of having a play, seeing where things are and what happens and why.
Hi mate,
Sorry, I'm late...
Great thread.
Just few questions:
The value I got (have ever seen) in my GPS status are: 10-40-90-160-220(5)?-640-10240
I have not seen these readings: 320, 1280 and 2600.
So, do I need to download and flash arrays.xml.zip first?
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
I had a thorough test on the one slopppy posted for me in LeeDrOid's thread. I works great except when the reading is at 40. At 40, the brightness is lowered to minimum. I know this as the button light has lit up. (My phone got 40-90-160 under fluorescent light, so if brightness is lowered to minimum at 40, it means it goes too low [for me].) Apart from this, everything works fine.
Sitting in the car under the sun, the brightness works well. Screen is readable even with sunglasses on. Walking out from the car, under direct sunlight, brightness still works fine.
Like what I said before, may be we should not be too particular about how it works under the sun as it maybe too bright an environment for our eyes to notice the difference.
So bro slopppy, what should I do now if I want to try them out now?
Regards!
So, do I need to download and flash arrays.xml.zip first?
Click to expand...
Click to collapse
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid but no themes/battery mods etc on top of it
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid and then installed the "Notification Power Widget" from the OP of the LeeDroid HD thread.
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
Click to expand...
Click to collapse
Yep, this is the one you should flash mate
works great except when the reading is at 40. At 40, the brightness is lowered to minimum.
Click to expand...
Click to collapse
I think that 40 isn't a value I come across in my daily life! haha ... I've only ever seen it when I mess around with the sensor to try and make it hit different readings. Couldn't hurt to up it a little I guess.
So bro slopppy, what should I do now if I want to try them out now?
Click to expand...
Click to collapse
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
slopppy said:
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
...
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
Click to expand...
Click to collapse
Thanks mate. Will do a thorough test again for this.
Value 40 is when I'm sitting at the corner and the phone facing away (opposite) the light. My eyes did not notice any much difference in brightness but my phone's sensor did.
Thanks more for the last sentence of your previous post... (maybe push it up a little to 8%-10%? frankly, me too not sure whether it will suit me more... my suggestion, 40 - 8-10%, 90 - 10-12% and 160 - 12-15%)
Edit: Oh, luckily I'm patient enough to wait for your reply this time...lol
Quick feedback for indoor test:
My personal opinion:
at 40, the brightness is a lowered to minimum and button light turn on, hence, a little too low.
at 90, didn't notice any difference in brightness. However, the button light turned off. So there must be an increment but not noticeable to my eyes. Still too low. (the one posted for me in LeeDrOid thread doesn't have this issue)
at 160, a little (really little only) too bright. Few percent reduction is better.
Will again update my feedback for outdoor test.
Regards!
HoneyHD Theme.
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
What about Kalagas theme...i would be very appriciate
Is this for Froyo only because i can't find arrays.xml inside GB framework-res.apk
Yes, sloppy should be a bit more specific, but in his defence, he does mention in the first post cwm recovery 2.5.1.3,...... relative only to LeeDrOiD Froyo.
Sent from my Desire HD using XDA App
Yep, good point, sorry about that. It's for Froyo SENSE ROMs only.
Anyone know how I can modify the title of the thread??
I'll get on to the requests now.
Cheers,
hamurabi1 said:
What about Kalagas theme...i would be very appriciate
Click to expand...
Click to collapse
Which version of Kalagas theme are you running? There seems to be a zillion of them
kennykenneth said:
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
Click to expand...
Click to collapse
Hi,
The framework-res.apk from Honey HD doesn't want to play ball. It gets a couple of errors when I decompile it, then totally flips out when I try to recompile it. It's an intense theme ... maybe he's doing some things which are incompatible with the way I'm going about my changes.
You could always see if the developer is nice enough to cook you up a version using my arrays.xml from the OP. He has other changes in his arrays.xml as well, so he would have to make sure he just uses the auto-brightness section.
Sorry mate!
slopppy said:
Which version of Kalagas theme are you running? There seems to be a zillion of them
Click to expand...
Click to collapse
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].
Thank you!
hamurabi1 said:
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].!
Click to expand...
Click to collapse
Here you mate
As stated in the OP, please do a nandroid backup first ... better safe than sorry ...
Have been using the increase volume steps xposed mod for a while now and that's great for media volume and alarm volume but not for the actual system volume.
Running Monx's rom and wondered if anyone had that ability yet?
Many thanks.
I don't know but maybe this can help, what you think?
Link: http://forum.xda-developers.com/showthread.php?t=2639862
eclyptos said:
I don't know but maybe this can help, what you think?
Link: http://forum.xda-developers.com/showthread.php?t=2639862
Click to expand...
Click to collapse
Yea i've actually tried that out m8, works ok but doesn't alter the steps on the volume.
Not sure if i was as clear as i could be m8 sorry, you know the volume sliders?
Well when expanded theres three of them, the media one when the volume slider mod has been installed is very smooth with what seems like 100s of steps, but the actual volume (the one you say when volume is not expanded) has around 10 - 20 steps max, no where near as smooth as the media one, basically i'm trying to get it so that both volumes are the same and act as smooth as they should.
dladz said:
Yea i've actually tried that out m8, works ok but doesn't alter the steps on the volume.
Not sure if i was as clear as i could be m8 sorry, you know the volume sliders?.
Click to expand...
Click to collapse
Now perfectly clear. I checked and you are right. Music, Video,Games & other Media slider working smooth like 5x (100 steps), Ringtone & Alarms 20x (20 steps).
Sure the output Volume can be Increased or decreased but really don't know how to modified the scrolling of the sliders, somewhere on system perhaps.
eclyptos said:
Now perfectly clear. I checked and you are right. Music, Video,Games & other Media slider working smooth like 5x (100 steps), Ringtone & Alarms 20x (20 steps).
Sure the output Volume can be Increased or decreased but really don't know how to modified the scrolling of the sliders, somewhere on system perhaps.
Click to expand...
Click to collapse
Yea it just doesn't look right lol.
Fair enough though, glad it's not just me.
To be clear........ I'm not asking about getting louder volume but rather more volume steps. 15 steps for multimedia volume just isn't enough. I don't want to go down the custom rom route. The only way I can see to get more volume steps at the moment is to downgrade to MM and use Xposed with Gravitybox or something similar.
Is there any way to get more volume steps on Nougat? It would be really nice if Oneplus could implement this into the stock rom as they have with several other "custom rom" types of features.
appro77 said:
To be clear........ I'm not asking about getting louder volume but rather more volume steps. 15 steps for multimedia volume just isn't enough. I don't want to go down the custom rom route. The only way I can see to get more volume steps at the moment is to downgrade to MM and use Xposed with Gravitybox or something similar.
Is there any way to get more volume steps on Nougat? It would be really nice if Oneplus could implement this into the stock rom as they have with several other "custom rom" types of features.
Click to expand...
Click to collapse
Looking at AudioService in AOSP repository for Android 7.0 I can see:
https://android.googlesource.com/pl...om/android/server/audio/AudioService.java#624
which means if you are rooted you should be able to edit build.prop to insert config line ro.config.media_vol_steps=X where X is the number of desired volume steps.
I too would like this. When streaming BT audio the jump in volume from one step to the next is way too high.
Maybe Oneplus should change it to something like nexus devices, where you can scroll the volume bar continuously from 100% to 0% without steps...much more practical, especially in cases like an alarm, where even the first step now is quite loud.
Exactly same issue here! I hate it!! Music sounds all stupid and with OnePlus tweaking the sound. The music is not natural like it's supposed to be! Saw it on a video **** sucks! Maybe alot of people can't noticed the difference and I do mean ALOT. But I can! And the few also complaining about this too! No equalizer works properly. Treble too high and the mids are low! Bass not even there. I'm actually using my s7 edge for music because the DAC on oneplus 3T is absolutely horrible
Sent from my ONEPLUS A3000 using Tapatalk
C3C076 said:
Looking at AudioService in AOSP repository for Android 7.0 I can see:
https://android.googlesource.com/pl...om/android/server/audio/AudioService.java#624
which means if you are rooted you should be able to edit build.prop to insert config line ro.config.media_vol_steps=X where X is the number of desired volume steps.
Click to expand...
Click to collapse
Confirmed to work on a rooted 3t
install magisk and use the module that increases volume steps. You don't need a custom ROM or xposed for this.
bunu said:
install magisk and use the module that increases volume steps. You don't need a custom ROM or xposed for this.
Click to expand...
Click to collapse
tried all the above on lenovo m8 fhd (android 10) best I get is two volume ranges. No one has a fix for this so looks like a custom rom is needed
I am experiencing low sound in calls after latest update 4.0.3 . Any fixes available ?
Guys after looking into some threads , i got something useful . my call volume is fixed .
Download BuildProp Editor by JRummy on the Google Play Store and open it up. Tap on the “pencil” icon in the top right to bring up the manual editing mode. Scroll all the way to the bottom and add either of the build.prop lines mentioned above and set it equal to the number of volume steps you want to have. For example, entering these two commands at the end will double the number of in-call volume steps and media volume steps respectively.
ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30
Once you’ve entered these commands, reboot your phone. If it worked, you should now have as many volume steps as you specified in build.prop.
Vaibhunk786 said:
Guys after looking into some threads , i got something useful . my call volume is fixed .
Download BuildProp Editor by JRummy on the Google Play Store and open it up. Tap on the “pencil” icon in the top right to bring up the manual editing mode. Scroll all the way to the bottom and add either of the build.prop lines mentioned above and set it equal to the number of volume steps you want to have. For example, entering these two commands at the end will double the number of in-call volume steps and media volume steps respectively.
ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30
Once you’ve entered these commands, reboot your phone. If it worked, you should now have as many volume steps as you specified in build.prop.
Click to expand...
Click to collapse
Thanks for this post. I suffered from annoying low in call volume on my previous device so know how irritating it can be, especially when making calls in busy areas, like a road with heavy traffic. I've only had this device for a few days and since getting it have been away in an area where there is next to no mobile signal so I have not taken or received any calls.
Question
What you have written would seem to suggest that the prop changes would increase the number of volume steps that are applicable for each volume type, but, does does this really alter the actual maximum volume setting? if not then I can't see that this is a fix.
ben_pyett said:
Thanks for this post. I suffered from annoying low in call volume on my previous device so know how irritating it can be, especially when making calls in busy areas, like a road with heavy traffic. I've only had this device for a few days and since getting it have been away in an area where there is next to no mobile signal so I have not taken or received any calls.
Question
What you have written would seem to suggest that the prop changes would increase the number of volume steps that are applicable for each volume type, but, does does this really alter the actual maximum volume setting? if not then I can't see that this is a fix.
Click to expand...
Click to collapse
The code is like this
// Initialize volume
int maxVolume = SystemProperties.getInt("ro.config.vc_call_vol_steps",
MAX_STREAM_VOLUME[AudioSystem.STREAM_VOICE_CALL]);
if (maxVolume != MAX_STREAM_VOLUME[AudioSystem.STREAM_VOICE_CALL]) {
MAX_STREAM_VOLUME[AudioSystem.STREAM_VOICE_CALL] = maxVolume;
AudioSystem.DEFAULT_STREAM_VOLUME[AudioSystem.STREAM_VOICE_CALL] = (maxVolume * 3) / 4;
}
maxVolume = SystemProperties.getInt("ro.config.media_vol_steps",
MAX_STREAM_VOLUME[AudioSystem.STREAM_MUSIC]);
if (maxVolume != MAX_STREAM_VOLUME[AudioSystem.STREAM_MUSIC]) {
MAX_STREAM_VOLUME[AudioSystem.STREAM_MUSIC] = maxVolume;
AudioSystem.DEFAULT_STREAM_VOLUME[AudioSystem.STREAM_MUSIC] = (maxVolume * 3) / 4;
}
i think it alters the max volume but i am not sure but my low call volume is definitely fixed . I just added the lines which i mentioned above.
Testing on my Mi A1, now I have to wait to receive a call. (*Insert a Forever Alone Meme)
EDIT: It changes the number of incremental steps, but the maximum volume remains the same.
Does this fix work on latest OxygenOS betas? There was a TWRP flashable zip before but not sure if it works still.
just clean the speaker grill.
Already cleant the speaker grill. Need the volume to be boosted
volume fix
TheQuarterMile said:
Already cleant the speaker grill. Need the volume to be boosted
Click to expand...
Click to collapse
Flashable zip worked on nugatt but not work in oreo since tasha mixer files are in different localization, you need to manual change values in tasha_miser_paths.xml in system/vendor/etc root folder.
I can send you my edited file.
Deleted by Moderator.
magisk module named "low in call volume fix oneplus 3/3t for RR" not sure if the name is exactly the same but just type "low in" and the module should show up. Tho its for RR i use it on beta 25 and the issue is fixed ! :good:
Increasing the volume steps in root\System\build.prop didn't change the output volume for me.
I solve this issue by modifying a single parameter in "root"\system\vendor\etc\mixer_paths_mtp.xml
(https://forum.xda-developers.com/mi-a1/how-to/how-to-modify-ear-speaker-volume-mi-a1-t3779866)
Best regards.
Fixed it by editing the RX0-RX8 Digital Volume values from 84 to 94 in mixer_paths_tasha.xml file found in /vendor/etc folder and it works! Now I keep the call volume 1-2 levels lower than full. Tried it on OxygenOS beta 24. Thanks for the help everyone.