yashsingh1/xdaforums huggingface dataset:
[Magisk] jwds1978:
Yes, I'm using the audio modules below…

Audio Compatibility Patch v1.1

Audio Modification Library v1.5.3

ViPER4AndroidFX v1.5.8-test2

I just noticed that AML has been updated to v1.5.4, so will upgrade it now.
[Magisk] Zackptg5:
Just edited my last post. Updated material v4a. No updated apk yet, Team_Dewitt still has a couple more things to do

---------- Post added at 13:20 ---------- Previous post was at 12:35 ----------

New material v4a dropped, updated material zip with new apk (v2.6.0.1)

Note that when switching profiles or whatever, you will need to toggle the convolver on/off if you use one (it's being worked on)

---------- Post added at 13:23 ---------- Previous post was at 13:20 ----------

Ya, dropped new aml and updated v4a, do they fix the issues you were having?
[Magisk] yung40oz84:
Everything is working as expected for me with the latest updates. AML 1.5.4, Material Viper 1.1, Sauron, and Ice Sound 2.6. All errors and issues gone, no driver install popup on open Viper. Thanks bud. OnePlus 5T, DU rom.
[Magisk] Zackptg5:
Finally got it! Thanks for the report :)
[Magisk] yung40oz84:
No prob bud, thanks for dedicating time to fix.
[Magisk] jwds1978:
Initially, I was able to boot into the OS without it immediately rebooting to Recovery. However, upon opening the ViPER4AndroidFX app though, it continuously FCed again — ultimately, rebooting itself to Recovery as before. The only way out of the recovery-loop was to disable the ViPER4AndroidFX module via the recovery-based Magisk Manager. :(
[Magisk] Trupen:
Not working here same problem FC 1.5.8
[Magisk] Zackptg5:
Can you post your v4a folder?

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

Can you post your v4a folder?
[Magisk] jwds1978:
I've since reverted to v1.5.5 again. However, I'd made the attachments while v1.5.8 was installed though.
[Magisk] Zackptg5:
Wait, so latest aml works for you but v4a doesn't? That makes sense since you don't have an output_session_process section at all which is what these builds were aimed for. Can you post you v4a and aml folder with v4a v1.5.5 so I can see the difference? It must be something else.

Only the /sbin/.core/img/v4a and /sbin/.core/img/aml folders are needed for this
[Magisk] Mithias:
I'm getting the same. V4A FCs until I disable and remove the module but AML (with just Sauron also installed) works great.

Has anyone got a DL of the 1.5.5 version? That worked awesome and I can then do a comparison to add to diagnosis
[Magisk] Badger50:
Here ya go :good:

https://drive.google.com/file/d/1FyKVw8j4aw3Z38JnilCaRX99viKWxfAe/view?usp=drivesdk
[Magisk] Zackptg5:
It's in download link on the op. Just go to the Old Builds folder
[Magisk] jwds1978:
Yes, AML v1.5.4 and V4AFX v1.5.5 are working.
[Magisk] Mithias:
Got it. What dyu need? Just contents of folders? Might be tomorrow I get it uploaded but happy to help!
[Magisk] Zackptg5:
So the folders are identical so either a permission isn't being set right (which it can't be cause I changed nothing in that regards between versions) or it's something else like dalvik cache. I noticed that you had the material v4a installed before and now it's switching to regular v4a. Can you try wiping your dalvik cache and then flashing v1.5.8 v4a? I'm a little confused because I have a section in there to remove dalvik cache for V4A but maybe it's named something different
[Magisk] dvishalkhatri:
bro latest version of aml and viper4android with dolby, audio is not getting processed .... I don't know what type of file u need... If u need i can post that.... Pls help
[Magisk] jwds1978:
No change…

Uncheck V4AFX via MM.

Delete V4AFX via MM.

Restart to System.

Restart to Recovery.

Wipe "Dalvik / ART Cache".

Reboot to System.

Install V4AFX via MM.

