Originally Posted by osm0sis
Not an old thread at all!
Magisk's new addon.d ability used my work on FlashAfterUpdate, which is cool, but it does make it unpredictable results since it uses the same wait time as mine so both could be running simultaneously.
I've got an updated FlashAfterUpdate to work around that (1 second longer wait, and continue to wait if it's detected that Magisk's addon.d is in the middle of doing it's thing). I'll have it out when I put out busybox and some other updated goodies.
As for your idea, no.. way overcomplicating things. Rename the files under /sdcard/FlashAfterUpdate with 01- 02- etc. to dictate the order is the most obvious solution.
And for your reflashing Magisk issue, I'd suggest your kernel use AnyKernel2 so the Magisk changes remain intact through updates. If it's official Franco Kernel that should already work.
So my problem is that if I flash an updated version of FK, I will lose root (irregardless of magisk's addon.d, which makes sense since I am not updating the system). The only way to fix this is by reflashing Magisk.
So now, when I have CyanDelta install FK kernel, I must have it install Magisk.
However, it gets tiresome constantly renaming both files and moving it into the CyanDelta folder, since both are not on the same release schedule (understandably) .
I can always use the addon.d you made to keep my current kernel and use the magiskSU addon.d to keep that as well. However, if a new kernel is released, I need to flash that and magisk again manually (nothing is automated).
Essentially, I would like a way that I can have Magisk and FK updater to download the newest file when it comes out and when I hit install in CyanDelta, everything new gets installed. I'd like to do this without having to rename and manually moving the files (the kernel and magisk) into they cyandelta folder.