Guide to get rid of audio distortion on CM13 and Lineage OS 14.1
I have told quite a few people in the cm13 thread how to get rid of the audio distortion, I figured it was relevant to enough people that I should make a little guide on how to set it up although it is pretty straightforward.
[Disclaimer] I am not responsible if you manage to break your phone using this guide
What does this guide accomplish? This guide will help you install Viper4Arise which is a wonderful sound mod that I use on any phone or rom. Viper4Arise will allow you to eliminate audio distortion in media playback on your Axon 7 running CM13 or LOS14.1, by lowering the output gain which is not capped properly in these Roms
What does this guide fail to accomplish? This guide will not fix mic issues, in call volume, the left channel being missing on speakers, or any other sound related problem present in CM13 or LOS14.1, however most bugs are gone now in LOS14.1
Now that that's out of the way, lets get to the fun stuff!
Step 1
First thing you want to do is grab the Viper4Arise flashable zip
Download Viper4Arise 2.3.3
however if you want the newest version
Download Viper4Arise 2.4
once you have this you can boot into TWRP and flash it, then reboot into system
Step 1.5
This step is only necessary on the newest builds of lineage OS 14.1
lineage OS does not have root built in. we will download the root addon package from lineageOS
Download root addon
flash this in twrp, it doesnt matter if it is done before or after installing the Viper4Arise package
Step 2
SeLinux must be permissive and by default it is enforcing so we are going to grab this apk and install it
Download SeLinux Switcher
once installed, open the app, allow root access (you may need to enable root in developer options) and set SeLinux to Permissive. if Viper4Arise stops working always check to make sure Selinux is still in permissive as changing it back to enforcing will stop Viper4Arise from working.
Step 3
Next we will configure Viper4Arise to eliminate Audio distortion.
Start by going to the phone speaker and Headset tabs and Switching master power to on
Now press the menu button on the top left and press Driver status. as long as SeLinux is permissive it should say
NEON Enabled: Yes
Enabled: Yes
Status: Normal
the other things are not relevant. if the above message read "No" or "Abnormal" you may not have set SeLinux to permissive, please go back to step 2!
do this twice, once with the Headset tab Selected and once with the Phone Speaker tab selected
There are allot of awesome setting to mess with they can make you audio amazing, I encourage you to try them out. to make the audio distortion go away simply scroll to the bottom and find the "Master Gate (Limiter)" tab. Set the output gain to -10.5 dB on both the Headset and Phone Speaker. this level seems pretty good in my opinion however you may find you prefer a slightly lower or higher level.
That's it! I hope I have helped you guys out, feel free to ask questions or make suggestions on how to improve this guide and be sure to leave Thanks!
Thread created: 1/31/17
Last updated: 2/2/17
This won't make audio playback through the phone speakers stereo again, would it?
Does this work for LineageOS 14.1?
Abiram26 said:
This won't make audio playback through the phone speakers stereo again, would it?
Click to expand...
Click to collapse
Nope... Sorry. I will add that to the list of things it doesn't do.
borijess said:
Does this work for LineageOS 14.1?
Click to expand...
Click to collapse
I have only tested it in CM13 as I haven't made the jump. But the audio distortion problem is the same in Lineage OS as CM13.
It will work in Lineage OS.
masong397 said:
I have only tested it in CM13 as I haven't made the jump. But the audio distortion problem is the same in Lineage OS as CM13.
It will work in Lineage OS.
Click to expand...
Click to collapse
Nice job worked on LineageOS 14.1.
Thanks for the guide. My YouTube videos are no longer distorted and sound good enough, for not having stereo capability on LOS. However, all of my notifications that come in are still very distorted, is there a fix for this?
cms062407 said:
Thanks for the guide. My YouTube videos are no longer distorted and sound good enough, for not having stereo capability on LOS. However, all of my notifications that come in are still very distorted, is there a fix for this?
Click to expand...
Click to collapse
Glad the guide helped you! Unfortunately I don't know how to get rid of distortion when notifications come in. I do believe Unjustified Dev said that all audio distortion will be gone in the near future, of course this guide won't be important at that point. At least audio quality isn't really important for notifications...
Alrighty, no big deal. You're right, it isn't a huge problem...Just a little annoying. I may have to flash back to stock, the main reason most people bought this phone was for the speakers....And I'm starting to miss the immersive sound that I had from stock
cms062407 said:
Alrighty, no big deal. You're right, it isn't a huge problem...Just a little annoying. I may have to flash back to stock, the main reason most people bought this phone was for the speakers....And I'm starting to miss the immersive sound that I had from stock
Click to expand...
Click to collapse
Yeah the left and right channel bug really degrades the speaker experience... And weird sounding notifications is annoying. I listen to lots of music but always with headphones or with an aux in the car so I don't really care too much...
Hijacking this thread to ask specifically. I do not care about my speakers I literally only use Headphones.
Is media with headphones played via the AK DAC? Is the quality as good as "super" mode on the stock ROM ? (Again, asking for Media Playback with headphones!)
Question, is the audio on LOS 14.1 with speakers good enough to listen to podcasts and some music with this mod?
Doesnt work anymore on LineageOS 14.1 latest version. I cant change back to permissive.
borijess said:
Doesnt work anymore on LineageOS 14.1 latest version. I cant change back to permissive.
Click to expand...
Click to collapse
Flashing the latest build right now. I will let you know how it goes
borijess said:
Doesnt work anymore on LineageOS 14.1 latest version. I cant change back to permissive.
Click to expand...
Click to collapse
You need root to use SeLinux mode changer. check the OP I updated how to get root.
masong397 said:
You need root to use SeLinux mode changer. check the OP I updated how to get root.
Click to expand...
Click to collapse
My fault.
I didn't realize I lost root after I dirty flashed.
iNaruX said:
Hijacking this thread to ask specifically. I do not care about my speakers I literally only use Headphones.
Is media with headphones played via the AK DAC? Is the quality as good as "super" mode on the stock ROM ? (Again, asking for Media Playback with headphones!)
Click to expand...
Click to collapse
I use headphones all the time. I love it. If you are worried about the quality compared to stock I believe you will not be disappointed. Of course I am not an audio expert and do not have the means to compare the quality side by side. I am not sure if the HiFi DAC is used, that is more of a general lineage os question.
borijess said:
My fault.
I didn't realize I lost root after I dirty flashed.
Click to expand...
Click to collapse
I just flashed SuperSU again now I have root again.
spacemanvt said:
Question, is the audio on LOS 14.1 with speakers good enough to listen to podcasts and some music with this mod?
Click to expand...
Click to collapse
The speakers are not as good as stock, the mod works perfectly but I believe only right channel is played. Its a problem that the lineage os devs have to fix. It is good for listening to pretty Mich anything, oy won't have distortion or anything
spacemanvt said:
Question, is the audio on LOS 14.1 with speakers good enough to listen to podcasts and some music with this mod?
Click to expand...
Click to collapse
Yes works great for podcasts.
Related
I heard that there is a lot of confusion about installing ViPER4Android on Nougat. After searching around the web i found a way to do it ^_^ It should work on all Nougat build released until now. Last test on N4F26J
First of all unistall any previous ViPER4Android app.
Requirements:
Root
TWRP
SuperSU 2.78 or higher
BusyBox 1.24.2 or higher installed in \su\xbin
Installation:
Flash ViPER4Android_2.5.0.5_guitardedhero.zip in TWRP
Go to vendor\etc and remove/rename audio_effects.conf using any file manager with root access (ex. Root Browser)
Open ViPER4Android app and install driver (Grant root permission). (It could freeze for a few seconds, just be patient!)
Reboot
Disable MusicFX app
Reboot
Done :3
I hope this will help you
Thanks to guitardedhero for the modified zip file
EDIT: fixed google drive link
ElementalX kernel not required. Thanks for the guide.... Enjoy
Works on stock?
Sent from my Nexus 5X using Tapatalk
Magisk + V4A Add-on is how I use it flash those in twrp and then install v4a apk no editing system partition and you can install ota updates then just boot twrp and flash magisk again
I want to know if its working system wide.
viper4android saying not enable and not processing....anyone with the same issue?
for me its only working in compatible mode.. anyone else?
Did not completely work for me. At first when i did the procedure everything was ok,driver installed neon,ok. But when i played native audio or pandora no difference. Also when i plugged in my Fiio K1 DAC it change to not supported abnormal. Tried clean installing into system 3x, edidtin,deleting, the file in vendor. No luck, maybe we just have to wait a bit longer, rom used is Purenexus. Also when i did it,i already had the drive installed.....
---------- Post added at 07:23 PM ---------- Previous post was at 06:51 PM ----------
UPDATE:
So i did get it working, but i used the Viper 6.01 that guitar user posted in the nexus 5x forum.
Works with only Headphone jack,
NOT with usb out. When using USB out it just dosent work.
Also for some reason my pandora now keeps crashing
BUT IT WORKS, so i think ill keep it. Ill leave the DAC/AMP at home for my laptop, and use the viper limiter at maximum and just up the bass a bit.
All i wanted was to get the bass higher with out maximizing the volume.
Id suggest using arise, it's way better than stock Viper
If I may make a suggestion that will ultimately save you a lot of grief, move to the updated ARISE sound mod by guitardedhero and others. The latest is deuteronomy 2.x and, as opposed to the tweaks, futzing and issues of sound being processed/sticking or not, this is a much simpler install and just works.
Head over to http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 and just install the base version. You'll get Viper4ARISE. I still flash a permissive kernel zip with my Nougat ROMs, but since I switched to ARISE, V4A has worked flawlessly, and it sounds even better than the old V4A from this thread.
It also removes MusicFX with the install process and I haven't had to disable/remove the audio_effects.conf file either.
Lastly, I'm not sure development is continuing on the base V4A anyway. ARISE is the way to modify your Android sound processing now.
---------- Post added at 09:12 AM ---------- Previous post was at 09:12 AM ----------
banccalif said:
Id suggest using arise, it's way better than stock Viper
Click to expand...
Click to collapse
Sorry, only noticed your post after I posted my longer response saying the same thing
ultyrunner said:
If I may make a suggestion that will ultimately save you a lot of grief, move to the updated ARISE sound mod by guitardedhero and others. The latest is deuteronomy 2.x and, as opposed to the tweaks, futzing and issues of sound being processed/sticking or not, this is a much simpler install and just works.
Head over to http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 and just install the base version. You'll get Viper4ARISE. I still flash a permissive kernel zip with my Nougat ROMs, but since I switched to ARISE, V4A has worked flawlessly, and it sounds even better than the old V4A from this thread.
It also removes MusicFX with the install process and I haven't had to disable/remove the audio_effects.conf file either.
Lastly, I'm not sure development is continuing on the base V4A anyway. ARISE is the way to modify your Android sound processing now.
---------- Post added at 09:12 AM ---------- Previous post was at 09:12 AM ----------
I amd a bit confused. So i still need to flash a kernel zip besides the ARISE file? I am on 7.1.1 preview with stock kernel
Click to expand...
Click to collapse
angle409 said:
ultyrunner said:
If I may make a suggestion that will ultimately save you a lot of grief, move to the updated ARISE sound mod by guitardedhero and others. The latest is deuteronomy 2.x and, as opposed to the tweaks, futzing and issues of sound being processed/sticking or not, this is a much simpler install and just works.
Head over to http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 and just install the base version. You'll get Viper4ARISE. I still flash a permissive kernel zip with my Nougat ROMs, but since I switched to ARISE, V4A has worked flawlessly, and it sounds even better than the old V4A from this thread.
It also removes MusicFX with the install process and I haven't had to disable/remove the audio_effects.conf file either.
Lastly, I'm not sure development is continuing on the base V4A anyway. ARISE is the way to modify your Android sound processing now.
---------- Post added at 09:12 AM ---------- Previous post was at 09:12 AM ----------
I amd a bit confused. So i still need to flash a kernel zip besides the ARISE file? I am on 7.1.1 preview with stock kernel
Click to expand...
Click to collapse
You don't need to AFAIK and it isn't a kernel. V4A used to need SELinux permissive to run, but stock and most custom kernels run enforcing. I just mentioned that I flash a permissive mod out of habit FYI. You are likely better off going to the A.R.I.S.E. threads to discuss issues.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just flashed Deuteronomy 2.1 (non classic) on my nexus 6P. After enabling V4Arise and enabling speaker optimization, the phone speaker sound is actually worse than stock, more muted across range. I haven't tried headphones yet. kinda disappointed. My advice: V4A is overhyped. just keep stock sound.
angle409 said:
Just flashed Deuteronomy 2.1 (non classic) on my nexus 6P. After enabling V4Arise and enabling speaker optimization, the phone speaker sound is actually worse than stock, more muted across range. I haven't tried headphones yet. kinda disappointed. My advice: V4A is overhyped. just keep stock sound.
Click to expand...
Click to collapse
Sorry, but you clearly haven't tested anything at all yet. Speaker optimization isn't that great and yes it mutes it, but that's to avoid the pop and tinny issues with many phone speakers. However, if you use that, then play with the EQ and other settings, you may surprise yourself. That would require more than a 5 second evaluation though.
Have you tried the EQ presets or customized them? What about dynamic sound or the various compressions? How about any number of things most people would play around with before writing something off? These types of tweaks are, after all, the point of a sound mod with a detailed EQ.
Since you admit you haven't even tried headphones, let alone bluetooth and haven't played with the EQ at all, it may just be a wee bit early to pronounce it a failure. And ... the VAST majority of people who use it would disagree.
ultyrunner said:
Sorry, but you clearly haven't tested anything at all yet. Speaker optimization isn't that great and yes it mutes it, but that's to avoid the pop and tinny issues with many phone speakers. However, if you use that, then play with the EQ and other settings, you may surprise yourself. That would require more than a 5 second evaluation though.
Have you tried the EQ presets or customized them? What about dynamic sound or the various compressions? How about any number of things most people would play around with before writing something off? These types of tweaks are, after all, the point of a sound mod with a detailed EQ.
Since you admit you haven't even tried headphones, let alone bluetooth and haven't played with the EQ at all, it may just be a wee bit early to pronounce it a failure. And ... the VAST majority of people who use it would disagree.
Click to expand...
Click to collapse
What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer, I don't know what is best for my phone.
siren_shadows said:
What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer, I don't know what is best for my phone.
Click to expand...
Click to collapse
Exactly. If regular people have to spend hours or days to tweak the settings what's the good? I wish it's the install and forget type of app.
angle409 said:
Exactly. If regular people have to spend hours or days to tweak the settings what's the good? I wish it's the install and forget type of app.
Click to expand...
Click to collapse
Worst part is I've had hearing problems since I was an infant, so like, i can't really test settings and **** since I can't really tell the difference incrementally.
angle409 said:
Exactly. If regular people have to spend hours or days to tweak the settings what's the good? I wish it's the install and forget type of app.
Click to expand...
Click to collapse
Hours or days? It takes me a few minutes of playing on a fresh install until I hit what I like. Plus, you can save your settings as a profile. However, it's clear from your responses that you can't be bothered to actually test it. If you have a home stereo, you play around with EQ until you like it. If you listen to music in your car, you set treble and bass, balance and other things. This is no different. How on earth a sound app that, at its heart is an EQ, could be set and forget BEFORE YOU INSTALL IT is beyond me. That's not even the purpose of it. If that's what you want, then you're not looking for a sound mod. The entire point of a sound mod / EQ is to allow people to adjust the sound to their preference for their hardware and listening preferences/context.
angle409 said:
Just flashed Deuteronomy 2.1 (non classic) on my nexus 6P. After enabling V4Arise and enabling speaker optimization, the phone speaker sound is actually worse than stock, more muted across range. I haven't tried headphones yet. kinda disappointed. My advice: V4A is overhyped. just keep stock sound.
Click to expand...
Click to collapse
ultyrunner said:
Sorry, but you clearly haven't tested anything at all yet. Speaker optimization isn't that great and yes it mutes it, but that's to avoid the pop and tinny issues with many phone speakers. However, if you use that, then play with the EQ and other settings, you may surprise yourself. That would require more than a 5 second evaluation though.
Have you tried the EQ presets or customized them? What about dynamic sound or the various compressions? How about any number of things most people would play around with before writing something off? These types of tweaks are, after all, the point of a sound mod with a detailed EQ.
Since you admit you haven't even tried headphones, let alone bluetooth and haven't played with the EQ at all, it may just be a wee bit early to pronounce it a failure. And ... the VAST majority of people who use it would disagree.
Click to expand...
Click to collapse
siren_shadows said:
What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer, I don't know what is best for my phone.
Click to expand...
Click to collapse
ultyrunner said:
Hours or days? It takes me a few minutes of playing on a fresh install until I hit what I like. Plus, you can save your settings as a profile. However, it's clear from your responses that you can't be bothered to actually test it. If you have a home stereo, you play around with EQ until you like it. If you listen to music in your car, you set treble and bass, balance and other things. This is no different. How on earth a sound app that, at its heart is an EQ, could be set and forget BEFORE YOU INSTALL IT is beyond me. That's not even the purpose of it. If that's what you want, then you're not looking for a sound mod. The entire point of a sound mod / EQ is to allow people to adjust the sound to their preference for their hardware and listening preferences/context.
Click to expand...
Click to collapse
ultyrunner is absolutely correct here. The criticisms you have leveled against this project would be considered rude (and a bit ignorant) even if you actually had a solid point to make, or some evidence to back it up. As it stands, you don't have either, and asking a question like "What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer..." is just unthinkable. People specifically poured blood, sweat, and tears into this thing for that exact reason... so that people who aren't engineers can improve their experience via the developer's knowledge. Either you were just being flippant about "having to do all the work yourself" and you don't actually mean that - in which case it would have been preferable for you to just say "thank you but I am having a few problems," et cetera, and be on your way...OR you do actually think you're doing all the work, which is a smack in the face to a developer... a developer whose work you very obviously do not grasp the complexity of, nor the amount of time and effort required to produce said work. Don't bash people's work if you haven't yet evaluated it properly, and most especially make an effort to understand it at a high level before you complain (if you really need to complain at all, which you don't).
I'm sorry, but if I was the developer, seeing a comment/comments like these would be enough for me to close down the project ASAP. And I'm not just pulling that out of my ass, I've been through five or six phones and development communities here on XDA, and I have seen exactly that happen on more than one occasion.
And that's the problem with XDA. People take things to personally. This isn't a forum for babies. We're allowed to express our opinions and concerns here, believe he or not.
Hi All. The sound is fixed as you know but not on all ROM. So i've made a Fix zip. Tried on US and G version.
Edit: working on A2017 (Chinese version)
IMPORTANT: I'm not responsible for anything which could be happen. I suggest to make a backup from TWRP.
First of all i didn't fix it. Thanks @Unjustified Dev , @DrakenFX and Anynomous Dev
Instruction:
Flash zip via TWRP.
Download:
v4.1
https://www.androidfilehost.com/?fid=457095661767153882
v4
https://www.androidfilehost.com/?fid=457095661767152958
v2
https://www.androidfilehost.com/?fid=529152257862718359
WesTD said:
Hi All. The sound is fixed as you know but not on all ROM. So i've made a Fix zip. Tried on US and G versions.
IMPORTANT: I'm not responsible for anything which could be happen. I suggest to make a backup from TWRP.
First of all i didn't fix it. Thanks @Unjustified Dev , @DrakenFX and Anynomous Dev
Instruction:
Flash zip via TWRP.
Download:
uploading.
Click to expand...
Click to collapse
Thanks for that.
Do correct me if I'm wrong, but this still does not make use of the AKM DAC, right? This still uses the Qualcomm inbuilt DAC?
Thanks in any case!
joaste said:
Thanks for that.
Do correct me if I'm wrong, but this still does not make use of the AKM DAC, right? This still uses the Qualcomm inbuilt DAC?
Thanks in any case!
Click to expand...
Click to collapse
It's wired for it's AKM DAC the issue was we were dependent on ZTE crappy patch that made us bypass and force audio on. Now the amplifier HAL correctly calls to the NXP driver to properly calibrate and initialize audio in all usecases. It's more so the developer is trying to recreate how stock handles stuff like voice speaker, speaker reversing, mono + stereo, etc.
Unjustified Dev said:
It's wired for it's AKM DAC the issue was we were dependent on ZTE crappy patch that made us bypass and force audio on. Now the amplifier HAL correctly calls to the NXP driver to properly calibrate and initialize audio in all usecases. It's more so the developer is trying to recreate how stock handles stuff like voice speaker, speaker reversing, mono + stereo, etc.
Click to expand...
Click to collapse
How was this fix done exactly? Was it just fiddling with some configuration files or did you have to completely rewrite the way android works the audio so it calls the driver correctly? And if so, is it the same way Dolby does? I'm so curious how you guys and the anonymous dev managed to fix it
Also, I can't wait for this to upload. This + LOS based roms and this phone would be absolutely perfect. Too bad it's not mainstream enough to get more attention
If we flash this, will it cause any issues once it's officially merged into LOS and we update LOS on the phone?
WesTD said:
Hi All. The sound is fixed as you know but not on all ROM. So i've made a Fix zip. Tried on US and G versions.
IMPORTANT: I'm not responsible for anything which could be happen. I suggest to make a backup from TWRP.
First of all i didn't fix it. Thanks @Unjustified Dev , @DrakenFX and Anynomous Dev
Instruction:
Flash zip via TWRP.
Download:
uploading.
Click to expand...
Click to collapse
The download is not available.
Teet1 said:
How was this fix done exactly? Was it just fiddling with some configuration files or did you have to completely rewrite the way android works the audio so it calls the driver correctly? And if so, is it the same way Dolby does? I'm so curious how you guys and the anonymous dev managed to fix it
Also, I can't wait for this to upload. This + LOS based roms and this phone would be absolutely perfect. Too bad it's not mainstream enough to get more attention
Click to expand...
Click to collapse
Has nothing to do with dolby. There's a file libtfa9890.so stock audio hal calls this file does it's magic. On lineage we don't have the amp source which is packed into the audio hal on stock. We use an amplifier hal all this hal does it try to produce whatever the heck the stock audio hal did when it loaded libtfa9890.so. It basically allows you to instrument custom calls without touching the audio hal of the ROM therefore keeping it clean. ZTE gave us a patch that force loaded libtfa9890 and immediately said ignore all cases turn on the speaker. What the dev did is rewrite the patch to properly call all functions such as calibrate, set mode , speaker on , speaker off ,etc. This way we don't just force speaker we actually start saying if in call handle the speakers this way. If music is playing handle them this way. We don't just say if need sound ramp up the amp and make sound.
link added.
Has anyone who flashed it have a decrease in system performance?
Sent from my ZTE A2017U using Tapatalk
WesTD said:
link added.
Click to expand...
Click to collapse
Just installed this fix.
It works, it works, Hallelujah!.
Ya so this zip works on the Chinese version, so you can update the op
Also passed the stereo test. Left and right channels are both working independently and awesomely.
The distortion has nearly disappeared.
Calls work.
Thanks to all the devs especially unjustified dev and anonymous dev.
Thanks also to drakenfx and westd.
Also now that patch 3 is out, can we expect another zip in the future!
Unjustified Dev said:
Has nothing to do with dolby. There's a file libtfa9890.so stock audio hal calls this file does it's magic. On lineage we don't have the amp source which is packed into the audio hal on stock. We use an amplifier hal all this hal does it try to produce whatever the heck the stock audio hal did when it loaded libtfa9890.so. It basically allows you to instrument custom calls without touching the audio hal of the ROM therefore keeping it clean. ZTE gave us a patch that force loaded libtfa9890 and immediately said ignore all cases turn on the speaker. What the dev did is rewrite the patch to properly call all functions such as calibrate, set mode , speaker on , speaker off ,etc. This way we don't just force speaker we actually start saying if in call handle the speakers this way. If music is playing handle them this way. We don't just say if need sound ramp up the amp and make sound.
Click to expand...
Click to collapse
Genius. Didn't mean to say Dolby, meant zte I had Dolby Atmos on the mind. But if it's nothing to do with Dolby, how come they didn't release the source for a direct fix instead of releasing a half assed patch for devs to work with? Then there wasn't be an issue of it being closed or open source
WesTD said:
link added.
Click to expand...
Click to collapse
My latest Gerrit patch?
Sent from my ZTE A2017U using Tapatalk
FIGURES!!! I just went back to stock (but still have unlocked bootloader)....
Looks like I know what I'll be doing, at some point, this week!
GREAT WORK @DrakenFX
Unjustified Dev said:
My latest Gerrit patch?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
not latest, 2nd one. @DrakenFX will upload it soon.
WesTD said:
not latest, 2nd one. @DrakenFX will upload it soon.
Click to expand...
Click to collapse
Yeah, I sent him the libraries a few hours ago. Let me know if you need anything else.
Sent from my ZTE A2017U using Tapatalk
Unjustified Dev said:
Yeah, I sent him the libraries a few hours ago. Let me know if you need anything else.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Okay man. thanks for your works.
TWRP Flashable Stereo Sound Patch 3.
https://www.androidfilehost.com/?fid=457095661767152906
Thanks to Anonymous Dev. & @Unjustified Dev for all of this.
DrakenFX said:
TWRP Flashable Stereo Sound Patch 3.
https://www.androidfilehost.com/?fid=457095661767152906
Thanks to Anonymous Dev. & @Unjustified Dev for all of this.
Click to expand...
Click to collapse
Can users that already have the audio fix install this (NucleaROM)??
aLexzkter said:
Can users that already have the audio fix install this (NucleaROM)??
Click to expand...
Click to collapse
Yep this would work on any rom that uses amplifier hal which is all of them
Sent from my ZTE A2017U using Tapatalk
What's the improvement of V3 over V2 ?
PS : THX to every1 involved who made this possible !
Hi. I've created a patch that enable AK4490 on custom roms. Previosly it was pasted on 4pda.
Sry for bad English
If you are using latest Ainur betas from telegram you dont have to flash it because since beta 3 or 4 UltraM8 helped me integrate this patch into mod. Also Ainur doesnt have bag with call
Updated Magisk version to template 15000
Known bags:
When you call somebody you can not hear your subscriber. Solution: just enable and disable speaker mode.
UPD. If you're using OREO Rom, you dont have to use this mod because it was integrated into Rom. Plus if you're using Ainur, you dont have to flash it too
I thought that it was enabled by default on custom roms anyway? Or is this patch only so it works for sure with ainur?
Dodgexander said:
I thought that it was enabled by default on custom roms anyway? Or is this patch only so it works for sure with ainur?
Click to expand...
Click to collapse
If I understood right, no, patch will work without ainur
Dodgexander said:
I thought that it was enabled by default on custom roms anyway? Or is this patch only so it works for sure with ainur?
Click to expand...
Click to collapse
I also thought that, but I dualbooted LOS to try if the 192khz hack actually worked with the AKM DAC (because it was supposedly the one in use) and it was too obvious that it actually wasn't in use. The soundstage of the other DAC is much smaller. Maybe with this patch we can put it @ 192KHz with Poweramp? Can anybody try?
Skrem339 said:
Hi. I've created a patch that enable AK4490 on custom roms. Previosly it was pasted on 4pda.
Sry for bad English
If you are using latest Ainur betas from telegram you dont have to flash it because since beta 3 or 4 UltraM8 helped me integrate this patch into mod. Also Ainur doesnt have bag with call
Known bags:
When you call somebody you can not hear your subscriber. Solution: just enable and disable speaker mode.
Click to expand...
Click to collapse
Any chance that this will get integrated onto the ROMs themselves? This is the same as the Universal Bootloader stuff and the old TWRP it installs, we'll get to the point where we need to install dozens of zips to get a fully working system
p.s where can we get the Ainur betas?
Skrem339 said:
If I understood right, no, patch will work without ainur
Click to expand...
Click to collapse
Do you mean this patch is exclusively for Ainur to work with the DAC? Because custom roms have been working already in most apps with the AKM DAC.
Dodgexander said:
Do you mean this patch is exclusively for Ainur to work with the DAC? Because custom roms have been working already in most apps with the AKM DAC.
Click to expand...
Click to collapse
That's what everyone says, but dualboot stock and a custom ROM and using sound in LOS is like toggling the sound switch to standard
Choose an username... said:
Any chance that this will get integrated onto the ROMs themselves? This is the same as the Universal Bootloader stuff and the old TWRP it installs, we'll get to the point where we need to install dozens of zips to get a fully working system
p.s where can we get the Ainur betas?
Click to expand...
Click to collapse
In official Ainur Telegram chat. Pinned post
Dodgexander said:
Do you mean this patch is exclusively for Ainur to work with the DAC? Because custom roms have been working already in most apps with the AKM DAC.
Click to expand...
Click to collapse
Nope, it not only for Ainur because DAC doesnt work on Custom roms expect AEX.
Skrem339 said:
Nope, it not only for Ainur because DAC doesnt work on Custom roms expect AEX.
Click to expand...
Click to collapse
Really? I thought DAC was running OK on LOS... What about Pure Fusion and other ROMs? They say that high quality DAC is ALWAYS in use... I want to know what to flash when my phone arrives, DAC was mainly the reason for buying it.
FunkyRasta said:
Really? I thought DAC was running OK on LOS... What about Pure Fusion and other ROMs? They say that high quality DAC is ALWAYS in use... I want to know what to flash when my phone arrives, DAC was mainly the reason for buying it.
Click to expand...
Click to collapse
You want to know what to flash? Well this here zip is a start
Or stay stock lol
so no need for anything else just flash? even custom ROM?
gecko702 said:
so no need for anything else just flash? even custom ROM?
Click to expand...
Click to collapse
i think it is only custom ROM. Wouldn't make any sense if it was for stock since you have the hifi switch
Skrem339 said:
Hi. I've created a patch that enable AK4490 on custom roms.
Click to expand...
Click to collapse
Skrem339 said:
Hi. I've created a patch that enable AK4490 on custom roms. Previosly it was pasted on 4pda.
Sry for bad English
If you are using latest Ainur betas from telegram you dont have to flash it because since beta 3 or 4 UltraM8 helped me integrate this patch into mod. Also Ainur doesnt have bag with call
Known bags:
When you call somebody you can not hear your subscriber. Solution: just enable and disable speaker mode.
Click to expand...
Click to collapse
This is probably the best mod I've flashed on my phone. This + poweramp is magic. I tried Sauron (even joined the telegram chat) but it sounded very low and saturated. This is another story...
Awesome work, really.
Choose an username... said:
This is probably the best mod I've flashed on my phone. This + poweramp is magic. I tried Sauron (even joined the telegram chat) but it sounded very low and saturated. This is another story...
Awesome work, really.
Click to expand...
Click to collapse
Thx
Choose an username... said:
This is probably the best mod I've flashed on my phone. This + poweramp is magic. I tried Sauron (even joined the telegram chat) but it sounded very low and saturated. This is another story...
Awesome work, really.
Click to expand...
Click to collapse
What is your audio output setting on Poweramp?
I cannot get the Hi-Fi plugin to work.
Thanks dev for the mod
wannaskoo said:
What is your audio output setting on Poweramp?
I cannot get the Hi-Fi plugin to work.
Thanks dev for the mod
Click to expand...
Click to collapse
The Hi-res output? No, that doesn't work. But at least the AKM DAC is working. I'll try using the Samsung UHQA hack but I don't believe it'll work (it may just put the sd820 DAC at 192KHz
I enabled HiFi audio with the Lenovo Hifi line trick in the build.prop file, and i think i got a slight improvement, but it may be just placebo.
wannaskoo said:
I enabled HiFi audio with the Lenovo Hifi line trick in the build.prop file, and i think i got a slight improvement, but it may be just placebo.
Click to expand...
Click to collapse
The effect is really noticeable on the highs with a FLAC file. I used a 192KHz file to test, and the highs were awesome, but the soundstage got reduced a lot (this was on stock, so I went from 48khz AKM DAC to 192khz SD820 DAC). I'll try on LOS today
I would love to understand the workings behind this. Once you install this how can you tell it works?
Please don't tell me to listen because that's pointless with placebo effect. I'm simply looking for the technicalities that prove audio is being sent via dac with or without this mod.
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