[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7

[shadowstep]

Thank you for your work! Would this version of Viper FX you made work on Oneplus 8? I'm currently using Android 12, as Viper FX didn't work on A13. Do I need to install any add-ons for the one you made, or does it run smoothly on OOS13?

Feel free to test it out yourself; should work in OOS 13 without any additional modules (provided you aren't using other audio mods in parallel).

 

[TheMystic]

Hi!
I have a OnePlus 8 with Android 12.1 and I installed these modules that are in the zip. It works fine with the Viper Audio FX, but I noticed that if I have a stronger bass in the music, the sound bounces, it limits it back and makes the music unenjoyable. I think Dolby Atmos causes this problem, because if I turn off some settings there, it gets a bit better, but even then it's still quite unenjoyable, e.g. a Drum and Bass music. Is there any solution to stop the bass from bouncing?

Although V4A worked on my 8T, I didn't really enjoy the quality of sound as much as I would like to. V4A was pretty much the primary reason why I rooted my phone. Since that purpose was not served well, I unrooted my phone and reverted everything back to stock, including locking the bootloader.

So I'm not in a position to make any suggestions here on how to improve the quality of sound.

 

[Norbosz]

Feel free to test it out yourself; should work in OOS 13 without any additional modules (provided you aren't using other audio mods in parallel).

Ok, I will install OOS 13 in a few days and test if it works. I don't use any other audio mods.

 

[Norbosz]

Although V4A worked on my 8T, I didn't really enjoy the quality of sound as much as I would like to. V4A was pretty much the primary reason why I rooted my phone. Since that purpose was not served well, I unrooted my phone and reverted everything back to stock, including locking the bootloader.

So I'm not in a position to make any suggestions here on how to improve the quality of sound.

It doesn't give me the quality I'm used to on OOS11 either, maybe it's the Dolby Atmos, because after I turn it off, it sounds a bit nicer and the bass doesn't bounce.

 

[Norbosz]

Feel free to test it out yourself; should work in OOS 13 without any additional modules (provided you aren't using other audio mods in parallel).

I installed OOS13 on my OnePlus 8 and it works perfectly with the Viper FX you made Now I am very happy! Thanks for your work! But can I only use it in Legacy mode? Will it not work in normal mode? Because I noticed that it doesn't change the sound for some applications.

 

[shadowstep]

I installed OOS13 on my OnePlus 8 and it works perfectly with the Viper FX you made Now I am very happy! Thanks for your work! But can I only use it in Legacy mode? Will it not work in normal mode? Because I noticed that it doesn't change the sound for some applications.

You're welcome, good to know it works fine. And yes, it only works with legacy mode enabled, unfortunately.

 

[stem69]

Do you have your selinux set to permissive? If you don't and you dont want to thats fine but you can't say I want enforcing and viper to work you have to make a call.

install busybox magisk

Install viper zip

install james DSp 4.6 module

install audio modification library 4.1 magisk module

install selinux permissive magisk module v2 so it will lock it in

Open viperFX app install driver give root and reboot

should be working when you turn it on and set it up

Thanks Techguy777 this worked for me on my OnePlus 6 with Lineage 20 and didn't need busybox (which I've never managed to install), but did install all the others.

 

[Techguy777]

Thanks Techguy777 this worked for me on my OnePlus 6 with Lineage 20 and didn't need busybox (which I've never managed to install), but did install all the others.

To be completely honest I figured that out back in android 9. Im normally extremely good at getting viper to work on anything. I have thought for years it looks like viper will be all done and then I figure out how to make it work. Even on the fiio x5 III no one had it working and I grabbed the audio config policy from my nexus 6 on lollipop and replaced it and viper worked like a charm. Now the new system has done it in. My tab s8 will not run viper no matter what. Enjoy

 

[bbortel93]

I can't seem to get v4a up and running on Nameless. Was able to work it just a week ago on WatchDogs and crDroid. Any ideas?

 

[Reaper116]

I can't seem to get v4a running. I've tried using the repackaged installer and the stock .APK, I've tried the audio modification and audio comparability patch via magisk for both.

I currently have it installed with the repackaged installer and no other mods, and the driver is installed with neon enabled, but it's literally just blank. In theory I just have to enable the master limiter and it'll work but it's nothing is showing up.

It's an android based head unit running android 9, but it dose lie about running 12. This could be an issue, but I'm not sure why it would be unless 9 is too outdated.

I have tried the legacy 2.5.0.5 vertion, and while the icons do show, I can't seem to get the driver installed, even with busybox.

 

[olmiks]

Hello! Please help. The OnePlus9pro, Oxygen12 phone, the bootloader is unlocked, there is a root. I can't install Viper. Constantly requires the installation of the driver! What could be the problem and how to solve? Viper is very needed! Perhaps the Dolby Atmos installed in the firmware interferes? If so, how to disable it? And what version of Viper should I install? Please help!

 

[asripath]

Hello! Please help. The OnePlus9pro, Oxygen12 phone, the bootloader is unlocked, there is a root. I can't install Viper. Constantly requires the installation of the driver! What could be the problem and how to solve? Viper is very needed! Perhaps the Dolby Atmos installed in the firmware interferes? If so, how to disable it? And what version of Viper should I install? Please help!

Have you tried
.Boot to TWRP Recovery
-Flash v4afx-rootless_10.21.2020.zip
(https://zackptg5.com/downloads/v4afx-rootless_10.21.2020.zip)
4.
Reboot to System
Open v4a app

 

[fyresg]

I have been enjoying this fantastic app for a long time on my old phone. I just upgraded to a Xiaomi Mi 13, unlocked its bootloader, installed Xiaomi.eu firmware (MIUI 14.0.21; Android 13; Android Security Update 2023-02-01), flashed TWRP 3.7.0, installed Magisk 25.2, downloaded ViPER4AndroidFX-repackagedhoch61-697516a.zip, and finally installed Viper4Android with TWRP.

The accompanying app was automatically installed by the installer zip file. I ran the app but it always show a box "No driver found. Do you wish to install the driver now? Caution... (OK)" And tapping OK installed the app, rebooted the phone, and I verified the module ViPER4Android FX 2.7.2.1 by pittvandewitt, MrWhite214 is loaded in the Magisk app, Modules page. Yet, whenever I run the Viper app, it always show the "No driver found" box.

There is no way for me to troubleshoot the app, or change any settings, as the very moment it loads, the "No driver found" box comes up.

How should I proceed to troubleshoot? Thank you!

 

[zgfg]

I have been enjoying this fantastic app for a long time on my old phone. I just upgraded to a Xiaomi Mi 13, unlocked its bootloader, installed Xiaomi.eu firmware (MIUI 14.0.21; Android 13; Android Security Update 2023-02-01), flashed TWRP 3.7.0, installed Magisk 25.2, downloaded ViPER4AndroidFX-repackagedhoch61-697516a.zip, and finally installed Viper4Android with TWRP.

The accompanying app was automatically installed by the installer zip file. I ran the app but it always show a box "No driver found. Do you wish to install the driver now? Caution... (OK)" And tapping OK installed the app, rebooted the phone, and I verified the module ViPER4Android FX 2.7.2.1 by pittvandewitt, MrWhite214 is loaded in the Magisk app, Modules page. Yet, whenever I run the Viper app, it always show the "No driver found" box.

There is no way for me to troubleshoot the app, or change any settings, as the very moment it loads, the "No driver found" box comes up.

How should I proceed to troubleshoot? Thank you!

You have Magisk Stable v25 2, not Canary v25210 (it won't work with v25210)?

You can try V4A 64-bit Beta (for new devices with 64-bit audio):

GitHub - AndroidAudioMods/ViPER4Android: ViPER4Android app configuration files

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com

 

[fyresg]

You have Magisk Stable v25 2, not Canary v25210 (it won't work with v25210)?

You can try V4A 64-bit Beta (for new devices with 64-bit audio):

GitHub - AndroidAudioMods/ViPER4Android: ViPER4Android app configuration files

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com

Thanks for the suggestion. I tried V4A 64-bit version 0.30 downloaded and installed from the site you've given. Sadly, while the module installs properly and the app runs, the Status says Driver version: unknown; Enabled: No. But after setting to Legacy mode, it works!

 

[zgfg]

Thanks for the suggestion. I tried V4A 64-bit version 0.30 downloaded and installed from the site you've given. Sadly, while the module installs properly and the app runs, the Status says Driver version: unknown; Enabled: No. But after setting to Legacy mode, it works!

Always use that Legacy mode

 

[sarf2k4]

I need help with the v4a.

devices: realme c2 rmx1941
android: stock rmui android 10 debloated
recovery: stock realme recovery (i cant put twrp permanently)
magisk: 25.2 + zygisk enabled
v4a: repackagedhoch61

In opening the v4a, the driver status are the following

driver version: 2.5.0.4
neon enabled: no
enabled: no
status: abnormal
audio format: unsupported
processing: no
sampling rate: 0
Legacy mode: on

I even tried having aml as well as Audio Compatibility Patch installed with volup all the way except the recommended to voldown, the driver status is still the same as above.

I also tried with the older zackgpt5(?) v4a legacy and asked me to install driver, it stated driver install failed

I also tried to search on other guides, it is kind of all over the place. Maybe I'm doing it wrong?

 

[zgfg]

I need help with the v4a.

devices: realme c2 rmx1941
android: stock rmui android 10 debloated
recovery: stock realme recovery (i cant put twrp permanently)
magisk: 25.2 + zygisk enabled
v4a: repackagedhoch61

In opening the v4a, the driver status are the following

driver version: 2.5.0.4
neon enabled: no
enabled: no
status: abnormal
audio format: unsupported
processing: no
sampling rate: 0
Legacy mode: on

I even tried having aml as well as Audio Compatibility Patch installed with volup all the way except the recommended to voldown, the driver status is still the same as above.

I also tried with the older zackgpt5(?) v4a legacy and asked me to install driver, it stated driver install failed

I also tried to search on other guides, it is kind of all over the place. Maybe I'm doing it wrong?

Again, always (incl. Repackaged V4A v2.7.2.1) set to Legacy mode and enable Master Limiter.
Without Master Limiter, V4A is not enabled for the given speaker - phone, headset or BT

For the beginning, stay with Repackaged, disable AML and all other audio modules, reboot and try as above

If still not working, scroll back through the posts, find, download and test with V4A 64-bit Reversed Engineered instead.
Uninstall one V4A module, reboot, install the other V4A and reboot - to be clean

Once you have V4A working, you can later add other audio modules (like JamesDSP), but then you must also use AML

 

[sarf2k4]

Again, always (incl. Repackaged V4A v2.7.2.1) set to Legacy mode and enable Master Limiter.
Without Master Limiter, V4A is not enabled for the given speaker - phone, headset or BT

For the beginning, stay with Repackaged, disable AML and all other audio modules, reboot and try as above

If still not working, scroll back through the posts, find, download and test with V4A 64-bit Reversed Engineered instead.
Uninstall one V4A module, reboot, install the other V4A and reboot - to be clean

Once you have V4A working, you can later add other audio modules (like JamesDSP), but then you must also use AML

forgive me for not specifying in my previous post that; i did turn legacy mode on/off, master limiter on/off as well as compatibility mode on/off. Before and after your post just to be sure on the repackaged one.

I also flashed the v4a64bit and it went ok. I also tried to fiddle with the output gain in master limiter just to see it has taken effect, indeed it is. But not on the repackaged.

I read about having to append specific commands on the proc.sh or something? but the file are nowhere to be seen on /data/adb/module/viper4android/ (repackaged) so I guess it was an old repackaged or for the legacy v4a modules.

screenshot as follows too, one of the screenshot, after installing the app fired up its almost like an antivirus/malware scanner. I don't know what's the package name to remove that. v4a64bit though has that 'scanner' fired up, but with 2 buttons; continue and ok unlike the following screenshot for the v4a repackaged. The results for both were "security check failed"

I would like to stay with the v4a repackaged if that is even possible

 

[SirRhor]

You have Magisk Stable v25 2, not Canary v25210 (it won't work with v25210)?

You can try V4A 64-bit Beta (for new devices with 64-bit audio):

GitHub - AndroidAudioMods/ViPER4Android: ViPER4Android app configuration files

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com

On a Pixel 7 Pro running crDroid March update, is weird. This is the first time I get Viper to work on A13. When legacy mode is enabled, only audio coming from the speakers will activate the driver, but no Bluetooth audio. Disabling legacy mode will allow Bluetooth audio to be processed in Viper, but no on the phone speakers. Using AML I can get DTS Ultra to work with Viper. Maybe overkill for Sennheiser Momentum 3 earbuds, but it's nice to know that Viper is finally working on A13.