yashsingh1/xdaforums huggingface dataset:
[Magisk] bitye:
Any OS any Kernel any Vendor with and without Lib fix I get distortion on speakers immediately after give permission for Viper. Installed as system app 2.5.0.5 material on Poco with Magisk module.

Can anyone help please? The sound is super awesome from headphones but distortion make phone unusable.

If anyone can assist please drop a PM or a reply. Now latest vendor 9.3.14 DFE Magisk 18.1 on Latest LOS. All I miss is Viper
[Magisk] iceman0826:
Whick is superior when it comes to SQ the old or the new version?
[Magisk] MArtyChubbs:
I used 2.6.0.6 FX Forked to install driver then updated to 2.7 FX Forked on my p3xl.

Does this module work on p3xl? Forked has been the one that worked last time I checked.
[Magisk] Quinny899:
For anyone trying this on Android Q now Magisk Canary supports it on the P1/P2, you need to set SELinux to permissive for it to work. This is easily done via the terminal:

su
setenforce 0

Note that this doesn't survive a reboot so you'll need to do it every time or install a module to do it for you.
[Magisk] joedajoester:
How did you get it to work? I installed the viper from magisk and when I reboot and set selinux to permissive, it still prompts to install the drivers. I am on the latest magisk
[Magisk] Quinny899:
Didn't do anything beyond that. Make sure you definitely set SELinux to permissive (using "getenforce", which should return 0), and try restarting and running setenforce immediately after boot, see if that makes any difference.
[Magisk] Papaya45:
damn it ..

during installation v4fx using magisk i pushed the volume buttons to fast and installaltion restarted my s5

know i'm stuck in openrecoveryscript loop cause my device is trying to start in recovery and installing an script without success and device restarts

can someone help me out?
[Magisk] Wolfcity:
If it's the v4a magisk module you can just reflash it, the unity installer will uninstall it completely then.
[Magisk] ahmedyar91:
Hi everyone

I am using this module quite some time.

After the update i have to restart the phone to have viper working. After some time the processing status changes to no..
[Magisk] Dreamer(3MF):
Download

SELinuxModeInverter4Magisk

To Invert The Default Android SELinux Mode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive]) From This Thread https://xdaforums.com/apps/magisk/selinux-mode-inverter-t3775271 Then Flash It & Reboot.
[Magisk] Paschfire:
May I also suggest, with the use of init.d support you can set SeLinux Enforcing or Permissive via script.

Navigate into;

/system/etc/init.d

Creating a file named selinux0 with 755 permissions

(-rwxr-xr-x)

Contents of the file are as follows for Permissive SELinux state:

#!/system/bin/sh

setenforce 0

The init.d injector magisk module can also be used if init.d support isn't initially available on your device.
[Magisk] ahmtdlbdk:
İ installed this module but i have a problem. System app start perfectly but no sound difference when i change the settings. İ checked driver status. Everything looking ok. How can i fix it? (Lineage Os 16 - pie)
[Magisk] Lughnasadh:
Try turning off Master Power>Exit through 3 dot menu>Open V4A again>Turn Master Power On
[Magisk] ahmtdlbdk:
İ tried it so many times but still same.
[Magisk] Lughnasadh:
If you have anything like AudioFX or MusicFX, disable those as well.
[Magisk] vulturext:
My convolver is not working in latest update. Saying the kernel is empty. It used to work. Where can i get the needed files?
[Magisk] ahmtdlbdk:
Thanks man. İ uninstall audio fx and problem solved :)
[Magisk] givarius.kimza:
In order to user viper4android driver failed

Hi dude, i have problem with miui 10 9.3.21 beta pie mi6x. After flashing viper4android didn't working well. "in order to use viper4android you need to install/update the v4a driver" i have to reinstall the viper but can't working. Have any solution?

In oreo it working well. And after update to pie, viper didn't working,
[Magisk] cd993:
I'm on miui too (Mi 9) on the same 9.3.21 and I found a way to get it working on mine.

See here:

