yashsingh1/xdaforums huggingface dataset:
[Magisk] Zackptg5:
Hmm, app looks weird. Can you try extracting the material v4a from the custom folder of the zip and replacing the one in the v4a directory (renaming the app to match the name of the current one)?
[Magisk] aDarkBox:
I replaced the one in the vendor/app folder inside of the v4a folder and had the same result. Manually installing it leads to it asking for the driver to be reinstalled every time I open it
[Magisk] Zackptg5:
This makes me think this is some kind of magisk mounting issue. Have you tried uninstall and reinstall magisk v16? Also, can you send your /vendor/etc/audio_effects.cfg file (not the /magisk/v4a one)? Can you send a magisk log too?
[Magisk] aDarkBox:
I will do all of this and check back later today/tomorrow. It may be a bit of a process reinstalling as there is no TWRP for the mate 10 yet. Thanks for the continued help with this, though!
[Magisk] trackloading:
Thanks for looking into this. Here are the conf and the log...
[Magisk] Zackptg5:
As I suspected. Magisk didn't mount anything. Not sure what I can do about that I on my end as that's not a module problem. Can you send me your magisk img?
[Magisk] trackloading:
TWRP is almost there... :)

https://xdaforums.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399

---------- Post added at 12:39 AM ---------- Previous post was at 12:26 AM ----------

Unlike other devices, Huawei Treble devices uses ramdisk.img instead of boot.img for Magisk. I can't upload it since the file is a bit to big??
[Magisk] Zackptg5:
I guess the v4a folder itself will do. Do other magisk modules work?
[Magisk] trackloading:
Here is a link...

https://drive.google.com/file/d/1KY84EXegyNFFauu4jaA7QamYzCj0ywk5/view?usp=sharing

EDIT: This is just a clean patched ramdisk.img
[Magisk] aDarkBox:
other magisks modules do work for me, like the unified hosts adblocker that I have installed.
[Magisk] trackloading:
Yes other mods work. But not any Unity mods. Which folder do you mean?
[Magisk] Zackptg5:
/sbin/.core/img/viper4android (or whatever the folder is called)

---------- Post added at 19:07 ---------- Previous post was at 18:58 ----------

Can you both try to install v4a again, choose "save logs" in magisk manager, and attach them? Then try this test zip and do the same: https://www.androidfilehost.com/?fid=673956719939821315

Thanks!
[Magisk] AlexxAnders:
I just installed your "mate test zip" via Magisk. Icon still doesn't show up.

Magisk install log is attached. Thank you so much for trying to help!
[Magisk] AlexxAnders:
And the normal V4A1. 4 installation log right here...
[Magisk] aDarkBox:
Here you are. 171825 is the normal install, 172303 is the magisk log after rebooting, 172816 is the test install and 173442 is the magical log for that
[Magisk] Zackptg5:
Okay, that test was an epic fail so you'll want to just delete the v4a folder. Ya, I'm not sure what the issue is at the moment, sorry
[Magisk] aDarkBox:
Thanks for trying. I'll keep installing and testing as updates come out, and I'll uninstall/reinstall magisk v16 here in a while as well.
[Magisk] Lownita:
Does uninstalling the magisk module delete the mod completely from the system? I'm sick of restoring backups every time I'm trying something out. Still used to that from arise. :)
[Magisk] Didgeridoohan:
Yup. Just uninstall and you'll be back to normal.
[Magisk] madscribblerz:
In order to get this working on my Pixel 2 XL I had to manually copy two files into the magisk directory -

/magisk/ViPER4AndroidFX/system/vendor/lib/libstdc++.so

/magisk/ViPER4AndroidFX/system/vendor/lib/soundfx/libv4a_fx_ics.so

This expected?
[Magisk] Kids in Love:
Can anyone help me to set up viper4android on my Samsung Galaxy core 2 (rooted).. it seems that it doesn't change at all..
[Magisk] trackloading:
[/COLOR]

