yashsingh1/xdaforums huggingface dataset:
[Magisk] Zackptg5:
Unfortunately, since that's very device (and likely rom) specific, it can't be added in. That's just part of disabling any stock audio effects on the user end :(

---------- Post added at 11:24 ---------- Previous post was at 11:22 ----------

Did you read the troubleshooting section of the OP, there's a whole section for this kind of problem
[Magisk] Xennet:
Here it is

Sorry earlier post was XDA labs error....
[Magisk] Syoenth:
I read it, but I don't have any other modules that run other post-fs scripts and/or ART optimization
[Magisk] JairPaalman:
I tried this, and ViPER4Android did process my sound, but nothing comes out of my headphones when I enable V4A. I've got an S8. I think this started happening after a firmware update around november/december. I'll try to pull the audio_effects.conf from an older firmware to see what changed.
[Magisk] Zackptg5:
Hmm, can you try this ubdr? I modified it slightly so hopefully it'll work with your device
[Magisk] Zackptg5:
You're log didn't even run post-fs-data mode which makes me think there's something wonky with your magisk install. Can you try uninstalling and reinstalling magisk, flashing v4a again, and then taking magisk log?
[Magisk] Nguyễn Thế Vinh:
I figured this when i was messing around with the audio effect file. It work great on my Note 5 and S6 though. Also, the file i deleted is related to something called "myspace" and "mysound" which i probably never going to use :)
[Magisk] Xennet:
Thanks...

Tried the modded ubdr...

Flashed rebooted...

Still the same damn thing..

Install drivers and I/O error...

Not processing...???
[Magisk] Syoenth:
I uninstalled and reinstalled magisk and v4a but still nothing, I'm using a custom ROM for Samsung J7, when I was on the stock MM I haven't problems, I switched to custom ROM because I couldn't move app to system and app systemizer trigger SN for some reason on MM, I attach the logs
[Magisk] Zackptg5:
Can you replace this file in /magisk/audmodlib/system/vendor/etc with the attached one
[Magisk] Zackptg5:
That's too weird. Try moving the post-fs-data scripts in audmodlib and v4a to some other location and see what happens. Other than that, I'm not too sure why nothing is running. Can you post your magisk img?
[Magisk] Xennet:
Replaced the file gave permissions rw r r. Rebooted.

