yashsingh1/xdaforums huggingface dataset:
[Magisk] BootloopedMillennials:
Nope, this version with a combination of Magisk 15.1 is a no go. This is on LineageOS 14.1, android 7.1.2. Even tried setting selinux to permissive.
[Magisk] chudy_85:
Work correctly on P9 witch Magisk v15.1

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] mamama07:
This is why I ask. Thanks.

Don't be sad. It's just ridiculous why OP just change "something" in rom what destroy apps like v4a without touching SELinux state.

BTW - OP3 orejro, magisk 15.1 beta and your mod 2.8 - I still have problem with version double volume up - after reboot app not showing in draver, just broken icon and info about crash. App package name is with v2 in end of name. What kind of logs you need for fix that problem?
[Magisk] DarkDestiny08:
Hey! So I tried the new installer from Magisk Repo.

If I try to select the Old v2.3.0.4 with SSuper Quality Driver, it doesn't show Convolver and Viper DCC as options after successful installation.

Both these options are present and work flawlessly on v2.5.0.5 however.

I have a Viper folder with IRS files for convolver in Kernel Folder and everything in place. however, I'm unable to get the options in old Viper.

Possible Reason?

Devicces :

Samsung galaxy S6 (G920I)

OnePlus 5T (A5010)

Both running Stock ROMS.

Rooted with Magisk SU v15.1

Viper Version 2.8 from Magisk Repo.
[Magisk] Zackptg5:
Can you send a full logcat and magisk log (from magisk manager)?
[Magisk] Hellsblade:
My two cents. Switched to oneplus5t:good: Installed 7.4.6 ROM, TWRP 3.2.1.0 Magisk 15.1and V4A 2. 7 among other Magisk modules. Everything is working as expected.
[Magisk] p34rp34r:
I think you need to enable "Expert" UI

3 dots > UI Setting > Expert
[Magisk] Josey Wales:
Did anyone get the latest update working on Galaxy Note 5 stock/rooted Nougat 7.0?
[Magisk] sjamie:
When switching between old, new, and mat versions of this mod, is it recommended to completely uninstall it before switching or does dirty flashing work?
[Magisk] yyz71:
Best to reflash your ROM. But without wiping systems... Cache will do ?
[Magisk] Zackptg5:
Yup. Just flash zip again to uninstall. Dirty flashing won't work if your ROM has addon.d support as the mod will survive a dirty flash
[Magisk] sjamie:
Ahh... didn't know that. Thanks! :svetius:
[Magisk] DarkDestiny08:
Works on my S6 Stock Nougat. Should work on Note 5, same SoC.

Make sure you update to Magisk v15+

Disabling SoundAlive may help. Can be re enabled later if required. Both work parallely for me.

Use Titanium Backup to disable/re-enable.
[Magisk] Josey Wales:
I did already, still NOT processing. . .
[Magisk] anujyadava:
Is your AML updated to latest one?
[Magisk] QkiZMR:
Did you disabled deep buffer?

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] fahric74:
Install v4 and working in compatible mod, after

install dolby ,but after that dolby remove v4 app?

Please help!thanks
[Magisk] tinOFbeer:
I have the same problem with 2.5.0.5 (v2.8), I can not install drivers because there is an I/O error each time.

When I install version 2.3.4.0 the error did not occur, but after each restart v4a asked for driver installation again.

OnePlus 3, OOS 5.0, Magisk 15.1, v4a 2.8 from Magisk repo.

My currently installed modules:

App Systemizer, Busybox for Android NDK, iYTBP vanced, Privileged Permission Whitelist

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Magisk] condor020:
Having same problem on aicp rom 7.1.2 After the magisk update, it module from 29dec
[Magisk] DarkDestiny08:
What Music Player are you using?

---------- Post added at 04:36 PM ---------- Previous post was at 04:31 PM ----------

That is not necessary for Samsung Stock Music Player.

Works for me without it.

Same SoC and Android version.
[Magisk] Jerry SQ:
LG V20

Stock rom nougat 7.0

Magisk 15.1

