yashsingh1/xdaforums huggingface dataset:
[Magisk] DaveedDB:
The answer is 2 post under your original post on page 68 , delete all other sound mods install the new one and yes Dolby has be updated
[Magisk] chudy_85:
Now v2.0 work correctly with magisk v14.2 on my p9
[Magisk] TahirZX:
Thanks alot. Can you or anyone provide me link to the latest Dolby Atmos?
[Magisk] 24imelqui:
Choose the dobly atmos for your device

https://www.androidfilehost.com/?w=files&flid=165963

Search this thread for info

https://xdaforums.com/android/software/soundmod-axon-7-dolby-atmos-t3412342
[Magisk] andre0005:
Which one would you choose for the op5?
[Magisk] ahrion:
I didn't even know. Was it installed clean or did it work when upgrading?
[Magisk] 24imelqui:
Try the Axon 7 Dolby
[Magisk] mttrwlnd:
Did you install it through Magisk Manager, or did you flash it in TWRP. Also, did you need to set your SELinux to permissive?

I'm trying to troubleshoot V4A on my Pixel XL with 14.2
[Magisk] chudy_85:
I flash only via magisk manager
[Magisk] GalaxyS3only:
THANKS!

Finally an attempt that works:

I'm on Samsung Galaxy S3 LineageOS 14 and rooted by Magisk (do it best opensource solution!)

After i flashed your v4afx_2.0.zip with TWRP, i can finally enjoy Viper4Android as an magiskmodule without problems and strict SELinux ^^
[Magisk] Lycox:
Thanks. Works now :good:
[Magisk] abdullahsabbir:
I've tried a lot of variants of Viper4Android on my Phone, but it doesn't Process the Audio (In Driver Status Processing: No). Any solution for this?

I've tried replacing the .conf file of /magisk/v4a/system/etc to /magisk/v4a/system/vendor/etc (or the similar directory, I don't remember the exact one), but didn't fix anything.

P.S. I'm using Mi 5 with Resurrection Remix ROM and Magisk 14.0.
[Magisk] ~N.A.W.Y~:
Make sure your SELinux is Permissive.

MI 5 cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] Cristiano Lira:
Also not working here (driver status: abnormal), SELinux is permissive. Magisk v14, using MagiskSU.
[Magisk] gametimebrizzle:
Processing will only show 'Yes' if there is audio currently being processed - in other words, you must actually have music/audio playing in order for the libraries to process anything.

This may sound trivial (and obvious), but make sure audio is actually playing, then check your processing status.
[Magisk] abdullahsabbir:
Yes, I tried with SELinux in Permissive Mode. Didn't work.

---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------

I checked with Audio Playing on my Phone. I tried with PowerAmp and Spotify. Didn't work.
[Magisk] ~N.A.W.Y~:
Weird. I have the same setup (plus systemless xposed) and it's working.

Do you have the deep buffer remover v3.0? If not, try with that one.

MI 5 cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] gametimebrizzle:
Do you have init.d supoort?

OR

Is post-fs processing the scripts?

ROM? Kernel? Phone? Android Version? Logs?

Is SELinux statically set to permissive or do you have a init.d or post-fs script that temporary grants the permissive state?

Do you have the correct 'prerequisite' modules?

Have you looked anywhere to attempt to solve the issue on your own? Or looked/searched for common causes to the issue?

You should try to provide more pertinent information so others can help you with your issue; if you don't know what information may or may not be relevant, go over the FAQs to see some common issues, and that should give a clue to the information needed to at least attempt to resolve the issue.

HELP US HELP YOU!

---------- Post added at 04:14 PM ---------- Previous post was at 04:05 PM ----------

Those music players are notorious for not processing.

Search for more compatible music players, there is a list floating around somewhere that lists players that are known to work well with V4A.

Also, read up on the Android "deep buffer" (particularly the removal of said buffer), or just install the deep buffer remover module in Magisk. Also the Audio Modification Library Module.
[Magisk] abdullahsabbir:
Just installed V4A again and also this time installed Deep Buffer Remover 3.0 (I used an older version before), but still not working.

