yashsingh1/xdaforums huggingface dataset:
[Magisk] chudy_85:
Here you have

https://mega.nz/#!EMYhjS5b!qvfztssSSjjs74JM2QuEh8bdwg4N4cDqkwDga8G22y8

Thanks to OP and me [emoji16][emoji16][emoji16]
[Magisk] TahirZX:
I am unable to save or load any profile any help?
[Magisk] TahirZX:
Even after multiple tries with 2.0 module and audio mod

I still can't load or save profiles
[Magisk] checksamir:
Hello Arihon,

Can you please advise on the following installation error and any way around to resolve it? Logcat attached for analysis, if at all required.

Thanks in advance.

Samir
[Magisk] lekcin18:
installed and no luck. processing:NO :( magisk 14
[Magisk] Didgeridoohan:
You're installing an unreleased mod, that is a work in progress and that the creator has advised against using (because it's not ready). Expect issues...
[Magisk] nddan44:
No working for redmi note 4x miui 9. Does not receive superuser requests and can't install driver.
[Magisk] emuandco:
It does not need superuser requests and the driver should be there thx to Magisk. If this is not the case, then we have another problem.
[Magisk] antonholmstedt:
1.4 is working for me with magisk 14 after changing selinux from enforcing to permissive.
[Magisk] ahrion:
You're using a beta zip.

These beta zips shouldn't be circulating and if it doesn't work, well that's because it's not a stable release. Anything I've given to folks has been to test certain changes or features among different devices. I cannot stress that enough. You guys are downloading unstable zips. While the version has changed to 2.0 for AML/Unity on the github, it's not stable.

For example, if you download from the github right now, it will cause people to lose sound in earpiece + speaker.

I don't want to have to make my repositories private because of this.
[Magisk] ahrion:
Please delete this link and stop mirroring and sharing unstable git changes. I don't mind you downloading and trying unstable yourself, but don't share it like it's an official release on this forum. You're just causing people confusion and issues.

The new changes update the installer and process dramatically across all devices and it's not finished.

If this happens again I'm making all my repositories private and everyone will just have to wait until releases are final for every version.

Don't ruin it for everyone.
[Magisk] Hellsblade:
Sorry for that and of course I don't expect support from beta/alpha releases, I installed this one which I am sure I did not make myself, because the other ones wouldn't work because for modules to work in magisk 13 plus they need a higher template version. I posted my comment just to give you an idea on how I got my 4va to work while so many people are struggling including myself.
[Magisk] ahrion:
So Magisk 13.5/6 vs Magisk 14 are very different. .core no longer works at all. There had to be several internal changes done to the installer to get everything to work.

The next versions WILL require everyone who has a current version of any AML module installed to uninstall, reboot, and reinstall. This goes for AML + all AML modules.

System should be fine, but with system we will ask users to dirty flash their rom.
[Magisk] Som_esh:
It doesn't work. i am magisk 14 and this causes LOSS in audio playback. Processing is no under driver status when MUSIC is played. Tried selinux permission also but no luck. Helppp

---------- Post added at 06:15 AM ---------- Previous post was at 06:13 AM ----------

Nevermind can you please eta of v4a compatibke with magisk 14.
[Magisk] emuandco:
Noone will ETA anything here. And it's rude to even ask for an ETA at all.