Modules: Audio Modification v2.8, Greenify v3.9, Universal Deep-buffer v3.8, Dolby Atmos Le eco v3.8

Issues: Install Viper module from v2.6 to v2.8 cause all modules to be disabled

Please help, very Appreciate

P/s: Install log seem normal, aslo Magisk log
[Magisk] yung40oz84:
I am on OOS Oreo open beta 1 for OP5T and I cannot get viper processing......... what should I try to get it working?
[Magisk] Zackptg5:
Did the installer say oos Oreo device detected? If not, you'll need to set selinux to permissive. Otherwise, not sure. I won't be on Oreo on my op5t until it's stable.

Oos betas are pretty buggy betas anyways
[Magisk] Sytis:
Finally the latest version is working on my OP3T with OOS 5, but now it says always processing even when no music or sounds are playing. Other than that everything is peachy, thanks :good:
[Magisk] yung40oz84:
Ya it did say detected and went to permissive. I removed the modules and then reflashed them and now it's working. It was very odd, lol
[Magisk] Josey Wales:
I didn't think it did. All other versions of this module I simply flashed in MM and everything was great, NO issues period [emoji17][emoji17][emoji17]
[Magisk] yung40oz84:
It went back to not processing and the only way I could get it processing for now is UDBR, processing immediately but I'm not a big fan of removing deep buffer. For time being it will do, lol
[Magisk] Zackptg5:
Sounds about right. Seems lots of phones made around that timeframe need ubdr like my bullhead but my op5t doesn't strangely
[Magisk] tinOFbeer:
[MENTION=6037748]Zackptg5[/MENTION]

DO you have an idea for a problem in post #1493 ?

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Magisk] Zackptg5:
My first guess would be that one of the other magisk modules is interfering with it but not sure as the magisk log looks normal.

When you get the io error, that means that either the patched cfg files aren't being properly mounted or that there's an sepolicy not being set.

So can you send me a full logcat so I can see if there's any audit errors, and can you try without any other modules installed (busybox is definitely fine though so you can keep that)
[Magisk] Josey Wales:
I mainly use Disk DJ or YouTube and this is the first time this module does NOT process. . .
[Magisk] SoulSlayerPT:
Oneplus 3t with Oreo cannot install driver I/o error anyone has a solution for this?
[Magisk] tinOFbeer:
maybe you can read a few posts above

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Magisk] Cablespider:
I just installed Oreo 8.1 on my Axon 7 for the first time. I wanted to report that V4A 2.8 is processing fine. Awesome!
[Magisk] Syoenth:
I have a nougat ROM and can't see the app in the app drawer what I must do?
[Magisk] Badger50:
With your root explorer, go to your root directory, and go to...magisk/ViPER4AndroidFX/vendor/app/ViPER4AndroidFX/ViPER4AndroidFX.apk

Click and install the apk. Or, extract the apk from the zip, and then install it.
[Magisk] Syoenth:
I did that, but now ask me install the drivers .-.
[Magisk] Zackptg5:
That's not a real solution. Everything should already be installed including apk and driver so if it's not showing up in your app drawer, then that means that magisk didn't mount it. You'll need to see the magisk log (via magisk manager) to see the last things that ran to find out what caused the problem (likely a post-fs-data script). Can you post your magisk log?
[Magisk] Syoenth:
it seems it's a problem with post-fs-data, in the log can't see the post-fs-data running, I leave the log of the magisk
[Magisk] esbatulembek:
Even after update to magisk v15.1

Still no processing
[Magisk] themrmotivator:
HTC U11+ Latest magisk . Driver fails to install I/O error.
[Magisk] ketwi15:
I have UDB and am trying viper on Galaxy s6 edge with 15.1. Music processes through viper for about 6 seconds then stops on v2.8.
[Magisk] ketwi15:
Here's a log. Again v2.8 stop processing after about 5 or 6 seconds on my SUBSCRIPTION Edge
[Magisk] n@vier:
[MENTION=6037748]Zackptg5[/MENTION] [MENTION=5357345]ahrion[/MENTION] latest V4A was detected as harmful by google play protect...I know surely it will be a false positive but I flashed all versions from 2.0 to 2.8 and this is the first time I received this so I'm reporting.

