yashsingh1/xdaforums huggingface dataset:
[Magisk] ErickG233:
Well...I have a issue with my LG G7.(with stock rom)

G7 has dts sound,but this effect affect the bass of the V4A.

[.conf file(

eagle{

path /vendor/lib/soundfx/libeagle.so

}

eagle_pipeline{

library eagle

uuid 146edfc0-7ed2-11e4-80eb-0002a5d5c51b

}

)

.xml file(

<library name="eagle" path="/vendor/lib/soundfx/libeagle.so"/>

<effect name="eagle_pipeline" library="eagle" uuid="146edfc0-7ed2-11e4-80eb-0002a5d5c51b"/>

)

]

I want to remove these effects but the vendor partition can not be modified(error while saving the file).

That's why I ask the question about removing existing effects.:laugh:

Can you think about it again?:)
[Magisk] castrum_doloris:
I have a little question:

On my OP6, LiquidRemix (or any Android 9 Custom Rom), no matter which audio mods installed (even with none :P);

I have to use the following workaround to get bluetooth working:

Copy 'audio_policy_configuration.xml' From:

/sbin/.magisk/modules/aml/system/etc

To:

/sbin/.magisk/modules/aml/system/vendor/etc/audio

Simple question: why? ^_^

What's the error? And how could I help fixing this? I know It's not a big deal and just a bit annoying, but It's somehow interesting for me how this works. And I like 'bughunting' and helping to get it fixed :)
[Magisk] NoobSHISH:
I can't seem to make Viper 2.7 work on my OP6 on Omni TreskMod.

It breaks bluetooth audio for media files like music or videos but not for calls. I attached the logs I got from MatLog about it, the error that I think cause this is "E/audio_hw_primary(1661): start_output_stream: A2DP profile is not ready, return error" that is the same problem that is explained here probably ( https://github.com/phhusson/treble_experimentations/issues/133 ). Hope the dev can solve this or at least tell me if it is a ROM related problem or not.
[Magisk] NoobSHISH:
For all the people on OmniROM that have my same problem, to make the bluetooth audio work on V4A with AML you should copy the content of /system/etc/audio_policy_configuration_omni.xml to /vendor/etc/audio/audio_policy_configuration.xml. After a reboot it should work without problems. I did it but couldn't replace or modify the second file so I changed the code in it directly. I had to read a comment on this thread of some months ago to make it work ¯\_(ツ)_/¯
[Magisk] alwynjoshy:
Mine also have the same issue. audio for the media is not working in Bluetooth mode, but calls are working, any fix. If i uninstall the aml it will work again. Please look into this [MENTION=6037748]Zackptg5[/MENTION]
[Magisk] alwynjoshy:
I replaced the same but not working. Any other fix by editing the code?
[Magisk] OGWisdom:
Thank you, sir!! I don't know how long I have been looking for a fix to my bluetooth not working and this did just the trick! It can't be all that impossible to have this procedure automated through the install of AML, but I haven't looked into all that just yet. I was just excited that I finally got bluetooth working and recorded the steps necessary for the future.
[Magisk] purig:
Hello! My Bluetooth media stemming is broken after installing AML. Log says a2dp not ready. [MENTION=6037748]Zackptg5[/MENTION]
[Magisk] alwynjoshy:
I cant see any directory like that. Will you give any more info about it please
[Magisk] alwynjoshy:
As far i know for my case i installed viper legacy, on last step it is asking to do apatch to kill audio server if we do that it will cause to brake the Bluetooth. So what i did aVoided that patch. The other steps i did is forgot also i remember I copy pasted audio policy to vendors. Anyway it is working
[Magisk] najabi:
Hello, could you add Ainur Narsil to AML compatible list?

https://ainuraudio.ru/ainur-narsil-android-audio-mod/

https://ainuraudio.ru/wp-content/uploads/2019/08/AINUR-NARSIL-MK-I-12.08.zip

Thanks
[Magisk] Zackptg5:
It already is. It uses .aml script

Updated OP with it :)
[Magisk] Iv0:
[MENTION=6037748]Zackptg5[/MENTION] just wanted to get it from your site but it seems your hoster doesn't like you... getting the following error:

