yashsingh1/xdaforums huggingface dataset:
[Magisk] asripath:
Viper legacy ie 4.4 works with enforcing

whereas Dolby would not work unless it's permissive.

With Dolby convolver's ie irs files,

i find no difference between viper vs dolby.

Remove dolby mod and try viper with below dolby convolvers

Dolby headphone room irs for headphones &

Dolby virtual speaker living room irs for speakers
[Magisk] Vinayakn73:
Strange I have viper legacy 4.4 but it doesn't work without permissive.

I mainly use Dolby for volume level option because it gives audio boost in video files. I know there is audio boost in viper too but I don't find it sufficient so I use both.

could you please explain the covolver parts. How to do it?
[Magisk] asripath:
Ref below threads for info on Convolver's/IRS

https://xdaforums.com/zenfone2/general/collection-convolver-samples-389-t3140299

https://xdaforums.com/showthread.php?t=2324454

https://xdaforums.com/showthread.php?t=2765331
[Magisk] Wolfcity:
Some users have more luck with an older legacy build of Viper.

Here are some versions from my android filehost:

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

Feel free to test them.
[Magisk] warrencoakley:
Use JDSP instead
[Magisk] Vinayakn73:
Ok I'll give it a try.
[Magisk] dimon222:
How to uninstall correctly? I did remove in magisk and rebooted, but v4a fx app is not gone, and I can't uninstall it (it crashes UI to home screen when I click uninstall). LOS 17.1

(UPD: worked through Titanium backup)
[Magisk] thomas140:
Huh? Magisk module updated? But I have already used the apk from the XDA lab. Is there any difference?
[Magisk] alvintimothyjr:
The magisk module was updated on 10/30/2020.
[Magisk] Andreas96:
New Update (Magisk-Module) works flawless even with J-DSP-Manager. But I must say I prefer the old layout where you can always change the profile and not only when your connected with your headphones etc. But overall thx for your great work :good:
[Magisk] Vinayakn73:
I don't see any update in magisk module library.
[Magisk] sixisixsix:
Why are audio mods rarely FOSS? I don't understand the rationale of close sourcing a piece of software when it's freeware.
[Magisk] rypz79:
Hi,

Using latest Magisk module v2.7.2.1

It downloaded 443 *.vdc presets to

/storage/emulated/0/ViPER4AndroidFX/DDC-orig

but doesn't recognize them (3rd button from the right presets is empty)

Renamed DDC-orig to DDC and it didn't help.

If those presets are not deprecated:

Where those files should be?

Why there is no redirection option?

TnxAloT
[Magisk] fiddi1973:
Put your Files in the Folder located in Internal/Android/Data/Viper :good:
[Magisk] rypz79:
at /storage/emulated/0/Android/data/com.pittvandewitt.viperfx/files/DDC

It still doesn't recognize them
[Magisk] :
Not working with latest magisk 13.3 on android 6.0.1
[Magisk] mrmcshagbag:
Delete

---------- Post added at 05:47 AM ---------- Previous post was at 05:45 AM ----------

Page 27 of this thread has the answer for you guys on how to get this viper to work on magisk 13.3.
[Magisk] Immortalis:
Been here, done that - doesn't work, status abnormal on OP3T.
[Magisk] ahrion:
I'm looking to update this today/this weekend.
[Magisk] quimbexa:
:highfive:
[Magisk] HampTheToker:
Mine fails to boot on beta 12 with franco's kernel and Selinux set to permissive. I've tried just about every Magisk viper module that I can find and they all cause bootloops.
[Magisk] ogsho:
This worked perfectly.. Viper working on magisk 13.3
[Magisk] aki_007:
Same here

Moto g5 plus

