Database Users

[GUIDE]How to get Viper4Android to work on 6.0 Beta.

I'm a HUGE fan of V4A, so I finally got it to work, and today I'll share with You how to get to work.
Make sure that You have root and TWRP or Phillz installed
Download V4A from PlayStore
Download BusyBox(Stericson) and install it to System/xbin(Su/bin directory probably would work too)
Install V4A drivers.
Rename SoundAlive_31_M folder in System/Priv-App to something else or cut and paste it somewhere else.
Flash this file Click here!
In V4A change mode to compatibility.
Done!
Thanks to MaximumEntropy for his file.
Additional info:
6.0 beta
SuperSu 2.66 beta
V4A 2.3.4.0

i have given this a go as per your guide but is still not working on 6.0.1?
It's just acting like it did before v4a installed audio effects don't make a difference any help anyone?
thanks
iNeoTom

Likewise here, in driver status it says it is supported and that neon is enabled but it is not processing or enabled overall. I've tried changing to compatibility mode and normal mode without any change.

Thanks a lot, works flawlessly on 6.0.1!

To get it working I had to replace the audio_effects.conf in system/etc with the one arter97 posted here http://www.arter97.com/browse/S6/M/ViPER/ set the right permissions and reboot. Got a system FC at first but then seems to work flawlessly. Good luck! :good:

This worked! S6 noble ROM 6.0 Thanks!!

delete

[V4A] Viper4Android I/O Error (Driver Installation Failure) [FIX]

Hey everyone! I seem to have found put together 3 methods of installing/bypassing the V4A App on android. These methods include:
Regular Installation, and 2 Error bypasses/fixes.
If you get the error "superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!", then you've come to the right place.
Requirements: ROOT, (maybe) TWRP (or anything you can flash the zip onto your phone with. With this tutorial I'll be using TWRP.)
If you don't have TWRP, here's the link to that \\ https://twrp.me/Devices/
Type in/select your device, click download, and flash it to your phone.
====================================================================================
Regular installation:
1.) Download V4A from Google Play Store \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) Open, and grant root permission.
3.) Install drivers, and reboot phone. DONE!
==================================================================================================
V4A SuperSU Manager Error:
1.) Download V4A from Google Play Store (the newest one) \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
Open it, grant permissions, click "install drivers" <- just get through the driver menu. This is a troubleshoot test. If it fails, keep going on with the tutorial. If not, You're A-Okay.
2.) Download V4A Flashable ZIP from here \\ https://drive.google.com/file/d/0By-5wpCgi7OHMjFZRU1PYXljbDQ/view
Drag and drop from your computer onto your phone in your "Downloads" folder.
3.) Open TWRP and click "Install" and navigate to your "Downloads" folder where you Installed the V4A Flashable ZIP (Viper4AndroidMM_v2.4.0.1.zip)
Install the ZIP in TWRP, and reboot.
4.) Open your apps/app menu, navigate to the new (it's an older version, but it's newly installed) V4A. It should be a purple logo instead of a blue logo. At this point in the tutorial, you should have both the Google Play Store APK, and the TWRP Flashed APK. Open the PURPLE V4A, and Install drivers now.
5.) Reboot phone, go to the NEW (blue logo) V4A, and install drivers on that one too.
The rest is clean-up. You may now delete the older version of V4A (purple logo).
========================================================
Bypass/fix #2, The SELinuxModeChanger issue:
1.) Download V4A (newest version) from \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) (Grant root access) Attempt to install drivers. If this succeeds, then Idk why you're still here.
3.) Download SELinuxModeChanger APK from \\ http://forum.xda-developers.com/devdb/project/dl/?id=12506
4.) Open it, grant root access, and click "Permissive".
5.) Re-boot phone, and open V4A when done.
6.) Install drivers!
Sources/credit go to:
https://forum.xda-developers.com/showthread.php?t=2524485
^ SELinuxModeChanger
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
^ Driver install failure/ Disc I/O error/"superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!" error
https://twrp.me/about/
^ Team Win
https://forum.xda-developers.com/member.php?u=7249915
^ Me, I contributed very small amounts, that's why I'm last (I guess I contributed some common sense .. ?)

what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.

masri1987 said:
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
Click to expand...
Click to collapse
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8

zahidm said:
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
Click to expand...
Click to collapse
my head unit doesn't have vendor/etc or the audio effects configuration file....

Thanks
I had the Viper.apk from their website and the Google play version loaded also and I was getting the I/O error when trying to load the driver and the Google Play version didn't work at all. I did try to load SuperSU and busybox before attempting to load the driver again and it still didn't work. I don't know about permissive kernel, I'm running Resurrection ROM on a Rooted Note 3. The way I got this to work was to uninstalled the V4A Viper APK version that I had retrieved and loaded from their website. Next I booted into TWRP recovery and installed the V4A Flashable ZIP from the link that I found here. Next I ran the flashed version and granted SU permissions when asked during the install driver process. The driver finally loaded and bingo it works now.

Viper4android
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance

Banty448 said:
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Click to expand...
Click to collapse
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot

zahidm said:
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
Click to expand...
Click to collapse
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx

Banty448 said:
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Click to expand...
Click to collapse
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk

0
zahidm said:
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I already told u that I did it before opening the v4a

Banty448 said:
0
I already told u that I did it before opening the v4a
Click to expand...
Click to collapse
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk

zahidm said:
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies?

Banty448 said:
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies[emoji106]
Click to expand...
Click to collapse
You didn't followed this guide?
https://forum.xda-developers.com/mo...od-viper-4-android-oreo-tested-t3700287/page2
Sent from my Nokia 5.1 Plus using Tapatalk

When I install drivers for ViPER4Android FX I get "Driver installed, please reboot your device." and when I reboot, I'm asked to install drivers again. Did anyone figure out how to successfully install these drivers? I saw fixed around the forum, but they don't seem to work for me.
My phone huawei p10 lite rom Resurrection Remix OS Beta 3!

Audio Mod for Stock Nougat

I wanted to install Viper4android on stock 7.0 march but was unable to do so after following 2-3 different methods. Is there anyone successfully using viper4android on stock? And if not successful them suggest any other sound mod fully working and compatible with stock 7.0 march. I am rooted, elementalX 1.04 + busybox also installed :silly:

You intent with Viper4Aprise?

most of these require permissive selinux and i dont want to do that.

Why? I dont know for what flash permissive, what Is this?

JassyelZ said:
Why? I dont know for what flash permissive, what Is this?
Click to expand...
Click to collapse
selinux can be "enforcing" which is more secure or "permissive" which is less secure. V4A does require permissive kernel generally.

so anyone found a working sound mod for stock rom with selinux enforcing?

nitish_namdev said:
so anyone found a working sound mod for stock rom with selinux enforcing?
Click to expand...
Click to collapse
I've got ARISE running on my device (NPJS25.93-14.4, ElementalX, magisk v13). Note, I'm just running the core modules, any other addons I do not know if you need to tweak further. I have not changed ElementalX's SE Linux permissions, and running 'su getenforce' in a terminal returns as 'enforcing'.
My setup: XT1642, updated to NPJS25.93-14.4, ElementalX, magisk v12/v13 (think if you have SuperSU, should be okay too).
1) Downloaded ARISE Magnum Opus from here: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 (I currently have the 05/06 build). The download link is the Magnum Opus TM. Also, as I'm using magisk, I downloaded the magisk compatibility module. https://forum.xda-developers.com/an...y-research-t3379709/post71569390#post71569390
2) To configure ARISE before flashing, I extracted arise_customize.prop to /sdcard, and configured install.core to = true, install.v4a_2.5.0.5= to be true (and later found out I needed delete.deep_buffer to = true). Saved the ARISE customise file (I've uploaded my prop file if you want to see my modifications. If you wish to use this file, delete the .txt in the file name so the extension is .prop).
3)Rebooted to TWRP. Backed up. Flashed ARISE Magnum Opus - as configured, it should flash the 2.5.0.5 core module and delete the deep buffer (without deleting deep buffer, I found that ARISE did not process output).
3a)After ARISE, flashed the magisk compatibility module (if you're on SuperSU, you may not have to flash this). With magisk v13, this does not trigger Safety Net.
4)Wipe cache/Dalvik and reboot.
5)As I'm using Poweramp, I had to go to Poweramp Settings > Audio > Advanced Tweaks and disable Direct Volume Control. Also, I disabled the main Equalizer.
Now, ARISE processes headphone output as per the ARISE settings.

Viper4Arise on Android Oreo 8.1