"Account Suspended" :-/
[Magisk] bradical711:
Can confirm. I get the same error.
[Magisk] Zackptg5:
Ya, server maintenance by my hosting provider. Cpanel jacked their rates up so it's getting switched to directadmin or whatever. It should be back up later today, sorry!
[Magisk] bradical711:
Thank you for the quick response and no worries at all either! Our hearts just skip a beat every time one of the best mods in XDA goes missing lol ;)
[Magisk] Zackptg5:
Appreciate the kind words! Sites back up :)
[Magisk] beez1717:
I still can't get sauron and narsil working together. Haha. They detect the other and fail to install on my pixel 2 XL. I can't tell you why it doesn't work though.
[Magisk] jcmm11:
Because you're not supposed to install those 2 together. Pick one or the other, not both.
[Magisk] 101_CoreInsanity_101:
This fixed a lot of audio issues I had, thanks for that!

However, when I install this mod I cant get my bluetooth audio to work anymore. It says it's connected but it wont play audio.

Anything I can do to resolve this? I'm on a Redmi K20 Pro on Pixel Experience
[Magisk] androidfive:
If I have AML installed, the flashlight is grayed out in the status bar and i cant use it anf i cant make calls, i cant hear my conversation partner and he cant hear me either. Sounds strange, but i tested it with and without AML and it works without everything again. I have installed Sauron or Naril and V4A.
[Magisk] Hopie:
No Sound after flashing AML on my Xiaomi MI 9T Pro
[Magisk] ahmedmoselhi:
i have realme 3 pro when i flash advanced modification library module i got my bluetooth media sound broken

---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------

same here with realme 3 pro
[Magisk] Reli4nth:
Same here,

No bluetooth audio. OnePlus 6T with AOSiP Pie.

1. Installed Ainur Narsil

2. Installed V4A 2.7

3. Installed AudModLib

Can anyone help?
[Magisk] Nyuha:
I was hoping this would work but AudioWizard is still processing alongside viper which is really distorting my bass. Anyone have and advice?
[Magisk] aqua_hopps:
This mod is for multiple audio mods to work together. I assume you have AudioWizard natively on your device. In that case, you need not AML, but to manually comment out the dtsaudio audio effects in the audioeffects.conf / audioeffects.xml .
[Magisk] Nyuha:
Ty for the fast response I'll give that a shot!

Edit: Where are the files located?

Edit: Found the files but the dts part is actually located in the audio_effects_ZS660KL.xml.
[Magisk] gougous3:
Is AML aware of disabled modules? Also, how does it deal with modules that aren't AML compatible but replace audio files such as mixer_paths?
[Magisk] ZainBilq:
Same issue with me on rm3 pro [MENTION=6037748]Zackptg5[/MENTION]
[Magisk] Abhiman Chandru:
EDIT--

AFTER RESTART driver shows abnormal.(tried with viper 4.4 legacy version)

Only viper 2.7.1 version works perfectly after reboot too..

1.sauron

2.audio modification library

3.viper 2.7.1 version

This order works as of now..
[Magisk] DaveedDB:
Hey Zack ,long time

Could you be of any assistance with this error on the HTC U11 sense based rom ? I'm trying to flash Narsil and Viper just for a little bass but when I flash aml I get this error

The thing is it flashes to my 10 just fine with similar rom and Oreo on both so idk
[Magisk] Zackptg5:
That error is from narsil, not aml so you'll need to post debug logs to the ainur thread. Narsil applies patches specific to the device and software present which could explain why it was fine on oreo
[Magisk] Never_Sm1le:
[MENTION=6037748]Zachptg5[/MENTION].

Excuse me,