Restart to System.

Enable all permissions for V4AFX via OS settings.

Launch V4AFX.

V4AFX constantly FC.

Restart to Recovery.

Disable V4AFX via recovery-based MM.

Reboot to System.
[Magisk] Zackptg5:
Hmm. Could you get a logcat via adb while it's crashing? adb logcat -d > log.log

Maybe if I can see what's causing the crash, I can get a better idea as to what's going on. I don't have any issues with any of my devices or else I would have fixed it already :/
[Magisk] dvishalkhatri:
Bro do i need to provide log ? After installing the latest version of aml and Dolby .... [MENTION=6037748]Zackptg5[/MENTION]
[Magisk] Zackptg5:
Are you using dolby atmos oreo? If so, that doesn't always play nicely with v4a on some devices. Otherwise, can you post the full logcat like in my last post, the v4a folder, and the aml folder (zips of them). Thanks!
[Magisk] dvishalkhatri:
Yeah sure... Here are the zip files
[Magisk] Zackptg5:
Has v4a ever worked with Dolby Atmos Oreo for you? Everything looks fine in those folders
[Magisk] dvishalkhatri:
yeah it was working on v 1.5.7 ... [MENTION=6037748]Zackptg5[/MENTION]
[Magisk] Trupen:
[MENTION=6037748]Zackptg5[/MENTION] till aml 1.5.1 and viper FX 1.5.5 both were working fine with Dolby

but your latest update of 8 April both viper and aml are creating problem
[Magisk] Zackptg5:
Well the only difference between 1.5.7 and 1.5.8 is that 1.5.7 had a bug in the removal of effects from conf files but since your vendor audio_effects is an xml file, the install for you is identical. Have you tried toggling master power on/off in v4a? It can't hurt to remove all audio mods and reinstall them

---------- Post added at 16:20 ---------- Previous post was at 16:19 ----------

What kinds of problems? Have you gone through the troubleshooting section? AML should be good to go and I'm still trying to see where the issue is with v4a v1.5.8 as installs I've seen so far all look good
[Magisk] dvishalkhatri:
well after installing the v4a materialized.zip file and aml .. now it is working fine ... thanks... don't know why it was not processing the files.... anyway got the solution...
[Magisk] pehlm:
Hi, have the FC problem with Viper for the new 1.5.7-1.5.8 versions. Installing them leads to V4A frequent crasches, it isn't possible to use the device. Sending a matlog. Are on an Athene device with Omnirom 8.1, enforcing selinux. Tried to clear dalvik cache but no change. 1.5.5 works without problems. Thanks for your work!
[Magisk] Zackptg5:
You used material app before right? The interesting thing with this log is that it says unable to start audlabs service (the v4a 2.5 app) but then says that it's scheduling restart of the pittvandewitt service (which is the v4a material app). So there still must be some remnants of the material app that's causing issues. The question is where. The only location I know for certain is still left is dalvik-cache but that's been wiped. All of my devices switched over no problem so I can't really troubleshoot this on my end but can you search your device for anything called "com.pittvandewitt.viperfx" and post the results of the search? You may also need to try parts of that like just pittvandewitt or viperfx.
[Magisk] pehlm:
Yes I was using material app. And no I haven't any remnants of such files in root folders. I did a search. I have then dirty flashed my ROM (Omni), cleared dalvik and cache and again trying to install 1.5.8, with no luck. With Omni (official) we are encouraged to dirty flash the weekly upgrades, through delta updater. It is possible that this isn't going to work unless I clean flash my device. But I'm not going to do that now, haven't time. So I'm going to use 1.5.5 for now. But thanks again!
[Magisk] Zackptg5:
So quick update everyone. I managed to recreate the issue. It doesn't happen on my nougat device but does on my oreo one. It seems the problem occurs when a user was using the material v4a and switch to a different one. Since they have semi-different package names, android is still search for the material one and so v4a crashes. A remedy for now is to uninstall the old material v4a and reboot. Once booted with no v4a installed, then flash v1.5.8 and you should be good to go. I'm looking into a way of coaxing package manager to clear data during the initial boot without the need for this reboot
[Magisk] jwds1978:
Searching for "viperfx", with v1.5.5 installed, I get the attached results. Later, after charging my phone, I'll upgrade to v1.5.8 again, and repeat the same search.
[Magisk] Nitz327:
So no more material skin? That makes me sad just a little. Functionality is way more important tho, obviously.
[Magisk] jwds1978:
Are you meaning to remove ViPER4AndroidFX via the package manager, leaving the Magisk Module installed, and then update the module via Magisk Manager after rebooting? Because if you're meaning to just remove the v1.5.5 module, reboot, and then install the v1.5.8 module, I've done that as per my previous post.
[Magisk] reference2myself:
I can't get it to work with anything but the material theme as well. No amount of uninstalls and reboots will fix it for me.
[Magisk] Zackptg5:
I meant completely remove v4a, reboot. Let system settle (it'll destroy anything left from removed v4a). Then install new one
[Magisk] reference2myself:
Ya I tried that. New one will still force close endlessly as soon as i try to open it.
[Magisk] Zackptg5:
Well you could also try

pm clear com.pittvandewitt.viperfx

Once booted via adb shell

But regardless, the problem is that there are remnants left over because it wasn't uninstalled normally (viper is designed to be a data app so this isn't too surprising).

