• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

gfrank227

Senior Member
Feb 12, 2018
78
12
Moto G8 Plus
I see comments here giving people a hard time for not doing a "more detailed search" to get this to work but I would reply with the facts that

you use to always just be able to install it from magosk repo and people are use to that.

if the default way changed, it should be documented in the release notes of the package.

I see an update came out weeks ago and the latest release note showing in magisk is from almost a year ago to the day.

so go ahead and give then a hard time (whatever makes you feel superior and better about yourselves) but I would say the lack of documentation in release notes is the real problem.

even if it's too much info, give people a heads up. either way, it's no excuse to stop documenting why updates are being released in the place most users grab it from.

seeing how people are replied to with such attitude when the Dev couldn't even be bothered to update revisions makes me happy I found a better solution due to this apps lack of functionality / documentation

EDIT. not only does it have no revision updates for almost. a year now, the first paragraph is written as if you would be stupid to a assume more would be needed to be done via its "no hacky workarounds" and that the app "handles ALL of that now" good grief.
I agree with you about people giving others a hard time. I don't understand why people would want to do this.
 
Aug 31, 2021
34
4
How would we determine if this module is breaking the sound in LineageOS 18.1?

Sound in general is not working and this began after installing a driver provided by this module - sound stopped working after reboot and now i can't uninstall this module and restore sound.
 

Sherlock1123

Member
Mar 17, 2016
23
3
Ahmedabad
Oneplus 5
OOS 10.0.1
Magisk 23
blu_spark r225 (if it matters)

I can't get it to work when I flash the latest magisk zip along with AML, even with Legacy and compatibility on.

But, when I install app version 2.7.1.0 and AML it works perfectly. It works even after I upgrade the app to latest 2.7.2.1 version. It again stops working if I update the magisk module to latest and it doesn't work if I install the later two updates of app directly.

I don't get it. Can somebody enlighten me why?
Should I just leave it that? Don't fix what's not broken or am I missing out on any latest features? Driver version is the same, 2.5.0.4.
 
Last edited:

jrootmirror

New member
Jun 19, 2018
1
0
Got Viper working on my OnePlus 9 Pro (EvolutionX) using 2.7.1.6, no Legacy mode or permissive kernel required.
 

Attachments

  • Screenshot_20210914-043211_ViPER4Android_FX.png
    Screenshot_20210914-043211_ViPER4Android_FX.png
    842.5 KB · Views: 224
  • Screenshot_20210914-043140_Settings.png
    Screenshot_20210914-043140_Settings.png
    770.2 KB · Views: 228
  • Screenshot_20210914-043219_ViPER4Android_FX.png
    Screenshot_20210914-043219_ViPER4Android_FX.png
    473.7 KB · Views: 228

Sherlock1123

Member
Mar 17, 2016
23
3
Ahmedabad
Got Viper working on my OnePlus 9 Pro (EvolutionX) using 2.7.1.6, no Legacy mode or permissive kernel required.
I am on OnePlus 5, 10.0.1, I got it working with 2.7.1.0. But when I update the module in Magisk it doesn't work, though updating the app to latest 2.7.2.1 is fine. Does the same happen with you?

Can you please take a look at my comment just above yours and see if you can provide some input.

Thank you.
 

idiocracy_

Member
Jul 12, 2021
7
0
Maybe someone here can help getting this to work.
Have a 1+7 with latest A11 updated installed, latest Viber4android from magisk.
If I have compatible on the fence icon Grey's out.
If I have lagacy off/on, the fence icon is normal but when you click it, both activated and treating says no.
Neon activated, yes.
Status, normal.
Sound format, supported.

I have two magisk modules installed, Google framework and Viber4android.

I just don't seem to be able to get it to work, at all, and I have no idea why.
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,617
5,393
Sydney
Maybe someone here can help getting this to work.
Have a 1+7 with latest A11 updated installed, latest Viber4android from magisk.
If I have compatible on the fence icon Grey's out.
If I have lagacy off/on, the fence icon is normal but when you click it, both activated and treating says no.
Neon activated, yes.
Status, normal.
Sound format, supported.