XDA is no playground for ppl who wanna mod their phone to be different to others, but it's a developer platform which tolerates non devs to an extent.
[Magisk] Som_esh:
ETA is just knowing how the progress of your mod is going to comply with system changes So that users don't flash relentlessly the old version suffering from fuc++G brick OR something. If you can take up a work, you have to Keep it updated OR write ABANDONED on their posts So testers like me don't have to waste time. Good Luck.
[Magisk] Didgeridoohan:
If you want to know the progress you read the thread (they're working on it) and you can also see the progress on GitHub (link in the OP).
[Magisk] AhPek00:
FYI its rude to ask for ETA here in XDA. And show some appreciation to the dev. They are doing this for free in their free time, they dont have to report to u about what they are doing. If u really wants to know the progress check the dev's github
[Magisk] TahirZX:
Guys I got v4A 2.0 and aml 2.0 to work on magisk 14.

I know these are test builds and unstable and not official released.

I just wanted to try so I did try a few times and atleast got it to work.

I didn't work just by directly installing.

There are specific steps in which I tried it and it installed and also its working with dolby Atmos module.

I can tell specific steps I used if anyone is interested.

My point here was to just tell that the test build is working good and I highly appreciate what the dev is doing.
[Magisk] emuandco:
ahrion asked the ppl hosting git dumps as test builds to remove em. There is NO support for them and NO support from our side, because we don't want the dev to be forced to close his github for public, because some unofficial test builds taken from there are floating around and ppl want support for them. So you are on your own testing builds the dev told us making more fuzz than working fine right now.
[Magisk] TahirZX:
Ik what the dev asked. I am not asking for any support if my previous post wasn't clear enough. I just wanted to confirm it that it's working for me.

Again my point here was to only confirm that the test build is working fine for me. And I highly appreciate what the dev is doing.
[Magisk] Mr. Clown:
This ^^ so [MENTION=7159186]Som_esh[/MENTION] NO ETA requests..thank you.
[Magisk] ahrion:
The newest builds on Git no longer cause audio processing or speaker sound to be lost.

I don't mind anyone using the Git builds and posting their feedback, if you do provide any issues you have, and what the last commit that was made (so we can see if it was fixed). We always encourage testing and providing feedback rather than early access.
[Magisk] gil80:
so I installed the latest version of Magisk and I thought they would fix this issue with V4A, seems that I still need to manually change .sh files lines and permissions for V4A to work.

Or, is there a more elegant solution by now?
[Magisk] nissan skyline:
Guys ...i have installed V4A in magisk 14.0 but I can't find any V4A app in my app drawer for controls ...need help .. i have Nexus 6 running AOSPA ROM
[Magisk] whalesplaho:
Yhu installed tha one by magisk dev.... Yhu need to install tha app manually to have tha v4a app!
[Magisk] davidisflash:
Any of you can confirm that with this latest package, Usb/Doc tab is processing sound when hooked up to a USB external source? The official Viper apk, Viper arise zip packages, and guitadedhero's mods all don't work for USB with several other users posting the same.
[Magisk] Sytis:
Tested Version 7ca8048 (last commit) on a OP3T running CarbonROM, Magisk 1400 (beta) and blu_spark kernel. Installation went without problems, after a reboot the Viper App was installed as intended. Driver is also working and no errors whatsoever. Tested several effects on Bluetooth, speaker and Headphones (I have USB device sorry) and everything works flawless. Thanks I hope this heads-up helps the devs a bit ;)
[Magisk] ahrion:
Mine wasn't approved last version. I have to resubmit and wait another 2 months for it to be approved in the repo.
[Magisk] whalesplaho:
Wooooopppsssss.... Dahs too long!!!

Really waiting for yur updates brov!
[Magisk] Nemuritor01:
Just a short feedback. Latest version on your GitHub works fine on OP3t with Vertex OS and Magisk 14.

Great job :good:
[Magisk] Shriac:
When I try to install drivers, it says the busybox installation found doesn't work. use stericsons busybox. I tried both YDS busybox and osmOsis busybox.
[Magisk] Didgeridoohan:
Are you sure you're using this module, with the included app? I'm using it without issues and have no separate busybox installed.
[Magisk] Shriac:
Yes I am using v4afx_v1.4.zip file from androifilehost. I am on galaxy s6 nougat and magisk v14
[Magisk] Oliver94:
Got the same error yesterday, after flashing last LOS update
[Magisk] Zackptg5:
If you used this module, drivers are already installed
[Magisk] Shriac:
No. Because when I open the viper app, it asks to install the drivers.
[Magisk] Zackptg5:
Something didn't work with the installer then. If you go to driver status in v4a, it'll probably say status abnormal. It means your audio effects and/or vendor audio effects files weren't properly patched. The new version should fix any weird issues like this (shouldn't be much longer before it's released).

