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

Search This thread

Wishmasterflo

Senior Member
Nov 21, 2018
930
413
Stockholm
Hi all

I need some help with Viper4Android. I installed it a few days ago on my Oneplus 6 via Magisk Module.
Driver is installed and V4A is working via the internal speaker and when connecting a Headset via cable but for Bluetooth I dont get it to work.
There is just says Processing: NO

Device: Oneplus 6
Rooted using Magisk 19.3
Custom ROM: latest Syberia OS ROM
Viper4Android FX: v 2.7.1.0 (installed as Magisk Module)

Any idea why it is not working via Bluetooth?
When bluetooth is connected it just ignores all the Viper4Android settings means the same as if I would turn off Viper4Android.

When I install AML (Audio Modification Library) module in Magisk then Bluetooth is not working at all.
 

darkhunger95

Member
Jul 15, 2018
15
2
I've installed viper on Lenovo k5 note. (rooted). but it is not processing the audio.I've also installed aml, audio compatibility patch. Pls help
 

Attachments

  • Screenshot_2019-06-11-10-15-59-967.jpg
    Screenshot_2019-06-11-10-15-59-967.jpg
    98.4 KB · Views: 721

LeifAlbor

Senior Member
Feb 24, 2011
72
31
Launceston
Not sure what your "AutoStarter" app does, but if you already run a script to kill the audio server, would the following work by adding to the end of the first script, thus removing the need for "AutoStarter"
Code:
am start -n com.pittvandewitt.viperfx/com.pittvandewitt.viperfx.StartActivity;

Hmmm on my device the only activity V4A seems to have (at least as far I can see) is com.pittvandewitt.viperfx.MainActivity ... Was StartActivity taken out of the new version? I hope not, because it's a pain in the ass having to reload the app GUI each time...
 

Ceejay343

Senior Member
Jun 9, 2016
161
51
Working like a charm on an Umidigi Z1 pro, too bad the old Viper-DDC list is gone. Sound was great with that for my Denon and Sennheiser headphones. I got to fiddling though and have everything to my satisfaction now, great work @Team_DeWitt!!!
 

johnlgalt

Senior Member
Nov 16, 2009
1,394
412
50
Atlanta
androidforums.com
Do you have the 2.7.0.0 APK? I can't seem to find it anywhere and I've run into the same problem (Pixel 2, on Q Beta).

Sure, here you have

Thanks for hte link :)

Thanks! After a couple of reboots and toggling Audio Modification Library I've got it to work for around 10min on boot which is good enough for now (going to chalk up it failing afterwards as a Q beta issue).

Nefi, is this still an issue on Q Beta 4 build .019?
 

refi64

Senior Member
Nov 25, 2013
82
119
refi64.com
Thanks for hte link :)



Nefi, is this still an issue on Q Beta 4 build .019?

Thus far on beta 4 it's actually been pretty great, two catches:

- Occasionally it crashes on reboot, and you have to reboot *again*. This is pretty rare, and it'll say the driver is in an unsupported state.
- USB doesn't work, though BT and speakers do. Not sure about jack because I don't have one.
 
  • Like
Reactions: johnlgalt

XmechaniX

Senior Member
May 24, 2012
444
133
Module doesn't seem to work. Had 2.5.0.5 installed before. After installing the module there is no prompt to install the driver. Status stays abnormal. Any suggestions? Thanks

P.S. Oneplus3T here
 

nicknacknuke

Senior Member
Jan 14, 2011
105
18
Same here.. keep asking driver to be installed ( creating magisk module ) over and over..
tried to kill audioserver in terminal, only to see that the process is respawning again with another 2 PID.

Mind refreshing me on how to install 2.5.0.5 ?
I've been too long not keeping up here, and just updated to 9.0.3 OP3T...
 
  • Like
Reactions: Plovel

Plovel

Senior Member
Apr 16, 2019
51
9
Same here.. keep asking driver to be installed ( creating magisk module ) over and over..

tried to kill audioserver in terminal, only to see that the process is respawning again with another 2 PID.



Mind refreshing me on how to install 2.5.0.5 ?