Maybe it could be something in the new script...or some permission I have no idea...

If you can take a look at this it would be great....thanks and Happy New Year! ;)
[Magisk] Badger50:
If your using the material apk, that's what your gonna get from google play protect. Nothing to worry about :good:
[Magisk] n@vier:
Yeah the material V4A I'm using...thanks for the reply!

Best wishes to all!
[Magisk] JairPaalman:
V4A not processing on Magisk 15.2 on Samsung

[MENTION=5357345]ahrion[/MENTION] V4A has not been processing on my Galaxy S8. I suspected it was because of the SELinux permissions. Now, there has been a Magisk update fixing SELinux problems on Samsung ROMs. Sounds like my problem might have been solved, but is isn't. I've removed the module, updated Magisk, and reinstalled the module, but it still won't process. What did change, however, is the sample rate, which is now 44100, and was 48000 before. Anyways, I hope there will be an update to fix the SELinux permissions soon, though I know you've been busy with OnePlus Oreo support. Good luck! :D
[Magisk] bc1977:
Hi all,

I've tried to install this module in my oneplus 3t on Oreo/ob20 with magisk 15.2, but it keeps asking me to install the drivers.

Here is my log.

Thanks in advance.
[Magisk] RogerBoy123:
I need your help! I was flashing your viper4android magisk module, but it gave me a choice to install 2.5.0.5 or 2.3.4.0 with super quality driver. I want the new one, but I can't choose because you can't tap on it, so it's stuck on the flashing screen! :(
[Magisk] Badger50:
Use the volume control button to choose the version you want.
[Magisk] madscribblerz:
Just thought I'd throw in a kudos.

Pixel 2 xl with Jan update to 8.1 works great.
[Magisk] Diesel_Jeremiah:
Pixel 2, JAN 2018 update, working wonderfully.
[Magisk] otonieru:
No problem overhere as well, January Security Patch, Pixel 2 XL

Too bad, Dolby still not working
[Magisk] Badger50:
Well now, I wouldn't exactly say that :cool:

https://xdaforums.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
[Magisk] otonieru:
Still gonna say that, LoL,

am on that thread as well, and i tried the oreo zip shared there, but Dolby give me FC everytime i tried to open it. Weird. Viper work perfect though
[Magisk] Badger50:
Did you download the oreo zip to your pc and then transfer it to your phone. V4A and dolby are working fine on my end.
[Magisk] otonieru:
Yes i did,

It flashed fine as well,

Only it wont open
[Magisk] Badger50:
Oh that's weird. Sorry man, I can't help you further. I'm sure somebody will though :good:
[Magisk] dreinulldrei:
Hi there, trying v2.8 on OP5T with 4.7.6, but unfortunately it does not process audio. Is there anything I can help with to debug this?
[Magisk] Zackptg5:
Working fine for me on same device and same ROM so it's something with your setup. Remove any other magisk audio mods and any other audio apps. Also, processing is always no if you're not playing any music
[Magisk] dreinulldrei:
Thanks for the feedback. Indeed, I've tried this a couple of times. I just re-setup PlayerPro with DSP module off/on, and all of a sudden it's working. Strange. But thanks again.
[Magisk] otonieru:
Fixed it.

Apparently, it wont work if i use a temp TWRP (boot from fastboot)

I flash TWRP and then dolby,

Now it work.