https://xdaforums.com/Mi-9/how-to/guide-how-viper4android-rooted-xiaomi-t3913030
[Magisk] givarius.kimza:
Nice, thanks dude, you're awsome
[Magisk] scrpsy:
Hi ViPER! Can I know where is headphones of SENFER in digital correction's menu? Cause I didn't find
[Magisk] badtlc:
This module was working for me and now has quit sometime in the last week. Nothing seems to work. Tried uninstalling and reinstalling and using different install methods. Any suggestions how to troubleshoot this? Thanks.

EDIT: I think it was google play store that was causing me issues. When I was reinstalling V4A, I never got the "harmful app detected" warning. Sometime between flashing an update to my ROM and reinstalling V4A again, something changed with google play. This time it detected the harmful up, I told it to ignore and keep and now V4A module (materialized) seems to be working fine again.
[Magisk] Zackptg5:
Updated v4a to v4.0! Changelog:

* Fix boot script once and for all

* Don't prompt for lib workaround if device that needs it

* Get rid of aroma option

* Update to Unity v4.0
[Magisk] DarkCod3r:
Any solution for this.? Keep getting driver install on 4.0 version (did normal install and lib workaround one , both having same issue). Previous version was working fine with lib workaround enabled. Using miui latest pie beta.
[Magisk] Zackptg5:
Can you post your v4a module folder and install log?
[Magisk] Erpe7:
Cheers for the update !

Not installed yet, I'll report if anything goes wrong.

Regards,

Erpe7
[Magisk] yerebakan:
I get boot issue. Every time phone rebooted, app opens itself.
[Magisk] Wolfcity:
Known issue. Should be fixed, until then the only solutions are rolling back to an older build or live with the start of the app.
[Magisk] bohemist:
Update installed all good ?
[Magisk] afcaajax:
No problem