For anyone who's interested, here's what I did. based on the directions given by quinny899 in the thread here: https://forum.xda-developers.com/pixel-2-xl/help/viper4android-8-1-0-t3711474
I used the contents of the ZIP posted by quinny899 (for step 9, below) in post #8 on that thread: https://forum.xda-developers.com/showpost.php?p=74681544&postcount=8
The steps I took were:
1. Clean install of the Android 8.1 full factory images (with the -w option removed from the flash-all.bat file)
2. Completed the initial set up, then got rid of the lockscreen PIN (so that I wouldn't have decryption issues with TWRP in the next steps)
3. Put phone into fastboot, then booted into the TWRP 3.2 image
4. Installed Magisk (version 14.1456 beta)
5. Rebooted
6. Installed Buysbox for Magisk, and downloaded (did not install) the Vipe4Android Magisk module by ShadySquirrel
7. Extracted the Viper4Android.apk from the Magisk module that I downloaded
8. Rebooted
9. Copied the contents of quinny89's zip file into root/Magisk (using SolidExplorer, after granting it root privileges)
10. Rebooted. Now, Magisk thinks it has Viper installed (but it doesn't, yet!)
11. Install the Viper4Android.apk that I extracted in Step 7, as a normal user app
12. Reboot
13. In Viper4Android, put it in Compatibility mode, enable Developer mode, and disable seLinux (or use some other method to set seLinux to permissive, I suppose)
14. Reboot, and Viper is working for phone speakers, and Bluetooth, tested with Spotify and Poweramp. Convolvers, and all
All credit to quinny899 for figuring this out for the PixelXL.

anyone have a link to this busybox? man I search and get all kinds of junk but not the one I need. thanks

quinejh said:
anyone have a link to this busybox? man I search and get all kinds of junk but not the one I need. thanks
Click to expand...
Click to collapse
Can't you download and install it directly from MagiskManager?

pavanmaverick said:
Can't you download and install it directly from MagiskManager?
Click to expand...
Click to collapse
Strangest thing. The one that the manager downloads doesn't work. But I found another link in I believe it was the xl thread and after flashing it when I start playing music I get a viper has stopped error but u can hear it processing

quinejh said:
Strangest thing. The one that the manager downloads doesn't work. But I found another link in I believe it was the xl thread and after flashing it when I start playing music I get a viper has stopped error but u can hear it processing
Click to expand...
Click to collapse
Weird, indeed! Glad you got it working though!

I couldn't get it working using the apk from the magisk viper 14+, but using the apk from v4afx_v2.2.zip worked perfect.
---------- Post added at 04:02 AM ---------- Previous post was at 03:44 AM ----------
I notice with this method for viper it takes a sec to kick in when I change songs, which makes a little shift at the beginning. Anyone know how to get rid of that?

This works.
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/page126

Did any of you have to use a Magisk SELinux Permissive Script to get Viper to work?
If i disable the script in Magisk, Viper doesnt, work but if the script is enabled, it works.
IF you guys aren't using a script how did you get viper to work?
Im using the following Magisk Modules
Audio Modification Library v2.5 by ahrion, zackptg5
Busybox for Android NDK v1.27.2 by osm0sis
Magisk SElinux Permissive Script v1.1 by jman420
ViPER4Android FX v2.5 (2.3.4.0) by ahrion, zackptg5

I'm using the permissive script. Permissive is required for viper.

Viper4android driver status abnormal.

Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...

wakram001 said:
Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
Click to expand...
Click to collapse
Use the guide as in that post (the same can be also found in the XDA V4A general thread):
zgfg said:
There is actually an easier way to fix Viper4Android, follow the original post where the fix was described:
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android 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...
forum.xda-developers.com
In other words, replace (use TWRP or root explorer like MiXplorer)
/data/adb/modules/ViPER4AndroidFX/post-fs-data.sh
with the attached file (download and unzip) and reboot
Still make sure that Legacy mode in V4A Settings is enabled
AML module makes no harm but it's not needed (unless you install additional audio modules like mi9tpbitrate320.zip)
---
In case of installing V4A from scratch:
- install ViPER4Android_FX-v2.7.2.1.zip from Repo (through Magisk) and reboot
- open Viper4Android app and let it install the driver, it will reboot
- replace post-fs-data.sh as above and reboot once again
- open Viper4Android app and enable Legacy mode in its Setrings
- also, don't forget to enable Master limiter for e.g. speaker or headphones
Check the driver status, it must show Status Normal (and Processing Yes when playing nusic)
---
I have Xiaomi.eu A11 beta and I regularly update every week when they release (by dirty flashing their new MIUI zip release, wiping Dalwik and Cache and by flashing the new boot img patched by Magisk)
Up to the two weeks ago I had to re-do the relatively complicated procedure for V4A as was described in this thread upon every Xiaomi.eu update
Since two weeks ago when I replaced the post-fs-data.sh as described above, I just dirty flash Xiaomi.eu, apply root/Magisk, and my V4A continues to work as my all other installed Magisk modules (and root apps), with no needs to fix the V4A driver anymore
PS: This 'new' method with the modified post-fs-data.sh is specifically useful for Magisk Canary 22006 since Magisk 22006 has a known bug with processing the sepolicy.rule files (also in /data/adb/modules/ViPER4AndroidFX), and hence the 'old' method from this thread does not work with Magisk 22006 - but the 'new' method does work (I currently use that Magisk 22006)
Click to expand...
Click to collapse

Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.

wakram001 said:
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
Click to expand...
Click to collapse
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)

Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
zgfg said:
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Click to expand...
Click to collapse
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.

wakram001 said:
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Click to expand...
Click to collapse
Zip attachement was there, you have to go to that post and scroll down through the whole post, it was the last attachement (scrollshot below, click to open and scroll down, it's very long)
Do not read just my post there but study the whole thread and you will see that bobod made it working without Legacy mode on Mi 9T (Pro or not Pro). Google for the general V4A thread on XDA and you will see that most of users/phones can only work with Legacy mode. If you don't like, don't use V4A. Btw, what's wrong with, besides that is called 'legacy'

Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...

wakram001 said:
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
Click to expand...
Click to collapse
Go back to my first answer in this thread (post #2), answer to your original question about V4A.
Click on to the cited post there, to JUMP INTO
When you jumped to that other thread and the post there, scroll down till the end of the long post where ATTACHMENTS begin
CONTINUE SCROLLING through all atrachements, skip three screenshots and CLICK on the ZIP (last attachement) to start downloading
Really so hard?