thank you so much!
this fixed my problem with v4a not working properly
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
- Thread starter Team_DeWitt
- Start date
this fixed my problem with v4a not working properly
Dear,
The new version 2.7.1 look not be recognized on Xiaomi mipad 4 plus - latest Havoc rom - rooted device, please help me, I also install "Audio Modification Library" from Magisk Manager, Viper is not recognized as Magisk Module, does not load the driver and nothing happen, thank much for help !!!
Kenny
The new version 2.7.1 look not be recognized on Xiaomi mipad 4 plus - latest Havoc rom - rooted device, please help me, I also install "Audio Modification Library" from Magisk Manager, Viper is not recognized as Magisk Module, does not load the driver and nothing happen, thank much for help !!!
Kenny
There's a lot of trouble with v4a on Havoc. Nothing new. Change rom.
Running Android n7.1 rooted using magisk with elemental x kernel on nexus 6.
It installs and works fine using Google play music. But it is not processing audio played via YouTube. What could be the fix?
Can anyone assist?
Thanks
It installs and works fine using Google play music. But it is not processing audio played via YouTube. What could be the fix?
Can anyone assist?
Thanks
Try install acp from magisk repo
Or try switch compatibility mode in settings./ Attach audio effect
Last edited:
It always says: Downloading latest apk... Download failed!
Why is that?
I'm on a Xperia XZ2 running Magisk 18.1
Do I need v19?
Why is that?
I'm on a Xperia XZ2 running Magisk 18.1
Do I need v19?
No depends upon your music your ears your buds etc etc .
One profile does not fit all.
One profile does not fit all.
I mean the module does that when being installed via Magisk. Is there a way to fix that?
If you use v4a 2.7.1 from here? There's no installer for magisk. It's within the app itself. The installer. Just install as normal apk, open, let driver install, reboot, profit.
Otherwise. Use Zack's new likewise 2.7.1 from magisk repo.
And. Yes support for magisk prior to 19 has stopped. Says so in release notes. 19.2 latest stable.
Last edited:
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).
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).
Can you guys fix the download for the module?
https://zackptg5.com/testbuilds/v4afx.apk
This link inside the install script can be accessed inside chrome and the file is downloaded without any problem.
Inside magisk manager the module can't be flashed because of the said link.
Can you guys use github for example? Most likely it's due to a timeout on fetching the said apk
https://zackptg5.com/testbuilds/v4afx.apk
This link inside the install script can be accessed inside chrome and the file is downloaded without any problem.
Inside magisk manager the module can't be flashed because of the said link.
Can you guys use github for example? Most likely it's due to a timeout on fetching the said apk
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
Simple - some postings before I linked the older v2.7.1.6 - uninstall your latest Viper-version, install the older 2.7.1.6. Works as it should without any big problems.
After this avoid an update. xxxxxx
Mod Edit: Disrespect2
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.2Mod 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.1
Thank you, and sorry for bothering you with a question that would have been answered if I had simply skimmed through the last ~5 pages of this thread. Everything I tested so far works well.1 -
519ViPER4Android FX
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-27131Currently 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]115Changelog
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
1012.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: Link89Answers 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
New posts
-
G991U and G991U1 Firmware Links and Flashing Discussion Here- Latest: iBowToAndroid
-
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