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

Search This thread

Ragnar Eldur

Senior Member
Jul 22, 2016
639
238
After version 23 the module download list was removed. Just use version 23 to get the modules and follow the video instructions to properly install the Viper4Android. Several people have confirmed this method fully working. 🙂
 

zgfg

Senior Member
Oct 10, 2016
7,952
5,491
After version 23 the module download list was removed. Just use version 23 to get the modules and follow the video instructions to properly install the Viper4Android. Several people have confirmed this method fully working. 🙂
Do you really say that the point for Magisk v23 in your 'method' is in Modules downloading?!

Are you up to date with Magisk v24/v25?
Have you heard of Fox Magisk Module Manager:

By using that app you can find and install all modules to Magisk v25, and not only from the old (frozen) Modules Repository but also from three new repositories as well (with lot of new modules)

But anyway, with that app you can find and install all of your modules ACP, AML, V4A and JDSP if you wish.
You don't need Magisk v23 for installing those modules from the repos!

Not to mention that all those modules can be easily googled and found on GitHub, downloaded manually to the phone and installed to Magisk v25 by use of Install from storage option

Btw, there is a thread devoted to the new Magisk, and all these things like why Modules repo was removed from v24/v24, and how to use instead that FMMM app, and many other instructions about the new things like Zygisk etc can be learnt from the OP posts on the first page:
 

zgfg

Senior Member
Oct 10, 2016
7,952
5,491
Eh, really? The recent versions of Magisk don't support the recent versions of Viper, or vice versa? What happened there?

Is this why the driver never gets installed properly in Viper when installed as a Magisk module? Since several years back the only way to get the driver properly installed is to flash Viper in a custom recovery. But I'm running android 13 on a Pixel 6 and there are no custom recoveries for this phone.

I appreciate your suggestion, but there are also warnings of running old versions of Magisk in several places of the Pixel 6 forum. Is this really safe?
Of course that going to the old, unsupported version of Magisk is risky.
It was deployed at the times of A10 and maybe A11, no guarantee that it will work for new devices deployed with A12 and upcoming A13

Even if you may manage to install, you may have problems with OTA, etc

Leave that usage of the old and deprecated Magisk v23 to those who have old devices (and old ROMs) from those times

Moreover, with that old Magisk v23 you have no Zygisk, you cannot use the new modded USNF to pass the new Play Integrity API and you won't be able to use eg the new Wallet (and other apps are coming to check for PI)

Additional safety concern - that method (at the end of the video instructions) requires to force SELinux Permissive mode. By no mistake, many banking apps will immediately find it and declare your device as unsecure (rooted), not allowing to work on your phone
 
Last edited:

RobbyRobbb

Senior Member
Aug 17, 2012
170
32
Use Magisk to install Viper4Android. Uninstall the latest Magisk and install this version:


There you can search for the 3 modules needed for Viper4Android to work correctly.

Here's a solid video instruction how to install the Viper4Android correctly:


Still doesn't work. I've installed the audio modification library, the audio compatibility patch, Viper4AndroidFX, and set setenforce to 0 and the problem remains; Viper insists that no driver is installed and wants to install it. After a reboot it says the same thing.

I haven't had to use the modification library or the compatibility patch since several years back on other phones. Once the driver was installed it worked fine in all apps. The problem since maybe three years back is that the driver doesn't install *unless* I flash Viper in a custom recovery. That step alone used to be the only one necessary. No other modules required and no need to set SELinux to permissive or off. It just worked. Installing it through Magisk however always results in some kind of failure. But since no custom recovery exists for the Pixel 6 the problem with the driver remains.
 
Last edited:
  • Like
Reactions: Undeadwolfy

Ragnar Eldur

Senior Member
Jul 22, 2016
639
238
Still doesn't work. I've installed the audio modification library, the audio compatibility patch, Viper4AndroidFX, and set setenforce to 0 and the problem remains; Viper insists that no driver is installed and wants to install it. After a reboot it says the same thing.