Greetings from NL
[Magisk] kresnadetea:
my dolby has stopped working :(

but v4a it's fine enough

what kind of version of dolby should i install?

Edit: succeed, i'm using dax_a7000classic
[Magisk] mrmcshagbag:
That worked thank you! Just haven't used a root browser since before we went systemless because when it became a thing at first it broke safety net. I appreciate your help!
[Magisk] 6hexanexz:
But Wich one after I tried all but didn't work . Only working disable​ SELinux manually but now I use magisk 12 and old module all working fine . Don't need disable SELinux to work VIPER 4
[Magisk] docluv01:
Guys.... Please forgive me

But after you flash the script.... Does it also put the Viper app? Or does that have to be installed separate. If so... Which one?

Thanks
[Magisk] earlycray:
how does this module differ from the default viper4android in the magisk manager download list (by topjohnwu) ?
[Magisk] Didgeridoohan:
The module from this thread installs the V4A app as well.

This module uses an audio framework (AudModLib) with which you can use several different Magisk audio mods (which in turn must use AudModLib as well) without them clashing.
[Magisk] earlycray:
If I was only interested in v4a then there wouldn't be any advantage to using this module (versus the 'default' one) correct ? Cheers
[Magisk] Didgeridoohan:
Probably not... Just note that neither the module in the repo (Magisk Manager), nor the one in this thread has been updated for Magisk v13.3 and may not work without manual modifications and workarounds.

Also, the one in the repo does not come with the V4A app, you'll have to install that manually (link in the readme for the module).
[Magisk] ForgottenDude:
The Viper in the repo is working perfectly for me on 13.3 without any workarounds. SELinux is enforcing as well.
[Magisk] Plonkyplonk:
Although the app wants the driver to be installed / updated on my N5X (OmniROM) despite I installed the one available in the repository from the manager itself and rebooted.

Device: Nexus 5X

ROM: omni-7.1.2-20170716-bullhead-WEEKLY

Kernel: ElementalX-N5X-4.10-express
[Magisk] Didgeridoohan:
Interesting. I tested it on my Nexus 6 after v13 went to beta and tested again just now (Magisk v13.3). It does not work out of the box (for me)... You sure you're not using one of the workaround scripts that's been floating around (in post-fs-data.d)?
[Magisk] ForgottenDude:
Nope, no workarounds.

I don't know if it changes anything, but it was not a clean flash. I was already on Magisk 13.2 with Viper4Android working (no workarounds. Just usual flash through TWRP and installing app). Then I updated Magisk Manager and Magisk 13.3 through the Manager itself. And it's been working.

Redmi Note 4

AEX 7.1.2
[Magisk] docluv01:
Hmm... If the app is not installing then I geuss that's problem one...

Any suggestions?
[Magisk] Didgeridoohan:
Are you sure you're using the module from this thread and not the one in the Downloads section of the Magisk Manager? The one in the repo does not install any app. You'll find a link in the readme of that module (click the module in the Downloads list).
[Magisk] whalesplaho:
it never worked for me without workaround except on MM dat i used last........ even with workaround, it doesnt process sound on speaker except bluetooth and headset.
[Magisk] jianwen03:
it works as well in my rn3 (which i kinda broke) on stock los with los su (with certain custom kernel, most kernels must be set in permissive for this to work).
[Magisk] ngtung84:
This modules don't work with magisk 13.3 anymore
[Magisk] whalesplaho:
Just read previous posts and yhu ll get a solution.....
[Magisk] ngtung84:
disable SELinux in viper -> it works
[Magisk] Cablespider:
No problems to report with 4.0 on my OP6. :good:
[Magisk] BadToThePhone:
How does 4.0 differ from 2.7? Thanks
[Magisk] Wolfcity:
Read this a few posts above?
[Magisk] DarkCod3r:
Can you tell me where v4a module folder .? Cant seem to find it. (Rest of the logs are attached)

.

.

(Logs)https://filebin.net/kr1p3l9o2rr95p5z
[Magisk] putti71:
Since latest magisk module version, viper always opens automatically after every reboot. Why and must it be like that?

Device S8 pie

---------- Post added at 07:16 AM ---------- Previous post was at 06:55 AM ----------

How could I roll back to the version without the reboot problem?
[Magisk] Wolfcity:
Reflash the viper build that is on your device, that will uninstall it.

Install the one you want i.e viper 2.3.
[Magisk] mindlery:
App running very well. Had just tried it after not using for some time. Is it supposed to be running (opened to input selection page) right there, instead of home usual home screen at boot?
[Magisk] Wolfcity:
Read the posts above yours.
[Magisk] dragos281993:
That is the problem. I searched everywhere and nowhere are the older versions. V4 renders my device useless when I first reboot the phone after installing the module.
[Magisk] Wolfcity:
The oldest build I have in my clouds is ViPER4Android_FX-v2.3.zip.

Here you go: https://yadi.sk/d/HeR7WxGYlO_PcQ
[Magisk] dragos281993:
Thanks! It work well, as expected.

I'm gonna still ask though, while I'm at it, if anyone can link me to v3.3, if it's no trouble. I'd really appreciate it.
[Magisk] Txatxiquesi:
Updated with no problems, but in the first boot after install the app pop out, on the next boots no more.
[Magisk] Wolfcity:
Here is v.3.3 but this one starts at boot too, at least for me.

https://yadi.sk/d/94Tqp4AV6P-KJA
[Magisk] DorianX:
[MENTION=5237901]Wolfcity[/MENTION]

Do you have v3.4.2 on your cloud?

Don't know why OP doesn't leave old versions available to download, sometimes new version doesn't mean better

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Magisk] Wolfcity:
Here's v.3.4.2:

https://yadi.sk/d/x7z0akLbUEOsbg

I don't know either why old builds aren't available but if the dev don't want mirrors from other builds here I will obviously delete them.
[Magisk] dragos281993:
Thanks! I think I'll stay on 2.3, probably forever. This version even starts automatically after a reboot and I don't need to actually launch the app myself to trigger the processing.

Thanks again! I really appreciate it.
[Magisk] Tchania:
On note 9 version 4.0 doesn't work as 3.4.2.

