yashsingh1/xdaforums huggingface dataset:
[Magisk] Gergo659:
Hi!

I'm using batman rom 1.5 with s8 plus, with Stock Sound . V4A does not processing the sound. I have deleted soundalive and adaptsound. Installed with magisk 15, can someone please help how to enable processing? Or how and where to write the Audio conf file. I can send additional Info if needed. Thank you in advance
[Magisk] Sytis:
I can confirm the same behavior (same setup), had to go back to 2.5
[Magisk] CarlosPinheiroT:
Not processing for me
[Magisk] fahric74:
Install V4,after install Atmos, after that nothing works!

Installed Magisk 15 and manager 5.5.1
[Magisk] anhnambroz:
Still NO processing. Magisk 15, v4afx-2.6, udbr-3.6 :(
[Magisk] Jerry SQ:
LG V20 with stock rom, after i installed the module with Magisk 15.0 and Magisk manager 5.5.1, my entire magisk modules is gone. Uninstalled Viper module and they came back. Weird
[Magisk] ojedee:
Share your best settings please..
[Magisk] Zackptg5:
Okay everyone, so a quick heads up, without useful bug reporting, I can't help you. So if you say something like "I flashed v2.6 and now I get a bootloop" or "I installed latest v4a and now nothing works", I can't help you cause I can't read minds or magically see what's wrong with a device.

LOGS people :)

Logs of interest are: twrp recovery log (in twrp, Advanced -> Copy Log) - do this immediately after flashing mod, magisk log - obtained in magisk manager, full logcat - lots of ways to get this

Anyways, [MENTION=4684089]GR0S[/MENTION] report gave a strong hint as to what the problem might be. My only oreo device to test on is my bullhead which has a separate vendor partition and the lib path stuff works fine on it and on all of my devices on nougat and earlier. However, I noticed that I didn't have it set properly for oreo devices which don't have a separate vendor partition, not sure how long that's been there but it might be why some other mods weren't working for people since 2.4 (I've been seeing these reports in the dolby thread but once again, without proper logs or troubleshooting :/). So this quick update should fix all of those issues people were having.

So 2.7 is now live
[Magisk] mcaptur:
2.7 now processing on oreo 8.1 and magisk 15 :)
[Magisk] henk717:
Having difficulties on the PureFusion ROM which by default ships with AudioFX.

AudioFX is still functional when enabled but Viper refuses to work even when i toggle it off even though it says its processing fine.

Is there a way to disable AudioFX completely and if that requires manual file work can it be included as an option? (Since i assume many people with Cyanogenmod based roms will have this issue).

Extra information:

- I can't get Viper to work trough any sound mod installer with always this same result.

- The rom is set to permissive by default.

- The rom ships with MusicFX by default which they name AudioFX but even if the app is removed Viper is not creating any auditory difference.

- Viper4Audio claims to be processing fine.

- This rom is based on Android Oreo.
[Magisk] CarlosPinheiroT:
Does not work with Spotify, even with Universal deep_buffer Remover installed
[Magisk] mcaptur:
2.7 with magisk 15 works fine here with spotify.. (2.6 did not have any effect)
[Magisk] CarlosPinheiroT:
It does not work for me! I also noticed that SELinux is now permissive, before it was enforcing
[Magisk] Sreekantt:
v2.5 and magisk 14.5

on the first boot- it worked perfectly(both atmos and viper)

when i restarted- stopped working(it doesn't apply any effect)

on another reboot- viper is asking me to install driver- atmos crashing

what may be the reason ??
[Magisk] D-m-x:
And yet no one cares. The devs said it clearly, without logs no one will help.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] tinuz97:
2.7 with magisk V15, Oneplus 5 with the official Android oreo. Working great, thank you :highfive:
[Magisk] Jerry SQ:
LG V20, Magisk 15.0 with 5.5.1 magisk manager. Installed Viper from 2.7 version, all others module gone. Below is my Install log and magisk log. Thank you
[Magisk] Mar-cel:
Thanks [MENTION=6037748]Zackptg5[/MENTION] v2.7 works perfect on my OP5 with oreo :good:
[Magisk] chudy_85:
New version 2.7 work correctly at last on my P9 with magisk v15.0

Thanks

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] Sreekantt:
tried 2.7 in magisk 15.0 combined with atmos 3.7

neither viper nor atmos apps show in appdrawer

if i extract manually and install viper app- it asks me to install driver- installation succeeds and i reboot- it again asks me to install driver(i even tried with selinux permissive)

Update- even if i uninstall everything and reinstall only viper- it asks me to install driver again and again

