Related
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.
Hi Guys! I'm a little bit confused between Dolby Atmos and Viper4Android. I am a Kenzo user and currently using NOS O latest build.
So please suggest me which one should I flash? Dolby or Viper
and please give the best settings for it if you have.
Thanks in advance
Search FIRE SOUND in XDA (in our forum RN3 Pro)
Have Dolby and V4A and much other tweaks.
I love this mod
Edit: Link
Dolby, but you have to make sure that you flash the working version - some versions seem to work but actually do nothing and to make sound virtualizer work is not trivial.
Try Jetaudio music player, their plugins are actually working and doing the job great.
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
Has anyone been able to install Dolby Atmos on the Pixel 4a? I have tried several versions, but they fail to install. I have Viper4Android installed, but uninstalled it before trying the various Dolby mods.. I have tried Dolby Atmos on my iPad with Apple Music and it sounds really good! I am not able to replicate the sound with Viper either… Viper sounds excellent, but I can’t get the spatial sound as good as Dolby Atmos.
it works fine for me
10.0 OS - Google Drive
drive.google.com
Thanks! It worked, but this seems to be Dolby Digital… I use Apple Music and my wife’s Samsung S21 the Dolby Atmos switch is present in the app, on my Pixel 4a it’s not. Even with this mod it’s not possible to activate. There is a track on Apple Music, «From sterero to spatial» with The Weeknd’s Save Your Tears with a voiceover talking about Dolby Atmos. Halfway through the track, Dolby Atmos is activated and the change is extreme! Sadly, on my Pixel there’s no change in audio even with this mod.
So, what I am looking for is a Dolby Atmos mod which enables Dolby for Apple Music as well..
You can use Razer Phone 2 Dolby Atmos, which is one of the best modules ever made. Below is the zip file, as far as I know it works on all Android versions. If you are using A12, yes, it works. I tried the same on stock Android and Lineage OS, but in PE, but it was going to bootloop. But not in any other os.
arun_jose said:
You can use Razer Phone 2 Dolby Atmos, which is one of the best modules ever made. Below is the zip file, as far as I know it works on all Android versions. If you are using A12, yes, it works. I tried the same on stock Android and Lineage OS, but in PE, but it was going to bootloop. But not in any other os.
Click to expand...
Click to collapse
do i need root to install this module ?
lufa28 said:
このモジュールをインストールするには root が必要ですか?
Click to expand...
Click to collapse
yes