Still the same install drivers error pops up
[Magisk] Zackptg5:
Dang, so much for that idea. Once oneplus drops a stable oreo update for the 5t, I'll be able to take an in depth look at it. They messed up something with v4a but at this point, I'm not sure what :(
[Magisk] Syoenth:
Where I should move them?
[Magisk] Xennet:
Ok..Take your time..Hope you will finally get it up and running...
[Magisk] Zackptg5:
Anywhere really, like sdcard. Basically, if it works after moving them, try putting one of them back and seeing what happens. Try it with each to decipher which is causing the problems (if any). Also, I'm assuming you have core mode off, it needs to be off for modules to load
[Magisk] Syoenth:
Here is it: https://drive.google.com/open?id=1OaHNm_48nn5jMKsBKAPrvyn_HA29c5Gd
[Magisk] Zackptg5:
Well there's your problem. Nothing loaded cause nothing's installed. Did you flash magisk uninstaller, then reinstall magisk? Flash v4a 2.8 again after that's done
[Magisk] Syoenth:
I did al that and nothing :(
[Magisk] DSX2:
Hey all!

After hours of trying to get Spotify to work through V4A on my S8+ (running Rennovate Ice Note rom), i've managed to get it.

Initially i installed V4A and Universal Deep Buffer Removal (UDBR) from Magisk. This had V4A working with virtually everything (including Soundcloud) EXCEPT for spotify.

The solution for me was to uninstall Universal Deep Buffer Removal AND Audio Modification Library, leaving only V4A installed as the only Magisk module.

Now im not sure why this works, but hopefully it will work for some of you's with issues. Since it's all done through Magisk Installer, you can always just re-install AML and UDBR if theres issues
[Magisk] Syoenth:
I moved the post-fs-data.sh from v4a and it's working now, I tested it with version 2.6, I'm going to install the ver. 2.8

---------- Post added at 01:24 PM ---------- Previous post was at 01:04 PM ----------

Well, it worked, it seems my phone only can load a post-fs-data.sh script, I dunno why, but wwell, it doesn't matter now since it's working now, thanks [MENTION=6037748]Zackptg5[/MENTION] for the help
[Magisk] woozie.2007:
Sorry to bother you, i checked all but i can't figure out how to make it to works, really i'm feel stupid because sounds is incredible 10 sec, then is...no comment. Give me a sugestion please, where i have to look in android, what could stop it after 10 sec? Only stock eq is audio effects which is disabled, I haven't other eqs or app with own eq, if you need any file from the phone, just tell me and i'll send it to you. Thanks
[Magisk] Kdx10:
Hi guys. This is my first time using this mod. So please bear with me.

I browse a little page back but seem cant find answer to my problem.

I flashed this v2.8 of v4a in my moto z play with cosmos rom 8.1 rooted via magisk 15.2 but when i rebooted it cant find the app in the app drawer. But i think and only i think the sound is quite boost. Any tips how or what should i do to make it appear ?

Thanks in advance
[Magisk] griffynix:
I tried flashing this on Magisk 14 and i always get installation erro saying i should get Magisk v15.0+.

The problem is Magisk 15.2 can be flashed succesfully on my phone but after reboot Magisk App says Magisk not installed.

What can be the fix for this?
[Magisk] Nguyễn Thế Vinh:
I just updated the fix, good luck !
[Magisk] Hadi99:
Thanks! Removing that file from V4A Module 2.8 worked for me too. (Magisk 15.2, LG 7.0)
[Magisk] mahtiel:
Thank you very much for your great work. I installed it last week and it works perfectly on MIDO (Redmi Note 4 Global) with Pixel Experience ROM based on Oreo. :)
[Magisk] cichy.:
Thanks you!
[Magisk] JairPaalman:
This version worked for me. Apparently, the code you removed was added in the latest firmware updates, which is why V4A failed.

[MENTION=688191]zachp[/MENTION]tg5 perhaps you could add an update that removes this specific code. Since it is only present on Samsung devices, it should not cause compatibility problems on other devices. Otherwise, you could try to add an if statement that verifies wetrher the client is a Samsung device.
[Magisk] Lossyx:
I've seen people having issues on OOS Oreo Beta. Wanted to report it works fine for me on OOS Oreo Beta 1 (OP 5T)

Edit: latest version broke it for me,
[Magisk] st4ik:
What could be the reason that the sound effects randomly stop working ?

Driver status:

NEON Enabled: yes

Enabled: yes

Processing: yes

After the phone reboots by sound effects work and after some time they stop working again.
[Magisk] LuoTW:
I am very sorry .

I did not read the post carefully

attach the log,If you need any file,I will attach it immediately.

I will try to use translation to understand.

thank you very much

ps.I found after reboot all normal, when I plug in the headset, Dolby, ViPerFX become disabled, the headset pulled out and did not return to normal?.
[Magisk] knnthgngb:
Does anyone have Viper4Android FX 2.5.0.5 v2.5 zip file or any links? I did try searching but I can't find on any post..
[Magisk] tinOFbeer:
Really?

#1595

https://github.com/therealahrion/ViPER4Android-FX/tags

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Magisk] JairPaalman:
Means there is another sound effects application which block V4A from working. I had the same problem with SoundAlive; V4A would randomly stop working.

You can permanently solve the problem by removing or freezing the app that is interfering with V4A. To see which app is interfering, open settings, go to applications, show system applications, and try to force close any sound, audio or music app you suspect from interfering, then reopen V4A. If V4A works again, the app you closed was interfering. The most common suspects are SoundAlive on Samsung devices and MusicFX on AOSP devices. Your manufacturer might have a different application installed, though.
[Magisk] st4ik:
Thank you for the suggestion.