Update 2 - Found the culprit, It was ART optimization module which was simply making viper and Dolby Atmos disappear as soon as it is installed- without ART module- everything is perfect.

---------- Post added at 02:00 ---------- Previous post was at 01:58 ----------

weird - are you using this mod beside dolby atmos- i couldn't get it to work on emui

apps don't show up in magisk 15 and v2.7
[Magisk] Zackptg5:
Hmm, log looks okay. Can you send me the audmodlib and v4a folders from your magisk img?

---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------

Remove all v4a stuff, uninstall and reinstall magisk 15, then flash v4a and post recovery log. Then can you send me your audmodlib and v4a folders from your magisk img? Thanks
[Magisk] chudy_85:
I try use dolby atoms but i have fc after wire screen. I try all version viper v2.0. - v2.7 and only working correctly it's v2.0 and v2.7

Before when I try I don't have viper.app and when I install I need install drivers to correctly work mod.

Now I have install normal that same as v2.0

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] Dhdeanha:
Not processing

Hi all,

Recently installed a new ROM and V4A is not working. On Nougat Magisk 15.0.

Problem is that V4A is not processing when I have spotify play8ng music. I have deep buffer module and done a fresh install of V4A.

Logs attached.
[Magisk] CarlosPinheiroT:
It still does not work for me!

No process when playing back with Spotify
[Magisk] GR0S:
Here is it.
[Magisk] Zackptg5:
Logs look fine. If v4a works for non streaming apps like regular media players but not for streaming apps like spotify, then that's more of a system problem so you'll be more likely to find an answer on the deep buffer removal thread. If Spotify still doesn't work with deep buffer remover, then you'll need to research what's the issue (I use Google play music so I can't help you much there other than make sure everything installed properly)
[Magisk] Sreekantt:
It was ART optimization module causing the issue which is simply removing drivers of viper and atmos...if we install Viper and atmos over ART module---drivers don't get installed

Removing ART module completely fixed the issue. What may be causing the problem - because ART module was helping me in performance a lot-
[Magisk] Zackptg5:
Change the path to the v4a lib from /system/vendor to /vendor in the system and vendor audio effects.cfgs in audmodlib and reboot and see if it works

---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------

That would do it, I've seen that cause issues before. You had it on one of the speedier settings right? You might be able to reinstall it after v4a and Atmos are installed
[Magisk] GR0S:
Looks like magisk problem, even my dumb module doesn't work.

However when I push those files to /system in recovery everything works fine.
[Magisk] Dhdeanha:
I downloaded a random mp3 from my drive and it shows no processing when playing.

Edit**

How does one remove ART module?

My googling skills aren't good enough to find it myself

Edit2**

