I saw someone made a post on one way to remove the distortion from V4A, but that method breaks Bluetooth audio. This is how you fix it without breaking Bluetooth:
1. Reboot to recovery, mount Vendor
2. go to 'Advanced' -> 'File manager'
3. Go to "/Vendor/lib64/audiofx/" and rename/remove libvolumelistener.so
4. Go to "/Vendor/lib/audiofx/" and rename/remove libvolumelistener.so
5. Reboot to system, install V4A
And that's it
Edit:
You can also just use one of the older versions of V4A without needing a fix of any kind.
Couldn't you get the same result on a file manager with root permission without having to go through TWRP and reboot?
stewykam said:
Couldn't you get the same result on a file manager with root permission without having to go through TWRP and reboot?
Click to expand...
Click to collapse
I believe at least one of those is read only while the system is on. I remember trying that before and it wouldn't let me.
TiklMiPickles said:
I believe at least one of those is read only while the system is on. I remember trying that before and it wouldn't let me.
Click to expand...
Click to collapse
Ahh... Just wondering. Thanks for the info though ?
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
TiklMiPickles said:
I saw someone made a post on one way to remove the distortion from V4A, but that method breaks Bluetooth audio. This is how you fix it without breaking Bluetooth:
1. Reboot to recovery, mount System and Vendor
2. go to 'Advanced' -> 'File manager'
3. Go to "/System/lib64/audiofx/" and rename/remove volumelistener.so
4. Go to "/Vendor/lib/audiofx/" and rename/remove libvolumelistener.so
5. Reboot to system, install V4A
And that's it
Click to expand...
Click to collapse
Notification helper do this job systemless
However, I have a problem always with whatsapp voice notes crackling an stuttering sound if its mininized or force screen off
Dude, you are telling the same thing that I have posted (I'm sure you're talking about my post). You are asking users to manually edit volumelistener.so and I suggested users to flash the notification helper magisk module which does the exact same job automatically and most important, systemlessly. Is it really needed to create the same post with different heading and tagline? I'm sure you don't even know what I was talking about or didn't even try the module. Or else you would have realized you are not giving anyone any different solution. And if the method I told users breaks Bluetooth audio, then your method will do the exact same thing. Guess why. Because you are telling people to do the same thing, but manually. But I'm sure you didn't even bother to check the github of the particular magisk module I was talking about or didn't even try contacting the dev to see how exactly it works. Now the main question, what different solution did you give the users here?
---------- Post added at 08:53 PM ---------- Previous post was at 08:46 PM ----------
Dna10 said:
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
Click to expand...
Click to collapse
This is what happens when someone decides to make a post without having complete knowledge about what he is saying.
Dna10 said:
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
Click to expand...
Click to collapse
You have to mount those partitions in recovery. If you didn't manually mount them, a lot of files/folders won't show
Rowdyy Ronnie said:
Dude, you are telling the same thing that I have posted (I'm sure you're talking about my post). You are asking users to manually edit volumelistener.so and I suggested users to flash the notification helper magisk module which does the exact same job automatically and most important, systemlessly. Is it really needed to create the same post with different heading and tagline? I'm sure you don't even know what I was talking about or didn't even try the module. Or else you would have realized you are not giving anyone any different solution. And if the method I told users breaks Bluetooth audio, then your method will do the exact same thing. Guess why. Because you are telling people to do the same thing, but manually. But I'm sure you didn't even bother to check the github of the particular magisk module I was talking about or didn't even try contacting the dev to see how exactly it works. Now the main question, what different solution did you give the users here?
---------- Post added at 08:53 PM ---------- Previous post was at 08:46 PM ----------
This is what happens when someone decides to make a post without having complete knowledge about what he is saying.
Click to expand...
Click to collapse
No, you said to full on remove the audiofx folder rather than fix the specific files that cause the problem. The magisk also removes more files than necessary, which breaks Bluetooth audio.
It's funny you say I should know what I'm talking about when you are the one spreading false information. Before you go around throwing shade, you should have checked to see if I was right.
slimshouki said:
Notification helper do this job systemless
However, I have a problem always with whatsapp voice notes crackling an stuttering sound if its mininized or force screen off
Click to expand...
Click to collapse
The magisk module is definitely easier and let's you have the fix systemlessly, but I use Bluetooth audio all the time, and this is the only way I've found to have working notifications, Bluetooth and V4A.
Is the WhatsApp issue with the magisk module or fix I listed?
TiklMiPickles said:
The magisk module is definitely easier and let's you have the fix systemlessly, but I use Bluetooth audio all the time, and this is the only way I've found to have working notifications, Bluetooth and V4A.
Is the WhatsApp issue with the magisk module or fix I listed?
Click to expand...
Click to collapse
Both make same behaviour
Btw, Magisk module do not break BT audio
slimshouki said:
Both make same behaviour
Btw, Magisk module do not break BT audio
Click to expand...
Click to collapse
That's strange, I just double checked and it breaks it for me on Havoc-OS, it also did on Siberia and AEX when I used those. Maybe it has to do with the rom or vendor/firmware? I'm using Havoc and 8.12.20
TiklMiPickles said:
No, you said to full on remove the audiofx folder rather than fix the specific files that cause the problem. The magisk also removes more files than necessary, which breaks Bluetooth audio.
It's funny you say I should know what I'm talking about when you are the one spreading false information. Before you go around throwing shade, you should have checked to see if I was right.
Click to expand...
Click to collapse
Its funny how you accuse me of spreading false information without even digging into the module or atleast check the github. This is what happens when a randon user decides to show up once in a blue moon. Here is the github link of the module: https://github.com/Magisk-Modules-Repo/nhr
If you still don't understand how it works and what it does, then I feel sad for your noobness. And can you please list out what the module removes more than volumelistener.so? Don't just go on make claims, prove it first. And also, I have attached a screenshot of my post. Please show me where did I suggest people to remove audiofx folder (which is again wrong. There is no audiofx folder on vendor partition. Its called soundfx). And next time, if you decides to challenge someone who is more active on XDA than you, first upgrade your profile. I didn't get those thanks count just like that. It's the appreciation that I got from others upon helping them. So don't teach me what I am suggesting other users. First raise your profile standard.
slimshouki said:
Both make same behaviour
Btw, Magisk module do not break BT audio
Click to expand...
Click to collapse
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Rowdyy Ronnie said:
Yeah because that magisk module does nothing but removes volumelistener.so systemlessly when you choose volume down. And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make it work with Viper.
Click to expand...
Click to collapse
Do you have any idea about whatsapp voice notes issue?
slimshouki said:
Do you have any idea about whatsapp voice notes issue?
Click to expand...
Click to collapse
I have sent a message to Zack regarding the issue. Let see if he can address the issue. By the way, can you do one test. Remove the module and flash it again. This time when asked to choose between volume up and down, select up to remove notification helper and see if it fixes your problem.
Rowdyy Ronnie said:
I have sent a message to Zack regarding the issue. Let see if he can address the issue. By the way, can you do one test. Remove the module and flash it again. This time when asked to choose between volume up and down, select up to remove notification helper and see if it fixes your problem.
Click to expand...
Click to collapse
I did that as well.and same issue
Rowdyy Ronnie said:
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Click to expand...
Click to collapse
After doing some testing, it seems to be rom specific. AEX and Havoc-OS, it breaks Bluetooth audio, but I tested on Resurrection Remix and Syberia and it doesn't.
Rowdyy Ronnie said:
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Click to expand...
Click to collapse
I've managed to track down the issue. It isn't the notification remover module that is causing the issue, it's the Audio Modification Library, which the notification remover tells you to install if you have V4A installed. I have found this to be the case with AEX, Havoc-OS and MSM Xtended. Removing the AML module fixes the issue.
Not work viper and Dolby...havoc rom
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
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)
Hi guys,
I have some problems with audio after installing viper (beta). I've already had viper for a week and all worked perfectly (also upgraded to 2.7 stable). Since today that I decided to uninstall momentaneously the driver and now, if I reinstall viper, I have a broken audio (idk how to explain) for some reason.
Do you guys have any idea?
I think it would be good to clean all audio files, or something like this, and reinstall viper.
Thx in advance.
EDIT: Forgot to mention that I'm on AEX.
I would try a dirty flash of your current rom
JetzNicht said:
I would try a dirty flash of your current rom
Click to expand...
Click to collapse
Still have the same problem.
EDIT: Tried also by restoring a system backup done when viper was working but nothing to do.
Party5999 said:
Still have the same problem.
EDIT: Tried also by restoring a system backup done when viper was working but nothing to do.
Click to expand...
Click to collapse
So if you uninstall the viper module you do have audio?
Browns said:
So if you uninstall the viper module you do have audio?
Click to expand...
Click to collapse
Yup
Party5999 said:
Yup
Click to expand...
Click to collapse
First delete your current viper from magisk and android apps. Now go to magisk manager downloads. Search for viper and install the 3.4.2 version with lib workaround (last option you have to choose). Reboot and search for notification helper remove by zackptg5. Install and reboot and you should be fine.
Browns said:
First delete your current viper from magisk and android apps. Now go to magisk manager downloads. Search for viper and install the 3.4.2 version with lib workaround (last option you have to choose). Reboot and search for notification helper remove by zackptg5. Install and reboot and you should be fine.
Click to expand...
Click to collapse
I'll try but I've always installed viper by using the app and not the magisk module because it wouldn't install the driver. I have to say that I've never tried to install it with lib workaround... I'll let you know how it goes.
Party5999 said:
I'll try but I've always installed viper by using the app and not the magisk module because it wouldn't install the driver. I have to say that I've never tried to install it with lib workaround... I'll let you know how it goes.
Click to expand...
Click to collapse
The lib workaround fixes the issue with the driver :good:
Notification helper remover fixes issue with crackling ringtones and notifications
Browns said:
The lib workaround fixes the issue with the driver :good:
Notification helper remover fixes issue with crackling ringtones and notifications
Click to expand...
Click to collapse
Which options I have to choose in notification helper remover?
Party5999 said:
Which options I have to choose in notification helper remover?
Click to expand...
Click to collapse
The most drastic option. I think remove it was...
Browns said:
The most drastic option. I think remove it was...
Click to expand...
Click to collapse
Remove notification_helper effect
Remove volume listener library
I think it is the first one cuz it says to use the second if the first doesn't work.
Party5999 said:
Remove notification_helper effect
Remove volume listener library
I think it is the first one cuz it says to use the second if the first doesn't work.
Click to expand...
Click to collapse
It's the "Remove volume listener library"
For "Remove notification_helper effect" you'll need the "Audio Modification Library" magisk mod, which messes everything up on our phone
It's working, thank you.
Do you know a way to get also dolby working with viper?
I got them work with ADL but it has a bug that sounds won't play on Bluetooth earbuds.
Sorry my English.
Party5999 said:
Do you know a way to get also dolby working with viper?
I got them work with ADL but it has a bug that sounds won't play on Bluetooth earbuds.
Sorry my English.
Click to expand...
Click to collapse
I personally don't care about Dolby. Try to flash this one and see if it works (if not you can always uninstall the mod):
https://forum.xda-developers.com/mi-mix/themes/app-dolby-digital-plus-unity-t3819989
Browns said:
I personally don't care about Dolby. Try to flash this one and see if it works (if not you can always uninstall the mod):
https://forum.xda-developers.com/mi-mix/themes/app-dolby-digital-plus-unity-t3819989
Click to expand...
Click to collapse
It doesn't work. I think the only method is by using AML.
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
You need to install drivers twice.
Mhm, sure.
Though, to be honest, this was among the things I tried before. No difference.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
Uninstall your current Viper and reboot. Sideload Viper 2.7.1.0 apk or use the Magisk module. Install the driver and reboot. Once back in Android, install the driver again. Should work. If not, go into V4A settings and put in compatibility mode.
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
To repeat my question from another thread, i have the same issue and 2.7 only works for me when the "attach audio effects" option is checked and that introduces quite significant audio lag when skipping tracks.
I also can't seem to get rid of the permanent notification without breaking vipers functionality.
Is there any fix for this? Or a way to properly install 2.5.0.5?
Luxor144 said:
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
Click to expand...
Click to collapse
Lol. Forgot to suggest 2.7.1 and then install drivers twice.
Still an issue in 10.3.4
}{Alienz}{ said:
Still an issue in 10.3.4
Click to expand...
Click to collapse
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
GeekMcLeod said:
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
Click to expand...
Click to collapse
Tried to find that one again, too.
I ended up installing the Audio modification library magisk module, rebooting, deactivating (not uninstalling) that module and then installing the current Viper 2.7.1.6 module.
May have rebooted after that before installing drivers and therefore rebooting again, can't remember though.
But it does work perfectly and the guide did go something like this.
Also possible that a Viper update fixed the issue.
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?