I use Cardinal AOSP which had an equalizer installed - but it was turned off.

I have now uninstalled it via titanum backup - I'm testing ...
[Magisk] tonyfreak215:
I have the exact same issue on my V20 with 2.8. None of my other apps can access root, it's as if I "lost" root.

SuperSu 2.82, Stock-based Nougat rom. Uninstalling V4A fixed the problem.

I tried v2.8 through 2.4, this problem occurred on all of them but 2.4; 2.4 works.
[Magisk] Zackptg5:
Without logs, I can't help (see troubleshooting section on OP). Have you tried removing the v4a post-fs-data script from the su.d directory?
[Magisk] tonyfreak215:
Here are the logs.

Thank you for your help. If there is anything else that would help, let me know.
[Magisk] Zackptg5:
Hmm, I think I know what happened but I need to check one more thing. Can you post this file: /system/etc/ViPER4AndroidFX-files

(or contents of the file)
[Magisk] tonyfreak215:
Sorry it took so long, had to figure out how to do it.
[Magisk] Zackptg5:
Okay, it's what I thought (I think). In that file, remove this line: /system/vendor/lib/libstdc++.so

Then delete this file from your phone: /system/vendor/lib/libstdc++.so

See if it works, if not, can you post another logcat?
[Magisk] tonyfreak215:
Any tips on how to that?

