[MOD] Audio Modification Library v4.2 - Magisk

Audio Modification Library is a library of known audio mods. It'll search your magisk directory for any supported audio mods and incorporate them into itself. It's been completely redone to act as a standalone module so devs no longer need to worry about using a framework for their audio mods and users no longer are limited to just mods using that framework.
Some history
Originally, Unity Installer and AML were combined into one. That's what's archived on ahrions github.
Nowadays, unity 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
What is the purpose of this?
Audio mods often function in part by modifying some audio files (such as audio_effects, mixer_paths, etc.). The problem here is that each mod has it's own copy of the files and magisk can only mount 1 copy of each, so only 1 mod will completely work. AML functions by combining them all into one set of files to remedy this issue.
So how does it work?
It's now a standalone zip that is flashed once and forgetten about. It's magisk only for obvious reasons and will incorporate all supported audio mods into itself automatically during install, and then during each boot if any changes were detected. So it will adjust for any changes in audio mods such as new ones being installed, some being removed, or an existing one being updated.
Where the Mod is Located:
This is more of the nitty gritty for anyone interested but the aml specific copies of audio files and the mod itself are stored in the aml folder in the magisk directory like a typical module. However, it moves any detected audio files out of the folder of any audio mods so they won't be mounted by magisk and conflict. They're moved to .core/aml for safe keeping so they can be restored back to the mod later if you choose to uninstall aml or if upgrading aml
When do I flash this?
Unlike with older version of aml, order doesn't matter. However, it's best to flash aml FIRST. The reason for this is that an increasing number of audio mods look for aml and behave differently if it doesn't yet exist.
Troubleshooting:
If a mod didn't work before you flashed aml, it probably won't work after. Take up the issue on the mod's thread.
Otherwise, if a mod works before flashing aml and doesn't after: First, try uninstalling all audio mods and then reinstalling them (including aml). If that doesn't work, then I'll need you to make a post with this in it:
Recovery log after flashing AML
List of Audio Mods Installed
AML version last working on (if applicable)
Zip attachment of your aml magisk module (/data/adb/modules/aml) folder (note that there's a debug.log file in here that's shows everything)
Zip attachment of your aml backup folder (/data/adb/aml) folder
Currently Supported Mods:
AM3D
AudioWizard
V4AFX
V4AXhifi
Dolby Atmos (ahrion's ports)
Dolby Atmos Axon 7 Oreo (guitardedhero's port)
Dolby Digital Plus
Bang&Olufsen ICEPower (only tested ainur version)
Arkamys (only tested ainur version)
Dirac (only tested ainur version)
Dirac Hexagon (only tested ainur version)
JamesDSP
MaxX Audio 3
Audio Compatibility Patch (formerly universal deep_buffer remover)
Ainur Sauron
SquareSound
Sony Xperia Z2 Sound System
Ainur Narsil
Ainur DTSX
Ainur DTS Ultra
Dolby Atmos Pie/Q+ (guitardedhero's ports)
Want an audio mod added to AML?
Make a post about it and I'll see if it's eligible. No guarantees that I'll add it but these are things that it must have to even be considered:
Original/unique (so not a repackaging of other audio mods)
Universal(ish) (support a large number of devices - not specific to a handful of devices)
Patches files rather than replaces them (the whole point of aml is to be a collection of patches)
Patches must be static (won't be changing with each mod update)
Audio Mod Can't be Added to AML Directly? You can still add it in!
If it doesn't meet these requirements, you can still make it aml compatible.
You just need your mod to create a file called ".aml.sh" in the root of the mod directory ($MODPATH typically). It'll need to have the patches for your mod in a format that aml can understand:
For patching audio_effect files, AML includes a 'patch_cfgs' function that makes life much easier. So if you have an effect and library to add:
Code:
patch_cfgs <effect_name> <UUID> <library_name> <library_path>
For example:
Code:
patch_cfgs v4a_fx 41d3c987-e6cf-11e3-a88a-11aba5d5c51b v4a_standard_fx /vendor/lib/soundfx/libv4a_fx.so
Note that this patch_cfgs function is for audio effects files only. If you're patching audio policy or mixer_paths files, then you'll need to make the patches the old fashioned way yourself.
So if you're not patch audio effects files, skip on down to the 'Some other variables/options' section
'patch_cfgs' has several flags that can be used (the format followed by an example for each is listed here as well):
-l: patch library
Code:
patch_cfgs -l <library_name> <library_path>
Code:
patch_cfgs -l v4a_fx /vendor/lib/soundfx/libv4a_fx.so
-e: patch effect
Code:
patch_cfgs -e <effect_name> <UUID> <library_name>
Code:
patch_cfgs -e v4a_standard_fx 41d3c987-e6cf-11e3-a88a-11aba5d5c51b v4a_fx
-o: patch output_session_processing (postprocessing). Typically used with both 'l' and 'e' flags as well
Code:
patch_cfgs -ole <osp_section> <effect_name> <UUID> <library_name> <library_path>
Code:
patch_cfgs -ole music atmos 9d4921da-8225-4f29-aefa-aacb40a73593 atmos /vendor/lib/soundfx/libatmos.so
-q: patch pre_processing (preprocessing). Typically used with both 'l' and 'e' flags as well
Code:
patch_cfgs -qle <pp_section> <effect_name> <UUID> <library_name> <library_path>
Code:
patch_cfgs -qle music atmos 9d4921da-8225-4f29-aefa-aacb40a73593 atmos /vendor/lib/soundfx/libatmos.so
-p: patch proxy effect (note that since this is a special kind of effect, it cannot be used with '-e'). When used by itself
Code:
patch_cfgs -p <proxy_effect_name> <proxy_UUID> <sw_library_name> <sw_UUID> <hw_library_name> <hw_UUID>
Code:
patch_cfgs -p dax 9d4921da-8225-4f29-aefa-6e6f69726861 dax_sw 6ab06da4-c516-4611-8166-6168726e6f69 dax_hw a0c30891-8246-4aef-b8ad-696f6e726861
But it's typically used with 'l'
Code:
patch_cfgs -pl <proxy_effect_name> <proxy_UUID> <sw_library_name> <sw_UUID> <sw_library_path> <hw_library_name> <hw_UUID> <hw_library_path>
Code:
patch_cfgs -pl dax 9d4921da-8225-4f29-aefa-6e6f69726861 dax_sw 6ab06da4-c516-4611-8166-6168726e6f69 /vendor/lib/soundfx/libswdax.so dax_hw a0c30891-8246-4aef-b8ad-696f6e726861 /vendor/lib/soundfx/libhwdax.so
-r: replace. Normally, aml will only apply any of the above if it doesn't exist in the audio cfg file. With this flag enabled however, it'll replace any existing effects. It's pretty rare that this would be needed (none of the mods patches built-in to aml have this)
no flag specified: if no flags are specified, patch_cfgs will use -le by default (patch library and effect). This is what's typically used (like in the first example before this list)
For patching other files: just add you script logic like it it was in your mod.
If you're patching mixers for example:
Code:
for i in $(find $MODPATH/system -type f -name "*mixer_paths*.xml"); do
<add_patch_here> for mixer '$i'
done
MODPATH is equivalent to aml's directory since it's running the aml.sh script
Then when AML is installed, it'll detect this .aml.sh file and apply the patches accordingly
Source
Download

Awesome work! Excited to try it out. Will the usual AML mods such as ainur and v4a be updated or can I go ahead and test out with the current v2.9 zips?

nonchalantroller said:
Awesome work! Excited to try it out. Will the usual AML mods such as ainur and v4a be updated or can I go ahead and test out with the current v2.9 zips?
Click to expand...
Click to collapse
Just finished updating everything. Usual aml mods are now unity mods so you don't even need to worry about that anymore. I'll put a list of supported mods to the op in a min
Edit: OP updated, ainur mods will likely be released tomorrow so you'll need to hold off until then to use them

Here's the install log from Magisk where Viper is asking for drivers.

MrBrady said:
Here's the install log from Magisk where Viper is asking for drivers.
Click to expand...
Click to collapse
Can you try this test zip and send the recovery log?

Zackptg5 said:
Can you try this test zip and send the recovery log?
Click to expand...
Click to collapse
Sure! Installation failed. Log attached.

MrBrady said:
Sure! Installation failed. Log attached.
Click to expand...
Click to collapse
Danget, dumb error on my part. I reuploaded the attachment in my last post so try that. Sorry!

Zackptg5 said:
Danget, dumb error on my part. I reuploaded the attachment in my last post so try that. Sorry!
Click to expand...
Click to collapse
Installed the updated file. Still asking to install drivers. Log attached.

MrBrady said:
Installed the updated file. Still asking to install drivers. Log attached.
Click to expand...
Click to collapse
Dang, still same error on recovery log but now I'm starting to hone in on the problem. Thanks!

MrBrady said:
Installed the updated file. Still asking to install drivers. Log attached.
Click to expand...
Click to collapse
Does this aml work for you? (Post recovery log and aml folder please)

Zackptg5 said:
Does this aml work for you? (Post recovery log and aml folder please)
Click to expand...
Click to collapse
Installing this caused V4A to ask for drivers again. Folder and log attached.

MrBrady said:
Installing this caused V4A to ask for drivers again. Folder and log attached.
Click to expand...
Click to collapse
Think I got it. I'll need the same stuff as before

Zackptg5 said:
Think I got it. I'll need the same stuff as before
Click to expand...
Click to collapse
Bingo! That works now. Attached is the directory and log.

MrBrady said:
Bingo! That works now. Attached is the directory and log.
Click to expand...
Click to collapse
Sweet! Thanks for all your help, I really appreciate it :good:

Zackptg5 said:
Sweet! Thanks for all your help, I really appreciate it :good:
Click to expand...
Click to collapse
My pleasure! Thanks for making this mod! I know we all really appreciate it, even if it's not voiced often enough.

AML has been updated to v1.1! Main changes are fixes or xml cfg files (should fix issues with pixel 2's) and some other minor fixes. Thanks to @MrBrady for the troubleshooting help

v1.2 has been dropped. Hopefully this will be the last release for a while.
Changelog: Fixed janky bootmode stuff, Fix uninstall/upgrade when a supported audio mod has just been upgraded in bootmode
So basically any weird things that happened when flashing in magisk manager are now fixed

Zackptg5 said:
v1.2 has been dropped. Hopefully this will be the last release for a while.
Changelog: Fixed janky bootmode stuff, Fix uninstall/upgrade when a supported audio mod has just been upgraded in bootmode
So basically any weird things that happened when flashing in magisk manager are now fixed
Click to expand...
Click to collapse
Thanks! Seems to be working right on Pixel 2 XL now.

Safety net got tripped,RR unofficial 7.1.2, I passed again after uninstalling aml.
Gonna try again but install from twrp...seemed to fix my viper issues, might do the same for aml
---------- Post added at 08:27 AM ---------- Previous post was at 08:18 AM ----------
preference said:
Safety net got tripped,RR unofficial 7.1.2, I passed again after uninstalling aml.
Gonna try again but install from twrp...seemed to fix my viper issues, might do the same for aml
Click to expand...
Click to collapse
Yep, twrp install works with no safety net trip. I've never had this many issues using the direct install in magisk. I doubt that it's a module issue, I'm probably messing up the process.

Dropped v1.3. Fixes issues with output_session_processing patching - mainly applicable to dolby oreo

Related

[Module][v4.1] ViPER-FX **Discontinue**

COLOR="Red"]This thread will discontinue, Now I'm published my new mod's thread under Magisk, that mod includes Whole new ViPERFX app and many other mods and upcomings so From now everybody please follow this thread below:
[Module] ViPERFX
https://forum.xda-developers.com/apps/magisk/viperfx-t3667145[/COLOR][/SIZE][/B]
Introduction:
ViPER4Android is very popular audio mod around the world of Android and probably the best audio mod ever made. But there is so many complexity ViPER4Android couldn't go further through, so I wish "ViPER-FX" could be a project to let our beloved ViPER4Android step in advance. Original V4A details at ViPER4Android Official forum.
Modifications:
+ Based on ViPER4Android v2.5.0.5
+ New Material UI and Icon
+ App rotation enabled.
+ Default install as system app to prevent task kill.
in MIUI or some rom could be installed as user-app
for IRS compatibility [Experimental]
+ The zip edition includes apk.
Recommendation:
* Magisk Manager, Framework installed.
* Android 5.0+
* To update from ViPER-FX v4.0 (v4.0 only) first remove it.
How to install?
* Flash the zip using Magisk Manager or Custome recovery.
# Track this thread using the URL below.
URL: [url]http://forum.xda-developers.com/showthread.php?t=3535401[/URL]
Thanks To:
Code:
[user=4470081]@topjohnwu[/user] for Magisk Framework.
[user=3901724]@zhuhang[/user] and ViPER520 (Founders of ViPER4Android).
[user=4445176]@guitardedhero[/user] | [user=5704037]@repey6[/user] | [user=5210243]@exodius48[/user] | [user=6118476]@#mrk[/user]
for helping/support/testing.
...and those I forgot to mention.
I spend dedicated time, made pressure on brain and did hard work to make this perfect
If you like my post please hit Thanks and give a rate....
~~ Feel The power of ViPER-FX ~~
Contributors
metaspook
Version Information
Status: Stable
Current Stable Version: 4.1
Stable Release Date: 2017-01-13
The long waited finally come, will try this out.
the title is a bit misleading:
-this is not [Magisk], this is a [Module]
-it's not 100% clear if you packed the Magisk module or if you also offer a modded App (in thread description)
-it also has the same id as @topjohnwu 's module...
id=v4a
name=ViPER-FX
version=Base v2.5.0.5 | MKM v4.0
versionCode=3
author=ViPER’s Audio | Mod by Metaspook
description=ViPER-FX is a system wide audio enhancing software, modified edition of ViPER4Android.
support=https://www.androidfilehost.com/?w=files&flid=143525
donate=http://vipersaudio.com/blog/?page_id=95
Click to expand...
Click to collapse
@metaspook
Can you delete V4A app inside "\system\priv-app\ViPERFX" in next release? Because if V4A app installed inside /system/ there will be no sound improvement by IRS. Tested on my device running MIUI rom, dunno on other rom.
I use sepaker & many times change the IRS, but no sound improvement.
crusader727 said:
the title is a bit misleading:
-this is not [Magisk], this is a [Module]
-it's not 100% clear if you packed the Magisk module or if you also offer a modded App (in thread description)
-it also has the same id as @topjohnwu 's module...
Click to expand...
Click to collapse
Got it... actually I had to make this thread in short time making this of thread n sort it as well as possible is a bit hard something could be missing, but this thread will be more informative, well sorted soon...
Thank you.
exodius48 said:
@metaspook
Can you delete V4A app inside "\system\priv-app\ViPERFX" in next release? Because if V4A app installed inside /system/ there will be no sound improvement by IRS. Tested on my device running MIUI rom, dunno on other rom.
I use sepaker & many times change the IRS, but no sound improvement.
Click to expand...
Click to collapse
Do u'v installed Magisk n flash the zip through it?
B'cz this is a whole new way to dealing with system.
If u did but after that also don't work let me know.
metaspook said:
Do u'v installed Magisk n flash the zip through it?
B'cz this is a whole new way to dealing with system.
If u did but after that also don't work let me know.
Click to expand...
Click to collapse
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
exodius48 said:
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
Click to expand...
Click to collapse
OK I'll release next update separately..
I can't tell whether or how this differs from the existing V4A module offered by topjohnwu.
Cool. I'd like to try this out. I just had some questions:
1. What do these commands do:
Code:
/data/magisk/sepolicy-inject --live -s mediaserver -t mediaserver_tmpfs -c file -p read,write,execute
/data/magisk/sepolicy-inject --live -s audioserver -t audioserver_tmpfs -c file -p read,write,execute
2. Why are the following folders blank?
Code:
system/etc
system/lib/soundfx
system/vendor/etc
oreo27 said:
Cool. I'd like to try this out. I just had some questions:
1. What do these commands do:
2. Why are the following folders blank?
Click to expand...
Click to collapse
1. It helps to keep Viper FX alive in SELinux enforcement.
2. Into these directories necessary files will be extracted or pulled from original /system.
Thanks to wanna know. :good:
metaspook said:
1. It helps to keep Viper FX alive in SELinux enforcement.
2. Into these directories necessary files will be extracted or pulled from original /system.
Thanks to wanna know. :good:
Click to expand...
Click to collapse
Oh. I didn't think to check in the update-binary. It feels like this is a complicated script for sure:
Code:
# Push files
unzip -oq $ZIP "system/*" -d $MODPATH
unzip -pq $MODPATH/system/priv-app/ViPERFX/ViPERFX.apk assets/libv4a_fx_jb_$DRVARCH.so > $MODPATH/system/lib/soundfx/libv4a_fx_ics.so
ui_print "[OK] Pushing files."
# Config files modification.
for X in /system/etc/audio_effects.conf /system/etc/htc_audio_effects.conf /system/vendor/etc/audio_effects.conf; do
cp -af $X $MODPATH$X
sed -i '/v4a_fx {/,/}/d' $MODPATH$X
sed -i '/v4a_standard_fx {/,/}/d' $MODPATH$X
sed -i 's/^libraries {/libraries {\n v4a_fx {\n path \/system\/lib\/soundfx\/libv4a_fx_ics.so\n }/g' $MODPATH$X
sed -i 's/^effects {/effects {\n v4a_standard_fx {\n library v4a_fx\n uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b\n }/g' $MODPATH$X
done; ui_print "[OK] Config modification."
Does this mean that if I uninstall this mod, Viper is completely uninstalled without any changes present in my entire device? If so, it's a pretty good implementation.
Nice! Works just fine on my Nexus 6. Will this be submitted to the Magisk repo? Would be useful to have it in the manager...
oreo27 said:
Oh. I didn't think to check in the update-binary. It feels like this is a complicated script for sure:
Code:
# Push files
unzip -oq $ZIP "system/*" -d $MODPATH
unzip -pq $MODPATH/system/priv-app/ViPERFX/ViPERFX.apk assets/libv4a_fx_jb_$DRVARCH.so > $MODPATH/system/lib/soundfx/libv4a_fx_ics.so
ui_print "[OK] Pushing files."
# Config files modification.
for X in /system/etc/audio_effects.conf /system/etc/htc_audio_effects.conf /system/vendor/etc/audio_effects.conf; do
cp -af $X $MODPATH$X
sed -i '/v4a_fx {/,/}/d' $MODPATH$X
sed -i '/v4a_standard_fx {/,/}/d' $MODPATH$X
sed -i 's/^libraries {/libraries {\n v4a_fx {\n path \/system\/lib\/soundfx\/libv4a_fx_ics.so\n }/g' $MODPATH$X
sed -i 's/^effects {/effects {\n v4a_standard_fx {\n library v4a_fx\n uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b\n }/g' $MODPATH$X
done; ui_print "[OK] Config modification."
Does this mean that if I uninstall this mod, Viper is completely uninstalled without any changes present in my entire device? If so, it's a pretty good implementation.
Click to expand...
Click to collapse
1. The code I wrote looks a bit complicated but its for to reduce the size of the module (you can see I didn't packed the driver separately, codes are extracts those from the apk) and for more task will be done in less lines.
2. Yes.. obviously that's why using Magisk framework is so useful. It wont change anything in /system while installing nor in uninstalling your /system would be intact.
Didgeridoohan said:
Nice! Works just fine on my Nexus 6. Will this be submitted to the Magisk repo? Would be useful to have it in the manager...
Click to expand...
Click to collapse
Thanks... yes I wish also soon.
exodius48 said:
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
Click to expand...
Click to collapse
Actually I pushing the apk into the system cause if Viper install as user app in data, 3rd party or internal app killer kill it and Viper looses to output the effect even also when remove from recent list. but I have an idea if its just happens with your MIUI rom... can you give me your ROM's 'build.prop" file ???
Is not working for me, IS activated on Magisk Modules Install,
But V4A say "Install/Update now?", Samsung S5 G900m, Is rooted using SuperSU 2.79, Latest Magisk Manager/Installer,
I Installed this V4A why magisk "Refuses" to open Modules download page "No Modules Found", And i have to download manually from internet. (SafetyNet says RED, Root and Magisk is green in Magisk Manager)
V4A is installed as System App, And SELINUX is Permissive,
I Try to change V4A to user APP, But not working;
metaspook said:
Actually I pushing the apk into the system cause if Viper install as user app in data, 3rd party or internal app killer kill it and Viper looses to output the effect even also when remove from recent list. but I have an idea if its just happens with your MIUI rom... can you give me your ROM's 'build.prop" file ???
Click to expand...
Click to collapse
Yes you're right. But on MIUI (especially MIUI 8 on my device) i can control it. We can lock app into taskbar and turn off MIUI optimization for selected app by turn off background restriction. Those will prevent MIUI kill running app.
build.prop file attached. :good:
metaspook said:
1. The code I wrote looks a bit complicated but its for to reduce the size of the module (you can see I didn't packed the driver separately, codes are extracts those from the apk) and for more task will be done in less lines.
2. Yes.. obviously that's why using Magisk framework is so useful. It wont change anything in /system while installing nor in uninstalling your /system would be intact.
Click to expand...
Click to collapse
This is pretty good. I installed this and it's working great. Just a quick question, I don't suppose it can work on phone calls as well? I was looking to get my bluetooth volume increased.
oreo27 said:
This is pretty good. I installed this and it's working great. Just a quick question, I don't suppose it can work on phone calls as well? I was looking to get my bluetooth volume increased.
Click to expand...
Click to collapse
Not sure about it... Test urself, look can work or not

[MODULE] Volume Steps Increase (for Magisk v10+)

This module doubles the number of steps in volume adjustment for both media and in-call volume.
WARNING: Apparently doesn't work on all devices, for example OnePlus 3 according to this.
what about a collection thread for build prop tweaks to use in Magisk?
Thanks for the module. It's got a funny bump going louder until the middle of the scale, then getting suddenly significantly quieter again and going louder until the end, for media playback.
Bettik said:
Thanks for the module. It's got a funny bump going louder until the middle of the scale, then getting suddenly significantly quieter again and going louder until the end, for media playback.
Click to expand...
Click to collapse
Could be hardware/driver-dependant. I've used a (non-systemized) prop modification before on a tablet and it was pretty smooth.
time comes, good modules too :good:
Just a reminder for those who encounter problems. ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30 won't work for all devices, such as OnePlus 3, at least on its official OxygenOS.
Once you change your media volume steps from default 15 to the 30, using the script above which is included in the module, on your OnePlus 3. The steps are increased, while it's just a loop. The volume drop back to the lowest again at the 16th step and totally silent at some steps bigger than 20.
BTW, the xposed module VolumeSteps+ won't work on OnePlus 3 either.
accidentally quoted OP instead of editing it.
changes couldn't be reseted after removing the system.prop or the module. Any thing to do?
chjun90 said:
changes couldn't be reseted after removing the system.prop or the module. Any thing to do?
Click to expand...
Click to collapse
Remove module, reboot. When asking for help, provide logs.
stangri said:
Remove module, reboot. When asking for help, provide logs.
Click to expand...
Click to collapse
i do that many times. i have removed the module days ago, but the chages still on my phone. i found the bug in all the modules with system.prop not only yours. thinking it's bugs of magisk v11.1.
chjun90 said:
i do that many times. i have removed the module days ago, but the chages still on my phone. i found the bug in all the modules with system.prop not only yours. thinking it's bugs of magisk v11.1.
Click to expand...
Click to collapse
Would be great if you had created an issue against Magisk on github then. Probably uninstalling magisk (from recovery) and re-installing it would start you with a clean slate.
Alternatively, there're unofficial builds of the next-gen magisk available, maybe they would fix the issue.
stangri said:
Would be great if you had created an issue against Magisk on github then. Probably uninstalling magisk (from recovery) and re-installing it would start you with a clean slate.
Alternatively, there're unofficial builds of the next-gen magisk available, maybe they would fix the issue.
Click to expand...
Click to collapse
i had
Is it compatible with the latest 11.6 magisk? Anyone tested?
Angelos N. said:
Is it compatible with the latest 11.6 magisk? Anyone tested?
Click to expand...
Click to collapse
11.0.0 version is and I have.
Angelos N. said:
Is it compatible with the latest 11.6 magisk? Anyone tested?
Click to expand...
Click to collapse
Causes systemui FC.
This is because of system.prop. I had this same issue when changing.
To 11.6.
ahrion said:
Causes systemui FC.
Click to expand...
Click to collapse
As evident from the screenshots below it works fine.
Care to post link to the github issue where 11.6 has broken system.prop support?
stangri said:
As evident from the screenshots below it works fine.
Care to post link to the github issue where 11.6 has broken system.prop support?
Click to expand...
Click to collapse
I had the same issue with my mods, removing system.prop fixed this issues. 11.6 broke resetprop for certain people. I don't see any issues on the GitHub for magisk, but I know this is an issue because me on my own mods and others have reported this same issue. I've tested it and that's what I have found.
It doesn't happen to all phones but I think it's a magisk issue with resetprop, something that was not an issue in 11.5.
ahrion said:
I had the same issue with my mods, removing system.prop fixed this issues. 11.6 broke resetprop for certain people. I don't see any issues on the GitHub for magisk, but I know this is an issue because me on my own mods and others have reported this same issue. I've tested it and that's what I have found.
It doesn't happen to all phones but I think it's a magisk issue with resetprop, something that was not an issue in 11.5.
Click to expand...
Click to collapse
I think you're making way to large assumptions here. From my experience, there's no issue with resetprop. This module and many others I've tried and use on v11.6, that utilises system.prop and resetprop work just fine.
Yes, when I tested your module my device wouldn't boot unless I removed the system.prop from the audmodlib. But I don't think that had anything to do with the system.prop itself, but rather what you'd put in it...
Didgeridoohan said:
I think you're making way to large assumptions here. From my experience, there's no issue with resetprop. This module and many others I've tried and use on v11.6, that utilises system.prop and resetprop work just fine.
Yes, when I tested your module my device wouldn't boot unless I removed the system.prop from the audmodlib. But I don't think that had anything to do with the system.prop itself, but rather what you'd put in it...
Click to expand...
Click to collapse
I'm not making assumptions. I'm literally telling you what issues I've experienced with my 9 modules and I'm not the only one It worked before 11.5/11.6 until I removed system.prop, which was the issue. The issue itself was not present before on previous versions. This was happening for me when upgrading to 11.6.
This is a reproduceable issue that was introduced once resetprop changes were introduced in 11.5/11.6 which did not occur before then, with the same exact zips updated to v3 module template. If you check the magisk release notes it CLEARLY states he made changes to resetprop. Which obviously confirms what I'm saying now.
Audmodlib lib has literally nothing in it that would bootloop your device. All it does is copy your system files into its own magisk folder. Nothing else. It makes ZERO edits to those files if you look at the code. The additional mods that edit audmodlib are what make edits to your existing device code.
I was just seeing if we could figure out a solution to this issue and to pinpoint why this is happening.
ahrion said:
I'm not making assumptions. I'm literally telling you what issues I've experienced with my 9 modules and I'm not the only one It worked before 11.5/11.6 until I removed system.prop, which was the issue. The issue itself was not present before on previous versions. This was happening for me when upgrading to 11.6.
This is a reproduceable issue that was introduced once resetprop changes were introduced in 11.5/11.6 which did not occur before then, with the same exact zips updated to v3 module template. If you check the magisk release notes it CLEARLY states he made changes to resetprop. Which obviously confirms what I'm saying now.
Audmodlib lib has literally nothing in it that would bootloop your device. All it does is copy your system files into its own magisk folder. Nothing else. It makes ZERO edits to those files if you look at the code. The additional mods that edit audmodlib are what make edits to your existing device code.
I was just seeing if we could figure out a solution to this issue and to pinpoint why this is happening.
Click to expand...
Click to collapse
I get it that you're trying to promote use of your own audmodlib template over the standard magisk template. Have you personally tried using *this* module *without* any other borked/broken modules? If so, please list the HW/SW (ROM, kernel, magisk and magisk manager versions, list of installed modules) combination which results in a bootloop.
PS. This is not a support thread for other broken modules.

please delete thread

Ainur JamesDSP is now available in Magisk Manager. Thanks to the devs for their great work. Enjoy!
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
Yikes. I wonder if AML doesn't support Pixel yet. I will look into it and add a note to the OP. Thanks for the heads up.
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
By the way, were you running any other audio mods at the time?
s8m said:
By the way, were you running any other audio mods at the time?
Click to expand...
Click to collapse
no
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
yung40oz84 said:
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
Click to expand...
Click to collapse
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
s8m said:
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
Click to expand...
Click to collapse
Great! Looking forward to it.
When users provide logs...
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users.
Click to expand...
Click to collapse
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
s8m said:
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
Click to expand...
Click to collapse
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
ahrion said:
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
Click to expand...
Click to collapse
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
s8m said:
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
Click to expand...
Click to collapse
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Since you're looking from outside, in. Was Unity easy to configure for you? The entire point for AML is to link everything to together for Magisk. Then we created Unity to be an all in one installer. Any AML modules are encouraged and welcome. Ainur is running AML currently.
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
s8m said:
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
Click to expand...
Click to collapse
Awesome. You can thank @Zackptg5
Another addition is SETools-inject for Android, that functions like sepolicy inject that MagiskSU/SuperSU have. Essentially, it allows rootless and other forms of root to also use it via init.d. As of yet, no one has actually used SETools for this.
We've also added init.d patching, for rootless and other root methods. Essentially, ramdisk will be automatically patched for AML system modules to use init.d (even if your rom didn't support it before). So init.d patch for all Android versions, MM/N+, has been added. Currently nearly all (if not all) init.d support is broken.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
Click to expand...
Click to collapse
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
24imelqui said:
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
Click to expand...
Click to collapse
It's not that he has been picky. It's just it takes some time to get approved.
Topjohnwu is a busy man.
BTW, Unity allows system mode installation natively if Magisk is not installed, includes addon..d as well.
Magisk is not required for any Unity zips.
ahrion said:
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Click to expand...
Click to collapse
It may be a dumb question, but does your Ainur JamesDSP module require Ainur or can it run independently without Ainur installed?

Show what modules you have

I think it's a good idea to share the magisk's modules we have installed.
-mi A1 gcam
-youtube vanced
Google lens enabler
Google sans mod font
HAL3 enabler
iOS11.1 emoji
Unified hosts adblock
YouTube vanced
Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)
AirAudio - stream your music!
Android O APT-X libraries
Audio Compatibility Patch
Mi Mix 2 Snapchat Volume Fix
Unified Hosts Adblock
ViPER4Android FX Materialized
Magic Charging Switch (mcs)
kremmit said:
Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)
Click to expand...
Click to collapse
Did you installed Xposed on MIUI?
Adriano-A3 said:
Did you installed Xposed on MIUI?
Click to expand...
Click to collapse
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?
kremmit said:
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?
Click to expand...
Click to collapse
I'm going to install it on MIUI 9.5.8.
Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
I'm on RR rom and it worked ok.
Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
Did it work for you? I'm still on 9.1 because I need Xposed.
kurtextrem said:
Did it work for you? I'm still on 9.1 because I need Xposed.
Click to expand...
Click to collapse
I didn't try. I sold my Mix 2.

[MODULE] Mega Audio Mod - A collection of mods to give you the best audio experience.

Before I start, I'd like to apologize if you don't understand something I say. English isn't my native language
Mega Audio Mod​Overview​
Improve your audio experience
Install Audio Modification Library
Install DTS:X Ultra
Install ViPER4Android
A wide majority of you are probably already familiar with most of what happens here, in fact this module happens to be a collection of pre-existing Magisk modules helping keep your audio experience the best your device can provide. I earlier had to go through the pain of installing all of these modules every time I changed a ROM. (Which happened once or twice everyday) I, thus decided to make a module that automates the process for me and installs everything I need. I plan to keep updating this and learn even more magisk development in the future
To do:
Add some presets to the viper directory in Android folder (once I figure out how to write to /data via magisk modules)
Add some more audio associated improvements
Add some more modules
If you happen to have any idea on how to write to /data via magisk modules please reply to the thread..
If you have any suggestions please reply to the thread.
Credits​ @Team_DeWitt \ ViPer4Android
@UltraM8 @Nemuritor01 @JohnFawkes @LazerL0rd \ DTS:X Ultra
@Zackptg5 \ Audio Modification Library
I am not able to post links for some reason so please cope with me and copy and paste what I type below
Download:
Source: github.com/Maitreya29/Mega-Audio-Mod
Download: sourceforge.net/projects/mega-audio-mod/files/
reserved
reserved2
Can't get Viper driver to install. Even in permissive Selinux. DTS works. On Pixel 5
Your Android version is and have you a custom rom with custom kernel on your device or using stock rom?A lil bit more info where great.Cheers!!!
-CALIBAN666- said:
Your Android version is and have you a custom rom with custom kernel on your device or using stock rom?A lil bit more info where great.Cheers!!!
Click to expand...
Click to collapse
Android 11 stock rom
Magisk canary
Pixel 5

Categories

Resources