• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

Poipoii

Member
Jul 9, 2017
16
4
Ok so I'm having the same issues a lot of people have mentioned recently (2.7.2.1):
- Only works in Legacy mode
- Shows Abnormal driver status when not using Legacy
- Although processing works in Legacy mode, V4A doesn't seem to care which audio output is being used. Even when BT audio is being processed, V4A sticks to the very barebones Speaker presets.

I've tried installing ACP and AML, in different orders, but I'm doing it kind of randomly because I have no clue what is the correct order, and which options to choose during the ACP installation. I tried doing it the way I believe I got it working with previous versions of V4A but I'm having no success.

I'm going back to 2.7.1.6 for now with a Tasker setup for device-specific preset. Too bad, I was really looking forward for that feature being built-in in the new version.
 

mtkmanjaro

Senior Member
Apr 10, 2017
182
57
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------

[/COLOR]
Can you please provide me/us a link to downgrade to 2.7.1.6?

Like it or not - this update is unusable in my opinion.


I 100% agree with you guys this update is a big load of bugs Another change of format without any purpose in reality, the worst part is that if you update you lose all your profiles and files, when I update viper4 all the files and profiles were deleted without prior notice, you know some files were paid, i understood that the files do not work for the second format change that does nothing but delete your files without even asking if you want to back them up, no to mention how bad the audio processing is in this update, distorted sound echo and static noise
 

Madjax2020

Senior Member
Dec 7, 2019
408
57
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------

[/COLOR]



I 100% agree with you guys this update is a big load of bugs Another change of format without any purpose in reality, the worst part is that if you update you lose all your profiles and files, when I update viper4 all the files and profiles were deleted without prior notice, you know some files were paid, i understood that the files do not work for the second format change that does nothing but delete your files without even asking if you want to back them up, no to mention how bad the audio processing is in this update, distorted sound echo and static noise

Nice way to blast the dev working for free. I get your pissed, angry or whatever then create your own app. Pissing them off won't get them to help, or help faster.

Tried to revert back to 2.7.1.6 .. got the app, but now none of my presets are showing up.
 
Last edited:

Madjax2020

Senior Member
Dec 7, 2019
408
57
Wouldn't let me add it to my last post.
 

Attachments

  • Screenshot_20201103-213841.png
    Screenshot_20201103-213841.png
    135.1 KB · Views: 247

Madjax2020

Senior Member
Dec 7, 2019
408
57
Not sure why I can't add 2 screenshots to a post. When I flash ViPER4Android_FX-v2.7.1.6(2716).zip in ex kernel manager like I've done before it brings me back to ViPER4Android_FX-v2.7.2.1(2721).zip everytime. Now I have no viper to use lol.
 

Attachments

  • Screenshot_20201103-213946.png
    Screenshot_20201103-213946.png
    212 KB · Views: 645
Last edited:

mtkmanjaro

Senior Member
Apr 10, 2017
182
57
Nice way to blast the dev working for free. I get your pissed, angry or whatever then create your own app. Pissing them off won't get them to help, or help faster.

Tried to revert back to 2.7.1.6 .. got the app, but now none of my presets are showing up.

Now it turns out that saying facts is talking badly about the developer, one thing is to have bugs in an application which is very normal and another is to do things without purpose so stufu nibba delete the files of a user without any justification or warning I think it does not fit within the most transparent practices. Not to mention that many people are talking about how bad the update is and it turns out that you just come to tell me what I'm doing wrong.

by the way the files do not work because of the nonsense format change that have been done 2 times, which means that if you downgraded to version 2.7.1.6 you will need the files you used in the first format change.
 

Madjax2020

Senior Member
Dec 7, 2019
408
57
Now it turns out that saying facts is talking badly about the developer, one thing is to have bugs in an application which is very normal and another is to do things without purpose so stufu nibba delete the files of a user without any justification or warning I think it does not fit within the most transparent practices. Not to mention that many people are talking about how bad the update is and it turns out that you just come to tell me what I'm doing wrong.