ViPER4Android opens on boot and I get prompted for drivers install. Also during module installation it asks me whether I want to use lib workaround (note 9 needs it).

So I'm back to 3.4.2
[Magisk] Wolfcity:
The opening of the app after a boot is an issue since v.3.3, the method of the lib workaround has been changed several times but was always available. If your device needs it just tap for Yes when prompted. Maybe your drivers get installed correctly then, that's what the workaround is made for at last.
[Magisk] DorianX:
Thank you that version was working fine on my device, I'll keep old versions saved

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Magisk] papoy1019:
UI, drivers are the same. As I know.
[Magisk] jemail:
I can confirm ViPER4Android FX v4.0 (the version that fixes on boot problems once and for all ;)) starts full screen on boot for me.

It's no big thing, a very minor inconvenience. Apart from launching full screen on boot everything else works very well.
[Magisk] bitye:
I face Viper main screen everytime I restart my MIUI, how to avoid? Is this bug? I think same as previous comment
[Magisk] DorianX:
Flash an old version [emoji28]

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Magisk] methuntt:
Dev, New version 4.0 not working..

Prompting to isntall driver everytime i open.. I'm using Pixel 2 pie -Magisk v19

Is it magisk problem or v4a.

Thanks
[Magisk] whalesplaho:
I noticed after flashing magisk 19, after updating v4a to v4, it works after reboot but after subsequent reboots, it doesnt process anymore..
[Magisk] PapaZero0:
I do a reboot daily and no problem here with Viper...
[Magisk] Lazaroth:
Can't get the latest version to work on op6, "abnormal" error. Reverting to the previous version.
[Magisk] Cablespider:
Are you running OOS? V4 works without issue on a few custom ROMs I've tested.
[Magisk] Lazaroth:
I am, havn't debugged too much to be honest, but did try to reinstall 3 times with different settings and trying different things. Nothing changed, while the previous version just works.

Let me know if anyone wants me to tell you anything specific or try something.
[Magisk] PapaZero0:
Update: do a reboot and its not processing. Also, another magisk module is not working too. So probably the problem is 19.0
[Magisk] super_nooby:
for me with new magisk and v4a everything is working. the only thing i had to do is using the lib workaround. all versions before doesn't worked. i am using an galaxy s9 with soldiers-rom
[Magisk] tilasto:
After update and reboot i get system ui crashing. I flash old version back :D
[Magisk] สุรินทร์ พลโธา:
+1
[Magisk] Sulltan Mehmood:
Asking to reinstall drivers???
[Magisk] aoaleman:
Probably need to uninstall, reboot, then reinstall. Worked for me.
[Magisk] whalesplaho:
Dats wah i did, one cant keep uninstalling/rebooting/reinstalling everything.
[Magisk] Redhawk2000:
That happened to me once a few versions ago. I simply did a reboot and it worked normal. Maybe you did already try that, but if not, try it if it happens again with an update.
[Magisk] whalesplaho:
I ll try with dat & see.....:good::highfive:
[Magisk] kzhkr:
anyone having gps issue after update?
[Magisk] Indranil0:
Google play protect saying it's a harmfull app, I don't care. But on previous version play protect didn't showed this. Installed version 2.5.0.5.
[Magisk] bafforosso:
Please use search function as it would've told you that this issue (false positive) has been known since December at least and discussed several times already in this thread.

If this notification really bothers you turn off Play Protect or install original (non-material) version of V4A.
[Magisk] Fif_:
It's not a false positive since you can turn off SELinux with the material version (you can't with the classic one). Turning off SELinux is a big no-no for G.

What's annoying is that Play Protect will still complain even if you told it to only scan Play apps.

Can't someone come up with a material app without that switch? That would cure the issue.
[Magisk] Zackptg5:
Actually, you can with the classic one. It a feature in 2.5 apk

