Database Develop

How to install Viper4android Fx on Moto X Android 6

Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!

Well mine has problem of installing the sound driver.
通过我的 XT1096 上的 Tapatalk发言

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
How did you install the viper4android via apk or you flashed from recovery?

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
KazuhiroYasei said:
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".
Click to expand...
Click to collapse
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.

brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.

KazuhiroYasei said:
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.
Click to expand...
Click to collapse
Yes. I was only able to enjoy v4a after this procedure.

It's worth pointing out that V4A is going to F up your Moto Voice

Popping into this thread real quick to provide some info,
Using compatibility mode with V4A is bad news, causes extra battery drain and problems with some apps.
For every single rom and device I've used 5.0+ I've followed the same procedure to install V4A, without using compatibility mode, without having to delete a file every time, etc.
Flash the "lolliviper" zip attached to this OP.
Followed by the "Build.Prop-Tweaks" and "Soundfix-LibFiles" attached to this post.
You'll also need a way of setting selinux to permissive after every boot if you're using CM or something else with selinux set to enforced. Something like SELinuxModeChanger available here will work.
If you don't have busybox installed, V4A will tell you and help you install it.
The V4A version included in the "lolliviper" zip is not the newest , you'll need to "Check Update" via the 3 dot menu and install the latest apk.
After all this, install the driver via the V4A app, reboot, and you're golden.

Flipz77 said:
It's worth pointing out that V4A is going to F up your Moto Voice
Click to expand...
Click to collapse
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?

brunoperissotti said:
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?
Click to expand...
Click to collapse
Actually it still "works" because it detects your launch phrase, but after that, half of the time it just hangs without hearing your command. Sometimes it'll randomly work, but it was too much of a botch to keep it that way. I've now resorted to Noozxoide Pro: it's still a system-wide mod with modes for headset, speaker and BT, but it's installed as a "standard" app, it doesn't mess with your system and it sounds boss!

I ran across this link on a similar search on the google machine, and it made V4A installation a breeze. No manual messing with kernel settings and whatnot: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Battery life has been fine running this for about a week. I don't use Moto Voice so can't comment on that.

THANKS
brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Thanks a lot, I was already discouraged, tried several versions of viper, on diferent roms, this was the only solution, but is necessary to remember that for this file to appear in the folder, you need to open the application and save a profile, even if empty, without it you can not find the file audio_effects

If u root ur device using magisk, u can install viper magisk module...it works fine on android 6.0 with selinux enforcing..
Sent from a Motobot

ViPER4Android FX Legacy/XHiFI [Unity][Deprecated]

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..

[MODULE][DISCONTINUED] Magisk SELinux Permissive Script

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.

Viper4Arise Install Guide

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?

OOS 5.0 : Viper? Dolby ?

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...