OK, thanks for trying... :)
[Magisk] Zackptg5:
The installer should already do that
[Magisk] madscribblerz:
Any idea why it didn't?
[Magisk] Sneheth:
My V4A is not starting unless I open the app and switch the master power off and then on. I'm on AEX (7.1.2 ) and installed V4A 2.5 0.5. Any solution..??
[Magisk] Thyrador:
I'll give it a try, thanks.

EDIT: great, it seem to work as I want it too. Now I can use my banking app while listening to music. Great :)

My Note 4 tapablahed this!
[Magisk] Sytis:
Has anyone owning an OnePlus 3 been able to successfully use this module with the unofficial Magisk v13? The module isn't throwing any errors but the driver won't install regardless which method I try. Works perfectly with v12, so it's more out of curiosity than demanding support. :confused:
[Magisk] Didgeridoohan:
There seems to be Magisk Mounting updates in the next version (v13) that doesn't quite work right with the current module template (or something similar). You'll most likely have to wait until there's an official update... Or, knowing XDA, if someone hacks around it in an unofficial way. :silly:
[Magisk] Vivasanti:
Can't see the viper app after installing the Magisk module? This is on my OnePlus 3T.

Any idea team?
[Magisk] Didgeridoohan:
In that case I'm going to guess you're not using the module in this thread. This is not the V4A module found in the Magisk Manager...

Go to Downloads in the Manager and click the module (not the arrow). You'll find a link to the apk there.
[Magisk] Vivasanti:
Thank you!

Have the app now but can get it to start processing - grrr
[Magisk] Didgeridoohan:
If you need help with that, go to the general Magisk support thread.

Or, uninstall that module and use the one in this thread instead. I've had a very good experience with it when other V4A modules have failed...
[Magisk] otonieru:
Hi [MENTION=5357345]ahrion[/MENTION]

When i install any of your dolby or viper module, my magiskhide will stop working,

Any idea why ?

Magiskhide will start work again once i disable your module.

Audiomodlib n deep buffer remover is fine, it just the dolby/viper that causing this
[Magisk] Didgeridoohan:
That's interesting? No issues with this V4A module and Magisk Hide on either of my devices.

Can you see the folders unmounting properly in the log?
[Magisk] WarSpaz:
When trying to install this through magisk it gives me no errors.

However, after rebooting my phone (mi5 running lineage os) i cant start viper, it just force closes the second i try to open it.

Got latest official magisk installed.
[Magisk] otonieru:
Thats exactly the problem,

After post fs script of dolby module executed, magisk process is stopping,

No unmounting process is executed after that.

And i have trace down the issue to only this module. Other module works fine,

Viper from topjohnwu also didnt create this issue, but those viper doesnt work to mod the EQ on S8

Ahrion Dolby work well but kill magiskhide,

This is weird indeed