play protect is a useless feature anyways. It's only necessary for idiots who install malware laiden apps
[Magisk] Redhawk2000:
Any idea what this suggests? Contacting China?
[Magisk] Zackptg5:
Updated v4a to v4.1! Added mtk sepolicy and made the app open/close workaround an optional volume key thing so quick complaining about it
[Magisk] k3wlar:
Can l use Viper4Android FX or XHiFI on Huawei mediapad m5 8.4 ? Kirin960
[Magisk] D-m-x:
Could you explain with a few words what the app open/close workaround even does and who needs it. Or find out if one needs it? I have been following the topic sporadically but didn't see anyone mention why this is even in the module? What is different for the One Plus for example?
[Magisk] Indranil0:
By which app you tested? Just curious:confused:
[Magisk] Txatxiquesi:
Thanks for the update, apparently the app pop up on boot is fixed.
[Magisk] Redhawk2000:
App Snitch
[Magisk] Quinny899:
https://whatismyipaddress.com/ip/121.40.183.16

Shows as Alibaba, might be for analytics as there's no ads?
[Magisk] Zackptg5:
It opens v4a, kills it, and kills audioserver. It was needed for some OnePlus devices. Some other users reported it helped too but I forget which devices those were. It was found incidentally but I'm not sure exactly why it works, probably some oem audio crap or something
[Magisk] BHUSHAN7988:
This OnePlus issue is was still existing till OP6T (have both OP6 and OP6T had problems) thanks to this update it is fixed.
[Magisk] D-m-x:
Thanks, that makes sense. And thanks for keeping this updated. This module has been the only easy and effective way to use Viper. Since it hasn't been updated forever this has always been a pain in the ass otherwise.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] Supermaistro13:
Hi there. V4A was working fine on the last update, but once I installed the new version, each time I open Viper, it asks me to install the driver, and when I look at the driver status, it says that it isn't installed,. And if I allow it to install, when my phone reboots, viper asks the same thing. Any ideas of what's going on?

Moto G5 plus

Pixel Experience pie version
[Magisk] D-m-x:
Delete the Module in Magisk Manager, reboot, reinstall module, reboot. This is actually the standard procedure I need to do for the Pixel 2 XL. Just updating the Module gives this exact same error but if I remove it beforehand it works. Other devices I have don't need this. No big deal. Try it, if it's not working refer to the FAQ in the 1st post there may be other tips and tricks.
[Magisk] JacquesMerde:
Doesn't work unfortunately.
[Magisk] yam19:
Viper4AndroidFX v4.1 Processing: No

Hi

Viper4AndroidFX v4.1 installed from Magisk correctly, but not processing in youtube, for example.

Driver Status: 2.5.0.4

NEON Enabled: Yes

Enabled: Yes

Status: Normal

Audio Format: Supported

Processing: No

Sampling Rate: 48000

In local media player processing correctly.

RR 5.8.5 for Nubia Z7 Max. Please help.

p.s. JamesDSPManager working similarly.
[Magisk] manpildo:
I uninstalled, rebooted, reinstalled but it hasn't helped. This driver issue has started occurring only on the 4.1 update.

Mi A1

Stock 8.1

Magisk 18.1

Luckily I still have the 4.0 zip. Will try later if downgrading helps.
[Magisk] Zackptg5:
V4.1 is the same as 4.0 except I made the open/close work around optional
[Magisk] Supermaistro13:
Yeah, I tried that, but no luck unfortunately. I think I'll install the 4.0 update for now. Thanks, anyway.
[Magisk] manpildo:
Well, downgrading to 4.0 didn't help either, worked flawlessly before. Trying to reinstall AML, but for some reason it's not uninstalling... When I flash it, it says uninstalling. Then under modules says it will be updated at next reboot, after reboot AML is still there as if nothing happened. Rinse and repeat. I dunno, will have to dig deeper.

