Related
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
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 have kitkat lineageos 14.1, everything works fine, seem to be rooted, I'd like slightly louder bluetooth but if i try to change any settings in dsp manager it does nothing, tried to install viper4android but wouldn't install drivers.
Any idea what could be missing?
edit, nevermind, needed supersu to get v4a working.
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!
Hello, firstly sorry for bad english. My device is a Samsung s3 mini running 4.2.2 touchwiz. I'm trying to make that old phone my music player with viper4android. I installed latest magisk and magisk manager. Whenever I install a module installation happens without any issues. But after a reboot I can't see any changes that module makes. For example after installing viper4android it seems like it's installed on magisk manager but there aren't a app on app drawer, I tried few a more modules such as audio library patch etc. they all behave same. Looks like installed but has no effect over system. Secondly when I try to uninstall any of the modules it won't uninstall. I uninstall, reboot and it's still there. What can I do to solve my problem?