V4A v1.6 is live! I merged the new material build back into the main apk so if you're on old material build, you can just use this one and avoid this problem altogether
[Magisk] jwds1978:
[MENTION=6037748]Zackptg5[/MENTION] The ViPER4AndroidFX app — v1.6 (2.6.0.1) — is as attached and still FC.
[Magisk] Zackptg5:
Okay, so something is messed up from the old app. Try this:

Install the 1.5.x version that worked with material v4a. Then move the v4a app to your sdcard. Reboot, install it as a regular data app. Uninstall the v4a magisk mod. Go to app settings, clear all app data for v4a, then uninstall the app from there. Reboot into recovery and wipe cache/dalvik cache. Then reboot into system and finally try the new one. Hopefully that'll wipe out whatever remnants are left that are causing issues
[Magisk] jwds1978:
Unfortunately, after doing all of that, it's no different after installing ViPER4AndroidFX v1.6 (2.6.0.1). ?
[Magisk] Hakkinen3K:
Hello, last update not processing YouTube like older version.
[Magisk] Zackptg5:
Read through the OP troubleshooting section, it explains how to fix this

---------- Post added at 04:11 AM ---------- Previous post was at 04:10 AM ----------

Geez, other than a clean flash I don't know what to tell you the :/
[Magisk] pleasetouchmenot:
Latest update of v4a is not working for me (2.6.0.1). I can't get to install the drivers even though i selected the 2 selections (new material and original), drivers isn't installed after it prompts the driver was installed successfully, but after reboot it the same, drivers are not installed and asking for installation. The last working for me is the v1.5.7. My phone is Samsung S7 Edge (ERCB Oreo). Any help? Looks like the last recent updates of the module messed up a bit.
[Magisk] agplugged:
[MENTION=6037748]Zackptg5[/MENTION]

Cleaned app cache, cleared delvik and cache from recovery, then installed 1.6 material with 2.5.0.4. Finished flashing without problem. This was the end result - app didn't install, instead I get these (attached screenshots).

Edit: the screenshot of the app drawer is supposed to show the icon on the bottom right, which writes "#ff80..."
[Magisk] KorokHidup:
Same here
[Magisk] Sk.akram:
Hi.. Anyone tried on nitrogen os.. Thanks in advance..
[Magisk] :
I have the same problem. I will continue to use version 1.5.5.

Device: OnePlus 5

Rom: OOS 5.0.4