I've tried a few different "root explorers" with no luck. (copying pre-edited file, editing file directly) I don't think the apps have root access. (which would explain why supersu can't update)

I also tried adb push. But it glitches out. (using minimal adb)

Edit: Figured it out.

Apps still have root, just no supersu prompt so no new permissions can be added.

That worked, issue is resolved. Thanks for your help!
[Magisk] Zackptg5:
No problem! Next version will only have the lib copied for pixel 2 devices since they're the ones that seem to need it
[Magisk] pinoholo:
Not help too, installing permissive module make all madule disappeared. Had to reinstall Magisk to properly running Magisk again
[Magisk] Pablo.x:
That's so strange, I've never had a problem like that...
[Magisk] LuoTW:
Excuse me!

I reinstall Magisk Dolby,ViPerFX,UdbR,AML

Reboot everything works.

But earphone plugged in,Dolby ViPerFX result not work...

I try copy the audio effects from magisk/audmodlib/system/etc to magisk/audmodlib/system/vendor/etc.

Reboot earphone plugged in still not working.

help.
[Magisk] preference:
I have similar issues when using AML related mods, audio works on the phone speaker but the phone gets super ****ed up when I plug in headphones. No logs sorry, been using the alternate viper4android in the repo because I don't really need atmos

On OOS nougat oneplus 5t.
[Magisk] Zackptg5:
That's why. I have same device and ROM and everything works fine. Use aml v4a and get rid of ubdr as it's not needed for op5t nougat and messes stuff up
[Magisk] preference:
You are a ****ing God send. Thanks for all your hard work.
[Magisk] LuoTW:
oh...thank you for your help.This too difficult to me.

I've given up,maybe NitrogenosN not work?
[Magisk] FreeBait:
Is this mod Working on Zenfone 2 laser running a lineage os 15?
[Magisk] knnthgngb:
After installing the latest module of Viper4Android v2.8 on Magisk v15.3, still all modules disappeared like I encounter on the last Magisk v15.2. Any solutions for this? I'm running on Samsung 7.1.1 Nougat with Magisk v15.3..
[Magisk] JFK1975:
Have you already sent your logs to the thread that anyone is able to help you?
[Magisk] lock1nout:
cant get processing with headphone or speaker, just get it with dolby a7000.

using newest aml, v4a, ainur sauron, magisk.

selinux is permissive.

ressurection remix 7.1 on N9000W8 htle.

any thoughts?
[Magisk] Zackptg5:
V4A has been updated to aml 2.9! See aml thread for changelog.

V4A specific changelog: many of the newer sepolicy patches needed for some pixel and pixel2 devices seem to be causing problems with other devices so those patches will only be used on the pixel/2's that need them, old v4a install has been fixed for oreo devices :)
[Magisk] cjrivera04:
Just updated Magisk 15.3 and this module and it is no longer working for me. Tried deleting files and reapplying module and nothing. Not even showing up in Magisk to grant super user permission. Htc u11 oreo
[Magisk] Zackptg5:
Can you post logs/go through troubleshooting section in OP?
[Magisk] the_scotsman:
Apparently some people have this working on the Galaxy S8 Oreo beta ROMs with Magisk 15 (15.2 or 15.3).

I tried it just now on a clean flash of THIS ROM, by downloading/installing it through Magisk Manager. But as I have always found on Oreo, it just says Status Abnormal, and I just cannot get it to work.

Has anyone else go it working on the S8 on Oreo? if so, what on earth did you do to get it working?

Would love any assistance you can give :good:
[Magisk] Zackptg5:
hmm, can you post your magisk log, logcat, and /magisk/audmodlib folders?
[Magisk] the_scotsman:
Logs attached.

Also zipped up the requested folder contents and attached it. Wasn't sure if that's what you meant or not?

Appreciate your assistance. I haven't had V4A working on Oreo yet...it's the one thing that's been the let down for me using Oreo, no V4A. it's one of the main reasons I rooted and tripped Knox in the first place. If I can get it working again, I'll be extremely happy. :highfive:
[Magisk] Zackptg5:
So I have things for you to try. The first is to uncomment this line from /magisk/v4a/post-fs-data.sh:

#pixel2set_sepolicy hal_audio_default hal_audio_default process execmem

Just delete the "#pixel2" part.

The other thing is all of the stock effects in your vendor config which I can see you already tried taking care of. I took your original vendor config, added the v4a patches to it, and commented out the sa3d effect. I'm wondering if that'll do the trick because that's the only effect called by output_session_processing music and that's been known to break v4a sometimes. I don't think the other stuff should mess with v4a

At one point, we had aml completely comment out output_session_processing music section but there were some stock effects that didn't break v4a that shouldn't me commented out so now we just comment out music_helper which is what's there in place of sa3d for most devices I've seen so far
[Magisk] the_scotsman:
You bloody legend! That did it :good:

So what does that specific line do? And why is it relevant to specific devices, and commented out for the Pixel2?

Thanks for taking the time to look at this for me, it's very much appreciated :highfive:
[Magisk] purnenduraj234:
In oneplus 5t (oos oreo beta ) alao not working after upgrading to magisk v15.3 and viper v2.9

What should i have to do ..??
[Magisk] erak606:
Agreed, OP5 OOS Oreo Beta 3, was working fine before I upgraded to viper v2.9. Now it doesn't work unless SELinux is disabled, which is a bit annoying.
[Magisk] Zackptg5:
Not really sure to be honest with you. I just look for the avc errors in the logcats, look for any that could be relevant to audio/are located around anything mentioning the audio mod at hand and make the patch.

With v2.9, I have it only uncommented for pixel 2's because that's the only device I've seen so far that uses them. I had it uncommented for all on the v2.8 but some users were having issues with it so I made it pixel 2 only.

Did you replace the vendor config or was the sepolicy patch all you needed? V4A processes sound fine and such?
[Magisk] knnthgngb:
Here it is. Sorry for late reply..
[Magisk] the_scotsman:
All I did was uncomment that line, nothing more.

It seems to be processing sound fine, seems to be doing everything it should be!
[Magisk] DvLAx3l:
Yes also on OOS 5.0.1 the module is broken, the issue should be related to Dirac audio software in OOS Oreo ROMs, with the 2.8 everything was working normally.
[Magisk] TENN3R:
Same on pixel 8.1, magisk 15.3, module 2.9 doesn't work, can someone provide me the 2.8 zip while devs fix this please? I can't find the 2.8 anywhere and I don't have it anymore on my phone
[Magisk] ptblad:
2.9 not working for me either. Oneplus 5, Stock OOS 5.0.1, bluspark #84 and Magisk 15.3.

2.8 works fine however. Luckily I kept the zip. Attached here for anyone that wants to rollback.
[Magisk] TENN3R:
Thank you very much you saved my day :D

Also I think could be useful for other people with same problem :good:
[Magisk] woozie.2007:
THANK YOU for this new version, is only one that works for me, now i can hear radio and poweramp with this amazing sound.
[Magisk] SilvrDrgn:
Awesome! What's the best update procedure from V4A 2.8? Just flash with TWRP over the top of it? (My device is Google Pixel 2 (non-XL) with Oreo 8.1 January update.) Thanks!
[Magisk] Zackptg5:
Or instead of ignoring the troubleshooting section in the op, you could at least look at the changelog, see what changed, and see if you can find the issue with v2.9 so I can fix it in the next release.

A good place to start is by sending logs. Another is the v4a post-fs-data script, try removing the #pixel2 and #pixel from some of the lines and see if it works and let me know

---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------

Yup
[Magisk] Lossyx:
Removed "#pixel2" from

#pixel2set_sepolicy hal_audio_default hal_audio_default process execmem

and everything is working again, thanks!

OnePlus 5T OOS Oero
[Magisk] MrBrady:
I was able to get my Pixel 2 XL and v2.9 of this module to work only if Selinux is set to permissive.

Other than that it works fantastic!

Edit: I'll rereading the OP and pull some logs.
[Magisk] Zackptg5:
Reuploaded v4a - there was a bug in which selinux wasn't set to permissive when oos oreo was detected. It's been fixed now (and on magisk repo too). Thanks to [MENTION=4667597]Didgeridoohan[/MENTION] for pointing it out

---------- Post added at 12:19 ---------- Previous post was at 12:15 ----------

Only log I'll need is a full logcat (make sure you open v4a before taking it). I suspect it's sepolicy related, thanks!
[Magisk] hp13:
What's the step to installing on my pixel?

unlock bootloader, flash magisk to get root and then how do I get viper arise to work?

Thanks
[Magisk] DvLAx3l:
Everything is working now! Thanks for the fix!
[Magisk] Zackptg5:
If you want arise, go to the arise sound systems thread. This is for standalone v4a that can be used with other AML mods like Dolby, am3d, jdsp, and sauron (as well as others). Just flash the zip and you're good to go
[Magisk] chikimonke:
I'm on a 2XL, v2.8 worked fine, now it's not processing on 2.9. I started the log, then started music (GPM) and then launched V4A, checked driver status, exited V4A and stopped the log. Let me know if I can grab another log.
[Magisk] andrizmitnick:
the 2.9 is making my xposed module not being detected on the xposed installer
[Magisk] tonyfreak215:
The new update works great for me!

V20, stock rom, supersu
[Magisk] D-m-x:
Same here, 2.8 works fine on my 2 XL where as 2.9 has an Abnormal Driver Status and isn't processing. Switched back for now.

Another Log here so with 2.9 installed, maybe it will help you track down the Error.
[Magisk] Zackptg5:
Hmm., it looks like the installer didn't detect your devices were pixel 2's. Can you both attach your system/build.props?

In the mean time, the fix is to open magisk/v4a/post-fs-data.sh and remove the "#pixel2" from the one line and reboot
[Magisk] vibrantliker:
Could you expand on that? I've been a V4A user for years on Samsung no problems but now on a Pixel 2 xl. I usually have V4A, dolby, am3d and v4a_xhifi going at the same time.

Just want to be careful as the phone has no backups to rely on yet.
[Magisk] Zackptg5:
You said ARISE v4a in your previous post so I thought you meant the v4a from arise sound system. If you have no reliable backups, I'd use magisk and true magisk modules only since removing them is as easy as just deleting the mod folder or magisk img completely. At the moment arise is not a true magisk module in that it still installs everything to system so if something went haywire, you'd have to dirty flash you rom to fix it.

This thread is for AML v4a. To see what AML is/what it does, check out this thread here: https://xdaforums.com/android/software/module-audio-modification-library-t3579612

Long story short, either use arise, or the various aml mods posted in the thread I just linked. There's an aml mod for all of the mods you have listed except v4a_xhifi
[Magisk] chikimonke:
Here you go.
[Magisk] Zackptg5:
Hmm, can you post the /magisk/v4a/post-fs-data.sh contents? Thanks
[Magisk] ppelao3k:
where can i get "v4afx-v2.8.zip" please
[Magisk] Lossyx:
https://xdaforums.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/post75182770

?
[Magisk] chikimonke:
Here ya go
[Magisk] vibrantliker:
So am I flashing this or looking for it in Magisk?
[Magisk] Zackptg5:
This is too weird. It looks like the installer didn't detect that your device was a pixel 2 when it should have based on your build.prop. Can you flash this and send me the recovery log immediately after? I added a few debugging lines so I can try to see what's happening
[Magisk] Zackptg5:
You can just flash this after magisk is installed (or get it from magisk manager, doesn't matter). At the moment though, it looks like there's an issue with device_check function so after booting, you'll need to navigate to /magisk/v4a/post-fs-data.sh and remove the "#pixel2" from in front of the 1 line that has it and then reboot
[Magisk] Bartws95:
I've got the same issue with my Pixel 2XL. 2.8 worked fine and 2.9 keeps prompting me to install the driver. Changed the line in post-fs-data.sh and it still does the same. Let me know if I can provide any logs
[Magisk] chikimonke:
Recovery Log. The first flash uninstalled it and then I flashed it again.
[Magisk] Bartws95:
Is there still a link to 2.8 somewhere? Would like to see if that still works. Edit: page 171.
[Magisk] Zackptg5:
Well that was infuriating, it was the except same typo with the oos oreo stuff earlier today. I just reuploaded a fixed version to the op and magisk repo. Sorry!
[Magisk] ptblad:
Re-installed 2.9 from Magisk repo and now everything is working from OOS oreo (5.0.1 on OP5). Thanks for the update fix! And sry for not providing logs in the first place.
[Magisk] Zackptg5:
No problem, there's troubleshooting section in the OP that describes what logs to get and some troubleshooting steps you can do on your own as well :)
[Magisk] Aguys:
Sir, I just updated magisk to 15.3 and viper stop working, it says driver need reinstalled. Was working fine on magisk 15.2. Here the logs, hope it help (I noticed error about kernel or something)...

I'm on Los 15.1 (oreo 8.1)
[Magisk] vibrantliker:
Which of your Magisk dolby mods should work on 8.1 I tried the classic version and it didn't.

Also your AMD mod just gives me a black screen.

Any ideas?
[Magisk] chikimonke:
All good now, thanks!
[Magisk] kojak1989:
Processing dont work any ideas why?
[Magisk] rizkiliory89:
Sir, I just installed the newest module, but after reboot, I can't find V4A on app drawer. Is there anything wrong with the installation or is there something missing? Thanks
[Magisk] tinOFbeer:
Have you read the troubleshooting section in the first post? searching does not hurt either

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Magisk] SilvrDrgn:
Just flashed V4X v2.9 over v2.8 on my Pixel 2 (non-XL). Works fine! Thanks!
[Magisk] Neur0Nerd:
Tried installing this but when I open the app it gives me the Reinstalling driver message followed by the I/O error. (tried uninstalling Magisk and Viper and reinstalling too, always getting the same error
[Magisk] woozie.2007:
Hello, after each reboot v4a must be opened to work, otherwise it haven't any effect. After i opened once, it works verry well until reboot. Can I do something to start working itself? I mean without my intervention. Thank you