I wanted to suggest having root rights on iodeOS. Having root rights gives the user full right privilages, which puts users in complete control over there device. Without root, Android (including iodeOS) becomes limited.
Yeah I get there are risks associated with it, however everytime an app requires root privilages you are prompted if you want to allow the app to use root privileges. One useful case is that users can use something like tatinum backup to restore or backup there stuff and it requires root rights.
And if it is a concern why not just have it disabled by default and through developer options the user can enable the ability to give apps root privileges? Or have a separate branch which has root rights. I am pretty sure most users using iodeOS are not novice users and are technical so I just don’t see how having no root is beneficial.
I understand Magisk can be flashed with iodeOS, however users can’t receive OTA updates. That is why I am suggesting it.
? My device is rooted with Magisk and I receive OTA updates. Just updated to 3.3. The only thing which has to be done afterwards is to patch the new recovery with Magisk
Yes, but that is no big thing.
Load the new recovery from Github, patch it with Magisk, copy the file to a PC. Boot to Bootlaoder and flash the patched recovery with fastboot.
Good question, I don’t know. I updated recovery because I don’t know whether there are any changes in the recovery versions. The developer should answer this question.
There is a post-install management mechanism in LineageOS (and thus iodé). Some scripts are installed in /system/addon.d, are saved before flashing a new rom update, and then executed after updating. Magisk installs a survival script in this place, which patches the kernel after an update, so there’s normally no need to flash Magisk after each update.
How can I start this survival script? After each OTA update, the Magisk app was still there, but no root access. Patch recovery as described in #3 works, but if there is an easier way, tell us
I’m not an expert about magisk (and we do not officially support it). There are apparently plenty of particular cases… We can hypothesize though that the survival script is not copied into /system/addon.d. Maybe, if you patch the kernel and then flash it back, there’s no magic to later on copy the survival script. But what I’m sure is that if you manage to sideload magisk, the survival script is copied.
You should try to sideload the magisk apk instead of patching yourself the kernel. I think it works on most if not all the devices we support, and installs the survival script.
