(FIX)(TEST)CM12 Brightness issue - Xperia Z1 General

Hi All ,
i have seen that so many users are complaining about brightness issue in CM12 ... like it gets lower by its own and then starts flickering ..
i was facing same issue when my phone becomes HOT (50-55+ TEMP) my screen brightness starts getting lower by its own (adaptive brightness off) so i edited below lines in themalmanger.xml
just go to system > etc > thermalmanager.xml and edit
<control name="backlight">
<mitigation level="off"><value resource="backlight">255</value></mitigation>
<mitigation level="1"><value resource="backlight">255</value></mitigation>
<mitigation level="2"><value resource="backlight">255</value></mitigation>
<mitigation level="3"><value resource="backlight">255</value></mitigation>
<mitigation level="4"><value resource="backlight">255</value></mitigation>
</control>
change every value to 255 (max) so that screen wont get dim when phone is hot ....
or just simply delete below lines CAREFULLY ..
<!-- backlight -->
<configuration sensor="temp-emmc">
<threshold>
<mitigation name="backlight" level="off" />
</threshold>
<threshold trigger="424" clear="412">
<mitigation name="backlight" level="1" />
</threshold>
<threshold trigger="440" clear="428">
<mitigation name="backlight" level="2" />
</threshold>
<threshold trigger="456" clear="444">
<mitigation name="backlight" level="3" />
</threshold>
<threshold trigger="464" clear="452">
<mitigation name="backlight" level="4" />
</threshold>
</configuration>
i advice you to learn (study) about thermalmanager.xml carefully ... its so interesting ..... you can solve out most of the issues like slow charging and others ...
i only edited backlight value because when phone is hot my brightness decrease on its own ( may be thermal threshold trigger) but now i dont have any issues.....
i dont noe why google has implemented thermal threshold for brightness ...
REBOOT IS NECESSARY AFTER EDITING ABOVE LINES...
DO IT VERY CAREFULLY... M NOT RESPONSIBLE IF YOUR PHONE EXPLODE OR ANYTHING WRONG HAPPEN TO YOUR PHONE .. THIS METHOD HAS SOLVED MY BRIGHTNESS ISSUE
i need some experienced member to confirm if above methods has solved ur issue or not ... because m sure that those who tried this had done something wrong ..
m using this method from cdroid 16-1-2015 and 19-1-2015 works in both ROM ....
Forgive me for my English
Regards
Naitik..
here is my thermalmanager file View attachment thermanager.txt change extension to xml from txt (cant upload xml file )

Let me explain more
Issue :
Brightness decrease on its own when phone becomes hot and start flickering at lowest brightness ..
How ? :
at certain temp it start to reduce on its own because of thermalmanger.xml
check this
<configuration sensor="temp-emmc">
<threshold>
<mitigation name="backlight" level="off" />
means no thermal trigger
now
<threshold trigger="424" clear="412">
<mitigation name="backlight" level="1" />
means your phone reach to certain temp (424 donno how much temp and how its calculated from temp-emmc) and hence your brightness is reduce to level 1 which is 192 (i think) means it will automatically change your max brightness to 192 from 255 , file found in sys/class/leds/wled:backlight (if i remember right )
clear="412" means your brightness will back to 255 when temp reached to certain level (412 donno how much temp and how its calculated from temp-emmc)
same explanation for below lines
<threshold trigger="440" clear="428">
<mitigation name="backlight" level="2" />
</threshold>
<threshold trigger="456" clear="444">
<mitigation name="backlight" level="3" />
</threshold>
<threshold trigger="464" clear="452">
<mitigation name="backlight" level="4" />
</threshold>
</configuration>
How to solve this ? :
either change all brightness lvl to 255 or delete below lines
<!-- backlight -->
<configuration sensor="temp-emmc">
<threshold>
<mitigation name="backlight" level="off" />
</threshold>
<threshold trigger="424" clear="412">
<mitigation name="backlight" level="1" />
</threshold>
<threshold trigger="440" clear="428">
<mitigation name="backlight" level="2" />
</threshold>
<threshold trigger="456" clear="444">
<mitigation name="backlight" level="3" />
</threshold>
<threshold trigger="464" clear="452">
<mitigation name="backlight" level="4" />
</threshold>
</configuration>
What i did ? :
first changed brightness lvl to 255 and my issue solved but after that i also tried deleting above lines to check if phone goes in to bootloop but no !! i booted successfully so u can simply say that m using both methods .... event on new crdroid 19-01-2015 first i edited brightness lvl to 255 and then deleted above lines after that i flashed ROM and phone was working without any brightness issues .......
This is what all i can say ..
Thanks

