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

Search This thread

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
5,985
13,827
31
Ambala
OnePlus 9R
As I am sure you are aware, the majority of post-fs-data.sh fixes I have seen are SELinux allows. Your ZIP uses the sepolicy.rule file to achieve the same.
Yes, I'm aware. I should've been more clear. :) I just meant the SELinux allows are being taken care of in the recommended way (using sepolicy.rule) without moving them to post-fs-data.sh and using magiskpolicy (which is the old, traditional way).
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,070
5,955
Sydney
Yes, I'm aware. I should've been more clear. :) I just meant the SELinux allows are being taken care of in the recommended way (using sepolicy.rule) without moving them to post-fs-data.sh and using magiskpolicy (which is the old, traditional way).
The other thing I noted, but forgot to mention, which obviously is fine for you, but others running different ROMs may need to add, is the removal of existing pre-installed equalizers in their ROMs. In the module I use, it removes MusicFX and AudioFX , at least one of which has been used previously in LOS based ROMs I have run. Don't know if they include it in more recent Android builds. Its not required in my Pixel device either, but its there by default.

I also compared your permissions XML with the one installed (and working) on my device, and found the following weren't in yours.
Code:
android.permission.ACCESS_SUPERUSER
android.permission.BLUETOOTH
android.permission.WRITE_EXTERNAL_STORAGE
The one I am running was missing android.permission.FOREGROUND_SERVICE which sounds pretty instrumental, but hasn't appeared to cause issues. I haven't run APPT against the APK to check (ie manually create the permissions file from the APK). I understand we are running different versions, and there is no use assigning a permission if its not requested/used by the APK, and superuser is only used to install the driver, which the module already solves.

Its all just an FYI.
 
  • Like
Reactions: shadowstep

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
5,985
13,827
31
Ambala
OnePlus 9R
The other thing I noted, but forgot to mention, which obviously is fine for you, but others running different ROMs may need to add, is the removal of existing pre-installed equalizers in their ROMs. In the module I use, it removes MusicFX and AudioFX , at least one of which has been used previously in LOS based ROMs I have run. Don't know if they include it in more recent Android builds. Its not required in my Pixel device either, but its there by default.
That's correct. This Audio Mod Troubleshooting Guide is pretty comprehensive as well, and may prove to be beneficial if anyone is having trouble getting V4A to work.

I also compared your permissions XML with the one installed (and working) on my device, and found the following weren't in yours.
Code:
android.permission.ACCESS_SUPERUSER
android.permission.BLUETOOTH
android.permission.WRITE_EXTERNAL_STORAGE
The one I am running was missing android.permission.FOREGROUND_SERVICE which sounds pretty instrumental, but hasn't appeared to cause issues. I haven't run APPT against the APK to check (ie manually create the permissions file from the APK). I understand we are running different versions, and there is no use assigning a permission if its not requested/used by the APK, and superuser is only used to install the driver, which the module already solves.
I generated the permissions XML using AAPT only; used it against latest available version of the app, i.e. v2.7.2.1 (which is also the version present in my module).
 
Last edited:

vibrantliker

Senior Member
That's correct. This Audio Mod Troubleshooting Guide is pretty comprehensive as well, and may prove to be beneficial if anyone is having trouble getting V4A to work.


I generated the permissions XML using AAPT only; used it against latest available version of the app, i.e. v2.7.2.1.
I wondered if either @shadowstep or @DiamondJohn may be able to help me.
I've been using viper for probably at least 10 years? Since getting into a more high-fidelity/audiophile world, I have continued to use my phone as the source as I don't know anything else that can sound as good as Viper.

On it's own (straight from phone to headphones) viper works fine but when I use an external dac (RME ADI-2 DAC) or any other external dac, occasionally I get unbearable sounds when skipping tracks. It comes in a variety of different ways, like a squelching feedback, or an unusual distortion among others. I have to unplug my phone from the dac to clear it. I've learned to deal with it but wondered if either of you (or anyone) has ever experienced this or knows a fix.

I've never experimented if it happens without Viper enabled but will try that today.

Update: Does not happen without Viper enabled.
 
Last edited:

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
5,985
13,827
31
Ambala
OnePlus 9R
I wondered if either @shadowstep or @DiamondJohn may be able to help me.
I've been using viper for probably at least 10 years? Since getting into a more high-fidelity/audiophile world, I have continued to use my phone as the source as I don't know anything else that can sound as good as Viper.

On it's own (straight from phone to headphones) viper works fine but when I use an external dac (RME ADI-2 DAC) or any other external dac, occasionally I get unbearable sounds when skipping tracks. It comes in a variety of different ways, like a squelching feedback, or an unusual distortion among others. I have to unplug my phone from the dac to clear it. I've learned to deal with it but wondered if either of you (or anyone) has ever experienced this or knows a fix.

I've never experimented if it happens without Viper enabled but will try that today.

Update: Does not happen without Viper enabled.
I've never used an external DAC, so this is out of my wheelhouse. Sorry!
 

Wishmasterflo

Senior Member
Nov 21, 2018
1,225
714
Stockholm
OnePlus 8T
I wondered if either @shadowstep or @DiamondJohn may be able to help me.
I've been using viper for probably at least 10 years? Since getting into a more high-fidelity/audiophile world, I have continued to use my phone as the source as I don't know anything else that can sound as good as Viper.

On it's own (straight from phone to headphones) viper works fine but when I use an external dac (RME ADI-2 DAC) or any other external dac, occasionally I get unbearable sounds when skipping tracks. It comes in a variety of different ways, like a squelching feedback, or an unusual distortion among others. I have to unplug my phone from the dac to clear it. I've learned to deal with it but wondered if either of you (or anyone) has ever experienced this or knows a fix.