Which Audio Player do you use?
[Magisk] ~N.A.W.Y~:
Phonograph for local files and Spotify-Youtube for streaming

MI 5 cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] abdullahsabbir:
I did as you asked. Installed deep buffer remover and also Audio Modification Library. Still doesn't work. Do you have any preferable Music Player? Which one do you use?
[Magisk] TahirZX:
BlackPlayer EX
[Magisk] Cristiano Lira:
Android 8. Nexus 4. ROM Unlegacy Android.

SELinux comes already set to permissive with the kernel but I also tried installing the magisk permissive module.

The only prerequisite is auto-installed with this lib (audiomodlib).

Of course I have searched for who could make V4A work on Oreo but what they did didn't worked out for me, so I saw some cases where some people where able to have V4A working only with magisk and this module on their phones (but on android 7 or earlier) and I wanted to give a try. I think the problem is with Android 8, and Viper needs to be updated to support it, or there's still some protection built in for root apps that needs to be turned off for it to work (like su related), idk.
[Magisk] gametimebrizzle:
Your reply makes all the difference, the important thing here is, as you mentioned, Android Oreo. If it were Nougat, I could possibly help, but not Oreo.

I won't be much help to you with anything regarding Oreo and it's quirks because I've only managed to get it installed and rooted on a couple of test devices, none being in the Nexus family.

Curious though, have you looked into any of the other sound mods? I think they have A.R.I.S.E. up and running on Oreo.
[Magisk] Cristiano Lira:
Yeah, I've found a post with a installation prop that only installs V4A with A.R.I.S.E. but it was the same. But thanks for you will of help. :fingers-crossed: I'll go back to Nougat till I see someone on Oreo with it working on my device.
[Magisk] prasetya27:
Working fine on ZE601KL .. I use v2.0 and magisk v14.2 in AEX rom... And the status of SElinux is Enforcing no problem at all still worked 100% .. Thanks dev for you hard work to bring a amazing sound effect .. Here is the Screenshot for my device
[Magisk] ahrion:
I need Oreo testers.
[Magisk] ShaqBoss:
Hey all, i just want to confirm this working on Oneplus 3t running the latest (final) resurrection remix rom paired with the latest boeffla kernel.

The only issue i have is that it only works on the stock music app and not my preferred music player, jetAudio plus. It's no biggie, but i thought others should know as well. :b
[Magisk] ahrion:
Flash the Universal deep_buffer Remover (UDBR).
[Magisk] shantam3108:
Here for Oreo testing
[Magisk] ahrion:
Do any of mine and [MENTION=6037748]Zackptg5[/MENTION] modules work for you?
[Magisk] shantam3108:
Well it's pretty weird

On my redmi note 3(f2fs) nothing happens with the Dolby module(tested with axon7 and lepro) installed. Sometimes Dolby app would just crash. It's a mix sometimes app opens but doesn't work and sometimes it would just crash. Viper doesn't process for me

Installed udbr too and still same.

On my nexus 6p I will be flashing oreo by tomorrow and letting u know. :)

---------- Post added at 01:37 PM ---------- Previous post was at 01:17 PM ----------

[MENTION=5357345]ahrion[/MENTION] Just clean flashed my 6p and everything works great axon 7 + viper and no issues what so ever. :)

Though I am same rom on both my devices. It didn't work for redmi note 3(f2fs)
[Magisk] ahrion:
Something with Redmi is weird. But confirm working on Oreo? Try another version for Redmi note 3.
[Magisk] ahrion:
Have you checked on your Redmi note 3 if the files all placed in the v4a module folde in Magisk or system? Was it installed with Magisk or system?
[Magisk] shantam3108:
Yes confirmed working on nexus 6p oreo for sure. No issues
[Magisk] shantam3108:
It's in magisk. I installed it with magisk.

