Originally Posted by guitardedhero
I assure you guys I am not trying to frustrate you or flood this thread with another update, but I realized the Magisk installation was doomed if an existing Magisk module of any kind had an audio effects configuration symlinked to /system.
Today's build includes a lightweight and efficient audio effects configuration protocol for an audio framework for Magisk that I prepared a couple months ago that essentially "slipped in between the seats" while working on more than I should have at one time.
It took until today for it to dawn on me how essential such a component in /magisk is when dealing with the presence of anything added there by anyone and by any method.
I had to rewrite it from scratch tonight so it might be vulnerable to breaking by the flashing of additional modules that include an audio effects configuration, HOWEVER, my experience with Magisk suggests that the existing audio effects configuration(s) symlinked from /magisk to /system always prevail over future attempts (the reason why this audio effects configuration protocol is necessary) but likely prevents future modules using their audio effects configurations or just their edits (standard behavior anyway, not introduced from my protocol, just describing the landscape here).
My original framework included a script to handle the various configurations that may appear (from future installs) and merge additions as necessary upon boot, so this still needs to be done. Just bear with me, I've been in the hospital the past two days hanging out with my brand new son, Beau, who was born Friday morning (). I realized the previous builds were only successful (for Magisk) if no audio effects configuration already existed anywhere in /magisk, so I wanted to provide something that not only overcomes that obstacle, but preserve/restore the others as well.
...is there anything special to do?
Flashing process starts but stucks ..,
Nexus 6, Rom: Tesla, Oreo, September Patch, magisk 14