Database Develop

ViPER4Android FX Legacy/XHiFI [Unity][Deprecated]

Deprecated - Use the New ViPER4Android v2.7:
GO TO THE THREAD LINKED ABOVE. You don't need to flash any zips. Just install it as a regular apk, allow it to install the drivers, and you're good to go.
For magisk users: I made a zip on the repo that includes the original vdc's and my profile converter (will convert your old profiles to the new and better format).
For rootless users: I made a zip to install drivers and such
Zips can be found here
ALL SUPPORT QUESTIONS FOR 2.7 SHOULD BE AT THE THREAD ABOVE.
This is ViPER4Android FX and Xhifi Unity installers
These installers utilize my Unified installer that can install on Magisk OR System if Magisk is not detected (with Pixel support).
Credits of Originality:
- @zhuhang (Official Thread)
- @Osm0sis
- Viper's Audio (Official blog)
- @ViPER520
- @Team_DeWitt
Special Instructions:
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.
If you already know if you want it installed as a user or system app, add "uapp" for user app or "sapp" to system app to zipname.
If you already know if you want to apply the libstdc++.so lib workaround, add "lib" or "nlib" to zipname (note that there are some devices that are already known to require it and so they'll apply workaround regardless of choice)
If you already know if your device/rom requires the v4a open/close/fc audioserver workaround, add "ocw" to zipname. Otherwise, add "nocw" to zipname
To skip volkeys (if your device isn't compatible with them), add "novk" to the zipname. Note that if you don't specify the above, defaults will be applied which are: sapp, new
Make sure there are no spaces in the zipname
Audio Mod Troubleshooting Guide
Downloads
XDA:DevDB Information
ViPER4Android FX Legacy/XHiFI [Unity], App for the XDA Community Apps
Contributors
ahrion, Zackptg5
Version Information
Status: Stable
Current Stable Version: v4.4
Stable Release Date: 2019-08-11
Created 2019-01-18
Last Updated 2020-01-01

great!

Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.

kartikb said:
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
Click to expand...
Click to collapse
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.

ahrion said:
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
Click to expand...
Click to collapse
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..

kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Magisk limitation. @topjohnwu is always improving magisk. I do recommend may e trying another kernel for your device which may help compatibility.

Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...

Didgeridoohan said:
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
Click to expand...
Click to collapse
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.

ahrion said:
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
Click to expand...
Click to collapse
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.

kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread

Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
You are literally advertising your mods in everyone's threads. Stop this and make your own thread.
This is a magisk forum, not a system mod forum.

Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
I will remove it with next release. Thank you man. This **** only started happening with 11.6. this was the reason Atmos was boot looping as well so I removed system.prop in Atmos.
Can you do me a favor and remove a few lines to see if it's just the specific lines? I think that certain lines don't play nice with your phone.
Remove the first part, low power audio tweaks, reboot and see if it works. If it doesn't then that's the culprit. If not then remove the first two on the other audio tweaks.

Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.

kartikb said:
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
Click to expand...
Click to collapse
Enable permissive.
Turn off audiofx

ahrion said:
Enable permissive.
Turn off audiofx
Click to expand...
Click to collapse
I'll try again when I get a chance to. Thanks for the suggestion.

[UPDATED] ViPER4Android FX <2.5.0.5>
v1.1:
- Updated to Audio Modification Library (Magisk) v1.1
This should fix the boot loop issues seen in only Magisk v11.6
Download: Link - Mirror
Previous Changelogs (Unified installer):
HTML:
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

kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
Try 1.1.

ahrion said:
Try 1.1.
Click to expand...
Click to collapse
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.

kartikb said:
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
Click to expand...
Click to collapse
Flash my deep buffer remover. Look in the magisk forum.

ahrion said:
Flash my deep buffer remover. Look in the magisk forum.
Click to expand...
Click to collapse
Thanks, it all finally works on my Nexus 6P. Now to try on my OnePlus 3..

Viper4Arise Install Guide

Hi everyone, I was wondering if there is a composite install guide for Oneplus 3T devices for all ROM's for Viper4Arise. I really love that Mod. I am currently on RR 5.3.8 and I find that the installation via Magisk is very buggy and leads to FC almost all apps and the phone freezes after a few minutes of installation. I had no such issues installing Viper4Android though. I am a noob so find the current install method on the thread very complicated. Is there a zip file which makes it easier regardless of ROM or if there is anything specific to RR roms which can be used?

Don't know of any such guide, but it's a good idea to have one (although the request for a guide "for all ROMs" may be a tall order).
I was reading through the following sounds mods thread yesterday, and it was confusing as heck, and seems like some folks have varying results: https://forum.xda-developers.com/oneplus-3t/help/best-sound-mods-t3555160
I can't speak to RR, but what I can say, is that I easily installed ARISE on stock rooted ROM (rooted with SuperSU) with one of the AROMA versions; and ARISE works flawlessly. Did not need SELinux permissive or Busybox. I also skipped all of the options in the AROMA installer, since honestly, I don't know what most of them are, and they aren't critical for the "core" ARISE experience.

Happy to report that I was able to fix this. What I did was a little bit of sacrifice but I think I care about sound quality on my phone more than anything else. What I did was replace magisksu with supersu. While the convenience of magisk would be missed, I am happy that now I have arise numbers Module with dolby atmos installed. :good:

cluttered_butter said:
Happy to report that I was able to fix this. What I did was a little bit of sacrifice but I think I care about sound quality on my phone more than anything else. What I did was replace magisksu with supersu. While the convenience of magisk would be missed, I am happy that now I have arise numbers Module with dolby atmos installed. :good:
Click to expand...
Click to collapse
Did you just flash supersu over magisk or was the installation more involved? I was thinking of testing this but wasn't sure if it would work. My plan currently is:
1) Remove all magisk modules
2) Flash SuperSU from Recovery and reboot
3) Reapply magisk modules (V4A Included)
4) Reboot
Was this essentially all you did on your end?