AEX 7.1.2
[Magisk] mrsweet1991:
I have the S6 Edge+ G928F and im running the Khongloi rom which runs Magisk 12 and some version of Viper4Android. Strangely enough i updated Magisk to version 13.1 which was the available update in Magisk and once rebooted Magisk then offered Magisk 13.3 update which ive installed and rebooted. Viper4Android hasnt broke! Not sure if its coincidental that somethings been updated but im now passing safetynet and running Android Pay and Viper is running fine.
[Magisk] Immortalis:
This finally worked for me on my OnePlus 3T after a factory reset and clean flash. I think that too many mod flashes cause some sort of incompatibility, but now i got it sorted and I'm happily running Viper and Dolby with AudioModLib.
[Magisk] ahrion:
If you check my git you'll see that I'm almost finished with all of my mod support for Magisk 13.5. It has some pretty awesome features. I'm now partnering with [MENTION=6037748]Zackptg5[/MENTION] who I trust to help bring our visions together.
[Magisk] quimbexa:
Damn I miss my EQs
[Magisk] ahrion:
Please welcome [MENTION=6037748]Zackptg5[/MENTION] as my official partner moving forward with focusing on our vision together making AudModLib and the Unity Installer with all of my supported audio modules.

I've been on a team with numerous individuals and I'll have to say he's probably the easiest to work with.
[Magisk] DaveedDB:
Zack is magisk audio mod problem solving king
[Magisk] ahrion:
Zack is probably the only one who understands the jibberjabber I speak and vice versa.
[Magisk] TopGun904:
Installed clean with AudModLib for Magisk 13.3. Doesn't work at all. Installed drivers, rebooted, nothing. Galaxy Note 4 (T-Mobile)
[Magisk] Zackptg5:
Update is in the works to fix magisk 13 issues
[Magisk] ahrion:
We're aiming for 13.5 release. It currently works on 13.5 beta but not 13.3 and below. Still getting bugs squared away.
[Magisk] exodius48:
[MENTION=5357345]ahrion[/MENTION] IRS broken on MIUI if v4a installed to /system/app or /system/priv-app/. V4a won't process IRS if v4a installed in /system. But it works if v4a installed in /data/app/
[Magisk] badtlc:
I'm on Magisk 13.3. Is there anyway to get Viper4Android installed at this point either via Magisk or TWRP?
[Magisk] muletas479:
I just updated from magisk, but in this last update the presets that I used before, for some reason now they don't work the same, I love the intense sound of the bass, and I am using the same headphones, but no matter how much I configure, the bass is very soft and instead the treble was maximized a lot, and the truth is I want to go back to the previous version but I can't find that version anywhere, could you help me solve this problem?
[Magisk] davejimson:
Is this compatible on realme 6 Pro with AOSP rom?
[Magisk] Wolfcity:
Android version?

You can give it a try up to android 9, sometimes android 10.

There's no guarantee. If it doesn't work try the actual version

2.7.2.1: https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651/post76154949

downloadable here: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

or use a similar app like JamesDSP:

https://xdaforums.com/android/apps-games/app-reformed-dsp-manager-t3607970/post72324847
[Magisk] kuro_n:
galaxy note 9

There are some apps that do not have viper4 enabled on the Galaxy Note9. what should I do? (It becomes effective by switching the screen recording)

google translate
[Magisk] Wolfcity:
You can try to install Android Compatibility Patch to enable Viper for things like YouTube or Spotify if they don't work out of the box.

Downloadable in the module section of Magisk Manager.
[Magisk] kuro_n:
Thank you, I could not solve it (it does not work with some apps (games))
[Magisk] Wolfcity:
Maybe give the actual Viper build or James DSP a try:

Actual version

2.7.2.1: https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651/post76154949

downloadable here: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

or use a similar app like JamesDSP:

https://xdaforums.com/android/apps-games/app-reformed-dsp-manager-t3607970/post72324847
[Magisk] muletas479:
sup bro, first of all, thank you very much for the work done and the contributions, I have a small question, I flashed the zip by magisk to convert the presets compatible with the new update, and it already recognizes them .. but they appear "empty" , at the time of loading, simply no change is applied, they are the same as used before but in this version it only recognizes the xml but not the configs
[Magisk] Valerio5000:
Hi everyone, i updated Viper4 FX on my Pocophone F1 to version 2.7.2.1 everything was fine except for it to work I had to enable the "Legacy mode" function otherwise it doesn't work. It's normal ?
[Magisk] coldgin_:
Yes, newest version is expected to work in legacy mode, so it's normal although nobody can clearly explain why...

