Hi I am running CyanogenMod 11 nightlies on my Droid DNA and whenever the volume is over half on the external speakers, the bass makes a "slapping" sound (similar to what you'd hear in one of those overly loud car stereo systems). Anyways, this has begun to get pretty irritating and I'm wondering if anyone has come across this problem or has any solutions. I've checked the DSP manager app that comes preinstalled on CM and bass boost is turned off and all the settings look fine to me.
Regards,
Alex
EDIT: I found a solution, use a root uninstaller to delete the DSP application, reduces the speaker crackling and bass slapping effect.
cmdrtomalacc said:
Hi I am running CyanogenMod 11 nightlies on my Droid DNA and whenever the volume is over half on the external speakers, the bass makes a "slapping" sound (similar to what you'd hear in one of those overly loud car stereo systems). Anyways, this has begun to get pretty irritating and I'm wondering if anyone has come across this problem or has any solutions. I've checked the DSP manager app that comes preinstalled on CM and bass boost is turned off and all the settings look fine to me.
Regards,
Alex
EDIT: I found a solution, use a root uninstaller to delete the DSP application, reduces the speaker crackling and bass slapping effect.
Click to expand...
Click to collapse
Also you can use Viper4Android instead of DSP.
You try using http://forum.xda-developers.com/showthread.php?t=2211163 with clarity speaker option? It worked on my DNA to reduce the bass distortion. I used it on sense, so don't know how well it works on AOSP
Sent from my HTC6500LVW using XDA Free mobile app
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.
Hey all! Just bought the 7.1 from B&H for $349 to replace my Moto g5 plus which is full of issues. One thing I will miss is being able to install V4A (Viper equalizer). I can tune the settings and make my Bluetooth to car connection sound a hell of a lot better than actually changing the settings on the head unit. Was wondering if there was a stock (or built in) EQ for the Nokia 7.1 that I can use to tune Spotify, YouTube, etc. or if I'll have to download a crappy EQ app off of the play store. Is there a built in EQ, or even better, a way to install V4A on this phone without TWRP? Thanks!
Rhyme_Thyme said:
Hey all! Just bought the 7.1 from B&H for $349 to replace my Moto g5 plus which is full of issues. One thing I will miss is being able to install V4A (Viper equalizer). I can tune the settings and make my Bluetooth to car connection sound a hell of a lot better than actually changing the settings on the head unit. Was wondering if there was a stock (or built in) EQ for the Nokia 7.1 that I can use to tune Spotify, YouTube, etc. or if I'll have to download a crappy EQ app off of the play store. Is there a built in EQ, or even better, a way to install V4A on this phone without TWRP? Thanks!
Click to expand...
Click to collapse
There is a way to change the Bluetooth codec in the dev menue, not the same as an EQ but wouldn't you want the signal to transfer as true as possible and use your speaker source EQ?
tibman said:
There is a way to change the Bluetooth codec in the dev menue, not the same as an EQ but wouldn't you want the signal to transfer as true as possible and use your speaker source EQ?
Click to expand...
Click to collapse
Yeah I got the phone, saw the stuff in the devs. To answer everyone's question, there is a built in EQ, but you have to open Spotify to use it (not sure if GPM or Pandora work). It's not terrible, but certainly not as good as V4A. And to respond to your question, I don't think the signal transfer is really touched with an EQ. The EQ adds bass and lets me adjust my mids to the way I like them. Like I said, my head unit is garbage. The EQ practically does nothing to improve bass or mids. At first I thought it was the speakers but it isn't. Thats why I wanted a built in EQ on my phone, until I get a new head unit at least.
Hello,
i bought a LG V30 a few days ago, because i want to use it as DAC or DAC/AMP.
Before i used an Axon 7 with Viper4Android, a headphone amp (Schiit Vali2) and a custom VDC file for Viper4Android with these settings.
https://www.dropbox.com/s/v999jbft39506ma/Sennheiser HD800.pdf?dl=0
It made a huge difference to use my headphone (Sennheiser HD800) with or without these parametric equalizer settings.
Perhabs it is useful for you, here a link with many different eq settings. Think this can improve sound quality of many headphones or inears.
https://www.reddit.com/r/oratory1990/wiki/index/list_of_presets
1. Most important part, i want the best possible sound quality. Ainur Sauron, Ainur Narsil, Whiskeyomega Soundmods, https://forum.xda-developers.com/lg-v30/themes/magisk-bring-24-bit-output-aosp-pie-t3900863 .....
Dont know, because im new with this phone...
2. I need a parametric equalizer with 10 bands. Viper4Android use VDC files, but i read somewhere that Viper4Android only can handle 48000. And i wanna use the full potential from this Quad DAC.
It is an option for me to use USB Audio Player Pro and if i am right, it is possible to use inbuild parametric eq with only 6 bands.
3. If best sound quality is only with stock roms possible, its ok for me. But if it makes no difference i prefer custom roms. My device is H930, do you have any recommendations?
Hope someone can help me to squeeze the best audio quality from these wonderful device.
Thank you
Adriano
I don't think you can use viper4android with the DAC because viper4android will resample the audio back down to 16 bit @ 48khz. Thus it's pointless to use the DAC + v4a at the same time. Someone correct me if I'm wrong.
Sent from my SM-G955U using Tapatalk
Hi
1.) best possible sound quality - thus you want as little processing as possible (audiophile paradigm) - go with AINUR NARSIL
2.) viper4android is outdated, closed source and is supposed to offer worse quality vs. JamesDSP, both are limited to 48 kHz though
https://github.com/james34602/JamesDSPManager
https://forum.xda-developers.com/android/apps-games/app-reformed-dsp-manager-t3607970
So if you want to go that route, you'll limit yourself to 48 kHz and 16 bit.
according to https://github.com/jaakkopasanen/AutoEq
USB Audio Player PRO
USB Audio Player PRO is an Android app with improved USB audio drivers for usage with USB DACs. USB Audio Player PRO is not system-wide but works with local files and many streaming services though not with Spotify. USB Audio Player has Toneboosters Morphit plugin which has parametric equalizer. This app and the plugin are not free.
Click to expand...
Click to collapse
UAPP with the Morphit plugin (additional purchase) would be the (best?) way to go to retain best possible quality with a parametric equalizer.
Someone needs to try that though and e.g. toggle the quad / SABRE DAC and see how well it works with UAPP and the MorphIt plugin
3.) nope, in fact there's more processing on LG Stock ROMs and thus it sounds warmer and different than the less processed and colder output on AOSP-based ROMs - thus the quality on AOSP-based ROMs should be closer to source (less processing = "better", less additional artifacts and distortions)
LG Stock ROMs are a must though if you're dependent on voLTE or voWiFi
Hope that helps
I want to root and install viper4android to my s22+ with july update. Cause it's volume is too low. Evenmore, i tuned the bass little bit higher in equalizer, at cost the treble become lower. I've tried volume booster from playstore, but it rather buggy and distorted. So, is viper4android work on s22+ july update?
I still did not root my device, but if I do, I would use JamesDSP instead of V4A.
Without root, Wavelet does a decent, basic job. It lacks convolver/DDC functionality but allow to improve bass without ruining the rest of the frequencies (as Samsung equalizer does).