I've been too long not keeping up here, and just updated to 9.0.3 OP3T...
Ok, I had the same problem on some my devices, try this:
1)Install lagacy Viper like a magisk module (use lib workaround)
2)Delete module's apk of Viper and install 2.7.0.0

Отправлено с моего Pixel через Tapatalk
 

thomas140

Senior Member
Jul 3, 2018
641
139
Johor
There's no problems with 2.7.0.0,check it

Отправлено с моего Pixel через Tapatalk

Any idea on why this happens? since there is a problem, why don't the dev temporary remove the 2.7.1.0 and use 2.7.0.0? Just wonder why.:confused:

---------- Post added at 09:24 AM ---------- Previous post was at 09:22 AM ----------

Same here.. keep asking driver to be installed ( creating magisk module ) over and over..
tried to kill audioserver in terminal, only to see that the process is respawning again with another 2 PID.

Mind refreshing me on how to install 2.5.0.5 ?
I've been too long not keeping up here, and just updated to 9.0.3 OP3T...

You can find it in magisk module, find Viper4android, there is one with legacy and another one with xhifi. Go for the legacy, 2.5.0.5 is there.
 

Plovel

Senior Member
Apr 16, 2019
51
9
Any idea on why this happens? since there is a problem, why don't the dev temporary remove the 2.7.1.0 and use 2.7.0.0? Just wonder why.:confused:

---------- Post added at 09:24 AM ---------- Previous post was at 09:22 AM ----------





You can find it in magisk module, find Viper4android, there is one with legacy and another one with xhifi. Go for the legacy, 2.5.0.5 is there.
1)About "There's no problem for 2.7.1.0"
I meant other problem, you have problem with installing the driver
2)Install legacy edition (ViPER4Android FX Legacy)

Отправлено с моего Pixel через Tapatalk
 

PoochyX

Senior Member
Oct 23, 2016
2,171
420
Guys can you tell me which is the best way to get the dark theme to activate on my device I don't want to use the white one [emoji24][emoji24][emoji24][emoji24]

Sent from my SM-J327P using Tapatalk
 
  • Like
Reactions: Plovel

Plovel

Senior Member
Apr 16, 2019
51
9
Guys can you tell me which is the best way to get the dark theme to activate on my device I don't want to use the white one [emoji24][emoji24][emoji24][emoji24]

Sent from my SM-J327P using Tapatalk
My dark theme was activated when I've activated dark theme in my settings (mi 8, xiaomi.eu 9.6.13)

Отправлено с моего Pixel через Tapatalk
 

Top Liked Posts

  • 1
    Ah, OK, thank you! :)
    Will try it next.
    Edit: It's working with headphones (only in legacy mode, and stil got to test Bluetooth later.)
    So most effects don't work with the internal speaker, OK.
  • 2
    Mod Edit: Quote removed since post deleted

    App is not broken, it's how Android 10/11 handles audio sessions and equalizer apps. Just because you don't understand it doesn't mean it's "defect".

    "Hack" is only fix for recent Magisk versions and "fallback" legacy mode works perfectly fine system wide even in Android 10/11.
    2
    After a couple of days, it just stops working and then I have to go to settings and disable and enable legacy mode and it starts working again until the next time.
    Same for me, each time the processing status is no and I have to toggle off and on the legacy mode to have it processing again.
    1
    What are the mods here doing???

    Delete this 2.7.2.* update please! Its the source of all problems here....why do the mods watch this since months and doing nothing?

    Unbelieveable in my opinion whats going on here....more than 20 pages just because noone is willing to remove a defect update...
    Well buddy, not everybody would agree with your opinion.
    1
    Is there just 1 person, where the latest update work as it should? And no, legacy mode is not - as written by others in earlier postings - "working", its just a fallback for problems.
    Yep, me (and many others who used the magiskpolicy fix). Viper works with or without legacy mode, but I don't hear the difference between standard and legacy mode anyway (tried on a couple of headphones, both modes sounds the same). I assume that the difference is in how the equalizer connects to the audio session, the audio processing itself is still the same.
    1
    Ah, OK, thank you! :)
    Will try it next.
    Edit: It's working with headphones (only in legacy mode, and stil got to test Bluetooth later.)
    So most effects don't work with the internal speaker, OK.
  • 519
    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