[KERNEL] [Flounder] FIRE-ICE Kernel

ATTENZIONE NE IO NE IL FORUM CI RITENIAMO RESPONSABILI PER EVENTUALI DANNI ARRECATI AL DEVICE
CHI ESEGUE QUESTA PROCEDURA LO FA A PROPRIO RISCHIO E PERICOLO​

Codice:

[B]KERNEL[/B]
-| -O2/-O3 hybrid
-| Linux 3.10.94
-| SELinux disabled
-| build optimizations
-| debugging disabled
-| Brightness control
-| 2.0A charging
-| USB fastcharge
-| Full [URL="http://forum.xda-developers.com/showthread.php?t=2196707"]DriveDroid[/URL] support
-| fsync options
-| latest f2fs
-| intelli_plug
-| Frandom
-| crypto improvements
-| latest zram
-| TCP configs
-| UKSM
-| CIFS
-| others.. A lot

[B]OTG FILE SYSTEMS[/B]
-| NTFS
-| exFat

[B]I/O Control [/B]
-| VR
-| SIO
-| ZEN
-| BFQ
-| CFQ
-| FIFO
-| Noop
-| FIOPS
-| Deadline
-| SIOPLUS

[B]OVERCLOCKING[/B]
-| CPU OC 2.5Ghz
-| GPU OC 0.984Ghz

[B]RAMDISK[/B]
-| None Encrypted /data support
-| universal cache mounting / any file system
-| mount optimizations
-| unrestricted adb
-| init.d 
-| FI.d

built with SaberMod 5.3.x toolchain
you can get the toolchain [URL="http://sabermod.com/Toolchains%20%28DEV%20ONLY%29/aarch64/aarch64-kernel/"]here[/URL]

DOWNLOAD

download kernel e recovry

AOSPM è per le rom AOSP o basate su di essa
AOSPML è per alcune rom AOSP (usatelo se AOSPM non vi va)
CMM è per le cyanogenmod e derivate

INSTALLAZIONE

1. E' consigliabile mettere la twrp dark materialized fornita dall'autore del kernel
2. Copiare il kernel sul nexus
3. Riavviate in recovery
4. Flashate il kernel
5. Fate un wipe cache e dalvik cache
6. Riavviate

Fonte: xda​

 

Q/A
Q; la recovery va in bootloop.
A; flashate la twrp consigliata.

Q; quando flasho un altro kernel il mio n9 va in loop
A: fate un installazione pulita

Q; qual'è lo stato del kernel
A; experimental. il dev testerà varie cose e può essere che ci saranno problemi

Q; con cosa posso gestire il kernel ?
A; https://play.google.com/store/apps/d...ladiutor&hl=en

 

*** nuova build ***

k10
-| complete redo of everything
-| added: intelliactive
-| Linux: 3.10.95
-| FI.d: v38
-| dropped: intelliplug
-| latest from google
-| other's dont remember

 

*** nuova build ***

K10.0.2
-| Linux 3.10.96
-| testing fix for battery log
-| FI.d: v39
-| testing fix for freezes v2
-| removed: "lmk tuning for zram" :: needs more testing
-| readded: intelliactive :: sorry about that

 

*** nuova build ***

K10.0.3
-| latest: from google
-| some: optimization/changes :: testing
-| re-enabled: memory control groups
-| some: under the hood changes (mm stuff)

 

*** nuova build ***

K10.0.4

-| latest: from google
-| FI.d: v40
-| add: lmk control for swap :: look in FI.d
-| some: cleanups

 

*** nuova build della twrp ***

R12.T2
-| kernel: updated as to K10.0.5 (as of now)
-| TWRP: updated to 3.0.0-2

 

*** nuova build ***

K10.1.0 will most likely be my next update.
The main change that it will have is "Search and Destroy" (get the reference)
What that means is that I will go through every single commit making sure its working and applied.
Before I was a little bit, too much hack and slash he he (My bad ) so things most likely got broken,
that could explain all the reboots people have been having... And like always I don't get them lol my N9 is unbreakable!
So the next update could take a little while/or not as I go through all the commits (2000+) it all depends on how much I can do a day.

 

*** nuova build ***

K10.1.0
-| Linux: 3.10.98
-| latest: from google
-| some: reboots fixed

 

[QUOTE = "simoscorpion, post: 408140, member: 34213"] Q / A
Q; the recovery goes bootloop.
TO; flashed the TWRP recommended.

Q; When he flashed another kernel my n9 goes in a loop
A: you do a clean install

Q; what is the state of the kernel
TO; experimental. the dev will test various things and it may be That there will be problems

Q; with what I can handle the kernel?
TO; Kernel Adiutor [/ QUOTE]

Thanks for Mentioning my app Kernel Adiutor