Regards.
[Magisk] SleepingInMyCar:
On a head unit, 2.7.2.x removed all different options like speaker, headphone, etc. Is that intended behavior? Speaker doesn't have a lot of options compared to headphone.
[Magisk] Suavie103:
From my experience speaker always had the same options from headphones & bluetooth
[Magisk] Suavie103:
Great mood thanks for the work
[Magisk] Lughnasadh:
Headphone options will show up when you plug in headphone. Bluetooth options will show up when you connect your earbuds to bluetooth.

There are several options in headphone that are not applicable to speaker so speaker will naturally have less options.
[Magisk] Techguy777:
Hey everyone viper 2.3.4 is better than the new old driver 2.5.0.4 there blocking me in the new thread for viper2.7 apk because the dev doesnt have the permission to use the super driver quality driver. So im telling you im sure my account will deleted for no good reason. So try magiskv4.4 module and install the 2.3.4 super driver and try it its so much better i hate 2.5.0.4 because its strachy as hell.
[Magisk] boozlepuzzle:
The app used to work fine, I was very happy with it, then I updated and everything went to hell, it doesn't work anymore not even in legacy mode, now it's like this every time:

Is there any way to download the previous version? I can't find it anywhere
[Magisk] Techguy777:
i guess I dont have it I thought I did
[Magisk] Suavie103:
What version of Android are you on?
[Magisk] u777:
I absolutely agree with you. V4A 2.3.4.0 super driver is the best. V4a 2.5.0.4 and 2.7.1.0 is totally garbage. I am desperately looking for how to install v4a 2.3.4.0 to Android 10 Q. You said "try magisk v4.4 module and install the 2.3.4 super driver". what that mean? v4.4? magisk v4.4 and magisk manager v4.4 both are incompatible with Android 10. what 4.4 module? how did you install v4a 2.3.4.0 super driver on android 10 or 11 in detail?

V4a 2.7.1.0 developer said "If you already know which original v4a you want to use, just add 'old' for 2.3.4.0, 'mid' for 2.4.0.1, 'new' for 2.5.0.5, or 'mat' for material to the zipname prior to flashing." But Although I changed the file name v4afx_v2.7.2.1.zip to v4afx_v2.7.2.1_old.zip, it was installed as 2.7.1.0. How can I install 2.3.4.0 super driver?
[Magisk] BHUSHAN7988:
Use this zip, flash in magisk then use volume keys to choose old. It will ask at first for old version.

Best part is old v4a don't trigger play protect.
[Magisk] BHUSHAN7988:
Old super drivers can't be started back like the new 25 one by exiting and opening again any solution for that please tell. I love the old driver
[Magisk] maxkolonko123:
After updating magisk to ver 21.2 viper stopped working even after updating to new version (abnormal status, unsupported etc), reverting magisk to 20.4 ver, viper works fine again anyone have same problem?
[Magisk] u777:
I installed this file that you gave me. And I got stock in driver install fail error loop. It says "you need to install v4a driver. install now?" I clicked "yes". and it says "driver installed. reboot!". and after reeboot, It says "you need to install v4a driver. install now?".., repeat...repeat... unlimited repeat... I can't install 2.3.4.0 super driver on Android 10 Q. Selinux enforcind mode or permissive mode - fail. Audio modification library 4.0 or 2.5 - all fail. I definitely rooted phone. Although I installed busybox everywhere - v4a 2.3.4.0 super driver installing fail. when installing, some sort of workaround blabla yes - fail or no - all fail. Did you success installing v4a 2.3.4.0 super driver on Android 10 with this file? Is it possible? How did you install?
[Magisk] BHUSHAN7988:
https://xdaforums.com/t/viper4android-fx-legacy-xhifi-unity-deprecated.3577058/post-81531089

