Audio Modification Library Ryuki Mod is a compatibility layer for supported Android audio modules that need to edit the same effect configuration files. Based on the framework created by Zackptg5 and ahrion, it collects participating modules' changes so one audio mod does not simply replace another.
A Shared Layer for Audio Mods
AML coordinates common audio-effect files while the individual sound modules continue to provide their own libraries and processing.
Configuration Merging
Supported modules describe their required audio libraries and effects so AML can preserve multiple registrations in the resulting configuration.
Additional Mount Paths
Ryuki Mod adds bind-mount handling for audio files under locations including /odm/etc and /my_product/etc.
Modern Root Fixes
The fork includes fixes for newer Magisk versions, NoMount setups, permissions, SELinux-related command failures, and certain audio-service restarts.
When AML Is Useful
AML is relevant when two or more installed sound modules need the same audio_effects configuration. Without coordination, the module mounted last can hide the previous module's version, leaving one effect unavailable even though both packages appear installed.
A sound module must already be registered in AudioModificationLibrary.sh or provide its own aml.sh integration. AML cannot automatically make every unregistered audio port compatible, and it is not itself an equalizer or sound-enhancement engine.
Ryuki Mod Behavior
This branch supports modules that place audio files during post-fs-data.sh, avoids changing spatializer and haptic effect XML files that are known conflict points, and reapplies file permissions during early boot. Its metadata still directs in-manager updates to the official AML project.
Consequently, the Ryuki build must be obtained and updated through its own download channel. Review the installed version after any manager-driven update if you specifically need the fork's behavior.