Mods: RenderZenith Kernel, Magisk v16.3
[Magisk] pehlm:
Yes the last working version on Oreo (my ROM are Omnirom 8.1 official) is 1.5.5, which indeed is working like a charm. I think we must clean flashing our ROMs again before using 1.5.7-1.6. But I haven't tried that, I haven't that time now sadly :crying: But maybe @Zackptq5 have some other solutions. :good:
[Magisk] Hawkeye007:
I'm having trouble finding the magisk directory,going to system (root) using fx, there is a magisk folder but it doesn't have a .core folder inside of it. If somebody could please elaborate the steps, I'd really appreciate it. Thanks!

Redmi Note 4X, ViperOS 2.0, Stock Kernel, Magisk v13, Using alongside Dolby Atmos A7000 (before installing it, v4a seemed to work okay)
[Magisk] Didgeridoohan:
You have to enable viewing hidden folders in your file explorer. The period are the start of the folder name means it's a hidden folder...
[Magisk] Hawkeye007:
That was so silly of me. Thanks a ton mate! Will see how it goes :D
[Magisk] Gilg@mesh:
anyone got this processing with youtube? tried with Universal deep_buffer Remove but still no luck.
[Magisk] ahrion:
Yeah I mean it should work with YouTube. Have you tried other streaming apps?
[Magisk] Gilg@mesh:
no I only use PowerAMP and YouTube.
[Magisk] ahrion:
Poweramp has done dynamic volume bull****. Turn those EQ settings off because they interfere with audio equalizers.
[Magisk] Gilg@mesh:
sorry but PowerAMP works great with this only YouTube not working.
[Magisk] Sytis:
In my case it works without problems with YouTube an all other audio creating Apps. I use a OnePlus 3 with LineageOS and Magisk v13. Only problem is that Viper only runs in SE-permissive mode in my case.
[Magisk] EncryptedCurse:
How are you supposed to access the .core directory?
[Magisk] LazerL0rd:
View hidden files.

Or magisk mount in TWRP and use file manager from there.
[Magisk] Epikarus:
Hi. Thanks for this tip!

I've run the script and its working now but when i use my file explorer to place the script in the /magisk/.core/post-fs-data.d folder it kinda breaks magisk and i have to uninstall and reinstall magisk. What happens is my file explorer is no longer allowed root access after rebooting. What is the method you are using to place the script in the folder?
[Magisk] Didgeridoohan:
That should be a perfectly valid way of placing the script in the proper place. Sounds more like the script is causing issues... Use TWRP to get the Magisk log from /cache and post it (as an attachment).
[Magisk] gil80:
hi guys,

I have the latest Magisk Beta build 54e6a79 on my OnePlus One 6.0.1.

I can't get Viper4Android to work.

I keep getting Abnormal status and I have tried every goddamn possible solution I could find. I have Audio Modification Library v1.4 installed via Magisk Module manager.

Tried ARISE with V4A and it's not working. Viper4Android 2.5.0.5 used to work flawlessly with Magisk12.

Can someone please help out?

https://drive.google.com/file/d/0B-dutTOXysRrTVBNc1ppNlZ6WHM/view?usp=drivesdk

thanks
[Magisk] Didgeridoohan:
In your screenshot the audmodlib script doesn't have the correct permissions (755) and can't be executed. Try changing that...
[Magisk] gil80:
Magisk folder is not visible in twrp even is system is mounted.

I cannot chmod 755 in recovery. I have to use file manager, and AFAIK 755 is rwxr-xr-x
[Magisk] Nemuritor01:
Found a fix to get Magisk viper processing with Spotify and YouTube on my Oneplus 3t.

Uninstalled Magisk

installed divine beats 9 in twrp

Immediately removed divine (remover zip file)

Flashed Magisk again.

Flashed viper4android Magisk 1.4

Viper is processing with all streaming apps for me.

I don't know, if this method has some bad influence on this mod?

Perhaps Ahrion can share more details.
[Magisk] Didgeridoohan:
If you're gonna do it in TWRP you need to first flash the Mount Magisk script.