I have tried what you are about to embark on since if I had it my way, I would stick to magisk. Here's what I did, I rooted my phone with SuperSU after uninstalling magisk completely (remove all modules and uninstall using the magisk uninstall zip), I downloaded the magisk manager and tried to rely on the supersu for root access. Magisk did say the phone was rooted after seeking rights from supersu, but eventually just hung the system. Post which it was kind of futile coz it just won't work. If you flash the magisk zip you will cause bigger issues since supersu and magisk would conflict for libraries and that's not good either.
Feel free to try it anyway and see if you get somewhere. Take a backup of course:fingers-crossed:

For me arise works flawless on rr with magisk. And i didnt need any magisk module or extra zip. Only flashed simple modular installer.

cluttered_butter said:
If you flash the magisk zip you will cause bigger issues since supersu and magisk would conflict for libraries and that's not good either.
Click to expand...
Click to collapse
I just wanted to chime in and say that this information isn't correct. Magisk has been designed to work with SuperSU (systemless) as well as MagiskSU.

Instructions
nadejo said:
For me arise works flawless on rr with magisk. And i didnt need any magisk module or extra zip. Only flashed simple modular installer.
Click to expand...
Click to collapse
Can you share the link for installer or instructions for the specific arise installation you did? It'll help me try the same.

Didgeridoohan said:
I just wanted to chime in and say that this information isn't correct. Magisk has been designed to work with SuperSU (systemless) as well as MagiskSU.
Click to expand...
Click to collapse
Was just sharing my experience. Didn't mean to say that my information was correct.

cluttered_butter said:
Can you share the link for installer or instructions for the specific arise installation you did? It'll help me try the same.
Click to expand...
Click to collapse
1.First put this (my custom prop with dolby atmos and viper arise you can further customize it if you want)
https://drive.google.com/open?id=0B5cs9MEMO2MrNGo3eGJJVFdxemc
On sd card (dont rename it and dont put it in any folder) it must be at same place where all your folders are. Like downloads... Pictures...
2.Then go to rr settings and switch to selinux permissive
3.Now flash this file in twrp https://www.androidfilehost.com/?fid=529152257862724645
And reboot.
Have fun

Will give it a shot tonight! Thank you so much!

So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.

Worked like a charm ??thanks so much. Don't know what I was doing wrong all this time

trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me

trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me know

cluttered_butter said:
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me know
Click to expand...
Click to collapse
For my IRS profile I'm using DTS Mode Z128k. I had tried dolby pro logic 2/3 but the way it boosted the volume was just too much. DTS Mode has worked out well so far. What about you?

trentonite said:
For my IRS profile I'm using DTS Mode Z128k. I had tried dolby pro logic 2/3 but the way it boosted the volume was just too much. DTS Mode has worked out well so far. What about you?
Click to expand...
Click to collapse
I typically stick to dolby irs. But the main difference in sound is made by the profiles in viper4arise. I love the Audiophile X profile. Amazing fidelity on rock songs.

trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
Is it possible to flash after the procedure above -Viper4Arise?

Hi guys, I just bought my 3T, rooted and installed TWRP. Now I`m trying to install V4Arise, but with no success. I tried Freedom ROM... In this ROM V4Arise works fine, but the cell battery drains too fast. I returned to stock ROM... But I dont know how to install V4Arise in stock ROM. Could you help me?

Viper4Android on OOS 4.1.6

Hello,
I was wondering if anyone has successfully used V4A app on the Magisk rooted OOS 4.1.6?
I've successfully installed busybox, set the SELinux to "permissive", installed the latest V4A for Nougat with the latest drivers, turned Oneplus "Audioswitch" off, but still it doesn't seem to work.
As you can see from the screenshot, it all seems in order, but the "Processing" status is always set to "no".
What am I doing wrong?

I'm using this Magisk module on Magisk v13.2: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Works great, but since it hasn't been updated for Magisk v13+ yet it needs a couple of modifications: https://forum.xda-developers.com/showpost.php?p=72976454&postcount=316
The permissions I mention is for the scripts in post-fs-data.d and service.d and they need to be set to 755 (rwxr-xr-x).
No need for either busybox or permissive SELinux or any other alterations for that matter... YMMV, but this works perfectly for me on OOS 4.1.6.

Didgeridoohan said:
I'm using this Magisk module on Magisk v13.2: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Works great, but since it hasn't been updated for Magisk v13+ yet it needs a couple of modifications: https://forum.xda-developers.com/showpost.php?p=72976454&postcount=316
The permissions I mention is for the scripts in post-fs-data.d and service.d and they need to be set to 755 (rwxr-xr-x).
No need for either busybox or permissive SELinux or any other alterations for that matter... YMMV, but this works perfectly for me on OOS 4.1.6.
Click to expand...
Click to collapse
Thank for a great idea, but I've stumbled on an another bug while trying to download Viper4A as a Magisk module to follow your solution. It seems that the new Magisk crashes halfway when i download modules from the repo, which is really strange... I've looked it up everywhere, re-flashed Magisk after uninstalling it, re-installed Magisk Manager - but no luck.
UPD: clicked your link, installed in TWRP All works!

hrsa said:
Hello,
I was wondering if anyone has successfully used V4A app on the Magisk rooted OOS 4.1.6?
I've successfully installed busybox, set the SELinux to "permissive", installed the latest V4A for Nougat with the latest drivers, turned Oneplus "Audioswitch" off, but still it doesn't seem to work.
As you can see from the screenshot, it all seems in order, but the "Processing" status is always set to "no".
What am I doing wrong?
Click to expand...
Click to collapse
https://www.google.co.in/amp/s/www.gizdev.com/amp/viper4android-on-android-7-0-arise-sound-systems/
Try viper for arise ..follow the instructions, flash through TWRP..
Tried this when I was on Resurrection remix and freedom os..now on lineage 14.1..works really well in all roms..

hrsa said:
Hello,
I was wondering if anyone has successfully used V4A app on the Magisk rooted OOS 4.1.6?
I've successfully installed busybox, set the SELinux to "permissive", installed the latest V4A for Nougat with the latest drivers, turned Oneplus "Audioswitch" off, but still it doesn't seem to work.
As you can see from the screenshot, it all seems in order, but the "Processing" status is always set to "no".
What am I doing wrong?
Click to expand...
Click to collapse
:good:

[Guide][Magisk]Viper4Android on OOS Oreo with Magisk. (Easy Method)

Hello all ,
Update August 7th 2018.
Wirh recent versions of v4a , theres no need to use this method unless you tried the latest official v4a magisk module or zip and it didn't work, current v4a magaik module works perfectly with latest 5.0.4 stable rom and all betas from oos, and moat if not all 8.1 custom roms
The following is not necessary as of August 7th 2018, unless you tried official zip or module and faced issues:
a lot are asking and searching for a way to make V4A work on OOS Oreo, sadly so far most posible ways either require a lot work or setting Linux to permissive wich breaks saftynet.
the bad news is this method also Sets SELinun to Permissive but it's simulated through Magisk so it doesn't break SafetyNet...
Method:
1- download and install busybox (make sure it's installed) i personally use a pro version, some of the ones on playstore wont install so try until you find a working one.
2- Update , using the latest V4A 2.5+ version by ahrion you don't need to use Magisk SELinux Permissive Scrip because he added to his module a detection script that will detect OOS Oreo and set permissive automatically
Download and flash LatestViPER4Android FX 2.5.0.5 [Unity/AML] by @ahrion
3-reboot and have fun
if the above doesn't work
2a- download and install Magisk SELinux Permissive Script module v1.1 (all thanks to @Jman420 ) and reboot.
3a- download ViPER4Android FX 2.3.4.0 (Super High Quality) v2.1
4a- install V4A module downloaded in the past step then reboot.
5a- now V4A should be perfectly working...and It Passes SafetyNet
Screens Attached.

Excellent job, works like a charm with oos 5.
Big thx!

is bluetooth also working on this method?

I have tried your method but V4A is still not working. Thanks anyway

NOSTALGIA said:
is bluetooth also working on this method?
Click to expand...
Click to collapse
yes, it's specifically for Bluetooth
Soerdroid said:
I have tried your method but V4A is still not working. Thanks anyway
Click to expand...
Click to collapse
make sure Busybox app is installed and open it and inside it click install, the app itself has to install somethings... there's no reason for it not to work, if you've done that and it's not working please share a screen of v4a driver status while playing music .

It didn't worked for me either

Works fine!

weriwd said:
It didn't worked for me either
Click to expand...
Click to collapse
Working fine here, after following the instructions.
Be sure to Enable ViperFX in the UI (Master Power) as well.

Gamm86 said:
Working fine here, after following the instructions.
Be sure to Enable ViperFX in the UI (Master Power) as well.
Click to expand...
Click to collapse
Well for me the drivers just wont install. Which app are you using for busybox? I think this is causing the problem.

weriwd said:
Well for me the drivers just wont install. Which app are you using for busybox? I think this is causing the problem.
Click to expand...
Click to collapse
Busybox for Android by JRummy Apps

Gamm86 said:
Busybox for Android by JRummy Apps
Click to expand...
Click to collapse
Nope not working again . Drivers wont install for some reason.

weriwd said:
Nope not working again . Drivers wont install for some reason.
Click to expand...
Click to collapse
Have you correctly installed the zip's through Magisk modules?

Gamm86 said:
Have you correctly installed the zip's through Magisk modules?
Click to expand...
Click to collapse
Well I am just flashing them through Magisk what could I mess up

weriwd said:
Well I am just flashing them through Magisk what could I mess up
Click to expand...
Click to collapse
You could have tried flashing them in recovery.
Anyway, I'm sorry to inform you I'm out of ideas.

Gamm86 said:
You could have tried flashing them in recovery.
Anyway, I'm sorry to inform you I'm out of ideas.
Click to expand...
Click to collapse
It's not a big deal. I will wait for stable release. Thank you for the help anyways.

I flash viper4arise (Deuteronomy 2.4), it contains viper4android 2.5.0.5. To get it to work with selinux enforcing I used to install the magisk module Allow audio server on Nougat (https://forum.xda-developers.com/on...sk-modules-oneplus-3t-t3548446/post70819460). On Oreo I doesn't work anymore. Now I set selinux to permissive in developer settings in viper. It'll last till you reboot, then selinux is enforcing again.
Link to viper4arise: https://forum.xda-developers.com/an...stems-auditory-research-t3379709/post71959306
Downloadlink: https://androidfilehost.com/?w=files&flid=146718

weriwd said:
Nope not working again . Drivers wont install for some reason.
Click to expand...
Click to collapse
Sadly jrummy app is the one that works for me too, i use the pro version...
Make sure it has root access , and maybe try to change the installation directory
You can try the buaybox module fromt he following thread
https://forum.xda-developers.com/oneplus-3t/themes/magisk-magisk-modules-oneplus-3t-t3548446
You may also want to check the following
http://support.jrummyapps.com/topic/magisk

This works on OP3 with Magisk and is 2.5.0.5...
Install the APK separately.

skymera said:
This works on OP3 with Magisk and is 2.5.0.5...
Install the APK separately.
Click to expand...
Click to collapse
Can you also upload the apk? There are a lot of apks with ads.. Thank you

theduke7 said:
Hello all ,
a lot are asking and searching for a way to make V4A work on OOS Oreo, sadly so far most posible ways either require a lot work or setting Linux to permissive wich breaks saftynet.
the bad news is this method also Sets SELinun to Permissive but it's simulated through Magisk so it doesn't break SafetyNet...
Method:
1- download and install busybox (make sure it's installed) i personally use a pro version, some of the ones on playstore wont install so try until you find a working one.
2- download and install Magisk SELinux Permissive Script module v1.1 (all thanks to @Jman420 )
3-reboot
4- download ViPER4Android FX 2.3.4.0 (Super High Quality) v2.1 (i couldn't get the 2.5.0.5 version to work, if someone has a module of that version that works please mention it and i'll add it here as well)
5- install V4A module downloaded in the past step then reboot.
6- now V4A should be perfectly working...and It Passes SafetyNet
Screens Attached.
Click to expand...
Click to collapse
Вот кажется работает
https://drive.google.com/file/d/1Q3uzrZLpn9kK9O_YKA4GJ31YxO5gQt0X/view?usp=drivesdk

Trying to install Viper4Android, driver install fails (via magisk)

I've tried installing the driver multiple times and can't seem to make it work at all. The only method I've not been able to accomplish is renaming audio_effects.conf to audio_effects.conf.bak as has been recommended for other phones. For some reason, this file will not rename.
it would seem the file is set to be unwritable (I'm not familiar with linux permissions like this, so maybe that can be fixed somehow?). At the very least, Solid Explorer isn't able to do the job, and can't change the rw perms either, as the operation just fails. (I have got selinuxmodechanger changed to permissive and after reboot, but no change here either)
Any other ideas?

Well, for anyone else wanting to know how to make this work, follow this guide here: https://thedroidarena.com/install-viper4android-android-10-q/
Don't use the magisk module for V4A, it doesn't work.
Works great for me now!

I'm using it it works perfect but you have to use the new version not the older one
Sent from my ASUS_I003DD using Tapatalk

Matakor said:
Well, for anyone else wanting to know how to make this work, follow this guide here: https://thedroidarena.com/install-viper4android-android-10-q/
Don't use the magisk module for V4A, it doesn't work.
Works great for me now!
Click to expand...
Click to collapse
I followed the instructions above, but it doesn't work.

Matakor said:
Well, for anyone else wanting to know how to make this work, follow this guide here: https://thedroidarena.com/install-viper4android-android-10-q/
Don't use the magisk module for V4A, it doesn't work.
Works great for me now!
Click to expand...
Click to collapse
Do you still have that apk lying around? XDA Labs does not appear to be working ATM.

bencozzy said:
JamesDSP works
Click to expand...
Click to collapse
I saw that, didn't really know what it did. I'll check it out.

Nothing in JamesDSP is doing anything for me on Speakers, Headphones, or Bluetooth. I think that this may beacause of my failed install of V4A rootless (might work if I had the APK?). Any ideas if this is the problem? If It is, do you know how I might uninstall V4A?

If rooted, try installing latest V4A directly from here (https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx) rather than via Magisk.
I prefer older V4A versions, having tried above.
My preferred V4A is 2.5.0.5 (found in App folder in following .zip from here: https://androidfilehost.com/?fid=673368273298920860)
1. Ensure on latest BusyBox.
2. Install latest V4A from Magisk & download driver, device will auto-restart.
3. Uninstall this latest V4A (don't delete data or cache).
4. Install V4A 2.5.0.5 .apk from above link. Don't open app yet.
5. From Magisk, install Audio Modification Library (choose relevant options). Restart device.
6. Additionally, Magisk install Audio Compatibility Patch. Restart device.
7. Ensure V4A settings FX compatible mode option = Normal.
(Don't optmise V4A in battery settings).
Noticeable improvement in speaker volume (I don't play over BT or headphones, so cannot comment).

elmor0 said:
If rooted, try installing latest V4A directly from here (https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx) rather than via Magisk.
I prefer older V4A versions, having tried above.
My preferred V4A is 2.5.0.5 (found in App folder in following .zip from here: https://androidfilehost.com/?fid=673368273298920860)
1. Install latest V4A from Magisk & download driver, device will auto-restart.
2. Uninstall this latest V4A (don't delete data or cache).
3. Install V4A 2.5.0.5 .apk from above link. Don't open app yet.
4. From Magisk, install Busybox & Audio Modification Library (choose relevant options). Restart device.
5. Additionally, Magisk install Audio Compatibility Patch. Restart device.
6. Ensure V4A settings FX compatible mode option = Normal.
Noticeable improvement in speaker volume (I don't play over BT or headphones, so cannot comment).
Click to expand...
Click to collapse
I uninstalled everythingg I had installed up to that point (everything I could at least), and followed the instructions step by step. Still getting abnormal in the V4A app (at least the app looks cooler now : P). I really don't know what is going on at this point. I might just reset the whole phone and follow your instructions again. I will report back when I get around to that.

Ok, I decided to play around a little before trying a reset; and I installed Viper 4 Android legacy with the APK from the zip you gave me, and it now says audio format supported! Yay! It just says "Processing: no" now. I have a feeling that I have something setup wrong. Any ideas?
Edit: Grammer

You managed to install driver v.2.5.0.5 or latest v4a?
Processing should change to "Yes" whilst audio is playing (music player/ YouTube/ system sounds etc).
Streaming music can be hit & miss; set up Audio Compatibility Patch correctly (via Magisk).

elmor0 said:
You managed to install driver v.2.5.0.5 or latest v4a?
Processing should change to "Yes" whilst audio is playing (music player/ YouTube/ system sounds etc).
Streaming music can be hit & miss; set up Audio Compatibility Patch correctly (via Magisk).
Click to expand...
Click to collapse
I installed driver version 2.5.0.4 with the APK you pointed me towards in the .zip/viperfx/app folder.
I will reinstall the audio conpatibily patch. What options should I choose in the patch?
Edit: I did not install the driver *with* the APK, but alongside it. I installed the driver via ViperFX Legacy in Magisk.

Try the ACP if V4A not working for streaming music apps.
I selected following:
- Skip audio_policy patching? = NO
- Skip notification_helper remover? = YES
- Skip usb policy patching for usb dacs? = NO
- Use lib workaround? = NO

Error-404-Go-Home said:
Edit: I did not install the driver *with* the APK, but alongside it. I installed the driver via ViperFX Legacy in Magisk.
Click to expand...
Click to collapse
That's fine, as long as V4A driver is enabled/ status normal/ format supported/ and it is processing during audio play.

elmor0 said:
That's fine, as long as V4A driver is enabled/ status normal/ format supported/ and it is processing during audio play.
Click to expand...
Click to collapse
It still isn't processing audio : (. I have tried resetting and following your instructions again. The only way I am able to get it to stop displaying "Status: Abnormal" is by installing Viper4Android FX Legacy in the new driver mode with the user app, then installing the Audio Modification and compatibility patch, then restarting and installing the APK you gave me. Even with all that, it will not recognize audio being played (it displays "Processing: No" when audio is very clearly playing and I have effects enabled). I am now considering switching to LineageOS (I would be there already if it wasn't for the fingerprint sensor driver being broken).
Edit: Do you think switching kernels would change anything?
Edit 2: I noticed a toast notification from V4A on startup saying "A running program has requested Android to disable audio effects, so V4A will be temporarily disabled."
I am thinking that maybe the stock Dirac audio processing might be interfering with V4A somehow. Is there anyway to get Viper to ignore requests to disable?

Well, Lineage didn't fix anything (No matter what I did, V4A would not stop displaying abnormal). Took me a little while to get back to stock, but the latest version of V4A is working, but only for the first 30 seconds after reboot before giving me the previously mentioned toast notification. I have removed all apps that are even remotely audio processing related, but still have this problem. Anybody else had something similar? If you did, how did you fix it?
(Also, special thanks to elmor0 for all of your help getting me this far I'm so close)
Edit: Holy shiz it's working! I used the method described in my previous post, but with the added step of uninstalling and reinstalling audio modification library after the last reboot. Again thank you all for your help! And I really hope this helps someone!

Error-404-Go-Home said:
Edit: Holy shiz it's working! I used the method described in my previous post, but with the added step of uninstalling and reinstalling audio modification library after the last reboot. Again thank you all for your help! And I really hope this helps someone!
Click to expand...
Click to collapse
hi
I'm having the same problem for months now
I hear it needs SE Linux to be permissive for V4A to work properly
I had no success on getting that SE Linux to turn Permissive unfortunately
long story short , I found myself here
can you please give me a step by step on how you got V4A to work , that is off course if its still working for you man
I'm at the end of my rope here , any guidance would appreciated ,
Thanx

JimmyMX said:
hi
I'm having the same problem for months now
I hear it needs SE Linux to be permissive for V4A to work properly
I had no success on getting that SE Linux to turn Permissive unfortunately
long story short , I found myself here
can you please give me a step by step on how you got V4A to work , that is off course if its still working for you man
I'm at the end of my rope here , any guidance would appreciated ,
Thanx
Click to expand...
Click to collapse
I ended up refllashing with Lineage and installing this: https://forum.xda-developers.com/t/app-fix-100-working-viper4android-for-android-11-devices.4213647/
That version has worked flawlessly for me for Android 10 and 11.
Good luck!