by the way the files do not work because of the nonsense format change that have been done 2 times, which means that if you downgraded to version 2.7.1.6 you will need the files you used in the first format change.

Stop crying, I have all my original files AND the converted ones. You need a hug.
 

lilbrat

Senior Member
Jun 13, 2011
1,000
374
Amman
OnePlus 8T
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------

[/COLOR]



I 100% agree with you guys this update is a big load of bugs Another change of format without any purpose in reality, the worst part is that if you update you lose all your profiles and files, when I update viper4 all the files and profiles were deleted without prior notice, you know some files were paid, i understood that the files do not work for the second format change that does nothing but delete your files without even asking if you want to back them up, no to mention how bad the audio processing is in this update, distorted sound echo and static noise

No device info, logs, rom/os info ect. And you want to complain.... Go back to one that did work for you,.problem solved ..
 

lilbrat

Senior Member
Jun 13, 2011
1,000
374
Amman
OnePlus 8T
Wish I could figure out how to go back.

See there's the issue.. lack of information leads to lack of help... You want to go back or if you have an issue, folks here will try and help or point you in the right direction, ya you might catch a bit of hell if you didn't search but we can't do anything If the basic information is given.. phone model , rooted , non rooted, stock or custom rom, issue, what steps have you tried... Not [email protected]#$ing at you but it gets old seeing folks complain.. then wonder why devs stop working on projects and or just plain leave..
 

RyuukenZenkou

Senior Member
May 14, 2016
204
21
Santiago
I thought so too, but the problem is there is no AudioFX app anywhere

---------- Post added at 04:24 PM ---------- Previous post was at 04:16 PM ----------



I have found the solution:

open Termux (or any other terminal emulator)
type

su
setenforce 0

that's it.
Yes but that has to be set on every boot.

Sent from my Samsung SM-J400M using XDA Labs

---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
 
Last edited:

mrrocketdog

Senior Member
Oct 27, 2013
4,578
2,023
@Team_DeWitt , hope you dont mind this off-topic/¢.02 worth that i'm throwing in. if so , just have your favorite mod delete.
as i learned some time ago from a guy you may know as "lennon" (alias used to protect the …… , yeah) always make a backup of your system if your going to f*ck with your system. easy breezy. problem solved. free advice done.:good:

edit: forgot almost everyone else was on magisk. [emoji51]
 
Last edited:

popox

Senior Member
Apr 16, 2011
72
7
jakarta
www.instagram.com
v2.7.2.1 works for me in compatibility mode. it automatically convert my profiles during install but sadly messed up all of my profiles. all become unusable. they now produce scretching noises, hurt my ear.
i like v2.7.1.6 better, the interface was nice too easier to navigate.
 

itylermartin

Senior Member
May 4, 2011
57
18
Louisville
It is for me on my Pixel 4 XL and on a Nexus 6P. Latest V4A along side JamesDSP, ACP & AML on Android 11 & 10, respectively.

Just curious. Why do you need james dsp and v4a on the same device? Don't they do essentially the same thing and could possibly interfere with each other?

Also were you able to remove notification ducking with ACP?

I'm on a pixel 4xl with V4A, ACP, and AML on 11. Everything working fine except the notifications, and sometimes v4a randomly stops processing
 

Lughnasadh

Senior Member
Mar 23, 2015
2,049
1,344
Google Nexus 5
Huawei Nexus 6P
Just curious. Why do you need james dsp and v4a on the same device? Don't they do essentially the same thing and could possibly interfere with each other?

Also were you able to remove notification ducking with ACP?

I'm on a pixel 4xl with V4A, ACP, and AML on 11. Everything working fine except the notifications, and sometimes v4a randomly stops processing
I use JamesDSP because I much prefer the bass in it compared to V4A (using JamesDSP v. 2.7, not the latest) and they work fine together (because of AML). There are other options that JamesDSP has that V4A doesn't, and vice versa.