If ART optimization is a Magisk module, I don't have it. I only have Vanced Youtube, V4A, Deep buffer, and audmodlib
[Magisk] Zackptg5:
Do you have a separate vendor partition? That's what your audio cfgs are telling me let the installer didn't detect the symbolic link for some reason
[Magisk] GR0S:
Doesn't help, viper still wants to install driver.
[Magisk] Zackptg5:
Remove all modules other than AML and v4a. Other non AML audio modules like your James one will break things (there's an AML version of Jamesdsp by the way)

---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------

It's another magisk module so if you didn't install it, then it's not there so don't worry about it. Have you tried turning the v4a master power on and off?
[Magisk] kingsven149:
For all it doesn't work, simply try the v2,5
[Magisk] Sreekantt:
yeah, it was on d default speed setting

no- installing ART after flashing Viper and atmos also repeats the same thing- magically make viper/atmos drivers disappear

I should stay away from that module for time being until dev resolves/updates it

Peace
[Magisk] Dhdeanha:
Yes I have, still no progress
[Magisk] cichy.:
still no processing with v2.7, Magisk 15/5.1.1 Android 7.1.1
[Magisk] GR0S:
I believe I don't separate vendor partition. /vendor is linked to /system/vendor.

I started over with clean room and magisk.

Installed viper from magisk manager

Rebooted

Wants driver

Changed /system/vendor to just /vendor in audio configuration

Still wants driver

No other modules installed. All files are here and audio config is correct, yet audio server doesn't load library.

When I install James DSP manually it doesn't crash, but doesn't make any effect in play music. Disabling built in equaliser doesn't help (it was enabled all time)
[Magisk] Zackptg5:
Can you send me a full logcat after opening v4a. It's possible there's an sepolicy not being allowed
[Magisk] JairPaalman:
V4A Not Processing

After some problems with Magisk 15, I've reinstalled my S8's stock firmware and rooted it with Magisk 14. Then, I installed version 2.5 of this module (Which I had Installed before, and which worked). However, for some reason, now V4A won't process audio. Any help?

UPDATE:

Older versions also won't work. I've tried installing version 2.4, but the same thing happened. I've attached the installer log.
[Magisk] baku2313:
I'm getting some msg from play protect scan that is it harmful app.
[Magisk] Badger50:
That's because play protect doesn't recognize the V4A material app. Either...disable play protect, use the standard app, or just ignore it :good:
[Magisk] theduke7:
2.7, it FC's and causes Dirac to FC on OOS latest Oreo beta, the installation goes normally with no issues but after a reboot, i get continuous FC from both until the device reboots itself.
[Magisk] Sytis:
Ok, now I managed to completely **** up my system. (Props at me). I did:

-Completely uninstalled Magisk

-Wipe /system

-Flash ROM

-Flash Magisk 15

-Flash Custom Kernel

-Reboot

So far so good, everything seems to work. Now open up the Manager and install my modules. All went good except Viper: It installed in system mode instead of Magisk mode even though I used the internal shell from the manager. Right after it finished I get a black screen and a constant white LED. Need to hold the power button in order to get the device back to recovery mode. In there I renamed the v4a to uninstall-v4a and flashed it. Know it says it found a Magisk installation and removed the module which wasn't even there. So know while still in recovery I flashed v4a 2.7 again and it now detects Magisk again and installs as a module. After reboot everything show up but the driver says unsupported etc. I grabbed a Magisk log after the reboot as there where no errors whatsoever during TWRP installation. But if I try to upload it here I just get an "Android Failure while uploading"...
[Magisk] whalesplaho:
Im having bootloop with v2.7 too... Flashed but phone stuck on Bootlogo except i remove v4a buh v2.4 working fine.

Xperia Z5 Stock based rom 7.1.1.
[Magisk] Ragnar Eldur:
Noticed that after magisk module version 2.4 it's only working for some apps, not global effect anymore.
[Magisk] CarlosPinheiroT:
Do you have version 2.4?
[Magisk] Didgeridoohan:
Go to GitHub, download the source of your choice, repackage the zip so that all files and folders are in the root of the zip (rather than inside a separate folder, ViPER4Android-FX-X.X) and install manually in the Manager.
[Magisk] mipirakas:
I just updated from magisk 14.5 to 15.0 and i first removed the old modules, flashed magisk 15.0 and then installed viper 2.7. the app shows up and opens but the driver status is abnormal and does not process. This is on my oneplus 5 running android 8.0 stock rom. With magisk 14.5 and module 2.5 everything worked fine.
[Magisk] DorianX:
2.7 not working here...

- OnePlus 5

- OOS 5.0 (Oreo)

- Magisk 15.0

Attached Magisk log and logcat (ViPER4android only) if you need a full logcat just tell me and I'll upload.

Thanks in advance
[Magisk] Ragnar Eldur:
No I updated to the latest, 2.4 was the last properly working one.
[Magisk] QkiZMR:
I installed this module on my Moto G5S Plus and it doesn't work out of box. I tried to investigate why and I found cause. I used V4A for years, on different phones so I know how it works.
[MENTION=5357345]ahrion[/MENTION] you forgot to add few things that are in original Viper4Android zip which is flashed in recovery.

1. Lack of props set in

/system/build.prop

which are critical to work.

2. You didn't turn off deep_buffer in policy files.

What I do to make V4A processing on my phone.

1. I added following lines to

/magisk/ViPER4AndroidFX/system.prop

:

audio.deep_buffer.media=false
tunnel.audiovideo.decode=false
persist.sys.media.use-awesome=1

2. I removed deep_buffer config from following files:

/magisk/audmodlib/system/etc/audio_policy.conf
/magisk/audmodlib/system/vendor/etc/audio_output_policy.conf

I made it by sed command in terminal. I checked what command is used in original install script.

sed -i '/deep_buffer {/,/}/d' /magisk/audmodlib/system/etc/audio_policy.conf
sed -i '/raw {/,/}/d' /magisk/audmodlib/system/etc/audio_policy.conf
sed -i '/deep_buffer {/,/}/d' /magisk/audmodlib/system/vendor/etc/audio_output_policy.conf

After reboot I have working V4A in normal mode.

On other phones path can be different but it should be easy to find analogous files
[Magisk] Zackptg5:
Can you post the magisk/audmodlib folder, a full logcat, and magisk log (from magisk manager)? Oneplus oreo devices have always been problematic

That's because many devices don't need deep_buffer removed and it'll actually break sound for some people. So ubdr remover is a separate module: https://xdaforums.com/apps/magisk/module-universal-deepbuffer-remover-t3577067
[Magisk] DorianX:
Here you go.

By the way this mod was working (2.5 if I'm not wrong) + Magisk 4.5 + OOS OB2
[Magisk] Zackptg5:
Hmm, can you copy what's inside the post-fs-data script from the magisk/v4a folder?
[Magisk] DorianX:
#!/system/bin/sh
SH=${0%/*}
SEINJECT=magiskpolicy
AMLPATH=/sbin/.core/img/audmodlib
MAGISK=true
SYS=/system
VEN=/system/vendor
SOURCE=priv_app
LIBDIR=/system/vendor
MODID=ViPER4AndroidFX
### FILE LOCATIONS ###
CFGS="/system/etc/audio_effects.conf /system/vendor/etc/audio_effects.conf"
CFGSXML=""
POLS="/system/etc/audio_policy.conf /system/vendor/etc/audio_output_policy.conf"
POLSXML="/system/vendor/etc/a2dp_audio_policy_configuration.xml /system/vendor/etc/audio/audio_policy_configuration.xml /system/vendor/etc/audio_policy_configuration.xml /system/vendor/etc/audio_policy_volumes.xml /system/vendor/etc/r_submix_audio_policy_configuration.xml /system/vendor/etc/usb_audio_policy_configuration.xml"
MIXS="/system/vendor/etc/mixer_paths.xml /system/vendor/etc/mixer_paths_dtp.xml /system/vendor/etc/mixer_paths_i2s.xml /system/vendor/etc/mixer_paths_qvr.xml /system/vendor/etc/mixer_paths_skuk.xml /system/vendor/etc/mixer_paths_tasha.xml /system/vendor/etc/mixer_paths_tavil.xml /system/vendor/etc/sound_trigger_mixer_paths.xml /system/vendor/etc/sound_trigger_mixer_paths_wcd9330.xml /system/vendor/etc/sound_trigger_mixer_paths_wcd9340.xml"

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Magisk] atomomega:
As of the latest Magisk and V4A update, the driver is not processing. I flashed the deep buffer remover but made no difference, can I just uninstall the deep buffer remover from magisk manager or do I need to flash the deep buffer restorer?
[Magisk] Nitz327:
It's a silly question I know, but did you try toggling the master power on and off? Sometimes I have to do this after updates or changes before it'll show processing again.
[Magisk] anujyadava:
+1
[Magisk] anujyadava:
I am also facing the same issue on OP5 but it works fine after changing selinux to permissive.
[Magisk] BlueHawk:
I also couldn't get 2.7 working on my setup. I've got a Pixel 2 XL running 8.1. Magisk Manager is 5.5.1 and Magisk is 15.0. Install goes fine for stock 2.5.0.5 but FX Manager crashes after trying to start and continually crashes until the device shuts down after too many crashes. I can't get anything useful out of the system as the crash message just keeps coming up every time I tap on screen. My only option to recover is to boot into TWRP and uninstall the module from there (and remove the associated audio framework module). I can possibly try to get a catlog if you need it now that I've figured out how to recover (Pixel 2 XL is a pain as you can't transfer any files to and from it while in TWRP).
[Magisk] Ragnar Eldur:
I noticed the module stopped working for several apps like YouTube and my Samsung Music Player. The few apps that still got processed by the Viper was MX Player and Instagram but only when browsing posts but not when creating ones. Also when someone calls me while using the MX Player, the effects stopped working and I have to reboot to get it working again.

This started to happen after I updated to version 2.5 and still have not been fixed.

Found a month old backup of my phone with version 2.1 and I rolled back to that one and have no problems with that version.
[Magisk] CarlosPinheiroT:
With sounds of the system works, but with apps is not working for me
[Magisk] DorianX:
Yup that works for now

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Magisk] JairPaalman:
V4A not processing on Magisk 15.1

[MENTION=5357345]ahrion[/MENTION] Since the Magisk 15.1 update, I finally was able to run Magisk 15 on my phone and therefore download the most recent version of this module. Unfortunately, that did not solve my problem from before, namely, V4A does not process in any application. (Tried Samsung music, Youtube, Netflix and MX Player) I'll try to install the Universal Deep Buffer Remover module, and setting SeLinux to permissive. However, I'm a bit worried about the last thing. Wouldn't setting SeLinux to permissive trigger SafetyNet, and is it really necessary, since this module worked fine before without permissive SeLinux?

UPDATE:

Setting SeLinux to permissive (using a Magisk module) causes a bootloop, so that is not a viable option. The deep buffer remover module also had no effect (strangely, /magisk/Udb_Remover seems to be empty, besides a module.prop) and neither had clearing the cache (just to be sure). Two things I did notice: there no longer is a folder for V4A in /sdcard. Also, setting V4A to compatible mode does work somewhat, but the result is very poor. One last thing, I've removed Samsung SoundAlive in order to prevent V4A from exiting. Could this possibly cause my problem?
[Magisk] Zackptg5:
Ubdr and all AML modules store all cfg/pol/mix files in the magisk audmodlib folder so that's where all of the ubdr stuff is.

Any stock eq/sound app like Samsung sound alive can mess with v4a so that could be the cause of your problems.

Selinux set to permissive would break safetynet but magisk hides that
[Magisk] JairPaalman:
I guess removing SoundAlive should fix problems rather than cause them, then. But since I already have removed SoundAlive, that still leaves me with an unsolved problem.

V4A still doesn't process anything, not even system sounds, and I don't know what causes the error or how to solve it. V4A did work before my problems with Magisk 15, but those problems are solved now. I did a stock firmware restore too. Any idea what could be going wrong?
[Magisk] p34rp34r:
This was working great for me for a long time - probably since its inception (with a few hacks here and there). I had a lot of old junk from previous versions of Magisk scattered throughout various folders, so when v15 came out, I took the chance to clean up and start fresh. However, after doing so, V4A no longer processes anything, even Google Play Music. It just says that the driver is installed, enabled, supported, but no processing.

I tried with and without Forced processing and with Compatibility mode turned on. When Compatibility mode is on, GPM will process for a few seconds, then it stops. I don't see any errors in logcat when launching and nothing shows up when it stops processing in Compatibility mode. I've also tried with and without UDBR and with and without manually deleting deep_buffer junk. Previous versions that used to work no longer work (but that might be a Magisk issue?). I don't see errors in the Magisk log or logcat when launching viper. About the only thing I can see is weird (and perhaps I'm barking up the wrong tree here) is that when I try to run the post-fs-data.sh script in the viper4android folder, it gives me 3 errors:

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 this anything? Am I supposed to be able to set SEPolicy after the system is booted? Is there anything else I can provide to get that sweet, sweet, V4A goodness working on my phone again?

Nexus 6

Stock Android 7.1.1 N6F27M (Oct 2017)

Magisk 15
[Magisk] sjamie:
Does anyone have 2.7 working successfully?
[Magisk] Skittles9823:
Yes its possible to do. Also, have you tried using viper to go permissive just to see if that's the issue?

Yes, I do. On magisk 15.1 android 8.1.0
[Magisk] anujyadava:
Yes but with permissive selinux only
[Magisk] mamama07:
Is any way to work just viper on oreo based rom WITHOUT switch SElinux? I mean just stay on enforcing mode.
[Magisk] QkiZMR:
Standard selinux policies that are in this module doesn't work on Oreo?

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] mipirakas:
I think selinux permissive is only needed for oneplus oreo devices. So if you don't have a oneplus device running oreo you should be fine.
[Magisk] QkiZMR:
Leaving selinux in permissive mode is security issue.

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] mipirakas:
Yes i know but currently there is no other way for oneplus devices. It should work in enforcing mode on your moto though if i'm not wrong.
[Magisk] elandroido:
I guess maybe there is some other sound processing, equalizer or similar baked into the Samsung stock ROM which breaks v4a.
[Magisk] JairPaalman:
Nope, I checked. Also, the firmware I'm on now worked before, so that cannot be it.

---------- Post added at 02:15 PM ---------- Previous post was at 02:10 PM ----------

I guess we have the same problem. It seems to be that the module has problems with SeLinux permissions. The problems could be solved by setting SeLinux to permissive, but that's a grave security issue and in my case, it causes a bootloop. I've seen that the dev is working on the SeLinux permissions, though, so I guess we should wait.
[Magisk] QkiZMR:
yes, it works fine on my Moto. Here you have how to debug selinux denies:

https://source.android.com/security/selinux/validate
[Magisk] jj71787:
I get the can't install driver IO error. I tried changing the SElinux and giving access to storage
[Magisk] Zackptg5:
v4a has been updated to v2.8! Just a small bug fix release that fixes issues oos oreo users were having - still sets selinux to permissive for now :(
[Magisk] Rom:
I have not had time to test the sound quality of my phone, i have just see that the drivers is enabled and supported on my RR 7.1.2, but during the module setup, i have see the option selection UI, it's a really nice idea to implement it:good:

I did not think it would have been possible so early, a very good job!