Last time we covered how to install the glitchy Kernel and today we are back with a few more features of the same kernel. If you haven’t read our earlier post, hop on over to this link to find how you can install this bad boy on your very own tablet.
Based on Google AOSP 3.4.0 kernel source for MSM devices (AOSP variant)
Based on CyanogenMod’s kernel source for MSM devices (CM variant)
CPU OC up to 2.3Ghz with OV/UV support / minimum frequency down to 81 MHz (configurable)
L2/bus speed OC up to 1.49GHz / 4.8GBPS
GPU OC up to 627 MHz with OV/UV support
CPU governors : Faux’s intellidemand, interactive, ondemand (default), smartmax, smartmax_eps, intelliactive, conservative
I/O schedulers: noop, deadline, row (default), cfq, fiops, sio
Kernel based thermal control by crpalmer and flar2
Kernel based msm hotplug driver by Fluxi
Kernel based Intelli-plug hotplug driver by Faux123
-tni.andro’s battery life extender support
-Latest Sweep2wake/Sweep2sleep/Doubletap2wake from flar2
Magnetic on/off setting
SLIMbus OC by ZeroInfinity and Poondog
Panel color and gamma tweaking by Faux123
Dynamic Fsync by Faux123
USB fast charging support
USB OTG charge hack support by flar2
Kali Pwn Pad experimental support
Optimized algorithms and libraries
Various performance and power saving tweaks
NTFS, NFS and exFAT support
F2FS support up to all-F2FS with automatic ramdisk patching at flash time
Touchscreen patches from Showp1984
Aroma installer to set core features at flash time (L2 OC level, CPU OC, etc.)
Wifi firmware overrider to fix wifi on 4.4.3 & lower or on roms using old wifi firmware
Compiled with Cortex A15 optimized Linaro 4.9.2 toolchain using -Ofast optimizations
For Lollipop :
cernekee’s PIE bypass patch (Disabled by default, can be enabled in Aroma)
SELinux Permissive patch with system R/W access (Disabled by default, can be enabled in Aroma)
Chainfire’s partial root patch.
What do I have to do to use F2FS on one (or more) of my partitions ?
First, BACKUP your data if needed, especially if you’re planning to use F2FS on DATA partition, as changing filesystem will wipe the partition. Next, if you’re planning to convert your system partition, you’ll need a ROM that will use F2FS format (you can modify the install scripts yourself to get this part). The last thing to do is to flash any Glitch kernel with a revision number past r150. You can restore your settings from SDcard if any, the install process will detect the partitions and modify the ramdisk so you can finally boot your system and use your fresh FS. Keep in mind updating your rom will require to repeat the whole process so the best thing to do I guess is to convert only data and cache as F2FS, and to keep system as ext4 so you can update your rom just like before.
What hotplug driver should I use ?
It all depends on your tastes, but basically, Qualcomm MP-decision is the default, not so great binary-based driver you may not want, but it works nonetheless, Fluxi’s MSM Hotplug tries to mimic it somewhat with a kernel-side implementation and an improved design, better battery usage and performance (that’s the one I recommend for most users), and then we have Faux123 Intelli-plug, kernel-side implementation as well, more battery friendly oriented at the cost of a small performance hit you may not notice. The choice is all yours, they are all valid options ! Try and keep what you prefer.
Is my Nexus overclocked if I flash this kernel ?
When you’ll flash this kernel, the Aroma installer will ask you what settings you want so you can tweak it as you want it. You’re not forced to choose an overclocked frequency for the CPU, the GPU or bus/L2. Stock values are explicitly noted as is in the installer.
Can I change kernel settings I was able to tweak in aroma without reflashing ?
You can for everything but CPU and bus/L2 OC settings. You’ll need to open /system/etc/glitch-settings.conf and tweak it as you want.
In TWRP recovery, after I’m done flashing the kernel I get a black screen ! Help me !
The issue is linked to the use of Aroma installer on TWRP that will trigger a screen timeout when it shouldn’t. In TWRP settings, search for screen timeout option and disable it. It should now work normally with Aroma.
This brings us to an end of this article if you have any questions about any of the settings please leave a comment down below and we will try to help you out!!