So weird though
[Magisk] mattcooper:
Any idea why I'm getting "com.vipercn.viper4android_v2 has stopped"? Get the message on startup and cannot launch the app (just get that message). Nexus 5X on 8.1 with Magisk.
[Magisk] shindiggity:
Yup just delete it with tianium backup and reboot
[Magisk] madscribblerz:
Confirming Dolby works on Pixel 2 XL (with viper).
[Magisk] Frenzi2012:
Dolby works on Android 8.1? Please link
[Magisk] madscribblerz:
https://xdaforums.com/pixel-2-xl/how-to/viper-dd-atom-t3724096/page2
[Magisk] Zackptg5:
Hi everyone! A troubleshooting section has been added to the OP with some common problems and solutions and proper bug reporting. Any problems reported without consulting it first will be ignored as it's either already been answered, or there's simply no way anyone can help you without proper logs/troubleshooting. Thanks!
[Magisk] p34rp34r:
[MENTION=6037748]Zackptg5[/MENTION] Thanks for the new troubleshooting section. I checked my logs and I don't see any avc regarding viper4android (or its associated pid) in there, so it seems like it's not even requesting permission? When I checked the Enable checkbox on, there was a line near the bottom of the dmesg about the DSP initializing, but the stream or effects were inactive? I don't know how to troubleshoot this further. Logs are attached.

Also, did you see my previous post about the error in magisk/viper4androidfx/post-fs-data.sh? When I try to run it (with root priveleges) it returns the error shown here

source type hal_audio_default does not exist
Error in: allow hal_audio_default hal_audio_default process execmem
source type hal_audio_default does not exist
Error in: allow hal_audio_default hal_audio_default_tmpfs file execute
source type hal_audio_default does not exist
Error in: allow hal_audio_default audio_data_file dir search