In the mean time, you can open those files and see if the v4a lines are there and add them if needbe
[Magisk] Shriac:
Started fresh with a factory reset. Now the busybox problem is gone and Viper4 is working but only with local media players like poweramp and not working with steaming players like spotify.
[Magisk] Zackptg5:
You'll want to remove deep_buffer. Just flash this: https://xdaforums.com/apps/magisk/module-universal-deepbuffer-remover-t3577067
[Magisk] Shriac:
After flashing Universal deep buffer remover, the driver status was showing abnormal so again had to edit the 2 scripts in .core folder regarding the SEINJECT line and change the permissions to 0755. Still not working on youtube and google play music.
[Magisk] Aijen:
how can download the 2.0 version? im noob using GitHub... :(
[Magisk] yugotprblms:
So my V4A has stopped working. It is stuck on trying to install the driver when I open it up, and it says the status is abnormal.

OP3 Sultan's LOS 7.1.2

Magisk 14 (Maybe this is the problem)

V4A 1.4 from ahrion

Both script fixes done, permissions set to 755

BusyBox installed and working fine

I have removed audiomodlib and v4a multiple times through magisk, rebooted, then reinstalled, and had no success. I feel like I am missing something here.

Thanks
[Magisk] triggeredbot:
V1.4 doesn't work well with Magisk 14. Currently running the GitHub version and it works well ??
[Magisk] yugotprblms:
Can you link me to it? I tried downloading it from his github, but Magisk said it wasn't a magisk module.
[Magisk] triggeredbot:
Because there's a folder in the zip. Extract the files w/o any folders in a zip :p
[Magisk] yugotprblms:
Yep, that's pretty much exactly what I realized after I stopped being dumb and looked at it for a second.

Same issue though, wants me to download the driver.

EDIT:

Removed both, with the masterfx.zip for the 2.0, and the uninstall zip for the 1.4 Rebooted, reinstalled master, rebooted, same issue.

Disabling SELinux through V4A does nothing.

Changing scripts does nothing. I set them back to normal and had that vipersupportfix in there. Still nothing.

Anything else to try before rolling back Magisk, which I am not even sure how to do?
[Magisk] aki_007:
How
[Magisk] TahirZX:
Mounted magisk in recovery and removed every audio mod.

Flashed v4afx 1.4

And then v4afx 2.0 which also installs audio mod library 2.0

And then flashed Dolby Atmos
[Magisk] Rom:
Hello,

i would like to test this mod, so we just to have dl the zip version from github, check the package and build the flashable zip, right ?
[Magisk] Didgeridoohan:
This has got to be the most longed for module update ever!

Clean install on Magisk v14+ working beautifully, straight out of the box!

Awesome work [MENTION=5357345]ahrion[/MENTION] and [MENTION=6037748]Zackptg5[/MENTION].
[Magisk] Rom:
Thanks for your update, i have make tests majors stuffs works good :good:
[Magisk] ahrion:
Atmos coming soon. I haven't updated my repos yet. The Atmos take longer to upload because of sizes.
[Magisk] uri4578:
Hey Ahrion, could you upload back the uninstall files for this module and Universal Deep Buffer remover?
[Magisk] n@vier:
Uninstalled v1.5 and installed the 2.0 works like a charm!

I'll wait the new dolby atmos.

Thanks You Rock!
[Magisk] 24imelqui:
"systemv4afx_v2.0.zip" to install it aas system? [MENTION=5357345]ahrion[/MENTION] . thanks
[Magisk] ahrion:
This is to force system ONLY if Magisk is ALREADY installed. If Magisk is not installed it will default to system install.
[Magisk] ahrion:
No. Why would I do that?
[Magisk] yugotprblms:
So this brand new 2.0 still does the exact same thing for me. V4A tells me to download the driver on opening, and driver status shows 0.0.0.0 for the version and Abnormal for driver status.

Uninstalled AudioModLib and previous V4A from magisk, rebooted, installed this zip through magisk. Still nothing. Not sure where to go from here. Am I just making a dumb mistake?

OP3 Sultan's LOS 7.1.2

Magisk 14
[Magisk] Hellsblade:
Deleted older testversion. Reboot. Checked in magisk, modules gone. Installed the 2.0 version reboot.

Driver is enabled and working on speaker, headset and BT headset.

Have any idea on how to correct the profiles not saving error? )(Old issue for me) not a big thing by the way.