EDIT: Okay, AML had to be uninstalled with the uninstall button under modules, not by reflashing the zip. After reinstalling AML it's working again, but I'll probably skip v4.1 for now.
[Magisk] dvishalkhatri:
Getting driver installation when opening up the app. Can I know what should I do ?
[Magisk] bschmidy10:
Does this work on stock rooted Essential phone?
[Magisk] manpildo:
Try reinstalling AML if you have it.
[Magisk] dvishalkhatri:
I don't use any other sound mods so no need of AML
[Magisk] manpildo:
Try uninstalling V4A, reboot, install again, reboot.
[Magisk] badtlc:
Viper4Android magisk module has been acting up for me. It stops working. The issue essentially goes like this:

1) V4A stops working.

2) Go into V4A settings, turn off master power

3) reboot

4) start music app

5) go to V4A settings and turn on master power (it works!)

6) Once the music app closes, V4A stops working until I turn off master power and reboot again.

Is this fixable?

Phone is Moto g5 plus with rooted stock Oreo 8.1 rom.
[Magisk] JacquesMerde:
Seems to be working now I've updated Los16 to the latest build.
[Magisk] dvishalkhatri:
Yeah tried that too but still it is same
[Magisk] leho6694:
Can you share/upload v4.0 somewhere? I can't find this anywhere.
[Magisk] k3wlar:
Ochh. ..min 8.0 oreo .thx
[Magisk] warrencoakley:
don't get it. All of these updates to AML, Audio Patch and Viper seems to break other things. Once one thing is addressed another is broken. Spent over an hour trying different methods etc and all still the same. Spotify broken yet again. Plays for 2 second then cuts out. Grrrr!

Can someone please tell me what version of the following they are using and confirm Spotify is working with Viper etc? With all the updates I don't know if it's the audio patcher,AML or Viper that's the issue. What a pain.
[Magisk] Lughnasadh:
Spotify works fine for me.

Nexus 6P

Pie

AICP

Magisk 18.1

JamesDSP 2.0

ACP 1.7.3

V4A 4.1

AML 2.1
[Magisk] bohemist:
I am using the latest version of Viper4Android without AML but with Audio Compatibility Patch.

It works with Spotify.

My phone is OnePlus 6 on stock OOS with blu_spark kernel and Renovate Ice.

So far, no issues encountered. I did not install AML as I don't have any other audio mod installed but V4A.

Usually, when I have problems updating in the past, I remove all possible modules causing the problem then reinstall them one at a time. In my experience, AML usually causes problem, but since I don't use any other audio mod anymore alongside V4A, I skip it.
[Magisk] warrencoakley:
I have as I have Dolby Digital Plus. They all worked flawlessly until they all updated so something has to be broken somewhere
[Magisk] Zackptg5:
I recommend starting with clean magisk img/directory. Some devices had issues with the img migration in magisk 19 update so just delete any magisk imgs that still exist in data/adb and delete everything in data/adb/modules (and modules_update) as well as any boot scripts in the .d folders
[Magisk] dvishalkhatri:
[MENTION=6037748]Zackptg5[/MENTION] any help with this ?
[Magisk] Zackptg5:
Unusual and reinstall all audio mods (start with just v4a). Try different options too
[Magisk] dvishalkhatri:
i just use viper4android FX nothing else ... i am on magisk 18.1 shall update to magisk 19 ?
[Magisk] vrolok:
I have the exact same problem. It keeps asking to install drivers. It is so since I updated my poco f1 to last global stable.
[Magisk] makash720:
The latest apk is 2.7 but why magisk module uses outdated apk?
[Magisk] DanGLES3:
It's because the 2.7 apk is from a different developer,it's not an official app
[Magisk] warrencoakley:
So are recommending delete all my module's and start again? Or just delete the parts you recommend above?
[Magisk] makash720:
Although I prefer the default one as it has an exit option which doesn't run out battery.
[Magisk] LeoHeinzmann:
Both 4.0 and 4.1 keep asking to install driver everytime, already tried uninstalling and reinstalling instead updating directly and it didn't work either. Luckily I had the 3.4.2 zip here and it's working flawlessly. I'm using Zuk z2 pro with aosp extended 6.4 (pie)
[Magisk] Zackptg5:
Follow the troubleshooting guide, try the workarounds too