I haven't had to use the modification library or the compatibility patch since several years back on other phones. Once the driver was installed it worked fine in all apps. The problem since maybe three years back is that the driver doesn't install *unless* I flash Viper in a custom recovery. That step alone used to be the only one necessary. No other modules required and no need to set SELinux to permissive or off. It just worked. Installing it through Magisk however always results in some kind of failure. But since no custom recovery exists for the Pixel 6 the problem with the driver remains.
Did you do the installation in the right order and exactly as done in the video?
 

R77

Senior Member
Apr 27, 2013
332
8
I have the Note 9 rooted with magisk V25.2 with NOBLE ROM 2.6. I have ViPER4Android FX Legacy Materialized v4.4 (2.5.0.5). I flashed Dolby Digital Plus v7.3 then viper4Android and AML. The phone rebooted and I got this error when installing the drivers in viper Android pic down below. I even flashed the selinux changer in magisk and made it to permissive, but still the same. Any help?
SmartSelect_20220919_163706_ViPER4Android FX.jpg
 
i too am facing the same problem with my pixel 6 pro and android 13. driver install loop. everyone with a pixel 6 pro is having similar issues but no one has seemed to have it working. does anyone know how to get in touch with team dewitt? maybe see if they can share some light? it seems to be specific to the 6 pro for some reason.
 

ImRit

Member
Apr 7, 2022
6
0
Hi, today I reinstalled magisk and viper don't want install driver like a magisk module, it's just trying to install into system partition, but it can't to mount it because my phone(Redmi note 9) from factory on 10 android, just anyone help me to fix this issue, I means fix viper's installation of magisk module, waiting for help.
 

zgfg

Senior Member
Oct 10, 2016
7,952
5,491
Hi, today I reinstalled magisk and viper don't want install driver like a magisk module, it's just trying to install into system partition, but it can't to mount it because my phone(Redmi note 9) from factory on 10 android, just anyone help me to fix this issue, I means fix viper's installation of magisk module, waiting for help.
Try this module:

Scroll down, download latest zip, install from Magisk app, Modules, take Install from storage and navigate to the downloaded zip (as a Magisk module, it must be installed from the Magisk app, not through TWRP or so)
 

Kastilo

Member
Jun 30, 2016
22
12
Hurlante
Google Pixel 6 Pro
i too am facing the same problem with my pixel 6 pro and android 13. driver install loop. everyone with a pixel 6 pro is having similar issues but no one has seemed to have it working. does anyone know how to get in touch with team dewitt? maybe see if they can share some light? it seems to be specific to the 6 pro for some reason.
To answer the issues with the Pixel 6 devices and Android 13. Google seems to have decided to enforce a 64bit library requirement for some drivers, like audio. Due to this, Viper4Android does not work as it does not have 64bit drivers built for it. The original driver built by the ViperFX team is closed source, meaning that unless they either open source it or update it themselves, V4A will no longer work on ROMS requiring the 64bit driver.

There are ongoing projects to reverse engineer the V4A driver code but none of them have given fruit to a mature fully working driver. There is nothing that the two app devs can do, as all they did was write a new GUI to interact with the driver and make it systemless but couldn't more deeply modify the core because of the aforementioned closed source nature of the original project
 
To answer the issues with the Pixel 6 devices and Android 13. Google seems to have decided to enforce a 64bit library requirement for some drivers, like audio. Due to this, Viper4Android does not work as it does not have 64bit drivers built for it. The original driver built by the ViperFX team is closed source, meaning that unless they either open source it or update it themselves, V4A will no longer work on ROMS requiring the 64bit driver.

There are ongoing projects to reverse engineer the V4A driver code but none of them have given fruit to a mature fully working driver. There is nothing that the two app devs can do, as all they did was write a new GUI to interact with the driver and make it systemless but couldn't more deeply modify the core because of the aforementioned closed source nature of the original project
Thanks for the explanation, it all makes sense now too. Might have to jump off the pixel ship strictly because of this. Leave it to Google to make you update then take away the ability to downgrade and lose probably the single most important mod (imo) that I've used for longer than Ive had a pixel. Thanks Google :(
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,493
6,462
Sydney
To answer the issues with the Pixel 6 devices and Android 13. Google seems to have decided to enforce a 64bit library requirement for some drivers, like audio. ...
...snip...
Is there a list somewhere of devices they have done this to? I have a Pixel 4a 4G, and i can only assume i am going to be in the same boat; ViperFX is a deal breaker for any new phone/ROM.
 

