• 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

timofonic

Senior Member
The app itself is still in development, although not updated very frequently. But the driver has been always closed source and the original devs abandoned it long time ago

As an alternative you can try JamesDSP, although it's not that simple and straightforward to use as Viper
Is JamesDSP still in development too?

 

Lord Sithek

Senior Member
Is JamesDSP still in development too?

I think yes. But you can reach devs mostly on Telegram these days: https://t.me/jDSP_V4A
 

Lord Sithek

Senior Member
That team didn't post here since late 2020...
True, they're not active here. I don't know if they follow this thread, but I know that the main dev appears from time to time on the official Viper Telegram group:

https://t.me/Viper4Android FX

(Looks like big part of the community moved to Telegram these days 😉)

And from what I remember, the dev mentioned something about new release. But nobody knows when... As I said, the app seems to be still in development, but it's not rapid and if I understand correctly, it is al labout adjusting the app to the new Androids. And since the driver is closed source, the music quality and other features don't change
 

timofonic

Senior Member
S
True, they're not active here. I don't know if they follow this thread, but I know that the main dev appears from time to time on the official Viper Telegram group:

https://t.me/Viper4Android FX

(Looks like big part of the community moved to Telegram these days 😉)

And from what I remember, the dev mentioned something about new release. But nobody knows when... As I said, the app seems to be still in development, but it's not rapid and if I understand correctly, it is al labout adjusting the app to the new Androids. And since the driver is closed source, the music quality and other features don't change
So it's dead, Jim. We all are making necrophillia, unfortunately.

And this is a growing problem in Android, worsened by closed source projects. But there's Substratum, dead as hell despite being Open Source.

This demotivates me...
 
  • Like
Reactions: ProjectAlly

Sudhangshu

Senior Member
Hello guys
Hope everyone's doing fine and thanks a lot for providing us this awesome module. I wanted to install this module on my Oneplus3t and the thing is I didn't saw or may be I have missed installation instruction, so please can some provide me any link to instruction for installing viper4android.
I'm greatly grateful for your response.
Thank you very much.
 
Hello guys
Hope everyone's doing fine and thanks a lot for providing us this awesome module. I wanted to install this module on my Oneplus3t and the thing is I didn't saw or may be I have missed installation instruction, so please can some provide me any link to instruction for installing viper4android.
I'm greatly grateful for your response.
Thank you very much.
If you use MAGISK for root on your phone, it's a module that you can install from there, under the "Modules" section in the app. V4A on there is the latest version, it might work for you, or it might not, you'll have to try it.

If that doesn't work for you try these: 73sydney - XDA V4A Thread Post no. 5374. It's the older version (v2.7.1.6) that some (including myself) have had a lot of success with installing and using! If you're using MAGISK, just download those zip archives, and install through the "Modules" section of the app by selecting the option at that top that says "Install from Storage".
Simple to flash and just use, no other modules required to get it working.

Hope that helps :)
 

Sudhangshu

Senior Member
If you use MAGISK for root on your phone, it's a module that you can install from there. It's the latest version, it might work for you, or it might not, you'll have to try it.

If that doesn't work for you try these: XDA V4A Thread Post no. 5374. It's the older version (v2.7.1.6) that some (including myself) have had a lot of success with installing and using!

Hope that helps :)
Alright I'll try.
Thanks man.
 
  • Like
Reactions: ProjectAlly

Sudhangshu

Senior Member
If you use MAGISK for root on your phone, it's a module that you can install from there, under the "Modules" section in the app. V4A on there is the latest version, it might work for you, or it might not, you'll have to try it.

If that doesn't work for you try these: 73sydney - XDA V4A Thread Post no. 5374. It's the older version (v2.7.1.6) that some (including myself) have had a lot of success with installing and using! If you're using MAGISK, just download those zip archives, and install through the "Modules" section of the app by selecting the option at that top that says "Install from Storage".
Simple to flash and just use, no other modules required to get it working.

Hope that helps :)
Well hello I would like to confirm that your suggested method worked and really thanks for that, though I had one more question does this module can also be used to increase earpiece volume too.
 
  • Like
Reactions: ProjectAlly
Well hello I would like to confirm that your suggested method worked and really thanks for that, though I had one more question does this module can also be used to increase earpiece volume too.
Nice! Glad to hear that it worked!

Yes to increase volume, just play around with the "Playback gain control" option under the "Master power" setting in V4A. I think it has something to do with "strength and Maximum gain" in particular. Before moving the sliders take note of their default values, and then test all of those sliders and find what works for you. :)

