Related
Deprecated - Use the New ViPER4Android v2.7:
GO TO THE THREAD LINKED ABOVE. You don't need to flash any zips. Just install it as a regular apk, allow it to install the drivers, and you're good to go.
For magisk users: I made a zip on the repo that includes the original vdc's and my profile converter (will convert your old profiles to the new and better format).
For rootless users: I made a zip to install drivers and such
Zips can be found here
ALL SUPPORT QUESTIONS FOR 2.7 SHOULD BE AT THE THREAD ABOVE.
This is ViPER4Android FX and Xhifi Unity installers
These installers utilize my Unified installer that can install on Magisk OR System if Magisk is not detected (with Pixel support).
Credits of Originality:
- @zhuhang (Official Thread)
- @Osm0sis
- Viper's Audio (Official blog)
- @ViPER520
- @Team_DeWitt
Special Instructions:
If you already know which original v4a you want to use, just add 'old' for 2.3.4.0, 'mid' for 2.4.0.1, 'new' for 2.5.0.5, or 'mat' for material to the zipname prior to flashing.
If you already know if you want it installed as a user or system app, add "uapp" for user app or "sapp" to system app to zipname.
If you already know if you want to apply the libstdc++.so lib workaround, add "lib" or "nlib" to zipname (note that there are some devices that are already known to require it and so they'll apply workaround regardless of choice)
If you already know if your device/rom requires the v4a open/close/fc audioserver workaround, add "ocw" to zipname. Otherwise, add "nocw" to zipname
To skip volkeys (if your device isn't compatible with them), add "novk" to the zipname. Note that if you don't specify the above, defaults will be applied which are: sapp, new
Make sure there are no spaces in the zipname
Audio Mod Troubleshooting Guide
Downloads
XDA:DevDB Information
ViPER4Android FX Legacy/XHiFI [Unity], App for the XDA Community Apps
Contributors
ahrion, Zackptg5
Version Information
Status: Stable
Current Stable Version: v4.4
Stable Release Date: 2019-08-11
Created 2019-01-18
Last Updated 2020-01-01
great!
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
kartikb said:
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
Click to expand...
Click to collapse
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
ahrion said:
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
Click to expand...
Click to collapse
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Magisk limitation. @topjohnwu is always improving magisk. I do recommend may e trying another kernel for your device which may help compatibility.
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
Didgeridoohan said:
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
Click to expand...
Click to collapse
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
ahrion said:
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
Click to expand...
Click to collapse
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
You are literally advertising your mods in everyone's threads. Stop this and make your own thread.
This is a magisk forum, not a system mod forum.
Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
I will remove it with next release. Thank you man. This **** only started happening with 11.6. this was the reason Atmos was boot looping as well so I removed system.prop in Atmos.
Can you do me a favor and remove a few lines to see if it's just the specific lines? I think that certain lines don't play nice with your phone.
Remove the first part, low power audio tweaks, reboot and see if it works. If it doesn't then that's the culprit. If not then remove the first two on the other audio tweaks.
Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
kartikb said:
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
Click to expand...
Click to collapse
Enable permissive.
Turn off audiofx
ahrion said:
Enable permissive.
Turn off audiofx
Click to expand...
Click to collapse
I'll try again when I get a chance to. Thanks for the suggestion.
[UPDATED] ViPER4Android FX <2.5.0.5>
v1.1:
- Updated to Audio Modification Library (Magisk) v1.1
This should fix the boot loop issues seen in only Magisk v11.6
Download: Link - Mirror
Previous Changelogs (Unified installer):
HTML:
V1.0:
- Initial release
- Smali edits to automatically enable storage permissions
- Audio Modification Library v1.0 is included
- Unified installer that will install mod for both Magisk and System
- Pixel support included
- Magisk Template v3 support
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
Try 1.1.
ahrion said:
Try 1.1.
Click to expand...
Click to collapse
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
kartikb said:
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
Click to expand...
Click to collapse
Flash my deep buffer remover. Look in the magisk forum.
ahrion said:
Flash my deep buffer remover. Look in the magisk forum.
Click to expand...
Click to collapse
Thanks, it all finally works on my Nexus 6P. Now to try on my OnePlus 3..
AS OF 03/07/2018
Support and development of this module have been discontinued.
A replacement module can be found here : https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
This module has been tested on and is compatible with Magisk v11.6-15.2.
Disclaimer & Recommendations: This module should be used as a last resort only if appropriate SELinux Permissions can not be generated and injected into the SELinux Policy using selinux-inject, supolicy or magiskpolicy. Putting your device into Permissive Mode will essentially disable all of the operating system level security built into Android and allow any app in any context to do whatever it wants. Actions requiring root access will still trigger your SU Manager App, but all apps have elevated privileges due to permissive and may be able to take malicious actions on your device without needing root access. If you find that this module fixes issues you are experiencing with an app I recommend contacting the app developer and trying to work with them to isolate the necessary SELinux Permissions and have them injected into the SELinux Policy at startup.
Here is a discussion of some of concerns to consider when running your device in Permissive Mode : https://forum.xda-developers.com/general/general/discussion-root-selinux-risks-t3607295
Github Repo : https://github.com/Jman420/magisk-permissive-script
Change Log :
v1.0 - Initial Release
v1.1 - Update to Module Template v1400
v1.2 - Update to Module Template v1500
thank you brother!
LeEco LePro 3 Atmos can work finally!
huaiyue said:
thank you brother!
Can you tell me how to install LeEco LePro 3 Atmos ?
I hava supersu systemless.
Click to expand...
Click to collapse
These two things are completely unrelated.
If you want to install something, you install it. There's not much more to that.
huaiyue said:
thank you brother!
Can you tell me how to install LeEco LePro 3 Atmos ?
I hava supersu systemless.
Click to expand...
Click to collapse
In Magisk, go to the Modules section, and select the "+", and select the zip you downloaded.
Jman420 said:
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
Github Repo : https://github.com/Jman420/magisk-permissive-script
Click to expand...
Click to collapse
LeEco LePro 3 Atmos can work
however
xposed systemless failed.
---------- Post added at 01:32 ---------- Previous post was at 01:31 ----------
ahrion said:
These two things are completely unrelated.
If you want to install something, you install it. There's not much more to that.
Click to expand...
Click to collapse
http://imgur.com/a/Sbf9p
dolby fc.
---------- Post added at 01:36 ---------- Previous post was at 01:32 ----------
jhedfors said:
In Magisk, go to the Modules section, and select the "+", and select the zip you downloaded.
Click to expand...
Click to collapse
thank you brother!
Thanks a lot
huaiyue said:
thank you brother!
LeEco LePro 3 Atmos can work finally!
Click to expand...
Click to collapse
Regarding your other post mentioning Xposed (which I'm not quoting cause it's a mess). I'm running on Nougat so I can't use Xposed and haven't tested with it. If you give me more details I can try to determine what the issue is. Logs, error messages, symptoms would all be helpful.
Thor™ said:
Thanks a lot
Click to expand...
Click to collapse
I aim to please
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
its working with s5neo?
I've just flashed this zip. This allows Viper4Android to run in enforcing mode:
https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
I forgot the source. Maybe Google it
matssa said:
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
Click to expand...
Click to collapse
I agree that Magisk hides the actual SELinux Mode in such a way that if Magisk Hide is enabled the 'getenforce' command always returns 'Enforcing'. But if you do not run the 'setenforce 0' command the SELinux mode will still be set to 'Enforcing' rather than 'Permissive'. This script puts the SELinux mode into 'Permissive' at startup. Magisk Hide will still hide the fact that you are in Permissive Mode, which I believe is the 'pseudo permissive' mode that Magisk describes. But I can not find any settings or commands within Magisk that enable Permissive Mode.
htr5 said:
I've just flashed this zip. This allows Viper4Android to run in enforcing mode:
https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
I forgot the source. Maybe Google it
Click to expand...
Click to collapse
It's just a shell script, the source is in the zip file. This is really helpful and is the direction I want to take this project. Permissive Mode is great in that it gets the Apps/Mods that we want to run to work, but I consider it the equivalent of using a sledgehammer to hammer in a finishing nail. I would much rather be able to grant the specific permissions that each App needs rather than enable all permissions for all apps (which is what permissive mode does).
I plan on trying to develop an App which will assist in managing and generating a script which uses 'supolicy' to inject individual SELinux Policy Permissions. I had planned on using the Dolby Atmos LePro3 build as a guinea pig to try to isolate which permissions it needs and put together the supolicy command for them. I've hit a bit of a roadblock in verifying my supolicy command due to the format that the SELinux Policy is stored in on the device. I've found a project called sedump (https://ge0n0sis.github.io/posts/2015/12/exploring-androids-selinux-kernel-policy/) which claims to deserialize the Binary SELinux Policy to a readable format, but I can't seem to get it to work... the process seems to complete, but it generates an empty file... If anyone has experience with SELinux I'd really appreciate any feedback.
cosmin691 said:
its working with s5neo?
Click to expand...
Click to collapse
Dunno, I've only got an HTC 10 for testing. Give it a shot, if it doesn't work just uninstall the Magisk Package. Remember to disable Magisk Hide if you are testing to make sure it actually put your phone into Permissive Mode by using the 'getenforce' command.
It works for oneplus 3t on freedom OS rom.
Jman420 said:
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
Github Repo : https://github.com/Jman420/magisk-permissive-script
Click to expand...
Click to collapse
this zip must be flashed using twrp rite ? or stock recovery also will do fine ? because i tried many times to flash recovery for samsung e5 5.1.1 but ended up with boot loop. now running all stock !!
X_GOD said:
this zip must be flashed using twrp rite ? or stock recovery also will do fine ? because i tried many times to flash recovery for samsung e5 5.1.1 but ended up with boot loop. now running all stock !!
Click to expand...
Click to collapse
Should be able to install it through Magisk Manager or TWRP. Let me know if you have problems.
matssa said:
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
Click to expand...
Click to collapse
Now, I have magisk 11.6 on EMUI marshmallows V4A driver was abnormal because Enforcing selinux. Same happened with SuperSU 2.79. When I changed to permissive mode using terminal emulato/kernerl aduitor init.d script emulator/su.d SuperSU script, V4A driver was normal and it was processing. I like Magisk a lot because of its xposed like modules. Now using jman420's permissive magisk module.
Thor™ said:
Now, I have magisk 11.6 on EMUI marshmallows V4A driver was abnormal because Enforcing selinux. Same happened with SuperSU 2.79. When I changed to permissive mode using terminal emulato/kernerl aduitor init.d script emulator/su.d SuperSU script, V4A driver was normal and it was processing. I like Magisk a lot because of its xposed like modules. Now using jman420's permissive magisk module.
Click to expand...
Click to collapse
Without this module, ARISE is working fine, processing in 48000 on my side, so for V4A I don't think this is necessary, at least on my side.
Sent from my OnePlus3 using XDA Labs
matssa said:
Without this module, ARISE is working fine, processing in 48000 on my side, so for V4A I don't think this is necessary, at least on my side.
Click to expand...
Click to collapse
For ARISE I used to flash permissive script by osm0sis. Otherwise no luck with V4A, AM3D and Dolby.
Thor™ said:
For ARISE I used to flash permissive script by osm0sis. Otherwise no luck with V4A, AM3D and Dolby.
Click to expand...
Click to collapse
Strange... Did you enable magisk hide? If not, that is the reason.
Sent from my OnePlus3 using XDA Labs
matssa said:
Strange... Did you enable magisk hide? If not, that is the reason.
Click to expand...
Click to collapse
No, I was using SuperSU 2.79. Same happened with MagiskSU.
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!
Anyone got it working? I keep getting install driver loops.
Unless there is TWRP available, I wont try those risky flashing stuff.
Oh that's just easy hahah
Well here are the steps first you start clean so no audio modules or viper installed so delete them first then follow this steps
1. Open termux and type su -c setenforce 0 and to be sure type su -c getenforce if it stands on permissive
2. Flash viper module only so no other modules when it's done flashing don't reboot your device and startup viper then you need to install a module what the apps says then do it
3. DONT OPEN VIPER YET UNTIL YOU HAVE DONE THIS.
Then you go to /data/adb/modules/ViPER4AndroidFX and there you will see a file who is called post-fs-data.sh replace it with the one who has been send in this chat just overwrite it and then reboot
4. Open viper and you won't see any message popping up then it's means it works go to the settings and turn on legacy mode when that's done try to go to YouTube or any other music player like SoundCloud (btw i only have been testing it like that so maybe spotty works too) go back to your viper until you see this message jump away from the other (look at the screenshots)
5. If it is still not working and it doesn't hurt to install afterwards then install ainur narsil module don't reboot go back and flash audio modification library
HessNL said:
Oh that's just easy hahah
Well here are the steps first you start clean so no audio modules or viper installed so delete them first then follow this steps
1. Open termux and type su -c setenforce 0 and to be sure type su -c getenforce if it stands on permissive
2. Flash viper module only so no other modules when it's done flashing don't reboot your device and startup viper then you need to install a module what the apps says then do it
3. DONT OPEN VIPER YET UNTIL YOU HAVE DONE THIS.
Then you go to /data/adb/modules/ViPER4AndroidFX and there you will see a file who is called post-fs-data.sh replace it with the one who has been send in this chat just overwrite it and then reboot
4. Open viper and you won't see any message popping up then it's means it works go to the settings and turn on legacy mode when that's done try to go to YouTube or any other music player like SoundCloud (btw i only have been testing it like that so maybe spotty works too) go back to your viper until you see this message jump away from the other (look at the screenshots)
5. If it is still not working and it doesn't hurt to install afterwards then install ainur narsil module don't reboot go back and flash audio modification library
Click to expand...
Click to collapse
I'll try this when I'm off work.
HessNL said:
Oh that's just easy hahah
Well here are the steps first you start clean so no audio modules or viper installed so delete them first then follow this steps
1. Open termux and type su -c setenforce 0 and to be sure type su -c getenforce if it stands on permissive
2. Flash viper module only so no other modules when it's done flashing don't reboot your device and startup viper then you need to install a module what the apps says then do it
3. DONT OPEN VIPER YET UNTIL YOU HAVE DONE THIS.
Then you go to /data/adb/modules/ViPER4AndroidFX and there you will see a file who is called post-fs-data.sh replace it with the one who has been send in this chat just overwrite it and then reboot
4. Open viper and you won't see any message popping up then it's means it works go to the settings and turn on legacy mode when that's done try to go to YouTube or any other music player like SoundCloud (btw i only have been testing it like that so maybe spotty works too) go back to your viper until you see this message jump away from the other (look at the screenshots)
5. If it is still not working and it doesn't hurt to install afterwards then install ainur narsil module don't reboot go back and flash audio modification library
Click to expand...
Click to collapse
I'm still getting the driver loop. You have the zip to the ainur module?
Psych0t1c20 said:
I'm still getting the driver loop. You have the zip to the ainur module?
Click to expand...
Click to collapse
Then something's it wrong normal if you have placed the post-fs-data.sh in it then normally driver loop should have ended already delete everything of viper and try again
HessNL said:
Then something's it wrong normal if you have placed the post-fs-data.sh in it then normally driver loop should have ended already delete everything of viper and try again
Click to expand...
Click to collapse
What version/build of oos are you on? Maybe I need to update or something.
I'm right now on oos 11 but i used it with oos 12 and it was working okay and with colorOS 12.1 maybe you aml and ainur with it but i thought I posted the files but doesn't seem like it
HessNL said:
I'm right now on oos 11 but i used it with oos 12 and it was working okay and with colorOS 12.1 maybe you aml and ainur with it but i thought I posted the files but doesn't seem like it
Click to expand...
Click to collapse
Ok that's why. I'm on oos 12.1. It's prolly different.
It looks like OPPO decided to move audio_effects.xml to ODM instead of vendor like most other devices so V4A doesn't patch it.
I tried modding both vendor and odm to return original layout that other phones use and even used permissive selinux to make things go smoother but no luck. Then I patched the firmware manually and tried few other tricks too but no luck whatsoever on both OOS 12.1 and COS 12.1.
Ended up using Wavelet which isn't that bad but V4A has more customisation and better results.
As far as I remember I didn't have issues like ever with V4A not working on 8 Pro or any phone in fact, so it's pretty weird that it doesn't work here even with all these fix attempts.
Hi, just following up. Is anyone able to get this working on the Oneplus 10 pro? I'm on the global variant and I was unable to get viper working using the steps above. Thanks.
Psych0t1c20 said:
Ok that's why. I'm on oos 12.1. It's prolly different.
Click to expand...
Click to collapse
Really weird because i had this working in me OnePlus 9 pro too with colorOS 12.1
HessNL said:
Really weird because i had this working in me OnePlus 9 pro too with colorOS 12.1
Click to expand...
Click to collapse
I had it working on the OP9P as well on OOS 12, but on the OP10P none of the usual methods work for me. I keep getting the driver loop. Not sure what else to try.
kouzelnik3 said:
Unless there is TWRP available, I wont try those risky flashing stuff.
Click to expand...
Click to collapse
Won't SwiftBackup serve the purpose ?
Any body got this to work yet ?
HessNL said:
Any body got this to work yet ?
Click to expand...
Click to collapse
Been trying for about a week now. Nothing seems to work. I've tried aml, jdsp,ainur narsil,acp,permissive,viper12fix zip. I've tried different versions of viper. I've replaced the post-fs-data.sh with the one that worked for my OP9 pro that was running oos12. I know that the post-fs-data fix involves binding the two locations of the audio_effects.xml which on the OP9 pro is located /odm/etc and vendor/etc. On the OP10 pro they are located in odm/etc and vendor/odm/etc. I've tried changing the location to accommodate this, but no luck. I've been lurking and asked in the v4a telegram group trying to see if anyone with the 10 pro has got it to work, but it doesn't seem like it.
ecera said:
Been trying for about a week now. Nothing seems to work. I've tried aml, jdsp,ainur narsil,acp,permissive,viper12fix zip. I've tried different versions of viper. I've replaced the post-fs-data.sh with the one that worked for my OP9 pro that was running oos12. I know that the post-fs-data fix involves binding the two locations of the audio_effects.xml which on the OP9 pro is located /odm/etc and vendor/etc. On the OP10 pro they are located in odm/etc and vendor/odm/etc. I've tried changing the location to accommodate this, but no luck. I've been lurking and asked in the v4a telegram group trying to see if anyone with the 10 pro has got it to work, but it doesn't seem like it.
Click to expand...
Click to collapse
Hmm well i hope someone will find it out at the moment I'm only using 10 pro and i wanted some better audio settings i don't know if you know this app wavelet? It might work on every device but i didn't try it out yet i shaw this posted in one of the Viper4android channels
I never found Wavelet anywhere near as good as Viper
If I run "su -c dumpsys media.audio_flinger", it looks like the 10 pro using the libs from /vendor/lib64/soundfx/ while the 9 pro was using /vendor/lib/soundfx/. Not sure if there is a way to make it use the 32-bit lib folder.
ecera said:
Been trying for about a week now. Nothing seems to work. I've tried aml, jdsp,ainur narsil,acp,permissive,viper12fix zip. I've tried different versions of viper. I've replaced the post-fs-data.sh with the one that worked for my OP9 pro that was running oos12. I know that the post-fs-data fix involves binding the two locations of the audio_effects.xml which on the OP9 pro is located /odm/etc and vendor/etc. On the OP10 pro they are located in odm/etc and vendor/odm/etc. I've tried changing the location to accommodate this, but no luck. I've been lurking and asked in the v4a telegram group trying to see if anyone with the 10 pro has got it to work, but it doesn't seem like it.
Click to expand...
Click to collapse
After looking into it more I've come to the conclusion that both directories are the same on the OnePlus 10 pro. /odm/etc & /vendor/odm/etc is the same exact directory. So trying to apply the "mount -o bind /vendor/etc/audio_effects.xml /odm/etc/audio_effects.xml" fix won't do much for us in this case even if we add the "odm"(example: /vendor/odm/etc) because it's the same directory. I've found that audio_effects.xml exists in the following locations(refer to attachment).