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

Search This thread
I just found these somewhere here
just install the apk first but dont install the driver, instead install the module and aml

Oneplus 8T OOS 12

 

Attachments

  • Audio-Modification-Library_v4.1.zip
    13.1 KB · Views: 43
  • Viper4AndroidFXRepack.zip
    399.3 KB · Views: 64
  • 20201028-ViPER4AndroidFX-2.7.2.1.apk
    8.8 MB · Views: 118

Lord Sithek

Senior Member
Dec 19, 2018
1,224
625
Xiaomi Redmi Note 4
Huawei Watch 2
  • Like
Reactions: xn0live

BatZzn

Senior Member
Nov 20, 2011
548
131
I have several apps that won't work with viper. Some games and Stadia for example.In general I need to set legacy mode in viper options to get it working at all. With legacy mode Spotify and YouTube are working, but other apps not. I already tried compatibility mode, but the result is the same. I use magisk. Does anybody know what to do?
 

Eowieh

New member
Feb 14, 2020
4
0
Can I use v4a if I don't have Magisk? My phone is rooted, though (this way).

I suppose I'd need the apk. However, with the closing of XDA Labs, the apk seems to have become unavailable.
 

Lord Sithek

Senior Member
Dec 19, 2018
1,224
625
Xiaomi Redmi Note 4
Huawei Watch 2
Can I use v4a if I don't have Magisk? My phone is rooted, though (this way).

I suppose I'd need the apk. However, with the closing of XDA Labs, the apk seems to have become unavailable.
Viper should work with all root solutions. The latest apk you can download from Telegram Channel.
 
  • Like
Reactions: Eowieh

zgfg

Senior Member
Oct 10, 2016
7,933
5,474
Can I use v4a if I don't have Magisk? My phone is rooted, though (this way).

I suppose I'd need the apk. However, with the closing of XDA Labs, the apk seems to have become unavailable.
V4A installs as Magisk module.
It installs sound overlay files to
/data/adb/modules/ViPER4AndroidFX
where Magisk is supposed to read and process on every reboot

Even the V4A app does the same - at least for the phones rooted with Magisk

However, you could try with V4A app as suggested (maybe the app might detect that your phone is rooted and System is not read-only and make the changes directly to the System instead of through the Magisk mount/overlay mechanism).
I never tried that way (and cannot on my phones with read-only SAR where rooting works only the systemless way with Magisk - all new phones)

Btw, good to see that good, old Huawei P9 is still in use
 
Last edited:
  • Like
Reactions: Eowieh

sachinachude

Member
Aug 9, 2020
8
0
Screenshot_20220720-202617.png
any solution not working on Android 11 Nokia 2.3 with mtk processor and magisk 24.3.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,488
6,457
Sydney
... SNIP over-sized image please everyone, use THUMBNAILS...

any solution not working on Android 11 Nokia 2.3 with mtk processor and magisk 24.3.
Have you tried the following? Its worked for me every-time on multiple A11 ROMs. And for others.
 

Eowieh

New member
Feb 14, 2020
4
0
V4A installs as Magisk module.
It installs sound overlay files to
/data/adb/modules/ViPER4AndroidFX
where Magisk is supposed to read and process on every reboot

Even the V4A app does the same - at least for the phones rooted with Magisk

However, you could try with V4A app as suggested (maybe the app might detect that your phone is rooted and System is not read-only and make the changes directly to the System instead of through the Magisk mount/overlay mechanism).
I never tried that way (and cannot on my phones with read-only SAR where rooting works only the systemless way with Magisk - all new phones)

Btw, good to see that good, old Huawei P9 is still in use
Report of my experience:

I installed the ViPER4Android FX app. Upon entering it, it shows a message

No driver found

Do you wish to install the driver now?

Cuation: Your device will reboot automatically. Make sure your session is saved.

So, I tap "OK".

However, when the system has rebooted and I enter the app again, it will again show "No driver found". Same in the "driver status" window.

---
Should I try flashing the zip?
 

sachinachude

Member
Aug 9, 2020
8
0
Have you tried the following? Its worked for me every-time on multiple A11 ROMs. And for others.
I have tried this. Not working . Any other solution.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,488
6,457
Sydney
I have tried this. Not working . Any other solution.
Have you checked if you have ANY other sound modifications/equalizers?

In my Music player (Vinyl Music Player from the play store), I can go to the song full screen (as opposed to just playing a selected song from the list) then use the menu to pull up the active equalizer. If it does not pull up viper, then you have to disable the one it IS pulling up.
 

sachinachude

Member
Aug 9, 2020
8
0
Have you checked if you have ANY other sound modifications/equalizers?

In my Music player (Vinyl Music Player from the play store), I can go to the song full screen (as opposed to just playing a selected song from the list) then use the menu to pull up the active equalizer. If it does not pull up viper, then you have to disable the one it IS pulling up.
I am using James DSP and working very fine.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,488
6,457
Sydney
I am using James DSP and working very fine.
Generally speaking, you should only have a single audio modification when running Viper; and with viper I mean viper only. The Magisk module actually explicitly disables ones found commonly on other ROMs; but not JamesDSP. Installing more than one at the same time is asking for it to fail. Some may get it to work, but its not the way to go, especially when you are having problems. Try each, but uninstall so you only have one, for better chances of them working.
 

sachinachude

Member
Aug 9, 2020
8
0
Generally speaking, you should only have a single audio modification when running Viper; and with viper I mean viper only. The Magisk module actually explicitly disables ones found commonly on other ROMs; but not JamesDSP. Installing more than one at the same time is asking for it to fail. Some may get it to work, but its not the way to go, especially when you are having problems. Try each, but uninstall so you only have one, for better chances of them working.
I had removed jamesDSP then clean installed viper but no luck (i have used single magisk module but have same problem). Same viper magisk module working fine with Android 10 on another device. Both devices are from same brand Nokia but different thing is that they are from different processor like Android 10 on snapdragon and Android 11 on mediatek.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Update: After looking myself, I found out that the old Viper4Android FX(v2.7.2.1) doesn't work on Android 13. But there's a new version called Viper4Android Repackaged that is updated and does work on Android 13.
    Link: https://github.com/programminghoch10/ViPER4AndroidRepackaged
    3
    jeez i thought this was about viper4android fx
    3
    jeez i thought this was about viper4android fx
    Indeed, well said.
    Now the official reminder: Pls stay on topic 😎

    Cheers
    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.
  • 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