On another note (not related to Sudhangshu's reply).

I've been testing Android 12 Beta 3 on my Pixel 5 with V4A, and have had no success.
Have resorted to using Wavelet for the time being, but am seriously tempted to just reflash the last July 2021 Android 11 update again and stick with it.

Not sure if anyone here is running A12 yet, but I can't figure out why after starting the service for V4A (Ichigo 2716), the app still auto closes after a few seconds. I feel like it has something to do with not being able to get access to having a persistent notification in the notification area, or it may have something to do with how the driver is being installed.

Have taken some time to dig through the Android manifest file for this version of V4A, noticed there's a lot of comments or lines dedicated to Android SDK 23, went through and changed all of these to version 31 (the latest available now I believe), but haven't tried adding this to the archive and reflashing through Magisk. Not even sure it's worth it to try, because that manifest file might not actually have anything to do with Viper being installed.

For me, if there aren't any issues with the Viper driver being installed (not sure), my main goal is to have a way to update and flash Viper (Ichigo 2716) on my own through any Android version going forward from Android 11. Because eventually in order to keep my Pixel 5 up to date, using Android 12 is going to happen. Can't stay on an older OS forever.

I just don't know where to start, or where to look to achieve this. Not trying to be a bother to anyone here either, including the devs, but they seem to have moved on possibly.

Lol maybe I care too much about audio quality, but it's difficult to listen to and really enjoy music/audio without V4A. Maybe there are alternatives, but nothing that scratches that itch. :D
 
  • Like
Reactions: Sudhangshu

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,556
5,309
Sydney
Me too! But it's a dead end, using zombie software. It's not a viable long term solution.
NOTHING about android is "long term". It is a constantly evolving environment that is guaranteed to change. Every year google puts out a new OS that kills functionality for many apps, and also breaks existing functionality that some would consider core (I know I am annoyed that in A11 they have broken non-embedded album art :mad:). Use it while you can, find work-arounds for others if you can.

Even if you find an app (Im talking non google type devs) that is under current development, there is no real guarantee that it will be the case tomorrow. But even Google have dropped projects that they once supported.
 
Last edited:

gfrank227

Senior Member
Feb 12, 2018
73
12
Moto G8 Plus
On another note (not related to Sudhangshu's reply).

I've been testing Android 12 Beta 3 on my Pixel 5 with V4A, and have had no success.
Have resorted to using Wavelet for the time being, but am seriously tempted to just reflash the last July 2021 Android 11 update again and stick with it.

Not sure if anyone here is running A12 yet, but I can't figure out why after starting the service for V4A (Ichigo 2716), the app still auto closes after a few seconds. I feel like it has something to do with not being able to get access to having a persistent notification in the notification area, or it may have something to do with how the driver is being installed.

Have taken some time to dig through the Android manifest file for this version of V4A, noticed there's a lot of comments or lines dedicated to Android SDK 23, went through and changed all of these to version 31 (the latest available now I believe), but haven't tried adding this to the archive and reflashing through Magisk. Not even sure it's worth it to try, because that manifest file might not actually have anything to do with Viper being installed.

For me, if there aren't any issues with the Viper driver being installed (not sure), my main goal is to have a way to update and flash Viper (Ichigo 2716) on my own through any Android version going forward from Android 11. Because eventually in order to keep my Pixel 5 up to date, using Android 12 is going to happen. Can't stay on an older OS forever.

I just don't know where to start, or where to look to achieve this. Not trying to be a bother to anyone here either, including the devs, but they seem to have moved on possibly.

Lol maybe I care too much about audio quality, but it's difficult to listen to and really enjoy music/audio without V4A. Maybe there are alternatives, but nothing that scratches that itch. :D
This general issue is part of the reason why I tend to buy my phones one generation back. (the other reason is that they are MUCH cheaper). I'm running A10; it would be nice to get A11, but I don't think Motorola will be giving my phone A11. That's fine with me; i believe in the idea of, "if it ain't broke, don't fix it."

Hopefully by the time I am forced to use A12, someone will have figured it out. Keep us posted, please. I'm sure it would benefit the entire community.

I agree with you - I can tell an immediate difference on my headphones with or without V4A. I'm not sure I could ever do without it. I suppose James would work, but it would not be the same. So long live V4A.
 
  • Like
Reactions: ProjectAlly

gfrank227

Senior Member
Feb 12, 2018
73
12
Moto G8 Plus
Well hello I would like to confirm that your suggested method worked and really thanks for that, though I had one more question does this module can also be used to increase earpiece volume too.
Out of curiosity, were you able to simply install the drivers and it worked right away? Or did you have to play with it, such as installing and then disabling Audio Modifications Library like some, including myself, have needed to do?
 

Sudhangshu

Senior Member
Out of curiosity, were you able to simply install the drivers and it worked right away? Or did you have to play with it, such as installing and then disabling Audio Modifications Library like some, including myself, have needed to do?
No nothing like that, i just flashed the magisk module reboot my device and after it when I open the app it asked me whether I want to install drivers and that's it.
 

gfrank227

Senior Member
Feb 12, 2018
73
12
Moto G8 Plus
For those with Android 12, see the following thread - several people are reporting that they got it working.

 

maxmopp

Member
Jul 21, 2011
8
0
If you use MAGISK for root on your phone, it's a module that you can install from there, under the "Modules" section in the app. V4A on there is the latest version, it might work for you, or it might not, you'll have to try it.

If that doesn't work for you try these: 73sydney - XDA V4A Thread Post no. 5374. It's the older version (v2.7.1.6) that some (including myself) have had a lot of success with installing and using! If you're using MAGISK, just download those zip archives, and install through the "Modules" section of the app by selecting the option at that top that says "Install from Storage".
Simple to flash and just use, no other modules required to get it working.

Hope that helps :)
I had a selinux deny:
07-26 15:07:13.329 13850 13850 I HwBinder:13850_: type=1400 audit(0.0:333): avc: denied { execmem } for scontext=u:r:hal_audio_default:s0 tcontext=u:r:hal_audio_default:s0 tclass=process permissive=1

I could get 2.7.2.1 to work (A11/LOS18) by adding to sepolicy:
supolicy --live "allow hal_audio_default hal_audio_default process { execmem }"
that same allow is in /data/adb/modules/ViPER4AndroidFX/sepolicy.rule - why that did not work I dont know
 

Cruzy12100

Senior Member
Oct 15, 2014
150
12
Chennai
OnePlus Nord
If you use MAGISK for root on your phone, it's a module that you can install from there, under the "Modules" section in the app. V4A on there is the latest version, it might work for you, or it might not, you'll have to try it.

If that doesn't work for you try these: 73sydney - XDA V4A Thread Post no. 5374. It's the older version (v2.7.1.6) that some (including myself) have had a lot of success with installing and using! If you're using MAGISK, just download those zip archives, and install through the "Modules" section of the app by selecting the option at that top that says "Install from Storage".
Simple to flash and just use, no other modules required to get it working.

Hope that helps :)