Try this work around make sure to rename the file I attached to "selinux.a"
[Magisk] BHUSHAN7988:
thanks man this worked for me...oh how i missed legacy!!!!:D:D

---------- Post added at 03:05 AM ---------- Previous post was at 02:26 AM ----------

[/QUOTE]

the only thing is can't save or load presets. no storage access

[/QUOTE]

Did you figure out how to save profiles?
[Magisk] Techguy777:
Yes android 10 is difficult

Step 1 requires you have a permissive kernel. Samsung will not allow that on stock rooted.

Step 2 busybox magisk module

Step 3 selinux app and set it to permissive.

Step 4 Install viper 4.4 magisk try to use 2.3.4 to user app and than you need the actual viper 2.3.4 apk and after rebooting you install it and give it storage permission than set it to lock bluetooth effect. Ui advanced.

You might need to flash the viper 4.4 again on top of the app to get it to work.

That should do it
[Magisk] BHUSHAN7988:
Why the user app, does making it user app solve not saving of profiles.

And wanna ask one more thing in 2.5.0.5 there was a exit button which I used to exit app and launch again to start processing again when it stopped due to some interuptions

Any way to do the above in 2.3.4.0
[Magisk] u777:
Thank you BHUSHAN7988, Techguy777 for nice help. You two helped me a lot.

I have succeded in installing v4a 2.3.4.0 super driver on android 10 Q.

The key was to get rid of the audio modification library. After removing the audio modificarion livrary, v4a 2.3.4.0 was installed well.

The two apps seem to collide each other, if it sounds weird, this is a my real conclusion.