I've never experimented if it happens without Viper enabled but will try that today.

Update: Does not happen without Viper enabled.
I have a Audioquest Dragonfly blue DAC which I can use with Viper4Android without issues.
 
  • Like
Reactions: vibrantliker

tehrzky

Senior Member
Oct 24, 2010
161
22
I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)
after long search how to fix infamous "remount system rw" finally this module fixed the problem. (idk why dev of v4a not fixing this problem on their module, magisk has changed maybe that broke the module).
 
  • Like
Reactions: shadowstep

lindahl85

Senior Member
Feb 9, 2011
1,068
136
Vetlanda
I tried to install Magisk module one oneplus 9 with crdroid, rebooted and started the app. Install it and rebooted. Started the app but it still want to install the driver. Any suggestions?
 

lindahl85

Senior Member
Feb 9, 2011
1,068
136
Vetlanda
I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)
I tried it on my OP9 with Crdroid. Drivers didn´t install from Magisk so it pops up every time I start viper. Install and reboot does not install it.
 

Littlemether

Member
Dec 21, 2021
21
5
OnePlus 7
OnePlus 7 Pro
I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)
Also needs smalipatcher options used
 
  • Like
Reactions: DeMiane

DeMiane

Member
Dec 14, 2019
37
1
I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)
Hello, I tried your mod on OnePlus Nord 2. Hangs when the application starts. Tell me, maybe there are options to revive. SELinus = enforcing
 

zzenyoo

Senior Member
Sep 11, 2014
177
104
46
Chełm
LG V10
Xiaomi Poco X3 NFC
I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)
Uff, it worked on my POCO X3 nfc (arrowos a12) without extra steps (except legacy mode on and off).
 
  • Like
Reactions: shadowstep

DeMiane

Member
Dec 14, 2019
37
1
Quite simple.

  1. Install Viper4Android version 2.7.2.1 module zip
  2. Don't reboot
  3. Open Viper app
  4. Select yes to install the driver now
  5. The phone will reboot
  6. After reboot open Viper and enable Master limiter and, on settings, enable Legacy mode
  7. Close Viper
  8. Install my Fix module zip
  9. Reboot
  10. Wait for about a minute
  11. Reboot again

That should be enough. If it wasn't...reboot again.

Cheers!
OnePlus Nord2 .11 andr. oxygen. During the installation process, zip. Doesn't install the app anymore. fix doesn't help. The previous operations have not been completed.
 

Attachments

  • photo_2022-01-24_17-47-47.jpg
    photo_2022-01-24_17-47-47.jpg
    74.3 KB · Views: 106
Last edited:

Bourjois

Senior Member
Mar 1, 2012
62
23
Hello, I hope this isn't a stupid question.. Is there an updated download link? XDA Labs has shut down so the link on page 1 is dead.
 

SkaboXD

Senior Member
Jan 18, 2017
1,120
436
Ganja
Xiaomi Poco X3 NFC
I experience audio stutter whenever I start to play audio in any application with V4A.

Poco X3 NFC, ArrowOS, Legacy mode (as that's the only thing that it works)

I use @shadowstep version since original Magisk module doesn't install audio driver properly.

JamesDSP doesn't have that issue but it doesn't apply it's processing to alarm, calls & ringtone unlike V4A, so I'm stuck with this.
 
Hi guys,
i have some issues recently getting v4a working on my old legacy devices Samsung Galaxy S3 i9305 and Note II N7100 running a treble-enabled lineage 18.1 build by html6405.
On my S3 i9300 however, it runs a standard 18.1 build by rINanDO and v4a works here flawlessly.
V4a was working on the other devices aswell so i wonder if treble = trouble here.
So basically after flashing the magisk module and opening the app, i followed the prompt to install the driver.
However after a reboot, the app still prompts me to install the driver so it either failed to install or doesn´t load at startup.
Any ideas?
smdk4412 devices are extremely old but they have a very capable headphone DAC after enabling some boeffla-tweaks on the kernel side of things.
Thanks :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I have found solution for my OnePlus 8T OS 12.1
    Finally i can enjoy Viper Sound again! :)

    HERE.
    2
    I tried everything and no luck



    I have oneplus 10 pro android 12.1

    Magisk 24.3

    Anyone can help

    I think i need to get audio_effects.xml to vendor/etc/ but how?!🤔
    Try this modded version from shadowstep https://forum.xda-developers.com/t/...-0-viper4android-fx-2-7.3774651/post-86213263

    It works for me on S20 A12 OneUI 4.1 without any extra magisk modules or hacks.
    1
    I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it. :)

    Thanks for this. It works great on my S20, no additional files or modules required 😀
    Could you update this mod with the newest Viper app (3.0 Alpha 1)? Thanks again.
    1
    not sure how much you want to 'tweak' your bluetooth buds, but if it's just a custom eq setting you could try using the app called wavelet instead. it's made by the viper team, but it's just in the play store for free. it allows you to set a custom eq default for each audio device that connects, including a separate custom eq for the phone's internal loudspeaker.

    obviously it also allows for the default setting for any audio device to be left as system default, so it should do what you want eq wise.

    i couldn't get viper working on my phone, so i'm using wavelet instead and am very happy with it!
    Thanks, mate. I tried the Wavelet. It turns out that it works pretty well. The app has almost all of the settings that I have been looking for.
    1
    I installed v4a via magisk's module
    After opening app
    It asks to install drivers
    But
    After many times
    It install drivers, reboot, again again and again
  • 536
    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
    135
    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
    90
    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