Search for "ViPER4Android driver" or "ViPER4Android module" and you will find instructions from many different years. Most confusion comes from mixing those generations. This guide explains the current driver layer, which module to choose, and how to diagnose it.
What the driver is
The current driver is ViPERFX_RE, a reverse-engineered and modernized port of ViPER4Android. Its DSP has been re-implemented from a decompilation of the original libv4a_fx.so, now processes audio in float32, removes dead code and uses refreshed dependencies. The module credits several community developers, including pittvandewitt, MrWhite214, Zackptg5, Martmists, Iscle and llsl.
The driver is a shared library that the Android audio server loads as an audio effect. The ViPER4Android app talks to it and sends the parameters you set with its sliders.
Why it is a module
The audio server only loads effects listed in its configuration files under /vendor/etc and /system/etc. A Magisk-style module can add the library and a patched audio_effects configuration without permanently modifying those partitions. That systemless approach is why the driver ships as a module for Magisk, KernelSU and APatch.
AIDL vs non-AIDL
| Non-AIDL (legacy) | AIDL | |
|---|---|---|
| Audio interface | Classic effect plugin interface (often called the HIDL-era path) | Stable AIDL audio effect HAL introduced in Android 13 |
| Library name | libv4a_re.so | AIDL effect library |
| Confirmed on | Pixel 8 Pro, Android 14 | Pixel 8 Pro, Android 16 |
| Android 15+ launch devices | Not supported | Required |
Google moved the audio effect framework from the legacy C plugin model to an AIDL HAL. Devices launching with Android 15 no longer load the old plugin type, so only the AIDL module can work there. Installing the wrong module may do nothing or may cause boot problems, and you must never install both.
How to choose
adb shell ps -A | grep "audio.*aidl"
adb shell su -c 'service list | grep -i IFactory'
An AIDL audio process plus an IFactory service line means AIDL. Otherwise, start with the non-AIDL module. Some Pixel devices may need an extra vendor shim for AIDL; the README mentions a community project for that case.
Verifying that the driver loaded
Both drivers log under the ViPER4Android tag. On the AIDL path you will also see AOSP framework tags such as AHAL_EffectImpl.
- Check the log:
adb logcat -d -s 'ViPER4Android:*'should show "Welcome to ViPER FX", the version, and "ViperContext created". - Check the configuration:
adb shell su -c 'grep -r v4a /vendor/etc /system/etc'should list av4a_relibrary entry. - Check the SELinux label (non-AIDL):
adb shell su -c 'ls -Z /vendor/lib*/soundfx/libv4a_re.so'should show avendor_filelabel.
Common conflicts
- AudioModificationLibrary: documented as incompatible with the AIDL module. Disable it before using AIDL.
- Other DSP modules: two mods patching the same effect configuration can cancel each other out.
- Old ViPER drivers: remove leftover modules from older ViPER4Android generations before installing ViPERFX_RE.
How close is it to the original sound?
The maintainers describe audio fidelity as best-effort. Because the DSP was rebuilt from decompiled code, subtle deviations from the original ViPER4Android are expected. In normal listening most people will not notice, but if you compare closely with an old device you may hear small differences.
Licensing note
ViPERFX_RE is a reverse-engineering project that its maintainers say is not for commercial use and may carry legal restrictions in some jurisdictions. The app is published separately under GPL-3.0.
Related guides
Follow the installation guide for the full process, or read why the driver needs root.
Get the ViPER4Android source archive
main.zip from the official GitHub repository, GPL-3.0. The download starts on this page.