Or is the default (interactive) settings recommended?
Attachments
-
225.1 KB Views: 972
This is one of those install and forget type of kernels. Honestly, you wouldn't have to alter any kernel settings. Everything is already optimised. I would recommend doing a couple of charge cycles on default settings and see how you go. You'd be surprised.Or is the default (interactive) settings recommended?
Alright, I'll give it a shot! I flashed Franco for the first time today so I'll give it a couple of cycles.This is one of those install and forget type of kernels. Honestly, you wouldn't have to alter any kernel settings. Everything is already optimised. I would recommend doing a couple of charge cycles on default settings and see how you go. You'd be surprised.
That's subjective. Battery life is completely unrelated. But performance is hard to gauge.Would changing io to deadline from noop , as well as increasing the value to 512kb affect the battery/performance?
thankyou Franco,your love for the kernels has always been the bestNow that Oreo is out I'll be starting FK from scratch (as I always do).
Expect at least 24-48 hours for a new build.
Thanks! I have a question, you will update this kernel with every security mounthly release? Or we need to flash the ROM with the new security update, and the kernel again to have the latest security patch?Now that Oreo is out I'll be starting FK from scratch (as I always do).
Expect at least 24-48 hours for a new build.
Really was supposed to be inverted and 999 is # of da beast aka Franco KernelPage 666.
If you're talking about the procedure of updating a custom rom, then you need to flash the custom kernel after every update since it rewrites to the kernel included with the rom.Thanks! I have a question, you will update this kernel with every security mounthly release? Or we need to flash the ROM with the new security update, and the kernel again to have the latest security patch?
I assumed the same thing viewing the changelog, but until Franco starting to ask money for the answers i send that question hahaIf you're talking about the procedure of updating a custom rom, then you need to flash the custom kernel after every update since it rewrites to the kernel included with the rom.
If you're talking about using just stock, probably the same since the kernel gets updated too(based off the changelog of franco.kernel, I'm assuming the stock kernel might be included in the small updates).
I'm unsure about how Oreo updates work though. I wanna see it in action, unless it's the same as the previous versions of Android. [emoji848]
Sent from my Nexus 6P using Tapatalk
getting reboots after 2 minutes or soAnd r56 for Oreo is out!You can easily auto-flash it from my app! Enjoy!
Got the same here (stock ROM). System info tells me that your kernel is installed though, and it seems to work fine.just a heads up Franco,, updater app says r1 for kernel after 56 flashed and i rebooted a few times to see if that was it, does the app need to be updated also?? ty again dude