I suppose it's due to that fact nitrogen uses aosp trees and has its own so many boot scripts . I had it working on rr 7.1.2 just yesterday. Seems it only works on Los based rom. Since
[Magisk] shantam3108:
I am sure it would work on Los 15.1 on redmi note 3.

Everybody has complaints with nitrogen breaking stuff but it's currently most smoothest rom out their for Kenzo which is stable too
[Magisk] ahrion:
Is v4a/system/lib/soundfx/ there? I need to know if the lib installed.
[Magisk] shantam3108:
This one
[Magisk] shantam3108:
This is my v4a screenshot
[Magisk] ahrion:
I guarantee it's gonna be audio FX, musicfx, or one of your music players that keeps it from processing and. Udbr might be necessary. I would also check to see if it works on streaming apps and stock music apps that don't require streaming.
[Magisk] shantam3108:
I uninstalled music fx the first time I boot my device..

I was streaming using play music when I posted the screenshot.

Udbr is already installed
[Magisk] ahrion:
Did you enable? You may have to flash my deep buffer remover.
[Magisk] ahrion:
Good news guys. I finally found a fix for AM3D and Dolby Atmos to work 100% in enforcing on both MagiskSU/SuperSU, Magisk OR System install.

This will be available in the AudModLib v1.3 update I will be pushing soon. I'll obviously fix any more bugs or make any other additions in the meantime.
[Magisk] Phrodini:
Good news indeed
[Magisk] metrize:
Yh i tried to use viper using apk. Any link for deep buffer?
[Magisk] Zackptg5:
Just search for it dude: https://xdaforums.com/apps/magisk/module-universal-deepbuffer-remover-t3577067
[Magisk] metrize:
yeah I know I forgot to edit my post saying I found it.

Thanks bro anyway :safe:

Now it works in compatibility mode
[Magisk] jbaumert:
[MENTION=5357345]ahrion[/MENTION] - Thank you very much for this module!! Finally have ViPER working on my N6/7.1.1 stock using the Magisk method.
[Magisk] gettingerr:
Has any one with a Pixel XL had any luck with this module? I have tried installing through Magisk and through TWRP and either way I bootloop. Deleting the folders with mount Magisk lets me boot again, but obviously then I do not have V4A.
[Magisk] ahrion:
[UPDATED] ViPER4Android FX (2.5.0.5)

v1.3:

- AudModLib v1.3 update push which includes the script addition to allow various audio mods working with SELinux Enforcing

- Remove (audmodlib)service.sh and replace with pos-fs-data(.d) audmodlib.sh, which should fix when root may be lost upon installing certain mods

- System install will now have the same script updates as the AudModLib v1.3 to allow to work in SELinux Enforcing

Download

Previous Changelogs (ViPER4Android FX):

v1.2:
- Added audmodlib.sh post-fs-data.d script
- Install script fixes
- post-fs-data.d script fixes
- Push AudModLib v1.2 hotfixes

v1.1:
- Updated to Audio Modification Library (Magisk) v1.1
This should fix the boot loop issues seen in only Magisk v11.6

V1.0:
- Initial release
- Smali edits to automatically enable storage permissions
- Audio Modification Library v1.0 is included
- Unified installer that will install mod for both Magisk and System
- Pixel support included
- Magisk Template v3 support
[Magisk] ahrion:
Are you running MagiskSU or SuperSU?
[Magisk] gettingerr:
Magisk.
[Magisk] Miasaya:
After trying to install it for many hours I just can't manage to install viper's drivers

It just say that BusyBox wasn't installed

I tried with the "normal" app and magisk 's one but it keeps saying the same thing
[Magisk] mentallo:
I have always found that the Busybox error happens when audio.conf is present in the vendor/etc folder. Add .bak to the end of the file.
[Magisk] davall:
For me it's the same.

Looked into /vendor/etc but there is only audio_effects.conf and audio_output_policy.conf but no audio.conf