Thanks to your fix the viper service is running again. One question though, since the driver version is slightly old (2.5.x.x), will it make a difference as to how the processing happens. As after applying my earlier settings it feels a little "flat".

Also is there a Link I can refer for applying the recommended settings or something like that. I installed the permissive version.

Earlier android version was 10 current version is 11.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Problem solved. I installed audio compatibility patch and modification library. Removed all mods and cleaned up. Then followed this guide flashed trough recovery dolby atmos and then ViperFX provided there. Dolby app is not present, I'm not sure if it even gave any result. But ViperFX is working finally without errors and I'll leave it there.
    This works !
    1
    viper4android latest magisk module not working on:
    POCO F1
    Pixel Experience Plus ROM
    Android 11
    Magisk v23
    SELinux: Enforcing
    There many posts describing how to install, generallythere are two methods (AML or MagiskPolicy rules), and the same can be found also in different other threads on XDA, Telegram channels, YouTube, elswhere.
    Please do some search and try.
    I have Mi 9T with A11 and V4A works with no issues (installed by using Magiskpolicy rules in the module's post-fa-data.sh script
    1
    Yes this is literally the same method EVERYONE'S been talking about for a while now. It would be something if it showed how to use Viper on A11 without legacy needing to be enabled while still enforcing SElinux.
    1
    Hi,
    I am currently using the latest version in mi mix 2 with crDriod Android 11; It works, but I cannot create/edit/delete/rename presets; If I try, nothing happens, e.g. ... If I create a new profile, it seems to work, but if I go back to profiles, it is not there.

    The same happens renaming, etc.: The app does not complaint, but it does nothing.

    In the preset associated folders there is nothing...
    1
    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.
  • 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
    132
    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