Is "hal_audio_default" supposed to be a universal Android sepolicy? How can I tell if it's a valid policy for my stock 7.1.1 Nexus 6? Could this be the reason why it isn't working?
[Magisk] Zackptg5:
Hmm, if in doubt, just delete those lines from v4a post-fs-data script but I doubt that that would cause any issues. What other magisk modules do you have installed? I saw greenify mentioned in the logcat. It's possible that it's messing with v4a. Can you try removing it and seeing what happens?
[Magisk] p34rp34r:
Thanks for the reply. As far as Magisk modules go, I have Audio Modification Library (from V4A), injected YouTube Background Playback Vanced - black themed Magisk Repo, Pixel 2 Launcher Systemless, Tethering Enabler, Unified Hosts Adblock, Universal deep_buffer Remover (this never worked for me in the past, possibly because I don't have some of the XML files it looks for?), and Viper4Android FX.

I tried disabling Greenify and rebooting, but it doesn't make a difference.

I somehow managed to get V4A to process for a few seconds by using Force enable V4A and repeatedly playing/pausing something in Google Play Music, but it always stops processing after a few seconds. I've attached a new dmesg log which has some more interesting errors, but I still don't know what to make of these messages.
[Magisk] Zackptg5:
dmesg is more for kernel errors so that won't help me debug much :/ deep buffer remover looks for quite a few different file combinations. The logcat you posted before looked incomplete. Can you reboot, open v4a, toggle master power switch, try playing music, then post logcat? Also, have you tried it without deep_buffer remover?
[Magisk] whalesplaho:
I posted earlier... Flashing from v2.5 up causes bootloop!

Only v2.4 is working.

Sony Xperia Z5

Stock based rom 7.1.1

Nougat

Xposed

Magisk.
[Magisk] no_keys:
my volume keys are broken on my phone and so have tried to install the zip by appending "new"/"old"/"mat" to the file name without spaces as the op suggests but the zip still asks for volume selection of driver version. i've tried every combination of renaming the zip with no success.
[Magisk] ketwi15:
I have the same problem.
[Magisk] Zackptg5:
That only works in twrp, not in magisk manager. For example: Viper4AndroidFX-Mat.zip

Make sure there are no spaces in the name
[Magisk] Brachogan:
I am using Ainur Audio with AML 2.8

When installing v4a side by side with it it gives me conflict

I tried to install v4a first or Ainur first both ways conflict with each other, both works just fine tho
[Magisk] itssomraj:
In my case v4a mat new is working but v4a stock new is stopping continuously.

Flashed over ainur sauron mk2.

Lenovo z2 plus. Running AEX5.1.
[Magisk] Zackptg5:
That's by design. When an AML mod is flashed and sets the same props another AML mod sets, the installer won't install those props and will generate that file and message so you know. More advanced users can choose which ones to use by manually copy and pasting target lines to system.prop for the mod (but for this case, there's no need)
[Magisk] BootloopedMillennials:
[MENTION=5357345]ahrion[/MENTION] [MENTION=6037748]Zackptg5[/MENTION]

Since one of the Magisk 15 builds I've had trouble with getting this Viper4Android module to process.

I got it to finally process by doing the following, copying /magisk/audmodlib/system/etc/audio_effects.conf to /magisk/audmodlib/system/vendor/etc/. This overwrote the audio_effects.conf already in that directory. After a reboot v4a was processing successfully.

Any thoughts why this worked

Edit- This also worked for ahrion's Dolby Atmos module that I had issues with too.
[Magisk] Zackptg5:
That must mean you're on one of those roms where the devs forgot to add vendor configs for some reason. Both vendor and system configs need patched for these apps to work
[Magisk] BootloopedMillennials:
Official LineageOS 14.1. It's weird the rom developer must have changed it in a recent build, it has worked without doing this before.

Is there any issues I should expect moving that file?
[Magisk] Zackptg5:
Instead of moving it, copy it. So keep the one in system etc, and make a copy of it in vendor etc. Shouldn't cause issues (it's how it's supposed to be)
[Magisk] Syoenth:
I read you need that the kernel must be enforcing instead permissive to this module works, is it true?
[Magisk] Syoenth:
I have a permissive kernel and the last magisk, I installed this module and can't see the app on the app drawer, I looked at magisk log and can't see the post fs scripts log, what can I do to this module works? I attach the log
[Magisk] Zackptg5:
Literally nothing loaded. Do you have core only mode on, disable that if you do
[Magisk] Syoenth:
core only mode is disabled, when I enable magisk core only the post fs scripts load correctly, I load another v4a module and it load correctly, only on this module have issues :/
[Magisk] ozzrivi:
Old version 2.1

can anyone please share old version 2.1.

latest version did not work on my redmi note 3 pro running on pixel experience oreo 8.1

thank before
[Magisk] Syoenth:
i attach the log with only core mode on
[Magisk] p34rp34r:
Holy monkeys, that worked! Thanks [MENTION=3382406]Visi0nofExcellence2[/MENTION]!! V4A is working flawlessly now! I copied the conf in /system/etc to both /vendor/etc and /system/vendor/etc and now it's working great!

Strange though - I'm using a stock Google factory image (with the exception of Magisk, of course), so why are the confs messed up? I tried doing a compare of the two conf files and there are a lot of differences. All the lines referring to V4A are the same, but the vendor conf includes a lot of references to some "fmas," visualizers, and some mot_speaker_helper, which I'm guessing is related to the Nexus 6's front-facing stereo speakers. I might try adding a few lines from the vendor conf back into the system conf and see what line breaks it...

But anyway, thanks [MENTION=3382406]Visi0nofExcellence2[/MENTION] and [MENTION=6037748]Zackptg5[/MENTION] for the help, and of course [MENTION=5357345]ahrion[/MENTION] for the mod!
[Magisk] lekcin18:
I have 2.2 for a very long time and finally decided to upgrade to 2.8 but it causes error on my magisk? all my modules doesn't work after reboot. all my debloated apps came back. my iytbp is gone. and no viper4android.

all modules are still can be seen in module section. but for some reason all doesn't work including viper4android.

removing the viper4android module solve the problem.

installing version 2.2 no problem

installing version 2.8 causes problem

I'll stick to 2.2 for now

magisk 15.2

any solution?
[Magisk] MeetFace:
Thanks for this, working wonderfully in my Pixel XL 8.1 with latest Magisk. IMO, much easier and painless to run ARISE.
[Magisk] Syoenth:
can you give me a link to download the version 2.2? as you can see, I have issues with this module too
[Magisk] lekcin18:
I have backup here in my phone but can't upload it without developer's permission. you may ask him though or if it's OK to him I can upload it. sorry mate
[Magisk] Hadi99:
I have issue with both system and systemless Viper4Android on LG G5. Everything works fine untill suddenly, the phone reboots when playing audio from the speakers.

---------- Post added at 01:08 PM ---------- Previous post was at 01:06 PM ----------

If you post me version 2.6 it will be great, as version 2.8 disables all of my magisk modules. I don't think the developer would mind as it is still under his name/ in his thread and you aren't taking any credits.
[Magisk] sluogn:
[MENTION=5357345]ahrion[/MENTION], I using v2.4 working fine.

Today I updated to v2.8 but it error, when I flashed and rebooted, SuperSu app show notification "The su binary needs to be updated"

I press button update but it show unsuccessful update

I dont know why it error

I using rom CM13, supersu v2.82
[Magisk] BootloopedMillennials:
Apologies my wording was terrible, what I did was copy and paste not move. Glad to get these modules working again, especially enjoying the Dolby Atmos.

:good:
[Magisk] LuoTW:
Excuse me.

I use Magisk(15.2)Install Dolby(ZTE Axom 7)+ViperFX

But Dolby normal working

ViperFX not working?...How to deal with it.

I'm have install Audio modification Library (2.8)Module.

My device Redmi note3Pro+NOS 7.1.2

Help me?

Forgive me bad English，Thanks.

[IMG="error"]https://img.xda-cdn.com/yuLA8I2O4e92s_qVoW31mmFgFkU=/https%3A%2F%2Fi.imgur.com%2FJqXPDKB.png[/IMG]
[Magisk] SilvrDrgn:
I just finished removing absolutely everything related to Magisk from my Pixel 2 (non-XL) to "start fresh" with updated versions of everything I'm using.

Steps:

1) Using twrp-3.2.0-0-walleye, re-flashed V4A v2.4 to uninstall it and AML. Rebooted.

2) Using Magisk Manager v5.4.3, uninstalled Universal Deep Buffer Remover. Rebooted.