Both V4A and Dolby Atmos work well independently on my M8 running LOS14.1. Combining them almost always result in abnormal driver status in V4A. My flash order is this: V4A, Dolby, AML.

I tried all Dolby port. Is this a dolby or AML problem?
[Magisk] KackBarton:
I guys, this mod work on Android 10?

Thanks
[Magisk] marshharsha:
Viperxhifi keeps on asking busy box needs to be installed even I installed BusyBox in androidQ ROM
[Magisk] Zackptg5:
Updated AML to v2.5. Changelog:

Update to new magisk module template - only compatible with magisk versions 19+
[Magisk] DarkSJ1998:
Hey thanks for the update! It fixed the Bluetooth issue on Android Q/10 on my OP6T. v2.4 broke BT Audio on Android Q/10, but v2.5 is working fine again! Kudos man! :D
[Magisk] OjoDumeh76:
v2.5 Doldby digital Plus v6.5 does not work ... the problem cannot open the Dolby digital plus application, but after I re-installed the dolby digital plus v2.4 it worked fine
[Magisk] JazzMartian:
This thread states that AML is only compatible with Magisk (for obvious reasons?). Not sure what's so obvious about it. Not everybody uses Magisk and is familiar with how it works. Anyways, Ahrion's GitHub (for the deprected version) states that it is also compatible with system root installs. What is the last version of AML that works with system root installs, and what's the lowest version of Android supported on it? Thanks in advance.
[Magisk] Zackptg5:
So some history behind it all. Originally, Unity Installer and AML were combined into one. That's what's archived on ahrions github.

Nowadays, unity installer is its own thing and AML was completely redesigned into what it is today. The whole purpose of aml is to combine the audio effect/policy/mixer/etc files from multiple audio mods into one set because only one copy of a file can be active mounted at any given time. With non-magisk installs, the actual copies of those audio files are all modified by various mods (aka they all work with the same copy) and so there's no need for aml
[Magisk] JazzMartian:
Ah ok. Thanks for the explanation, Zack.
[Magisk] iblizdjava:
im only using AML and viper 2.7 at oneplus 7 pro, its works great.

the only problem is, it has crackling sound everytime when audio start, then its fine..

tried the old universal deep buffer removal, its still the same..

any helps?
[Magisk] Zackptg5:
That's due to the convolver or vdc your using most likely
[Magisk] Zackptg5:
Have a beta build here I'd like everyone to try out. Completely rewrote AML:

* Now uses diffutils, should automatically detect all audio mods now with any need for "aml compatibility" or whatever like before

* Only copy files needed - no more copying all audio files to aml mod directory - should help with users having weird issues with some audio policy files

Since it's been rewritten, I'm trying to really get a lot of testing in before I make it official.

Let me know if it worked and if not, follow troubleshooting steps. Thanks!
[Magisk] ISoreo:
Thanks a lot Mr.Zack I'll try it and tell you back

Edit : After Using the Beta version working fine ViPER and dolby working flawlessly am using Android 9
[Magisk] Zackptg5:
New beta build! Turns out that busybox grep doesn't always behave the way gnu grep did in my testing so I'm using gnu grep now

Edit: Removed build
[Magisk] castrum_doloris:
The new Beta works excellent for me. Now I don't have to copy the audiopolicy files manually anymore to get bluetooth working.

Nice work, thanks!

Testdevice:

Oneplus 6

AOSiP 9 (no GApps)

Magisk 20.3

Viper4Android 2.7, Ainur Narsil MK I

AML 3.0 beta 4
[Magisk] dkoek:
I have installed latest beta aml mod and viper4android fx. I have android 10 installed on Xiaomi redmi note 7.