Edit: Yes, you're correct about 755. That's the permissions it needs...
[Magisk] gil80:
Well, so even with this script set to 755, V4A is not working
[Magisk] Didgeridoohan:
Well, at least we're ruling out suspects... :good:

Have you checked the scripts in service.d as well, to make sure they're set to the correct permissions?
[Magisk] xanthrax:
Members !

please refrain from polluting this awesome thread with lucky patcher nonsense talks

This app has no place to be discussed nor to be linked on XDA as per Forum Rules

XDA and me personally have 0 tolerance on warez so anything related to apps which can easily allow the users to bypass a paid feature of an application , be it links , talks, will be taken down along with an action against so please check your inbox if you can`t refrain from talking / posting warez.

Thanks for understanding

Dan - forum moderator

thread cleaned
[Magisk] D-m-x:
Just to have one positive Post here, I have no Problems with 1.6 nor did I had with the Versions before. I had the Material installed, when it got removed the older and now Material again. Everything opening and processing fine, just had to setup my Profile again because the Conversion didn't work in the new App. Thanks!

Using a Pixel 2 XL on Stock Rom.
[Magisk] agplugged:
Rooted? Used the Magisk module? How did you flash it? Did you clean/delete/mod anything before you did?
[Magisk] D-m-x:
Yes, I'm rooted with Magisk, didn't mention that because I thought this was implied here^^

I just updated it through the Magisk Manager Download Section, from 1.5.5 to 1.5.6 then 1.5.7 to 1.5.8 and finally 1.6. Always when they got released not because I had planned it. Didn't clean or delete anything, nor Reboot in beetween the Update.
[Magisk] Trupen:
Strange we are also doing same steps but not working here
[Magisk] rippledrums:
Same issue on my Oneplus 3T running Nitrogen OS with Magisk 16.3.

Did a clean flash 2 days ago.

Had to revert to 1.5.5 also to have V4A working again.
[Magisk] woozie.2007:
i updated now and nothing works, without problems before, but problems now....
[Magisk] D-m-x:
Yeah, strange indeed, maybe Device dependent. Only thing I noticed just right now is Viper using quite a lot of Battery. Need to check that some more over the Day.

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Magisk] woozie.2007:
please can you share the 1.5.5 for me? i can't find it. Thanks
[Magisk] rippledrums:
There is a Download link in the OP, enter the folder Old Builds and it's there.
[Magisk] woozie.2007:
i found it thank you
[Magisk] Zgadnijcie:
New version 1.6 forces me to uninstall Lucky Patcher.

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka
[Magisk] kopitalk:
https://xdaforums.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/post76173589
[Magisk] rippledrums:
Again?

If you read some posts back:

Forum Rules

Lucky Patcher and other piracy software is forbidden on XDA.

Please don't post about it.

EDIT: oops ninja'd by [MENTION=4476875]kopitalk[/MENTION] :p
[Magisk] VK'ed:
Why am I getting this threat message on play store?

"Google play protect detected a harmful app

Viper4Android fx

This app can permanently damage your device or cost you money"

Also my hdfc bank app refuses to load because i have "malware" on my device.

Please help.

------------------------------------------------

Btw i am a new user of v4a and also an instant fan! V4a gave my ears their 1st orgasm [emoji23] [emoji7]
[Magisk] D-m-x:
That's because it isn't recognized by Play Protect. It's a false positive Message.

Btw. you guys were right, despite everything working on 1.6 for me I decided to revert back due to the Battery Drain of the new Material App. I noticed the Processing seems better on 1.5.5 with less distortion etc.

I noticed because I listened to Music with 1.6 and right after reverting again on 1.5.5. The Driver Status sometimes went to not Processing when the Sections currently playing in the Song didn't have Bass but rather just spoken Text.
[Magisk] VK'ed:
Is there a way to prevent play store from detecting it. I really need to use my banking apps
[Magisk] Badger50:
The material app version of V4A triggers google play protect because it isn't recognized. Either use the original app version, disable play protect, or just ignore it. Can't answer the banking app since I don't use them.
[Magisk] rippledrums:
[MENTION=6037748]Zackptg5[/MENTION],

Tried again with the steps below but same issue:

1 - Delete V4A app data

2 - Remove V4A folder from sdcard root

3 - Uninstall in Magisk

4 - Reboot

5 - Delete leftover dex files with SDMaid's Corpse Finder

6 - Reinstall in Magisk

7 - Reboot

Still the same...

However, this time while reinstalling I noticed that the xml files being inflated in the script have the word permissions misspelled as you can see in the attached screenshot. Could that be the problem?
[Magisk] prathu30:
Nvm pls ignore
[Magisk] rippledrums:
Well I'll be damned...

Went to "/sbin/.core/img/ViPER4AndroidFX/system/etc/permissions" and renamed the xml file to the correct spelling and rebooted but still no dice...

After that, I went to XDA Labs and updated the V4A app from there and now it's showing correctly in the app drawer and processing.

Maybe something wrong during the apk installation or mounting?

Also, the version available in XDA Labs is 2.6.0.2 and your script has 2.6.0.1.

PS: To make it process in all apps I had to remove it from Android's battery optimization in the system Settings.
[Magisk] Zackptg5:
Oh dang, I totally missed that. If you're not using the original 2.5 app, can you delete that and see what happens? Also, I'll update it with new material apk

Updated v4a to v1.6.1 with new material apk and fixes to the permission file names
[Magisk] rippledrums:
Removed the xml file from the Magisk image folder like you said and it's working without it.

Only thing I noticed is that disabling and re-enabling V4A is needed on first boot, but I guess that's a known issue.

Also couldn't find the audio_effects.conf file (as per the Troubleshooting section of the OP) in /system/vendor, only in /system/etc, but that's probably device/ROM dependant.
[Magisk] Zackptg5:
V4a will pull in any audio_effects files on your device so if you have none in vendor, that means the devs never put on in the rom (not sure why they'd do that but oh well)
[Magisk] rippledrums:
Well, updated to 1.6.1 but the issue returned. App shows a hashtagged name and FCs.

Went to XDA Labs again and updated the app from there and when installing I noticed the versions didn't match.

Screenshot attached.

Could your script still be installing 2.5.0.5? It's really weird.
[Magisk] Zackptg5:
I checked, it definitely isn't. It worked fine on my op5t. I'm wondering if it's because of where the app is installed. Maybe it behaves better as a data app?
[Magisk] rippledrums:
Yeah, you might be right.

I think I read somewhere that it's supposed to be a data app and that's also probably why it has to be removed from battery optimization so it doesn't get closed by the system.
[Magisk] sushuguru:
Try the 1.6 module and install the material version, the new material V4A v2.6 does not have SELinux switch included and should pass Play Protection.
[Magisk] Vatsal157:
There's strange issue on my Redmi Note 4 running official RR v.6.0.0 (Oreo 8.1 Treble version) rom. Everything looks fine when I'm not playing music but when I start playing music my V4A drivers stop processing. Whenever I try to tweak my sound settings it has no effect at all. Attaching screenshots for the same. Also attaching logcat for the same. Please help
[Magisk] franz:
[MENTION=8337960]Vatsal157[/MENTION] I see you're using BlackPlayer, have you set it up to use the stock equalizer instead of its own? If not, goto settings, audio, equaliser and select stock, then check to see if it works. If you've already done that, then check if your selinux is set to permissive, i think v4a doesn't work with enforcing selinux.
[Magisk] Vatsal157:
[MENTION=6848241]franz[/MENTION] I'm using stock equaliser and my selinux is permissive.
[Magisk] jandia7381:
Tried v1.6.1 still fc and it still name by hashtag. Back to v1.5.7