I tried starting magiskhide daemon manually btw, and its the same. It wont unmount
[Magisk] Zackptg5:
Which Dolby are you using? Did you try one of the more compatible ones?
[Magisk] otonieru:
Tried all honestly, and all act the same :(

Only Viper from topjohnwu that didnt causing magiskhide to stop working
[Magisk] otonieru:
Found the culprit,

Apparently i cant use this module together with app systemizer, or any module that adding app to system priv app,

When used together, magiskhide wont be able to unmount anything, not sure why

So i have to decide whether to uninstall sound module or app systemizer module,

I choose the second one
[Magisk] grandpajiver:
Just set viperfx to 0 in /magisk/AppSystemizer/extras/appslist.conf

From: "com.audlabs.viperfx,VIPER4Android,priv-app,1"

To: "com.audlabs.viperfx,VIPER4Android,priv-app,0"

I'd recommend:

1. Removing this mod with the uninstaller script in recovery

2. Uninstall viperfx (if it's on your system}

A. If it's still a system app after a reboot, delete it from /magisk/AppSystemizer/System/priv-app/viperfx/ then reboot

3. Once it's definitely gone, install audio modification library, reboot.

4. Install the viper mod from this thread. Reboot

5. Install Dolby Atmos Lee pro3 ;). Reboot

6. Rock out with your... NM.

This is the best working implementation of viper+Dolby. I'm bummed that surround doesn't work with BT but oh well.
[Magisk] otonieru:
Hi Mate, thanks for the recommendation

although, in my case, thats not the issue, since i never set viper nor dolby as system app,

the case is that : IF i HAVE app systemizer installed along with Viper or Dolby Module in magisk, the magisk hide will stop working. Doesn't matter which app is systemized, as long as this two modules installed together, it will cause a mess on my magisk daemon, LoL

still not sure why
[Magisk] grandpajiver:
Wow. That's crappy. Messy daemons are not fun to be around.

I may be threadjacking here... but I'm gonna ask anyways. What version of AppSystemizer are you using? I've tried the 12.x versions with the app by loserskater, but it never works for me. I'm using 11.0.7, which works just fine for me... I tried 12.0.6 (or whatever the latest test was in that thread), before reverting. It never worked for me, other than systemizing ActionLauncher3 in /system/priv-app/... even after manually altering the standalone apps config manually.

ymmv... also, theres the terminal emulator app systemizer module, which may solve your problem. I wish you the best of luck, as it's really fn annoying to try and use android pay and all of a sudden you cannot at a register.
[Magisk] otonieru:
Am gonna agree with you that app systemizer definitely has problem starting from 12.0.4 as far as i remember,

either it failed to install, or it buggy,

anyway, sorry to [MENTION=5357345]ahrion[/MENTION] , your module has nothing to do with magisk hide problem

and lets move forward this issue to general magisk help i guess, lol

Thx everyone
[Magisk] MiuKing:
My processing is always stuck on "no" after attempting to play music in the background.

Nexus 6 running Pure Nexus 7.1.2 with Magisk version 12.0
[Magisk] Didgeridoohan:
Try switching to compatible mode in settings.
[Magisk] Zackptg5:
Without a recovery log, nope. Can you tried the mod and Dave the recovery log? Then send that along with the v4a folder and your /system/build.prop?
[Magisk] madscribblerz:
Not worth it if I'm the only one with the issue. I'll just copy the files manually and call it a day.
[Magisk] carlese:
Is there a way to avoid Play Protect warning about v4a? It pops app saying it's not safe.. Disabling it is not an option :)
[Magisk] madscribblerz:
I turned off play protect.
[Magisk] gk1984:
Google is targeting apps that can change SE Linux policy. The Material version of Viper4Android can change SE Linux. Ignore it or use the other version of Viper4Android.
[Magisk] Nakedsnake14:
Sorry I haven't been on by that I mean it will lock the effect that you made on the app so that it will not take off when you go to settings you will see it under notification enabler
[Magisk] Kids in Love:
Can Anyone please help me to set my v4a speaker settings, my device is samsung galaxy core 2..
[Magisk] carlese:
Just FYI, non material version if v4a crashes on OP5 (xXx 9.6 oreo rom), while material version works fine..
[Magisk] matt1515:
View attachment 4430940

I have pixel 2 xl installed this through magisk app but when I open up viper app it won't install the drivers. It has root access
[Magisk] Zackptg5:
V4A has been updated to v1.5! Lots of changes here:

Fix for essential phone oreo

Fixed vendor files in bootmode for devices with separate vendor partitions

Bring back old keycheck method or devices that don't like the newer chainfire method

Fix seg faults on system installs

Edit: Turns out that falling back to the keycheck method in magisk manager completely broke it. So any users with an older device that need it will need to use twrp, or change the zip name. I reuploaded v4a (and other unity mods) with a quick fix (v1.5.1)
[Magisk] carlese:
Non material version still crashes on Oneplus 5 Oreo (xXx 9.6 rom), while material works just fine.. It crashes when I click on the app every time, then forces me to recovery and if I'm not fast enough I have to dirty flash the rom to have a working phone again.. Could you please have a look at it? Cheers!
[Magisk] AlexxAnders:
And sadly still not working or even showing up on Mate 10 Pro... :(
[Magisk] madscribblerz:
Copy the files I mentioned above from this archive into your magisk viper folder.

https://1drv.ms/u/s!Au7GK6mR1p90n6wXt9J0t487FuInqQ
[Magisk] Spooderman46:
Probably hear this a lot around here. But I have the module installed, and drivers all say they're installed fine then when I go to listen to music is doesn't process at all. I've tried both old and new drivers and it makes so difference?

On Axon 7 RR Oreo if it makes any difference.
[Magisk] afcaajax:
Viper Sauron JamesDSP Working all fine together on Oreo S8. I miss one thing.. Dolby
[Magisk] madscribblerz:
Tried this?

https://xdaforums.com/pixel-2-xl/how-to/viper-dd-atom-t3724096/page13

It's for a pixel 2 xl - it worked for me so maybe it'll fly for you.
[Magisk] Adolamin:
I managed to get Dolby, V4A and Ainur all working through magisk on my Kenzo running NOS Oreo (20/2/18).

I flashed Dolby unity in twrp and this worked. I then later flashed v4a FX 1.5.1, then Ainur, then AML all sequentially through twrp and rebooted, and all worked. Flashing these modules through magisk didn't work for me.

****Make sure your music is paused when toggling the master power on in V4A or the audio won't process. This fooled me for ages :(
[Magisk] carlese:
[MENTION=6037748]Zackptg5[/MENTION] Any advice? I see that some other users have this problem (post #1454) but no answers.. Thanks!
[Magisk] raphael.e:
I had the same issue with lineageos 15.1, magisk 16, oneplus 3t.

The order of magisk modules did the trick for me.

1. Install viper & deep buffer remover for example

2 only afterwards install aml

---------- Post added at 12:16 PM ---------- Previous post was at 12:11 PM ----------

I had the same issue with lineageos 15.1, magisk 16, oneplus 3t.

The order of magisk modules did the trick for me.

1. Install viper & deep buffer remover for example

2 only afterwards install aml
[Magisk] Lownita:
I'm getting play protect message on every reboot even though I have disabled it. Will try the non material version to hopefully bypass it.
[Magisk] carlese:
Non material version crashes on my op5, tell me if it crashes also for you..
[Magisk] triggeredbot:
Yes, i had that issue too. Reverted to material version for the time being...
[Magisk] Lownita:
Same on OP3. It crashes and there is a permanent, empty FC message on screen which is getting constantly spammed, I can't even interact with the phone anymore, lol. Have to somehow uninstall the module through recovery or completely uninstall magisk to get back into the OS again.
[Magisk] bjevers:
I'm having this issue on my 5T but with the material version. 1.4.0 worked fine for me, but 1.5.1 is not.
[Magisk] Zackptg5:
Logcat or it didn't happen. This goes to everyone. I can't read minds or hack into your phones to see what happened. You all need to run through the troubleshooting section on the OP. Also, material v4a is fine on my op5t on oos Oreo
[Magisk] carlese:
Material is fine but triggers play protect, non material crashes every time and boots to recovery then, and since you have a OP phone, can you check it this happens on your phone as well?
[Magisk] Zackptg5:
Doesn't happen on my phone. Play protect is useless to anyone with a brain so I just shut it off
[Magisk] ANDR01DN00B:
Is there any way we could get this working on SeLinux enforcing again? After version 2.8 it completely stopped working for my P2XL.
[Magisk] carlese:
I have a brain, the annoying thing is that if I disable it i get the red notification and I personally don't like it. I see that another user has this problem, are you using stable or beta OOS? I switched from beta to stable right now on my OP5 (latest xXx 9.8 Oreo rom) and I might give it a try again.. In case something goes wrong, what should I need to delete from recovery to get the system working again without dirty flashing?

Thanks!
[Magisk] AlexxAnders:
Alright then, here I go with some logs from my installation tries. I hope they are useful somehow.

Viper4Android FX still doesn't show up or even work on Mate 10 Pro...
[Magisk] Zackptg5:
Follow the troubleshooting guide, it has a section for these kinds of problems (post outlined logs if needed too)

Can you get a full logcat and magisk log? Thanks
[Magisk] carlese:
Just FYI, tried non material on latest stable 5.0.4 and it works fine, so I think it has something to do with the open beta..
[Magisk] Fluff'n'Stuff:
Hi! Installation and app is working fine on my OP3 running Lineage OS 15.1 (material+new)

However sound is not processing. I've uninstalled AudioFX and installed deep buffer removal, besides there's not much to see in the logs? Driver status only says "Processing: No", other items are good: driver is enabled, status is normal and audio format is supported.

[EDIT] Wow, my mistake; working perfectly now after uninstalling AudioFX and

rebooting

.
[Magisk] madscribblerz:
Why not use the permissive module for magisk?
[Magisk] ANDR01DN00B:
I have a better peace of mind when SeLinux is enforcing. For this reason, I dont really want to change it for ONE Magisk module, especially since I have an earlier version that works just fine.

I will try to post some logs later in the week!
[Magisk] madscribblerz:
That's the gist of what I'm asking - I'm not trying to be a jerk - I don't know what risks I'm running by allowing permissive or why it's preferable to be enforcing. Was hoping you'd help me understand that.
[Magisk] jcmm11:
Just Google Selinux
[Magisk] Zackptg5:
Updated v4a to v1.5.2! Finally got the volume key stuff figured out so anyone having issues with that shouldn't anymore
[Magisk] Zasnizas:
Hi, first I want to thank to dev for your hard work . A few days ago I install viper 1.5.1 on my device running R.R.O , everything is working fine but I have one problem. When I play music whether on speaker phone or headphone and then I open viper it only stick on Bluetooth and didn't go to speaker phone or headphone. I have to manually change it. How to make it automatically change to whatever source I used. Sorry for my broken English.
[Magisk] DvLAx3l:
I've tried again the module (v1 to v1.5.1) but nothing, still doesn't work, I've tried also to flash it through recovery but no luck, the drivers are not installed...

It's strange because like I said before until the old version 2.9 everything works.

OP 5 with oos 5.0.4 + magisk 16

EDIT: Nevermind, 1.5.2 works!
[Magisk] marbertshere:
Yeah I have the same thing. I'm listening on headphones but Viper thinks I'm on Bluetooth. I have to tweak those settings to get how I like it on my headphones, which is a very different set of preferences compared to my normal Bluetooth setup.
[Magisk] Zasnizas:
(edit) problem solved after update to 1.5.2, have you updated your Viper? If not then you can update it.
[Magisk] alatnet:
Don't know why but it seems to not work for me anymore.

LineageOS latest nightly, Nexus 6, Disabled AudioFX with pm disable, did not install AML.

Use to work before... But everytime I start the app, it says that it needs to install the driver but it is usually fixed with a soft restart.

Now after a soft restart, it just shows abnormal status on it...
[Magisk] Amit Kumar21:
Just updated to the latest version on mi 5s works great
[Magisk] carlese:
To make it work I need to click on exit and then start viper again.. Is it normal? Oneplus 5 oreo
[Magisk] Zgadnijcie:
No, have you other equalizers etc. on phone?

Xiaomi Redmi Note 4X Resurrection Remix 6.0.0 Tapatalk
[Magisk] DvLAx3l:
Same issue, I'm thinking it's something with Dirac audio, also the os close to often the v4a process, so u have to close and open it 3/4 time during the day... I'll try to flash the aml and/or deep buff remover and investigate. ?
[Magisk] carlese:
No equalizers here, just V4A magisk module.. Can't flash deep buffer remover since on OP5 it breaks stuff..
[Magisk] JimFre:
Working great on my OP3 with oos 5.0.2

Made a world of difference for my listening pleasure :)
[Magisk] hatim52:
How do I make it work with Dolby Atmos unity? I flashed it but viper doesn't process...

I am on Oreo 8.1...
[Magisk] Didgeridoohan:
Try closing down your audio player, exit the V4A app (three dot menu - exit), open V4A again and then start your music.

Whenever V4A doesn't process this works for me (and many others). And I'm using Dolby for Oreo unity as well...
[Magisk] hatim52:
Ok will try out....
[Magisk] TahirZX:
Having issues with volume key on 1.5.2 I downloaded through magisk and when flashing through magisk it says press volume up to detect

I press (tried pressing up/down with same results) and then it doesn't ask what version I want to install and just automatically installs old version.

I don't want to use old version I want to use new version with original ui.

Same issue with Dolby Atmos (leeco le pro) I want new version and it automatically installs old version without asking me what I want.

I had no such issues on 1.5.1 [MENTION=6037748]Zackptg5[/MENTION]
[Magisk] Zackptg5:
Can you post the recovery log?
[Magisk] JBolho:
Tried to install from Magisk Manager and from TWRP, first Viper, then UDB remover and then AML (following a user suggestion), but nothing shows up. Manager says it's installed, log doesn't show any error but Viper4Android app simply does not show up...

Running EMUI8 on a Honor 9.
[Magisk] jcmm11:
Just rename the install zip

v4afx-v1.5.2_mat.zip

The install will see the mat at the end and automatically install the new material design version.
[Magisk] TahirZX:
Okay and What to rename to if I want original ui and 2.5.0.5?

---------- Post added at 06:57 AM ---------- Previous post was at 06:57 AM ----------

Sure just give me a second
[Magisk] TahirZX:
[MENTION=6037748]Zackptg5[/MENTION]

I tried again. Viper4fx installed okay this time idk how. It was having same issue as the one I will tell now.

Here are the magisk logs of 1.5.1 and 1.5.2 as well

In both i pressed volume up

1.5.1 installs new ui as I wanted so it's perfect

Problem:

But 1.5.2 installs old ui even when I press volume up

It only asks for volume press check and when I press volume up

It skips for asking what ui I want and just directly installs old ui.

Plz help!
[Magisk] jcmm11:
Well if you'd read the OP you would see the following:

Special Instructions:

If you already know if you want the old or new v4a, just add 'old', 'new', or 'mat' to the zipname (make sure there are no spaces) prior to flashing

So the answer to your question is "new".
[Magisk] JBolho:
Tried every single method, even with SE Linux permissive, logs don't show any error, files are in place (i went to look for them manually in magisk folders), but app just does not show up in drawer. Installing only the app itself tells me to install the driver, says it's done, i reboot, tells to install the driver again. Any suggestions? Please?

EDIT - It seems that Magisk is pointing and installing the app to "vendor/app" (and it does install and mount that path), but my system originally does not have that folder, so i'm guessing that anything that is installed onto "vendor/app" will not be recognized. Is there any way that instead of installing onto "vendor/app", the script installs on "system/app" or "system/priv-app", since apparently those are the only paths that my system recognizes as app paths? (EMUI8, Android 8.0.0)
[Magisk] FootSlave:
Thanks for that info (wondered why there is no app)

Just cut the folder from vendor and paste it into /system/app

Restart and you have the app working!
[Magisk] Zackptg5:
Wow, that's the first I heard of that. Unzip v4a, open config.sh, add a # in front of the line that says DYNAMICOREO=true. Then rezip it and flash away

---------- Post added at 03:06 PM ---------- Previous post was at 03:03 PM ----------

Logs look fine, I'll look everything later today but since this is for Dolby, can we move this to the Dolby thread? Also, for the name change, just add "new" for new ui or "old" for old ui at end of zipname (make sure you use no spaces) and then flash in twrp (won't work in magisk manager) as an alternative to using the vol keys