Why not use the thermal manager from crdroids Google plus? It fixed everything for me. (If you can't be bothered to manually modify it.)

Chocolatetrain said:
Why not use the thermal manager from crdroids Google plus? It fixed everything for me. (If you can't be bothered to manually modify it.)
Click to expand...
Click to collapse
I tried it, brightness was much better than the "stock" one, but this thread here solved it completely. Thanks a lot OP! (replaced the lines you mentioned with number 255, and also deleted the other ones).

Papanik said:
I tried it, brightness was much better than the "stock" one, but this thread here solved it completely. Thanks a lot OP! (replaced the lines you mentioned with number 255, and also deleted the other ones).
Click to expand...
Click to collapse
my goshh at last some one did it properly and solved brightness issue..... nice ... m very happy that i help you

Flashable version? Or just fixed file? Can you upload?

sulexi said:
Flashable version? Or just fixed file? Can you upload?
Click to expand...
Click to collapse
You just have to use an .xml editor man.
EDIT: @naitik2012 it works with official CM12 nightlies as well.
Thanks again. :good:

Papanik said:
You just have to use an .xml editor man.
EDIT: @naitik2012 it works with official CM12 nightlies as well.
Thanks again. :good:
Click to expand...
Click to collapse
We Can Edit Without rooting phone or need root ?

Virus Detected said:
We Can Edit Without rooting phone or need root ?
Click to expand...
Click to collapse
You need root, and you need to unlock your bootloader.

Will this work for the z3 as well?
Edit: it is working just fine with the z3 (d6603) and should work on every cm12 device theoretically.

Hey I am a bit late. Thank you for this piece of information you have shared, quite a life saver. I used to hate the random brightness spike with lollipop on my z1 compact. Not anymore!
I see you have also mentioned editing thermanager to stop slow charging. Please if you can share more of this since I could be using my phone on charge but instead of battery going up it stays the same or lowers!
Thanks in advance

Thanks,confirmed working here too!

in the latest nightly cm-12-20150315, this method does not work anymore, I have changed it to 255 but the brightness still flickering.
but this method work in the last few nightly.

where can i get the text editor for this ? everyone is trying it and its working and i am stuck trying to find the app / program / location of the editor lolol

I got it work. root explorer did the trick. a big thank you on this

ll_l_x_l_ll said:
I got it work. root explorer did the trick. a big thank you on this
Click to expand...
Click to collapse
Hi Bro ,
if you want to install multiple ROM on your device..
Try this > http://forum.xda-developers.com/xperia-z1/orig-development/mod-multirom-v30x-t3006363..... your kernel need to have multi boot patch for multirom to work ..
i do not use multiple ROM so don;t have much information ...

hi everyone,
aside of auto brightness spikes, did anyone experience this:
http://imgur.com/a/KYWhC
https://youtu.be/E9wyRHnjH3E
it happens when phone is heated (38C and over), but not always at exact temperature so the triggers is rather a combination of events (however the temperature is main suspect, thus the thermal management). can anyone confirm similar issue?

You could also just apply the thermanager.xml from this pending change:
http://review.cyanogenmod.org/#/c/96629/

Change each value to 255 >>>
<control name="backlight">
<mitigation level="off"><value resource="backlight">255</value></mitigation>
<mitigation level="1"><value resource="backlight">255</value></mitigation>
<mitigation level="2"><value resource="backlight">255</value></mitigation>
<mitigation level="3"><value resource="backlight">255</value></mitigation>
<mitigation level="4"><value resource="backlight">255</value></mitigation>
</control>
and delete this >>>>
<!-- backlight -->
<configuration sensor="temp-emmc">
<threshold>
<mitigation name="backlight" level="off" />
</threshold>
<threshold trigger="424" clear="412">
<mitigation name="backlight" level="1" />
</threshold>
<threshold trigger="440" clear="428">
<mitigation name="backlight" level="2" />
</threshold>
<threshold trigger="456" clear="444">
<mitigation name="backlight" level="3" />
</threshold>
<threshold trigger="464" clear="452">
<mitigation name="backlight" level="4" />
</threshold>
</configuration>

Can I use this in CM12.1? THANKS

Related

[Q] Remove Preference in smali

Hello there,
i want to achive a simple thing. Removing an entry in the "SpareParts" app.
This is the xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen
xmlns:android="http://schemas.android.com/apk/res/android">
<PreferenceCategory android:title="@string/device_info_title">
<PreferenceScreen android:title="@string/title_battery_history" android:key="battery_history_settings" android:summary="@string/summary_battery_history">
<intent android:targetPackage="com.android.settings" android:action="android.intent.action.MAIN" android:targetClass="com.android.settings.battery_history.BatteryHistory" />
</PreferenceScreen>
<PreferenceScreen android:title="@string/title_battery_information" android:key="battery_information_settings" android:summary="@string/summary_battery_information">
<intent android:targetPackage="com.android.settings" android:action="android.intent.action.MAIN" android:targetClass="com.android.settings.BatteryInfo" />
</PreferenceScreen>
<PreferenceScreen android:title="@string/title_usage_statistics" android:key="usage_statistics_settings" android:summary="@string/summary_usage_statistics">
<intent android:targetPackage="com.android.settings" android:action="android.intent.action.MAIN" android:targetClass="com.android.settings.UsageStats" />
</PreferenceScreen>
</PreferenceCategory>
<PreferenceCategory android:title="@string/general_title">
<ListPreference android:entries="@array/entries_animations" android:title="@string/title_window_animations" android:key="window_animations" android:summary="@string/summary_window_animations" android:dialogTitle="@string/dialog_title_window_animations" android:entryValues="@array/entryvalues_animations" />
<ListPreference android:entries="@array/entries_animations" android:title="@string/title_transition_animations" android:key="transition_animations" android:summary="@string/summary_transition_animations" android:dialogTitle="@string/dialog_title_transition_animations" android:entryValues="@array/entryvalues_animations" />
<CheckBoxPreference android:title="@string/title_fancy_ime_animations" android:key="fancy_ime_animations" android:summaryOn="@string/summary_on_fancy_ime_animations" android:summaryOff="@string/summary_off_fancy_ime_animations" />
<ListPreference android:entries="@array/entries_font_size" android:title="@string/title_font_size" android:key="font_size" android:summary="@string/summary_font_size" android:dialogTitle="@string/dialog_title_font_size" android:entryValues="@array/entryvalues_font_size" />
<CheckBoxPreference android:title="@string/title_haptic_feedback" android:key="haptic_feedback" android:summaryOn="@string/summary_on_haptic_feedback" android:summaryOff="@string/summary_off_haptic_feedback" />
<CheckBoxPreference android:title="@string/compatibility_mode_title" android:key="compatibility_mode" android:summaryOn="@string/compatibility_mode_summary_on" android:summaryOff="@string/compatibility_mode_summary_off" />
</PreferenceCategory>
[b][SIZE="4"]<PreferenceCategory android:enabled="false" android:title="@string/disabled">
<ListPreference android:entries="@array/entries_end_button" android:title="@string/title_end_button" android:key="end_button" android:summary="@string/summary_end_button" android:dialogTitle="@string/dialog_title_end_button" android:entryValues="@array/entryvalues_end_button" />
</PreferenceCategory>[/SIZE][/b]
</PreferenceScreen>
The preference i want to remove is in bold. Now just deleting it, obviously will cause the app to fc. I have to remove the preference in the smali code.
Unfortunatly i have no idea, where and how exactly implement the right code to remove the preference.
An example on how to remove a preference would be (Just an example, thats not what i want to remove):
Code:
invoke-virtual {p0}, Lcom/android/settings/WirelessSettings;->getPreferenceScreen()Landroid/preference/PreferenceScreen;
move-result-object v12
const-string v13, "toggle_wifi"
invoke-virtual {p0, v13}, Lcom/android/settings/WirelessSettings;->findPreference(Ljava/lang/CharSequence;)Landroid/preference/Preference;
move-result-object v13
invoke-virtual {v12, v13}, Landroid/preference/PreferenceScreen;->removePreference(Landroid/preference/Preference;)Z
If anyone could help me out on where to implement the appropiate code i would be glad to learn about this.
I attached the smali code.
Thanks in advance
This is a system app right? So it's sources might be present. That could save you from smali
Edit-And upto what I remember. Removing a preference from settings.apk mainsetting.xml didn't make it fc
Sent from my GT-S7392 using XDA Premium 4 mobile app
arpitkh96 said:
This is a system app right? So it's sources might be present. That could save you from smali
Edit-And upto what I remember. Removing a preference from settings.apk mainsetting.xml didn't make it fc
Click to expand...
Click to collapse
Thank you for your reply.
Unfortunatly just removing it from the *.xml will cause a fc. I think the system trys to call the preference and as it won't be defined, causing a "Javalang nullPointer exception".
The app is of course available as a source, which would make it very easy to remove the preference in java.
Code:
preferenceScreen.removePreference((ListPreference) findPreference("*********"));
Then again i don't have the appropriate tools at hand and not unlimited bandwidth to download them.
Hence my question if somebody knows how to do it in smali.
Take care
u can also let that preference load custom layout... and make that layout 0.0dip
thats what i did when some preferences were linked to id in smali
check touchwiz resurection settings.apk and then settings.xml
in it i used custom layout called empty_pref.xml
Sent from my Acer S500 CloudMobile

Fixing Low Volume In Calls on LineageOS and RR

1: Download the file from here: https://www.gammerson.com/downloads/lineageos-audi-fix(Gammerson.com).zip
2: Transfer the zip file to your device’s storage;
2: Flash it with TWRP;
3: Wipe Dalvik Cache;
4: Restart your device;
5: Have Fun.
All the credits to the user hemanlu, that send me a private message with this procede.
Thanks if it works!
Will this also work on epic rom?
rouxbee said:
Will this also work on epic rom?
Click to expand...
Click to collapse
Dont know
I would advise against this method, as it more or less disconnects audio configurations completely.
You are better off increasing the /system/etc/mixer_paths_tasha.xml handset ctl's digital volume slightly.
Probably not a good idea to go over default 84, as there may be good reason for Xiaomi setting this as low as 80.
Code:
<path name="handset">
<ctl name="SLIM RX0 MUX" value="AIF_MIX1_PB" />
<ctl name="SLIM_0_RX Channels" value="One" />
<ctl name="RX INT0_1 MIX1 INP0" value="RX0" />
<ctl name="RX INT0 DEM MUX" value="CLSH_DSM_OUT" />
<ctl name="EAR PA Gain" value="G_0_DB" />
[B] <ctl name="RX0 Digital Volume" value="84" />[/B]
<ctl name="PIEZO Port Switch" value="1" />
</path>
Strangely enough when I flash this the calls are perfectly hearable but all of my system sounds / alarms / ringtones are not working anymore.
Does anyone has a solution for this?
EDIT:
I did a 'upgrade' using the latest LOS rom (the same I used) and now the in call volume and the sound works... without flashing the above zip...
Strange but glad it works again
Tiago A said:
1: Download the file from here: https://www.gammerson.com/downloads/lineageos-audi-fix(Gammerson.com).zip
2: Transfer the zip file to your device’s storage;
2: Flash it with TWRP;
3: Wipe Dalvik Cache;
4: Restart your device;
5: Have Fun.
All the credits to the user hemanlu, that send me a private message with this procede.
Thanks if it works!
Click to expand...
Click to collapse
It does not work can you maybe attach the file

Microphone issues

Hi, I have Galaxy S5 klte and Resurrection Remix 5.8.3 (latest version) installed but the microphone does not work correctly. I can record but when I listen to the recording the sound ist very quiet and unclear. How can I fix this problem? Thanks for help!
With my Phone on 6.0.0 at android 8.1.0 is exactly the same.
find mixer_paths.xml in /system/etc/ and modify the "Recording scenario" values to your needs
jizzy001 said:
find mixer_paths.xml in /system/etc/ and modify the "Recording scenario" values to your needs
Click to expand...
Click to collapse
Any examples?
fparri said:
Any examples?
Click to expand...
Click to collapse
The file can be located in /system/etc or /system/vendor/etc (in my case RR 6.0.0 - G900F)
open up the file and edit the values by your needs after editing save it,
set the permissions to -rw-r--r-- (644) and reboot your device
this is my modified version of the original file (just the microphone part)
the values are normaly aroud 85-93...and that is pretty low
Down below the bold values are the ones that should be modified
Code:
<!-- ================================================================ -->
<!-- Recording Scenario -->
<path name="rec-main-mic">
<path name="main-mic" />
<ctl name="DEC2 Volume" value="[B]115[/B]" />
</path>
<path name="rec-sub-mic">
<path name="sub-mic" />
<ctl name="DEC4 Volume" value="[B]110[/B]" />
</path>
<path name="rec-headset-mic">
<path name="ear-mic" />
<ctl name="ADC2 Volume" value="14" />
<ctl name="DEC5 Volume" value="[B]92[/B]" />
</path>
<path name="rec-stereo-mic">
<ctl name="Main Mic Delay" value="4" />
<path name="sub-main-mic" />
<ctl name="DEC2 Volume" value="[B]110[/B]" />
<ctl name="DEC4 Volume" value="[B]110[/B]" />
</path>
<path name="rec-high-gain-main-mic">
<path name="main-mic" />
<ctl name="DEC2 Volume" value="[B]68[/B]" />
</path>
<path name="rec-high-gain-sub-mic">
<path name="sub-mic" />
<ctl name="DEC4 Volume" value="[B]68[/B]" />
</path>
<path name="rec-high-gain-headset-mic">
<path name="ear-mic" />
<ctl name="ADC2 Volume" value="14" />
<ctl name="DEC5 Volume" value="[B]84[/B]" />
</path>
<path name="rec-high-gain-stereo-mic">
<path name="sub-3rd-mic" />
<ctl name="DEC2 Volume" value="[B]72[/B]" />
<ctl name="DEC4 Volume" value="[B]72[/B]" />
</path>
<path name="rec-NS-mic-interview">
<ctl name="ES705 TX1 Enable" value="1" />
<path name="main-sub-mic" />
<ctl name="DEC2 Volume" value="[B]110[/B]" />
<ctl name="DEC4 Volume" value="[B]110[/B]" />
<ctl name="ES705-AP Tx Channels" value="One" />
<ctl name="Internal Route Config" value="7" />
</path>
<path name="rec-NS-mic-conversation">
<ctl name="ES705 TX1 Enable" value="1" />
<path name="main-sub-mic" />
<ctl name="DEC2 Volume" value="[B]112[/B]" />
<ctl name="DEC4 Volume" value="[B]112[/B]" />
<ctl name="ES705-AP Tx Channels" value="One" />
<ctl name="Internal Route Config" value="8" />
</path>
<path name="rec-NS-mic-conference">
<path name="main-sub-mic" />
<ctl name="DEC2 Volume" value="[B]110[/B]" />
<ctl name="DEC4 Volume" value="[B]110[/B]" />
</path>
<!-- end of Recording Scenario -->
<!-- ================================================================ -->
Thanks a lot! I've bookmarked your reply. I'm going to try that tonight at home
fparri said:
Thanks a lot! I've bookmarked your reply. I'm going to try that tonight at home
Click to expand...
Click to collapse
Report if it works
I have the same problem in s5 G900H but i cant find recording scenario in it. Would u plz help me
---------- Post added at 11:54 PM ---------- Previous post was at 11:30 PM ----------
swppy said:
I have the same problem in s5 G900H but i cant find recording scenario in it. Would u plz help me
Click to expand...
Click to collapse
@jizzy001
jizzy001 said:
The file can be located in /system/etc or /system/vendor/etc (in my case RR 6.0.0 - G900F)
open up the file and edit the values by your needs after editing save it,
set the permissions to -rw-r--r-- (644) and reboot your device
this is my modified version of the original file (just the microphone part)
the values are normaly aroud 85-93...and that is pretty low
Down below the bold values are the ones that should be modified
Click to expand...
Click to collapse
I've got the same problem on an Galaxy S5 (SM-G900W8 ) with crDroid. I think both ROMs come from Lineage OS and although I haven't tried it I'll bet Lineage 15.1 has the same problem.
I'd like to give it a try, but I can't seem to modify the file. I mixer_paths.xml in /system/vendor/etc, but when I try to edit it I get a message that it's a read only file system.
Permissions on the directories look OK:
/system 755
/system/vendor/ 755
/system/vendor/etc 755
I also tried to create a file with "touch" in /system/vendor/etc and that failed-confirming the whole directory can not be written. Can someone please tell me what I'm doing wrong.
rootkitty said:
I've got the same problem on an Galaxy S5 (SM-G900W8 ) with crDroid. I think both ROMs come from Lineage OS and although I haven't tried it I'll bet Lineage 15.1 has the same problem.
I'd like to give it a try, but I can't seem to modify the file. I mixer_paths.xml in /system/vendor/etc, but when I try to edit it I get a message that it's a read only file system.
Permissions on the directories look OK:
/system 755
/system/vendor/ 755
/system/vendor/etc 755
I also tried to create a file with "touch" in /system/vendor/etc and that failed-confirming the whole directory can not be written. Can someone please tell me what I'm doing wrong.
Click to expand...
Click to collapse
Just mount the system partition R/W find some tutorial or app how to mount it
swppy said:
I have the same problem in s5 G900H but i cant find recording scenario in it. Would u plz help me
---------- Post added at 11:54 PM ---------- Previous post was at 11:30 PM ----------
@jizzy001
Click to expand...
Click to collapse
Can you send me the whole file or paste iz somewhere?
jizzy001 said:
Just mount the system partition R/W find some tutorial or app how to mount it
Can you send me the whole file or paste iz somewhere?
Click to expand...
Click to collapse
Im not able to snd it through this way would you give ur email address ???
swppy said:
Im not able to snd it through this way would you give ur email address ???
Click to expand...
Click to collapse
[email protected]
Sent from my SM-G900F using Tapatalk
jizzy001 said:
[email protected]
Click to expand...
Click to collapse
Plz check ur email bruh

Boost Mate 9 Oreo Headphones Volume

Hi everybody
This method has been tested and working but you do at your own risk. I will not be held responsible for any damage
To do this your phone must be unlocked and rooted :
*** I use Root Explorer to do this ***
Go to:
odm/etc/audio/hi6403
and open the file named "mixer_volumes_MANHATTAN_normal.xml"
find the lines :
<path name="media-headphone" >
<ctl name="S1 IL PGA GAIN" value="0" />
<ctl name="S1 IR PGA GAIN" value="0" />
</path>
Click to expand...
Click to collapse
replace the zeroes with higher value (7 works perfect for me)
Save
Reboot
Enjoy

increase volume in android headphones 6, 7, 8 is under test

hello guys sorry for my bad English, I bring this little contribution to the forum.
I have p9-Lo9, but the sound is a bit low, I come from an m8 htc and I like it to sound louder than normal, So look in other forums, the way to do it without any results, only exists for the p9 lite, I found a way to do it without using applications, I managed to modify a file of the system that allows us to alter the volume standards,
requirements
have the rooted phone and a file explorer that allows us to enter the system folder
1- for android 6
Download the file mixer_volumes_EVA android 6 or 7 and copy it to system / etc / audio / hi6402.
2- for android 7
enter the root of the whole system, find the folder product / etc / audio / hi6402.
decompress the downloaded files and move them, that's all maybe in the future it could be in oreo, at the moment it does not work modifying the file
links
android 6
https://mega.nz/#!j8Ry1I7R!EAB-OiIW0Q39nhZb4ItzKkLyqwF7jRP9EITeMxBdWVw
android 7
https://mega.nz/#!bkYUCQLY!SHNcAUO9KlWi-hWM1O_o1k_ysHD__fSqdoBHw0yA7_Q
android 8
https://mega.nz/#!G0RwQIwK!Ew1bE4M-DiWhPszOv0owE81ydSc6fPrUD62QlXZqlm8
updated for oreo android
I do not speak English sorry if you do not understand some thing
already works for oreo
luis taylor said:
already works for oreo
Click to expand...
Click to collapse
Do you keep a patent on that or why you don't describe how you do it for Oreo?
hi
zgfg said:
Do you keep a patent on that or why you don't describe how you do it for Oreo?
Click to expand...
Click to collapse
I will update the thread
Headphones volume Oreo
zgfg said:
Do you keep a patent on that or why you don't describe how you do it for Oreo?
Click to expand...
Click to collapse
Oreo
root/ODM/etc/audio/hi6402
Save original mixer_volumes_EVA_ce.xml
Edit
<ctl name="HPL PGA GAIN" value="12" />
<ctl name="HPR PGA GAIN" value="12" />
Replace it
<ctl name="HPL PGA GAIN" value="27" />
<ctl name="HPR PGA GAIN" value="27" />
Copy root/ODM/etc/audio/hi6402
Check permissions. -rw-r--r-- ( 644 ).
Reboot
cunaja said:
Oreo
root/ODM/etc/audio/hi6402
Save original mixer_volumes_EVA_ce.xml
Edit
<ctl name="HPL PGA GAIN" value="12" />
<ctl name="HPR PGA GAIN" value="12" />
Replace it
<ctl name="HPL PGA GAIN" value="27" />
<ctl name="HPR PGA GAIN" value="27" />
Copy root/ODM/etc/audio/hi6402
Check permissions. -rw-r--r-- ( 644 ).
Reboot
Click to expand...
Click to collapse
For some reason (?) I had problems to make a copy of the xml file. Every time I tried, it copied but as an empty file, 0 B.
Eventually, I copied to SD card and back, to get a correct copy, 80,17 KB
hi
cunaja said:
Oreo
root/ODM/etc/audio/hi6402
Save original mixer_volumes_EVA_ce.xml
Edit
<ctl name="HPL PGA GAIN" value="12" />
<ctl name="HPR PGA GAIN" value="12" />
Replace it
<ctl name="HPL PGA GAIN" value="27" />
<ctl name="HPR PGA GAIN" value="27" />
Copy root/ODM/etc/audio/hi6402
Check permissions. -rw-r--r-- ( 644 ).
Reboot
Click to expand...
Click to collapse
no, that does not work in oreo
hi
luis taylor said:
I will update the thread
Click to expand...
Click to collapse
use the files for oreo and you will notice the difference, just moficar a file does not make a difference

Categories

Resources