Closed Zenlua closed 7 months ago
This willl break TWRP backups, people still don't understand this..... Already doing twrp backups with KSU became impossible, and kernelsu workarounds on the wiki don't work as if you shrink the modules image the modules break, so no doing this change is simply nosense in my opinion. The only thing would be to offer the choice to the user to do this or not maybe but for example I wouldn't as then twrp backups would become unfeasible and them are more important than some stupid module honestly (at least for me)
agreed, this is why i switched from ksu to ap
I really don't know how to pray APatch creator to close this as unfeasible..... Please don't ruin apatch as well.....
If you don't want to increase the size of the img module file, then delete the img module because it's not suitable. If the module is faulty, leave it like magisk.
it really hard to handle that 1T sparse file, i tried to do a backup under recovery, but native twrp doesnt work (size exceeded). i backup with tar (sparse file supported) and it took more than an hour to complete, just the adb folder!!
so pls dont go back to sparse file
我拒绝😡
it really hard to handle that 1T sparse file, i tried to do a backup under recovery, but native twrp doesnt work (size exceeded). i backup with tar (sparse file supported) and it took more than an hour to complete, just the adb folder!!
so pls dont go back to sparse file
Just compress module.img into zip and delete module.img it won't take up space.
not consider
Add storage like ksu to avoid the problem of not enough throughput if the flash module is heavy.
If you remove module.img so that the directory is the same as magisk, even better