3) Using twrp-3.2.0-0-walleye and Magisk-uninstaller-20180101.zip, uninstalled Magisk-v14.5420NOdtbo. Rebooted and checked for proper stock device operation.

4) Removed "-w" from the appropriate line of the Pixel 2 January update flash-all.bat file, and flashed the update. Rebooted and waited for it to finish its updates. A notification bar appears at the top of the screen for it. Just have to wait for that to disappear.

5) Using twrp-3.2.1-0-walleye (note update version of TWRP), flashed Magisk-v15.2.zip. Rebooted and checked for root. All good.

6) Usgin twrp-3.2.1-0-walleye, flashed v4afx-v2.8.zip from OP. Rebooted. Check music, cannot process.

7) Using Solid Explorer, copied /magisk/audmodlib/system/etc/audio_effects.conf to /magisk/audmodlib/system/vendor/etc/. and rebooted.

8) Processing is working now and is stable! Yay!! Note: SELinux is in enforcing mode, and Universal Deep Buffer Remover is not needed.

Thanks guys!!
[Magisk] JairPaalman:
ViPER4Android not processing on Samsung Galaxy S8

[MENTION=6037748]Zackptg5[/MENTION] ViPER4Android is still not processing on my Samsung Galaxy S8.

As last resort, I've restored the stock firmware and did a factory reset, but that didn't help either.

I've tried installing Magisk using TWRP and by flashing a patched boot image, and for both methods I've tried enabling and disabling force encryption, but I still couldn't get the module to work.

I suspect is that there is something work with the SELinux permissions. I've tried setting SELinux to permissive using a Magisk module, but this caused a bootloop.

I should also notice that there is no audio_effects.conf file under /system/etc and /magisk/audiomodlib/system/etc. The file does exist in /system/vendor/etc and /magisk/audiomodlib/system/vendor/etc. I've read that I should move the file from /system/etc to /system/vendor/etc, but as it doesn't exist in the first folder, I can't.

ViPER4Android did work before, on Magisk 14, module version 2.2 and an older firmware version (but the same Android version).

Is this a known error on Samsung Galaxy S8 devices, and are you still working on the permissions?
[Magisk] BootloopedMillennials:
I feel this "issue" with the audio_effects.conf could be the reason for a good chunk of v4a module not processing and other audio modules not working. I had to do it on two of my devices.