But good to see the 2.0 version of your driver working.

Thanks for the hard work on this.
[Magisk] ahrion:
Install in TWRP because Magisk 14 is bugged.
[Magisk] ahrion:
Install the zip through TWRP and tell me what happens?
[Magisk] yugotprblms:
Should I give this a shot for my issue?

EDIT: Just saw that you told me to try this. Will let you know.

---------- Post added at 09:25 AM ---------- Previous post was at 09:21 AM ----------

No dice, same exact issue.
[Magisk] Rom:
Personally i have successfully install your last zip version, but yesterday i maked a fresh install of Magisk (due to my test on my magisk module project..).

Maybe it could be different on other device i don't know.

About the v14 of Magisk, its really bugged yeah :eek:
[Magisk] Shriac:
I have previous modules such as AML 1.4, Viper 1.4 and universal deep buffer remover. How do I uninstall these and install the new version.
[Magisk] Thomas_BA:
Flashed 2.0 with TWRP and working good so far on my Samsung Galaxy Tab S2 with Lionage 7.1 Nougat. Tested only with Spotify so far.

Excelent work!
[Magisk] yugotprblms:
Well, I got it to work. I just wiped my device and started over, it was being stupid anyway. TWRP was showing the system partition as like 1747572938374893 MB. So, something was off. All is good now. Thanks [MENTION=5357345]ahrion[/MENTION]
[Magisk] ahrion:
I was having issues installing via Magisk but with only v14+. I think Magisk 14 is kind of buggy.
[Magisk] yugotprblms:
Mine actually installed via Magisk just fine. No problems there. But I wouldn't be surprised if it was Magisk, as 1.4 worked on Magisk 13.3 just fine. I think upgrading to 14 is what did it.
[Magisk] Zackptg5:
Easiest is to uninstall and reinstall magisk. Otherwise, just navigate to /magisk, delete the module folders, and delete all scripts in the .core folders and subfolders
[Magisk] puhu:
I just flashed this v2.0 over v1.4 Is there any problem i did like that??

MI 5 cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] Zackptg5:
Yeah, there's been lots of changes between those versions so there's no telling what kind of weird stuff could happen
[Magisk] uri4578:
So I can uninstall the previous versions of them
[Magisk] ahrion:
I see. You can uninstall system by reflashing your rom or just flashing right over it.
[Magisk] puhu:
I uninstalled this module in magisk manager list and i reboot phone checked the list and there is no vfx or audio lib. And İ flashed new version 2.0

This proccess is true?

MI 5 cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] TahirZX:
I fixed it by downloading a profile folder for v4A and now it saves profiles
[Magisk] uri4578:
I actually had the uninstall file previously in my downloads for this module but not UDB remover so I've flashed the uninstallation and removed UDB module in Magisk. Then flashed your latest module and man my phone isn't freezing and rebooting on it's own anymore. Also Viper4android doesn't turn off and back on by itself anymore as well, so thanks a lot!!! Will test for longer but I think it'll be ok. Thanks again for all of your hard work and time!!!
[Magisk] ahrion:
Thank [MENTION=6037748]Zackptg5[/MENTION]. He's put a lot of work and time into it as of late.
[Magisk] Hellsblade:
I deleted the Viper4android directory in TWRP.

