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

Search This thread

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,208
6,119
Sydney
Android 12. I had it working in my Samsung S21+ (Exynos) with Android 12. Now my S22 ultra (Snapdragon) with Android 12 gets driver installation loop.
there is A12 specific thread for Viper. You may get better help posting your questions there.
 

ffp.

Senior Member
Oct 6, 2011
546
71
there is A12 specific thread for Viper. You may get better help posting your questions there.

This thread you posted is for pixel phones
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,208
6,119
Sydney
This thread you posted is for pixel phones
Android phones in general have more in common than not. Pixel phone builds can be considered a "base" of Android. ie AOSP

The techniques may apply, and more so than those in a thread that service different version of android, but even if for your specific device. I am not saying you MUST use the info, just a suggestion where you may get some more appropriate help.
 

aeonline

Senior Member
Apr 26, 2018
53
1
Please help me I want to delete viper4android in Magisk but I can't delete it. because I want to download a new version

My unit : PX5 for android auto car

android 10

Please help as link;
 
Last edited:

lysaer

Senior Member
Apr 2, 2012
94
6
Is this no longer in development?

I am having issues getting it to work with android 12 on my pixel 2 XL

Is there perhaps an alternative to viper4android that has all the output gain increase etc or a newer updated version someone is working on?
 

69363727

New member
May 31, 2019
1
0
Sorry for disturbing, I faced with this happen( selinux=permissive android 11 rom, and they said that they're not processing the audio when I using the legacy mode and neon enabled and normal activated situation
 

mn1968

Senior Member
Nov 7, 2011
583
157
Been using V4A 2.7.1.6 on my Pixel 4a 5G for the past year. All works well except when I try to save a preset, the app (V4A) crashes, and thus no preset gets saved. Any thoughts how to fix this?

Thanks!
 

mn1968

Senior Member
Nov 7, 2011
583
157
Been using V4A 2.7.1.6 on my Pixel 4a 5G for the past year. All works well except when I try to save a preset, the app (V4A) crashes, and thus no preset gets saved. Any thoughts how to fix this?

Thanks!
Still no luck with trying to save presets...v4a keeps crashing.

However, I have gotten v4a to work with Android Auto. In settings I toggled on BOTH "Attach audio effects (All sessions but 0)" and "Compatibility mode". The sound enhancements, unfortunately, come thru the "Speaker" settings...but it's better than nothing. At one time enhancements appeared to work via v4a bluetooth settings but I have not been able to replicate that since - audio is always routed thru the speaker settings.
 

matt#1

New member
Jun 3, 2022
1
1
Still no luck with trying to save presets...v4a keeps crashing.

However, I have gotten v4a to work with Android Auto. In settings I toggled on BOTH "Attach audio effects (All sessions but 0)" and "Compatibility mode". The sound enhancements, unfortunately, come thru the "Speaker" settings...but it's better than nothing. At one time enhancements appeared to work via v4a bluetooth settings but I have not been able to replicate that since - audio is always routed thru the speaker settings.
you can read this comment and check your v4a folder permission. I used to unable to save preset, but after follow him it works perfectly

 
  • Like
Reactions: mn1968

mn1968

Senior Member
Nov 7, 2011
583
157
you can read this comment and check your v4a folder permission. I used to unable to save preset, but after follow him it works perfectly

Thanks! Works now.
 

mn1968

Senior Member
Nov 7, 2011
583
157
However, I have gotten v4a to work with Android Auto. In settings I toggled on BOTH "Attach audio effects (All sessions but 0)" and "Compatibility mode". The sound enhancements, unfortunately, come thru the "Speaker" settings...but it's better than nothing. At one time enhancements appeared to work via v4a bluetooth settings but I have not been able to replicate that since - audio is always routed thru the speaker settings.
I have experimented more with v4a and Android Auto. On the phone in Developer Settings I toggled on "Disable USB audio routing". I kept v4a settings toggled on for "Attach audio effects" & "Compatibility mode". I then connected to Android Auto and voila...v4a was processing through the bluetooth settings. I was able to tweak settings and could hear the differences. It was definitely processed via bluetooth settings. This worked for Spotify & Musicolet. When I tried Muzecast , v4a didn't process any audio tweaks. Nor does it work for TuneIn Radio or Audacy.

What's weird though, is now Spotify and Musicolet have reverted back to processing thru the "Speaker" settings - not bluetooth anymore. Even after rebooting the phone and re-starting the car.

Not sure why the bluetooth settings don't process any longer when connected to Android Auto, and why some apps don't work while others do. Very weird.

FWIW - v4a does process bluetooth settings for all apps when connected solely to the car's bluetooth WITHOUT Android Auto, but I have to disable v4a setting "Attach audio effects".
 

mn1968

Senior Member
Nov 7, 2011
583
157
I have experimented more with v4a and Android Auto. On the phone in Developer Settings I toggled on "Disable USB audio routing". I kept v4a settings toggled on for "Attach audio effects" & "Compatibility mode". I then connected to Android Auto and voila...v4a was processing through the bluetooth settings. I was able to tweak settings and could hear the differences. It was definitely processed via bluetooth settings. This worked for Spotify & Musicolet. When I tried Muzecast , v4a didn't process any audio tweaks. Nor does it work for TuneIn Radio or Audacy.

What's weird though, is now Spotify and Musicolet have reverted back to processing thru the "Speaker" settings - not bluetooth anymore. Even after rebooting the phone and re-starting the car.

Not sure why the bluetooth settings don't process any longer when connected to Android Auto, and why some apps don't work while others do. Very weird.

FWIW - v4a does process bluetooth settings for all apps when connected solely to the car's bluetooth WITHOUT Android Auto, but I have to disable v4a setting "Attach audio effects".
Just to give a final update...

I have v4a working over bluetooth while connected to Android Auto on a consistent basis. I have AA AIO Tweaker installed and have checked "Disable Bluetooth Auto Connect". The v4a settings I mentioned above remain the same. Now after I connect to Android Auto I need to manually turn on bluetooth from the phone, but I have been successfully getting music processed through v4a bluetooth settings. Spotify and Musicolet work perfectly this way. Muzecast does not process thru v4a until I disable "Attach audio effects". Audacy and TuneIn Radio do not process thru v4a no matter what settings I try...but I don't use those much in the car. They're more like a back-up for if I travel out of state and want to listen to my local stations.

I still don't know why some apps work this way and other don't. They all work as intended when I simply connect to a bluetooth speaker or ear-buds but not Android Auto. 🤷‍♂️

If you don't have AA AIO Tweaker installed you MAY be able to achieve the same results by simply going into the Android Auto app on the phone and disabling "Use Bluetooth". However, I have not experimented with that so it may or may not work as intended...but I don't see why it wouldn't.

Hope this helps someone.
 

Lostprophet85

Member
Apr 17, 2018
46
10
I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)
Thank you for sharing this, I can confirm this works like a charm on a Oneplus 7 Pro with crDroid 8.6 (Android 12.1), I don't even need to enable legacy mode :cool:
 