It would be fine when viper Magisk module would install and operate with only Magisk busybox running? :(
[Magisk] ahrion:
So your ROM doesn't have a vendor audio effects then, correct? If not then copy it over from system/etc.

That may fix your prob.
[Magisk] davall:
Thanks for your hint. There was no audio_effects_vendor.conf in /vendor/etc neither in /system/etc

So I copied one from another Nexus 6P ROM to /vendor/etc. But I had no luck to get my Nexus 6P with ABCrom and ahrion's viper Magisk module running.

Maybe I've to start clean?

Nevertheless thanks for your work and help!
[Magisk] kantjer:
The modules are all running fine for me on ABC ROM on the 6P
[Magisk] davall:
Oh no! I'm using your build :)

So I've to start clean. Thanks!
[Magisk] kantjer:
one user reported that he had to rename vendor/etc/audio_effects_conf to .bak in TWRP before applying the modules after a clean flash

I can't confirm. I haven't done a clean flash in ages.
[Magisk] Miasaya:
I have no /vendor/etc in my system directory

So I tried to copy the files from system and it didn't work
[Magisk] shantam3108:
For stock music. I downloaded a track right now and played using play music
[Magisk] ahrion:
What music app? Do you have any other equalizer apps installed or music apps?
[Magisk] ahrion:
Have you gotten any v4a version to work at all?
[Magisk] shantam3108:
Yeah I was using on rr nougat 7.1.2 with no issues along with Dolby atmos lepro 3. Just today I flashed Oreo.

---------- Post added at 03:48 PM ---------- Previous post was at 03:48 PM ----------

Nope I use Spotify and Google play music

---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------

I am betting issue is with nos rom. Every Kenzo dev has problem with this rom. It would work with lineage OS

---------- Post added at 03:59 PM ---------- Previous post was at 03:49 PM ----------

One thing I just noticed my se Linux is permissive and I am unable to change it to enforcing. It will stay permissve
[Magisk] ahrion:
SELinux Permissive actually would make it work every time.

So the Atmos installs, the v4a installs, it just has issues processing? I'm betting money it is not the apps but deep_buffer related.
[Magisk] tpuserhp:
[MENTION=5357345]ahrion[/MENTION]. I installed v4afx_v2.0.zip on my OPO device running LOS 15.0. But v4a is not working. Looking at logcat, I found the following v4a messages:

10-02 16:53:40.247 I/ViPER4Android(1434): System booted.

10-02 16:53:40.248 E/ViPER4Android_Utils(1434): [Fatal] Can't load libV4AJniUtils.so

10-02 16:53:40.248 I/ViPER4Android(1434): Jni library status = false

Not sure whether the native libraries need to be recompiled for Oreo.

Thanks for your assistance.
[Magisk] shantam3108:
I flashed deep buffer.

When I don't flash deep buffer Dolby app opens but has no effect but when I flash deep buffer Dolby app crashes and doesn't open

---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------

Yes they install without any issues

---------- Post added at 02:27 AM ---------- Previous post was at 02:26 AM ----------

Library isn't installed for viper4android. Have you installed busybox. If not install busybox then again flash v4a

---------- Post added at 02:39 AM ---------- Previous post was at 02:27 AM ----------

I suppose u might be right. I had this issue once on nos 7.1.1 . And what I did was flash deep buffer remover and Dolby from arise thread and then it worked without any issues
[Magisk] shantam3108:
Logs
[Magisk] tpuserhp:
The script should install busybox if it is not already installed. I should not need to install it manually. Thanks.
[Magisk] DevALT:
Tasker bro it's life setenforce 0 for your apps you wanna use with selinux permissive than close the app setenforce 1

Best way to keep safety net and get permissive for certain app might be handy but it's flawless

Note safety net break if you listen music but close the app and it is back on track :)
[Magisk] shantam3108:
I know but it gave me error until I installed busy box myself. after installing busybox again I had no issues
[Magisk] tpuserhp:
I installed busybox module and rebooted to twrp to flash the v4a zip. Rebooted and still get the same error in logcat and v4a driver status.
[Magisk] DevALT:
Oh with further testing, when you do

su

setenforce 0

