If you are in a call and the other person hears himself or noises when the top mic is touched, by hair or hat..., you can try this:
[ROOT needed]
Edit this file:
\vendor\etc\mixer_paths_overlay_static.xml
find this sections:
<!-- Dual MIC devices -->
<path name="handset-dmic-endfire">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />
<ctl name="AIF1_CAP Mixer SLIM TX8" value="1" />
<ctl name="CDC_IF TX7 MUX" value="DEC7" />
<ctl name="ADC MUX7" value="AMIC" />
<ctl name="AMIC MUX7" value="ADC3" />
<ctl name="CDC_IF TX8 MUX" value="DEC8" />
<ctl name="ADC MUX8" value="AMIC" />
<ctl name="AMIC MUX8" value="ADC1" />
<ctl name="SLIM_0_TX Channels" value="Two" />
</path>
<path name="speaker-dmic-endfire">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />
<ctl name="AIF1_CAP Mixer SLIM TX8" value="1" />
<ctl name="CDC_IF TX7 MUX" value="DEC7" />
<ctl name="ADC MUX7" value="AMIC" />
<ctl name="AMIC MUX7" value="ADC3" />
<ctl name="CDC_IF TX8 MUX" value="DEC8" />
<ctl name="ADC MUX8" value="AMIC" />
<ctl name="AMIC MUX8" value="ADC1" />
<ctl name="SLIM_0_TX Channels" value="Two" />
</path>
and add this lines, so they look like this:
<!-- Dual MIC devices -->
<path name="handset-dmic-endfire">
<ctl name="DEC8 Volume" value="0" />
<ctl name="DEC7 Volume" value="92" />
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />
<ctl name="AIF1_CAP Mixer SLIM TX8" value="1" />
<ctl name="CDC_IF TX7 MUX" value="DEC7" />
<ctl name="ADC MUX7" value="AMIC" />
<ctl name="AMIC MUX7" value="ADC3" />
<ctl name="CDC_IF TX8 MUX" value="DEC8" />
<ctl name="ADC MUX8" value="AMIC" />
<ctl name="AMIC MUX8" value="ADC1" />
<ctl name="SLIM_0_TX Channels" value="Two" />
</path>
<path name="speaker-dmic-endfire">
<ctl name="DEC8 Volume" value="84" />
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />
<ctl name="AIF1_CAP Mixer SLIM TX8" value="1" />
<ctl name="CDC_IF TX7 MUX" value="DEC7" />
<ctl name="ADC MUX7" value="AMIC" />
<ctl name="AMIC MUX7" value="ADC3" />
<ctl name="CDC_IF TX8 MUX" value="DEC8" />
<ctl name="ADC MUX8" value="AMIC" />
<ctl name="AMIC MUX8" value="ADC1" />
<ctl name="SLIM_0_TX Channels" value="Two" />
</path>
This will set top mic sensitivity to 0, noise cancellation will not work but you can adjust "<ctl name="DEC8 Volume" value="0" />" as needed to have a little noise cancellation, default is 84. I've set it to 0 and i find it very good, no complains about the sound quality.
Also I've set 92 as the sensitivity for the lower mic, and it helps a little. Adjust <ctl name="DEC7 Volume" value="92" /> as you wish, default is 84.
I don't know if this is the best solution, but it helped me, so I share
* to make changes to this file, you need to mount vendor and system in twrp (in twrp>mount>check both)
** please report this bug using Settings > Feedback > and check "Issue" and describe the problem you are having, hopping that Poco devs will look into it.
*** I've built a magisk module to apply this fix, it makes it easier for those who flash roms frequently.
Heyy @wizard8400 i have one other problem, the mic doesn't work in calls on speakerphone but works well with normal. Do you know the fix for this?? I've tried both miui and other custom roms and have same issue.
@ayush.gl I don't think I can help, but for starts you can test if is a hardware problem: go to CIT (tap a few times on kernel version) and test main mic and top mic, I think you need headphones(simple ones, without mic on them) . From what I have tested it seems that on speaker it uses the top mic, in normal call it uses both mics, mainly the bottom one and the top one is for ANC.
wizard8400 said:
@ayush.gl I don't think I can help, but for starts you can test if is a hardware problem: go to CIT (tap a few times on kernel version) and test main mic and top mic, I think you need headphones(simple ones, without mic on them) . From what I have tested it seems that on speaker it uses the top mic, in normal call it uses both mics, mainly the bottom one and the top one is for ANC.
Click to expand...
Click to collapse
hi....thanks for the fix...was plagued with this issue for a while...quick question...this is safe correct? also if i still want noise cancellation instead of setting it to 0 i can set it to like 60 so it wouldn't be so sensitive? thanks
wizard8400 said:
@ayush.gl I don't think I can help, but for starts you can test if is a hardware problem: go to CIT (tap a few times on kernel version) and test main mic and top mic, I think you need headphones(simple ones, without mic on them) . From what I have tested it seems that on speaker it uses the top mic, in normal call it uses both mics, mainly the bottom one and the top one is for ANC.
Click to expand...
Click to collapse
I have tested the mic, it shows passed. Mic also works with recorder, cam, whatsapp calls. Only for calls on speakerphone it doesn't work. Any suggestions
ayush.gl said:
I have tested the mic, it shows passed. Mic also works with recorder, cam, whatsapp calls. Only for calls on speakerphone it doesn't work. Any suggestions
Click to expand...
Click to collapse
Same problem here
anil rajput said:
Same problem here
Click to expand...
Click to collapse
have you found any workaround?
ayush.gl said:
have you found any workaround?
Click to expand...
Click to collapse
No
Thanks will try this
Hey guys, i'm rooted and copied the overlay file to a different location and edited it with es datei explorer, but when i try to copy it back to vendor etc it always says vendor write only and i get a error. What to do to make it writeable. Permission is granted for the datei explorer.....dunno what to do. Have this echo and its really annoying for the peoe i call
Edit: solved it by mounting vendor in recovery and copying my modified file into vendor/etc folder
I'm having the same issue, even at low volume. But I can't find the file specified. Do I have another issue?
@Zundrium
I don't know what ROM you have, I'm on xiaomi.eu latest beta(weekly). You have root and mounted system and vendor in twrp, right?
Please help me I do not know how to do it please help me thanks
@calandula
what you don't know, how to edit the file, how to root? If one of those, then you need to search or open a topic about that operation, else will talk off topic and is not a good practice to be offtopic on a forum. ex.: I can't explain here how to root pocophone f1, there is already a topic about this.
@calandula
what you don't know, how to edit the file, how to root? If one of those, then you need to search or open a topic about that operation, else will talk off topic and is not a good practice to be offtopic on a forum. ex.: I can't explain here how to root pocophone f1, there is already a topic about this.
Hello in voip call like whatsapp work? Thanks
wizard8400 said:
@Zundrium
I don't know what ROM you have, I'm on xiaomi.eu latest beta(weekly). You have root and mounted system and vendor in twrp, right?
Click to expand...
Click to collapse
I used LineageOS and PixelExperience, both have the same issue, when rolling back to beryllium_global_images_V10.2.2.0.PEJMIXM I experience no issues.
I can also confirm that this isn't a firmware issue, I installed fw_beryllium_miui_POCOF1Global_V10.2.2.0.PEJMIXM in all cases.
Zundrium said:
I used LineageOS and PixelExperience, both have the same issue, when rolling back to beryllium_global_images_V10.2.2.0.PEJMIXM I experience no issues.
I can also confirm that this isn't a firmware issue, I installed fw_beryllium_miui_POCOF1Global_V10.2.2.0.PEJMIXM in all cases.
Click to expand...
Click to collapse
Have done the same tests and getting the same results. Seems to be OS related and not firmware.
Cool you made a magisk module! If install it is it permanent? Or when i remove it it gos back to normal?
@Mooatreides magisk module is systemless, you can enable / disable this fix to apply/revert the file. After flashing a new version of the ROM and magisk, this fix is applied, or not depending by the state of the module.
Related
Credit for this goes to @langeveld024, in this thread: http://forum.xda-developers.com/lg-g3/themes-apps/g3-t2936465
I've only modified and tested it for the Sprint LS990 version.
You need to be rooted, and use a root editor to modify the mixer_paths.xml file.
1. Make a backup of your existing file. You might want to make a nandroid backup so if something goes badly wrong you can recover easily.
2. In your root editor, search for the text string "speaker" (with the quote marks). You should find this path:
<path name="speaker">
<ctl name="SLIM RX1 MUX" value="AIF1_PB" />
<ctl name="SLIM_0_RX Channels" value="One" />
<ctl name="RX3 MIX1 INP1" value="RX1" />
<ctl name="RX3 Digital Volume" value="60" />
<ctl name="RX4 Digital Volume" value="60" />
<ctl name="RDAC5 MUX" value="DEM3_INV" />
<ctl name="LINEOUT1 Volume" value="16" />
<ctl name="LINEOUT3 Volume" value="16" />
<ctl name="RX3 HPF cut off" value="MIN_3DB_150Hz" />
<ctl name="SPK Amp Volume" value="3" />
</path>
ABOVE the row <ctl name="RX3 Digital Volume" value="60" />
insert this line. I copied the existing RX3 Digital Volume row, pasted it, and changed RX3 to RX1.
<ctl name="RX1 Digital Volume" value="60" />
When complete, it should look like this:
<path name="speaker">
<ctl name="SLIM RX1 MUX" value="AIF1_PB" />
<ctl name="SLIM_0_RX Channels" value="One" />
<ctl name="RX3 MIX1 INP1" value="RX1" />
<ctl name="RX1 Digital Volume" value="60" />
<ctl name="RX3 Digital Volume" value="75" />
<ctl name="RX4 Digital Volume" value="60" />
<ctl name="RDAC5 MUX" value="DEM3_INV" />
<ctl name="LINEOUT1 Volume" value="16" />
<ctl name="LINEOUT3 Volume" value="16" />
<ctl name="RX3 HPF cut off" value="MIN_3DB_150Hz" />
<ctl name="SPK Amp Volume" value="3" />
</path>
A couple of notes:
(1) Your values may be different than 60. I've edited my mixer_paths multiple times, and no longer remember what the original values are. If yours are different, you can leave them at your current settings.
(2) RX1 = the earpiece, RX3 = the rear speaker. I set the rear speaker louder to get better balance between the two when the phone is face up.
(3) The sound seems to still be mono, not stereo, but there's a noticeable improvement in the sound quality when viewing videos.
Finally, save the file. Make sure permissions are 0644 (rw-,r--,r--). And reboot.
@meyerweb
The top lines should be like this:
<ctl name="SLIM RX1 MUX" value="AIF1_PB" />
<ctl name="SLIM RX2 MUX" value="AIF1_PB" />
<ctl name="SLIM_0_RX Channels" value="Two" />
<ctl name="RX3 MIX1 INP1" value="RX1" />
<ctl name="RX1 MIX1 INP1" value="RX2" />
Then it will be stereo
---------- Post added at 09:44 AM ---------- Previous post was at 09:40 AM ----------
Oh and u might want to add some of these, IF present in headphone path:
<ctl name="COMP0 Switch" value="1" />
<ctl name="DAC1 Switch" value="1" />
<ctl name="CLASS_H_DSM MUX" value="DSM_HPHL_RX1" />
<ctl name="HPHL DAC Switch" value="1" />
<ctl name="HPHL Volume" value="30" />
<ctl name="HPHR Volume" value="30" /
Great find.
langeveld024 said:
@meyerweb
[/COLOR]Oh and u might want to add some of these, IF present in headphone path:
<ctl name="COMP0 Switch" value="1" />
<ctl name="DAC1 Switch" value="1" />
<ctl name="CLASS_H_DSM MUX" value="DSM_HPHL_RX1" />
<ctl name="HPHL DAC Switch" value="1" />
<ctl name="HPHL Volume" value="30" />
<ctl name="HPHR Volume" value="30" /
Click to expand...
Click to collapse
Can you explain what these do? Thanks!
meyerweb said:
Can you explain what these do? Thanks!
Click to expand...
Click to collapse
These will complete a proper configuration, but only if these line's are also found in the headphones path.
Cuz I pasted it from a note 4 path xD
I've made several surround sound mods for several device's (S5, xperia SP, LG G3, and put some time in others who wanna make it for LG G2 and note 4) and in almost every case some of these line's and maybe others may be needed for proper surround sound.
But it is very important to not copy my work by using line's found in some of my mods.
Every mod is device specific and therefore in every device may be other lines be used.
The base principal is the same for any device but it is very important to look in the headphones path and speaker-ear path. Use only those lines.
The lines I posted above are (as I said earlier this post) lines from a note 4, but may appear in ur stock headphones section or so.
The note 4 lines I posted as example will tell the earpiece to play better and louder and will help you to create real stereo effect. (At least, that's what I found out by trial and error)
If u want me to make an test version, send me the file and I'll look into it :thumbup:
Thanks. Attached my mixer_paths file. I haven't had time today to look into it and see if I have those lines or not.
langeveld024 said:
These will complete a proper configuration, but only if these line's are also found in the headphones path.
Cuz I pasted it from a note 4 path xD
I've made several surround sound mods for several device's (S5, xperia SP, LG G3, and put some time in others who wanna make it for LG G2 and note 4) and in almost every case some of these line's and maybe others may be needed for proper surround sound.
But it is very important to not copy my work by using line's found in some of my mods.
Every mod is device specific and therefore in every device may be other lines be used.
The base principal is the same for any device but it is very important to look in the headphones path and speaker-ear path. Use only those lines.
The lines I posted above are (as I said earlier this post) lines from a note 4, but may appear in ur stock headphones section or so.
The note 4 lines I posted as example will tell the earpiece to play better and louder and will help you to create real stereo effect. (At least, that's what I found out by trial and error)
If u want me to make an test version, send me the file and I'll look into it :thumbup:
Click to expand...
Click to collapse
Anyone have tihs working on ZV6? I am running stock ZV6 and cannot get this working. Tried editing myself and tried downloading one in post. It doesn't play anything out the front speaker.
You're on a rooted ZV6?
I'm using it on BarRin, which is a slimmed down ZV6, and it's working fine. Did you make sure permissions were set correctly after modding the file?
One more thought: Did you make only the changes in post #1, or did you also make the changes in post #2? I could never get those to work correctly.
Has anyone tested this on CM12?
Yes sorry assumed that I was rooted is implied to be even attempting this. I have only done post 1 mods, not trying to get stereo going. Permissions are correct, etc. It's not a big deal the increased sound level worked so that speaker by itself is much louder now anyway.
/etc/mixer_paths.xml is apparently related to TinyAlsa (https://stackoverflow.com/questions/26923301/understanding-mixer-paths-xml-in-android).
The file can be edited to reroute or alter audio. "adb root && adb remount && adb push mixer_paths.xml /etc/ && adb reboot"
The file starts with a series of default parameters. I assume each corresponds to a hardware/ALSA value or rounting preference.
XML:
<ctl name="Voice Rx Device Mute" id="0" value="0" />
"id" is used when multiple controls appear under the same name. It's like an indexing scheme.
<ctl name="Voip Mode Config" value="12" />
<ctl name="SLIM_0_RX Channels" value="One" />
<ctl name="SLIM_0_TX Channels" value="One" />
Then there are a series of profiles, which override default parameters.
XML:
<path name="headphones">
...
<ctl name="HPHL DAC Switch" value="1" />
<ctl name="HPHL Volume" value="20" />
<ctl name="HPHR Volume" value="20" />
<ctl name="RX1 Digital Volume" value="82" />
<ctl name="RX2 Digital Volume" value="82" />
<ctl name="COMP1 Switch" value="1" />
</path>
I observed that changed "RX1/2 Digital Volume" changed the output volume. "HPHL/R Volume" had no effect.
Some paths include an inner "path name=" tag. I assume this inherits settings.
XML:
<path name="voice-line">
<path name="voice-headphones" />
</path>
<path name="voice-headphones">
<path name="headphones" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="HPHL Volume" value="20" />
<ctl name="HPHR Volume" value="20" />
<ctl name="RX1 Digital Volume" value="78" />
<ctl name="RX2 Digital Volume" value="78" />
</path>
--------
Now the kicker... What do path names mean?
For example, "headphones" obviously means headphone port, and "speaker" means speakers.
However, there are literally hundreds of speaker, headphones, headsets, handsets, mic, sidetone-iir, tty, etc... How does Android choose which path to enable?
If I'm trying to decrease headphone volume (for earbuds), which settings do I have to change? "headphones" only, or some unknown set of options?
I noticed an interesting <path name="ADSP testfwk">... What could that mean?
A Google search took me to http://www.perkel.com/x/snd_soc_msm . Searching `snd_soc_msm` took me to https://android.googlesource.com/pl.../4765c43/libalsa-intf/snd_soc_msm/snd_soc_msm... The log link references "mako" (Nexus 4), not my Nexus 5X (this is the first commit the file appears). Additionally, the file is not available in "master" branch (replace the hex with master), as apparently libalsa was removed.
jimbo1qaz said:
/etc/mixer_paths.xml is apparently related to TinyAlsa (https://stackoverflow.com/questions/26923301/understanding-mixer-paths-xml-in-android).
The file can be edited to reroute or alter audio. "adb root && adb remount && push mixer_paths.xml /etc/"
The file starts with a series of default parameters. I assume each corresponds to a hardware/ALSA value or rounting preference.
XML:
<ctl name="Voice Rx Device Mute" id="0" value="0" />
"id" is used when multiple controls appear under the same name. It's like an indexing scheme.
<ctl name="Voip Mode Config" value="12" />
<ctl name="SLIM_0_RX Channels" value="One" />
<ctl name="SLIM_0_TX Channels" value="One" />
Then there are a series of profiles, which override default parameters.
XML:
<path name="headphones">
...
<ctl name="HPHL DAC Switch" value="1" />
<ctl name="HPHL Volume" value="20" />
<ctl name="HPHR Volume" value="20" />
<ctl name="RX1 Digital Volume" value="82" />
<ctl name="RX2 Digital Volume" value="82" />
<ctl name="COMP1 Switch" value="1" />
</path>
I observed that changed "RX1/2 Digital Volume" changed the output volume. "HPHL/R Volume" had no effect.
Some paths include an inner "path name=" tag. I assume this inherits settings.
XML:
<path name="voice-line">
<path name="voice-headphones" />
</path>
<path name="voice-headphones">
<path name="headphones" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="HPHL Volume" value="20" />
<ctl name="HPHR Volume" value="20" />
<ctl name="RX1 Digital Volume" value="78" />
<ctl name="RX2 Digital Volume" value="78" />
</path>
--------
Now the kicker... What do path names mean?
For example, "headphones" obviously means headphone port, and "speaker" means speakers.
However, there are literally hundreds of speaker, headphones, headsets, handsets, mic, sidetone-iir, tty, etc... How does Android choose which path to enable?
If I'm trying to decrease headphone volume (for earbuds), which settings do I have to change? "headphones" only, or some unknown set of options?
I noticed an interesting <path name="ADSP testfwk">... What could that mean?
A Google search took me to http://www.perkel.com/x/snd_soc_msm . Searching `snd_soc_msm` took me to https://android.googlesource.com/pl.../4765c43/libalsa-intf/snd_soc_msm/snd_soc_msm... The log link references "mako" (Nexus 4), not my Nexus 5X (this is the first commit the file appears). Additionally, the file is not available in "master" branch (replace the hex with master), as apparently libalsa was removed.
Click to expand...
Click to collapse
"headphones" only, or some unknown set of options?
---------
Yes change "headphones" only
<ctl name="RX1 Digital Volume" value="82" />
<ctl name="RX2 Digital Volume" value="82" />
I don't want people saying "change headphones only".
I'm a programmer. I want to know what the different options mean, which files in the Android source code associates different phone/call/Bluetooth states with different audio paths, and documentation on which paths are used/unused, and when.
Because I want proof that my ears won't get blown out when I get a call, or some app happens to output audio to the wrong path, etc.
Did you ever find any documentation on this? There seem to be many posts about changing this or that, but where are they getting the information from on exactly what is what?
sumade said:
Did you ever find any documentation on this? There seem to be many posts about changing this or that, but where are they getting the information from on exactly what is what?
Click to expand...
Click to collapse
https://github.com/CirrusLogic/tinyhal/blob/master/audio.example.xml
Hey guys. First : Sorry for my maybe bad english
Back to topic :
I realised that my Voicemessages on Whatsapp and Voicerecording are not loud enough, people had problems to hear my voicemessages on Whatsapp,Telegram etc...
When i use normal Telephoning or Videorecording the Volume of Voice is okay.
So i decided to play a little bit with the mixer_paths.xml. After three days of try and error i decided today a last try and it worked !
I copy and paste the Line of the mixer_paths.xml :
<!-- #ifdef VENDOR_EDIT-->
<!-- [email protected]rv,2015/3/19,add for 14049 mic -->
<path name="adc3">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1"/>
<ctl name="SLIM_0_TX Channels" value="One" />
<ctl name="SLIM TX7 MUX" value="DEC4" />
<ctl name="DEC4 MUX" value="ADC3" />
<ctl name="DEC4 Volume" value="84" /> Change "DEC4 Volume" value= 96
<ctl name="IIR1 INP1 MUX" value="DEC4" />
<ctl name="ADC3 Volume" value="13" />Change "ADC3 Volume" value= 19
</path>
Change DEC4 to 96, and ADC3 to 19 that is perfect for me
That is 3x louder with less distortion. But dont go any higher, because i tryed DEC4 = 106 and you are loud as hell, but not good understandable.
Maybe that needs a little bit finetuning, but it is just a dirty fix.
You need to have a rooted device to do that changes
And do not forget to save the file and do a reboot after changes ^^
Greetings from germany
amorosa
A could not to find the lines.
Can you tell me where i can search this line or file where have this information.
I am using HalogenOS
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
Which file i nees use? imgur.com/a/ER1Y7
iago1966 said:
A could not to find the lines.
Can you tell me where i can search this line or file where have this information.
I am using HalogenOS
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
Which file i nees use? imgur.com/a/ER1Y7
Click to expand...
Click to collapse
Use the "Mixer_paths.xml".
It is near the End of the File. There are many lines like this. (adc1,adc2,adc3,adc4,adc5.....dmic1,dmic2,dmic3....) And all lookes like this codeblock i have posted.
Running Resurrection Remix here, my mixer_paths.xml didn't have the ctl elements in that section, but I copy-pasted yours with the altered values and it works like a charm. I was wondering if it'd work for the audio recording during videos, might give it a try once I'll have some free time...
TheZorg said:
Running Resurrection Remix here, my mixer_paths.xml didn't have the ctl elements in that section, but I copy-pasted yours with the altered values and it works like a charm. I was wondering if it'd work for the audio recording during videos, might give it a try once I'll have some free time...
Click to expand...
Click to collapse
Hey, what problem do you have with Audiorecording during videos ? I think its loud enough ??
If you want, i can try to give you a fix.
Here it is :
- <path name="adc4">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />
<ctl name="SLIM_0_TX Channels" value="One" />
<ctl name="SLIM TX7 MUX" value="DEC3" />
<ctl name="DEC3 MUX" value="ADC4" />
<ctl name="DEC3 Volume" value="84" /> <----Try 96
<ctl name="IIR1 INP1 MUX" value="DEC3" />
<ctl name="ADC4 Volume" value="13" /> <----Try 19
This stuff is directly under the adc3 Stuff, that i posted before.
The Problem is : The Camcorder Mic, is using the path "handset-dmic-endfire". And some other Stuff is using that too. You can try to raise the volume.
It will be good, that you give me feedback, if it will work !
If that dont work, change it back to stock-values. I have annother ideas to fix that
amorosa said:
Hey, what problem do you have with Audiorecording during videos ? I think its loud enough ??
If you want, i can try to give you a fix.
Here it is :
- <path name="adc4">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />
<ctl name="SLIM_0_TX Channels" value="One" />
<ctl name="SLIM TX7 MUX" value="DEC3" />
<ctl name="DEC3 MUX" value="ADC4" />
<ctl name="DEC3 Volume" value="84" /> <----Try 96
<ctl name="IIR1 INP1 MUX" value="DEC3" />
<ctl name="ADC4 Volume" value="13" /> <----Try 19
This stuff is directly under the adc3 Stuff, that i posted before.
The Problem is : The Camcorder Mic, is using the path "handset-dmic-endfire". And some other Stuff is using that too. You can try to raise the volume.
It will be good, that you give me feedback, if it will work !
If that dont work, change it back to stock-values. I have annother ideas to fix that
Click to expand...
Click to collapse
I don't know, it seems to have a lower volume... Will try your fix later & I'll come back with feedback! Thanks a lot
amorosa said:
Hey guys. First : Sorry for my maybe bad english
Back to topic :
I realised that my Voicemessages on Whatsapp and Voicerecording are not loud enough, people had problems to hear my voicemessages on Whatsapp,Telegram etc...
When i use normal Telephoning or Videorecording the Volume of Voice is okay.
So i decided to play a little bit with the mixer_paths.xml. After three days of try and error i decided today a last try and it worked !
I copy and paste the Line of the mixer_paths.xml :
<!-- #ifdef VENDOR_EDIT-->
<!-- [email protected]rv,2015/3/19,add for 14049 mic -->
<path name="adc3">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1"/>
<ctl name="SLIM_0_TX Channels" value="One" />
<ctl name="SLIM TX7 MUX" value="DEC4" />
<ctl name="DEC4 MUX" value="ADC3" />
<ctl name="DEC4 Volume" value="84" /> Change "DEC4 Volume" value= 96
<ctl name="IIR1 INP1 MUX" value="DEC4" />
<ctl name="ADC3 Volume" value="13" />Change "ADC3 Volume" value= 19
</path>
Change DEC4 to 96, and ADC3 to 19 that is perfect for me
That is 3x louder with less distortion. But dont go any higher, because i tryed DEC4 = 106 and you are loud as hell, but not good understandable.
Maybe that needs a little bit finetuning, but it is just a dirty fix.
You need to have a rooted device to do that changes
And do not forget to save the file and do a reboot after changes ^^
Greetings from germany
amorosa
Click to expand...
Click to collapse
This bug was present ever since. Thanks for the fix.
Sent from my ONE A2003 using Tapatalk
lalit.kultham said:
This bug was present ever since. Thanks for the fix.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
No Problem. Glad to help u guys ^^
I'm on CM 13 MM now but even on OOS3.1, H2OS or CM14 could not use the mic because the sound was too low .
After your tweak now even Allo works like a charm!
Thank you so much !
Are you running the stock global ROM and you've noticed that even at max volume the headphone jack output is too low? Here's how to fix it.
For some reason Xiaomi uses different mixer settings between global and China ROMs. The ones in China ROM give you substantially louder volume output.
Those settings are stored in 3 files:
/system/etc/mixer_paths.xml, /system/etc/mixer_paths_i2s.xml, and /system/etc/mixer_paths_tasha.xml (I think that only the last one is actually used by the system, but I didn't check it). To fix the audio volume problem you have to extract those files from the China ROM and overwrite the ones on your /system/ partition. Then you just need to reboot and done.
Here are those files from China stable ROM 8.1.3.0: https://drive.google.com/drive/folders/0B0LGcdBSjQjKeERFRmRuM0ZXSlU?usp=sharing
GREAT... thank you so mush
hcwdjk said:
Are you running the stock global ROM and you've noticed that even at max volume the headphone jack output is too low? Here's how to fix it.
For some reason Xiaomi uses different mixer settings between global and China ROMs. The ones in China ROM give you substantially louder volume output.
Those settings are stored in 3 files:
/system/etc/mixer_paths.xml, /system/etc/mixer_paths_i2s.xml, and /system/etc/mixer_paths_tasha.xml (I think that only the last one is actually used by the system, but I didn't check it). To fix the audio volume problem you have to extract those files from the China ROM and overwrite the ones on your /system/ partition. Then you just need to reboot and done.
Click to expand...
Click to collapse
i did it and now there is no sound at all, help me please
never mind, i fixed it. It woks great
This works for the Mi Max as well, albeit using a different filename.
felixmorillo said:
never mind, i fixed it. It woks great
Click to expand...
Click to collapse
how ? i don't have sound too
yorikkk said:
how ? i don't have sound too
Click to expand...
Click to collapse
Probably have to fix the permissions?
felixmorillo said:
never mind, i fixed it. It woks great
Click to expand...
Click to collapse
oreo27 said:
Probably have to fix the permissions?
Click to expand...
Click to collapse
did, no change
yorikkk said:
how ? i don't have sound too
Click to expand...
Click to collapse
i deleted the three files, i rebooted de phone then i move the new files to etc folder, i rebooted the phone and it worked
felixmorillo said:
i deleted the three files, i rebooted de phone then i move the new files to etc folder, i rebooted the phone and it worked
Click to expand...
Click to collapse
that works, thanks...
yorikkk said:
that works, thanks...
Click to expand...
Click to collapse
happy to help
I would actually like to do the opposite, lower the volume on ROMs different from the Global-Stable
Other ROMs I've tried (xiaomi.eu and CM based) increase the volume but also the background noise... At least on sensitive In-Ear monitors.
And CM14/Lineage even changes the sound in other ways, increasing the bass (yes, even with AudioFX "off").
I wish it wasn't so, I prefer the sound as unadultered as possible...
Its working. Thanks a lot
Could someone please upload the mixer_paths_tasha.xml file from the global stable ROM, I'd like to understand what changes are made from this to Xiaomi.eu and to CM/Lineage.
I was able to retrieve it from the ROM image.
It seems the differences are these, in the "headphone" mixer path:
Lines present in Global stable but not on Lineage:
<ctl name="COMP1 Switch" value="0" />
<ctl name="COMP2 Switch" value="0" />
<ctl name="HPHL Volume" value="11" />
<ctl name="HPHR Volume" value="11" />
Lines changed from Global stable to Lineage (below are the original Global Stable lines):
<ctl name="SLIM RX5 MUX" value="AIF4_PB" />
<ctl name="SLIM RX6 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="RX INT1_2 MUX" value="RX5" />
<ctl name="RX INT2_2 MUX" value="RX6" />
RX5 and RX6 become RX2 and RX3.
Changing these settings on the Lineage mixer paths file has an effect on sound, but it isn't consistent. Sometimes, volume and noise is lower (what I wanted), but sometimes it isn't. This with Spotify.
Pausing and resuming playing a song sometimes results in louder and sometimes in lower volume, so it seems it is not reading the setting all the time or consistently...
strikereg said:
I was able to retrieve it from the ROM image.
It seems the differences are these, in the "headphone" mixer path:
Lines present in Global stable but not on Lineage:
<ctl name="COMP1 Switch" value="0" />
<ctl name="COMP2 Switch" value="0" />
<ctl name="HPHL Volume" value="11" />
<ctl name="HPHR Volume" value="11" />
Lines changed from Global stable to Lineage (below are the original Global Stable lines):
<ctl name="SLIM RX5 MUX" value="AIF4_PB" />
<ctl name="SLIM RX6 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="RX INT1_2 MUX" value="RX5" />
<ctl name="RX INT2_2 MUX" value="RX6" />
RX5 and RX6 become RX2 and RX3.
Changing these settings on the Lineage mixer paths file has an effect on sound, but it isn't consistent. Sometimes, volume and noise is lower (what I wanted), but sometimes it isn't. This with Spotify.
Pausing and resuming playing a song sometimes results in louder and sometimes in lower volume, so it seems it is not reading the setting all the time or consistently...
Click to expand...
Click to collapse
I noticed similar changes between Global and China ROMs as well:
Code:
<ctl name="COMP1 Switch" value="0" />
<ctl name="COMP2 Switch" value="0" />
<ctl name="HPHL Volume" value="11" />
<ctl name="HPHR Volume" value="11
strikereg said:
I was able to retrieve it from the ROM image.
It seems the differences are these, in the "headphone" mixer path:
Lines present in Global stable but not on Lineage:
<ctl name="COMP1 Switch" value="0" />
<ctl name="COMP2 Switch" value="0" />
<ctl name="HPHL Volume" value="11" />
<ctl name="HPHR Volume" value="11" />
Lines changed from Global stable to Lineage (below are the original Global Stable lines):
<ctl name="SLIM RX5 MUX" value="AIF4_PB" />
<ctl name="SLIM RX6 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="RX INT1_2 MUX" value="RX5" />
<ctl name="RX INT2_2 MUX" value="RX6" />
RX5 and RX6 become RX2 and RX3.
Changing these settings on the Lineage mixer paths file has an effect on sound, but it isn't consistent. Sometimes, volume and noise is lower (what I wanted), but sometimes it isn't. This with Spotify.
Pausing and resuming playing a song sometimes results in louder and sometimes in lower volume, so it seems it is not reading the setting all the time or consistently...
Click to expand...
Click to collapse
But do you know which lines should change to make the speaker louder?
The <ctl name="HPHL Volume" value="11" /> only increase the headphones volume.
<ctl name="HPHR Volume" value="11" />
The difference is huge btw from Global to China rom.
Apexinioo said:
But do you know which lines should change to make the speaker louder?
The <ctl name="HPHL Volume" value="11" /> only increase the headphones volume.
<ctl name="HPHR Volume" value="11" />
The difference is huge btw from Global to China rom.
Click to expand...
Click to collapse
He simply compared the Global rom with the china ROM to spot the differences.
Can we use the files from the OP on the new Global Beta ROM, which is based on nougat? It's version 7.1.19
*KiD CuDi* said:
Can we use the files from the OP on the new Global Beta ROM, which is based on nougat? It's version 7.1.19
Click to expand...
Click to collapse
Try to compare the files first and see if there are any major differences.
All welcome!
If you notice, the stock camera in the Mi5 records video with the wrong audio channels. The top microphone is the right channel, and the main one is the left one.
This is noticeable when you record moving objects, for example from the left to the right. A sound on the video will be from right to left
To fix this developer error, we need to edit the file mixer_paths_tasha.xml
Looking for section:
Code:
<path name="camcorder-mic">
<path name="handset-mic" />
</path>
<path name="camcorder-dmic">
<ctl name="AIF1_CAP Mixer SLIM TX6" value="1"/>
<ctl name="AIF1_CAP Mixer SLIM TX5" value="1"/>
<ctl name="SLIM_0_TX Channels" value="Two" />
<ctl name="SLIM TX6 MUX" value="DEC6" />
<ctl name="ADC MUX6" value="AMIC" />
<ctl name="AMIC MUX6" value="ADC3" /> [COLOR="SeaGreen"]<-ADC3 change to ADC1[/COLOR]
<ctl name="SLIM TX5 MUX" value="DEC5" />
<ctl name="ADC MUX5" value="AMIC" />
<ctl name="AMIC MUX5" value="ADC1" /> [COLOR="seagreen"]<-ADC1 change to ADC3[/COLOR]
</path>
We need to swap the left and right microphones.
ADC1 - main mic near usb-c
ADC3 - top mic near IR
After editing the file, do not forget to set the permissions -rw-r--r--
After that we reboot the phone.
Now the stock camera records the sound correctly
Great find and solution. However, on my phone(global xiaomi.eu 9.2.1.0) the default settings were
AMIC MUX6...ADC1
AMIC MUX5...ADC3
Swapped values and works well.
More info:
1. mixer_paths_tasha.xml is in etc folder and the camcorder values are about 90% down the page, so there's a lot of scrolling.
2. front cam records audio channels well after changes, don't know if it was affected before.
3. just noticed that if you hold the phone upside down(with volume buttons on the bottom) the video comes completly upsidedown(image and sound) from both cameras. Thought it would automatically turn both so that they are viewed correctly however you hold the phone...