okku007

New member
Jun 22, 2022
2
0
Viper4Android Ain't working on my phone



Hey,

I have Samsung Galaxy M20,

I rooted the device using odin and installed magisk as well, but after i install the apk of viper it says install driver but after installing the driver and rebooting the device viper says that the Driver Status is Abnormal, i tried installing viper thru magisk module but it's still not working.

when i first rooted my phone it was working i installed it thru the magisk module zip. but after that my same phone went into BootLoop so i reset it and now viper isnt working.

If you guys have any solutions please reach me out

(im trying installing viper on the same device)
 

okku007

New member
Jun 22, 2022
2
0
Viper4Android Ain't working on my phone



Hey,

I have Samsung Galaxy M20,

I rooted the device using odin and installed magisk as well, but after i install the apk of viper it says install driver but after installing the driver and rebooting the device viper says that the Driver Status is Abnormal, i tried installing viper thru magisk module but it's still not working.

when i first rooted my phone it was working i installed it thru the magisk module zip. but after that my same phone went into BootLoop so i reset it and now viper isnt working.

If you guys have any solutions please reach me out

(im trying installing viper on the same device)
I fixed it, first flashed magisk module, then didnt restarted, installed viper and installed driver, then opened viper settings and then turned on compatibility mode and then played a song on spotify then turned compatibility mode off, its working flawlessly.
 

X-Nemesis

Senior Member
Jun 12, 2012
436
54
Kitchener
I have a Oneplus One on Lineage 18.1 that I'm using as a DAP but I'm unable to get V4A processing. I have Magisk 25.1 installed, SElinux is permissive and Busybox installed.

