[FIX][MOD][GUIDE] AUX Cable + Onboard Mic Fix - Nexus 5 Android Development

I believe I have found a solution to a problem that I have found with the Nexus 5 that I never experienced with my GNex before.
https://productforums.google.com/forum/#!category-topic/nexus/calls-and-voicemail/nexus-5/5G5LXC8XHeI
The above link captures a summary of the problem, but I will restate it here. When plugging headphones or an AUX cable into the phone, the phone seems to utilize standard microphone gain settings (that is - you need to practically hold the phone to your face for the other party to hear you well). I primarily use an AUX cable when I'm in my car and have the phone sitting in my center console or on my lap. When I do this, people cannot hear me. BUT when I enable speakerphone mode, the other party can hear me fine (even without unplugging the AUX cable - though no sound would be going through it). Ah-hah, I believe that this must be a software setting issue and not a hardware issue (even though Google offered to do an RMA).
After some research I came across a system file called mixer_paths.xml which has been used by other devs here (thanks folks!) to improve the performance of the audio OUTPUT of the device (that is increasing the volume we hear on our end). But I had seen no mods fixing the audio input / microphone issues I was having.
I tested my theory today by modifying the mixer_paths.xml file to override the default values under <path name="headset-mic"> and <path name="voice-headset-mic"> to mirror those of <path name="voice-speaker-mic">. Initial testing (a simple phone call to my fiancee) seems to indicate that the receiving party cannot tell the difference between my voice whether speaker is on or off when I have headphones plugged in.
In order to perform this mod/fix you will need to be rooted.
WARNINGS:
Make sure to make a backup of your existing mixer_paths.xml file.
This may cause issues if your headset or AUX cable have their own microphone (I don't have one to test with, so I don't know if it causes issues).
I am not guaranteeing results - I am hoping that this fix works for others and others might be able to test and confirm that this does work. I am not a developer - I am just a somewhat tech savvy guy who was trying to resolve an issue I thought was software related. Hopefully someone who is more savvy will come along and implement these changes into an existing app or program for simplicity!
+ Props to Drummerjed for creating the thread for audio output http://forum.xda-developers.com/showthread.php?t=2532788 which inspired my exploring around for this fix. I hope you don't mind I stole some of your directions for ease of posting.
DIRECTIONS
Before you start modifying you need grant ES File Explorer root access. To do this press the icon in the top left corner then scroll down and select Root Explorer, then select Mount R/W, then select RW for both / and /system.
Open ES File Explorer and navigate to /system/etc and find the file "mixer_paths.xml"
Tap on the file and select ES Note Editor
Press the menu button in the top right corner and select Edit
Find: <path name="headset-mic">
You will see this string just below it:
<path name="adc2" />
<ctl name="ADC2 Volume" value="16" />
<ctl name="DEC5 Volume" value="90" />
Change <path name="adc2" /> to <path name="adc3" />
Change <ctl name="ADC2 Volume" value="16" /> to <ctl name="ADC3 Volume" value="14" />
Change <ctl name="DEC5 Volume" value="90" /> to <ctl name="DEC4 Volume" value="97" />
Find: <path name="voice-headset-mic">
You will see this string just below it:
<path name="adc2" />
<ctl name="ADC2 Volume" value="17" />
<ctl name="DEC5 Volume" value="96" />
Change <path name="adc2" /> to <path name="adc3" />
Change <ctl name="ADC2 Volume" value="17" /> to <ctl name="ADC3 Volume" value="14" />
Change <ctl name="DEC5 Volume" value="96" /> to <ctl name="DEC4 Volume" value="97" />
You will notice we are overwriting the default settings from <path name="voice-speaker-mic"> for both. I found this has worked. This may be more modification than necessary to accomplish the same goal. Please feel free to respond if we can further minimize the amount of changes needed in this file to resolve this issue. I'm happy to make edits and adjustments as needed!

Thanks! Going to try this later. I have a pair of headphones (mic included) that the same thing happens to. If I plug them in, no one can hear me over the phone. I need to unplug them or enable speaker to work. I honestly thought it was my headphones.

RoyJ said:
Thanks! Going to try this later. I have a pair of headphones (mic included) that the same thing happens to. If I plug them in, no one can hear me over the phone. I need to unplug them or enable speaker to work. I honestly thought it was my headphones.
Click to expand...
Click to collapse
{
"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"
}
One thing you might also try is taking a look at your headphones+MIC and seeing how they line up with the above chart. From my understanding, the Nexus 5 uses an OMTP set-up and not a CTIA (aka iPhone compatible) set-up internally. You can buy a converter for a few bucks off of Amazon (made by Sony). So if the software fix I suggested in post 1 doesn't help, you could give that a try.
Good luck!

people hear me just fine when i plug in aux cable in my car. but this is handy if the problem ever occurs