In a terminal after booting, safety net doesn't break even with selinux in permissive, so I created a task with Tasker to send "setenforce 0" command after each boot to get a working workaround for v4a, Dolby and other mod that requires selinux permissive without breaking safetynet...

I'm in permissive and I passed safetynet test :D
[Magisk] shantam3108:
Finally got v4a to process on redmi note 3. Busy box issues.

But Dolby wouldn't work. It's opening now but doesn't have any effect
[Magisk] ahrion:
The mods should already work with SELinux enforcing.
[Magisk] alexbelgium:
This mod works great with Magisk 14 on S5, thank you for providing it.

Would it be possible to do a version with Viper4android 2.3.4 ? I've always found it to sound better... (and I'm not the only one according to several threads on xda).
[Magisk] whalesplaho:
[MENTION=5357345]ahrion[/MENTION] yur github has AML/V4A 2.1.... is it safe to flash or wait for update here!

thanks for yur support always!
[Magisk] kwanthenewbie:
That's unstable build
[Magisk] whalesplaho:
just wanna be sure too...... ai buddy!
[Magisk] hexen02:
there is no way to set ON the processing on v4a. I set permissive ON, rename audioconfig, install another busybox from magiskmanager, etc. Please help me, its very stressful
[Magisk] gametimebrizzle:
Press play, check again.
[Magisk] hexen02:
what ? i already fixed this, i flashed these files using magisk manager:

- audiomodlibrary

- udbr

now v4a is processing :D
[Magisk] gametimebrizzle:
New version won't install. Old version removed.

Appears this is no longer a requirement. V4A working just fine without it.

I use viper4arise not viper4android ... semantics ... It's theme is different, that's all.

Edit: forgot to mention ^^^

HTC 10 (latest sec patch)

Magisk 14 (latest)

LeeDroid (latest)

ElementalX (latest)
[Magisk] gametimebrizzle:
TWRP fail
[Magisk] gametimebrizzle:
Processing will show "No" if there is no audio currently being processed... obviously (not inherently obvious however, considering the number of times this is asked).

"Press play" meant start some audio

"Check again" meant check the processing status in v4a while audio is playing
[Magisk] hexen02:
ah hahaha, i was playing something obviously (zplayer) xD
[Magisk] Rom:
Maybe corrupted dl ?
[Magisk] gametimebrizzle:
Another note, always try vanilla install first. No extra compatibility libraries.

Audio mod lib is for using MULTIPLE audio libraries​ simultaneously. It serves no real purpose if V4A works out of the box, irregardless of using multiple audio processing effects (ie HTC BoomSound + V4A works out of the box for me)

UDBR is a FIX, not a requirement. If V4A works for you out of the box...it isn't needed.

---------- Post added at 10:16 PM ---------- Previous post was at 10:11 PM ----------

I don't think that's it, but now that you mention that...why are these modules being distributed without their md5 automatically?

Of course, one can generate the hashes manually, but so can a couple lines of code in the installer script in Magisk.

Edit..of course, we'd need the reference hash first...

Maybe I'll make a pull request on the project
[Magisk] hexen02:
mm i dont know, but after installing the last one v4a works perfectly
[Magisk] gametimebrizzle:
Cool, then don't mess with it lol.

Just saying...from experience...if it works, leave it alone.

Unless you just like troubleshooting - which could very well be the case, considering this is an android development forum lol. I enjoy troubleshooting, but I'm a nerd and a half, so there is that.
[Magisk] Rom:
Its an choice of the Module's author.

MD5 or SHA-256 in Magisk Module install automate script checker ? We aren't in 2025 yet ;)

Try to dl zips again and compare them.
[Magisk] gametimebrizzle:
Lol, it wouldn't be THAT hard to generate MD5 hash for file integrity checking. The code already exists actually, Hash Droid and ZArchiver come to mind. Hash Droid is open source and both are in the play store. Yet another reason to support open source, laziness HAHA (on my part)

Security wouldn't be it's task, that's a completely different use case.

