Has anyone got Viper working? In the normal mode, audio sounds terrible and stuttery. IN compatibility mode, it doesn't do a thing. I'm on RR-P.
With the magisk module, it works, but all audio besides music/YouTube sounds like how you're describing it. I'm on the Pixel Experience Plus Unofficial 8/23 ROM btw. I haven't gotten my system audio sound right no matter how I installed it either. Every time I want to do a video chat with my gf or something, I have to quickly remove Viper and reboot so she doesn't sound like a robot.
Is it still not working properly? Im wondering if shold I install it
Wysłane z mojego Mi 9T Pro przy użyciu Tapatalka
In the Evolution Rom thread i found a magisk module that solve the problem, it works with Evolution but idk with other roms.
https://forum.xda-developers.com/attachment.php?attachmentid=4838655&d=1570553745
Ekil said:
In the Evolution Rom thread i found a magisk module that solve the problem, it works with Evolution but idk with other roms.
https://forum.xda-developers.com/attachment.php?attachmentid=4838655&d=1570553745
Click to expand...
Click to collapse
How to use it.
Step by step guide plz.
There is already another thread here with working instructions for V4A:
https://forum.xda-developers.com/k20-pro/themes/guide-viperfx-miui-11-android-10-t3994621
Note: Use up to Magisk stable 20400 or Magisk Canary 20401 (driver cannot be properly installed with Magisk Canary 20404 or 20405)
What works for me on every ROM is the following:
Notes:
If you have any audio modification module installed (Dolby, V4A, AML, ACP etc.), uninstall them all first.
In my experience, the Audio Modification Library module does not work anymore to get Viper to work.
--Download the module "Audio Compatibility Patch" in Magisk.
During the installation, you need to press a total seven times (six times without volume test key (1st prompt)) the volume buttons (a way of answering questions by yes or no).
This is the sequence is use.
1. (volume test) - or + (as it doesn't matter which key you use)
2. -
3. -
4. -
5. -
6. -
7. -
That's it, reboot your phone.
--After reboot, install Viper4Android. It's going to ask for root, install the driver, and reboot.
After reboot, V4A should work perfectly fine.
infoflo said:
What works for me on every ROM is the following:
Notes:
If you have any audio modification module installed (Dolby, V4A, AML, ACP etc.), uninstall them all first.
In my experience, the Audio Modification Library module does not work anymore to get Viper to work.
--Download the module "Audio Compatibility Patch" in Magisk.
During the installation, you need to press a total seven times (six times without volume test key (1st prompt)) the volume buttons (a way of answering questions by yes or no).
This is the sequence is use.
1. (volume test) - or + (as it doesn't matter which key you use)
2. -
3. -
4. -
5. -
6. +
7. -
That's it, reboot your phone.
--After reboot, install Viper4Android. It's going to ask for root, install the driver, and reboot.
After reboot, V4A should work perfectly fine.
Click to expand...
Click to collapse
Thanks, the only solution on the internet that actually worked for me!
My ROM is LineageOS 17.1 on raphael.
Related
Hi everyone, I was wondering if there is a composite install guide for Oneplus 3T devices for all ROM's for Viper4Arise. I really love that Mod. I am currently on RR 5.3.8 and I find that the installation via Magisk is very buggy and leads to FC almost all apps and the phone freezes after a few minutes of installation. I had no such issues installing Viper4Android though. I am a noob so find the current install method on the thread very complicated. Is there a zip file which makes it easier regardless of ROM or if there is anything specific to RR roms which can be used?
Don't know of any such guide, but it's a good idea to have one (although the request for a guide "for all ROMs" may be a tall order).
I was reading through the following sounds mods thread yesterday, and it was confusing as heck, and seems like some folks have varying results: https://forum.xda-developers.com/oneplus-3t/help/best-sound-mods-t3555160
I can't speak to RR, but what I can say, is that I easily installed ARISE on stock rooted ROM (rooted with SuperSU) with one of the AROMA versions; and ARISE works flawlessly. Did not need SELinux permissive or Busybox. I also skipped all of the options in the AROMA installer, since honestly, I don't know what most of them are, and they aren't critical for the "core" ARISE experience.
Happy to report that I was able to fix this. What I did was a little bit of sacrifice but I think I care about sound quality on my phone more than anything else. What I did was replace magisksu with supersu. While the convenience of magisk would be missed, I am happy that now I have arise numbers Module with dolby atmos installed. :good:
cluttered_butter said:
Happy to report that I was able to fix this. What I did was a little bit of sacrifice but I think I care about sound quality on my phone more than anything else. What I did was replace magisksu with supersu. While the convenience of magisk would be missed, I am happy that now I have arise numbers Module with dolby atmos installed. :good:
Click to expand...
Click to collapse
Did you just flash supersu over magisk or was the installation more involved? I was thinking of testing this but wasn't sure if it would work. My plan currently is:
1) Remove all magisk modules
2) Flash SuperSU from Recovery and reboot
3) Reapply magisk modules (V4A Included)
4) Reboot
Was this essentially all you did on your end?
I have tried what you are about to embark on since if I had it my way, I would stick to magisk. Here's what I did, I rooted my phone with SuperSU after uninstalling magisk completely (remove all modules and uninstall using the magisk uninstall zip), I downloaded the magisk manager and tried to rely on the supersu for root access. Magisk did say the phone was rooted after seeking rights from supersu, but eventually just hung the system. Post which it was kind of futile coz it just won't work. If you flash the magisk zip you will cause bigger issues since supersu and magisk would conflict for libraries and that's not good either.
Feel free to try it anyway and see if you get somewhere. Take a backup of course:fingers-crossed:
For me arise works flawless on rr with magisk. And i didnt need any magisk module or extra zip. Only flashed simple modular installer.
cluttered_butter said:
If you flash the magisk zip you will cause bigger issues since supersu and magisk would conflict for libraries and that's not good either.
Click to expand...
Click to collapse
I just wanted to chime in and say that this information isn't correct. Magisk has been designed to work with SuperSU (systemless) as well as MagiskSU.
Instructions
nadejo said:
For me arise works flawless on rr with magisk. And i didnt need any magisk module or extra zip. Only flashed simple modular installer.
Click to expand...
Click to collapse
Can you share the link for installer or instructions for the specific arise installation you did? It'll help me try the same.
Didgeridoohan said:
I just wanted to chime in and say that this information isn't correct. Magisk has been designed to work with SuperSU (systemless) as well as MagiskSU.
Click to expand...
Click to collapse
Was just sharing my experience. Didn't mean to say that my information was correct.
cluttered_butter said:
Can you share the link for installer or instructions for the specific arise installation you did? It'll help me try the same.
Click to expand...
Click to collapse
1.First put this (my custom prop with dolby atmos and viper arise you can further customize it if you want)
https://drive.google.com/open?id=0B5cs9MEMO2MrNGo3eGJJVFdxemc
On sd card (dont rename it and dont put it in any folder) it must be at same place where all your folders are. Like downloads... Pictures...
2.Then go to rr settings and switch to selinux permissive
3.Now flash this file in twrp https://www.androidfilehost.com/?fid=529152257862724645
And reboot.
Have fun
Will give it a shot tonight! Thank you so much!
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Worked like a charm ??thanks so much. Don't know what I was doing wrong all this time
trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me
trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me know
cluttered_butter said:
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me know
Click to expand...
Click to collapse
For my IRS profile I'm using DTS Mode Z128k. I had tried dolby pro logic 2/3 but the way it boosted the volume was just too much. DTS Mode has worked out well so far. What about you?
trentonite said:
For my IRS profile I'm using DTS Mode Z128k. I had tried dolby pro logic 2/3 but the way it boosted the volume was just too much. DTS Mode has worked out well so far. What about you?
Click to expand...
Click to collapse
I typically stick to dolby irs. But the main difference in sound is made by the profiles in viper4arise. I love the Audiophile X profile. Amazing fidelity on rock songs.
trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
Is it possible to flash after the procedure above -Viper4Arise?
Hi guys, I just bought my 3T, rooted and installed TWRP. Now I`m trying to install V4Arise, but with no success. I tried Freedom ROM... In this ROM V4Arise works fine, but the cell battery drains too fast. I returned to stock ROM... But I dont know how to install V4Arise in stock ROM. Could you help me?
So i've seen a lot of viper/viper4arise ( + Dolby + etc ) on many threads...
with maybe way too many versions..
On 7.1.1 default OOS 4, I have mine worked just fine with the one coming from magisk repo.
I've tried the one from Magisk 14.5, processing says Abnormal..
and i can hear crackle sounds in the background when playing music.
Decided not to clutter my magisk modules with install/reinstall, i immediately restore from nandroid backup with clean magisk
( plus one google camera patch module only. )
So have anyone got anything worked on our new OOS 5.0 ?
preferably with Dolby atmos working ? i've never tasted this one on my 1+ device ever...
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
nicknacknuke said:
On 7.1.1 default OOS 4, I have mine worked just fine with the one coming from magisk repo.
I've tried the one from Magisk 14.5, processing says Abnormal..
and i can hear crackle sounds in the background when playing music.
Click to expand...
Click to collapse
If you're talking about the repo on the Magisk Manager, those V4A versions are horribly outdated.
Try the modules by ahrion, downloaded from the thread: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
I personally have v2.0 working perfectly with Magisk 14.3. But also needed SELinux permissive module to process properly. Yeah, I know, a of folks are not going to want to set SELinux to permissive. But I'm just sharing what worked for me.
v2.3 wouldn't work properly for me. But one of the devs told me that I should delete all V4A and AML (Audio Mod Libs) and try to install through TWRP. Haven't had a chance to retry it doing all that. If you still have troubles, you can post the TWRP recovery log on the above thread, and they will try to help you out.
Dolby Atmos does not work on Oreo. Do NOT flash, bootloop is a possiblity.
This is how I got V4A working with OOS oreo. I had to set SELinux to permissive.
1. Use Magisk v14.5
2. Install 'Magisk SELinux Permissive Script' module by jman420 from within magisk manager (Modules -> + button -> select file)
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
3. Reboot. Optional - Install 'Display SELinux status' module in magisk
4. Install 'Viper4Android FX for Magisk v14+' v4.0 by ShadySquirrel in magisk manager. You can get it from Magisk repo. (Other V4A modules might work too.)
5. Reboot and voila!
Okay... so far there are 3 alternatives to get this audio mod in Oreo
I will try them and test...
Let's say, this is my attempt to keep track of how to install in oreo..
Thank you guys for all the suggestions ( and warning ! )
talpes said:
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
Click to expand...
Click to collapse
did this version require any SELinux permissive trickery?
Brian
Yes it does but you don't have to install separate apps or magisk modules to archive that. After you flashed the whole thing, open Viper - Settings - Turn on developer mode and disable SELinux. That's it.
Talpes
redpoint73 said:
If you're talking about the repo on the Magisk Manager, those V4A versions are horribly outdated.
Try the modules by ahrion, downloaded from the thread: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
I personally have v2.0 working perfectly with Magisk 14.3. But also needed SELinux permissive module to process properly. Yeah, I know, a of folks are not going to want to set SELinux to permissive. But I'm just sharing what worked for me.
v2.3 wouldn't work properly for me. But one of the devs told me that I should delete all V4A and AML (Audio Mod Libs) and try to install through TWRP. Haven't had a chance to retry it doing all that. If you still have troubles, you can post the TWRP recovery log on the above thread, and they will try to help you out.
Click to expand...
Click to collapse
On my attempt with your method, It installs just fine with TWRP, but fail on running.
- Installed just fine with TWRP, no errors. (*)
- Reboot, but i can not find the V4A apps in drawer...
- So i opened up the zip file, extract the APK from v4afx-v2.3.zip/system/app/ViPER4AdnroidFX.apk.
- Install it manually, then it shows up in drawer.
- Everytime i try to run it.. it keeps asking to install drivers. I assume because it wasn't install in /system
( confirm install, reboot, then it asks to install again when i open it ).
So i decide your method does not works well on my device... or i may have missed something in the steps.
( Stock OOS 5.0, Bluspark's 8.54 TWRP, Magisk 14.5 )
fluster84 said:
This is how I got V4A working with OOS oreo. I had to set SELinux to permissive.
1. Use Magisk v14.5
2. Install 'Magisk SELinux Permissive Script' module by jman420 from within magisk manager (Modules -> + button -> select file)
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
3. Reboot. Optional - Install 'Display SELinux status' module in magisk
4. Install 'Viper4Android FX for Magisk v14+' v4.0 by ShadySquirrel in magisk manager. You can get it from Magisk repo. (Other V4A modules might work too.)
5. Reboot and voila!
Click to expand...
Click to collapse
Your method works OK on my device :good:
so we are only limited to v4A ? no Arise, or Dolby atmos ?
i see some OP3T users saying they got it working on their device with Oreo ..
talpes said:
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
Click to expand...
Click to collapse
It said aroma, i'm on stock ROM.. is it safe ?
I will take nandroid backup and try it...
EDIT:
My mistake for not understanding aroma installer.
Tried your method, only install v4a 2.5, and DD Plus..
No errors, when playing music, V4A says abnormal. Second tries, i can not even get the Driver Status to popup.
Dolby Digital seems to work, but it quit everytime i changed the mode, but sound does noticably change.
*rolling back to nandroid backup*
nicknacknuke said:
On my attempt with your method, It installs just fine with TWRP, but fail on running.
- Installed just fine with TWRP, no errors. (*)
- Reboot, but i can not find the V4A apps in drawer...
- So i opened up the zip file, extract the APK from v4afx-v2.3.zip/system/app/ViPER4AdnroidFX.apk.
- Install it manually, then it shows up in drawer.
- Everytime i try to run it.. it keeps asking to install drivers. I assume because it wasn't install in /system
( confirm install, reboot, then it asks to install again when i open it ).
So i decide your method does not works well on my device... or i may have missed something in the steps.
( Stock OOS 5.0, Bluspark's 8.54 TWRP, Magisk 14.5 )
Click to expand...
Click to collapse
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
redpoint73 said:
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
Click to expand...
Click to collapse
Could you upload v2.0?
redpoint73 said:
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
Click to expand...
Click to collapse
my bad for not paying attention
but i'm a bit reluctant to downgrade my magisk
i've managed to get mine working as per Post #5,
i saw there's a new version just came out from ahrion ( v4afx-v2.4.zip , 11/30/2017 ).
I might gonna give it a try also with magisk 14.5...
I've tried installing the driver multiple times and can't seem to make it work at all. The only method I've not been able to accomplish is renaming audio_effects.conf to audio_effects.conf.bak as has been recommended for other phones. For some reason, this file will not rename.
it would seem the file is set to be unwritable (I'm not familiar with linux permissions like this, so maybe that can be fixed somehow?). At the very least, Solid Explorer isn't able to do the job, and can't change the rw perms either, as the operation just fails. (I have got selinuxmodechanger changed to permissive and after reboot, but no change here either)
Any other ideas?
Well, for anyone else wanting to know how to make this work, follow this guide here: https://thedroidarena.com/install-viper4android-android-10-q/
Don't use the magisk module for V4A, it doesn't work.
Works great for me now!
I'm using it it works perfect but you have to use the new version not the older one
Sent from my ASUS_I003DD using Tapatalk
Matakor said:
Well, for anyone else wanting to know how to make this work, follow this guide here: https://thedroidarena.com/install-viper4android-android-10-q/
Don't use the magisk module for V4A, it doesn't work.
Works great for me now!
Click to expand...
Click to collapse
I followed the instructions above, but it doesn't work.
Matakor said:
Well, for anyone else wanting to know how to make this work, follow this guide here: https://thedroidarena.com/install-viper4android-android-10-q/
Don't use the magisk module for V4A, it doesn't work.
Works great for me now!
Click to expand...
Click to collapse
Do you still have that apk lying around? XDA Labs does not appear to be working ATM.
bencozzy said:
JamesDSP works
Click to expand...
Click to collapse
I saw that, didn't really know what it did. I'll check it out.
Nothing in JamesDSP is doing anything for me on Speakers, Headphones, or Bluetooth. I think that this may beacause of my failed install of V4A rootless (might work if I had the APK?). Any ideas if this is the problem? If It is, do you know how I might uninstall V4A?
If rooted, try installing latest V4A directly from here (https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx) rather than via Magisk.
I prefer older V4A versions, having tried above.
My preferred V4A is 2.5.0.5 (found in App folder in following .zip from here: https://androidfilehost.com/?fid=673368273298920860)
1. Ensure on latest BusyBox.
2. Install latest V4A from Magisk & download driver, device will auto-restart.
3. Uninstall this latest V4A (don't delete data or cache).
4. Install V4A 2.5.0.5 .apk from above link. Don't open app yet.
5. From Magisk, install Audio Modification Library (choose relevant options). Restart device.
6. Additionally, Magisk install Audio Compatibility Patch. Restart device.
7. Ensure V4A settings FX compatible mode option = Normal.
(Don't optmise V4A in battery settings).
Noticeable improvement in speaker volume (I don't play over BT or headphones, so cannot comment).
elmor0 said:
If rooted, try installing latest V4A directly from here (https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx) rather than via Magisk.
I prefer older V4A versions, having tried above.
My preferred V4A is 2.5.0.5 (found in App folder in following .zip from here: https://androidfilehost.com/?fid=673368273298920860)
1. Install latest V4A from Magisk & download driver, device will auto-restart.
2. Uninstall this latest V4A (don't delete data or cache).
3. Install V4A 2.5.0.5 .apk from above link. Don't open app yet.
4. From Magisk, install Busybox & Audio Modification Library (choose relevant options). Restart device.
5. Additionally, Magisk install Audio Compatibility Patch. Restart device.
6. Ensure V4A settings FX compatible mode option = Normal.
Noticeable improvement in speaker volume (I don't play over BT or headphones, so cannot comment).
Click to expand...
Click to collapse
I uninstalled everythingg I had installed up to that point (everything I could at least), and followed the instructions step by step. Still getting abnormal in the V4A app (at least the app looks cooler now : P). I really don't know what is going on at this point. I might just reset the whole phone and follow your instructions again. I will report back when I get around to that.
Ok, I decided to play around a little before trying a reset; and I installed Viper 4 Android legacy with the APK from the zip you gave me, and it now says audio format supported! Yay! It just says "Processing: no" now. I have a feeling that I have something setup wrong. Any ideas?
Edit: Grammer
You managed to install driver v.2.5.0.5 or latest v4a?
Processing should change to "Yes" whilst audio is playing (music player/ YouTube/ system sounds etc).
Streaming music can be hit & miss; set up Audio Compatibility Patch correctly (via Magisk).
elmor0 said:
You managed to install driver v.2.5.0.5 or latest v4a?
Processing should change to "Yes" whilst audio is playing (music player/ YouTube/ system sounds etc).
Streaming music can be hit & miss; set up Audio Compatibility Patch correctly (via Magisk).
Click to expand...
Click to collapse
I installed driver version 2.5.0.4 with the APK you pointed me towards in the .zip/viperfx/app folder.
I will reinstall the audio conpatibily patch. What options should I choose in the patch?
Edit: I did not install the driver *with* the APK, but alongside it. I installed the driver via ViperFX Legacy in Magisk.
Try the ACP if V4A not working for streaming music apps.
I selected following:
- Skip audio_policy patching? = NO
- Skip notification_helper remover? = YES
- Skip usb policy patching for usb dacs? = NO
- Use lib workaround? = NO
Error-404-Go-Home said:
Edit: I did not install the driver *with* the APK, but alongside it. I installed the driver via ViperFX Legacy in Magisk.
Click to expand...
Click to collapse
That's fine, as long as V4A driver is enabled/ status normal/ format supported/ and it is processing during audio play.
elmor0 said:
That's fine, as long as V4A driver is enabled/ status normal/ format supported/ and it is processing during audio play.
Click to expand...
Click to collapse
It still isn't processing audio : (. I have tried resetting and following your instructions again. The only way I am able to get it to stop displaying "Status: Abnormal" is by installing Viper4Android FX Legacy in the new driver mode with the user app, then installing the Audio Modification and compatibility patch, then restarting and installing the APK you gave me. Even with all that, it will not recognize audio being played (it displays "Processing: No" when audio is very clearly playing and I have effects enabled). I am now considering switching to LineageOS (I would be there already if it wasn't for the fingerprint sensor driver being broken).
Edit: Do you think switching kernels would change anything?
Edit 2: I noticed a toast notification from V4A on startup saying "A running program has requested Android to disable audio effects, so V4A will be temporarily disabled."
I am thinking that maybe the stock Dirac audio processing might be interfering with V4A somehow. Is there anyway to get Viper to ignore requests to disable?
Well, Lineage didn't fix anything (No matter what I did, V4A would not stop displaying abnormal). Took me a little while to get back to stock, but the latest version of V4A is working, but only for the first 30 seconds after reboot before giving me the previously mentioned toast notification. I have removed all apps that are even remotely audio processing related, but still have this problem. Anybody else had something similar? If you did, how did you fix it?
(Also, special thanks to elmor0 for all of your help getting me this far I'm so close)
Edit: Holy shiz it's working! I used the method described in my previous post, but with the added step of uninstalling and reinstalling audio modification library after the last reboot. Again thank you all for your help! And I really hope this helps someone!
Error-404-Go-Home said:
Edit: Holy shiz it's working! I used the method described in my previous post, but with the added step of uninstalling and reinstalling audio modification library after the last reboot. Again thank you all for your help! And I really hope this helps someone!
Click to expand...
Click to collapse
hi
I'm having the same problem for months now
I hear it needs SE Linux to be permissive for V4A to work properly
I had no success on getting that SE Linux to turn Permissive unfortunately
long story short , I found myself here
can you please give me a step by step on how you got V4A to work , that is off course if its still working for you man
I'm at the end of my rope here , any guidance would appreciated ,
Thanx
JimmyMX said:
hi
I'm having the same problem for months now
I hear it needs SE Linux to be permissive for V4A to work properly
I had no success on getting that SE Linux to turn Permissive unfortunately
long story short , I found myself here
can you please give me a step by step on how you got V4A to work , that is off course if its still working for you man
I'm at the end of my rope here , any guidance would appreciated ,
Thanx
Click to expand...
Click to collapse
I ended up refllashing with Lineage and installing this: https://forum.xda-developers.com/t/app-fix-100-working-viper4android-for-android-11-devices.4213647/
That version has worked flawlessly for me for Android 10 and 11.
Good luck!
All features are working. If you follow the process as described, viper4android works fine on YouTube and all platforms. Moreover, it eliminates the problem of voice reduction when forwarding videos.
Tested PE PLUS (A10) and PE (A11) OFFİCİAL
Before you start installing the Sound Mode, install the SELINUX PERMİSSİVE file with MAGİSK and restart the device.
FOLLOW THE PROCEDURES IN THE ORDER
1. Install the Viper4Android FX zip file with Magisk and
Open the Viper4Android FX application and install the driver and restart.
2a. Install the Audio Modification Library file with Magisk.
2b. Install the Audio Compatibility Patch file with Magisk. ---> Options will be as below.
Volume UP - Volume UP - Volume DOWN - Volume DOWN - Volume DOWN
Restart the device.
3. Open the Viper4Android FX application and activate LEGACY MOD in settings.
DONE.
(FOR SETTİNG FILES)
VIPER4ANDROID_DDC-KERNEL-PRESET FOLDER
---> Copy to folder Android / data / com.pittvandewitt.viperfx / files.
MY SETTİNG FOR HEADPHONES and SPEAKER ---> Viper4Android_DDC-KERNEL-PRESETS File
FİLES :
https://www.dosyaupload.com/ou0i
https://www.dosyaupload.com/ou0k
https://www.dosyaupload.com/ou0l
https://www.dosyaupload.com/ou0m
https://www.dosyaupload.com/sH1O
Update ---> DDC-KERNEL-PRESETS
First of all i want to thank you for the clear and detailed guide...
i have few questions tho, is there any way to install without switching SELINUX to permissive?? my concern here are the security issues
also can i add ainur narsil along with V4a, or is it even worth it?! if yes then what the installation process would be??
thank you in advance!
Obito_Sama said:
First of all i want to thank you for the clear and detailed guide...
i have few questions tho, is there any way to install without switching SELINUX to permissive?? my concern here are the security issues
also can i add ainur narsil along with V4a, or is it even worth it?! if yes then what the installation process would be??
thank you in advance!
Click to expand...
Click to collapse
Unfortunately viper doesn't work properly without selinux permissive.
You can try different sound modes. however, problems occurred when I tried it on pe +. Also I don't think an extra sound mod will be needed after making good adjustments with the viper.
ryukseloglu said:
Unfortunately viper doesn't work properly without selinux permissive.
You can try different sound modes. however, problems occurred when I tried it on pe +. Also I don't think an extra sound mod will be needed after making good adjustments with the viper.
Click to expand...
Click to collapse
Somehow v4a works fine with selinux enforcing on my xz premium, less headache for me
Hey all,
some tips on getting ViPER4Android to work on your S21 / OneUI 3.1.
Disable Sound Alive via ADB or a root solution of your choice (not sure if this is actually needed, but I recommend to do so). You can use the Dolby Atmos Magisk module by repey6 if you still want Atmos.
Install the Audio Modification Library module from Magisk
Install the ViPER4Android module from Magisk
Go to /sdcard/ViPER4Android and install the apk that the Magisk module has put there
Open ViPER4Android, grant root access and let the driver install (your phone will reboot immediately)
After the reboot, go to Magisk and disable the Audio Modication Library and reboot again
After the reboot, open ViPER4Android and install the driver again
After the reboot, re-enable Audio Modification Library and once again... reboot.
Now go to ViPER4Android settings and enable Legacy mode (you will have an abnormal driver status otherwise).
You should be good now.
You do not need to set selinux to permissive. Yep, 4 reboots to make it work, but hey - good sound!
Works with Ainur and Dolby Atmos as long as you use AML. I recommend to do this installation procedure after you have installed the other sound mods.
Note: If you only want to use ViPER, no other sound mods, it might be possible to just perform step 1, 3, 4, 5 and 9 (not tested). If not, do all steps.
If it still does not work you can try to add the Audio Compatibility Patch module. There is also another thread here, providing useful information.
Best regards,
lartsch
Thanks for sharing
Thanks for that, I was having a tough time installing it on the tab s7+ maybe this will work...