And voila it was recreated automaticallyafter reboot, It's saving profiles now. Restored the kernel dir for my favourite IRS files.
[Magisk] 24imelqui:
Thanks. I have magisk installed and I wanted to do a system install for your sound mod.
[Magisk] ahrion:
Last minute changes were made to v4afx_v2.0 among the other modules I haven't uploaded yet. The changelogs were kept the same, re-uploaded the file. Essentially not every rom is bundled with BusyBox and it used an $UNZIP function that not every phone has, so it was reverted. A few other minor changes were made last minute . Those of you having issues with the lib file not being placed or the app saying the library is not being installed for whatever reason, or any issues in general, just go ahead and install the re-uploaded zip and delete the old one.

Those of you not seeing any issues don't have to do anything.
[Magisk] ahrion:
Then you have to put "system" anywhere in the zip name and flash via your recovery. It can't be done through Magisk manager because for whatever reason, Magisk changes the zip name before it flashes through the manager.
[Magisk] uri4578:
Thank you [MENTION=6037748]Zackptg5[/MENTION] for your time and effort as well!! :good:
[Magisk] 24imelqui:
Running perfectly on Zenfone Selfie RR Nougat !
[Magisk] Wrapscallion:
I'm on an HTC One M7 with LOS Nougat and it seems to work great! :)
[Magisk] fjsferreira:
This module still breaks some apps (for example tapping "settings" in tapatalk pro or videoder, those apps just freeze). Removing the module fixes it.
[Magisk] ahrion:
I couldn't imagine why it would do this.
[Magisk] fjsferreira:
But it does :( I can reproduce it every time. I'll try to get logs.

Sent from my OnePlus 5
[Magisk] ahrion:
Is it AML or v4a causing this?I currently use Tapatalk and don't have this issue.
[Magisk] fjsferreira:
I don't know which one does it, guess I'll have to do more testing, but here are the logs captured when going to Videoder and tapping "settings" and the same with Tapatalk Pro

Videoder

https://pastebin.com/FPYxPJCn

Tapatalk

https://pastebin.com/L8dC4GtQ

I'm on Oneplus 5, latest OOS 4.5.10. If I remove both modules, those apps return to normal. If I install viper4android from the magisk repo, they are still normal.

I don't get why it would make this issue, but it's definitely only happens when installing this module :(
[Magisk] ahrion:
Does this happen for other modules
[Magisk] fjsferreira:
I only use Viper4android from the repo, and with that it doesn't happen, so I really can't say :S but if no one is having this issue, it's probably something on my end or with OnePlus 5

Sent from my OnePlus 5
[Magisk] n@vier:
Which device ROM and kernel?

Edited

You posted above :svetius:

Well it is weird!
[Magisk] ahrion:
The thing is that if you check the v4a folder in Magisk nothing touched anything besides v4afx file. Try deleting service.sh in the v4afx module folder in Magisk and see if that works.

Are you sure it's not Audio Modification Library?
[Magisk] ~N.A.W.Y~:
It's magisk related. When the module starts cloning /system files this is where this error occurs (you can see it in the logs if module uses clones)

There are few other modules that breaking few apps-app parts too, so i recommend you to install such app or modules into system directly till magisk dev fixes this issue..

MI 5 cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] Didgeridoohan:
I saw a little something in the Unified hosts module thread about this that seems to have worked. Could you try adding Tapatalk to the MagiskHide list and see if that changes anything?
[Magisk] andre0005:
Is it safe to replace the magisk apk in the module with this one:

https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx ?

I love the functionality, but the app looks like it was designed in the 90s.

I know that i could deactivate the included app and just keep both, but i'd prefer to have only one installed if possible.

Edit: Went ahead and just did it. Seems to be working fine.
[Magisk] chudy_85:
Not work with new magisk 14.1 All time want update drivers to install
[Magisk] TahirZX:
Hi guys.

I had been using the test build and I wanted to try the new update to v4A fx [MENTION=5357345]ahrion[/MENTION].

So like what's the procedure?

And can u clear me if there is a new Dolby Atmos update available as well or not?

These are my current modules
[Magisk] erak606:
I made a mistake by not reading anything. I updated my Magisk and after a reboot, my viper4android wasn't working so I downloaded the updated module from here and flashed it through Magisk, and now my phone is stuck on boot. Any help?

EDIT: Just used Magisk Mount and deleted a bunch of modules.

So it seems like the Magisk update broke the driver for me, the module here and the repo don't work. What should I do?
[Magisk] mttrwlnd:
Can confirm that it does not work with Magisk 14.1.

I am unable to downgrade to version 14.0, as I have a Pixel XL, and 14.1 is the first version to officially support it.

The only other module I currently have installed is the NDK BusyBox from the repo. I have also switched my SELinux to permissive, since that has helped in the past. No difference.

I am running 7.1.2 with the August security patch. No custom kernel.
[Magisk] Didgeridoohan:
[MENTION=5357345]ahrion[/MENTION] I'm gonna make an uneducated guess that the issues reported for v14.1(1410) beta comes from this commit:

https://github.com/topjohnwu/Magisk/commit/cfae6c63b5cf74b6ab6752b4660a714ee1b29186
[Magisk] mttrwlnd:
I uninstalled the modules, then attempted to flash the zip in TWRP. Seems it doesn't like my magisk img? Screenshot attached.
[Magisk] ahrion:
Template has not updated yet.

So sepolicy command has changed YET again?
[Magisk] andre0005:
The new template is exclusively to the beta branch for now it seems.
[Magisk] ahrion:
How many of you would use a Liveboot Magisk module? I've smali hacked it to work with not just SuperSU and init.d but also MagiskSU.
[Magisk] whalesplaho:
[MENTION=5357345]ahrion[/MENTION] i noticed dat when i restarted my phone and play music, v4a doesnt work until i launch v4a!

any way around though i flashed tha one on yur github lastweek...
[Magisk] Shriac:
I m on magisk v14 Galaxy s6. Cleaned previous modules and installed this one. Now works with every player no need to flash deep buffer remover. Now I want to install Dolby atmos. Should I just flash it? Or anything has to be done before
[Magisk] Rom:
ouloulou i would like it :cool:

Thanks in advance:good:
[Magisk] paed808:
I use Liveboot manually by copying the liveboot init script into service.d but having a module would simplify things.

---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------

Yes, just flash it (make sure it's the latest module version)
[Magisk] Didgeridoohan:
False alarm on that sepolicy commit, I think.

I've finally had time to do some proper testing and there's some other issue going on. For example, I've got major issues with all kinds of audio on my devices if I Magic mount anything to /system/etc. It's being looked into...

Edit: Here's the fix: https://github.com/topjohnwu/Magisk/commit/89330b89d86ae6cfb5143b0061963b50b04fd2bf
[Magisk] coeptisr:
I use miuipro and magisk 14 and module works well too. Great job dudeee! Your realyy amaze me. :)
[Magisk] Lycox:
Has anyone figured out, how to get it work with Tunein Radio?
[Magisk] 24imelqui:
[MENTION=263394]Lycox[/MENTION] try to flash deep buffer remover

[MENTION=5357345]ahrion[/MENTION] how to uninstall audiomodlib on magisk root? Can I simply delete the module on Magisk app/or folder?
[Magisk] Luq4dmin:
Will it works on x86 device ? Since the original one isnt supported on x86 devices...can u hack to make it works too ? Just asking :silly:
[Magisk] TahirZX:
If anyone can help I'd highly appreciate it. Thanks