I didn't try to remove notification ducking with ACP b/c I prefer to have the media volume lowered while a notification comes in.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    fwiw, heres the V4A magisk module zips that i use for Android 11. Not my work (except adding a few lines to permissive.sh in the enforcing version ala @DiamondJohn) so credit given where due.

    Pick one to suit your needs


    ViperFX_Android11_Permissive.zip

    Permissive: This is the original one (permissive) - credit to Ichigo Kywrosaki


    ViperFX_Android11_Enforcing.zip

    Enforcing: This is the one that switches back to enforcing after 3 minutes - credit to @DiamondJohn and his permissive.sh script tip which is exactly the same as the Permissive zip, with:

    /systems/scripts/permissive.sh

    from

    Code:
    #!/system/bin/sh
    setenforce 0
    echo 0 > /sys/fs/selinux/enforce

    to:

    Code:
    #!/system/bin/sh
    setenforce 0
    echo 0 > /sys/fs/selinux/enforce
    
    # after 90 seconds, switch to enforcing
    (sleep 90;
    setenforce 1
    echo 1 > /sys/fs/selinux/enforce)&
    2
    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.
    2
    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 :)
    2
    Ran a search in the thread, but was curious if anyone with a (Pixel 5) running the latest Android 12 beta, has had any success in flashing v4a. Thinking specifically of Ichigo Kywrosaki's v2716.
    I've just upgraded and learned that while I can get reliable root through Magisk, v4a closes upon opening. Thanks for any input! :)
    I am assuming you are using the same zip I linked to above.
    Here's my logcat: Pixel 5 V4A 2716 Android 12 Beta 3 Log

    Hopefully it shows what is going on. I'm suspecting the driver isn't properly installing or isn't loading correctly.

    The version I mentioned before I've been using since Android 10. I imagine that Android 12 does things differently.

    I should also mention that I've used both the original Ichigo permissive build, and the enforcing zip that was posted a page or two back. Same issue either way.

    The app will load, stay open for a few seconds then crash before I can mess with settings. This is also on a newly wiped and fresh Android 12 Beta 3 flash. When flashing the OS I disabled verity and verification as per a post for my device, in order to successfully obtain root with Magisk Canary.

    Also within Magisk, V4A is the only module installed, since running this particular zip over two other Android OS versions, I've had no need for AML, ACP, etc, because they weren't necessary to run Viper without issue.
    Your error is:
    Code:
    [07-18 01:01:38.208 27084:27084 E/AndroidRuntime]
    FATAL EXCEPTION: main
    Process: process.ViPER4Android, PID: 27084
    android.app.ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{263590a u0 com.pittvandewitt.viperfx/.service.ViPER4AndroidService}
        at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:1915)
        at android.app.ActivityThread.access$2500(ActivityThread.java:250)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2140)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loopOnce(Looper.java:201)
        at android.os.Looper.loop(Looper.java:288)
        at android.app.ActivityThread.main(ActivityThread.java:7829)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:982)

    To be clear, I am NOT running A12, but A11 on a Pixel 4A, so all the below is a blind stab in the dark.

    Its failing to start the viper service (from above log), before viper opens.

    Try starting the service [com.pittvandewitt.viperfx/.service.ViPER4AndroidService] manually through a shell. Check if that works or gives you any different errors. (not sure if the below will work without modifying the APK manifest)
    see: https://stackoverflow.com/questions/7415997/how-to-start-and-stop-android-service-from-a-adb-shell
    am start-foreground-service com.pittvandewitt.viperfx/.service.ViPER4AndroidService;
    1
    different5r people have had success with different methods, and some (inc me) with a lot less messing about. So I dont think posting it on every page will help everyone.
    you are right. was speakig from emotios...because i had tried everything right from Page 1...almost gave up. lol.
    but you are right.
  • 522
    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