Viper4android fx keeps asking to install the driver to make it work. What am I doing wrong?
[Magisk] avaie:
LG V40 - no processing through the media player or weak processing. DSTX 3D is default on this device. Processing is on chimes and system sounds (boot animations, notifications etc). Can't get it to work on Dolby, V4A or any other port available.
[Magisk] Mynouddin:
Earpiece is being used for media sound. How to remove? Havoc rom 3.1
[Magisk] realista87:
this mod 2.5 saved my rom!! i have a lenovo p2 ( kuntao) i flashed havoc 2.9 and i faced the problem of youtube stuttering and audio lag, i partially solved it deleting MAGISK, but it is not a viable solution!

THEN one member on telegram said me to try this audio modification libary and WOW.... if fixed the problem! can i ask you WHY? this mod is not born to fix video/audio stutterings..... but in my ase forked as a FIX !!
[Magisk] ace_apr27:
Just installed this on my OnePlus One running Lineage OS 16.0-202000208-NIGHTLY and Magisk 20.4-b39f4075. Now Magisk crashes every time I click on the Modules button :/

I can't find any of the mods on my phone and I can't uninstall the library. Is there any way for me to diagnose what is going on and figure out how to fix it?
[Magisk] guest4711:
Have a look into /data/adb/modules folder. There you will find all modules installed on Magisk. Simply delete (or move it out of the way) the corresponding folder...
[Magisk] ace_apr27:
Deleting the folder fixed the problem. Does this imply that the libraries won't work on my device or is there something that I could be missing?
[Magisk] guest4711:
Your download is probably corrupted. I'd try again. If it does not work have a look on the file called module.prop This file contains the description of the module which is displayed when opening "Modules" in Magisk. If this file contains garbage Magisk may crash.
[Magisk] Keule-Tm:
Best thing would be to place an empty file in the folder named 'disable'. After reboot you can still see the module in mm, but unticked.
[Magisk] guest4711:
But this does not help if this module description file kills Magisk cause the file is parsed even on disabled modules. Disabling does help if the module prevents you from booting or does not work as expected..
[Magisk] Zackptg5:
So a quick update on the progress for AML v3.0

As you may already know, it's completely different from aml v2.x in that it uses diffutils to compare files and some hacky scripting to merge conflicts. The problem here is that conflict merging is a manual process and so there's no way for me to script it to be truly automated. Due to this, I'm not going ahead with the v3 beta that uses the diffutils. I took down the beta builds I posted here to eliminate confusion

Instead, I'm working on updating and revamping/redoing v2.x so it'll become the v3 once it's ready.

What's changed?

The mod itself has been completely rewritten - slimmer, more efficient, more idiot proofed.

The big change for any audio module devs is that the aml.sh logic has changed slightly - it actually makes things much easier now:

The extra variables (NAME, LIBDIR, RUNONCE, COUNT) have been removed. There's no need for them anymore and they made things way more confusing then they needed to be.

The aml.sh script only runs once which is why the above is no longer needed. If you're patching aml files, call them like you would any other - $MODPATH/system/whatever

This isn't really a change - it behaved the same way before minus how many times the script is run

The syntax for patch_cfgs has changed to be more streamlined. the <library_path> actually should point to your library now:

i.e. /vendor/lib/soundfx/whatever.so

Note that lack of $MODPATH or any magisk paths - just use what the path would show up as if you were patching an audio_effect file

Once this becomes stable - I'll update the OP and such with better instructions but as you can see, the changes you would need to make are minimal and make life easier
[Magisk] Zackptg5:
Okay everybody, here's the new beta. If there's any issues (I don't think there will be though), post the debug.log and errors.txt files from the module directory

Edit: Beta 2 out now, grab it from here
[Magisk] mario0318:
Odd. For some reason this breaks Xposed Framework on my system. Currently on the latest magisk with xposed 90 beta v3. I noticed with the boot process as I have LiveBoot installed that some warnings or fatal errors were showing up in red text. When the phone boots up, magisk and xposed installer and everything else is there but the actual xposed framework appeared to be disabled despite it being installed.

Removing AML v3 beta restored xposed framework.

Btw, I'm running Lineage OS 15.1, on an LG K20.

What logs could i go about sharing with you? I'm not really sure where to find any that you may need.
[Magisk] Zackptg5:
Aml shouldn't touch xposed at all as it only modifies audio related files. If you could grab a logcat so I could see what the errors are, that'd be great. And a zip of your magisk modules folder would also be helpful :)

What audio mods do you have installed?
[Magisk] mario0318:
You need the modules folder in data/adb/magisk as a zip? It's pretty large because of YouTube Vanced and App Systemizer having several apk files in it.

Or is it another directory entirely?

I'll reinstall the mod and grab the logcat as well.

As far as audio mods, only Ainur Sauron. I've also got a screenshot/camera sound disabler mod but as i understand it only replaces audio files with empty ones and doesn't touch any audio config files.
[Magisk] mario0318:
Here you go, zips attached.

Is this what you needed?
[Magisk] Zackptg5:
Yup and the problem here is sauron. I changed how the aml.sh script works and so sauron isn't compatible with this new aml (yet). Looks like the aml script is locking up because of it.

Related to this issue is beta 2! Only change here is addition of some debugging features and aml will now detect and skip old aml scripts so this doesn't happen

Edit: beta removed
[Magisk] mario0318:
I appear to be having the same issue with beta 2. Same warnings during boot as mentioned previously.
[Magisk] Zackptg5:
Can you post the debug and error files in aml module folder and then try again without sauron?
[Magisk] mario0318:
Here are the aml logs.

Tried it with Sauron disabled and issue persists. Xposed disabled. I also noticed YT Vanced gets reset. So it's both YT Vanced and Xposed Framework magisk modules being affected.
[Magisk] Zackptg5:
Hmm, the logs look fine so I'm not entirely sure what the issue is. I'll look into it though
[Magisk] Zackptg5:
So I don't see anything that aml would interfere with however you do have a lot of modules with post-fs-data.sh scripts. Best way to figure this out is to disable all modules, add back sauron and aml, and then keep adding them back one by one to find where the problem lies
[Magisk] ISoreo:
Thanks a lot Mr.Zackptg. No problem with this module, Ainur narsil and V4A worked normally but Dolby seem broken.
[Magisk] Zackptg5:
AML 3.0 is finally HERE!!!

I've had several different beta channels over the past couple months including many scrapped ideas. The big one was using diff3 but there was no good way to automate conflict merging and so that was scrapped.

Instead I rewrote 2.5 to be much learner, more efficient, and easier to make an aml.sh script for if you need to.

Note that the logic for aml.sh files has been changed - it's much easier now - as you can see by the bottom section in the OP

If you were on a previous beta, completely uninstall that beta first (I used different directories in that one). If you fail to do this, you'll have to reinstall all of your audio mods

Changelog:

* Complete overhaul - most everything happens in the boot script now, no need for redunduncies

* Added Guitardedhero's Dolby Atmos Pie/Q

* Added Ainur DTS

* Removed IceWizard
[Magisk] Kayniedude:
No longer working

I updated to version 3 and now my Viper4Android doesn't work, it's asking to install drivers.

Using Pixel 3a android 10
[Magisk] Arda Süzen:
Normally i used beta 4 and working good with projectduality tasha patcher, ainur narsil 0403 and dolby digital plus 7.2. Also i tryed new beta 2 but always bootloop. Now i tryed stable 3.0 with same modules but clean install and now all audio mods not working any more. This is my data/adb/modules/aml folder.
[Magisk] Lughnasadh:
All seems to be working well with this latest version and the latest version of JamesDSP and ACP :good:
[Magisk] Zackptg5:
Can you follow the troubleshooting section in the OP?

Narsil has some issues I'm in the process of working out. Try removing that
[Magisk] Zackptg5:
Which v4a are you using? You need to run this in terminal:

su
chcon u:object_r:vendor_file:s0 /data/adb/modules/ViPER4AndroidFX/system/vendor/lib/soundfx/libv4a_fx.so