SCrid2000

Senior Member
Jun 13, 2011
442
89
Puyallup, WA
To answer the issues with the Pixel 6 devices and Android 13. Google seems to have decided to enforce a 64bit library requirement for some drivers, like audio. Due to this, Viper4Android does not work as it does not have 64bit drivers built for it. The original driver built by the ViperFX team is closed source, meaning that unless they either open source it or update it themselves, V4A will no longer work on ROMS requiring the 64bit driver.

There are ongoing projects to reverse engineer the V4A driver code but none of them have given fruit to a mature fully working driver. There is nothing that the two app devs can do, as all they did was write a new GUI to interact with the driver and make it systemless but couldn't more deeply modify the core because of the aforementioned closed source nature of the original project
Is there any way to bypass that? I'm guessing no.
 

Kastilo

Member
Jun 30, 2016
22
12
Hurlante
Google Pixel 6 Pro
Is there a list somewhere of devices they have done this to? I have a Pixel 4a 4G, and i can only assume i am going to be in the same boat; ViperFX is a deal breaker for any new phone/ROM.
Seems any Google device that gets the Stock update for Android 13 has this limiter as far as I can tell
Is there any way to bypass that? I'm guessing no.
Custom ROMS that allow for 32bit drivers to be used... other than that no, there's no bypass. For now JamesDSP does have 64bit binaries with the Huawei option. You do need Audio Compatibility Patch but otherwise works fine, sadly the app isn't as friendly as the Viper4Android app
 
  • Like
Reactions: DiamondJohn

rubnduardo

Member
Nov 23, 2012
37
11
Maracaibio
I'm on P3XL pixeldust A13 Magisk latest + foxmanager. I installed from the manager and Magisk app shows it's installed but there's nothing else around, no app, nothing. I think it's unsupported? Can't find info about it.

I'd love some help. Thanks in advance.

PS: if you read this and know how to change bootanimation in my setup please tell me, thank you.
 
  • Like
Reactions: fallenangel1389

gokou46

Senior Member
Mar 3, 2011
212
6
Hey guys i was able to install viper but i get this error on the bottom and i don't know what to do. I also have them in the right place but. I click on convolver and than click on impulse response i get this error. Also running anriod 12.1
 

Attachments

  • Screenshot_20221016-133249_FX.png
    Screenshot_20221016-133249_FX.png
    265.9 KB · Views: 55
  • Screenshot_20221008-200019_ViPER4Android FX.png
    Screenshot_20221008-200019_ViPER4Android FX.png
    173.2 KB · Views: 55
  • Like
Reactions: BostonDan

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    jeez i thought this was about viper4android fx
    Indeed, well said.
    Now the official reminder: Pls stay on topic 😎

    Cheers
    3
    jeez i thought this was about viper4android fx
    3
    Have you tried the V4A module by programminghoch10?
    swieder711 has to wait because Google changed the architecture on the Pixel 7 Pro to be 64-bit only ... V4A uses old 32-bit.
    Right now someone is trying to reverse engineer V4A (As it's closed source)
    2
    I just flashed my old Pixel 4a 5G to Oct 22, and completely wiped everything out to OOB condition. Rooted with magisk and downloaded this version of viper. Following instructions, I rebooted and then ran Viper, which DID prompt me to install the driver, rebooted again, opened viper successfully, enabled legacy mode and turned on a couple of switches, hit play in youtube music and am successfully processing YES on the status screen.

    I have to wait a few more weeks until my P6P gets unlocked so I can root it, but this is fantastic! Ill dual phone in the car until then. Btw, I dont know how close most of you listen to the audio quality, but the P6 does a better job of playback than the P4.

    mmarczView attachment 5751729

    I tested this on my P6 (A13, Oct), and it was just giving the driver missing error even after letting it install the driver and reboot.
    2
    Yeah, I I follow the telegram group and try every update but I too end up with driver loop.
    Someone in the telegram group claims to have reverse engineered viper, and got it working on 64bit android. They won't release anything at this time, so for now, we are SOL.
  • 541
    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
    92
    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