Installing ViPER4Android today is a two-part job: an app and a driver module. Done in the right order, it takes about ten minutes. This guide follows the order recommended in the official README and adds checks so you know each step worked.
Before you start: flashing a system audio module can stop some phones from booting. The driver maintainers only confirm Pixel 8 Pro configurations. Make a full backup and know how to boot your root manager's safe mode or recovery.
What you need
- A phone running Android 9 (API 28) or newer.
- Root through Magisk, KernelSU or APatch.
- A computer with ADB, or a terminal app with root, for the HAL check.
- The ViPER4Android APK from the app Releases page.
- One ViPERFX_RE module from the driver Releases page.
Step 1: Identify your audio HAL
The driver comes in two versions that are not interchangeable. Run these commands from a computer with USB debugging enabled:
adb shell ps -A | grep "audio.*aidl"
adb shell su -c 'service list | grep -i IFactory'
If you see an audio HAL process containing "aidl" and an android.hardware.audio.effect.IFactory/default line, you need the AIDL module. If not, the non-AIDL (legacy) module should be the right one. Devices that launched with Android 15 or later need the AIDL module.
Step 2: Install the app
- Download the APK from the official Releases page.
- Open it from your browser's downloads or a file manager.
- If Android blocks it, allow "Install unknown apps" for that one app only. Do not disable Play Protect or other security features.
- Finish the install, but you do not need to configure anything yet.
Step 3: Flash exactly one driver module
- Open Magisk, KernelSU or APatch.
- Go to the Modules section and choose "Install from storage".
- Select the AIDL or non-AIDL ZIP you identified in Step 1.
- Wait for the installer to finish without errors.
Under KernelSU and APatch, the modules mount their own files during boot; under Magisk, Magisk mounts them normally. The README lists compatibility with several mount solutions, including Magic Mount, meta-overlayfs and Mountify.
Do not flash both modules. If you picked the wrong one, remove it, reboot, and then flash the other.
Step 4: Reboot
The audio server only reads its effect configuration at boot, so a full restart is required. If the phone does not boot, use your root manager's safe mode or recovery to disable the module.
Step 5: Verify the driver
Open ViPER4Android and grant root access when asked. Then check the driver status in the app. To confirm from a computer:
adb logcat -d -s 'ViPER4Android:*' | grep -E 'Welcome|version|created'
You should see lines such as "Welcome to ViPER FX" and "ViperContext created". If they are missing, the audio framework did not load the library. Our driver guide explains the deeper checks.
First-use setup
- Choose Global mode in Settings. It processes the whole audio mix and is the most compatible.
- Play a familiar track through the output you use most.
- Enable one effect at a time, for example the equalizer first, then ViPER Bass, then Clarity.
- Keep Output Volume conservative and enable the limiter to avoid clipping.
- Switch outputs and repeat. Each device gets its own profile automatically.
Importing presets
Version 2 imports presets in the v2.1 JSON format. Older presets need converting first:
python3 tools/convert_preset.py preset.xml --to 2.1 -o preset.v2.json
The converter is included in the source archive that our download button provides.
Optional: Per-app mode
Per-app mode creates a separate effect for each player. On Android 14 and later it needs root to read real session IDs through dumpsys audio, unless the app is installed as a privileged system app. Only switch if you need different processing per app.
How to uninstall cleanly
- Export presets you want to keep.
- Remove the ViPERFX_RE module in your root manager.
- Reboot.
- Uninstall the app like any other Android app.
Next steps
Once sound is processing, our settings guide gives sensible starting points for earbuds, headphones and the phone speaker.
Get the ViPER4Android source archive
main.zip from the official GitHub repository, GPL-3.0. The download starts on this page.