That's not an aml issue but Q being more picky with files
[Magisk] Homeboy76:
Try disabling AML 3.0. Start Viper4Android after the drivers are installed (it may take a few restarts) enable AML 3.0.
[Magisk] Kayniedude:
Thank you it worked! But the second I re-enable all it seems to break Viper
[Magisk] kowallis.r@gmail.com:
For the record, new aml 1.4.3 update broke my Dolby Atmos on my Axon 7 with AEX 8.1. No problem. Rollback to 1.4.2 worked.
[Magisk] Zackptg5:
Can you post your aml folder with 1.4.2, then with 1.4.3?
[Magisk] Zackptg5:
Everything looks good here, not sure what the issue was before since I haven't seen any of it myself
[Magisk] kowallis.r@gmail.com:
I can mail them to you.

---------- Post added at 11:34 PM ---------- Previous post was at 11:24 PM ----------

Sorry, have folders ready. Don't know how to attach.
[Magisk] Zackptg5:
If you're on your pc, just reply to this post (not quick reply, hit the reply button at the bottom of it). Then towards the bottom of the new page should be the file attachment section
[Magisk] Trupen:
This version also sometimes gives crackling sound from viper

V 1.2

Pls find attachment
[Magisk] Zackptg5:
Aml has nothing to do with crackling sound. But you have Atmos entry under music_helper twice in vendor/etc/audio_effects.cfg. you want to remove one of those. I recommend uninstall all audio mods and reinstalling them (with aml 1.4.3) cause I bet something got messed up along the way
[Magisk] Trupen:
Cleans flashed the ROM still crackling sound
[Magisk] Zackptg5:
AML has nothing to do with that, that's likely related to whatever settings you have set in the apps and/or something with your rom
[Magisk] Zackptg5:
Hi everyone! So I don't have to keep repeating myself, I added a troubleshooting section to the OP so please consult that before reporting any bugs here. Thanks!
[Magisk] manhong2112:
dolby atoms (standand 20180215 by guitardedhero ) stop working (not processing) after flashing aml 1.4.3. Also dolby is working again after uninstalling aml.

I'm using mi5 with AEX.mod Oreo 8.1 which built on 02/15/2018.

(magisk_img.zip only included .core and aml)

EDIT: It is also not working with aml 1.4.2
[Magisk] Zackptg5:
Well this is a weird one. AML files actually look fine while I see 2 problems with the originals ironically. The logcat shows v4a being installed but I don't see it in aml anywhere? Is it a different logcat?
[Magisk] manhong2112:
i installed apk of v4a for keeping my setting, module is uninstalled
[Magisk] Zackptg5:
Gotcha. That might be messing with stuff but I'm not certain yet. You can just save your profile (which saves it to sdcard/Viper4AndroidFX) so you don't have to worry about that. Can you uninstall v4a and then send another full logcat after attempting to open dolby?
[Magisk] manhong2112:
sure, here it is
[Magisk] Zackptg5:
Hmmm, this is an enigma. Can you try one more thing? Can you copy magisk/.core/aml/dolbyatmos/system/vendor/etc/audio_effects.xml to magisk/aml/system/vendor/etc/audio_effects.xml?

This file is literally the only thing different between having aml installed and having it not installed
[Magisk] manhong2112:
done, dolby atoms works again.
[Magisk] Zackptg5:
This is a strange one. So I attached 2 screenshots showing the differences between the original dolby one (left) and aml one (right). In the first one, you'll see what's actually a typo in the original one (but it doesn't break anything in this case). But I think the second screenshot is where things get interesting. The postprocess section is correct in the aml one but not in the original and yet the aml one doesn't work which makes me thing that music_helper is the culprit or it has something to do with the commenting. So can you try a few things for me (sorry for all of this but I don't have any devices that use xml audio_effects). Can you try each one I attach and let me know what happens with each (of course rename them to be the proper name)? Thanks! My guess is that there's some nuance with commenting in these files that's breaking stuff or something wonky with music_helper