Thread to be closed.
Thanks for the guide, much appreciated!
works great on EvoX too.... Thanks for the tip
I have installed this mod on Miui eu v11.0.11 and it works beautifully. The bass is much cleaner than dolby atmos plus which has very muddy bass. The definition is also way better with viper. The only thing I'm yet to figure out is how to reduce the processing delay. It is noticeable sometimes when increasing volume or changing tracks.
Also when the bass hits there's clearly some hint of attenuation going on which makes me feel that something is limiting the overall output. I will go over the instructions for v4a because it's much more complicated than atmos. After that I can give a proper opinion.
Thanks a lot for this tutorial.
Sent from my Redmi Note 9S using XDA Labs
twistyplain said:
I have installed this mod on Miui eu v11.0.11 and it works beautifully. The bass is much cleaner than dolby atmos plus which has very muddy bass. The definition is also way better with viper. The only thing I'm yet to figure out is how to reduce the processing delay. It is noticeable sometimes when increasing volume or changing tracks.
Also when the bass hits there's clearly some hint of attenuation going on which makes me feel that something is limiting the overall output. I will go over the instructions for v4a because it's much more complicated than atmos. After that I can give a proper opinion.
Thanks a lot for this tutorial.
Click to expand...
Click to collapse
That's normal as every device will be hardware limited on the output gain. Try adding gain amplification, it might help in some cases.
There are way too many options to go through, but you will most likely find what you need.
Failed to install on sootis GSI rom, everything installed but NEON: enabled and the rest all say no
TheFieryBreeze said:
Failed to install on sootis GSI rom, everything installed but NEON: enabled and the rest all say no
Click to expand...
Click to collapse
Don't worry, v4a does not work on his A10 or 11 versions. I tried on both already. I recommend you trying other firmware. PixysOS works well.
On redmi note pro global after doing everything it shows the driver version but the rest is No's neon enabled no too . I'm on latest EU.miui
Russlle said:
On redmi note pro global after doing everything it shows the driver version but the rest is No's neon enabled no too . I'm on latest EU.miui
Click to expand...
Click to collapse
MIUI 12? I havent tried this on MIUI 12 yet. Global is still receiving the update, so I'm currently using PyxisOS.
EDIT: I've found the "fix" for the issue. Just go to Settings and enable Legacy Mode. This alone worked for me on MIUI 12.0.1 EEA Global.
Russlle said:
On redmi note pro global after doing everything it shows the driver version but the rest is No's neon enabled no too . I'm on latest EU.miui
Click to expand...
Click to collapse
Turn on legacy mode on Settings
Quick note for all those who like to install every single update out there... The newest version of v4a app (2.7.2.1) was really misbehaving on my 9s running miui eu v11.0.11 so I had to remove it. Every time a notification came in there was a loud crackling noise from the loudspeaker just before and after playing the notification tone. It's as if the speaker is turned on and off just before playing a sound but the popping sound was extremely annoying. Also, the app obviously isn't optimized to work on the rom because it could only work in compatibility mode. Disabling compatibility mode made the app unresponsive and sometimes it froze up the entire system forcing me to hard reboot. Loading ddc and irs presets was hit and miss at best.
Anyone wishing to update the v4a app from v2.7.1.6 be warned. If you decide to update anyway, let us know if it works well for you and your rom setup.
PS: I just stumbled across the ddc and irs profiles for my iems and I'm completely sold. Viper4Android is the king of sound mods. Dolby can't touch a hair on it. I knew that my once timid redmi note 9s was a music giant. It just needed to be woken up and v4a was the adrenaline shot it needed.
I just couldn't live with the crappy sound of the stock rom knowing that the Texas Instruments TAS2562 Class-D Audio Amplifier in my phone was capable of putting out up to 6w of power.
Sent from my Redmi Note 9S using XDA Labs
Can you share those profiles? I tried the latest v4a and it wouldn't work. It just wasn't active when I clicked on the chip icon.
kalehrl said:
Can you share those profiles? I tried the latest v4a and it wouldn't work. It just wasn't active when I clicked on the chip icon.
Click to expand...
Click to collapse
To make v4a work just go back to version 2.7.1.6.
DDC profiles are specific to the headphones they're calibrated for. If you try them on different headphones they will sound like crap because every headphone model is tuned differently by the manufacturer.
Sent from my Redmi Note 9S using XDA Labs
Actually it works in legacy mode after removing Audio modification library and rebooting.
kalehrl said:
Actually it works in legacy mode after removing Audio modification library and rebooting.
Click to expand...
Click to collapse
Thanks. I didn't try that. Is it completely stable?
Sent from my Redmi Note 9S using XDA Labs
It is. No problem with notification sound. Didn't notice any instability.
kalehrl said:
It is. No problem with notification sound. Didn't notice any instability.
Click to expand...
Click to collapse
Keep testing. I'm not going to reinstall it just yet. I don't even see a big difference over the previous version. The most notable changes target android 11.
Sent from my Redmi Note 9S using XDA Labs
I can confirm this, V4A FX 2.7.2.1 work on 11.0.10.0 without Audio Modification Libary.
I just needed to enable legacy mode, it seems stable and without any bugs.
I will report back in a few days if something is wrong
12/11/2020 edit: yup, everything seems to be fine
Seems like V4A doesn't work on Redmi Note 9S with MIUI 12.0.2 Global, or atleast it doesn't work on my RN9S. I've tried everything mensioned here and on other forums but I always get
Neon enabled: No
Status: Abnormal
Audio Format: Unsupported.
Ive literally ran out of ideas now.
[Update] I finally got it working. I remembered that some years back, in order to get V4A working we had to change SELinux from "Enforce" to "Permissive". So I downloaded SELinuxModeChanger, changed SELinux to "Permissive" and now V4A is working great. To keep V4A working after every reboot I have to change SELinux to "Permissive", which I don't really mind...
Thanks for the update, helped me get v4a processing again on v12. I knew about the selinux restriction but it was so long ago I completely forgot about it. Good thing SELinuxModeChanger still works despite not being updated for 3 years
Related
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.
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.
So just like with other OnePlus phones, since the introduction of Dolby Atmos, EU devices are missing the equaliser option from their settings. The solution to get it back was quite simple: You could install the global AA firmware and the setting would re-appear. Better yet it was discovered that you could simply install the Dolby Atmos APK from the Razer 2 and get even more control.
Now that we're dealing with Dirac, it's clear that installing the Dolby Atmos APK won't do us any favours, so back to plan A: install the India firmware (this time DA - AA firmware is out there, but not on Oxygen Updater yet). However, it turns out that was wasted effort as, despite now being on India firmware, the option is still missing.
Now I know there is (or was) an equaliser option on the Nord - as I've spotted it in various Indian review vids.
For example, here is the XDA review of the EU Nord, which lacks the option: https://www.xda-developers.com/oneplus-nord-review/ | [Dirac Audio Tuner]
And here is an example of the Indian Nord, which has the option: https://youtu.be/q476VlnRsbQ?t=765
So this begs the question - have OnePlus introduced further checks to disable the option for EU units? Or have they simply removed the option for everyone?
It'd be interesting to see whether other people are seeing the option and whether there's anyone out there with the global firmware (AA) and what they see
Hey I just flashed my EU device with the global FW and still got no EQ
But I just did it via local update and did not wipe, maybe that helps.
Would be awesome to activate it with adb or something
I don't have it in my Indian variant. It's only there when I connect an earphone.
AmoghUpadhyay said:
I don't have it in my Indian variant. It's only there when I connect an earphone.
Click to expand...
Click to collapse
If that's the case, sounds like they just outright removed the option.
Must admit, the version shown in the YouTube video did look like the dolby atmos eq. Perhaps dolby weren't to happy about that and told OnePlus to remove it... We can only speculate.
I have the dirac audio tuner on mines?
I have the Equaliser in my EU Rom!
denndenn said:
I have the Equaliser in my EU Rom!
Click to expand...
Click to collapse
That is not the equilizer as mentioned in the TS: https://youtu.be/q476VlnRsbQ?t=765
But I understand correctly there is no solution to get the equaliser working on the Nord? That is a real bummer! Because sometimes you just want to add a little bit of bass or surround to your source. Isn't there anything we can do? Like complaining @ One+?
I do have Equalizer in India. But this works only when earphones are connected.
Sent from my OnePlus AC2001 using XDA Labs
AmbientBenji said:
That is not the equilizer as mentioned in the TS: https://youtu.be/q476VlnRsbQ?t=765
But I understand correctly there is no solution to get the equaliser working on the Nord? That is a real bummer! Because sometimes you just want to add a little bit of bass or surround to your source. Isn't there anything we can do? Like complaining @ One+?
Click to expand...
Click to collapse
Oh, sorry! You are right!
Damn
Works for me with sony wireless headphone !!!
adnanahmad1786 said:
Works for me with sony wireless headphone !!!
Click to expand...
Click to collapse
Latest version? Else we can install the Indian version and this would fix our problems.
Why doesn't EU and Global versions doesn't have an equalizer pffff.. Due to restrictions? It's just an equalizer. Can somebody explain why?
I have added an idea for the equalizer. Please vote, and hopefully they will add this option: https://www.oneplus.com/nl/communityideas#/detail?threadId=1662
lekiaM said:
Why doesn't EU and Global versions doesn't have an equalizer pffff.. Due to restrictions? It's just an equalizer. Can somebody explain why?
Click to expand...
Click to collapse
Possibly some patent (infringement) they would need to pay for, or some law around data collection being broken. there are equalizers in the app store, so you could also say, great, less bloatware on the device
Does anybody have this kind of problem since last update 11.0.11.0 on redmi note 9s?
I had this problem on stock rom and miui eu but I installed dolby digital and the volume is much better. It's a lot louder and with the dolby presets it seems to have higher definition and much wider soundstage. I use music preset with volume leveler and open eq.
Sent from my Redmi Note 9S using XDA Labs
this is not because of the update. this is long issue and permanent, atleast in selective region. solution for this is change your region to st. helena then reboot ur phone
I like to try out new things so I installed viper4android and the results are phenomenal. @Urosz you should skip dolby and install viper. My audio is so much better than it was with dolby. Dolby made the phone louder but it was quite muddy. Viper is a lot crisper and you have control over a lot more aspects of the audio. Try viper and you won't regret it.
Another audio mod I loved is Ainur Sauron or narsil but unfortunately there's no compatible version for curtana.
Sent from my Redmi Note 9S using XDA Labs
twistyplain said:
I like to try out new things so I installed viper4android and the results are phenomenal. @Urosz you should skip dolby and install viper. My audio is so much better than it was with dolby. Dolby made the phone louder but it was quite muddy. Viper is a lot crisper and you have control over a lot more aspects of the audio. Try viper and you won't regret it.
Another audio mod I loved is Ainur Sauron or narsil but unfortunately there's no compatible version for curtana.
Sent from my Redmi Note 9S using XDA Labs
Click to expand...
Click to collapse
Is viper in flashable mod format or a magisk module? Can you link to it?
Sent from my Redmi Note 9S using Tapatalk
gsmyth said:
Is viper in flashable mod format or a magisk module? Can you link to it?
Click to expand...
Click to collapse
It is not in a flashable zip but it uses magisk to alter system files systelmlessly. In magisk you need to install audio modification library from the online repo and then the viper apk. Here is a thread with instructions that work for installing v4a perfectly. Make sure you follow the instructions to the letter. Otherwise you'll have to start afresh. There's no risk of bricking your device during this installation.
https://forum.xda-developers.com/redmi-note-9-pro/how-to/mod-viper4android-how-to-install-t4163447
Also, i found that the newest viper does not work well unless you enable legacy mode which I don't like because it means that something in it doesn't work well on our system. I have the previous version which is flawless but it isn't available from the viper download page. I have uploaded it on my mega cloud drive. You can download it using this link... Happy modding. Thumbs up if this eventually solves your low audio issue.
https://mega.nz/file/J14SRIIT#CGNUlQ1QTTB_HYPTvLkGzmLupMXDYkP3ZjXQ_2Ul9fg
Sent from my Redmi Note 9S using XDA Labs
I feel like I tried every combination of installing things to get Viper4Android to work on the Pixel 6. I'm currently on rooted January update and I don't think I ever had Viper4Android working correctly. I've gone through this forum trying to find a solution and have tried...
SE Lenix Changer.apk to set to permissive (I've flipped back since it didn't work)
Ainur-Narsil
AML-4.0.zip
acp.zip
ViperFx_Android12_fix.zip
I followed a few different solutions that didn't work for me and was just wondering if anyone has had luck getting it to run correctly on the Pixel 6 Jan update - your solution would be greatly appreciated!
happynexuss said:
I feel like I tried every combination of installing things to get Viper4Android to work on the Pixel 6. I'm currently on rooted January update and I don't think I ever had Viper4Android working correctly. I've gone through this forum trying to find a solution and have tried...
SE Lenix Changer.apk to set to permissive (I've flipped back since it didn't work)
Ainur-Narsil
AML-4.0.zip
acp.zip
ViperFx_Android12_fix.zip
I followed a few different solutions that didn't work for me and was just wondering if anyone has had luck getting it to run correctly on the Pixel 6 Jan update - your solution would be greatly appreciated!
Click to expand...
Click to collapse
This method worked for me. I did install JamesDSP and AML beforehand.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Lughnasadh said:
This method worked for me. I did install JamesDSP and AML beforehand.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Click to expand...
Click to collapse
I tried and it was the first time I saw it work!! was excited but I was using the phone's speakers. When I tried using my XM3s I was still getting the same
NEON enabled: No
Enabled: No
Status: Abnormal
Processing: No
I'm not sure if it wasn't working before because I didn't try it with my phone's speakers but at least now I know it's somewhat working! any idea if I should expect it to not work using my bluetooth headphones?
Lughnasadh said:
This method worked for me. I did install JamesDSP and AML beforehand.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Click to expand...
Click to collapse
Sorry was excited to see some progress and forgot to thank you - I sincerely appreciate your response!
happynexuss said:
I tried and it was the first time I saw it work!! was excited but I was using the phone's speakers. When I tried using my XM3s I was still getting the same
NEON enabled: No
Enabled: No
Status: Abnormal
Processing: No
I'm not sure if it wasn't working before because I didn't try it with my phone's speakers but at least now I know it's somewhat working! any idea if I should expect it to not work using my bluetooth headphones?
Click to expand...
Click to collapse
Legacy Mode does need to be enabled. It does work with my Pixel Buds Series -A via bluetooth for me.
happynexuss said:
Sorry was excited to see some progress and forgot to thank you - I sincerely appreciate your response!
Click to expand...
Click to collapse
No problem
Lughnasadh said:
Legacy Mode does need to be enabled. It does work with my Pixel Buds Series -A via bluetooth for me.
Click to expand...
Click to collapse
yup it's enabled! so weird though because I can't get the headphones to work. I found a thread where someone was using viper4android with the xm3s so I think it's do-able. I also tried the below with no luck
audio compatibility patch
audio modification library
viperfx_android12_Fix.zip
Ainur Narsil
If anyone has any idea what might still be causing issues using Viper4Android on my bluetooth Sony XM3s but it works fine on the phone's speakers I'd sincerely appreciate your input!
And thanks again Lughnasadh!
happynexuss said:
yup it's enabled! so weird though because I can't get the headphones to work. I found a thread where someone was using viper4android with the xm3s so I think it's do-able. I also tried the below with no luck
audio compatibility patch
audio modification library
viperfx_android12_Fix.zip
Ainur Narsil
If anyone has any idea what might still be causing issues using Viper4Android on my bluetooth Sony XM3s but it works fine on the phone's speakers I'd sincerely appreciate your input!
And thanks again Lughnasadh!
Click to expand...
Click to collapse
One more thing I can think of to try. Go into Developer Options and disable HD audio. Forgot about that, lol. Hope it works for ya.
It's pretty easy to get it working, download the regular APK of Viper, open it and let it install the drivers, after the reboot go into adb/modules/viper4android and replace the old post-fs-data.sh file with this one and enable legacy mode, reboot and enjoy
Tested on Stock, ProtonAOSP and CalyxOS on pixel 6
Lughnasadh said:
One more thing I can think of to try. Go into Developer Options and disable HD audio. Forgot about that, lol. Hope it works for ya.
Click to expand...
Click to collapse
I tried to disable HD audio in Dev Options but it was already disabled and the toggle option itself was disabled - could that be an issue?
flyl0 said:
It's pretty easy to get it working, download the regular APK of Viper, open it and let it install the drivers, after the reboot go into adb/modules/viper4android and replace the old post-fs-data.sh file with this one and enable legacy mode, reboot and enjoy
Tested on Stock, ProtonAOSP and CalyxOS on pixel 6
Click to expand...
Click to collapse
I tried that and it gets it working for the phone's speakers and I just learned it also works in my car. But when I hook up my Sony XM3s all the options are disabled like I posted above even with legacy on. It seems to be something with the headphones themselves since the car is also BT it can't be a BT issue.
happynexuss said:
I tried to disable HD audio in Dev Options but it was already disabled and the toggle option itself was disabled - could that be an issue?
Click to expand...
Click to collapse
Mine is greyed out as well but I think only because I have it disabled in my Pixel Buds settings. If I enabled in the Pixel Buds settings I believe it won't be grayed out on the Developer Options. Buds are in the car so can't test right now but that's how I remember it.
Not really sure why you can't get yours going.