Anyone able to shed some light on getting this working?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)
    Thank you for sharing this, I can confirm this works like a charm on a Oneplus 7 Pro with crDroid 8.6 (Android 12.1), I don't even need to enable legacy mode :cool:
    1
    Still no luck with trying to save presets...v4a keeps crashing.

    However, I have gotten v4a to work with Android Auto. In settings I toggled on BOTH "Attach audio effects (All sessions but 0)" and "Compatibility mode". The sound enhancements, unfortunately, come thru the "Speaker" settings...but it's better than nothing. At one time enhancements appeared to work via v4a bluetooth settings but I have not been able to replicate that since - audio is always routed thru the speaker settings.
    you can read this comment and check your v4a folder permission. I used to unable to save preset, but after follow him it works perfectly

  • 537
    ViPER4Android FX
    YF7EJvAcFH9ZuuytKO91DimKH-TQUvYOaA-gmdBrioXY-LSgtjoadLI17gtaGgIkR6KBXyVA4IXtcdjfLdQ=w2880-h1608

    By pittvandewitt and MrWhite214

    Introduction
    Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look of the app. As a solution for these troubles we have rewritten the 2.4.0.1 app source and added all 2.5.0.5 features to it. Many more features have been implemented too.
    With our huge success of ViPER4Android 2.6 we decided to completely rewrite the ViPER4Android app in Kotlin. This allowed us to squeeze out the remaining bugs and clean up the code even more. After a long time of waiting for you and developing for us, ViPER4Android 2.7 is finally here!
    There are many new features and improvements compared to 2.6, of which some can be found in the changelog. Hit the download button to check it out yourself!

    Downloads
    You can download the latest version on XDA Labs
    If you were pointed here for the installer by @Zackptg5, the link can be found here

    pittvandewitt's vdc service
    If you've always wanted to get the most neutral and arguably best sound coming from your headphones, make sure to join the VDC service to request a file!

    Donate
    You can donate to us via PayPal or buy our donation package from XDA Labs with extra features!
    Donate via PayPal
    Buy our donation package *coming soon*

    Dev Note
    If you want to include the app in your work, you're free to do so as long as you give proper credits

    Legal notice
    We are not associated with vipersaudio nor audlabs.
    Stating their Github readme we're free to use the driver as long as it's not used commercially.
    The driver parameters are obtained from the 2.4.0.1 source. The graphical EQ interface is inspired by the Cyanogenmod DSP application
    The app is still named ViPER4Android, because the driver isn't any different from what ViPER ACOUSTIC provides.
    Renaming it without changing anything would be considered kanging, which is not what is going on here.

    Credits
    ViPER ACOUSTIC for the driver
    Bappo for Swedish translation
    pittvandewitt for Dutch translation
    sazuke0703 for Thai translation
    R1DEN for Russian translation
    Hede for Danish translation
    gloeyisk for Indonesian translation
    LCS for Chinese simplified and traditional translations
    razor84 for Turkish translation

    Installation
    Download and install the APK from XDA Labs
    Follow the instructions when opening the app

    XDA:DevDB Information
    ViPERAndroid, App for the Apps & Games

    Contributors
    Team_DeWitt, pittvandewitt, Mr_White_214

    Version Information
    Status: Stable
    Current Stable Version: 2.7.2.1
    Stable Release Date: 2020-10-27

    Created 2018-04-09
    Last Updated 2020-10-27
    136
    Currently on the wishing list
    • Car mode / head unit detection
    • More translations. If you're interested, take a look over here to find the files. Fork the repo and make a pull request to get your translation merged in next release!
    • EMUI (Huawei) 8.0+ refuses to load the driver. Ask ViPER ACOUSTIC for a 64bit driver (Can't fix)
    • Updated driver that does not require selinux injections or the libstdc++ dependency workaround (Can't fix)

    Before reporting:
    Make sure you use the latest APK provided on XDA Labs
    Make sure any other audio mod is disabled/removed before installing the driver. We really cannot afford fixing every single device setup, especially when it's not related to the app


    If you would like to report a bug, pm @Team_DeWitt using the following format:
    [Describe the problem and your steps you take to reproduce it]
    [Phone brand and model]
    [OS (ROM) + Android version]
    [Root method (in case of magisk: core or full)]
    [Provide a link to your log file]
    116
    Changelog

    2.7.2.1
    • Improved loading logic for convolution files
    • Fixed an issue when installing the module on older Magisk versions
    • Bug fixes
    • Stability improvements


    2.7.2.0
    • Android 11 support
    • Automatically save/restore settings based on the device type/name
    • Add preset widget
    • Reworked presets
    • Performance improvements
    • Close service when no music playback is active if legacy mode is disabled
    • Add optional crashlytics to help improving future versions

    2.7.1.6
    • Support Magisk 20.3
    • Long press a feature to show description
    • Material theme update
    • Support scoped storage on Android 10+ (Preset dir is now /sdcard/Android/data/com.pittvandewitt.viperfx/files/Preset)

    2.7.1.0
    • Support Magisk 19
    • Add compatibility setting
    • Add ability to attach to sessions
    • Fix preset loading bug
    • Switch from setools to magiskpolicy
    • Important release notes: Link

    2.7.0.0
    • Full rewrite in Kotlin
    • New UI
    • Presets can be managed in the app itself
    • Effects can be set more precisely with seekbars
    • Min API 23
    • Uses 2.5.0.4 driver only
    • Audio routing bug fixed
    • Driver status bug fixed
    • Cross device effect changing bug fixed
    • App follows system dark/light mode (can be toggled with google messages e.g.)
    • Installation is faster and more versatile
    • Notification settings
    • Reduced APK size significantly

    2.6.0.5
    • Add app shortcuts (7.1+)
    • Minor interface redesign
    • Fix muffled sound
    • Fix options not applying
    • Fix profile conversion
    • Introduce vdc service
    • Improve performance
    • Update driver installation
    • Update chinese translations, thanks to KiSS

    2.6.0.4
    • Retain service after clearing recents
    • Emergency service.sh fix
    • Support Magisk core mode
    • Fix profile load loop
    • Recover speaker service
    • Fix convolver
    • Support Pixel devices
    • Use su.d if possible
    • Force global effect mode
    • Add Korean translation by @nebulac

    2.6.0.3
    • Fix /system install and uninstall.
    • Add temporary workaround for the convolver
    • Updated strings

    2.6.0.2
    • Fix FC while installing the driver
    • Add root check before installing the driver
    • Removed lucky patcher check
    • Capitalized driver status outputs
    • Updated strings

    2.6.0.1
    • Fix profile loading
    • Fix assets bug
    2.6.0.0
    • Initial Release
    101
    2.7.1.0 released

    Yay it's finally time to release an update

    And with this release come a few important release notes:
    Support for Magisk prior to v19 is dropped.
    If you did not use magisk, you need to reflash your /system partition and reinstall the driver
    An audio attach setting is added too to improve compatibility and it needs some explanation:
    For every time you play a song, the audio player should send information about what session the audio is played on, so equalizer apps can attach to that session.
    Session 0 is the default but deprecated session. Most of the time V4A processes just fine at session 0, but if it doesn't you can enable this switch and Viper will attach to other sessions. Note that if you don't have any session open, the driver status will say abnormal, which makes sense.
    There is the need for a switch, because in a lot of cases audio players do NOT send the information when a session is closed. So they keep the driver occupied and this mutes all other audio streams, including session 0 which is the fallback session.
    To make this problem a bit less bad, I excluded session 0. But when you still run into this problem, the solution is not to kill viper but to kill the audio app that was playing music previously.
    Bad design, I know. But it's not my fault. You should contact the developer of the music app to fix their crappy code and send a broadcast when audio playback stops/pauses.
    This switch makes ACP obsolete.

    Other things that have improved:
    I've seen multiple issues with android pie where the viper library wasn't detected any longer because a dependency is removed since the update. A workaround is shipped in the new release.
    The compatibility mode switch has been added back. This seems to be mandatory for car mode and some android q builds.
    An issue when loading presets has been resolved

    Download can be found on labs as always: Link
    91
    Answers to some related questions

    Help, the driver status says no
    • In case of Enabled: no; Please flip the Master limiter switch and go sit in a corner for a while
    • In case of Processing: no; If you use an application that uses audio sessions, enable session attaching in the settings. If that does not work, the audio is routed over session 0. You might want to try Audio Compatibility Patch from the Magisk repository in this case.

    What happened to the profiles?
    • They're now called presets. They are reworked to use independently per device, a feature that was very welcome. Because of many technical changes and improvements on how the preset is stored and loaded, they are not compatible with older versions than 2.7. You will have to recreate them by hand unfortunately. You can access the menu by pressing the selected device in case you missed the huge showcase when you first launched the app after installing the driver

    Why does your Magisk module not work?
    • Probably because you installed some other mod that also has an audio_effects file in it. Whatever module gets loaded last will become active
      The easiest way to bypass this is to let the app build a module after you installed all your favorite audio mods, and delete all files containing audio_effects in the other modules
      AudModLib will not come in handy this time, because the app doesn't flash a zip that AML can intercept

    Where can I find the source code?
    • You can't. And there is an obvious reason for that: This app is more sensitive to kangers who start selling this app, likely after adding their bullsh*t to it, rather than to people who actually want to help improve the app. Something like that already happened in the past to other audio software here on xda. Not really something we want to see happen again

    Where did the Selinux switch go?
    • What..? Are you really that careless security wise?
      The app handles this in a much more sophisticated way now. It injects only the absolute necessary rules to allow V4A to process, fully automatically

    Help, why do I still experience service drops?
    • Probably because doze is kicking in because Android doesn't like long running services. The service has been implemented the way the docs suggest. You can try excluding it from doze. Alternatively you can check out dontkillmyapp.com for tips

    Do you have a zip file for me?
    • No. There is no point in providing a zip file anymore. The driver installation is written from scratch and actually works now

    How do I uninstall the driver?
    • Use Magisk Manager to delete the module. If you use another root solution, you can dirty flash your rom or just leave it there