I have two magisk modules installed, Google framework and Viber4android.

I just don't seem to be able to get it to work, at all, and I have no idea why.
The following ZIp has worked for a number of users running A11 (I havent herd opf anyone it has failed for...). I would first revert all the changes / modules / settings you have modified up to this point (ie start clean) and then try the following Magisk install (not from the repository)
 

idiocracy_

Member
Jul 12, 2021
7
0
The following ZIp has worked for a number of users running A11 (I havent herd opf anyone it has failed for...). I would first revert all the changes / modules / settings you have modified up to this point (ie start clean) and then try the following Magisk install (not from the repository)

I uninstalled viper4android, rebooted, installed your zip, rebooted. Now sim is not detected and app opens to a black screen. Uninstalled it, rebooted, sim not detected after reboot. Also oneplus boot animation was gone.

Edit. Uninstalled it, reinstalled the firmware to the second slot only keeping Google framework. Sim still not detected, re-inserting the sim does not help.
Don't know how to undo whatever this did
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,617
5,393
Sydney
I uninstalled viper4android, rebooted, installed your zip, rebooted. Now sim is not detected and app opens to a black screen. Uninstalled it, rebooted, sim not detected after reboot. Also oneplus boot animation was gone.

Edit. Uninstalled it, reinstalled the firmware to the second slot only keeping Google framework. Sim still not detected, re-inserting the sim does not help.
Don't know how to undo whatever this did
It is purely a Magisk install, so it is all systemless.And its not "my" zip.

It installs a module (which can be deleted within magisk) abd a serviced.d script.
 

gladykov

Member
Jul 12, 2010
24
3
Any hope to support processing of Tidal FLAC in the future? James DSP is just not giving me convincing results

BTW. Viper works on my Sony ZX1 Compact with Lineage OS 18.1 for Spotify
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,617
5,393
Sydney
Any hope to support processing of Tidal FLAC in the future? James DSP is just not giving me convincing results

BTW. Viper works on my Sony ZX1 Compact with Lineage OS 18.1 for Spotify
That makes it 100% clear you have done something incorrect, and probably failed to clear all your previous attempts.

The Viper app IS installed as part of the Magisk module. If you had to uninstall an app after removing the magisk module, then you clearly had leftovers from some other attempt.
 
Last edited:

Yassinbadr

New member
Jan 7, 2021
2
0
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

(An error occurred while mounting system. Please try again. Contact the developers if this problem persists)
😕 I'm using Redmi Note 5 Pro
 

jojy thomas

Senior Member
Sep 13, 2016
54
14
Kottayam
Oneplus 5
OOS 10.0.1
Magisk 23
blu_spark r225 (if it matters)

I can't get it to work when I flash the latest magisk zip along with AML, even with Legacy and compatibility on.

But, when I install app version 2.7.1.0 and AML it works perfectly. It works even after I upgrade the app to latest 2.7.2.1 version. It again stops working if I update the magisk module to latest and it doesn't work if I install the later two updates of app directly.

I don't get it. Can somebody enlighten me why?
Should I just leave it that? Don't fix what's not broken or am I missing out on any latest features? Driver version is the same, 2.5.0.4.
same thing happened to me, I'm using latest los on poco f1, latest update rip my viper, it says unsupported audio, could you send me the working magisk module
 

gladykov

Member
Jul 12, 2010
24
3
That makes it 100% clear you have done something incorrect, and probably failed to clear all your previous attempts.

The Viper app IS installed as part of the Magisk module. If you had to uninstall an app after removing the magisk module, then you clearly had leftovers from some other attempt.
I think you read my post wrong ☺️ I was stating it works , asking for possibility of Tidal FLAC support in the future
 

Top Liked Posts

  • There are no posts matching your filters.
  • 526
    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
    133
    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]
    115
    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
    89
    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