Only Caesium is confirmed to work with Omni Oreo, please search their thread refer to it...
Only a custom recovery is mandatory for kernel flashing, you don't need root to run a custom kernel but you'll need root for the corresponding kernel manager app to adjust the kernel settings according to your preferences, without it the kernel will run with it's default values...So,I never had tried to use kernels, the maximum I've did was flashing stock ROMs on my xiaomis, so I'm wondering if I need to root my device too flash the kernel, I've read in some forms that this isn't the case, but others said that indeed I need to. And if not, can I just but the fku and flash from there on my 3t? It'll work perfectly (regarding any but from the kernel itself)? I'm not totally fluent so it's kind of fatigating read, and reread the same text till a get it. And search those info here, is a bit hard... I'll keep reading, but if someone answer me, it would be great, just in case I don't find what I'm looking for...
Just check it out yourself, betas aren't officially supported and you should refrain from bug reports too when running beta but this doesn't necessarily mean it it's incompatible, according to my experience it works pretty well for the most beta releases - haven't checked out the current open beta with FK though but if something isn't working you can easily revert back by dirty flashing or restoring boot from within TWRP - for me personally it's only "better" to use stock if nothing else really worksI know that the Franco v36 isn't for the official beta 21 for OP3T, but I wonder if it's still "better" to use then stock, or if there are some mayor differences that will cause huge problems?
/Söder
this is der to a general problem of OB21. For any reason one partition is completely filled and so kernel or at least some drivers can't be stored or loaded afterwards. So in general OB21 is to be used as is, or better use OB20 if you want to modify things.I know that the Franco v36 isn't for the official beta 21 for OP3T, but I wonder if it's still "better" to use then stock, or if there are some mayor differences that will cause huge problems?
/Söder
Sent from my ONEPLUS A3003 using Tapatalk
blu_spark's kernel (don't know about others) does modify /system partition (which is impossible on latest OB without empty space, system partition is completely full by default now), I'm running another kernel atm (derp) which doesn't modify system and it works flawlessly, no problems, as franco never mentioned to use a similar approach (like blu_spark) I assume his kernel won't suffer from the same issue...this is der to a general problem of OB21. For any reason one partition is completely filled and so kernel or at least some drivers can't be stored or loaded afterwards. So in general OB21 is to be used as is, or better use OB20 if you want to modify things.
Gesendet von meinem Xperia Z3 Tablet Compact (Wi-Fi) mit Tapatalk
OT but there won't be issues with magisk as it's systemless, it's not going to modify system...I installed the Franco kernel and magisk and it works fine. Then I have uninstalled some system applications with Titanium Backup to avoid having an error with Adaway and magisk modules. For now everything works correctly.
OT but there won't be issues with magisk as it's systemless, it's not going to modify system...
Sent from my OnePlus 3T using XDA Labs
Well, I use both too but with Adaway ticked "systemless hosts" and osmosis busybox module from magisk repo (magisk manager -> downloads) and my system partition is still filled to the max... So if you use a systemless installation method for both you'll not run into any issues...Actually I only had problems when applying Adaway and trying to install busybox, which did need to have space in the system partition. I uninstalled some applications and it worked by having space.
No, there's only a OOS version for Oreo available...