Related
/////
THIS GUIDE WAS FROM THE NOVEMBER SECURITY PATCH ON NOUGAT!!! DO NOT DO THIS IF YOU ARE ON OREO CAUSE YOU WILL LOSE ALL SOUND!
IF YOU WOULD LIKE TO USE VIPER ON OREO/PIE DEVICES. PLEASE USE THE MAGISK MODULE AND/OR FIND A BETTER GUIDE WITH A COMPATIBLE ZIP
//////
Okay I have confirmed that sound mods work on the Moto z2 force with no issues whatsoever many probably know that
How to Install:
1.
make sure you have root and TWRP installed on your Moto Z2 force
2.
download this version of A.R.I.S.E.
https://androidfilehost.com/?fid=457095661767141554
3.
Place the zip file in the Internal storage of your device (so its easy to find)
4.
Boot into TWRP recovery and click install
5.
Find the file you put in your internal storage named;
ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip
And then swipe to install
6
An install wizard should appear and assuming that you haven't used this before select easy mode on the wizard and make sure you have it set to "install core engine then modules" and spam the hell out of the next button besides those 2 things
7.
TWRP screen should appear and you should boot into your device like normal
8.
ENJOY
SOME NOTES:
A.R.I.S.E AM3D DOES NOT WORK BUT OTHER THAN THAT EVERYTHING ELSE IS FINE
Update: DO NOT ATTEMPT TO INSTALL MAGNUM OPUS IT WILL FAIL
!!!!DISCLAIMER!!!!!
-I AM NOT RESPONSIBLE FOR A INCREASE IN GAS PRICES GETTING CHEATED ON BY YOUR WIFE OR A BRICKED DEVICE
Man.. I was going to try ARISE, but with all the concerns that I couldn't restore a nandroid because of data partition encryption, I just said screw it and I installed the v4a 2.3.4 module right from Magisk, and it works great with both USB Type-C to 3.5mm and Bluetooth.
I don't know if anyone's noticed or not, but Oreo has an entire section on Bluetooth audio protocol under the development options. Things like sample rate, bit rate, etc etc. I do know that v4a works with all protocols (SBC, AAC, aptX, aptX HD and LDAC), but if you up the sample rate to 96khz, it will NOT process. I usually use 48khz and it sounds great.
I installed arise and lost all audio on device . I don't know if it's a setting or something in aroma I should not have added or if it's viper settings I messed with .
I need to uninstall this how do I
Or how do I get sound back this is weird
joesee said:
Man.. I was going to try ARISE, but with all the concerns that I couldn't restore a nandroid because of data partition encryption, I just said screw it and I installed the v4a 2.3.4 module right from Magisk, and it works great with both USB Type-C to 3.5mm and Bluetooth.
Are you on Oreo 8.0 running V4A? Thanks!
Click to expand...
Click to collapse
climbhigh77 said:
Are you on Oreo 8.0 running V4A? Thanks!
Click to expand...
Click to collapse
Yes sir, I am. Since I got it working, I haven't touched anything in fear that it'll stop working. I haven't even made a nandroid. Twrp isn't installed, I just booted in it from adb.
Right on! I was also advised not to install TWRP. I flashed it and it seems to be working so far. Having other issues though like my camera and flash (flashlight) don't work now since installing magisk or the v4a which one I'm not sure but I assume magisk.
3/12/18 Update: camera and Flash are working properly now after a wipe Dalvik, cache and reboot.
Is anyone else having issues with viper4android working intermittently on Oreo? Sometimes it works but mostly it doesn't and I have no way to control it, toggling the switches does nothing and it doesn't matter if I reboot or not. It does work sometimes so I know the drivers are installed, and I've tried a fresh install a few times using the 2.3.4 version and the newest 5.0 version which produces the same result.
Is there a setting in magisk or Viper that I need to apply to to get it working seamlessly? I have systemless hosts check-in magisk already for ad blocking. There's got to be something I'm missing here. Any help is greatly appreciated thanks!
I was having this situation, the I disabled the music FX and it's gone for now
Flashlight stops because of selinux
Dolby Atmos for oreo works fine without any problems. You just have to find the working version in the last few pages of the mod thread.
Was able to get the latest ARISE, plus V4A, and Dolby ATMOS Oreo from guitardedhero working. I'm using SuperSU as I'm not a fan of Magisk. Flashed the latest ARISE, including the V4A 2.5.0.5. Crap, I made sure V4A opened and checked that the drivers were installed. But I may have flashed the ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk over the ARISE loaded v4a apk....? Try to see if the loaded apk works first. If not, flash Nougat_IO_test_fix.apk over: ViPER4Android_FX_v2505.zip Anyway, use this to set permissive: The.SELinux.Switch.ver.6.0.3.build.603.apk. Reboot. ARISE libs will be there and V4A should work. Sometimes you have to turn off the main power button for the V4A mod, go up to the corner button and exit. Clear out anything in recents. Then open V4A back up, and enable the power button. If music is playing, you will hear the change.
Ok.....Dolby. Go HERE and download the normal zip. Thank the dude, he's done a lot for us audiophiles. Flash it. Reboot. Apps will be there, and will likely forceclose. You have to extract the dolby zip and copy the libs from the dolby/lib and dolby/lib/soundfx files and paste them in the related folders in root /system/vendor and system/vendor/soundfx. You need to set the permissions to rw-r-r (644). Now save/reboot. Apps should work. I'm betting other libs/files weren't installed either, but just those got Atmos working, working well. Still looking through things and will verify later what else wasn't placed.:good:
Quick Question, I have used ARISE and Viper before and really like them but this is a Software Mod. I would just like to clarify that this Software Mod works on the actual Hardware Mod and if it does, does this Software Mod work on the Hardware Mod using a Custom ROM or Kernal? Can anyone confirm that yet?
androidddaaron said:
I installed arise and lost all audio on device . I don't know if it's a setting or something in aroma I should not have added or if it's viper settings I messed with .
I need to uninstall this how do I
Or how do I get sound back this is weird
Click to expand...
Click to collapse
Sorry about this... You may have to back up your internal then flash back to stock. This guide was from when our device was still on nougat. For Oreo I need you to install the module from MAGISK or find the magnum opus zip
Any GP 2 owner got error "Installation failed because of an I/O error. Try rebooting" after freshly installing (from magisk/twrp)?
Driver Version = 0.0.0.0
Enabled: No
Status: Abnormal
Audrio Format: Unsupported
Magisk Modules installed:
Busybox for Android NDK
Audio Modification librabry
universal deep_buffer removar
SeLinux mode changed to permissive.
No matter how many times I install/reboot this/phone, I always get this error.
OS = 8.1 w/ March Sec Update
Logcat
03-20 20:17:31.572 3573 3573 I ViPER4Android: System booted.
03-20 20:17:31.573 3573 3573 E ViPER4Android_Utils: [Fatal] Can't load libV4AJniUtils.so
03-20 20:17:31.573 3573 3573 I ViPER4Android: Jni library status = false
03-20 20:17:31.573 3573 3573 I ViPER4Android: Driver not configured correctly.
Click to expand...
Click to collapse
Get the one from zack it works flawlessly
Sent from my Pixel 2 using Tapatalk
I use the one from magisk actually works its the fx materialized one by ahrion and zack
Delta wolf said:
I use the one from magisk actually works its the fx materialized one by ahrion and zack
Click to expand...
Click to collapse
I've tried to install this several times and the driver never gets enabled. It asks to reboot in order to install the driver every time I open the app after rebooting the phone. Did you do anything special? What's the secret?
westhaking said:
I've tried to install this several times and the driver never gets enabled. It asks to reboot in order to install the driver every time I open the app after rebooting the phone. Did you do anything special? What's the secret?
Click to expand...
Click to collapse
You have to choose viper4android fx.
Thank you all for your replies. Zack helped me figure out the issue. I had installed Audio-Modification-Library module which was preventing A4A installation. Cheers!
Burninh2o said:
Thank you all for your replies. Zack helped me figure out the issue. I had installed Audio-Modification-Library module which was preventing A4A installation. Cheers!
Click to expand...
Click to collapse
Because of this post, I decided to install the Audio Modification Library module to see what it does. Oddly enough, for me, V4A actually started working after enabling this additional module and setting my kernel to permissive. Weird. Glad it's working now though!
westhaking said:
Because of this post, I decided to install the Audio Modification Library module to see what it does. Oddly enough, for me, V4A actually started working after enabling this additional module and setting my kernel to permissive. Weird. Glad it's working now though!
Click to expand...
Click to collapse
lol... nice!
I just had the same issue as a result of upgrading stock MIUI Android 7.1 ROMS on a Xiaomi Mi Max 2.
I solved it by:
1. In Magisk, disabled both Audio Mod Library and Viper4Android --> REBOOTed.
2. In Magisk, ENABLED both Audio Mod Library and Viper4Android. --> REBOOTed.
No driver errors and it works in Speaker and Headphone.
But I'm not getting any Viper Notification in the Shade or the Status.
Burninh2o said:
Thank you all for your replies. Zack helped me figure out the issue. I had installed Audio-Modification-Library module which was preventing A4A installation. Cheers!
Click to expand...
Click to collapse
This fix works flawlessly on the H918 running the Alpha 3.0 rom
Catalyst2012 said:
I just had the same issue as a result of upgrading stock MIUI Android 7.1 ROMS on a Xiaomi Mi Max 2.
I solved it by:
1. In Magisk, disabled both Audio Mod Library and Viper4Android --> REBOOTed.
2. In Magisk, ENABLED both Audio Mod Library and Viper4Android. --> REBOOTed.
No driver errors and it works in Speaker and Headphone.
But I'm not getting any Viper Notification in the Shade or the Status.
Click to expand...
Click to collapse
Stock Kernel too? I cannot get it to install drivers to save my life
MikeyLee said:
Stock Kernel too? I cannot get it to install drivers to save my life
Click to expand...
Click to collapse
Did you try Disabling/Enabling the modules in Magisk? I had to do this a few times before it worked. Viper status will report 'Processing: No' until you start playing a music file, then it should change to 'Processing:Yes'.
I was able to get the notification to show up by selecting the first option in Settings>Show Notification.
I've tried just about everything I can think of.
Here's what I don't get. I have 3 devices currently. All running Oreo. Huawei Mate SE, Xiaomi Redmi Note 3 and Ulefone T1. The Redmi Note 3 and Ulefone T1 both have V4A working fine and both kernels are Enforcing. The Huawei no matter how it's set refuses to work.
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
i had the same but then i tried to use the other viper release from magisk and it worked. there is this one called hifi and fx
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
dgunn said:
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
Click to expand...
Click to collapse
that works for like 10 mins and then it gets killed
byReqz said:
that works for like 10 mins and then it gets killed
Click to expand...
Click to collapse
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
dgunn said:
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
Click to expand...
Click to collapse
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
byReqz said:
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
Click to expand...
Click to collapse
I was unaware that you were using the magisk module. I could not get that one to work either
dgunn said:
I was unaware that you were using the magisk module. I could not get that one to work either
Click to expand...
Click to collapse
the normal one doesnt work with viper doewsnt it?
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
TheNetwork said:
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
Click to expand...
Click to collapse
it only works for a few mins that way
I'm using the Android p beta and i don't have the problems with viper as i did with oxygen os 5. it's always processing for my headphones, either plugged in or Bluetooth. the only exception is sometimes after receiving a call while listening to music, after the call is over and my music resumes, viper is no longer processing. not every time though. i used the latest magisk and the viper module in the screenshot.
i also didn't make any changes to conf files, just installed through magisk download. rebooted, opened viper fx, gave it storage permissions and turned it on.
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
TuxRuffian said:
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
Click to expand...
Click to collapse
as i said, idk why but its working now.and im on material now
byReqz said:
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
Click to expand...
Click to collapse
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
reaper000 said:
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
Click to expand...
Click to collapse
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
byReqz said:
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
Click to expand...
Click to collapse
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
reaper000 said:
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
Click to expand...
Click to collapse
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
byReqz said:
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
Click to expand...
Click to collapse
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
reaper000 said:
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
Click to expand...
Click to collapse
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
byReqz said:
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
Click to expand...
Click to collapse
And you replaced the audio_effects.conf file in /system/vendor/etc with the one from the downloaded zip?
(Sorry to belabor the point, but it's not clear to me you tried all that)
I am an audiophile and I make it a point to use audio mods whenever possible. That being said, the audio mods that I've tried and worked amazingly well are Viper4Android and Ainur Sauron, but you will also need Audio Compatibility Patch and Audio Modification Library to make things work so seamlessly.
That being said, I get to see a lot of people complaining about Viper4Android being too buggy in that after every restart, it asks for the driver to be installed again, etc. Well, I have clean flashed/dirty flashed plenty of ROMs now so I can honestly say that my method works.
So, what is my method for installing all of the audio mods I mentioned earlier? Well here are the steps:
1. Install Busybox for Android (in Magisk Repo)
2. Install Audio Compatibility Patch. It now comes with a multi-option installer, so you want to Select NO to the first option then choose Vol + (Patch New Logic). Select NO to the second option and then use Vol - (remove Volume Listener Library). This is done so that your audio won't crackle. You can skip USB Dac if you're not using it and you should choose NO at the last option (library workaround).
3. After Installing ACP with the chosen options, proceed to install Ainur Sauron.
4. Once that is done, install Audio Modification Library. After AML, DO NOT REBOOT YET.
5. Download the Viper4Android 2.7.1 APK here: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx . I find this to be the best iteration of the module since it is not buggy at all. Once that is installed, run the application and it will prompt you to install drivers for the first time, choose OK and then allow it to reboot. (Note: after installing this, a Magisk Module will be created automatically)
At this point, all of the audio mods should work in unison. Do not toggle anything else in Viper4Android but the main interface. This means that do not go to the settings and toggle anything. Just configure the audio options as per your liking.
6. Currently, the setup will bork BT audio which means that there is no sound that is going to come off of your BT speakers or headphones. What you need to do to fix this is as follows:
a. Rename "audio_policy_configuration.xml" in "/sbin/.magisk/img/aml/system/vendor/etc/audio" to "audio_policy_configuration.xml.bak".
b. Copy the audio policy configuration xml file from "/sbin/.magisk/img/aml/system/etc" to "/sbin/.magisk/img/aml/system/vendor/etc/audio".
c. Restart the device.
Additional Notes
a. When dirty flashing your custom ROM, allow the modules to recoup itself. In other words, do not touch anything until everything is back to normal (or after 5 minutes from dirty flashing).
b. If you happen to uninstall Ainur Sauron (or Narsil), I find that it usually uninstalls viper4android as well. If that is the case, uninstall Sauron and then click the viper4android app from the drawer and allow it to install drivers again.
c. In some devices, the BT workaround is no longer needed. However, I find that for the Pocophone, the workaround is still required. I guess you just have to test it for yourself if it works right off the bat or not.
d. Audio compatibility patch (remove patch logic) actually enhances the volume and the sound quality of the Poco F1. I cannot test this on other devices since I do not have another phone, but you can try and see if it works for you. (thanks to @Jonas G. Morsch for this).
e. If you are going to try Ainur Narsil, I suggest that you do not install viper4android anymore since it provides a great listening experience right off the bat. You can still install v4a, though if you really want it (The same procedure applies).
f. If you are using a custom ROM that has a built-in "AudioFX" app, you need to freeze it using Titanium Backup or similar apps for Viper4android to work. Thanks to @mikedavo for this tip.
g. If, after following all of the above instructions, and you still experience random driver issues or bugs, I suggest that you do a clean installation of your ROM and do the entire steps again. If it still presents the same error, I suggest that you hop on the Viper4android telegram channel to address your concern so that the dev can fix it.
h. Attached below is a profile converter, so if you're using the old version of Viper4android, you can use the attached file to convert all of your profiles to supported presets.
That's about it! If you have questions, feel free to drop them below. Happy listening!
man just what i needed. thank you very much. will try it later. :good:
Point 6 should be fixed. Possible a failure in Poco firmware or something. Use latest AML from Magisk repo. Also install all modules via magisk manager by now. Seems there is an issue and we are working in it.
Also I would replace Viper with JamesDSP.
JamesDSP future is bright and expect a tone of new **** in future. ?
Work as a charm in MIUI latest... But Bluetooth is working without step 6
Sent from my POCOPHONE F1 using Tapatalk
Hmm, I just make sure to disable and freeze any inbuilt audio equaliser or fx from custom roms before installing viper and have never had a problem with vipers drivers installing or instability in viper. I also, after installing viper, activate enhanced sound at the bottom of the sound menu in settings and choose my headphones in the dropdpwn, mine are mi inear pro. If I happen to forget to do this, I'll get the drivers need installing message from viper.
Use jamesDSP. Better ****. Has even 24-bit support. Viper just 16-bit. Also our viper guys teamed up with James. So expect some new **** soon.
it doesn't work for me at all, viper keeps asking to install driver and reboots the phone.. again and again
efakkawy98 said:
it doesn't work for me at all, viper keeps asking to install driver and reboots the phone.. again and again
Click to expand...
Click to collapse
Same here, i gave up after the tenth try
efakkawy98 said:
it doesn't work for me at all, viper keeps asking to install driver and reboots the phone.. again and again
Click to expand...
Click to collapse
Edit:- This worked perfectly for me even in the Secondary ROM with the following changes. V4A 2.7.0 instead of Latest 2.7.1 probably because I'm using Magisk 18.1 and V4A kept on asking to install driver even after reboot so I had renamed the MusicFX.apk in the System to MusicFX.apk.bak.
@BenParz Thank you very much for the guide.
This trick doesn't work with MultiROM for sure.
Will viper work with a bitrate of over 48k? My headphones us 96k which doesnt work with the buggy v4a i use, but its the only version of v4a that actually works at all for me (will try your way of installing later)
SVR said:
This trick doesn't work with MultiROM for sure.
Click to expand...
Click to collapse
I'm not using MultiROM. I'm on PE latest build
I've created a monster hehe. Ainur Sauron also installed
BenParz, i can't thank you enough for this! the choppy audio after installing Viper was making me crazy.
I'm running Lineage OS 05/18/2019 + nano gaaps
After mess around with this modules i got other way:
1 . Install Audio Compatibility Patch. It now comes with a multi-option installer, so you want to Select NO to the first option then choose Vol + (Patch New Logic). Select NO to the second option and then use Vol - (remove Volume Listener Library). This is done so that your audio won't crackle. You can skip USB Dac if you're not using it and you should choose NO at the last option (library workaround).
2. Download and install Viper4Android 2.7.1 Magisk Module here: https://zackptg5.com/downloads/v4afx_v2.7.1.0.zip .
More info : https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
3. Fix BT:
a. Rename "audio_policy_configuration.xml" in "/sbin/.magisk/img/acp/system/vendor/etc/audio" to "audio_policy_configuration.xml.bak".
b. Copy the audio policy configuration xml file from "/sbin/.magisk/img/acp/system/etc" to "/sbin/.magisk/img/acp/system/vendor/etc/audio".
4. Go to ViperFx and install drivers, Viper will auto Reboot!
I'm probably cutting some corners here, but i got no problems at all this far.
Jonas G. Morsch said:
BenParz, i can't thank you enough for this! the choppy audio after installing Viper was making me crazy.
I'm running Lineage OS 05/18/2019 + nano gaaps
After mess around with this modules i got other way:
1 . Install Audio Compatibility Patch. It now comes with a multi-option installer, so you want to Select NO to the first option then choose Vol + (Patch New Logic). Select NO to the second option and then use Vol - (remove Volume Listener Library). This is done so that your audio won't crackle. You can skip USB Dac if you're not using it and you should choose NO at the last option (library workaround).
2. Download and install Viper4Android 2.7.1 Magisk Module here: https://zackptg5.com/downloads/v4afx_v2.7.1.0.zip .
More info : https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
3. Fix BT:
a. Rename "audio_policy_configuration.xml" in "/sbin/.magisk/img/acp/system/vendor/etc/audio" to "audio_policy_configuration.xml.bak".
b. Copy the audio policy configuration xml file from "/sbin/.magisk/img/acp/system/etc" to "/sbin/.magisk/img/acp/system/vendor/etc/audio".
4. Go to ViperFx and install drivers, Viper will auto Reboot!
I'm probably cutting some corners here, but i got no problems at all this far.
Click to expand...
Click to collapse
Have you tried whatsapp voice notes?
Are they making crackling sound when app is minimized or screen is off while playing voice note?
Thanks a lot for such an easy guide.
hugolol said:
Will viper work with a bitrate of over 48k? My headphones us 96k which doesnt work with the buggy v4a i use, but its the only version of v4a that actually works at all for me (will try your way of installing later)
Click to expand...
Click to collapse
Well, you can actually change the Bluetooth bitrate setting in developer options. Doing that allows me to use V4a on my sony BT speaker (which uses LDAC).
slimshouki said:
Have you tried whatsapp voice notes?
Are they making crackling sound when app is minimized or screen is off while playing voice note?
Click to expand...
Click to collapse
Yeah, Whatsapp on Lineage crackles no matter what.
I'm dealing with this problem since my Zenfone 2 with Lineage 14 and no audio mod whatsoever, but never cared too much, because when i rarely listen Whatsapp audio files i do in foreground, and using the earpiece, . I also use telegram for 95+% off my conversations this days.
Hi Again!
After some time of testing, i think i got it how to use Audio Compatibility Patch (1.7.3+) with Lineage OS properly on our device:
Skip audio_policy patching?
- No
Patch flags or remove selections?
- Remove (old logic)
If patched the audio gets worse/lower on speaker/jack.
Would you like to skip notification helper?
- No
Remove notification helper effect or volume listener library?
- Remove volume listener library
Would you like to skip usb policy patching for usb dacs?
- Whatever
Use library workaround?
- No
If used causes bluetooth routing problems.
No Audio Modification Library needed.
After this sequence, my earphones,bluetooth and speaker worked fine with ViperFX 2.7.1, especially the jack, witch was really quieter and muffed before.
Can you guys try it out?
AudioModificationLibrary (AML) has been updated to 2.4. we've also updated unity modules. Everything should work now. Viper, James, Sauron and DTS.
At least on latest MIUI pie betas there should be no Bluetooth bug or anything.
There was a question regarding viper and above 48k.
Viper can just process up to 48. We've released yesterday the new module with DTSultra port. This is capable of up to 96k.
Nemuritor01 said:
AudioModificationLibrary (AML) has been updated to 2.4. we've also updated unity modules. Everything should work now. Viper, James, Sauron and DTS.
At least on latest MIUI pie betas there should be no Bluetooth bug or anything.
There was a question regarding viper and above 48k.
Viper can just process up to 48. We've released yesterday the new module with DTSultra port. This is capable of up to 96k.
Click to expand...
Click to collapse
What about bluetooth on PE and other custom ROMs?
received Buds Z for my OP9 purchase and have very slowly converting to the new phone (rooting, stability and assure privacy issues were addressed) and was very happy with their performance with my rooted OP6 on A11-Pixen OS with ViperFX. Without VIper, the sound is lackluster. even a downloadable EQ makes minimal difference.
Attempting to convert fully to OP9 today and installed viperFX mod form magisk but when I attempt to perform the initial launch to download and install the driver, the phone just reboots without actually getting the driver installed. Im not sure if its a hardware compatibility issue or the fact the OP9 root isnt as full and fleshed out like the one on my OP6. (something about DM verify and/or selinux enforcement? idk, I am pretty lame at the deep understanding of android 11s workings)
I know there are a few other magisk mod for audio listed and more that i could possibly find that arent and add myself via zip installation but even if one ends up working, I will still be aiming for VIperFX as my preferred solution.
If anyone has a solution, plz reply (or whatever possible replacement you've chosen)
PS. I swore the buds z touch controls were suppose to be customizable. anyone else unable to set custom controls for them?
In magisk, install "audio modification library". That should fix the driver issue.
To customize the touch controls, go in Settings, bluetooth and device connections, bluetooth, settings cog next to the buds, headphones. Now you can customize them. Not a lot of options though.
You might need to install the oneplus buds app first.
NotTheGiant said:
In magisk, install "audio modification library". That should fix the driver issue.
To customize the touch controls, go in Settings, bluetooth and device connections, bluetooth, settings cog next to the buds, headphones. Now you can customize them. Not a lot of options though.
You might need to install the oneplus buds app first.
Click to expand...
Click to collapse
i tried that and its the same results. No driver found, it installs, force reboots and loops from there. thank you though.
applyscience said:
i tried that and its the same results. No driver found, it installs, force reboots and loops from there. thank you though.
Click to expand...
Click to collapse
Same issue. Tried ACP as well, just gave up on it and using the inferior built-in Atmos
No, but I did install James DSP and it's working just fine.
@applyscience
After alot of trail and error I finally got ViperFX working on my OP9 !
You must install magisk-permissive-script_v1.2 and audio modification library modules in Magisk and of course the ViperFX
Glad you got it working! I wonder why I didn't need to do that
Hopefully it works for everyone else.
Just use JamesDSP. Same functionality as Viper, and works 100% of the time.
Jg1234 said:
@applyscience
After alot of trail and error I finally got ViperFX working on my OP9 !
You must install magisk-permissive-script_v1.2 and audio modification library modules in Magisk and of course the ViperFX
Click to expand...
Click to collapse
Can you tell me how you got it working in more detail? Because this isn't working for me
Okay it randomly worked for me after installing the BusyBox magisk module, then the Audio compatibility module, then the Audio modification module and then viper. After that the driver installed but did not work. After setting the selinux mode to permissive and switching to legacy mode in viper it worked flawlessly.
Im trying for several hours now, i have tried everthing i found including this Thread
(https://forum.xda-developers.com/t/app-fix-100-working-viper4android-for-android-11-devices.4213647/)
Nothing worked for me anyone any idea, i have allready updatet to the latest OxygenOs (11.2.4.4.LE25BA) Maybe thats why it doesnt work?
Domi04151309 said:
Okay it randomly worked for me after installing the BusyBox magisk module, then the Audio compatibility module, then the Audio modification module and then viper. After that the driver installed but did not work. After setting the selinux mode to permissive and switching to legacy mode in viper it worked flawlessly.
Click to expand...
Click to collapse
Did you reboot between the steps? have you installed any audio changing application before?
I'm using james dsp. It does the same and works without problems
noname122414 said:
I'm using james dsp. It does the same and works without problems
Click to expand...
Click to collapse
Can you link to said James dsp? Now I'm curious as to what this is. And if it works as well
Just search inside of magisk it's a standard module and works flawlessly for op9
noname122414 said:
Just search inside of magisk it's a standard module and works flawlessly for op9
Click to expand...
Click to collapse
Does it not need root rights.?But I'm using through by streaming now on way home from work. Very nice
Of course it needs root, magisk without root is kind of pointless.
noname122414 said:
Of course it needs root, magisk without root is kind of pointless.
Click to expand...
Click to collapse
But mine isn't asking for root rights is what I'm saying.
It is a module. Module always have root when it's functional then everything is alright
noname122414 said:
I'm using james dsp. It does the same and works without problems
Click to expand...
Click to collapse
Do you use any presets? If not, are you able to use those?