So, I've found that the audio on Lineage OS and other Roms based on LOS wasn't as good as on the stock firmware. Both when it comes to mic and headphones audio.
I followed this up by comparing the "mixer_paths.xml" files from Lineage OS between the file from stock marshmallow as well as stock nougat (A2017G model) and there are quite a few missing lines in the AOSP version and some lines that just have different values. B.T.W Is the "mixer_paths.xml" the only file where you edit values which have to do with audio?
Anyway, I then used the standard mixer file from the stock Marshmallow firmware on the Lineage OS rom and although the sound is lower than with the standard mixer file from LOS the audio is noticeably better according to my ears. (This could be placebo but I doubt it. I also use the HD 598 headphones which are quite good compared to many other headphones on the market so the difference in audio quality is easier to discover).
Feel free to try this out if you are on a AOSP rom and want better audio. Steps below:
1: Make sure you're rooted and have disabled system write protection.
2: Navigate to System -> etc -> mixer_paths.xml.
3: Cut the "mixer_paths.xml" file to a backup location in case you want to go back.
4: Download either the marshmallow or the nougat file that I've provided below and rename it to "mixer_paths.xml" and paste it in the same location. System -> etc.
5: Reboot.
6: Profit? I don't know, it's up to you if you think it sounds better. Remember that with cheap earbuds you most likely won't hear a difference, at least I wouldn't.
You can try the process with either the Nougat or the Marshmallow file i uploaded. The Nougat is a little bit louder.
In case you want to go back then just copy the mixer_paths.xml file you backed up and replace the current mixer_paths.xml file in the same directory as above. Also reboot.
Edit: As @RUNNERX pointed out, make sure that the permissions are set to 644 and then reboot to make sure it's working correctly.
Download
I think we need a properly soundmod...
I tried with stock ROM (B19 A2017U) but it only affects the Normal Mode in headphones.
There's so much potential with this device... Ak4490 is a beast that needs to be released from its "cage".
As far as I can tell, the problem is that no custom rom is using the akm dac?
This is too bad, especially since regular dac sounds in my opinion much much better (and different) in aosp with the latest sound fix compared to stock normal (loudness being part of it). Still it is clearly not the akm dac.
On stock, both normal and superior mode have some kind of strange tuning, almost like there is some postprocessing even with dolby off. On aosp that seems to be gone at least.
It was mentioned previously that the mixer XML was ignored and all changes needed to be made the (ADC**?) files. This has since been patched resulting in proper use of akm DAC. The issues with the sound not being as good quality wise lies within these files, not the XML.
icenight89 said:
It was mentioned previously that the mixer XML was ignored and all changes needed to be made the (ADC**?) files. This has since been patched resulting in proper use of akm DAC. The issues with the sound not being as good quality wise lies within these files, not the XML.
Click to expand...
Click to collapse
Ok. Where would I find these files?
icenight89 said:
It was mentioned previously that the mixer XML was ignored and all changes needed to be made the (ADC**?) files. This has since been patched resulting in proper use of akm DAC. The issues with the sound not being as good quality wise lies within these files, not the XML.
Click to expand...
Click to collapse
So can anyone confirm that they got the akm dac working with headphones? (and comment on the results?)
I installed the AOSP extended 7.1.2 and then magisk zip, but it didn't seem to work, though it did play louder (and stereo on speakers).
Maybe I'll try a different rom...
cfbruck said:
So can anyone confirm that they got the akm dac working with headphones? (and comment on the results?)
I installed the AOSP extended 7.1.2 and then magisk zip, but it didn't seem to work, though it did play louder (and stereo on speakers).
Maybe I'll try a different rom...
Click to expand...
Click to collapse
I was under the impression that the headphone DAC has been working since early March. The stereo speaker fix has nothing to do with the headphone DAC.
https://forum.xda-developers.com/showpost.php?p=70971100&postcount=1041
Ok, it might just be that it sounds bad in the LOS-implementation then. Thanks to senny for exploring possibilities.
Just to give some feedback
This definitely changes the sound. Standard aosp sounded kind of raw to me, with tizzy trebles, though with a lot of detail. This makes it smoother, sounds more like it should in a way, easier to listen to.
There is some loss of information though, and soundstage a bit smaller.
(I found that if I tried to copy and replace the file it didn't work (sound not working). I had to first delete the mixer file present, then paste the other one.)
After replacing the file make sure permissions are 644 and reboot.
cfbruck said:
Just to give some feedback
This definitely changes the sound. Standard aosp sounded kind of raw to me, with tizzy trebles, though with a lot of detail. This makes it smoother, sounds more like it should in a way, easier to listen to.
There is some loss of information though, and soundstage a bit smaller.
(I found that if I tried to copy and replace the file it didn't work (sound not working). I had to first delete the mixer file present, then paste the other one.)
Click to expand...
Click to collapse
Well good to hear that more people find a difference.
when i'm looking at this: http://blog.son-video.com/en/2017/01/test-fiio-x5-iii/
I can't help but think that ZTE could have done so much more to make the experience more complete. The fiio got viper pre-installed, and digital low pass filter to play with that are actually coming straight from AKM :
"Five different 32-bit digital filter types are available: Short delay sharp roll-off and short delay slow roll-off filters have overall short delay characteristics. Sharp roll-off filter and slow roll-off filter preserve the phase difference and a new filter that has even slower roll-off character was added to these four filters. They are selectable according to the user audio and system preferences."
We've got a phone with one of the best DAC in the world, but can't do much because android by default is limited, and it seems obvious that zte don't have a lot of experience when it comes to makes audiophile device. a partenrship with fiio, cayin, or ibasso would have been terrific, especially considering that fioo and cayin have both already launch a product with an akm4490 running on android at full potential.
Maybe we can hope that some developer with at interest in audio can unlock some of the potential.
Listening some more with the mixer files I have to say it really is a big improvement, especially with the marshmallow to me.
Whatever it is that makes it better should be part of LOS. Using LOS 14.1 with the beastmode kernal and the changed mixer paths - it actually sounds pretty good.
However, for me changing the mixerpaths breaks audio functionality. I get no audio in calls, neither speaker nor headphones. I am using the sounds fix for stereo speakers 4.1, maybe that affects it.
Does it work without side effects for you senny? Whats your setup?
No mixer_paths.xml
Hi,i have marshall london phone and i'm sure i don't have mixer_paths.xml to edit,please help me to find the file responsible for editing volume output values.
FocaTm said:
Hi,i have marshall london phone and i'm sure i don't have mixer_paths.xml to edit,please help me to find the file responsible for editing volume output values.
Click to expand...
Click to collapse
same here I did not find the mixer_paths.xml file in my AOSP extended Android pie rom.
Related
Hey, all.
I installed Malaysk's latest ROM on my Eonon GA5151F. It's one of the HuiFei units for a Mazda. Instantly I noticed the sound quality is garbage and am determined to turn it around. On second thought, it might a KDL type unit ... it doesn't actually say under hardware info.
I followed aluver's awesome advice on getting USB audio working after finally getting a FiiO E18 in the mail.
I'm stuck: I can only play via UAPP (USB Audio Player Pro) and even when I do play in UAPP, the sound quickly becomes jumbled and distorted. If I set to 25ms for the buffer, I get about 20 seconds of play time before it crashes.
I've tried a regular 1m cable and even a tiny, short .25m cable but no change.
I do see that I have better luck using alluver's provided audio.primary.rk30board.so file but that only gives me the 20 seconds of play time. That file is 133K in size while the one installed on the unit (or maybe it's from the Malaysk ROM) is 213K. I did not see anywhere in my unit's file to edit and hard write the pcmC2D0c.
Any ideas?
Note: I see a similar thread of a similar issue but thought it would be rude to light back.
I tried to open up the unit but the CD drive is preventing me from getting a good look in. The USB cable that runs from inside to outside the unit is quite long. Seems like it might actually be 1.5 meters.
How can I get in there to pull this thing out and try a short cord? Or should I look in to a powered USB hub (such as the one sold by Carnetix)?
How interesting: I purchased a 7-port powered USB hub (these are quite hard to find in stores!) and now it works! I just plugged the thing in and connected a regular 1m cable to the hub and FiiO and UAPP plays without issue. I did have to enable the first two tweaks in the settings but it's a good start.
Issue continues though: only UAPP will play for me. I am guessing this is a driver issue but not sure where to begin on solving this.
Also, if I have the device turned on while the head unit boots, the head unit sits in safe mode.
@supaneko
Congradulations! Now you have enough power to supply your E18.
About how to make it possible all android sounds going to E18 without UAPP.
All ROMs higher than 4.2 android have audio.primary.rk30board.so file without that numbers to change - it's dynamic.
I have found the other way on 4.4 to make sound routing. It's more right way. Through ALSA.
But I'm not sure I can write a guide now, because I can't remember all I did in details.
And, secondly, I hope there is a more simple way, that was founded by kumarai, that I did not tested yet. His solution is to use system.img from KGL_rk3188_h(20151019) in his ROM. He says he just copied my drivers and wrote insmod strings to install-recovery.sh and all works flawlessly, with hot-plug, as I have working too.
Here is his post with that custom ROM on russian KGL HU forum http://4pda.ru/forum/index.php?showtopic=704299&view=findpost&p=45437941
You can try it (at your own risk, of course)
aluver, your kindness is contagious. Thank you for that.
I will try the link you provided and report back. I'm guessing flashing system.img shouldn't kill me because I can always reflash if needed.
At this point, I am still super determined to get this working. You've helped me in the right direction, aluver. Thanks again!
Well .... I thought that would be useful but I am on an RK3188 unit and then, it also dawned on me, I have the latest Malaysk ROM running. I was thinking I could just install this and extract the install-recovery.sh but it's not for the same unit.
I downloaded the update.rar listed and it only had an update.img in it. I tried to extract it using simg2img but it gives me an error.
I've PM'ed kumarai on here in hopes that he can help me out.
I'll give it another go tomorrow.
@supaneko
Oh, sorry, I thought you have RK3066. That image is not for RK3188 HU of course. But I think it makes things simpler. The trick of kumarai was exactly RK3188 system.img. It must work on RK3188 ROM "from the box" with your HU...
You just need to check what system.img version (date) Malaysk has used for the ROM you have. Or just give me a link to your ROM version. I'll check it by myself.
I use RK3xxx Firmware Tools for unpacking Rockchip update.img, system.img, boot.img & recovery.img
aluver said:
@supaneko
Oh, sorry, I thought you have RK3066. That image is not for RK3188 HU of course. But I think it makes things simpler. The trick of kumarai was exactly RK3188 system.img. It must work on RK3188 ROM "from the box" with your HU...
You just need to check what system.img version (date) Malaysk has used for the ROM you have. Or just give me a link to your ROM version. I'll check it by myself.
I use RK3xxx Firmware Tools for unpacking Rockchip update.img, system.img, boot.img & recovery.img
Click to expand...
Click to collapse
I am using the latest (posted here anyway) Malaysk ROM for 800x480 RK3188: https://yadi.sk/d/R0RY7sxbmmuwi
I located the RK3xxx Tools but .... they're for Windows and I'm on Linux. :\
I'd appreciate the help, aluver.
I have compared system folders of ROMs from kumarai and yours from the link you provided.
They are differ by files at /system/lib
but files at /system/lib/hw are the same
I think something in libaudioflinger.so or other library at /system/lib may do the trick with sound routing.
kumarai's system version 20151012.145613
yours - has a later date - 20151130.180905
Don't understand what's wrong with it...
Now I going to find Malaysk's ROM with same version of system.img as kumarai has.
Can't find needed version among Malaysk's ROMs. Looks like he didn't use that.
The previous to yours version has 20150824.182544 system.img only.
But I have another solution for routing for now.
You can replace audio.primary.rk30board.so by my patched version (already tested on RK3188). Do a backup of the original file, check it's permissions before.
Copy attached audio.primary.rk30board.so to /system/lib/hw folder and change permissions to original file had.
Power off HU and wait few minutes it complitely turned off.
After Power on check the sound is going to DAC (you may hear effect even without reboot - just after replacing the file).
If you will have a problem with sound stucks after some time, you'll need to edit /etc/audio_policy.conf (make backup first)
Delete whole this alsa_usb part of it:
Code:
alsa_usb {
outputs {
alsa_usb {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
}
}
inputs {
alsa_usb {
sampling_rates 8000|11025|16000|22050|32000|44100|48000
channel_masks AUDIO_CHANNEL_IN_MONO|AUDIO_CHANNEL_IN_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_IN_ANLG_DOCK_HEADSET
}
}
}
Because it can make a conflict. Reboot is needed to take effect.
By the way, did you have checked insmod's result? It must load all 4 modules *.ko without any errors.
Good luck and post any information about your progress.
SUCCESS!!
The insmod commands were already in there thanks to your original post, aluver. I replaced the .so file originally supplied in that post with what you attached here and ... it works! The ALSA lines were already in there so I didn't need to change that.
IT WORKS! I am terribly excited.
One final thing: if I have the FiiO device turned on when the Android boots, the unit boots into Safe Mode. I suspect there might not be much of a solution for this. Any ideas, aluver?
Alright. Made the drive home and ... it kept on working! I am so happy, aluver. Thank you.
I saw in another thread a mention about the volume control not working. This does indeed seem to be the case for me as well. I tried using the alsa_amixer command in Terminal but get a "Command not found" error when I do.
Out of curiosity, what DSP do you use, aluver?
supaneko said:
The ALSA lines were already in there so I didn't need to change that.
Click to expand...
Click to collapse
You didn't understand - You have to DELETE all that strings I wrote from audio_policy.conf and save it. They make a conflict I think.
supaneko said:
One final thing: if I have the FiiO device turned on when the Android boots, the unit boots into Safe Mode. I suspect there might not be much of a solution for this. Any ideas, aluver?
Click to expand...
Click to collapse
I think this problem should gone, if you delete strings from audio_policy.conf as I told you.
supaneko said:
Alright. Made the drive home and ... it kept on working!
Click to expand...
Click to collapse
Sorry, can't understand this... What drive?
supaneko said:
I saw in another thread a mention about the volume control not working. This does indeed seem to be the case for me as well. I tried using the alsa_amixer command in Terminal but get a "Command not found" error when I do.
Click to expand...
Click to collapse
Did you install Alsamixer from google play? It must be installed before use of mtc-service and\or alsa_amixer commands.
I think we need to make sound routing scheme better. As for me, I made it through alsa, not by replacing digits in audio.primary.rk30board.so.
With alsa configuring, we can make lossless 24bit volume control. Now we have a dynamic range losses because of 16bit volume control only.
Each -6dB from max digital volume are equal to 1-bit of bit depth loss.
I.e. if you listening music at volume position 10 of 30, it is about -40dB, you hear about (16bit - 40/6)~=10bit sound only!
But we know that a human's ear is logarithmic, so we can hear this losses.
To prevent that we can do the trick with adding amount of zero LSBs to make 24bit sound from 16bit source.
Then the digital volume will not become by fear for us.
Sorry for my English. I hope you understand.
supaneko said:
Out of curiosity, what DSP do you use, aluver?
Click to expand...
Click to collapse
I have russian amplifier with built-in modified by myself 8-channels DSP, based on 2 chips Analog Devices ADAU1701. But this DSP is not "for all". The sound processing algorithms for it I build in SigmaStudio. This is hard for usual people, but is very interesting for me .
The chain is: HU RK3066 Android 4.4.4 -> HiFiMeDIY Sabre U2 24/96 USB-DAC -> toslink -> Ryazanpribor X1 mkII (w/mod DSP X5 8channels)-> Focal Performance PS165FX, P25F+Pioneer GM-D8601
aluver said:
You didn't understand - You have to DELETE all that strings I wrote from audio_policy.conf and save it. They make a conflict I think.
I think this problem should gone, if you delete strings from audio_policy.conf as I told you.
Sorry, can't understand this... What drive?
Did you install Alsamixer from google play? It must be installed before use of mtc-service and\or alsa_amixer commands.
I think we need to make sound routing scheme better. As for me, I made it through alsa, not by replacing digits in audio.primary.rk30board.so.
With alsa configuring, we can make lossless 24bit volume control. Now we have a dynamic range losses because of 16bit volume control only.
Each -6dB from max digital volume are equal to 1-bit of bit depth loss.
I.e. if you listening music at volume position 10 of 30, it is about -40dB, you hear about (16bit - 40/6)~=10bit sound only!
But we know that a human's ear is logarithmic, so we can hear this losses.
To prevent that we can do the trick with adding amount of zero LSBs to make 24bit sound from 16bit source.
Then the digital volume will not become by fear for us.
Sorry for my English. I hope you understand.
I have russian amplifier with built-in modified by myself 8-channels DSP, based on 2 chips Analog Devices ADAU1701. But this DSP is not "for all". The sound processing algorithms for it I build in SigmaStudio. This is hard for usual people, but is very interesting for me .
The chain is: HU RK3066 Android 4.4.4 -> HiFiMeDIY Sabre U2 24/96 USB-DAC -> toslink -> Ryazanpribor X1 mkII (w/mod DSP X5 8channels)-> Focal Performance PS165FX, P25F+Pioneer GM-D8601
Click to expand...
Click to collapse
You amaze me, aluver. Again, thank you.
I installed Alsamixer AND the modified MCT service app. Volume control is working! There is one bug though: when I hit the volume up or down, a + and - toast pops up. The problem is that if I go from a volume of 30 down to 0, this +/i will pop up 30 times ... that's along with the volume bar at the bottom of the screen. I can turn it off by turning off the Media keys option in MCT but doing that kills, well, the media keys.
Also, I removed the lines specified from audio_policy.conf. If the FiiO is turned on while Android boots, it still goes in to Safe Mode. I did notice that after removing those lines, I started to get crackling, hissing, and just overall poor sound quality so I re-added the lines and the problems went away. It's still TOO QUIET though!
How can I make these changes you mention in ALSA? I have some sharp hearing myself and it's driving me nuts that things just don't sound as good as they should. I am curious to see your own ALSA parameters.
Quite the setup you have, aluver. I find it inspiring. One day, maybe I'll have the patience to program my own slopes and equalizations. We'll see.
supaneko said:
You amaze me, aluver. Again, thank you.
I installed Alsamixer AND the modified MCT service app. Volume control is working! There is one bug though: when I hit the volume up or down, a + and - toast pops up. The problem is that if I go from a volume of 30 down to 0, this +/i will pop up 30 times ... that's along with the volume bar at the bottom of the screen. I can turn it off by turning off the Media keys option in MCT but doing that kills, well, the media keys.
Click to expand...
Click to collapse
I am glad to help somebody, who has a good target About a + and - toast popups - it can be disabled in the code of mtc-service. I do not like that too, but have no time to make this job.
supaneko said:
Also, I removed the lines specified from audio_policy.conf. If the FiiO is turned on while Android boots, it still goes in to Safe Mode. I did notice that after removing those lines, I started to get crackling, hissing, and just overall poor sound quality so I re-added the lines and the problems went away. It's still TOO QUIET though!
Click to expand...
Click to collapse
It is very interesting effect.... I can't explain it yet. Let's try to determine the problem's cause by looking at logs. Just install CatLog from google play and try to show me what happens at start of HU with FiiO turned on.
supaneko said:
How can I make these changes you mention in ALSA? I have some sharp hearing myself and it's driving me nuts that things just don't sound as good as they should. I am curious to see your own ALSA parameters.
Click to expand...
Click to collapse
Sorry, but I cannot write it right now. I need to collect all information and copy changed drivers from my HU. Then I going to do a full guide. I made my installation at summer, and I am affraid to forget some details.
supaneko said:
Quite the setup you have, aluver. I find it inspiring. One day, maybe I'll have the patience to program my own slopes and equalizations. We'll see.
Click to expand...
Click to collapse
Thank you. All is in our hands. Keep moving
I forgot about "too quiet". Didn't you install any android mixers or volume regulators?
aluver, I haven't forgotten. Been a very busy week.
I got a new DSP and put that in (though not as fancy as your's ). Totally resolved my volume/gain issues but I'm wondering: what do you mean about the volume and the bits changing from 24?
I installed CatLog and when I did a reboot with the DAC powered on, the unit got stuck in a bootloop. It's never done that before. I'll have to give it a try again tomorrow or figure out what's changed to cause that. I'll report back again soon.
Thanks again, aluver!
@supaneko
What DSP did you get? Does it have a remote volume control unit? And what's the cause for volume/gain issues?
About bit depth and volume - read this http://www.head-fi.org/t/671220/eff...e-to-keep-software-at-full-volume-is-nonsense
That is why I say we need 24bit for the lossless volume regulating within HU.
If you have DSP with remote control unit now, you better use that, because it has 56 or 64 bit of internal processing deph (Volume at HU must be 100%).
About a bootloop. You can try to comment the 4 usb-audio driver insmod strings in install-recovery.sh (check the permissions after that! do not lose root!), then reboot without them, run catlog, and then type insmod commands at terminal emulator (don't forget "su" at first), and see what happens in catlog.
aluver said:
@supaneko
What DSP did you get? Does it have a remote volume control unit? And what's the cause for volume/gain issues?
About bit depth and volume - read this http://www.head-fi.org/t/671220/eff...e-to-keep-software-at-full-volume-is-nonsense
That is why I say we need 24bit for the lossless volume regulating within HU.
If you have DSP with remote control unit now, you better use that, because it has 56 or 64 bit of internal processing deph (Volume at HU must be 100%).
About a bootloop. You can try to comment the 4 usb-audio driver insmod strings in install-recovery.sh (check the permissions after that! do not lose root!), then reboot without them, run catlog, and then type insmod commands at terminal emulator (don't forget "su" at first), and see what happens in catlog.
Click to expand...
Click to collapse
@aluver, I picked up an AudioControl DQDX. It has a remote control but it only controls the bass or sets the various delays and other settings. I am thinking of swapping out the DAC I picked up with another single DIN head unit that supports DAC. That way, I can control the volume with an analog dial and still have steering wheel controls work. That's down the road though. I need to upgrade my amp and some other items first. Might just use the volume control on the DAC I picked up for now.
I'll post the CatLog logs in a bit. Thanks again, aluver.
Wow, your DSP is very rare in my world AudioControl's conceptuality is a vintage radicalism.
I don't understand why are you going to swap your DAC with a single DIN HU. In most cases analog volume control can't be used when you build a system with DSP. And analog volume control has it's own noise...
I think you better have to think about swapping of DSP. Something like Helix DSP Pro or anything else, more widely using our time.
About using the volume control on the DAC - You better have to connect your DSP and DAC by digital interface if you don't want to kill the sound by needless DA-AD conversions.
You make me laugh, aluver.
Yeah, one day I'll have the cash for a Helix DSP but ... for now ... I have to be budget conscious. Helix DSP is certainly in the plans though. Just gotta get the "eaiser" stuff like this Android head unit working first!
Again, I'll post the logs later!
aluver, I'm looking over the specs of the Helix DSP and ... wow. I'm impressed. I've added it to my bucket list. Will have to pick one up after I swap out my speakers for better ones.
Those Focal's you run, did you find them too bright at all? I've heard the Focals can be a little bright and I am sensitive to the higher freqs.
Hello,
This is my personal edit of the mixer_ paths.xml for the G4 [H815] to increase the headphone volume and decided to share it.
You might say, that there is already a thread for this, but unfortunately none of the files provided there did the trick and the volume remained the same as before - on Android 6.
As the FauxSound module was giving me issues (muffled sound each time I inserted the headphones), so I decided to dig deeper and modify the the file as it was working on my previous devices and finally managed to get it work.
The testing method was the following:
Used 4 tracks (HQ sync via Deezer App) and the same headphones (Ultimate Ears super.fi 3) and comparing them before and after
1. Armin Van Buuren - Waiting for the night
2. Sebastian Brandt - Mana
3. AC/DC - TNT
4. Eagles - Hotel California
With the default mixer_paths.xml tracks 1. and 2. were playing loud enough at MAX volume, but 3. and 4. were much quieter
After modifying the mixer_paths.xml tracks 1. and 2. were playing very loud with distortions appearing at MAX, but 3. and 4. were now loud enough.
After experimenting I decided to go with digital RX values "90" as with this setting I had all of my tracks playing loud enough for my needs and much louder than the default setup, but if it is too loud or not enough for you, feel free to modify it.
INSTALLATION:
1. download the attached .zip and extract it
2. navigate to system/etc and backup your original mixer_paths or rename it to mixer_paths.xml.bak (use e.g. Root explorer)
3. copy over attached file
4. set permissions 0644 (or rw-r--r--)
5. reboot
Make sure you have granted root access and mounted /system as RW.
Tested on the H815 INT variant only and Android 6.0 (V20c and V20d)
*it should work on V20e as well, as it is basically same as V20d
*it probably will not work on other variants if the file location/name or the contents are different
add speaker too if you can!!!
pikachukaki said:
add speaker too if you can!!!
Click to expand...
Click to collapse
Speaker is also set to 90 from 84.
Will give it a try and thanx for the mod..
It works in my G4 (20d). Thank you very much for your work
Can you make a flashable zip? I'm having a lot of problems, i've moved the file of the mixer to the etc folder but the volume is the same
I deliberately didn't provide any files, as between country/region/version differences I didn't want to have any problems caused in the off chance that something was different.
I provided a very clear step-by-step that took 5 minutes tops to do, yet people still complained about lack of zips or the whole file itself? I thought XDA was about learning how to modify your device, power users and all.
As for the files other people provided, I cannot speak for them working or not. Again, with the mod being ridiculously simple, I didn't test them myself.
If there's differences in the files between LP and MM, I'd would ask you to provided the details on which lines you changed in order to replicate your mod if someone doesn't want to use the provided file?
Anyhow, I'm glad to see other people experimenting on it in general. Maybe there's a magic value that makes it sound better, though I've not been able to find it!
Cheers
There's a Nougat Dolby port confirmed working on 8.1 ROMs. Thanks to @roisuke guide (and permission to repost for info) on the LOS15.1 thread summarising steps similar to the original Pixel 2XL guide, which uses the old ARISE N Dolby Atmos zip. In roisuke's post, his/her reason for trying this old Dolby is the newer Dolby boot loops on LOS15.1. In my case I was looking for a better compatible and audio quality Dolby when I found out about it. There's a few reasons i'll group into headings below. I know Dolby speakers that we paid for on stock for our device is a loved feature sought by more than just a few of us. I hope to help improve some people's speaker audio experience like I have, finally rivaling stock performance with V4A extra on top :laugh:
For installation instructions I'll just link roisuke's post, as mine has more to do with settings and usage explanation. I will just add that I had a different issue installing that Dolby zip on RR-O, the process would freeze without an error, requiring a force restart. The zip isn't detected by Magisk Manager and so can't be installed there. I couldn't install the zip when any Magisk version is installed. I ended up having to uninstall Magisk to allow the zip to install to system and then follow up with the other Magisk audio mods installed normally, Viper4Android (i'm on the old 2.3.4.0 for it's Super driver and better graphic equaliser), Ainur Sauron (optional maybe, it claims to improve audio in system and targets Axon 7 as well, I haven't tested this mod without it yet) and lastly Audio Media Library. Also thanks to @Oki for pointing out the hifi DAC patch is necessary with this particular Dolby mod.
Nougat Dolby sounds better
The reasoning is that I've recently been testing custom ROM N Dolby and it sounds just as good as stock N had. While I tested Oreo Dolby ports back when the B32+B10 bootstack was new also just recently too and found it didn't sound as good as N's. Therefore I understand it's not a custom port issue that the new O Dolby sounds worse than N but that it's the updated Dolby itself.
It can work together with V4A
A benefit of this old N Dolby is it is working with current V4A whereas I can't seem to get the new O Dolby to run with V4A, it did when I tested months ago but I can't recreate that either. A benefit to using V4A in combination is it's "Firequalizer" to preset "Small Speakers" accentuates bass and lessens the tinny treble, this is something I used to do back on stock N as well.
It can be configured to set and forget
A little talked about but great feature of stock Dolby is it remembered the settings separately for plugged/unplugged and for each individual app last playing audio too. That made it so good being only on for internal speakers as I preferred and would change settings mode automatically when you stopped audio and started in another app.
Custom ROMs with Dolby ports doesn't remember states, however with a bit of compromise it can be used as such on this N Dolby if you prefer Dolby to only affect internal speakers. The trick is to set no extra filters and EQ in Dolby but just have Dolby enabled. With all other settings off, it still positively affects speaker audio but has no affect on headphone jack audio, you can test this by listening either way while switching on and off. This works combined with the V4A equaliser settings as previously explained. Set rather simply as so, the speaker output has less harsh treble and increased bass to sound similar in presentation to listening on quality headphones.
Extra notes
A shortcoming bug with this N Dolby port however is the Surround Virtualisation feature doesn't work on speakers. It seems reversed and only works when plugged in, I find it best to leave it off as preferred and it will stay off. This bug is unfortunate as the surround was always nice in my opinion, but it's only one loss compared to all the other gains. For what it's worth I couldn't audibly hear a benefit of the surround feature on the O port in my limited testing. Also consider if using the O port where the effects are all somewhat changed for worse in my opinion, it also has to be manually switched off afterwards to not affect plugged audio unlike with the workaround available in the N port. In terms of comparing missing new features, the Oreo version has a bass boost toggle and a dynamic setting, overall though I couldn't settle on an audio setup I liked with any Oreo Dolby settings.
Conclusion
I hope my experience will help others to finally get the most out of their speakers with Dolby and V4A. Since moving from stock N to custom Oreo in early April left me disappointed in O Dolby quality usage issues, I'd stopped using it and relied only on V4A's Speaker Optimisation setting for improving the speakers as a compromise but it always left me wanting in comparison. However now recently finally figuring all this out, i'll be using this for the forseeable future. I really adore the loud unbeatable quality Dolby speaker output for general listening, I mean even a dozen meters away it sounds transformed like a good dedicated mini speaker is playing. This coming from someone who appreciates listening on premium headphones too.
Nice work ofcourse but i dont agree nougat dolby sounds better. In dolby oreo there is more to adjust also
Predatorhaze said:
Nice work ofcourse but i dont agree nougat dolby sounds better. In dolby oreo there is more to adjust also
Click to expand...
Click to collapse
It depends on your ears (or beliefs) I guess. Regardless if you've preference for O or N's Dolby, there's still good reason to use the N port. Mainly that it's able to be set and forget and also it's working with V4A aiding it too without issue.
So after reading your guide I liked the idea of a "set and forget" approach and chose certain presets for fireequalizer while in headset (bass booster) or speaker (small speakers) modes; also I changed v4a to the older version since I was unaware of its "super driver". However in the Dolby app I chose to leave on the "intelligent eq open" because to my ears the sound came across "fuller" if that makes sense.
roisuke said:
So after reading your guide I liked the idea of a "set and forget" approach and chose certain presets for fireequalizer while in headset (bass booster) or speaker (small speakers) modes; also I changed v4a to the older version since I was unaware of its "super driver". However in the Dolby app I chose to leave on the "intelligent eq open" because to my ears the sound came across "fuller" if that makes sense.
Click to expand...
Click to collapse
I'd recommend Dolby's extra customisations to be off because they remain active when plugged in. Unless of course you like any of its setting for both plugged and speaker. Relying on V4A for separated audio modifications fits well, you could try playing around trying to improve settings there if desired.
I used to prefer Rich in Dolby with Small Speakers in V4A together with Surround Virtualisation. Now with SV unavailable, I assume the EQ effects in Dolby are less pronounced because I can't notice much of positive difference with them on. When the issue being the setting will affect plugged too, it's a small worthwhile loss turning them off for the automated convenience.
Your headset preferences will totally depend on your headphone hardware and listening preferences. From my reading and understanding it's better to only use an EQ to reduce Frequency Response range positive peaks. Never to increase EQ as that introduces artificial noise. I'll attach two screenshots showing my hifi headphones FR graph and the V4A EQ I use to show what I mean (EQ graph doesn't match scale, zoom in to see the tiny DPI X Y values). The green line is the ideal neutral target FR with bass effect for headphones. Note when adjusting V4A's graphic equaliser the range of each frequency band is only shown on the old original 2.3.4.0 version.
Obviously mobile speakers are different in severely lacking bass, accuracy and need the bass EQ boost regardless of accuracy.
Sent from my ZTE Axon 7 using XDA Labs
@roisuke, It works as expected using Magisk 16.7. I did in another order and it also worked:
1. V2A FX 1.6.9 or later (I've tested old and current versions)
2. Sauron MK II.II 02.05.2018 or later (I've tested old and current versions)
3. BQ-E4 Dolby ATMOS (Dolby-Oreo.zip)
4. AML 1.7 or later (I've tested old and current versions).
I've noticed the flashing order is irrelevant as long as AML is the last one (It is intented to be always the last module to gather all the audio configs). It works with any install option of V2A (I prefer 2.5.0.5 traditional interface).
I believe the flashing of the ARISE module reroutes the audio paths and disables the hifi DAC when the BQ-E4 Dolby ATMOS is installed. I suspect it because the quality is vastly improved only if, at the end, I flash the Mixer_AK4490.zip to restore the HiFi DAC wiring paths.
These are great news since in Oreo I haven't found a way to have DA and V4A together.
Oki said:
It works with any install option of V2A (I prefer 2.5.0.5 traditional interface).
I believe the flashing of the ARISE module reroutes the audio paths and disables the hifi DAC when the BQ-E4 Dolby ATMOS is installed. I suspect it because the quality is vastly improved only if, at the end, I flash the Mixer_AK4490.zip to restore the HiFi DAC wiring paths.
These are great news since in Oreo I haven't found a way to have DA and V4A together.
Click to expand...
Click to collapse
I already listed why I prefer 2.3.4.0. I didn't mention in general UI the newer versions hide settings behind presses, makes it harder to use and see for example the selected EQ visual profile.
I was focused on speakers so actually hadn't tested jacked audio expecting it to just continue hifi as always on newer bootstacks. I thought Ainur Sauron is supposed to include the DAC patch as @Skrem339 added Axon 7 mods to it, he's also the author of the AK4490 DAC patch in question.
In any case I gave jacked audio some testing. I immediately found with the DAC patch there's static noise when booting jacked in and charging, but it phased out after replugging power, further testing for this may be necessary. After a few short install uninstall tests audio comparison, quality does sound improved. Thanks for mentioning that detail.
Here's the DAC patch thread with system and systemless. I updated the OP with this detail. Systemless only installs through TWRP still by the way. Small note worth mentioning though maybe unrelated is my fingerprint sensor stopped working after installing the Magisk patch, but worked again after uninstalling and reinstalling (a reset may have been enough).
Infy_AsiX said:
I already listed why I prefer 2.3.4.0. I didn't mention in general UI the newer versions hide settings behind presses, makes it harder to use and see for example the selected EQ visual profile.
I was focused on speakers so actually hadn't tested jacked audio expecting it to just continue hifi as always on newer bootstacks. I thought Ainur Sauron is supposed to include the DAC patch as @Skrem339 added Axon 7 mods to it, he's also the author of the AK4490 DAC patch in question.
In any case I gave jacked audio some testing. I immediately found with the DAC patch there's static noise when booting jacked in and charging, but it phased out after replugging power, further testing for this may be necessary. After a few short install uninstall tests audio comparison, quality does sound improved. Thanks for mentioning that detail.
Here's the DAC patch thread with system and systemless. I updated the OP with this detail. Systemless only installs through TWRP still by the way. Small note worth mentioning though maybe unrelated is my fingerprint sensor stopped working after installing the Magisk patch, but worked again after uninstalling and reinstalling (a reset may have been enough).
Click to expand...
Click to collapse
This patch is useless for Roms based on Android 8 because DAC works on them without patch. Also, this DAC patch was remove from Ainur by my request to Ultra8
Skrem339 said:
This patch is useless for Roms based on Android 8 because DAC works on them without patch. Also, this DAC patch was remove from Ainur by my request to Ultra8
Click to expand...
Click to collapse
For some reason the DAC patch is required after installing the Dolby Atmos patch mentioned in the OP, even in Oreo ROMs.
Hi @Infy_AsiX, can you give a link to the exact Nougat dolby port module which you are using on Oreo together with the 2.3.4.0 v4a? I tried all Oreo versions but they give me bootloop on S8 device, thanks
paradoxxman said:
Hi @Infy_AsiX, can you give a link to the exact Nougat dolby port module which you are using on Oreo together with the 2.3.4.0 v4a? I tried all Oreo versions but they give me bootloop on S8 device, thanks
Click to expand...
Click to collapse
Following the installation links brings you to Pixel 2 XL guide with the download. But here's a link to that Pixel2XL guide anyway https://forum.xda-developers.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
Sent from my ZTE Axon 7 using XDA Labs
Great [emoji3] works fine on Havoc Treble Oreo
Oki said:
For some reason the DAC patch is required after installing the Dolby Atmos patch mentioned in the OP, even in Oreo ROMs.
Click to expand...
Click to collapse
did you made Dolby working on treble ROM ? (I m on latest Havoc) because I've followed the OP (not the patch that did not install) but Dolby app quit, w/o message, after 1s. Just the nice logo
dwnoel said:
did you made Dolby working on treble ROM ? (I m on latest Havoc) because I've followed the OP (not the patch that did not install) but Dolby app quit, w/o message, after 1s. Just the nice logo
Click to expand...
Click to collapse
Well, I havent tried it in a Treble ROM. I don't play games or watch ATMOS movies. For Youtube, music and general audio, Viper4Android provides more features and richness to the sound so I don't use ATMOS at all. For external speakers I only notice more volume and some equalization, and I also have that configured in V4A in the speakers section. Treble roms are tricky. V4A is awesome when used properly.
Oki said:
Well, I havent tried it in a Treble ROM. I don't play games or watch ATMOS movies. For Youtube, music and general audio, Viper4Android provides more features and richness to the sound so I don't use ATMOS at all. For external speakers I only notice more volume and some equalization, and I also have that configured in V4A in the speakers section. Treble roms are tricky. V4A is awesome when used properly.
Click to expand...
Click to collapse
Do you mind sharing your settings? I used Atmos on dynamic setting in my car with Android Auto and Spotify. Car never sounded better. I'm now on treble with PixelExperience P and stuck with Viper. Sounds ok, but the dynamic system makes the sound go in and out.
kyuza said:
Do you mind sharing your settings? I used Atmos on dynamic setting in my car with Android Auto and Spotify. Car never sounded better. I'm now on treble with PixelExperience P and stuck with Viper. Sounds ok, but the dynamic system makes the sound go in and out.
Click to expand...
Click to collapse
I use V4A 2.5.0.5 with the classic interface with these settings:
Master Pwr ON
Playback Gain Control: ON
Extreme
4x
-1.9 dB
Spectrum Extension: ON
0.37
Dynamic System: ON
Common Earphone v2
25%
Viper Clarity: ON
Natural
6.0 dB
The rest is off, even the EQ
Been meaning to ask, @Oki. Your settings above are for headphones, right?
The Axon 7 isn't my daily driver so I don't use headphones with it much as I don't carry it around. Been trying to get some good speaker settings, mostly for locally stored music and occasional streaming video.
On this Nougat ROM Dolby Atmos and Viper 2.6.0.5 are working well together. In AEX 5.4 Oreo the two are also working but not necessarily together. A long time ago someone posted custom FireEQ settings which I still use but the other stuff not too sure about.
ZTE Axon 7 A2017U, Dark ROM, LlamaSweet 0.5 Kernel, Multiboot, XDA Legacy
Has anyone got Dolby to work on LOS 15.1?
EDIT: Never mind, got it working by going to the pixel 2xl forum for it
troy5890 said:
Has anyone got Dolby to work on LOS 15.1?
EDIT: Never mind, got it working by going to the pixel 2xl forum for it
Click to expand...
Click to collapse
Are you on the latest nightly los 15.1? Dolby just crashes for me now on latest
roisuke said:
Are you on the latest nightly los 15.1? Dolby just crashes for me now on latest
Click to expand...
Click to collapse
I'm on the latest LOS official 15.1 . I used the zip called "Dolby-Oreo.zip" the one for BQ.
Install "Ainur JamesDSP v1.7" Magisk module and choose the HQ 64bit driver
Install "Audio Modification Library v.1.8.1" Magisk module
Reboot
Configure JamesDSP app
Confirmed working (speakers & headphones (can't test bluetooth)) on my FIG-LX1 (L31) - EMUI 8.0.0.148(C432) - Magisk v17.1
Edit: If you don't want ringtones/notification-sounds to be processed, switch DSP registration from global to conventional. (3dot menu - top right, screenshot added)
Huge thanks to natanrosenfeld (he made a YT video, explaining a fix for previous version (now fixed with v1.7)) - and especially the JamesDSP dev team!
Great news I seen it on .android-hilfe.de myself
Messing around and cant seem to get it right, either too loud or doesnt work
Viper4android was much easier to setup, using Huawei DTS.irs or srs_2_1.irs then not much else and worked great
redultra82 said:
Great news I seen it on .android-hilfe.de myself
Messing around and cant seem to get it right, either too loud or doesnt work
Viper4android was much easier to setup, using Huawei DTS.irs or srs_2_1.irs then not much else and worked great
Click to expand...
Click to collapse
Have you tried using the same impulse response files with JamesDSP?
Copy the .irs (or .wav, .flac) to /storage/emulated/0/JamesDSP/Convolver and enable Convolver in JamesDSP.
Works great here.
Greetings from "androphil"
callmeWhiskers said:
Have you tried using the same impulse response files with JamesDSP?
Copy the .irs (or .wav, .flac) to /storage/emulated/0/JamesDSP/Convolver and enable Convolver in JamesDSP.
Works great here.
Greetings from "androphil"
Click to expand...
Click to collapse
I did thanks
Can you send screenshot of what you have, not sure on other settings
redultra82 said:
(...)Can you send screenshot of what you have, not sure on other settings
Click to expand...
Click to collapse
Even if we'd share the exact same setup (e.g. settings/IR xy sound great with my Shure SE425 in-ear headphones, but not so great with my AKG Q701) and preference of music, it would still be incredibly subjective and mainly based on taste. Certified sound-engineers would probably disagree, I guess
My suggestion is: leave every (other) option off, download a pack of different IRs (e.g. https://forum.xda-developers.com/zenfone2/general/collection-convolver-samples-389-t3140299) and try each one out. If you found one you like, (slightly) tune it with the EQ. At least that's my "non-pro" approach.
Mostly all I want is to make the phone louder, well the phone speaker, on Bluetooth speakers etc it's fairly OK
Next issue is echo sound on ringtone and notification
I'll try IRS out and maybe someday have Viper4android
It's a system-wide audio-mod, so yes, if you have e.g. Virtual Room Effect turned on or use a noticably "reverberating" impulse response file, you'll experience echo on ringtones/notification-sounds too.
I've managed to make the speakers slightly louder by choosing the highest IR Volume Level (30dB), but I think the device's speaker volume level/overall sound-quality is just physically limited. They are not the "best" speakers after all.
callmeWhiskers said:
It's a system-wide audio-mod, so yes, if you have e.g. Virtual Room Effect turned on or use a noticably "reverberating" impulse response file, you'll experience echo on ringtones/notification-sounds too.
I've managed to make the speakers slightly louder by choosing the highest IR Volume Level (30dB), but I think the device's speaker volume level/overall sound-quality is just physically limited. They are not the "best" speakers after all.
Click to expand...
Click to collapse
I noticed the room effect and turned it off, but just using Irs or some of them and seemed to be an echo,
Speaker is good enough, it is only a phone after all, there are small bluetooth speakers now that have great volume to help
A nice guy from the Telegram channel pointed out, that you can avoid processing system sounds (ringtones/notification) by switching DSP registration mode from global to conventional (screenshot added to OP).
YEEEES!!!! This mod is also working on Huawei P20Pro with EMUI8.1.. I just follow the same steps above. Thanks a lot man!
callmeWhiskers said:
Install "Ainur JamesDSP v1.7" Magisk module and choose the HQ 64bit driver
Install "Audio Modification Library v.1.8.1" Magisk module
Reboot
Configure JamesDSP app
Confirmed working (speakers & headphones (can't test bluetooth)) on my FIG-LX1 (L31) - EMUI 8.0.0.148(C432) - Magisk v17.1
Edit: If you don't want ringtones/notification-sounds to be processed, switch DSP registration from global to conventional. (3dot menu - top right, screenshot added)
Huge thanks to natanrosenfeld (he made a YT video, explaining a fix for previous version (now fixed with v1.7)) - and especially the JamesDSP dev team!
Click to expand...
Click to collapse
Hi do you know if I can change mixer path values without root and using adb on pc? , I'm trying to raise volume of WhatsApp calls, calls and maybe a bit of loud speaker volume but I'm trying to avoid root etc. Thanks any advice would be appreciated or a link to tutorials. I'm on psmart. Thanks again
jason13v8 said:
Hi do you know if I can change mixer path values without root and using adb on pc? , I'm trying to raise volume of WhatsApp calls, calls and maybe a bit of loud speaker volume but I'm trying to avoid root etc. Thanks any advice would be appreciated or a link to tutorials. I'm on psmart. Thanks again
Click to expand...
Click to collapse
Sorry - I'm not an expert, so don't take my word for it - but I don't think that's possible, since all these files are stored in locations, where (non root) users don't have write permissions. Even with a rooted and/or custom recovery device, I don't think it's possible to alter app-specific volumes by just changing mixer_paths.xml values.
callmeWhiskers said:
Sorry - I'm not an expert, so don't take my word for it - but I don't think that's possible, since all these files are stored in locations, where (non root) users don't have write permissions. Even with a rooted and/or custom recovery device, I don't think it's possible to alter app-specific volumes by just changing mixer_paths.xml values.
Click to expand...
Click to collapse
Sorry I know I mentioned whats app but really I just mean overall volume. With my moto g5 I was able to edit mixer path values which led to louder everything. But that was only with root as I'm new to adb. Thanks for your response
jason13v8 said:
Sorry I know I mentioned whats app but really I just mean overall volume. With my moto g5 I was able to edit mixer path values which led to louder everything. But that was only with root as I'm new to adb. Thanks for your response
Click to expand...
Click to collapse
In case your bootloader is unlocked, iirc you could theoretically fastboot flash TWRP - and use TWRP's "privileged" terminal (e.g. (mount /system), adb pull/push and edit the file(s)), and then (re)flash stock recovery again - without actually rooting the device.
Again, I'm not an expert (also didn't try it myself) and can't guarantee above mentioned procedure works, despite my inner-Sherlock-Holmes tells me, your bootloader is actually not unlocked.
callmeWhiskers said:
In case your bootloader is unlocked, iirc you could theoretically fastboot flash TWRP - and use TWRP's "privileged" terminal (e.g. (mount /system), adb pull/push and edit the file(s)), and then (re)flash stock recovery again - without actually rooting the device.
Again, I'm not an expert (also didn't try it myself) and can't guarantee above mentioned procedure works, despite my inner-Sherlock-Holmes tells me, your bootloader is actually not unlocked.
Click to expand...
Click to collapse
Yeah still locked dude, tried DC unlocker but they refunded as I'm on latest security patch and admitted there is nothing they can do right now.
Themes
So, i've edited tinyalsa-audio.xml file to make sound louder. It worked. But, after some time, usually after phone calls, audio settings roll back to default values, while the tinyalsa-audio.xml file remains unchanged. To get louder sound back I just need to reboot android. Untill it happens again...
This is really annoying. Is there a way to fix this?
OS: Android 7.1.2
Somepony said:
So, i've edited tinyalsa-audio.xml file to make sound louder. It worked. But, after some time, usually after phone calls, audio settings roll back to default values, while the tinyalsa-audio.xml file remains unchanged. To get louder sound back I just need to reboot android. Untill it happens again...
This is really annoying. Is there a way to fix this?
OS: Android 7.1.2
Click to expand...
Click to collapse
Instead of editing .xml files, try editing the default_gain.conf file, something like this:
https://forum.xda-developers.com/showthread.php?t=2777535
There are also similar and possibly better guides and mods for audio on the S2/S3/S4 devices here at XDA but I did not find them with a general search, you can find them using the XDA search box, audio is similar in all of them. Look around here on XDA about editing sound files to improve audio. Editing audio.xml is, by no means, the only way, nor is it even the best way to modify audio, I've seen mods for .soc files, .xml files, .db files and .conf files. It just depends on the device and exactly what aspects of audio you want to change.
There are also things like Viper4Android or Dolby Atmos and other similar sound mods, some of them are combinations of the various sound mods to give more variety of features and options to improve audio on various platforms. For example, the mod will be named something like Dolby Atmos+something or V4A+something or Dolby Atmos+something+something. The mods that are combinations of the others can, in some cases, on some devices, give more improvement than using only one of the mods by itself.
Sent from my LGL84VL using Tapatalk