When taking calls through my headset, the voice on the other end is too loud, even when the volume is set to 1/5. I've tried different headsets to no avail. Does anyone know how I can reduce the volume of the call below the minimum volume setting? The phone is rooted.
you could try changing the entry in the mixer_paths.xml file located in the the 'etc' directory.. you'll need root.
look for..
<path name="voice-headphones">
<path name="headphones" />
<ctl name="HPHL Volume" value="20" />
<ctl name="HPHR Volume" value="20" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
</path>
and change the 20 values to 15 and the 84 ones to 83, this should give them the same values as music through headphones.. reboot to take effect, if there no difference change them back
Thank you!
Sorry if this has been asked, I have been googling and not found any particulur answers, the audio on the z3 is too low, I have very easy to drive headphones and several others and it is just too low (Dunu 2000j, Hifiman re600s, Senn ie80)
Tried the mods, but the sound sligthly distorted and it seems that editing the file is the best option, as sony sets a super low limit, apparantly.
Sooo, I know I need to edit :
<ctl name="HPHL Volume" value="19" />
<ctl name="HPHR Volume" value="19" />
Or
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
But what is the diff? im getting the impression "HPHL Volume" is amp, and rx1/2 is just digital amplicfication.
So what is the difference and what do they do?
Thanks,
Thought I'd start a thread for the Qualcomm sd820 S7 / S7 Edge Volume/Sound levels, as it's different than the other S7 / S7E variants. Instead of changing system/etc/mixer_paths.xml, we need to edit mixer_paths_tasha.xml
On my device I have both /system/etc and /root/etc, and for some reason I need to edit /root/etc to make it stick.
Here's how to change the Headphone Max Volume. The file you need to modify is mixer_paths_tasha.xml. In there, look for the following code snippet:
Code:
<path name="headset">
<path name="ear"/>
<ctl name="COMP1 Switch" value="1"/>
<ctl name="COMP2 Switch" value="1"/>
<ctl name="HPHL Volume" value="20"/>
<ctl name="HPHR Volume" value="20"/>
<ctl name="RX1 Mix Digital Volume" value="76"/>
<ctl name="RX2 Mix Digital Volume" value="76"/>
</path>
<path name="headset-44.1">
<path name="ear-44.1"/>
<ctl name="COMP1 Switch" value="1"/>
<ctl name="COMP2 Switch" value="1"/>
<ctl name="HPHL Volume" value="20"/>
<ctl name="HPHR Volume" value="20"/>
<ctl name="RX1 Digital Volume" value="76"/>
<ctl name="RX2 Digital Volume" value="76"/>
</path>
The analog gain, "HPHL/R Volume" is already maxed out at 20. You can safely raise the various "Digital Volume" entries by 8 dB to 84 without adding any distortion. Beyond 84 (likely up to 124!)
I'm hoping this will spur more discussion on our devices' sound, as the chipset, I believe, allows for some really great mods, bringing sound quality up to match HTC etc.. I don't personally know much about the settings in mixer_paths, but please feel free to mess around and post your findings (and PLEASE first make a BACKUP of your mixer_paths_tasha.xml file!!!!!)
Also, permissions on the file should be 644, I just used root explorer so there was no need to add new permissions.
The mixer paths is like none Ive seen before. Im headphones there are no RX volume adjustments any where, has anyone cracked this yet? The volume is way to low
Thanks
USMC retired said:
The mixer paths is like none Ive seen before. Im headphones there are no RX volume adjustments any where, has anyone cracked this yet? The volume is way to low
Thanks
Click to expand...
Click to collapse
hey USMC. can you clarify what you mean by "None i've seen before"? what device's mixer paths are you comparing it to?
this is an area of interest for me as i have tinkered with mixer paths but i do not know the results yet because i haven't been able to get my rom working. the RX volumes are in there. look again. not just mixer paths, but the other mixer path files there's 7 of them
Digitalkarma said:
hey USMC. can you clarify what you mean by "None i've seen before"? what device's mixer paths are you comparing it to?
this is an area of interest for me as i have tinkered with mixer paths but i do not know the results yet because i haven't been able to get my rom working. the RX volumes are in there. look again. not just mixer paths, but the other mixer path files there's 7 of them
Click to expand...
Click to collapse
I have the HTC u11 and the structure is unusual compared to say the pixel phones. If you were to put the 2 XML side by side you would see what I'm talking about. For the HTC there no RX paths in which to change the volume where on other phones those volume values exist
USMC retired said:
I have the HTC u11 and the structure is unusual compared to say the pixel phones. If you were to put the 2 XML side by side you would see what I'm talking about. For the HTC there no RX paths in which to change the volume where on other phones those volume values exist
Click to expand...
Click to collapse
Mind if you upload the Pixel XML for me. I'm curious.
Digitalkarma said:
Mind if you upload the Pixel XML for me. I'm curious.
Click to expand...
Click to collapse
I know what he means.
This is a mixer path for a few other phones (not whole XMLs, sorry), but from what I recall, the Exynos S7, the Pixel and a few other smartphones (LG G5/G6) all have similar mixer path edits like this too.
Nexus 7
Code:
<ctl name="HPHL Volume" value="10" />
<ctl name="HPHR Volume" value="10" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
OnePlus 2
Code:
<path name="handset">
<ctl name="SLIM RX1 MUX" value="AIF1_PB" />
<ctl name="SLIM_0_RX Channels" value="One" />
<ctl name="RX1 MIX1 INP1" value="RX1" />
<ctl name="CLASS_H_DSM MUX" value="DSM_HPHL_RX1" />
<ctl name="DAC1 Switch" value="1" />
<!-- #ifdef VENDOR_EDIT-->
<!-- [email protected],2015/4/3,change to pass test for qualcomm advise -->
<[B]ctl name="RX1 Digital Volume" value="90" [/B]/>
<!-- #endif VENDOR_EDIT-->
</path>
S7 Edge Exynos
Code:
<path name="gain-media-headset">
<ctl name="Noise Gate Switch" value="0" />
<ctl name="HPOUT1L Impedance Volume" value="105" />
<ctl name="HPOUT1R Impedance Volume" value="105" />
<ctl name="HPOUT1L Input 1 Volume" value="43" />
<ctl name="HPOUT1R Input 1 Volume" value="43" />
</path>
Partial Pixel Code (From Head Fi)
{
"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"
}
HPHL & HPHL from what you said before is already maxed out at 20 but where is the digital volume values on the U11? Viper's ROM has an audio boost for headphones, but they have edited almost every mixer path file. I'll compare when I have the time.
The OP3T was also similar to this, HPHL and HPHR were already maxed out at 20. Editing digital volume via a kernel (Such as Flar's) introduced distortion immediately so wasn't worth it.
This is also quite nice to look at
https://docs.google.com/document/d/1NqfEpbhXfXyqRPJoLxtifbEMNCEuVOIokwT5kyjJ2KI/pub
Im sure it isnt structured in the same order, no surprises there but its similar in referencing which is all that matters.
There are 7 RX Digitals from RX1 through RX7 in the U11 mixer, I think RX1 and 2 has something directly to do with headphones, not sure what the other RX's do. Probably another two is responsible for the top and bottom speaker and who knows what the other 3 do..
There is also a dedicated RX for ANC, 44.1 headphones etc. Thats not in the main mixer path
---------- Post added at 03:06 AM ---------- Previous post was at 02:25 AM ----------
Galactus said:
HPHL & HPHL from what you said before is already maxed out at 20 but where is the digital volume values on the U11? Viper's ROM has an audio boost for headphones, but they have edited almost every mixer path file. I'll compare when I have the time.
The OP3T was also similar to this, HPHL and HPHR were already maxed out at 20. Editing digital volume via a kernel (Such as Flar's) introduced distortion immediately so wasn't worth it.
This is also quite nice to look at
https://docs.google.com/document/d/1NqfEpbhXfXyqRPJoLxtifbEMNCEuVOIokwT5kyjJ2KI/pub
Click to expand...
Click to collapse
Yeah most of the digital values are set at 84 on the U11 as well, not all. Anything more than 84 and you'll start to get distortion if you're volume rocker is set on the higher levels. The registered values are 0(-84 db) to 124(+40 db)
Digitalkarma said:
Im sure it isnt structured in the same order, no surprises there but its similar in referencing which is all that matters.
There are 7 RX Digitals from RX1 through RX7 in the U11 mixer, I think RX1 and 2 has something directly to do with headphones, not sure what the other RX's do. Probably another two is responsible for the top and bottom speaker and who knows what the other 3 do..
There is also a dedicated RX for ANC, 44.1 headphones etc. Thats not in the main mixer path
---------- Post added at 03:06 AM ---------- Previous post was at 02:25 AM ----------
Yeah most of the digital values are set at 84 on the U11 as well, not all. Anything more than 84 and you'll start to get distortion if you're volume rocker is set on the higher levels. The registered values are 0(-84 db) to 124(+40 db)
Click to expand...
Click to collapse
On Vipers ROM the values seem to be set to 88 for most things.
Using V4A increasing software gain by 6dB doesn't introduce any audible background noise or distortion on my RHA MA 750. Also noticed that in "mixer_paths_tavil" they have removed some lines.
Before
Code:
<path name="headphones-voice">
<path name="headphones-voice-generic" />
<path name="sidetone-headphones" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
<path name="headphones-fm">
<path name="headphones-generic" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="COMP2 Switch" value="1" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
<path name="headphones-hw-voip">
<path name="headphones-voice-generic" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="COMP2 Switch" value="1" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
<path name="headphones-audio-voip">
<path name="headphones-voice-generic" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="COMP2 Switch" value="1" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
After
Code:
<path name="headphones-voice">
<path name="headphones-voice-generic" />
<path name="sidetone-headphones" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
<path name="headphones-fm">
<path name="headphones-generic" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
<path name="headphones-hw-voip">
<path name="headphones-voice-generic" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
<path name="headphones-audio-voip">
<path name="headphones-voice-generic" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
I'd be content with using the Usonic headphones if they weren't so crackly at the high end, sibilant songs sound harsher than they should.
On another note, HTC have done something to the mixer paths that has now ruined editing volume steps. On the original firmware, I could set volume steps via Magisk modules to anything I wanted, and it worked fine for the 3.5mm adapter. After updating to 1.13, the volume steps simply repeat once you go past step 15, which is rather annoying. (It is also busted in Vipers ROM).
Digitalkarma said:
Mind if you upload the Pixel XML for me. I'm curious.
Click to expand...
Click to collapse
Galactus said:
On Vipers ROM the values seem to be set to 88 for most things.
Using V4A increasing software gain by 6dB doesn't introduce any audible background noise or distortion on my RHA MA 750. Also noticed that in "mixer_paths_tavil" they have removed some lines.
Before
Code:
<path name="headphones-voice">
<path name="headphones-voice-generic" />
<path name="sidetone-headphones" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
<path name="headphones-fm">
<path name="headphones-generic" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="COMP2 Switch" value="1" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
<path name="headphones-hw-voip">
<path name="headphones-voice-generic" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="COMP2 Switch" value="1" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
<path name="headphones-audio-voip">
<path name="headphones-voice-generic" />
<ctl name="COMP1 Switch" value="1" />
<ctl name="COMP2 Switch" value="1" />
<ctl name="RX0 Digital Volume" value="84" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="HPHL Volume" value="16" />
<ctl name="HPHR Volume" value="16" />
</path>
After
Code:
<path name="headphones-voice">
<path name="headphones-voice-generic" />
<path name="sidetone-headphones" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
<path name="headphones-fm">
<path name="headphones-generic" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
<path name="headphones-hw-voip">
<path name="headphones-voice-generic" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
<path name="headphones-audio-voip">
<path name="headphones-voice-generic" />
<ctl name="RX0 Digital Volume" value="88" />
<ctl name="RX1 Digital Volume" value="88" />
<ctl name="HPHL Volume" value="17" />
<ctl name="HPHR Volume" value="17" />
</path>
I'd be content with using the Usonic headphones if they weren't so crackly at the high end, sibilant songs sound harsher than they should.
On another note, HTC have done something to the mixer paths that has now ruined editing volume steps. On the original firmware, I could set volume steps via Magisk modules to anything I wanted, and it worked fine for the 3.5mm adapter. After updating to 1.13, the volume steps simply repeat once you go past step 15, which is rather annoying. (It is also busted in Vipers ROM).
Click to expand...
Click to collapse
I forgot about RX0, there's 8 RX's.. anyhow
Actually the before and after is reversed. HTC added in the Comp switches to the path names. if my memory is right and assuming things haven't changed since then the volume step controls are handled in the framework.jar, I've applied code on the increase volume step mod before on previous devices.
Besides HTC didnt really alter the mixer path too much from update to update to warrant breaking the volume step so I don't think mixer path has anything to do with it at all. the few tweaks HTC made is related to headphone output.
Also for Usonic try editing the ANC(active noise cancellation) values then maybe reduce the RX and increase the HPH
Right I've done some actual testing
@Digitalkarma
Controlling loudness of USonic headphones only when noise cancellation is enabled works by editing the file below. 3.5mm adapter doesn't change regardless of what I have tried.
Code:
<path name="anc-headphones">
<ctl name="COMP1 Switch" value="0" />
<ctl name="COMP2 Switch" value="0" />
<ctl name="ANC Function" value="ON" />
<ctl name="ANC Slot" value="0" />
<ctl name="SLIM RX2 MUX" value="AIF4_PB" />
<ctl name="SLIM RX3 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="ADC MUX10" value="AMIC" />
<ctl name="AMIC MUX10" value="ADC3" />
<ctl name="ADC MUX12" value="AMIC" />
<ctl name="AMIC MUX12" value="ADC4" />
<ctl name="ANC0 FB MUX" value="ANC_IN_HPHL" />
<ctl name="ANC1 FB MUX" value="ANC_IN_HPHR" />
<ctl name="ADC3 Volume" value="8" />
<ctl name="ADC4 Volume" value="8" />
<ctl name="RX INT1_1 MIX1 INP0" value="RX2" />
<ctl name="RX INT2_1 MIX1 INP0" value="RX3" />
[B]<ctl name="RX1 Digital Volume" value="74" />
<ctl name="RX2 Digital Volume" value="74" />[/B]
<ctl name="ANC OUT HPHL Enable Switch" value="1" />
<ctl name="ANC OUT HPHR Enable Switch" value="1" />
</path>
here you go galactus. this is the Sprint version. everything else is the same besides tavil. there is ver. 29 and ver. 30, HTC made a few changes there
Galactus said:
Right I've done some actual testing
@Digitalkarma
Controlling loudness of USonic headphones only when noise cancellation is enabled works by editing the file below. 3.5mm adapter doesn't change regardless of what I have tried.
Code:
<path name="anc-headphones">
<ctl name="COMP1 Switch" value="0" />
<ctl name="COMP2 Switch" value="0" />
<ctl name="ANC Function" value="ON" />
<ctl name="ANC Slot" value="0" />
<ctl name="SLIM RX2 MUX" value="AIF4_PB" />
<ctl name="SLIM RX3 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="ADC MUX10" value="AMIC" />
<ctl name="AMIC MUX10" value="ADC3" />
<ctl name="ADC MUX12" value="AMIC" />
<ctl name="AMIC MUX12" value="ADC4" />
<ctl name="ANC0 FB MUX" value="ANC_IN_HPHL" />
<ctl name="ANC1 FB MUX" value="ANC_IN_HPHR" />
<ctl name="ADC3 Volume" value="8" />
<ctl name="ADC4 Volume" value="8" />
<ctl name="RX INT1_1 MIX1 INP0" value="RX2" />
<ctl name="RX INT2_1 MIX1 INP0" value="RX3" />
[B]<ctl name="RX1 Digital Volume" value="74" />
<ctl name="RX2 Digital Volume" value="74" />[/B]
<ctl name="ANC OUT HPHL Enable Switch" value="1" />
<ctl name="ANC OUT HPHR Enable Switch" value="1" />
</path>
Click to expand...
Click to collapse
unless maybe try turning off the ANC OUT enable switch to 0?
anyway. so there is no difference editing the headphones path and headphones 44.1 path? also try editing the initial HPH settings back to 20 too. they originally had it at 20 but changed it to 16 on the latest version.
that's what i have set on my Sprint DK11 rom. 20 for all HPH. 84 on ANC, HP and HP 44.1 paths. glad to know there is an audible change with ANC
Digitalkarma said:
unless maybe try turning off the ANC OUT enable switch to 0?
anyway. so there is no difference editing the headphones path and headphones 44.1 path? also try editing the initial HPH settings back to 20 too. they originally had it at 20 but changed it to 16 on the latest version.
that's what i have set on my Sprint DK11 rom. 20 for all HPH. 84 on ANC, HP and HP 44.1 paths. glad to know there is an audible change with ANC
Click to expand...
Click to collapse
We have lift off in terms of editing audio levels with the USonic Without ANC enabled
I accidentally deleted a comma over the value hence it didn't register when I tried it.
Code:
<path name="headphones">
<ctl name="SLIM RX2 MUX" value="AIF4_PB" />
<ctl name="SLIM RX3 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="RX INT1_2 MUX" value="RX2" />
<ctl name="RX INT2_2 MUX" value="RX3" />
[B]<ctl name="RX1 Mix Digital Volume" value="74" />
<ctl name="RX2 Mix Digital Volume" value="74" />[/B]
</path>
I set both to 90 and I hear no distortion, of course I didn't max out and in fact will lower it. The USonic is super loud now. Either way, all other mixer path edits seem to be ignored. The USonic headphones don't change at all until you edit the mixer_paths_tavil.
Next step, trying to do the same with 3.5mm adapter, so far all my efforts have failed. 3.5mm adapter doesn't get louder or quieter regardless of what is done.
Galactus said:
We have lift off in terms of editing audio levels with the USonic Without ANC enabled
I accidentally deleted a comma over the value hence it didn't register when I tried it.
Code:
<path name="headphones">
<ctl name="SLIM RX2 MUX" value="AIF4_PB" />
<ctl name="SLIM RX3 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="RX INT1_2 MUX" value="RX2" />
<ctl name="RX INT2_2 MUX" value="RX3" />
[B]<ctl name="RX1 Mix Digital Volume" value="74" />
<ctl name="RX2 Mix Digital Volume" value="74" />[/B]
</path>
I set both to 90 and I hear no distortion, of course I didn't max out and in fact will lower it. The USonic is super loud now. Either way, all other mixer path edits seem to be ignored. The USonic headphones don't change at all until you edit the mixer_paths_tavil.
Next step, trying to do the same with 3.5mm adapter, so far all my efforts have failed. 3.5mm adapter doesn't get louder or quieter regardless of what is done.
Click to expand...
Click to collapse
So the ANC path works for the Usonic with ANC on and the headphone path is also for Usonic but with ANC off?
Headphone 44.1 is a no go? Just to clarify and confirm. Thanks for testing! Yeah 90 must be a little too loud, 84 is more neutral but louder than 74 that's for sure.
Digitalkarma said:
So the ANC path works for the Usonic with ANC on and the headphone path is also for Usonic but with ANC off?
Headphone 44.1 is a no go? Just to clarify and confirm. Thanks for testing! Yeah 90 must be a little too loud, 84 is more neutral but louder than 74 that's for sure.
Click to expand...
Click to collapse
Yeah ANC path for ANC on and headphones path for ANC off.
44.1 doesn't seem to change anything at all
Galactus said:
Yeah ANC path for ANC on and headphones path for ANC off.
44.1 doesn't seem to change anything at all
Click to expand...
Click to collapse
and the headphones path doesn't do anything for the 3.5 mm headphones as well when listening to USonic and regular headphones side-by-side?
hmmm i wonder what else would change it without altering values all over the place.
Digitalkarma said:
and the headphones path doesn't do anything for the 3.5 mm headphones as well when listening to USonic and regular headphones side-by-side?
hmmm i wonder what else would change it without altering values all over the place.
Click to expand...
Click to collapse
Yeah editing the headphones path doesn't seem to touch the 3.5mm headphones at all. Lowering the value to 10, the USonic without ANC enabled is barely audible. Plug in the adapter and the 3.5mm headphones volume is untouched.
I have no idea where the values for the adaptor or external audio devices would be. There is a ton of USB_AUDIO references in the files but they all seem to have a value of 0 or 1.
I can't really find how it is implemented on other devices either.
Galactus said:
Yeah editing the headphones path doesn't seem to touch the 3.5mm headphones at all. Lowering the value to 10, the USonic without ANC enabled is barely audible. Plug in the adapter and the 3.5mm headphones volume is untouched.
I have no idea where the values for the adaptor or external audio devices would be. There is a ton of USB_AUDIO references in the files but they all seem to have a value of 0 or 1.
I can't really find how it is implemented on other devices either.
Click to expand...
Click to collapse
Time to put on my thinking cap lol
I thought i2s would of had something to do with it..
more than 84
Digitalkarma said:
I forgot about RX0, there's 8 RX's.. anyhow
Actually the before and after is reversed. HTC added in the Comp switches to the path names. if my memory is right and assuming things haven't changed since then the volume step controls are handled in the framework.jar, I've applied code on the increase volume step mod before on previous devices.
Besides HTC didnt really alter the mixer path too much from update to update to warrant breaking the volume step so I don't think mixer path has anything to do with it at all. the few tweaks HTC made is related to headphone output.
Also for Usonic try editing the ANC(active noise cancellation) values then maybe reduce the RX and increase the HPH
Click to expand...
Click to collapse
On the Nexus 6 I took values from 84 to 100 with no problems with distortion or clipping, and as far as the other mixer paths go, most of those arent adjustable. I will keep tinkering and let you know if I find a combo that raises headphones to an acceptable level
I think I have it narrowed down now enough to say that once I find out which MP addjustments are the "master controls" of the entire XML we will be good to go
USMC retired said:
On the Nexus 6 I took values from 84 to 100 with no problems with distortion or clipping, and as far as the other mixer paths go, most of those arent adjustable. I will keep tinkering and let you know if I find a combo that raises headphones to an acceptable level
I think I have it narrowed down now enough to say that once I find out which MP addjustments are the "master controls" of the entire XML we will be good to go
Click to expand...
Click to collapse
You can edit the mixer path tavil which will boost ANC/USonic headphones but believe me when I say the USonic does not need to go past 84 unless you are trying to damage your hearing or the headphone drivers themselves.
As for editing loudness from the 3.5mm adaptor. That is routed to USB_AUDIO which has no editable settings unless you re-route the sound to a SLIMBUS mixer path. By all means give it a go though.
Any suggestions/ development in terms of making the ear-piece & speaker louder by modifying the mixer_paths?
Using squid2's XML files from his github I was able to get phone calls working on all of the ROMs I used, I'm also using Google dialer instead of factory.
Replace the current ones in the system/etc folder and reboot and calls should work.
https://drive.google.com/file/d/0Bzk7IAINn5jfbmFDUG5HaEFTLUE/view?usp=drivesdk
The only problem I'm having is call audio is kind of low and I'm not sure exactly how to make it louder.
In stock ROM, there is: /etc/mixer_paths.xml
I imagine it is in the custom ROMs as well. If so, copy & open the file in Notepad++, then edit line 737 (or look for <ctl name="RX1 Digital Volume" value="84" />
84 is the stock level. Increase it to what you'd like, but don't go crazy. I made mine 88. Save the file and replace it on your phone. Set permissions to rw-r-r and reboot.
You can also edit overall speaker volume by editing lines 25-31, 35,36
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
<ctl name="RX3 Digital Volume" value="84" />
<ctl name="IIR1 INP1 Volume" value="84" />
<ctl name="IIR1 INP2 Volume" value="84" />
<ctl name="IIR1 INP3 Volume" value="84" />
<ctl name="IIR1 INP4 Volume" value="84" />
<ctl name="DEC1 Volume" value="84" />
<ctl name="DEC2 Volume" value="84" />
Again, don't go crazy as you could blow your speaker or your ears.
mn1968 said:
In stock ROM, there is: /etc/mixer_paths.xml
I imagine it is in the custom ROMs as well. If so, copy & open the file in Notepad++, then edit line 737 (or look for <ctl name="RX1 Digital Volume" value="84" />
84 is the stock level. Increase it to what you'd like, but don't go crazy. I made mine 88. Save the file and replace it on your phone. Set permissions to rw-r-r and reboot.
You can also edit overall speaker volume by editing lines 25-31, 35,36
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
<ctl name="RX3 Digital Volume" value="84" />
<ctl name="IIR1 INP1 Volume" value="84" />
<ctl name="IIR1 INP2 Volume" value="84" />
<ctl name="IIR1 INP3 Volume" value="84" />
<ctl name="IIR1 INP4 Volume" value="84" />
<ctl name="DEC1 Volume" value="84" />
<ctl name="DEC2 Volume" value="84" />
Again, don't go crazy as you could blow your speaker or your ears.
Click to expand...
Click to collapse
Worked like a charm, thanks.
KyleBryant said:
The only problem I'm having is call audio is kind of low and I'm not sure exactly how to make it louder.
Click to expand...
Click to collapse
The one I have used works well at the proper level of sound for the boost version. I legitimately believe that there are minor differences with parts in each Moto E4 variant. (I had this issue with the camera back then with the LG Volt {Virgin vs Boost})
CDMA?
Edit: wait, I'm in Qualcomm, pretty sure these are all CDMA right?
Thexmastermind said:
CDMA?
Edit: wait, I'm in Qualcomm, pretty sure these are all CDMA right?
Click to expand...
Click to collapse
No. Only sprint (and all Sprint mvno's) and Verizon are CDMA.
mn1968 said:
In stock ROM, there is: /etc/mixer_paths.xml
I imagine it is in the custom ROMs as well. If so, copy & open the file in Notepad++, then edit line 737 (or look for <ctl name="RX1 Digital Volume" value="84" />
84 is the stock level. Increase it to what you'd like, but don't go crazy. I made mine 88. Save the file and replace it on your phone. Set permissions to rw-r-r and reboot.
You can also edit overall speaker volume by editing lines 25-31, 35,36
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
<ctl name="RX3 Digital Volume" value="84" />
<ctl name="IIR1 INP1 Volume" value="84" />
<ctl name="IIR1 INP2 Volume" value="84" />
<ctl name="IIR1 INP3 Volume" value="84" />
<ctl name="IIR1 INP4 Volume" value="84" />
<ctl name="DEC1 Volume" value="84" />
<ctl name="DEC2 Volume" value="84" />
Again, don't go crazy as you could blow your speaker or your ears.
Click to expand...
Click to collapse
cani use the same method to reduce in call vaolume?
Sachin ET said:
cani use the same method to reduce in call vaolume?
Click to expand...
Click to collapse
You could probably limit your max volume that way. Seems risky and unnecessary though. Why not just turn the volume down?
madbat99 said:
You could probably limit your max volume that way. Seems risky and unnecessary though. Why not just turn the volume down?
Click to expand...
Click to collapse
the minimum volume is comfortable but some people while calling mentioned that they are hearing their own sound back as an echo (may be their sound is being picked up by my microphone )....so i was thinking that reducing it below minimum level could solve it.
Wrong section brother.
Sachin ET said:
the minimum volume is comfortable but some people while calling mentioned that they are hearing their own sound back as an echo (may be their sound is being picked up by my microphone )....so i was thinking that reducing it below minimum level could solve it.
Click to expand...
Click to collapse
No, that's a network issue. Nothing to do with your device's volume in any way. It happens to my wife occasionally on her e4. Usually in certain locations. I know it's the network because it happens with her other phone as well. In her case, it's Sprint (or Sprint mvno).
madbat99 said:
No, that's a network issue. Nothing to do with your device's volume in any way. It happens to my wife occasionally on her e4. Usually in certain locations. I know it's the network because it happens with her other phone as well. In her case, it's Sprint (or Sprint mvno).
Click to expand...
Click to collapse
thanks for replying....I'll check using another SIM card.