I do appreciate the tip, but I'm going to follow my own advice and leave well enough alone :silly:
[Magisk] shantam3108:
[MENTION=5357345]ahrion[/MENTION] pls look at this. Does it tell why Dolby isn't working
[Magisk] shantam3108:
[MENTION=5357345]ahrion[/MENTION] These are of v4a. All the files are installed and files are also their in sound fx folder

Pls have a look when u have time
[Magisk] ahrion:
If the mod was downloaded from the repo you're gonna get an install error. Git didn't push the changes to the repo. I'm fixing now.
[Magisk] batsup606:
viper4 nexus 7 2013

I installed this for my nexus 7 2013 and it doesn't work properly unless I set it to compatible mode, but that still isn't perfect because I have to reboot the device every time I want Viper to take effect. I am still in enforcing mode and I haven't been able to keep permissive permanently.

I'm running resurrection remix OS latest version (Android ver. 7.1.2). Also, Musicfx was already installed so I uninstalled it to help viper work.

Thanks for any help!
[Magisk] ahrion:
It might be a deep buffer problem. Try flashing the deep_buffer remover and it should fix.
[Magisk] mttrwlnd:
Is this compatible with the Osmosis BusyBox module for Magisk or do I need it installed on its own via the JRummy/Stericson managers? I've been trying to get Viper working on this Pixel XL for days. About the only thing I've yet to attempt is to try using a different BusyBox variant.
[Magisk] Zackptg5:
Osm0sis busybox works great with it
[Magisk] ahrion:
Yeah it works. It's the one I recommend.
[Magisk] Watanabe_You:
Thanks a lot. I had a game that FC when it detects Magisk, so I went unrooted. This file bypasses everything and works perfectly.
[Magisk] batsup606:
Yeah, I already did that but it did not work. I reinstalled viper, reinstalled busybox, applied the deep_buffer, but it still won't work under-enforcing mode. Only method that still works is when I set viper to compatible mode, unfortunately.
[Magisk] ahrion:
Which Magisk version do you have installed?

Something you have on your phone is conflicting with v4a. Compatible mode is specifically for v4a to be more compatible with other apps.
[Magisk] batsup606:
It says that I have version 14.0. It came pre-installed already when I flashed the resurrection rom.
[Magisk] mttrwlnd:
That's somewhat unfortunate then. As Osmosis BusyBox is the one I've been had installed during all these attempts.

The issue I'm having is that when I open the viper app, the driver install never sticks. After being granted SU permissions, it locks up for several seconds, then says the install was successful and to reboot. When I do so, however, and then go back into the app, it asks me to do it all over again.

This happens with the APK that I extract from your .zip, as well as the Materialized version.

Yours says "driver needs to be installed/updated"

Materialized specifically says it needs to be reinstalled.

What troubleshooting steps would you recommend for when this happens? Maybe you know something I haven't tried yet.
[Magisk] r80ies:
I flashed V2.0 in Magisk 14.2 running on an XL 8.0 and neither UI for V4A FX and Atmos install. I was going to extract and install .apk manually, but I thought I would check in here first. Any thoughts?
[Magisk] 24imelqui:
14.2 not yet supported. Wait for an update.
[Magisk] sushuguru:
Works fine on Andoird 7.1.2 and Magisk 14.2 here.
[Magisk] vaibhav1:
Hi

I installed v 2.0 app version 2.5.0.5 version but

Buy in app is show 2.5.0.4 ???

What's wrong...???
[Magisk] DerpleNerple2000:
Good news! It seems the latest GitHub source successfully installs V4A and it's driver upon flashing on the Pixel XL 8.0.0 (I think it was commit 0b8df7ac5d6069adc94ccf72373eb75f6f209eac that fixed the Pixel install). However, the driver will show abnormal status until SELinux is set to permissive (There is a magisk module that flashes fine with flashfire that will do this).
[Magisk] Lownita:
Greetings, does this mod survive a dirty flash of rom?
[Magisk] ahrion:
Natively yes, as long as there is add-on.d support. It also survives if it is installed via Magisk.