(I'm sorry, but /data/adb/service.d/selinix.a method didn't work. It seems that the purpose of the method was to make selinux permissive, but my phone was already permissive. And even if I put selinux.a file in that folder, the v4a 2.3.4.0 installation failed. That's no matter. I really appreciate you for your kindness help ^^)

And another key was the file 'v4a legacy v4.4 module' which BHUSHAN7988 gave me, as Techguy777 has said. I could not install other files other than that file v4a legacy v4.4 module.

To load and save preset profiles. I had to install the v4a legacy v4.4 module as user app. If Techguy777, BHUSHAN7988 hadn't told me that tip, I wouldn't know and I thought it's impossible and gave up. I was giving up thinking that to load and save presets wasn't possible at first.

If it was installed as system app, to load and save preaet profiles could not be executed.

Techguy777

I didn't have to install real apk v4a 2.3.4.0 file over zip module v4a 2.3.4.0 legacy v4.4.

The zip module v4a 2.3.4.0 legacy v4.4 only one file one time. It was enough to install it once.

Thank you ^^.

And finally...

I'm a little bit disapointed at sound quallity v4a 2.3.4.0 super driver on android 10 Q.

In oreo 8.0, v4a 2.3.4.0 sounded so exellent, but apparently, despite installing the 2.3.4.0 super driver, the sound in the 10 Q is not as satisfactory as in oreo. I do not know if it is because it is a different phone by changing the phone or because the operating system is changed from oreo 8.0 to 10 Q. When the sound source is few at the beginning of song, the sound quality is good, but the sound deteriorates bad(weaker) when you go to the climax with many sound sources.

Of course, v4a 2.3.4.0 super driver sound is much better than the v4a 2.7.1.0 on android 10.

My phone system:

magisk 20.4

android 10 Q.

rooted

busybox installed

selinux permissive.
[Magisk] BHUSHAN7988:
What I want is when the processing stops sometime how do you start it.

Do you reboot?

In 2.5.0.5 there was a exit option which was helpful to relaunch app and start processing
[Magisk] u777:
I have not experienced a processing stop error at all with v4a.

Did v4a stop sometimes?

I don't know what symtoms you are talking about, but if in that case I think there is way to reboot

or cleanig cache data at system app setting

or wipe cache at TWRP

or installing audio compatibility patch sort of things module in magiak manager

or delete and reinstall v4a... etc...you would try, I guess.

I hope somebody else can help you.
[Magisk] meetXD:
Yeah abnormal status and not working for me too - and the worst part of it is that the zip doesn't contain the APK so I can't use the old installer to downgrade!
[Magisk] sas46:
Same problem here, AML did nothing for me, still abnormal
[Magisk] sas46:
Latest Magisk 21.3 (21300) and Busybox 1.31.1 solved the problems
[Magisk] Wolfcity:
Just as an addition: Latest Canary breaks v4a (at least legacy) functionality too. Magisk stable 21.3 should work.
[Magisk] GorfDroid:
Can confirm, latest magisk versions break this. Can't install 20.4 on Android 11.
[Magisk] GeneFitz23:
Magisk 21.4 seems to have stopped v4a from installing properly. Driver status shows its not enabled and abnormal.
[Magisk] Wolfcity:
Not new (if you read the last posts right above yours). Stay on 20.4 if you have no other problems.

No need to update magisk if it's working.
[Magisk] GeneFitz23:
Thanks. I was just confirming as well.
[Magisk] Essentrix:
Slight digression - I've stayed on 20.4 as suggested to keep v4a functional. Anyone know how to patch a file through magisk now without updating if to latest?
[Magisk] Wolfcity:
What kind of file? Are you talking about boot.img or similar like recovery.img? Should work the same way, patching these files isn't a new function.

Sorry if I don't get your point.
[Magisk] Essentrix:
I want to pre patch TWRP. But before I can magisk wants to update to latest version. I of course don't want to update...
[Magisk] TaimoorBoss:
help its not working, im on poco x3 global with resurrection remix rom android 10 i flashed it through magisk intsalled drivers and restart.
[Magisk] Wolfcity:
Why magisk needs to update before you're able to pre-patch TWRP? Another question: What do you want to patch in the official TWRP?

Sorry, but it needs some more information (maybe I'm just to dumb to understand it).

What magisk version? Everything above 20.4 seem to cause problems with legacy viper and maybe with the actual builds too.

Which Viper version are you trying to flash?
[Magisk] TaimoorBoss:
Latest magisk with latest viper 2.7
[Magisk] vibrantliker:
So who's got Viper working on android 11?
[Magisk] vibrantliker:
Thanks, what version of Magisk and V4A are you using?
[Magisk] Lughnasadh:
Working on Android 11/Pixel 4 XL/VIPER4Android FX Legacy/Magisk 22.0
[Magisk] vibrantliker:
Interesting, I read in a few places that anything newer than Magisk 20.4 breaks viper. Maybe it's because you're using the legacy version?
[Magisk] Lughnasadh:
Yeah, Legacy version works but I can't get the newer version to work on Magisk 22.0. I also use JamesDSP alongside it and only use V4A for a couple of settings. Because of scoped storage I can't use Convolver with the Legacy version so I use JamesDSP for that.
[Magisk] GorfDroid:
legacy not working on lineage 18 with magisk 22
[Magisk] OrigiNox:
Finally, got v4a (legacy mode enabled) working on my Pixel 4 XL with android 11/magisk 22

Just install latest app from v4a telegram channel (should be working with magisk module as well), install driver, reboot and then follow the solution from _mysiak_

https://xdaforums.com/t/app-all-root-solutions-6-0-viper4android-fx-2-7.3774651/post-84121895

Tested on Pixel 4 XL, PixelDust 11, Magisk 22.0, and V4A 2.7.2.1
[Magisk] Xosrov:
For people having the "abnormal" and "not enabled" here's a Fix i found that works on my xiaomi.eu A11 rom. It might be worth testing on other roms too.

The problem seems to be that magisk/viper can't patch the selinux policy when it's set to enforcing.
[Magisk] mehediceps:
Thanks a lot man! Huge respect. Follow your instructions and it works like charm in Samsung M21 One UI 3.0
[Magisk] QkiZMR:
Magisk 22.1, Viper4Audio 2.5.0.5 works without any issues. No workarounds have been made. Just install and works.
[Magisk] BHUSHAN7988:
Just make sure the app is installed as user app.

Then when it stops processing just force stop and start it.
[Magisk] Eric_Nobrega:
V4A is running on Android 11, the only problem is the audio limitation on Bluetooth devices.

Legacy mode works but "Convolver" does not work on Bluetooth devices.

Please help me fix this bug. 😁🙏
[Magisk] andrey bobylev:
Я сегодня с этой проблемой столкнулся , I ran into this problem today, I cannot find the reason. Presumably I did not install RIRU correctly myself могу причину найти. Предположительно я сам не правильно поставил RIRU.
[Magisk] GorfDroid:
So is there any solution to get this working in Android 11, Lineage 18.1?
[Magisk] nitinvaid:
Does viper works in Samsung S21 Ultra exynos version? what are the steps t install it
[Magisk] Wesley Souza 05:
Everytime I try to install from bootloop does anyone know how to fix it?
[Magisk] Wesley Souza 05:
It bootloops again, selinux was in permissive, installs everything correctly when installing the drivers and restarts it bootloops 😞

https://www.google.com/search?hl=pt...&ampcct=4472&source=com.teslacoilsw.launcher#
[Magisk] Wolfcity:
Your post doesn't really help. The link goes to a Google search (see screenshot).

Also there are no information about

- your device

- Android version (10/11?)

- Root method/ magisk version?

- Viper build (apk?/ magisk module?)

- maybe a log?
[Magisk] Misterio7Gamer:
Hi! I installed the rootless method, and it works, the status is enabled, but the processing is "NO", everything should be installed fine, but no effect is applied in the end, even if NEON is enabled.

Anyone have an idea of what can I do to make the processing work? is just that, some random times it works for a few minutes, then stop working again with the same apps.

I'm not using any other equalizer.

I have the notification of viper that say "Processing (headphones)", but it's not processing in the status check.

I tried it in a lot of apps like Youtube, Stellio, the miui music preinstalled app etc.

I already use viper with my phone rooted time ago, but this time I don't want to root my device, so it means it's compatible with the driver, my device is a Redmi Note 7.
[Magisk] Wesley Souza 05:
Sorry the link was wrong, my phone is a galaxy A8 2018 with custom rom TreeUI Android 11, I'm using the latest version of magisk 23.0, the installation happens normally but when I install the drivers and I asked to restart it from the bootloop and it keeps appearing in the corner blocked OEM screen, this does not only happen with viper4android it also happens with dolby digital and other sound modules even with permissive selinux!!
[Magisk] estemanito:
Hi

I installed V4A FX Legacy 15.10 on Magisk 20.04 and i puted some irs files into the Kernel directory, but Viper tell me that he dont find any file inside.

Same thing with DCC files, i put them inside the DCC directory but he dont find them.

I tried with the last Magisk version 23 too and i get the same.

I tried to format my Data partition then reinstall all the stuff but still the same problem.

Im on a LG V50 with Open Android 10

Need help, any idea please...?

Thanks
[Magisk] Gueste4555:
does the module support Android q (11)?
[Magisk] bohemist:
Magisk module VIPER4AndroidFX v2.7.2.1 works perfectly on my OP6 with the latest OOS 11 based on Android 11.

Make sure to install additional modules;

1. Audio Compatibility Patch, and;

2. Audio Modification Library

Once installed and it is not working, try switching to Legacy Mode. You can find this switch in the VIPER4AndroidFX settings.

Also, check the other thread: https://xdaforums.com/t/app-all-root-solutions-6-0-viper4android-fx-2-7.3774651/
[Magisk] scaniathe:
On xperia xz2 with lineage 18.1 working fine. Magisk 23, ViPER4AndroidFX, busybox, selinux permissive...
[Magisk] 3mel:
I'm confused, magisk info points to this thread which says deprecated but also shows the latest version is from this month, 9/9/2021.

still got a download failed on the apk.

what to do ?

I've found a thread of edits I want to try as a solution to repeated failures.

https://xdaforums.com/t/mod-viper4android-miui-12-magisk-21-1.4203489/