I was wondering about those parameters when I was browsing through that file. Was going to play some but never got around to it!
Good job!

zoomass07 said:
One thing you might also try is taking a look at your headphones+MIC and seeing how they line up with the above chart. From my understanding, the Nexus 5 uses an OMTP set-up and not a CTIA (aka iPhone compatible) set-up internally. You can buy a converter for a few bucks off of Amazon (made by Sony). So if the software fix I suggested in post 1 doesn't help, you could give that a try.
Good luck!
Click to expand...
Click to collapse
How can I test which my headphone is?
Also do you know if the nexus 4 used OMTP or CTIA?
Found a post stating that nexus 4 is ctia so if my mic didn't work for those then they'll probably work on my n5 correct (assuming they're omtp).
Also same post stated that ctia has grey rings and omtp is black or blue rings on the 3.5mm plug, any truth to that as I can't tell if mine is black or grey.
Sent from my Nexus 5 using Tapatalk

fone_fanatic said:
How can I test which my headphone is?
Also do you know if the nexus 4 used OMTP or CTIA?
Found a post stating that nexus 4 is ctia so if my mic didn't work for those then they'll probably work on my n5 correct (assuming they're omtp).
Also same post stated that ctia has grey rings and omtp is black or blue rings on the 3.5mm plug, any truth to that as I can't tell if mine is black or grey.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's harder to tell the difference between CTIA and OMTP than it is knowing whether there is a mic or not. I'm not sure about the colorization on the rings. I do know that I've read the N5 is OMTP (not sure how much truth there is to that). You can look into whether your headphones are marketed as "iPhone compatible" it is likely CTIA.

Anyone try this on voip service? I'm using fongo as my main voice service
Sent from my Nexus 5 using Tapatalk

detdett said:
Anyone try this on voip service? I'm using fongo as my main voice service
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Should still work - what I would do is give it a shot! Make a copy of the file and save it as a backup. Make the changes suggested and test it out.
If it doesn't work for you, revert to the back up and report back to us! I started this thread in hopes we could all work together to help alleviate this issue - because Google hasn't expressed an interest in doing so.

I've last cataclysm rom. why es file explorer doesn't allow me to save the new xml?

phantomEVO said:
I've last cataclysm rom. why es file explorer doesn't allow me to save the new xml?
Click to expand...
Click to collapse
Worked fine with root explorer

Great find! I'll be testing these over the course of today!

Is this consistently working for you all? I had great success at first... But now I'm having the same people who told me I sounded fine reporting the poor sound issues again.

i've only <path name="headset-mic"> and <path name="voice-speaker-mic"> and not <path name="voice-headset-mic">

I'm on minimus rom w/ franco kernel. Never had this issue, I leave my aux plugged in from car and when I answer, people can hear me just fine. Sitting about 2-3ft away from phone

Echo fix?
Hello,
This seems to be the same issue i'm having, but no one mentioned an echo...
When I plug an aux cable into the phone and am in a call, the caller hears a horrible echo. I have to put the phone on speakerphone (obviously bypassing the whole sound system) for them to be able to hear properly.
In my head, i image that if i was user the Speakerphone settings for the mic while connecting the aux cable, then it would work.
Is this what your proposed solution would do?
I'd love to get this fixed. Thanks!

Related

[Q] Adjusting microphone sensitivity

Hey everyone,
I recently bought a Nubia Z5S, flashed CyanogenMod12 on it and everything worked perfect until I sent a voice note through Whatsapp.
In other threads, I read that the microphone gain and volume can be adjusted inside /etc/mixer_paths.xml, so I
tweaked some values but all I got were some weird sounding recordings.
My device has 2 microphones : One on the bottom and one near the camera lens on the back.
After some experimenting I found out that dmic1 belongs to the bottom one and dmic3 belongs to the one
on the back. I changed the value inside handset-mic to dmic3 and the recorder app recorded
through the microphone on the back.
Whenever i record a video using the stock camera app the sound is loud and clear , but when i record a voice note with Whatsapp
it isn't loud and clear at all. After I took some sample recordings I looked at the audio-stream properties. This is what I got :
Stock camera : 48.0KHz , 2 channels, AAC (LC)
Whatsapp (sent) : 22.05KHz , 2 channels , AAC (Version 4) (LC)
Whatsapp (received) : 22.05KHz , 1 channel , AAC (Version 4) (LC)
This is my mixer_paths.xml
http://pastebin.com/yiwmCpQM
I use voice notes quite often, so it is important to me that the receiving person can understand what I said.
I really hope someone can help me over here.
need to change from <ctl name="ADC1 Volume" value="19" />
<ctl name="ADC2 Volume" value="19" /> to <ctl name="ADC1 Volume" value="0" />
<ctl name="ADC2 Volume" value="0" />

Audio Output

Hi all,
I've been rooting my devices for a long time (since my HD2) and using custom software, but these days I just don't seem to find the time. Combined with the stock 6P software being pretty good, I haven't felt the need.
However, I am now forced to use my phone as my primary music listening device, usually hooked up to my home stereo. Much like my Nexus 6, before the 6P I have now, the audio output seems very low. On my last phone, there was a file that could be edited to boost the audio output (judging from the values in the file, it defaulted to 80% max vol?) and required at least root to do.
So, a few questions:
Do I have to wipe my device to get root access?
Are there exposed modules that can boost my audio output? Or,
I spotted an 'audiophile' rom recently - would that be my best bet for better audio output?
Any possible solutions to low audio output volume would be great!
Cheers
Ross
phanteh said:
Hi all,
I've been rooting my devices for a long time (since my HD2) and using custom software, but these days I just don't seem to find the time. Combined with the stock 6P software being pretty good, I haven't felt the need.
However, I am now forced to use my phone as my primary music listening device, usually hooked up to my home stereo. Much like my Nexus 6, before the 6P I have now, the audio output seems very low. On my last phone, there was a file that could be edited to boost the audio output (judging from the values in the file, it defaulted to 80% max vol?) and required at least root to do.
So, a few questions:
Do I have to wipe my device to get root access?
Are there exposed modules that can boost my audio output? Or,
I spotted an 'audiophile' rom recently - would that be my best bet for better audio output?
Any possible solutions to low audio output volume would be great!
Cheers
Ross
Click to expand...
Click to collapse
thays my problem before... i came from moto x pure edition.. sound way better there. i dont want to root my nexus 6p .. just install equilizer fx from playstore and disable music fx.. now my audio boosted by 50%. .. its way better now.
Thanks pato, but I've tried EQ apps before, on my nexus 6 - while they may improve audio quality, you can't get any serious volume gains without some serious clipping.
Do I have to wipe my device to get root access?
No
Try this mod.
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Thanks Turgur,
That mod looks like just what I want, but it also says you need a custom recovery - I thought that required unlocking / resetting your device?
Either way I'll probably be trying it out later...
Cheers
Ross
phanteh said:
Thanks Turgur,
That mod looks like just what I want, but it also says you need a custom recovery - I thought that required unlocking / resetting your device?
Either way I'll probably be trying it out later...
Cheers
Ross
Click to expand...
Click to collapse
Unlocking your bootloader will wipe user data, but you can just back it up to a PC, unlock, then copy it all back over after. It adds some time to the process. But, after that, there's very little need to ever format internal again.
Just root it and edit these two value <ctl name="RX1 Digital Volume" value="96" /><ctl name="RX2 Digital Volume" value="96" /> I put mine at 96 now it sounds way better than stock. Its system/etc/mixerpath by the way.
troyd28 said:
Just root it and edit these two value <ctl name="RX1 Digital Volume" value="96" /><ctl name="RX2 Digital Volume" value="96" /> I put mine at 96 now it sounds way better than stock. Its system/etc/mixerpath by the way.
Click to expand...
Click to collapse
How are you doing this in android 7?
I have romtoolbox with rb text editor that work in android 6.
Tried other editors that let me change but will not save.
Well I'm learning, I may have done it the hard way by coping to computer & changing that way but it did work.
Edit: This little edit along with Deuteronomy 2.23 Classic makes sound outstanding!!!
Thanks troyd28
crackerjack1957 said:
Well I'm learning, I may have done it the hard way by coping to computer & changing that way but it did work.
Edit: This little edit along with Deuteronomy 2.23 Classic makes sound outstanding!!!
Thanks troyd28
Click to expand...
Click to collapse
You're welcome, I try not to go above 96 because it distorts and sounds crappy I maxed it at 99, you can also edit the speaker of the phone itself or the microphone volume and other stuff in there. Thanks to the XDA community I learned that little trick.
Anyone get this to work on Pure Nexus?
It has 6 lines to change vrs 4 lines on stock rom.
When I change it breaks sound.
Edit: Forgot to set permissions, working now.

[GUIDE] [7.1.x] [Not working?] Enable 24bit/192KHz playback on Poweramp 704

Please avoid opening this guide on the XDA apps, the images are messed up and displayed on the wrong places as always
Seems that this hack only makes Poweramp think that 192KHz works. Please try this and do this:
Open a terminal emulator
"su"
"dumpsys media.audio_flinger"
Just don't expect miracles for now!
I've been trying for months to make Poweramp work in hi-res mode on Nougat, and finally, it works! I'm pretty sure that the DAC in use is the Snapdragon one (I'm in MiFavor 5.0 and using the super/advanced switch does nothing, not even a stutter) but it's 192KHz still, so, it's better than nothing. If anyone can try on an LOS-based ROM (where the AKM DAC is supposedly used all the time) we may get 192KHz out of that DAC!
I'm not sure if this method wouldn't work on other Android versions. But I only tried on 7.1.1.
Please be sure that you downloaded Poweramp 704 from the official forum - the one on Play store is 703 which doesn't support Hi-Res on Nougat!
I found this fix on the Poweramp official forum, by user dhenyaw.
•Download a build.prop editor or a file manager with root access. Personally, I use Root Browser. If you will use a build.prop editor, just skip the next step.
•Once you open Root Browser, your root directory will appear. Scroll down and open the "system" folder, then scroll down and open the "build.prop" file
•Once you are in build.prop, you have to find the "ro.product.manufacturer" line. In my case it was around line 30.
{
"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"
}
•Add a "#" in front of the "ro.product.manufacturer=ZTE" line, so that you can revert the change if other things break. Also, write just below "ro.product.manufacturer=samsung" and "persist.audio.uhqa=1" just like in the picture 2:
•Save the changes, reboot your phone
After your phone boots, connect some headphones, open Poweramp, play a hi-res FLAC file and go to Audio - Output - Hi-res output, then check if the active output is Wired headsets and the frequency it is outputting to.
Enjoy!
Doesn't work for me. Build.prop just resets after a reset. But even with a soft reset, Poweramp's HiFi output still fails.
Probably cuz I have the Sauron mod on my phone, though I've seen that post you're talking abt on the Poweramp forum and it does seem to work for some devices/ROMs.
Oh well, I'll just wait for Poweramp to update. Whenever that will be. Lol.
dantedakilla said:
Doesn't work for me. Build.prop just resets after a reset. But even with a soft reset, Poweramp's HiFi output still fails.
Probably cuz I have the Sauron mod on my phone, though I've seen that post you're talking abt on the Poweramp forum and it does seem to work for some devices/ROMs.
Oh well, I'll just wait for Poweramp to update. Whenever that will be. Lol.
Click to expand...
Click to collapse
I think that's because you have write protection on. Connect your phone to a PC, enable USB debugging, open CMD and see if ADB recognizes the phone. then write 'adb reboot disemmcwp' and the write protection should disappear
Choose an username... said:
I think that's because you have write protection on. Connect your phone to a PC, enable USB debugging, open CMD and see if ADB recognizes the phone. then write 'adb reboot disemmcwp' and the write protection should disappear
Click to expand...
Click to collapse
Alright. I got it working but there's something I'm a little suspicious about.
It's outputting and being processed by "SAMSUNG UHQA PCM" which I don't think the Axon 7 has. Plus, I was switching between Hi-Res and AudioTrack and AudioTrack actually sounded better. Hi-Res made it feel like I was listening to music in a box.
My guess is Hi-res is outputting through the Qualcomm DAC and not the AKM 4490. So while hi res works, it's not proper hi-res, IMO.
I'm still deciding whether to regress mine to B11 MM, unlock bootloader, update to B08, flash twrp and root and get ViPER4Android in it in compatability mode for system wide effect and DAC use, and debloat it. Don't really care about custom ROMs for it.
dantedakilla said:
Alright. I got it working but there's something I'm a little suspicious about.
It's outputting and being processed by "SAMSUNG UHQA PCM" which I don't think the Axon 7 has. Plus, I was switching between Hi-Res and AudioTrack and AudioTrack actually sounded better. Hi-Res made it feel like I was listening to music in a box.
My guess is Hi-res is outputting through the Qualcomm DAC and not the AKM 4490. So while hi res works, it's not proper hi-res, IMO.
Click to expand...
Click to collapse
I think I should've added that somewhere.That is called a workaround... This works by telling Poweramp that your phone is a Samsung and has a UHQA DAC. This DAC somewhat works as the Qualcomm one, so it manages to drive it @ 192KHz. And the soundstage might be a little bit worse than the AKM DAC but it's in no way canned as you say. At least not with my headphones
Choose an username... said:
I think I should've added that somewhere.That is called a workaround... This works by telling Poweramp that your phone is a Samsung and has a UHQA DAC. This DAC somewhat works as the Qualcomm one, so it manages to drive it @ 192KHz. And the soundstage might be a little bit worse than the AKM DAC but it's in no way canned as you say. At least not with my headphones
Click to expand...
Click to collapse
Yeah, narrower soundstage was what I was trying to say but I couldn't find the words. Hahah. The difference is slight, but definitely noticable. Thing is, Sauron also forces the AKM DAC to be used system wide. So, despite Hi-Res failing, the sound is still being processed by the DAC.
I'll stick to defaults for now and wait for the PA update. I'm not saying no one should try this. If it works for you and everyone trying it, cool.
Did you do this with stock? It doesn't work with dark room (a LOS rom). What I normally use is "ro.lenovo.hifi_support=true", which does work. It does say 16 bit minimum, but I think as long as poweramp is using the hi-fi mode our phone will use the high quality audio.
Honestly, I wish there was a way to check the output to see what quality is being used. Anybody have an idea of what to use? It would be good to compare stock to all these other mods/apps.
pinkywinky said:
Did you do this with stock? It doesn't work with dark room (a LOS rom). What I normally use is "ro.lenovo.hifi_support=true", which does work. It does say 16 bit minimum, but I think as long as poweramp is using the hi-fi mode our phone will use the high quality audio.
Honestly, I wish there was a way to check the output to see what quality is being used. Anybody have an idea of what to use? It would be good to compare stock to all these other mods/apps.
Click to expand...
Click to collapse
It works on stock and LOS. If you did it right your phone should appear as 'Samsung UHQA' on the audio settings of poweramp
I think Dark Rom is based on LOS, so it should be the same?
You could compare but you need (very expensive) recording equipment then compare the two waveforms. But at the same time, if you can't notice the difference, then why would you use 192KHz anyways?
Choose an username... said:
It works on stock and LOS. If you did it right your phone should appear as 'Samsung UHQA' on the audio settings of poweramp
I think Dark Rom is based on LOS, so it should be the same?
You could compare but you need (very expensive) recording equipment then compare the two waveforms. But at the same time, if you can't notice the difference, then why would you use 192KHz anyways?
Click to expand...
Click to collapse
So I'm pretty sure our phone biases all that anyways.
pinkywinky said:
So I'm pretty sure our phone biases all that anyways.
Click to expand...
Click to collapse
what?
I have a G530FZ and this worked for me, now the HI-Res output works at 192 KHz (48KHz previously).
Thanks!!!
otamaglimmer said:
I have a G530FZ and this worked for me, now the HI-Res output works at 192 KHz (48KHz previously).
Thanks!!!
Click to expand...
Click to collapse
Hold on, we're not so sure that it works really. Can you check?
Download a terminal emulator and do this:
Type "su "
Hit enter
Then type "dumpsys media.audio_flinger"
Then just share that here
So this is great news unless you're an axon 7 user or any user of a non standard(non Samsung UHQA) dac.
Blah
Choose an username... said:
what?
Click to expand...
Click to collapse
Damn I had one too many beers. I just meant that I'm pretty sure our phone doesn't use the normal android way to do the audio
Choose an username... said:
Hold on, we're not so sure that it works really. Can you check?
Download a terminal emulator and do this:
Type "su "
Hit enter
Then type "dumpsys media.audio_flinger"
Then just share that here
Click to expand...
Click to collapse
Looks like its not working after all. I launched the terminal while playing some 192 KHz files and every sample rate mentioned is 48KHz.
Placebo effect!
otamaglimmer said:
Looks like its not working after all. I launched the terminal while playing some 192 KHz files and every sample rate mentioned is 48KHz.
Placebo effect!
Click to expand...
Click to collapse
Yeah, it seems so. The only thing I'm sure of is that doing this on the stock system of the Axon 7 actually improves the highs. I'll modify the thread to add this for now; I'll need someone to dump that file on stock with this mod later
Dodgexander said:
So this is great news unless you're an axon 7 user or any user of a non standard(non Samsung UHQA) dac.
Blah
Click to expand...
Click to collapse
Well I'm not sure if it actually works anywhere, but I still believe that highs improve substantially on stock with this mod (without using the AK4490).
The Samsung UHQA DAC is in no way standard. I believe it is the DAC on the Exynos chips maybe
Choose an username... said:
Well I'm not sure if it actually works anywhere, but I still believe that highs improve substantially on stock with this mod (without using the AK4490).
The Samsung UHQA DAC is in no way standard. I believe it is the DAC on the Exynos chips maybe
Click to expand...
Click to collapse
This is the problem. It's hard enough knowing if high frequency and bit depth audio works when sources are available. You can bet in a lot of cases where it seems audio is passed correctly it's either a display error or some kind of dithering or resampling is going on.
I would love to understand how to read the process our phones take when processing audio in different scenarios but it just seems impossible. As for the stock music player working with higher fidelity files we don't know this either. It doesn't make sense for it not to but then it also doesn't make sense that a lot of software/drivers can't handle the hardwares maximum specifications.
If there was some kind of framework and a front end that could read the process it would be awesome (like graphedit on Windows) it would be useful but even that didn't work if non-standard renders we're used.
I try my best to not get worked up about it, it's very annoying to know that probably something like this will never be known..or fixed or whatever. Here we have a nice DAC with specifications to suit our hi res music collection yet probably it's all being downsampled to 44.1 or 48khz 16bit.
Hopefully the rumours are true and zte focus more on using the dac with external applications in oreo.
Sent from my ZTE A2017 using Tapatalk
Dodgexander said:
This is the problem. It's hard enough knowing if high frequency and bit depth audio works when sources are available. You can bet in a lot of cases where it seems audio is passed correctly it's either a display error or some kind of dithering or resampling is going on.
I would love to understand how to read the process our phones take when processing audio in different scenarios but it just seems impossible. As for the stock music player working with higher fidelity files we don't know this either. It doesn't make sense for it not to but then it also doesn't make sense that a lot of software/drivers can't handle the hardwares maximum specifications.
If there was some kind of framework and a front end that could read the process it would be awesome (like graphedit on Windows) it would be useful but even that didn't work if non-standard renders we're used.
I try my best to not get worked up about it, it's very annoying to know that probably something like this will never be known..or fixed or whatever. Here we have a nice DAC with specifications to suit our hi res music collection yet probably it's all being downsampled to 44.1 or 48khz 16bit.
Hopefully the rumours are true and zte focus more on using the dac with external applications in oreo.
Click to expand...
Click to collapse
Well you could do what's plastered in the OP (dumpsys media.audio_flinger)

Bold beast call recorder

This app is no longer working now that call screening has arrived on my rooted pixel2 xl. Anyone recording calls after this update ?
billhilt said:
This app is no longer working now that call screening has arrived on my rooted pixel2 xl. Anyone recording calls after this update ?
Click to expand...
Click to collapse
Tried a couple. Didn't work until i disabled call screening.
Is there a setting to disable it ?
I haven't used Bold Beast for awhile because I always had issues with it after updates. I use Call Recorder by SKvalex. His call recorder works perfectly with call screening enabled and he provides constant updates. I'm rooted and I think that some people on his thread have had success with unrooted devices also but I'm not sure. You can download the main app on the playstore but you have to get the root companion from his thread on XDA.
murphyjasonc said:
I haven't used Bold Beast for awhile because I always had issues with it after updates. I use Call Recorder by SKvalex. His call recorder works perfectly with call screening enabled and he provides constant updates. I'm rooted and I think that some people on his thread have had success with unrooted devices also but I'm not sure. You can download the main app on the playstore but you have to get the root companion from his thread on XDA.
Click to expand...
Click to collapse
Didn't work for me. Had tried the same before. Nothing gets recorded for me. Call screening also breaks as transcription doesn't work when recording is on. Can you share your settings ?
coolsid8 said:
Didn't work for me. Had tried the same before. Nothing gets recorded for me. Call screening also breaks as transcription doesn't work when recording is on. Can you share your settings ?
Click to expand...
Click to collapse
Sure. I have Call recorder version 3.04 and Root addon companion version 2.03_1
I thought I had the Device setting as the Pixel XL 2 but it must have changed during an upgrade at some point. I just checked and the Device is set as
Qualcomm MSM89xx
Recording Method= Root
Root Settings
Audio source=CAF
Recording format=FLAC
Volume control= 200%
All other boxes are left unchecked.
For call screen make sure you have all these enabled unless you it has rolled out natively for you. The first one was added later and my call screen didn't work very well until I went back in and enabled it.
<boolean name="__data_rollout__SpeakEasy.CallScreenOnPixelOneAndTwoRollout__launched__" value="true" />
<boolean name="__data_rollout__SpeakEasy.OverrideUSLocaleCheckRollout__launched__" value="true" />
<boolean name="G__enable_speakeasy_details" value="true" />
<boolean name="G__speak_easy_bypass_locale_check" value="true" />
<boolean name="G__speak_easy_enabled" value="true" />
Nevermind
murphyjasonc said:
Sure. I have Call recorder version 3.04 and Root addon companion version 2.03_1
I thought I had the Device setting as the Pixel XL 2 but it must have changed during an upgrade at some point. I just checked and the Device is set as
Qualcomm MSM89xx
Recording Method= Root
Root Settings
Audio source=CAF
Recording format=FLAC
Volume control= 200%
All other boxes are left unchecked.
For call screen make sure you have all these enabled unless you it has rolled out natively for you. The first one was added later and my call screen didn't work very well until I went back in and enabled it.
<boolean name="__data_rollout__SpeakEasy.CallScreenOnPixelOneAndTwoRollout__launched__" value="true" />
<boolean name="__data_rollout__SpeakEasy.OverrideUSLocaleCheckRollout__launched__" value="true" />
<boolean name="G__enable_speakeasy_details" value="true" />
<boolean name="G__speak_easy_bypass_locale_check" value="true" />
<boolean name="G__speak_easy_enabled" value="true" />
Click to expand...
Click to collapse
I was using the same things. Not working for me. Outgoing works but during incoming call, the transcript breaks and it doesn't record anything the other person says. Is it working perfectly for you ?
Yeah, both sides of the conversation record perfectly for me. There was a couple of versions prior to this release of call recorder that didn't work though. I would try the update but always reinstall the older version that worked. This latest update works the best so far.
I have my call recording back thanks to the skvalex call recording app. Call screening isn't transcribing the person's responses.
In a few countries Google enabled the call recording feature in Pixel / Pixel 2 / Pixel 3 Android 9 Pie, no root needed, most recorders in the market work great. For example Pixel 3 in China mainland has the feature enabled, so no root needed.
However in most countries Google disabled the call recording feature in Pixel / Pixel 2 / Pixel 3 Android 9 Pie, as a result all recorders in the market can only record your own voice, the caller's voice is very weak in recordings. No matter what recorder you are using the result is the same. You should root the phone then Boldbeast Recorder can fix the problem, recorded calls are crystal clear in both sides. After root the phone please use the Alsa settings in this link to record calls: Google Pixel 3 Call Recording
Pixel phones have a new feature named ""Call Screening", some users said the feature doesn't work well when the recorder is working. Please change following settings in Boldbeast Recorder to perfectly fix the problem:
Call Settings - Incoming Calls - Auto Detect Answered State: No
Call Settings - Incoming Calls - Answered State Delay (Seconds): 3
Confirmed that v11.8 is working on my Pixel 2 XL which has been rooted and is running the Liquid Remix custom ROM
Only issue is that the dialer key press tones are not recorded, but am not sure that they should be

Static noise suppression for audio jack output

Hi,
I noticed a weird static noise in my headphones when listening to music or any app using the default Android output. This is strong enough to be annoying at the lowest volume steps, and I can also notice it at higher volume when the track is quiet.
I think this noise is here from the start : H930DS HK bought in November, ROMs open EU 21o to 22j and even stock HK ROM if I remember correctly (I followed the WTF thread as soon as I received it but I tried it on original HK ROM). It is completely independent from headphones, but I don't have high impedance ones to test if it would disappear in this situation.
However, I am a proud user of Poweramp... and the experimental high res output (set up on 24 bits / 48kHz) is able to completely annihilate the static noise for all my tracks (encoded 16 or 24 bits / 44100Hz to 96kHz, flac or 320 MP3). Quad DAC section effects are working but unfortunately DTS:X is bypassed. In fact, if I disable Direct Volume Control the noise is back : in this situation it seems I can't use any audio effect.
I am completely unable to recreate this effect with Ainur Narsil or any audio mod (like Ainur, then I stopped experimenting with it as I read somewhere it would disable the Quad DAC).
How is this possible ? I already spent hours studying system .xml files, XDA threads and tried installing/uninstalling audio mods, but I didn't find any solution. My android audio knowledge is limited, so I came here to figured this out : does anyone have a suggestion ?
Thanks for reading this looooooong post :victory: !
Jilano34 said:
Hi,
I noticed a weird static noise in my headphones when listening to music or any app using the default Android output. This is strong enough to be annoying at the lowest volume steps, and I can also notice it at higher volume when the track is quiet.
I think this noise is here from the start : H930DS HK bought in November, ROMs open EU 21o to 22j and even stock HK ROM if I remember correctly (I followed the WTF thread as soon as I received it but I tried it on original HK ROM). It is completely independent from headphones, but I don't have high impedance ones to test if it would disappear in this situation.
: !
Click to expand...
Click to collapse
If you have any audio mod, uninstall all of them.
use Hifi status app to check whther your headphone is recognized as high impendance due to bae connection.
Overall, the static noise only happens on HIM mode ( which turn avc to 0 hence generate the noise), so if you have any mod that force HIm mod, it will make that noise. if everything is still happens with my suggestion (no HIM mode mod, and headphone recognize as normal headphone) you can try changing the avc from 14 to higher (18 or 20)
Mrxyzl said:
If everything is still happens with my suggestion (no HIM mode mod, and headphone recognize as normal headphone) you can try changing the avc from 14 to higher (18 or 20)
Click to expand...
Click to collapse
So, I deleted all my audio related mods and even reinstalled my custom kernel with HIM disabled. HiFi app does not show high impedance whatsoever, but the noise is still here...
I'm trying to figure out by myself how to modify the AVC, but I have a few questions : can I achieve that through system file modification (I will make my personal Magisk mod then) ? If it's the case, will I need aml when using audio mod ?
Thank you a lot for your answer.
Jilano34 said:
So, I deleted all my audio related mods and even reinstalled my custom kernel with HIM disabled. HiFi app does not show high impedance whatsoever, but the noise is still here...
I'm trying to figure out by myself how to modify the AVC, but I have a few questions : can I achieve that through system file modification (I will make my personal Magisk mod then) ? If it's the case, will I need aml when using audio mod ?
Thank you a lot for your answer.
Click to expand...
Click to collapse
are you on stock? try modified the mixer_path_tavil.xml in vendor/etc. try searching for ess dac start then modified the next following avc value (one is 14 one is 0) to 16 or 18 to see how it goes
Mrxyzl said:
are you on stock? try modified the mixer_path_tavil.xml in vendor/etc. try searching for ess dac start then modified the next following avc value (one is 14 one is 0) to 16 or 18 to see how it goes
Click to expand...
Click to collapse
Well, I am on stock so I found the ESS DAC section in mixer_path_tavil and started to experiment with the values. I still don't understand which section serve which purpose, but with the avc value to 21 (3 times higher than the standard value from Anxious V30 mod) for the dac sections and 9 for the aux sections, the static noise is now gone.
I spend a long time trying to understand how mixer_path_tavil works... Is there a complete manual somewhere I can study ?
Jilano34 said:
Well, I am on stock so I found the ESS DAC section in mixer_path_tavil and started to experiment with the values. I still don't understand which section serve which purpose, but with the avc value to 21 (3 times higher than the standard value from Anxious V30 mod) for the dac sections and 9 for the aux sections, the static noise is now gone.
I spend a long time trying to understand how mixer_path_tavil works... Is there a complete manual somewhere I can study ?
Click to expand...
Click to collapse
For your information, hifi-dac = normal headphone, hifi-dac-advanced = high impedance headphone, hifi-dac-aux = aux (car or speaker)
The value is as following
ctl name="Es9018 AVC Volume" value="8" /> --> stock is 14, the higher, the smaller volume output, FYI, AVC stand for analogue volume control (basically should make less noise comparing to digital gain)
<ctl name="Es9018 Master Volume" value="0" /> --> no idea, should have no effect on audio quality, seem the lower the louder volume is
<ctl name="Es9018 HEADSET TYPE" value="1" /> --> type of headset, 1 = normal, 2 = high impedance, 3 = aux, this should determine the voltage output ( supposed so, but voltage output also hardcoded in kernel , so no idea how this turn out)
Edit: My headphone (64 Ohm custom headphone) was fine with HIM set at 8 (not 0), as i talked with John (developer of Ainur and narsil) , he said that he have no prob on his headphone, so it all fall down to headphone quality or so
Edit2: yes anxious mod modified to pseudo forced HIm mode and also mess up with DTS value (IMO, worse than stock)
Jilano34 said:
Well, I am on stock so I found the ESS DAC section in mixer_path_tavil and started to experiment with the values. I still don't understand which section serve which purpose, but with the avc value to 21 (3 times higher than the standard value from Anxious V30 mod) for the dac sections and 9 for the aux sections, the static noise is now gone.
I spend a long time trying to understand how mixer_path_tavil works... Is there a complete manual somewhere I can study ?
Click to expand...
Click to collapse
I just want to point out that modding the values DOES NOT force HIM or AUX mode. Anxious and another op pointed this out as well.
Sent from my LG-H932 using XDA Labs
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
Mrxyzl said:
are you on stock? try modified the mixer_path_tavil.xml in vendor/etc. try searching for ess dac start then modified the next following avc value (one is 14 one is 0) to 16 or 18 to see how it goes
Click to expand...
Click to collapse
That only changes volume lvl. It does not set DAC mode.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
I just want to point out that modding the values DOES NOT force HIM or AUX mode. Anxious and another op pointed this out as well.
Sent from my LG-H932 using XDA Labs
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
That only changes volume lvl. It does not set DAC mode.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
And yes, no one talking about changing the mode , he just had a problem with noise, i tell him to change the value and problem gone
I don't care about forced HIM (or falsified/pseudo/...), as I understand it's just a gain (you're not wasting your arguments on other threads @BROKEN1981 !). The modded DTS parameters I use are from JohnFawkes (he published them a while ago) and I like this side-by-side effect. In fact I state using Anxious mod but I edit it to match my needs... And now, I have installed narsil and jamesdsp : thanks to both of you my setup is perfect and noiseless.
I just don't understand how Poweramp with its HiFi Audio can clean all static noise without lowering my volume or anything... This is really weird.
Jilano34 said:
I don't care about forced HIM (or falsified/pseudo/...), as I understand it's just a gain (you're not wasting your arguments on other threads @BROKEN1981 !). The modded DTS parameters I use are from JohnFawkes (he published them a while ago) and I like this side-by-side effect. In fact I state using Anxious mod but I edit it to match my needs... And now, I have installed narsil and jamesdsp : thanks to both of you my setup is perfect and noiseless.
I just don't understand how Poweramp with its HiFi Audio can clean all static noise without lowering my volume or anything... This is really weird.
Click to expand...
Click to collapse
Glad you have it sorted out, sucks when you have static when you're trying to listen to music.
Sent from my LG-H932 using XDA Labs

Categories

Resources