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

Search This thread

DiamondJohn

Recognized Contributor
  • Aug 31, 2013
    5,207
    4,795
    Sydney
    So I tried the Viper4Android 2.7.2.1 magisk module ... and immediately went into bootloop.
    simply removing the magisk module from twrp browser does nothing. What are the files that magisk module changed?? How can I get this back to normal!?
    On android 11 with a s10
    Have y0u checked for scripts in post-fs-data.d and service.d?
     

    gil80

    Senior Member
    Nov 14, 2010
    1,380
    60
    Sydney
    Ok, trying to have another go at this.
    Using latest Magisk. Oneplus one. LinageOS 17.1
    Using Viper4Android magisk module.
    I removed the Audio Modification Library module and made sure all of its files are gone.

    I have the following folders and files in the attached screenshots. Are these correct? Should I have them in the folder they appear?

    I'm really confused. Why is it always an issue installing V4A?
    It worked before well. The latest version is not working. Installing previous versions are no longer working either. WTF?
     

    Attachments

    • Screenshot_20210324-163701_FX.png
      Screenshot_20210324-163701_FX.png
      61.9 KB · Views: 143
    • Screenshot_20210324-163649_FX.png
      Screenshot_20210324-163649_FX.png
      133.4 KB · Views: 143
    • Screenshot_20210324-163714_FX.png
      Screenshot_20210324-163714_FX.png
      49.1 KB · Views: 141
    Last edited:

    sand_man

    Senior Member
    May 9, 2008
    396
    878
    Johannesburg
    Working beautifully on Oneplus 7T Pro, model 1913, Android 11RC, rooted, Magisk Canary, xXx NoLimits rom...

    provided SElinux is set to permissive mode: using Termux rooted>su>setenforce 0 (still green as to what the risks are re permissive mode). Rebooting phone restores to enforced mode.

    Installed via Magisk - V4A v2.7.2.1 + Audio Modification Library v4.0 (not sure if the latter is necessary)
     

    sand_man

    Senior Member
    May 9, 2008
    396
    878
    Johannesburg
    I thought that "abnormal status" on my phone is due to MIUI (just purchased a new phone), but reading previous posts it seems to be a common problem recently. SElinux permissive is working, but I do not like this approach. I fixed it this way (after installing Viper as Magisk module and installing drivers):

    1. Locate and edit file
    Code:
    /data/adb/modules/ViPER4AndroidFX/post-fs-data.sh
    2. Add this text to the end of the file
    Code:
    magiskpolicy --live 'allow audioserver audioserver_tmpfs file { read write execute }'
    magiskpolicy --live 'allow audioserver system_file file { execmod }'
    magiskpolicy --live 'allow mediaserver mediaserver_tmpfs file { read write execute }'
    magiskpolicy --live 'allow mediaserver system_file file { execmod }'
    magiskpolicy --live 'allow audioserver unlabeled file { read write execute open getattr }'
    magiskpolicy --live 'allow hal_audio_default hal_audio_default process { execmem }'
    magiskpolicy --live 'allow hal_audio_default hal_audio_default_tmpfs file { execute }'
    magiskpolicy --live 'allow hal_audio_default audio_data_file dir { search }'
    magiskpolicy --live 'allow app app_data_file file { execute_no_trans }'
    magiskpolicy --live 'allow mtk_hal_audio mtk_hal_audio_tmpfs file { execute }'
    3. save, reboot phone
    4. go to viper4android app and toggle legacy mode off and on, it should work now with legacy mode enabled

    Alternative way is to run commands from step #2 from Tasker on each boot.

    Tested on MIUI 12, Magisk 21.1 and Viper 2.7.2.1
    Actually thanks for this!! This solution negates the SElinx permission work around!! Great work!
     
    Last edited:

    file2mail

    Member
    Dec 20, 2010
    16
    0
    get and review your last_kmsg That is the log to look at for boot issues.
    been sifting through the 2mb log file! ... after hours, i pretty much feel like i dont know what im looking for

    This is the only fatal exception in the log, and not sure how to deal with "com.android.server.voiceinteraction.VoiceInteractionManagerService":
    Code:
    <6>[   17.950594]  [6:  system_server: 5675] [email protected]*** FATAL EXCEPTION IN SYSTEM PROCESS: main
    <6>[   17.950594]  [6:  system_server: 5675] java.lang.RuntimeException: Failed to create service com.android.server.voiceinteraction.VoiceInteractionManagerService: service constructor threw an exception
    <6>[   17.950594]  [6:  system_server: 5675]     at com.android.server.SystemServiceManager.startService(Unknown Source:118)
    <6>[   17.950594]  [6:  system_server: 5675]     at com.android.server.SystemServiceManager.startService(Unknown Source:13)
    <6>[   17.950594]  [6:  system_server: 5675]     at com.android.server.SystemServer.startOtherServices(Unknown Source:4716)
    <6>[   17.950594]  [6:  system_server: 5675]     at com.android.server.SystemServer.run(Unknown Source:424)
    <6>[   17.950594]  [6:  system_server: 5675]     at com.android.server.SystemServer.main(Unknown Source:5)
    <6>[   17.950594]  [6:  system_server: 5675]     at java.lang.reflect.Method.invoke(Native Method)
    <14>[   17.952005]  [4:           init:    1] init: starting service 'resetreason'...
    <3>[   17.953829]  [0:  kworker/u16:2:   71] IOF drv: Can't obtain absolute path:           (null)           (null)
    <14>[   17.954163]  [3:           init:    1] init: Control message: Processed ctl.restart for 'resetreason' from pid: 5675 (system_server)
    <14>[   17.965879]  [5:           init:    1] init: starting service 'bugreportd'...
    <3>[   17.968082]  [0:  kworker/u16:2:   71] IOF drv: Can't obtain absolute path:           (null)           (null)
    <14>[   17.968207]  [0:           init:    1] init: Control message: Processed ctl.start for 'bugreportd' from pid: 5675 (system_server)
    <6>[   18.164121]  [7:  BootAnimation: 5673] [email protected] : Number of frames drawn 161
    <6>[   18.281268]  [7:            iod: 5020] [email protected]   8,0 r 40302 1682232 w 945 31504 d 274 12468 f 224 371 iot 6784 6584 th 102400 0 0 pt 0 inp 0 0 18.270
    <6>[   18.442923]  [7:    kworker/7:4: 5182] samsung-abox 18c50000.abox: abox_disable
    <6>[   18.446552]  [7:    kworker/7:4: 5182] samsung-abox-gic 18cf1000.abox-gic: abox_gic_disable_irq
    <6>[   18.603835]  [6:  kworker/u18:0: 1439] [SSP]: MSG From MCU - Sensor_Algo =>
    <6>[   18.603835]  [6:  kworker/u18:0: 1439] [SSP_MCU] 000000 0001000000 0000000000 0000000000 0000001000 0000000000 0000000000 0000000000
    <6>[   18.603835]  [6:  kworker/u18:0: 1439] [SSP_MCU] LCD On_Off 1, AP_Status 1
    <6>[   18.603835]  [6:  kworker/u18:0: 1439] [SSP_MCU]Sensor_Bypass => ACC:0,-1,20 Gyro:0,-1,20 Mag:0,-1,-1
    <6>[   18.603835]  [6:  kworker/u18:0: 1439]  MagC:0,-1,-1 Baro:0,-1,-1 Prox:0,-1,-1 Light:0,-1,-1 UnGy:0,-1,-1
    <6>[   18.603835]  [6:  kworker/u18:0: 1439]  GRV:0,-1,-1 RV:0,-1,-1 Bulk:1,60 Timer:20 VDIS = 0, VDIS_Bat = 0, Motor = 0
    <6>[   18.604370]  [7:  BootAnimation: 5673] [email protected] : Number of frames drawn 171
    <2>[   18.855055]  [6:SettingsProvide: 5873] watchdog: watchdog1: watchdog did not stop!
    <6>[   18.855067]  [6:SettingsProvide: 5873] softdog: softdog_ping: 100
     

    jjcdennis

    Senior Member
  • Jun 20, 2015
    427
    98
    Toronto
    Just installed latest 2.7 via Magisk Manager V22.0. The app when opened doesn't show the bottom bar - Headphones Speaker, etc. I tired to search this with no success. How do I resolve this?
    I tried to delete the module twice via Magisk Manager, but it doesn't delete it and it still opens up to the main page. How do I delete the module and driver if Magisk delete doesn't work.
     

    Lord Sithek

    Senior Member
    Just installed latest 2.7 via Magisk Manager V22.0. The app when opened doesn't show the bottom bar - Headphones Speaker, etc. I tired to search this with no success. How do I resolve this?
    I tried to delete the module twice via Magisk Manager, but it doesn't delete it and it still opens up to the main page. How do I delete the module and driver if Magisk delete doesn't work.
    this version work differently than previous ones. it shows only current output settings. you'll see another options when you connect to headphone jack or bluetooth

    BTW, if needed, you can delete the module in root directory: /data/adb/modules/ViPER4AndroidFX
     
    • Like
    Reactions: jjcdennis

    jjcdennis

    Senior Member
  • Jun 20, 2015
    427
    98
    Toronto
    this version work differently than previous ones. it shows only current output settings. you'll see another options when you connect to headphone jack or bluetooth

    BTW, if needed, you can delete the module in root directory: /data/adb/modules/ViPER4AndroidFX
    I didn't find it in that location, but did find it at /storage/emulated/0/ViPER4Android. I deleted that folder and the app still opens when I tap the icon.
     
    Last edited:

    _mysiak_

    Senior Member
    Apr 1, 2009
    2,412
    1,391
    Xiaomi Mi 10T Lite
    I didn't find it in that location, but did find it at /storage/emulated/0/ViPER4Android. I deleted that folder and the app still opens when I tap the icon.
    Viper4android is a standalone Android app, Magisk module is needed only for driver. If you want to completely remove Viper, you must uninstall module from Magisk and app from the phone.
     
    • Like
    Reactions: jjcdennis

    Demianis

    Senior Member
    Mar 31, 2012
    117
    16
    I'm curious to know, did you have to install the Audio Modification Library or the Audio Compatibility Patch? Or did you simply install viper and modify the post-fs-data file?
    Sorry haven´t been here a while.
    No , it was working without AML., just activated Legacy Mode. At first it looked like the driver was not enabled, but after second boot it surprisingly worked.
     

    Scientist07

    Member
    Jun 20, 2013
    40
    2
    Viper works well for me using spotify but I want to use ith with other media players. I have youtube vanced installed and also tunein radio. Any idea how to get it to work with these apps?
     

    Scientist07

    Member
    Jun 20, 2013
    40
    2
    I don't use tunein app, but tried it quickly and Viper seems to be working in it with legacy mode enabled. Maybe try to restart tunein completely after enabling Viper legacy mode.
    Did that and no change. Will try reinstalling Viper.

    EDIT: Reinstalled and no change.

    EDIT: Installing audio modification library seems to do the trick.
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 1
      Does anybody here have an instruction manual or something to learn what does every option do in the app? I don't know who designed it but it has some high horse sindrome or something to call the settings things like "Channel displacement" to the good old channel balance....

      I've seen things like the compressor have settings named like "inflection point" which I don't have the most remote idea of what is does.

      I cannot find information on the web on what the options do; all I find here in XDA is how to make the app work on X phone model.

      I need to set it up to be some kind of auto-volume so different youtube videos stay at the same volume and also compress them so quieter parts can be heard and louder parts don't freak me out (mostly voices and loud piano songs in the same videos, voices very quiet and piano very loud).
      Viper came into existance many years ago and it has been abandoned by the original devs. That's why its unofficial right now. @Team_DeWitt put much effort to bring it to the newer Android versions and it's really great. As far as I remember, since 2.7.6.x version it has short descriptions when you long press on a feature name. There is a guide with more information prepared by the original dev team, but it was created long time ago and some features are not present right now or named differently. Im attaching it
      1
      Viper came into existance many years ago and it has been abandoned by the original devs. That's why its unofficial right now. @Team_DeWitt put much effort to bring it to the newer Android versions and it's really great. As far as I remember, since 2.7.6.x version it has short descriptions when you long press on a feature name. There is a guide with more information prepared by the original dev team, but it was created long time ago and some features are not present right now or named differently. Im attaching it

      Thanks Lord Sithek! being honest, the information is not very useful but it is much more that what I could find. I think we should ask @@Team_DeWitt to make some kind of instructions document.
      1
      Does anybody here have an instruction manual or something to learn what does every option do in the app? I don't know who designed it but it has some high horse sindrome or something to call the settings things like "Channel displacement" to the good old channel balance....

      I've seen things like the compressor have settings named like "inflection point" which I don't have the most remote idea of what is does.

      I cannot find information on the web on what the options do; all I find here in XDA is how to make the app work on X phone model.

      I need to set it up to be some kind of auto-volume so different youtube videos stay at the same volume and also compress them so quieter parts can be heard and louder parts don't freak me out (mostly voices and loud piano songs in the same videos, voices very quiet and piano very loud).
      Terms like "inflection point" are actually used in digital music production. Viper is an advanced application and as such requries advanced understanding. Sure, some terms are not common to you or me, but its a biug world out there, and sometiomes to use something, the onus is on us to do the personal research.
      1
      Posting this here in case someone needs it. I was able to make Viper4Android v2.7.2.1 work on my OnePlus 7 Pro running on OxygenOS (OOS) 10.3.8 (Android 10), with Magisk 23.
      I followed the steps given in this thread on Reddit, which I am reiterating and rewording below (credits to @CR7Raees):
      1. Install Magisk module 'Ainur Narsil' and then reboot.
      2. Install Viper4Android module from Magisk. Open it, install the drivers and reboot from within V4A.
      3. Open Magisk and uninstall Ainur Narsil module. Again reboot.
      4. Open V4A and turn on Legacy Mode from the settings.
      Currently, I've just tried it out on my phone's speakers, but I am pretty sure it would also work with my headphones. Will report back and edit below.
      Screenshot_20210525-111502.jpg


      Edit: Yup. Working gorgeously with my XM3.
      1
      That is the problem right there: how do we know what the options do if we are not sound ingineers and there is no information available on what the options do?

      Everybody here in XDA talks about "beginners" and "experts" but no experts seem to be coming to this places since nobody knows what those "advanced" options do. :unsure:
      This is not the place to cover the basics of sound engineering. There are thousands of articles on the web already that cover that. This thread would be bloated beyond belief if it contained all that info. XDA is a developer forum not a beginners support site; especially for a free app. A simple web search and read would give you the info on using apps such as Viper. If ypou drive a car, you should learn how to drive first, not expect the sale people to teach you.
    • 521
      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
      131
      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
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone