{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD
HERE
Google Drive mirror
I'm not responsable for data loss or any damage to your phone if you're using my kernel. You flash this at your own risk. Always make a backup!
(You need SuperSU 2.50 for this kernel to work!)
M/6.0 kernel:
Features:
new name: almost-stock, since it's... almost stock, but not really.
built on the base of latest Android 6.0 release, merged with franciscofranco's L kernel and CM/CAF12.1
built with -mcpu=cortex-a15 for enabling maximum performance with our Krait CPU.
reduced wireless wakelocks
underclocked GPU idle (GPU min/max 20/450MHz)
default CPU governor: CAF interactive, updated from CM/CAF12.1 branch.
built with cpu-boost driver to handle touchboost, default touchboost is set to 500ms and 1.2GHz
Motorola memory patches for ARM
default hotplug: MPDecision with updated rq_stats from CM.
I/O default schedueler: row
the famous I2C @ 19.2MHz, plus some other chips dropped at 19.2MHz and voltages lowered for internal components (Cl3Kener)
compilled with Linaro GCC (5.2.0) - arter's own build.
removed useless debug
workqueue udates from linux 3.7, power saving workqueues set on by default
selinux enforced (You need SuperSU 2.50 for this to work!)
partialsuspend enabled
various updates and fixes for net, mmc, thermal, selinux, block, cpufreq, sched, rcu, block
I probably forgot something
Credits:
neobuddy89, dorimanx, hellscore, franciscofranco, flar2, Cl3Kener
Christopher83 for Linaro GCC binaries, tutorials on how to compile Linaro, his Linaro binaries and tutorials
other people who work on Linux kernel.
arter97 for his GCC 5.2.0
Kernels from where I cherry-pick: Chaos/Hybrid - neobuddy89, Uber - Cl3Kener
Other guys from where I might cherry pick in the future.
Sources:
Kernel: ttps://github.com/StefanescuCristian/hammerhead
Ramdisk: https://github.com/StefanescuCristian/ramdisk_hammerhead
Toolchain:
https://github.com/arter97/linaro-lto
The attached images are from the KK version.
Oh, and if you want to build this for yourself, check this out!
XDA:DevDB Information
[KERNEL] [6.0] almost-stock (aka ex big-bum), Kernel for the Google Nexus 5
Contributors
big_bum
Source Code: https://github.com/StefanescuCristian/hammerhead
Kernel Special Features: GCC5
Version Information
Status: No Longer Updated
Current Stable Version: 2
Stable Release Date: 2015-11-01
Created 2014-07-07
Last Updated 2015-11-01
Reserved
Old kernel info:
Which version do I need?
It's pretty simple and I think I structured the download sites pretty good. If you want another structure or you have ideas for improvements, then feel free to post them. Anyway:
For AOSP based ROMs (Mahdi, Paranoid, Liquid Smooth, etc) use the AOSP folder. If you didn't change the ROM to support f2fs or f2fs-all, you must use ext4 or mpd*.
For Cyanogenmod based ROMs (CM, Carbon, AOKP, etc) you must use the kernels from the CM folder (cm or cm-mpd) . You can flash a f2fs version on CM. Read post 2, the Q&A section.
*mpd stand for MPDecision (make poor decision). It's qualcomm's user-space implementation for plugging/unplugging the cores. Some people say it's bad, some people say it's good. I personally like it and use it
Reserved
Lollipop Kernel
Features:
backports from upstream for most of main components
exfat for mounting exfat formatted sticks via USB OTG
f2fs for mounting f2fs formatted sticks via USB OTG or if you have an f2fs formatted internal memory (use the same image for all combinations of f2fs formatted partitions).
for mounting OTG sticks formatted in NTFS/exFAT/f2fs/other filesystem I recommend this app. FAT formatted sticks will automount if you use CM (might work on AOSP too, I haven't tested it)
I also include cherry-picks from other N5 kernels (especially from Chaos/Hybrid - @neobuddy89, Uber - @Cl3Kener and Code_Blue - @eng.stk)
min default CPU freq: 300MHz
max default CPU freq: 2.26GHz
default CPU governor: impulse
available CPU governors: ondemand, bacon, performance, powersave, interactive
hotplug: msm_hotplug developed by myfluxi
cpu-boost driver from CM.
I/O readahead size: 512KB
I/O default schedueler: fiops
other available I/O scheduelers: noop, deadline, cfq, BFQ, tripndroid
GPU min/max 20/450MHz
GPU default governor: simple
other GPU available governors: ondemand, performance
color profiles. Based on franco, works with FKU or Nexus Display Control app.
savoca's KCAL
franco sound
CM sound patches
dynamic fsync
various memory improvements. This doesn't mean less consumed RAM, also free RAM is wasted RAM for linux. Also, read this: http://www.linuxatemyram.com/
msm limiter (limits screenoff freq to 1.2GHz)
KSM: Kernel Samepage Merging.
KSM merges memory pages from one app with another app, thus only loading one memory page, not two pages that are the same.
Let's say that app A has the page X loaded in memory. Let's say that app B loads pages X and Y in memory. KSM detects that and points app B to the memory address from page X loaded by app A. In the end we have this:
Without KSM:
A: X
B: X, Y
Total: X, X, Y
With KSM:
A: X
B: ^, Y
Total: X, Y
Click to expand...
Click to collapse
the famous I2C @ 19.2MHz, plus some other chips dropped at 19.2MHz
HTCP as default TCP congestion control. (I personally don't see any differences between different TCP Congestion Control algorithms)
other TCPCC available: reno, bic, cubic (I used this in DD-WRT), westwood (they say it's good for wireless/3G/4G devices), vegas, veno
compilled with latest Linaro GCC (4.9.3), and with SaberMod
removed useless debug
I probably forgot something
Q&A
- Is it stable/bug free?
- As stable/bug free as franco's kernel is.
- Does it score better in benchmarks?
- I think so. At least Antutu says so, in the integer and float benchmarks. Quadrant also says this. It's not a huge difference, and you can't see it with the naked eye. But I don't trust in benchmarks that much.
- How's the battery life?
- (From Reddit) "The same battery life you get with Franco, if not a little better. Optimization means better performance, better performance means less time executing the same code, less time online means more deep sleep. Idk how much better it is, but it's not worse, anyway."
How can I configure it?
1. Universal Kernel Manager (Synapse + Script). Flash kernel, flash the zip from the link, install Synapse. Read here for more info on frequency getting stuck at 1.2GHz. TL;DR: go and setup via Synapse how you want, then go to CPU Tab, set minimum freq to 300Mhz, apply, enjoy.
2. FKU
3. Kernel Tweaker
4. Trickster Mod, via scripts in init.d, etc.
Recommended & tested ROMs:
Optipop
SlimAOSP
Terminus
Blisspop
This doesn't mean that ROMs are not supported, jus that I haven't tested them. The ROMs from this list are working as they should with my kernel.
Rollback:
Rename /system/lib/hw/power.msm8974.so.bak to /system/lib/hw/power.msm8974.so
Rename /system/bin/thermal-engine-hh-bak to /system/bin/thermal-engine-hh
Reboot to the bootloader and flash stock Kernel by downloading the Nexus images and then fastboot flash boot boot.img
Start the phone
Reboot to bootloader again and flash what kernel you want, and then start the phone.
Special thanks for testing and help:
@_MirageX_ @dox81 [mention]@pianistaPL[/mention] [mention]@shadowdevil[/mention]
Special thanks for donations:
[mention]@Paddybecks87[/mention] and the guy from reddit (notable-_-shibboleth) who also uses my build of pf-kernel for Ubuntu. (If you see this and you have a XDA username, give me a PM to put you in the list here)
Sources:
Kernel: ttps://github.com/StefanescuCristian/hammerhead
Ramdisk: https://github.com/StefanescuCristian/ramdisk_hammerhead
Toolchains:
Linaro: https://github.com/Christopher83/arm-cortex_a15-linux-gnueabihf-linaro_4.9.git
SaberMod: https://github.com/AuxXxilium/sm-arm-cortex_a15-eabi-4.9
BbKT (Big bum Kernel Tweaker): https://github.com/StefanescuCristian/android-kernel-tweaker
fabi_92 said:
I use big bum as primary but with some secondary rom and some kernel doesn't work.
FIX:
-flash rom
-flash gapps
-flash big-bum
-flash zip EXT4 or F2FS
-done
Click to expand...
Click to collapse
Old kernel info:
I said last night that this kernel works on CM.
First of all, CM is CAF. Our kernel is not CAF. This means that some libraries are not compatible with our kernel and need to be changed to make it compatible. This is exactly what Calkulin made. He made a zip that contain non-CAF libs to boot stock AOSP kernels.
I took that zip, modified it and put our kernel in it. This is more like a hack, it's not the real CAF kernel!
Also, in the OP I said that this isn't CAF-compatible by default. This is what I was talking about. With a little hack, it can run on CM.
This has nothing to do with the kernel. It's all in the libs. I only made a simple/easy/convenient way to flash CM and this kernel together.
How to:
Scenario 1: You don't have CM installed, you want to install it.
1. Download CM(tested with 07.07 nightly) or CM-based ROM zip. (In theory it should work)
2. Flash CM/CM-based ROM, gapps. Read the ROM OP for more details.
3. Flash the latest kernel/zip from CM folder.
When updating the ROM, you must reflash the kernel zip file from CM folder.
When updating the kernel, you can flash the normal ext4 version (zip or img from AOSP folder), or the hacked CM one (the zip from CM folder).
Scenario 2: You have CM and you want to try this kernel.
1. Download and flash the kernel/zip from CM folder.
When updating the ROM, you must reflash the kernel zip file from CM folder.
When updating the kernel, you can flash the normal ext4 version (zip or img from AOSP folder), or the hacked CM one (the zip from CM folder).
QA:
-f2fs/f2fs-all version for CM?
-No.
First of all, CM formats partitions to ext4 when flashing. You must edit your updater-script for it to work. If you know this, then you know what I'm talking about in the next 2 paragraphs.
Second, you can make a flashable zip by yourself.
Third, it's easier to download the zip from the thread and flash it, then flash a f2fs/f2fs-all kernel. (AOSP folder, zip or img)
You just have to be carefull that if you're on f2fs-all, you must edit META-INF/com/google/android/updater-script from Calkulin's zip file: replace ext4 with f2fs. Repack, flash your zip, flash f2fs/f2fs-all kernel, enjoy.
-I have done what you said. I now run CM on f2fs/f2fs-all. What do I do in case of an update?
-Well, it depends.
For ROM update:
1. Flash CM ROM.
2. Flash the zip you made and flashed when you asked the previous question (third point)
3. Flash f2fs/f2fs-all kernel
For kernel update:
1. Flash the appropiate f2fs/f2fs-all kernel. (AOSP folder, zip or img)
Credits: Calkulin for his thread, zip, files and discovery.
That's cool man ! Thank you for sharing this with us !
Sent from my Nexus 5 using XDA Free mobile app
Nice one
Sent from my Nexus 5 using Tapatalk
Thanks for sharing your kernel with us. Specs and notes sounds great, looking forward to running this.
-Sent from my Almighty Nexus 5 Hammerhead using XDA Premium 4 mobile app
Best kernel in 'da hood !
WoW !
Downloading. :good:
No disrespect, but since this is based on Franco this should be in Android Development. The mods will more than likely move it there soon.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Welcome and very nice OP
Best kernel name by some margin.
This thread must be moved to Android Development as there are no "original" features here. Read rules before posting bro
Enviado do meu Nexus 5 através de Tapatalk
No problem man. I'll report myself and tell a mod to move it.
EDIT: It's already reported.
Dude take it easy "bro"..why do people get so upset?!? It's a freaking website forum...nothing more..people already mentioned it before you in a much much nicer way...thanks for the work OP it's great
Sent from my Google/LGE Nexus 5 Hammerhead
I really didn't get upset.
I didn't know how else to move the thread, so I thought that reporting it is the way to go.
Nice I'm gonna test it out great work man
Btw can live without it but gotta ask is dt2w included?
Sent from my Nexus 5 using Tapatalk
big_bum said:
I really didn't get upset.
I didn't know how else to move the thread, so I thought that reporting it is the way to go.
Click to expand...
Click to collapse
@big_bum hey sorry man I wasn't talking to you...I was talking to TomorrowLand_Ace
Sent from my Google/LGE Nexus 5 Hammerhead
Nice
Sent from my Nexus 5 using XDA Premium 4 mobile app
Sounds awesome, trying out this kernel NOW! Thanks for sharing
Sent from my Nexus 5 using Tapatalk
idriff said:
Nice I'm gonna test it out great work man
Btw can live without it but gotta ask is dt2w included?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No. But if you want dt2w you can use Linaro. You'll loose bfq and franco sound patches.
Dt2w or s2w will never be great on this phone because of battery drain.
But we have a hardware pedometer in our phone, so theoretically all the apps that are tracking step numbers should not use any battery at all because they are not using the accelerometer. I guess we can't have it all.
Sent from my Nexus 5 using Tapatalk
Related
Info & Thanks
What you need to know before you use this kernel.
This kernel got Selinux Permissive state as it supports more apps like TiTaniumbackup.
Reverting back to a Selinux enforced Kernel (stock) is no longer a problem from Rev3.0 and up.
You can set Selinux Status with the included Synapse app
You want to know why this kernel comes with Selinux included, google for Selinux and search your answers.
AllCast mirror will not work as this is a Samsung thing and not opensource.
If this is a problem for you, don't use this kernel.
DISCONTINUED , A NEW THREAD WILL BE OPENED FOR THE NEW KERNEL SUPPORTING ONLY THE KITKAT BOOTLOADER.
NO JELLYBEAN BOOLTOADER SUPPORT, IT IS TIME TO MOVE FORWARD.
INSTALLATION
Take a full nandroid backup.
NO NEED TO BE ON ANY KITKAT BOOTLOADER (your wifi will work with this kernel)
YOU NEED TO BE ON A KITKAT TOUCHWIZ ROM.
Install with cwm
Thanks:
sidmoraes for pointing me to other kernel source that I could use as base, still had to change some stuff but this is better then waiting for samsung to release there source, if they ever will. (Finally Samsung released source)
Andreilux - Faux123 - Yank555.lu for kernel work
ZaneZam for the zzmoove governor
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This kernel comes with the policy: IT IS AS IT IS.Use at your own risk
Take a Nandroid backup of your system and of your boot.img
You need to be on custom cwm to install this
ONLY FOR SAMSUNG TOUCHWIZ BASED KITKAT ROMS
Benchmark scores:
Stock Normal Note8.0 Antutu Ranking. 17708 points
My Antutu = 23486 points
Stock Quadrant ranking = 6613 points
My Quadrant = 13685 points
CivZ-SphereKat-REV5.4-GT-N5110-5100/5120 And older versions.
Never install a kernel that is not for your device, it will cause a hard brick.
Stock kernels can be found in the SphereKat folder of your device
The only good app to control this Kernel is the included SYNAPSE appExample of what synapse looks like,THIS IS JUST A EXAMPLE.
SphereEngine KERNEL Features
If you change nothing these are the following Features/optimisations you get compared to Stock:
SELINUX protection included but set at Permissive = No problems wit apps like Paragon and Titainium.
SELinux control with Synapse
S-Pen Alignment fixed
Default Speeds 200MHz-1600MHz
Activating Saving power will result into 200MHz-1100MHz.
GPU Overclocking thanks ZaneZam / DerTeufel / AndreiLux
GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel
Init.d support
ARCH-Power enabled
DynamicFSYNC = Use Terminal command or Trickster Mod app. = enabled by default.
Memory Leak fixed
mmc cap erase disabled ( just as a precaution )
[*]IKCONFIG_PROC support
Driver support included in kernel:
NTFS_RW / FAT / FAT32 / EXFAT support
3Gusb Support (ppp widget)
CIFS / UFS / ISO9660 / UDF_FS / HF / HF_PLUS
Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter support
Ralink driver support : Ralink rt2500 (USB) / Ralink rt2501/rt73 (USB) / Ralink rt27xx/rt28xx/rt30xx(USB)/rt2800usb - Include support for rt33xx , rt35xx , rt53xx
Extra Drivers: MAC80211 / RTL8187 / EEPROM_93cx6 Support
Boeflla 1.6.0 Sound engine support
OTG Audio dock , Car dock support
[*]SideSync support
[*]Dynamic Samsung Hotplugging
Note on CIFS:
Example on what you enter, but your IP and share, if that wasn't clear. The option section is very important
Note on NTFS
You need to use Paragon!
You need to set your mount point yourself.
Example and recommended is:
Code:
/mnt/extSdCard/paragon
Advanced users support
OC & UV support for CPU
Max CPU speed is 1920MHz
Min CPU speed is 100MHz
Governors: Adaptive, Pegasusq (recommended), Performance, Ondemand, Interactive.
Schedulers: cfq, Noop, Deadline, Row, Sio, VR
Extra TCP wifi connection added: Westood, reno, htcp, vegas, veno.
Changelog:
07/Jun/2014 First Public release Rev2.0
08/Jun/2014 First Public release Rev2.1
[*]GPU step 5 included, now max it will go to 533MHz
[*]Auobrightness sensor fixes part2
[*]CPU sloop adjusted
[*]zzmoove profile nr8.
09/Jun/2014 First Public release Rev2.2
[*]Memory Leak fix cpu stats
[*]Memory Leak fix Kernel Ext4 & Power
[*]zzmoove profile nr6.
I recommend not to use Interactive and Powersave governor as they are buggy.
09/Jun/2014 First Public release Rev3.0
[*]Selinux included in the kernel as more security is better. This is the reason why I bumded to Rev3.0 to make a clear difference.
This kernel got Selinux Permissive state as it supports more apps like TiTaniumbackup.
Reverting back to a Selinux enforced Kernel (stock) is no longer a problem from Rev3.0 and up.
You can set Selinux Status with terminal command to ENFORCED with "setenforce 1". Or use a init.d script to have it on reboot also on ENFORCED.
You want to know why this kernel comes with Selinux included, google for Selinux and search your answers.
[*]Governors , powersave, userspace = Disabled as they are useless and buggy.
10/Jun/2014 Rev3.1 Released:
Ramdisk changes
Interactive set on all parameters as startup and default governor, this to prevent lockup of cores on boot.
Synapse SELinux status oprion, change to ENFORCED & PERMISSIVE , default is permissive
Small tweaks in kernel boot_up custom script.
12/Jun/2014 Rev3.2 Released:
Ramdisk changes
CPU freq rework to solve the hotplug problems
zzmoove and interactive removed = I strongly recomment pegasusq
Synapse Global voltage control added and some more info stuff
Github source updated
13/Jun/2014 Rev3.3 Released:
Ramdisk changes
Revert CPU freq rework to solve the hotplug problems
Compiled with Samsun Dynamic Hotplugging to resolve this problem
Synapse GPU info added
15/Jun/2014 Rev3.4 Released:
Bus_freq changes
A ton of missing driver commits for the KONA device added
Autobacklight 0.0 lux light problem fixed, no it works correctly even in a dark room
That is the problem working with a kernel that isn't for this device. You need to debug and add the stuff that is missing.
18/Jun/2014 Rev3.7 Released:
N5100 support added = no testers pm'd me so this is experimental
N5120 support added = no testers pm'd me so this is experimental
Ramdisk changes and github updated
20/Jun/2014 Rev3.8 Released:
Hotplug rework
Ramdisk changes for the s-pen
28/Jun/2014 Rev4.0 - 5110 Released: (support for the 5100 & 5120 will follow later)
Merged with official Samsung KK source = fixes all existing problems with wakelock and many other optimizations for our device
29/Jun/2014 Rev4.0 - support for the 5100 & 5120 added
Merged with official Samsung KK source = fixes all existing problems with wakelock and many other optimizations for our device
Github updated
02/Jul/2014 Rev4.1 - support for the 5110 , 5100 & 5120
Boeffla sound driver updated to 1.66
ZZMOOVE governor reactivated
06/Jul/2014 Rev4.2 - support for the 5110 , 5100 & 5120
Balanced the voltage settings
13/07/2014 Rev4.3 is released
DynamicFsync updated
IntelliHotplug introduced = replacement for the samsung hotplug driver. = Synapse controled
quad core stats for better performance
avg_running time for intelli hotplug support
Synapse settings backup/restore option
I/O advanced settings in Synapse.
Build.prop tweaks in Synapse
Network tweaks in Synapse
...............
15/07/2014 REV4.3_B released
[*]VPN - Reverse path filtering FIX = caused by wrong Synapse settings
[*]Synapse = Network settings changed to solve the vpn problem
16/07/2014 Rev5.0 is released
Dynamic Hotpluging enabled
Update governors
New source 5110NA commits added for the 5120LE
Music skipping problem solved (please use Pegasusq or interactive governor)
SideSync driver added and enabled
Ramdisk removed hotplug locks
Compiled on new toolchain arm-2010q1 from "code sourcery" as suggested by Samsung for the Note8.0 KitKat
...............
17/07/2014 Rev5.1 is released
Different setting for Dynamic Hotpluging, less agressive
Frandom added and enabled
CPU slope changed like on the JB kernel
Dirty writeback
Various performance tweaks
Toolchain arm-2010q1 from "code sourcery" uploaded for the people that want to compile it with this toolchain (look in the kernel folder) as suggested by Samsung for the Note8.0 KitKat
Github updated to Rev5.1
...............
24/08/2014 REV5.4 released
[*]Synapse settings updated
[*]Updated toolchain arm-2010q1(202) from "code sourcery"
[*]GPU Overclocking thanks ZaneZam / DerTeufel / AndreiLux
GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel
[*]Corrected CPU freq going above scaling_max thanks to Yank555.lu
Source
XDA:DevDB Information
SphereKat, Kernel for the Samsung Galaxy Note 8.0
Contributors
civato
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Rev2.0 first public
Stable Release Date: 2014-06-07
Current Beta Version: Rev1.4 non public re
Beta Release Date: 2014-06-05
Created 2014-06-07
Last Updated 2014-09-16
Thank You very much!!!
I will try this kernel in order do fix the spen accuracy.
Doing a nandroid backup and trying.
I´ll let you now my experience.
Martín
It is almost perfect!!!
MartinBM said:
Thank You very much!!!
I will try this kernel in order do fix the spen accuracy.
Doing a nandroid backup and trying.
I´ll let you now my experience.
Martín
Click to expand...
Click to collapse
S-pen alignment is fixed in the kernel and rom so you need both to have 100% accuracy.
This kernel will fix it for 95%. The other 5% is in the roms framework.
#########################################################
Note to all users:
Don't be a lurker, hit thanks as it took plenty of hours to build this.
Samsung didn't release the kernel source (not yet) so a lot of debugging was needed to fix problems like the sensors not reporting correctly.
This is the only thing I ask, hit thanks if this helps you.
It is free and enjoy it.
#########################################
Edit:
About the lurkers,
Martin from this post isn't one as he is a donator and thanks hitter.
A example to you all.
I wanted that cleared out as I didn't want Martin to take that lurker thing personal.
civato said:
S-pen alignment is fixed in the kernel and rom so you need both to have 100% accuracy.
This kernel will fix it for 95%. The other 5% is in the roms framework.
Note to all users:
Don't be a lurker, hit thanks as it took plenty of hours to build this.
Samsung didn't release the kernel source (not yet) so a lot of debugging was needed to fix problems like the sensors not reporting correctly.
This is the only thing I ask, hit thanks if this helps you.
It is free and enjoy it.
Click to expand...
Click to collapse
Much appreciated adding dock & boeffla support. You are a super dev.. will test and report and thanks.
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi. [emoji106]
Sent from my GT-N5110 using Tapatalk
androidmonsta said:
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi. [emoji106]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Damn... if only I had waited.
THANK YOU CIVATO!!! What is arch-power?
androidmonsta said:
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Oh I didn't know that, well that is a good thing, I will add this in my OP.
civato said:
Oh I didn't know that, well that is a good thing, I will add this in my OP.
Click to expand...
Click to collapse
Yup, I'm running FLEXNOTE 1.3 with 4.2.2 bootloader using this kernel. Did a full wipe in Philz using the "I want to install new rom" option.
Sent from my GT-N5110 using Tapatalk
Rev2.1 released
08/Jun/2014 First Public release Rev2.1
[*]GPU step 5 included, now max it will go to 533MHz
[*]Auobrightness sensor fixes part2
[*]CPU sloop adjusted
zzmoove profile nr8.
GPU control is not possible , maybe later as the GPU driver is totally different then on JB.
androidmonsta said:
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi. [emoji106]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
I confirm. Wifi working great. Thanks
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Flashed and while it seems to be working fine for the most part, my CPU is constantly maxed out for some reason. I changed no settings or anything, and it was idling fine before flashing. I'm sure it might be something with my device, but I thought I'd put it out there just in case it's not. I'm going to mess around with some settings, see what I can do, and see if it changes.
ArobeeTV said:
Flashed and while it seems to be working fine for the most part, my CPU is constantly maxed out for some reason. I changed no settings or anything, and it was idling fine before flashing. I'm sure it might be something with my device, but I thought I'd put it out there just in case it's not. I'm going to mess around with some settings, see what I can do, and see if it changes.
Click to expand...
Click to collapse
Like you said, it could be something with your device, mine goes into deep sleep and it has gone as high as 90% deep sleep. Pretty amazing I would say and great job by @civato. Are you on pegasusq governor?
cbrinnny said:
Like you said, it could be something with your device, mine goes into deep sleep and it has gone as high as 90% deep sleep. Pretty amazing I would say and great job by @civato. Are you on pegasusq governor?
Click to expand...
Click to collapse
I was indeed using pegasusq. After trying multiple different governors and nothing changing (even stayed at 1600mhz on powersaving), I've decided to wipe my device entirely and start from scratch. No biggie. If I narrow it down to a specific app or device setting that was causing it, I'll post it so people are aware.
09/Jun/2014 First Public release Rev2.2
[*]Memory Leak fix cpu stats
[*]Memory Leak fix Kernel Ext4 & Power
zzmoove profile nr6.
I recommend not to use Powersave governor as is very buggy. Next release will it have removed as it useless.
Best governors are Pegasusq - Adaptive and zzmoove.
I am running it an am happy to report no issues. The only changes I made were to up my top cpu speed to 1.8gzh. All govs are at default. Thanks again. Can't wait to see what is next in the works for this tablet.
Sent from my GT-N5110 using XDA Premium HD app
Scores
With my rom & kernel
Benchmark scores:
Stock Normal Note8.0 Antutu Ranking. 17708 points
My Antutu = 23486 points
Stock Quadrant ranking = 6613 points
My Quadrant = 13685 points
Running with rom v1.3 and civz kitkat bootloader. Is data wipe needed? Sorry for the stupid question.
Sent from my GT-N5110 using XDA Premium 4 mobile app
slushbilly said:
Running with rom v1.3 and civz kitkat bootloader. Is data wipe needed? Sorry for the stupid question.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not needed, me as a habit always wipe cache and dalvik.
Sent from my GT-N5110 using Tapatalk
Hi androidmonsta, How did you get Nandroid added under your Backup Settings? I assume it is part of the FLEXNOTE rom. What app does this link to?
rjamer said:
Hi androidmonsta, How did you get Nandroid added under your Backup Settings? I assume it is part of the FLEXNOTE rom. What app does this link to?
Click to expand...
Click to collapse
It comes from the rom. Its an backup app. Never use before LOL.
Sent from my GT-N5110 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial DorimanX builds by gsstudios(The resurrection of jellybean kernels)
Development has been discontinued due to commitment to lollipop roms
The Background:
DorimanX development has stopped for a while now. I've been a long term dorimanx user, but I felt that a lot of features need to be implemented into the kernel. As of a result, I decided to make my own personal builds! Please note that I'm no way as good as the master himself, Dorimanx, but I try to implement features to the best of my abilities. Also, I'm not going to be a proper maintainer of dorimanx kernel, this is just what I've done in my spare time.
If you have problems or if anything goes wrong, you can flash latest build by Computoncio
You can download from his official website:
http://dorimanx.casoncia.org/
The Mission:
To continue giving support for the much loved kernel. New features and additions will be added to improve flexibility and speed to the already amazing kernel. My goal is to improve DorimanX kernel as much as I can, without sacrificing stability.
NO LOLLIPOP SUPPORT HERE. JUST 4.1.X - 4.3.X JELLYBEAN ONLY!
STOCK JB ROM IS SUPPORTED HERE
DISCLAIMER:
ONLY FOR AOSP BASED ROMS
I'm not responsible for bricked devices or wrong version flashing
You are using this kernel at your own responsibility
——— !!!!!!!! YOU HAVE BEEN WARNED !!!!!!!! ———
FEATURES:
This kernel includes the following additional features over stock dorimanX kernel:
- CPU Governors: HYPER, Ondemand, pegasusQ, Intellidemand, neoX, darkness, nightmare, zzmoove, powersave, sleepy, conservative, performance (Default: HYPER)
- IO Schedulers: ROW, Tripndroid, FIOPS, SIO, BFQ, CFQ, Noop, ZEN, Deadline (Default: SIO)
- TCP Algorithms: Cubic, Reno, BIC, Westwood, Highspeed, Hybla, HTCP, Vegas, Veno, Scalable, Lp, Yeah, Illinois (Default: Westwood)
- Updated SuperSU
- Built with Latest Optimized Linaro 4.9 Toolchain (Smooth, fast and fluid)
- Built-in Stweaks profiles updated (All profiles suit needs for most people now)
- Trim support (Be careful if you have brickbug affected chip!)
- Updated FPBug fix is already included in this kernel!
- Updated Linux Kernel version to 3.15 stable!
THINGS TO DO:
- Why don't you tell me what to do
THINGS I WILL NOT ADD:
Code:
- LZ4 Compression (Our Boot partition is way too small to support this)
- Useless CPU governors such as Userspace
- Colour tuning support (Unless someone helps me with this)
- Recovery version (WIll only consider doing this if working on LP kernel)
- Higher thermal limits (We all know what happens if we do this)
- Higher overclocking/Lower underclocking capabilities (So you want less stability and more SODs?)
- Synapse support (Stweaks is the only app that can fully support this kernel)
- Linux Kernel version updates (My skills need to improve first before taking on something this big)
CREDITS:
Dorimanx (the real master of the kernel)
Gokhanmoral (Siyah Kernel)
Voku1987(This Kernel)
Alucard_24(This Kernel)
STANTRC(This Kernel)
Entropy512 (CyanogenMod)
Tungstwenty (On screen gestures addon)
Torvalds (Kernel 3.6.Y maintainer)
Computoncio (This Kernel)
cybernetus (This Kernel)
stelistcristi (Contents of this post)
chhapil (For helping me with all of the issues, thanks man)
Chet Kener (For UBER toolchain)
Lanchon (For TRIM fix)
Zeitferne (For FP Bug/Music Bug fix)
DOWNLOAD:
Refer to third post
CHANGELOG:
Refer to second post
KERNEL SOURCE:
Source code of the kernel can be found here:
https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel
https://github.com/gsstudios/initramfs3
ISSUES:
- All dorimanx bugs
USEFUL LINKS
- CPU Governor and I/O Scheduler Guide
- DorimanX tuning guide
TCP Algorithm guide
HAVING PROBLEMS?
Read post 4 before posting questions!
And please if you can, also log an issue here: https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel/issues
GOT QUESTIONS?
Q&A Thread isn't up yet. You can post questions here for now.
HOW TO FLASH?
Check the troubleshooting guide
XDA:DevDB Information
DorimanX Unofficial 4.1.X - 4.3.X, Kernel for the Samsung Galaxy S II
Contributors
gsstudios
Source Code: https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel
Kernel Special Features: See post #1
Version Information
Status: No Longer Updated
Current Stable Version: See changelogs
Current Beta Version: See changelogs
Created 2015-07-29
Last Updated 2015-11-27
Changelogs:
--UNRELEASED VERSIONS (KERNEL UNDER TEST) --
Code:
- Nothing to see here :)
--RELEASED VERSIONS (GENERAL AVAILABILITY) --
Code:
[B]DorimanX 8.45 v006 (BETA) - Last build for Jellybean Branch 8.XX[/B]
- Synced most net, ipv4, TCP Cubic, ipv6 and mutex updates from KK branch. Not all changes were committed due to conflicts.
- Upstreamed kernel version to 3.15.0 stable! Lots and lots of fixes for various parts of the kernel, once again, thanks to realex-fire for contributing! ;) Not all changes were committed due to conflicts.
- Change the VM_MAX_READAHEAD value to 512KB for best throughput
[B]DorimanX 8.45 v005 (STABLE) - Linaro[/B]
- This build is built with latest Linaro 4.9 from Christopher83
- Comes with all changes from original v005 release
[B]DorimanX 8.45 v005 (STABLE)[/B]
- Updated UBER toolchain to 20151031 build
- Last build built with UBER toolchain
[B]DorimanX 8.45 v004 - SCREEN TWEAK BUILD[/B]
[COLOR="Red"]NOTE: This build might give launcher FC's for some odd reason, doesn't happen with non-tweak build[/COLOR]
- All updates from v004 is included in this build
- MOVHYSTI/vitalij value changed to 0 (Super sensitive, suitable for gamers and people who want really responsive screen)
[B]DorimanX 8.45 v004 (STABLE)[/B]
- Updated UBER toolchain to 20151024 build
- Fixed derp in Samsung WL Bug patch (Doesn't make a difference since our phone is not affected anyway. Looks like I will have to recreate the patch files again :) )
- Reverted I/O scheduler updates
- Tuned I/O scheduler fifo batch and other tweaks
- Fixed all zzmoove tunables in stweaks. I'm not adding more tunables for zzmoove since it will cause stability issues.
- proper zzmoove profile switching has been added (previous solution was more of a workaround).
- Allow tunable mode for zzmoove (It's just no profile set, this is required if you want to manually adjust zzmoove values)
[B]DorimanX 8.45 v003 (BETA)[/B]
- Changed toolchain to UBER 4.9 and updated to latest version
[B]DorimanX 8.45 v002 (BETA)[/B]
- Toolchain reverted back to custom dorimanx linaro toolchain
[B]DorimanX 8.45 v001 (BETA)[/B]
- This build will contain all features from KK and LP builds. Including TCP algorithm changing, updated io schedulers and etc
- initramfs based on chhapil's JB branch to fix package parsing error, but with my own changes.
- TRIM and NON-TRIM builds will be available
If you want to see more specific changes, look at my github. It's pretty much most changes from the kk branch with some extras done on the initramfs.
[B]DorimanX 9.45 v003 (STABLE) - Last build for DorimanX branch 9.XX[/B]
- Revert Custom profiles 1, 2 and 3 and related fixes
- Revert GPU changes
- Updated default profile
- Revert Partitions and Root tab
- Updated UBER 4.8 toolchain to latest
- We're moving back to UBER 4.8 toolchain (should be more battery friendly than linaro)
[B]DorimanX 9.45 v002 (BETA)[/B]
- Allow mod of vfs cache pressure
- Updated BFQ io scheduler to v7r8
- Update zzmoove to 1.0 beta 8
- Updated IO schedulers
- Updated SuperSU (Not sure if I've updated it in previous release)
[B]DorimanX 9.45 v001 (BETA)[/B]
- TRIM support
- TCP Algorithm changing support
- Tripndroid and FIOPS IO scheduler
- Updated toolchain to Linaro 4.9
- zzmanX replaced with zzmoove v1.0 beta 7a
- Updated FP Bug fix
- And many other changes from my other kernel builds :)
Downloads
I test most of these builds to make sure they are stable. There may be some cases where I might not test out a build before releasing it. Kernels marked with '(STABLE)' are safe for everyday use, but only take this as a indication.
--IMPORTANT, PLEASE READ--
CAUTION: All builds marked with 'TRIM' at the end has TRIM enabled. If you have brickbug affected emmc chip, avoid downloading it if you don't know what you are doing! For more information about the trim brickbug, visit Lanchon's guide here: http://forum.xda-developers.com/gal...ives/rom-brickbug-aftermath-speeding-t2843238
All builds without 'TRIM' (marked as 'NON-TRIM') have trim disabled. These kernels are safe on brickbug affected chips.
MAKE SURE YOU'RE DOWNLOADING THE RIGHT KERNEL. OTHERWISE YOU COULD BRICK YOUR DEVICE!
For TRIM users:
To use TRIM, you can download an app on the app store called trimmer or use terminal commands as directed in the troubleshooting guide.
Linaro or UBER
I have constantly changed between UBER and Linaro toolchains, and have stuck with UBER toolchain. Choose whichever you believe is best for you. UBER is just Linaro toolchain with extra patches and updated components for speed and smoothness improvements. Linaro is more simplistic and stable.
Which version to choose?
9.x support = 4.1.y, 4.2.y, 4.3.y, 4.4.y maliv2 only! LATEST: DorimanX 9.45 by gsstudios - ROMS include CM10.1.3
8.x support = STOCK, 4.1.y, 4.2.y, 4.3.y, 4.4.y maliv1(STOCK) maliv2 all the rest! LATEST: DorimanX 8.45 by gsstudios - ROMS include Stock 4.1.2 JB, NeatROM, Omega ROM
mali = video driver (for new users that dont care to look for answers)
STOCK = Stock 4.1.2 Jellybean Update for s2
Click to expand...
Click to collapse
And finally, I always see the question on whether to use TRIM or NON-TRIM builds. I recommend using TRIM builds on all devices, even if you have brickbug affected chip. This is because TRIM builds are safe from brickbug as they have been correctly patched up and so it has been used by many users. However, when in doubt, use NON-TRIM builds.
DorimanX 8.XX Branch
Main download link:
https://www.androidfilehost.com/?w=files&flid=43492
Mirror download link:
https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel/releases
DorimanX 9.XX Branch
Main download link:
https://www.androidfilehost.com/?w=files&flid=43494
Mirror download link:
https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel/releases
Beta builds and stable builds will only be uploaded on AFH and github.
Troubleshooting
(Probably one of the most detailed troubleshooting guides for kernels on XDA)
Q: Why flash your kernel? - For new users of DorimanX kernel
This applies to dorimanx kernel in general. Dorimanx kernel is an aftermarket kernel (or custom kernel) that is designed to allow users to tweak their phone at the kernel or near-hardware level side of things. In other words, users get more fine-grained control over their phone, this includes overclocking, underclocking, changing behavior of CPU/GPU etc. Adjusting such settings isn't for the faint-hearted since there is soooo many things to understand, but you aren't required to understand all of the settings. Ultimately, if you want to improve your phone experience, try dorimanx kernel!
Have a look at one of my posts on the thoughts on using my own kernel on neatrom (STOCK JB): http://forum.xda-developers.com/showpost.php?p=63063198&postcount=23
Q:How do I flash your kernel?
A: You flash kernels like flashing roms, except you don't have to factory reset your phone. If you can't flash the kernel for some reason, you can either flash philz recovery then flash the kernel OR you can just make your own kernel .tar file and flash via ODIN by following this guide: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381
Q: Which kernel version build should I flash?
A: Flash the latest stable version if you want the most stable experience. Builds that have not been marked with 'Stable' are mostly stable, or haven't been tested enough to earn a stable tag. Either way, it's up to you which one you want to flash. Read the changelog for any important changes that might have occurred in a particular build.
Q: What is the difference between v8.XX and v9.XX builds?
A: The 8.XX kernel branch was supposed to be the universal kernel that could be used for stock users and 4.2.X users as well as 4.3.X users. To be more specific, the 8.XX kernel branch has 2 GPU drivers for maliv1 and maliv2 roms, meaning that more ram needs to be allocated for the GPU. There isn't much of a performance difference using one or the other if you are on maliv2 rom, however one branch may get specific optmisations that are not present in others. In other words, choose the kernel version that you require, not the one that will support the most android versions. STOCK 4.1.2 users should use 8.XX builds, whereas 4.2.X and 4.3.X users should use 9.XX builds, depending on the ROMs mali (GPU driver) version.
Q: Wifi doesn't work after I flash this kernel
A: There are two main causes to this issue, either there is a problem with your:
- Partitions OR
- Permissions OR
- Gapps OR
- ROM OR
- Compatibility with your wifi hardware
Don't use a pit with modded preload! It will just cause issues with ROMs and Kernels. Use stock pit or use a pit with unmodded preload. Sometimes, the gapps package you flash somehow breaks compatibility with the kernel. You can fix this by flashing a different gapps (making sure to clean cache and dalvik). If you have permissions problem, you can fix this by repartitioning your internal sd card or by reflashing back to stock rom. Sometimes, the ROM doesn't fully support the wireless drivers in the kernel, this can be solved by flashing a different ROM or different kernel. But if your wifi hardware is not compatible (a way to tell this is when you have tried everything and failed), there is nothing you can do but reflash the rom or flash a different kernel.
Q: My sd cards don't mount after I flash dorimanX kernel!
A: Please check the format (or file system) of your sd cards. DorimanX kernel doesn't support ext4 formatted sd cards and hence you can't see them. You will need to format the sd cards to fat32 or other format.
Q: I came from a different custom kernel that used Stweaks, now the app has issues
A: Every time you come from a different custom kernel with stweaks support, make sure to wipe cache and dalvik cache after install dorimanx kernel
Q: My battery life sucks after flashing this kernel!
A: Download and install Betterbatterystats and see what is the culprit to your problem. If it is kernel related, have you made sure you have wipe cache and dalvik and reset stweaks settings? If yes, it would be nice if you posted a logcat.
Q: How do I get a logcat for the kernel?
A: In stweaks, go to BUG-REPORT and tap on KERNEL-BUG.
Q: Why do I get bootloops with this kernel?
A: If you were on a working version on dorimanx kitkat before, there is probably something wrong with the installation. If you are on a ROM that is not kitkat, you flash the wrong kernel! You need to flash the right kernel for your android version. Sometimes, bootloops can occur due to corruption of the kernel zip file (usually from bad download) or from corrupted partitions.
Q: What do all of the settings mean? They are all confusing!
A: Please note that DorimanX kernel isn't for users who have just rooted their device. Before jumping into the custom kernel world, try playing around with other kernels first. Once you think you have some experience, read the stweaks beginners guide I made and then attempt to tweak the kernel using stweaks.
Q: How do I trim my partitions?
BEWARE: Make sure you have read all of the precautions before attempting to trim your partitions!
A: install the trimmer app from the playstore. App link . Check for all 3 partitions, and tap on run. grant root access. the 3 fstrim operations should be successful ("partition was trimmed" means success).
alternatively, instead of using trimmer you can run one of these commands (these are better because they also trim /preload):
# on the phone in the terminal app:
su -c "fstrim -v /system; fstrim -v /data; fstrim -v /cache; fstrim -v /preload"
# on your PC if you are connected to the phone via adb:
adb shell su -c "fstrim -v /system; fstrim -v /data; fstrim -v /cache; fstrim -v /preload"
reboot.
Click to expand...
Click to collapse
Q: My device is (hard) bricked after flashing your kernel!
A: Have you read all of the precautions before installing the kernel? You made the decision to flash the kernel and now you've stuffed up your phone.
Q: I get constant FCs after flashing your kernel!
A: Have you wiped your cache partition, dalvik cache and reset stweaks settings? If you've done all of these already, a logcat would be nice
Q: How do I use dual boot?
A: There are many guides on how to dual boot roms using dorimanx kernel. Just use the search function on XDA or GOOGLE it!
Q: What's a good combination for CPU governor and I/O scheduler?
A: Have a look at the default settings, they are optimised for our phone
However, here are some settings I personally like:
1. Governor: HYPER/Ondemand I/O scheduler:SIO/SIO
2. Governor: PegasusQ/Nightmare I/O scheduler: SIO/SIO
3. Governor: NeoX/Ondemand I/O scheduler: SIO/SIO
4. Governor: Nightmare/Nightmare I/O scheduler: SIO/SIO
Q: Why does the screen turn blank after the dorimanx logo appears during the boot process?
A: If your kernel doesn't bootloop, but the screen remains blank, there is a good chance that the ROM that you've used uses an older version of GPU drivers (Mali). This kernel only support ROMs with Maliv3 support. If you flash this kernel on MaliV2 or MaliV1 only roms, you will get a blank screen after flashing. To fix this, flash to the kernel the corresponds to your mali driver version and you should get your display back.
Q: What is a TCP algorithm?
A: Congestion control strategies (or algorithms) are used by TCP, the data transmission protocol used by many Internet applications. The main goal of a TCP algorithm is to avoid sending more data than the network is capable of transmitting, that is, to avoid causing network congestion.
Q: What is UBER?
A: After years of using different custom toolchains like Linaro and SaberMod, I found there were things I liked about both of them but also things that didn't sit quite as well with me. SaberMod always seemed to have UI lag (especially in scrolling) but opened apps well and Linaro always seemed to be buttery smooth but had terrible app opening speed. Linaro battery was also worse for me than SaberMod. After going back and forth between toolchains I finally had this epiphany! Why not just take all of the best parts of all toolchains and merge them into one? So I began bringing up my own toolchain from gnu.org. At first I patched in all of the AOSP toolchain pactches (much like how SaberMod did it originally however it is important that you realize that No! I did not copy and paste SaberMod into my source I'm simply stating that I used their idea of merging aosp into gnu.org) to my source. Then I went through and added all of the linaro patches that I could to the source. I also made sure that I had the very latest of every toolchain component. I then made very minimal changes to the aosp toolchain build folder to allow for building with these newer toolchain components and UBERTC was born!!! (Note: both Linaro and SaberMod both made lots of modifications to the toolchain build folder, UBERTC is the closest to the aosp build process)
Click to expand...
Click to collapse
No build up yet, will build sometime on Friday or on the weekend. (Internet speed is quite slow right now)
Also, out of the 3 branches I maintain, updates to this branch will be the slowest. (More work will be done on kitkat and lollipop kernels).
Works on 4.1.2?
spaliaras said:
Works on 4.1.2?
Click to expand...
Click to collapse
No, doesn't work. This version has mali v2 drivers.
Kernel works on SlimBean 4.3.1 also. So, 4.2.X roms, and some 4.3.x
OMG it is happening
nhmanas said:
OMG it is happening
Click to expand...
Click to collapse
Yeah, my internet is soooooo slow. I think there is some issues with my virtual machine. Might have to redo it. (Only getting less than 50KB/s when downloading source)
gsstudios said:
Yeah, my internet is soooooo slow. I think there is some issues with my virtual machine. Might have to redo it. (Only getting less than 50KB/s when downloading source)
Click to expand...
Click to collapse
Are you using Ubuntu on vm?
nhmanas said:
Are you using Ubuntu on vm?
Click to expand...
Click to collapse
Yep, Ubuntu 14.04 on Virtualbox. I just reinstalled the vm and still issue occurs. I think the connection between github and my pc is just slow, sometimes it is fast, but most of the time it is slow.
Edit: Looks like a good old reset the router trick did the job. Now downloading source at normal speeds.
Releasing first build this afternoon. Will have most changes from my lp and kk kernel.
Hello guys. I have released my first personal build for the 9.XX branch of dorimanX kernel. You can download it from AFH or from github as I speak. Build v001 will contain most of the changes in KK and LP kernels, however some changes still need a bit more working. This is a massive upgrade over the original unofficial 9.xx branch which was inactive for a while. As I said earlier, I will not be working on this kernel branch as often compared to my KK and LP kernel.
@nhmanas, you got what you wished to see as what you said in my general fpbug suggestion thread
cheers, gsstudios
gsstudios said:
@nhmanas, you got what you wished to see as what you said in my general fpbug suggestion thread
cheers, gsstudios
Click to expand...
Click to collapse
@gsstudios thanks mate! I will try itit after I test rr5.1.1! I needed an updated kernel on stable cm10.1
why with dorimanx kernel versions until 9(v8.x.x)we have only 784 mb ram on JB ??? on some roms with different version s of DorimanX having 806 and on stock based kernels whole 826!? Could not be done in sucha maner???? memory hungry, ha?!?!?? Jessus and Maria! Be dev and fix it! Tnx!
Works on 4.2.2 Rom??
yimisito said:
Works on 4.2.2 Rom??
Click to expand...
Click to collapse
Yes works well :good:
When I have time, I will compile the last build for this branch with all of the features I've promised.
Gsstudios.
Build v002 released. I will not release any new builds for a while until I finish my exams.
This release comes with updated BFQ io scheduler, updates to all other io schedulers, updated zzmoove and some other changes (refer to changelogs).
gsstudios.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial DorimanX builds by GreekDragon(The resurrection of jellybean kernels)
Dorimanx JB unofficial kernel by GreekDragon
The Background:
DorimanX development has stopped for a while now. I've been a long term dorimanx user, but I felt that a lot of features need to be implemented into the kernel. As of a result, I decided to make my own personal builds! Please note that I'm no way as good as the master himself, Dorimanx, but I try to implement features to the best of my abilities. Also, I'm not going to be a proper maintainer of dorimanx kernel, this is just what I've done in my spare time.
This is a fork from Dorimanx's git.
If you have problems or if anything goes wrong, you can flash latest build by Computoncio
You can download from his official website:
http://dorimanx.casoncia.org/
The Mission:
To continue giving support for the much loved kernel. New features and additions will be added to improve flexibility and speed to the already amazing kernel. My goal is to improve DorimanX kernel as much as I can, without sacrificing stability.
4.1.X JELLYBEAN ONLY!
DISCLAIMER:
I'm not responsible for bricked devices or wrong version flashing
You are using this kernel at your own responsibility
——— !!!!!!!! YOU HAVE BEEN WARNED !!!!!!!! ———
FEATURES:
This kernel includes the following additional features over stock dorimanX kernel:
- CPU Governors: HYPER, Ondemand, pegasusQ, Intellidemand, neoX, darkness, nightmare, sleepy, conservative (Default: HYPER)
- TCP Algorithms: Cubic, Reno, BIC, Westwood, Highspeed, Hybla, HTCP, Vegas, Veno, Scalable, Lp, Yeah, Illinois (Default: Westwood)
- FPBug/Musicbug fix is already included in this kernel!
- BLN and BLNWW support
- Updated Linux Kernel version to 3.15.0 stable!
- IO Schedulers: ROW, FIOPS, SIO, BFQ, CFQ, Noop, ZEN, Deadline (Default: SIO)
- Trim support
THINGS I WILL NOT ADD:
Code:
- LZ4 Compression (Our Boot partition is way too small to support this)
- Useless CPU governors such as Userspace
- Colour tuning support (Unless someone helps me with this)
- Recovery version (WIll only consider doing this if working on LP kernel)
- Higher thermal limits (We all know what happens if we do this)
- Higher overclocking/Lower underclocking capabilities (So you want less stability and more SODs?)
- Synapse support (Stweaks is the only app that can fully support this kernel)
CREDITS:
Dorimanx (the real master of the kernel)
Gokhanmoral (Siyah Kernel)
Voku1987(This Kernel)
Alucard_24(This Kernel)
STANTRC(This Kernel)
Entropy512 (CyanogenMod)
Tungstwenty (On screen gestures addon)
Torvalds (Kernel 3.6.Y maintainer)
Computoncio (This Kernel)
cybernetus (This Kernel)
stelistcristi (Contents of this post)
chhapil (For helping me with all of the issues, thanks man)
Chet Kener (For UBER toolchain)
Lanchon (For TRIM fix)
Zeitferne (For FP Bug/Music Bug fix)
gsstudios (For his help and his thread template)
DOWNLOAD:
Siyah-Dorimanx-V8.70-JB-SGII-PWR-CORE-DRAGON-TRIM.zip
AndroidFileHost Download Folder
CHANGELOG:
Refer to second post
KERNEL SOURCE:
Source code of the kernel can be found here:
https://github.com/dragonGR/Dorimanx-SG2-I9100-Kernel
https://github.com/dragonGR/initramfs3
ISSUES:
- All dorimanx bugs
USEFUL LINKS
- CPU Governor and I/O Scheduler Guide
- DorimanX tuning guide
TCP Algorithm guide
XDA:DevDB Information
DorimanX JB by GreekDragon, Kernel for the Samsung Galaxy S II
Contributors
GreekDragon, chhapil
Source Code: https://github.com/dragonGR/Dorimanx-SG2-I9100-Kernel
Kernel Special Features:
Version Information
Status: Stable
Created 2016-07-15
Last Updated 2016-12-03
Changelogs:
--RELEASED VERSIONS --
Code:
[B]DorimanX 8.70 (STABLE) [/B]
- Massive update -
- Upstream & Security fixes -
- Stability improved -
- Switched to gsstudio's fork -
Reserved
Welcome to the team
@Lysergic Acid @gsstudios , @arnab , @GreekDragon @Trafalgar Square ..... and i missed many but what a Team on I9100 again
thanks to all to continue to maintain our device with a so high level of development !
Troubadour666 said:
@Lysergic Acid @gsstudios , @arnab , @GreekDragon @Trafalgar Square ..... and i missed many but what a Team on I9100 again
thanks to all to continue to maintain our device with a so high level of development !
Click to expand...
Click to collapse
After 5 years, s2 is still alive and kicking. I guess is a zombie now.
Its work
Do you have any profile between battery/stability/games
I am here
xn0live said:
Its work
Do you have any profile between battery/stability/games
Click to expand...
Click to collapse
I don't want to touch profiles because i know i will screw up there.
Trafalgar Square said:
I am here
Click to expand...
Click to collapse
Of course you are here.
I'm testing a new v8.52. I added IsoRec and some other things, if everything is good, i will release it.
Have you pulled the fix for package parsing error in JB?
As I mentioned to you I'm not able to keep up these days due to me professional commitment, so your contribution to JB branch is a welcome change. Thanks for that
I have one concern over how the Dorimanx kernel development is heading.
Already the JB vs KK, MM code is now much fragmented, I was trying to my best to bring JB much closer to the current branches but not fully.
I would like to know your views on this
chhapil said:
Have you pulled the fix for package parsing error in JB?
As I mentioned to you I'm not able to keep up these days due to me professional commitment, so your contribution to JB branch is a welcome change. Thanks for that
I have one concern over how the Dorimanx kernel development is heading.
Already the JB vs KK, MM code is now much fragmented, I was trying to my best to bring JB much closer to the current branches but not fully.
I would like to know your views on this
Click to expand...
Click to collapse
Fragmentation was going to happen sooner or later, especially with all those changes required just to get MM working.
I will help with JB development when I have free time alongside GreekDragon. LP and MM will and always be my primary focus (until new android versions come out)
gsstudios
Could you explain why there's dorimanx.zip file inside the kernel file
Was it a mistake or you compiled two different kernels?
gsstudios said:
Fragmentation was going to happen sooner or later, especially with all those changes required just to get MM working.
I will help with JB development when I have free time alongside GreekDragon. LP and MM will and always be my primary focus (until new android versions come out)
gsstudios
Click to expand...
Click to collapse
May be my expectations would be wrong, apart from Mali code, rest of the code should be almost same.
Even the WiFi driver has become totally open source now but it's not merged to JB branch fully.
Lot of pieces related to net, scheduling are also different.
I guess since Dorimanx and computino's days it has started bifercating.
I hope we can bring it together
Always if my mobile is off(screen off) and i get a whatsapp message my phone wake up
where is the option, where i can disabled it?
BLN is off
and what does it mean if a person say i am using " cpu grpup 2 or cpu group 3" where is the setting for that
chhapil said:
Have you pulled the fix for package parsing error in JB?
As I mentioned to you I'm not able to keep up these days due to me professional commitment, so your contribution to JB branch is a welcome change. Thanks for that
I have one concern over how the Dorimanx kernel development is heading.
Already the JB vs KK, MM code is now much fragmented, I was trying to my best to bring JB much closer to the current branches but not fully.
I would like to know your views on this
Click to expand...
Click to collapse
Yeah, i'm testing it along with some other things.
I have something in my mind. If everything is ok, JB kernel will be closer to LP one. Not sure if you get me.
gsstudios said:
Fragmentation was going to happen sooner or later, especially with all those changes required just to get MM working.
I will help with JB development when I have free time alongside GreekDragon. LP and MM will and always be my primary focus (until new android versions come out)
gsstudios
Click to expand...
Click to collapse
Thanks again.
Thanks.
Muhammadsoli said:
Could you explain why there's dorimanx.zip file inside the kernel file
Was it a mistake or you compiled two different kernels?
Click to expand...
Click to collapse
Is a mistake.
chhapil said:
May be my expectations would be wrong, apart from Mali code, rest of the code should be almost same.
Even the WiFi driver has become totally open source now but it's not merged to JB branch fully.
Lot of pieces related to net, scheduling are also different.
I guess since Dorimanx and computino's days it has started bifercating.
I hope we can bring it together
Click to expand...
Click to collapse
WIFI Drivers is stable on JB.. correct me if i'm wrong, but why to update the drivers when the one from JB works great?
xn0live said:
Always if my mobile is off(screen off) and i get a whatsapp message my phone wake up
where is the option, where i can disabled it?
BLN is off
and what does it mean if a person say i am using " cpu grpup 2 or cpu group 3" where is the setting for that
Click to expand...
Click to collapse
What do you mean?
About cpu group, is on STweaks and specifically in CPU-Voltages tab.
Dorimanx v8.55 is up!
Changelogs:
- Added IsoRec
- Kernel is now 3.15
- Removed zzmanX
- Added zzmoove
- Removed Powersave governor
- Removed Perfomance governor
- Removed VR and FIFO schedulers
- Enabled other flags for FIOPS
- Updated SuperSU to v2.46
- Fixed permissions for power efficient workqueues parameter
- Fixed parsing package error
- Synced chhapil's zram updates
- Set lz4 as the default algorithm for zram
- Merged almost all fixes from zzmoove develop branch.
- Added tcp algorithm changing support and set westwood as the default
- Governors Updated
- Tuned IO schedulers
- Fixed some memory corruptions
- Sync IO scheduler changes with KK branch
- Fixed some leaks
- Applied some security updates
- Added PE workqueue control
- Added TCP algorithm changing support to stweaks
- Initial support for software CRC toggle
Downloads
AFH: https://www.androidfilehost.com/?fid=24591000424948196
Github(mirror):https://github.com/dragonGR/Dorimanx-SG2-I9100-Kernel/releases/tag/v8.55-stable
Found some issues
Stweaks always detects a value been changed, I think your profiles are out of sync
Trim is not working properly, phone hangs while trimming, check the discard option in fstab in initramfs
Overall deep sleep is good, resume is faster after screen off state
:good:
chhapil said:
Found some issues
Stweaks always detects a value been changed, I think your profiles are out of sync
Trim is not working properly, phone hangs while trimming, check the discard option in fstab in initramfs
Overall deep sleep is good, resume is faster after screen off state
:good:
Click to expand...
Click to collapse
TRIM works fine here. And i have affected chip if that matters.
About Stweaks, i think i know the problem. Testing.
Resume is faster indeed.
I flash the 2 version
the kernel is not very stable, its freeze almost
xn0live said:
I flash the 2 version
the kernel is not very stable, its freeze almost
Click to expand...
Click to collapse
No freeze for me. All is good. @chhapil you faced freeze?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Hello everyone, this is my kernel for the Nexus 6, based on my kernel for the Nexus 6P. I aim to add enough features to matter while keeping it lean and stable. Hopefully you enjoy! Please read this entire post, most of your questions will be answered in here!
Features
Here are the major features of the kernel (feel free to explore Github)
Upstream Linux versions 3.10.41-3.10.104
Updated to the December security patch
Patches for some CVEs
Upstream patches from CAF
Support for overclocking to 2880 MHz (stock values by default)
CPU governors: barry_allen, blu_active, chill, conservative, darkness, elementalx, impulse, interactive (default), nightmare, ondemand, performance, smartmax, userspace, zzmoove
Hotplugs: blu_plug, mako_hotplug, msm_sleeper, zen_decision (default - mpdecision is disabled)
High brightness mode and backlight dimmer
KCAL color control
Adreno Idler
Wake gestures (sweep2wake, doubletap2wake, sweep2sleep, and camera launch gesture)
Voltage control
Franco sound control and high performance audio
Adaptive low memory killer
UKSM (disabled by default)
I/O schedulers: bfq, cfq, deadline, fiops, maple, noop, sioplus (default), tripndroid, and zen
USB fast charging
Wakelock controls
BCL disabled
TCP algorithms: bic, cubic, highspeed, htcp, hybia, illinois, lp, reno, scalable, vegas, veno, westwood (default)
Kexec patch for MultiROM support
Full F2FS support
Compiled with an Uber-based 6.3.1 toolchain located here
Forced encryption and dm-verity disabled
Built with AnyKernel2 thanks to @osm0sis
Downloads
7.0/7.1/7.1.1 (1.x): Main
Installation
If you are on stock:
If you are on the stock kernel: flash the kernel zip and reboot
If you are on a custom kernel: flash the stock boot image matching your build number, flash the kernel zip, and reboot
If you are on a custom ROM:
If you are on the kernel that came with your ROM: flash the kernel zip and reboot
If you are on a custom kernel: dirty flash your ROM zip, flash the kernel zip, and reboot
Upgrading from one Flash version to the other:
Just flash the kernel zip and reboot
Changelog
Nougat 7.0
Code:
[B]1.8[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=70246281]release post[/URL])
[LIST]
[*]Toolchain bumped to 6.3.1
[/LIST]
[B]1.7[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=70112925]release post[/URL])
[LIST]
[*]December security update
[*]Upstream F2FS commits
[*]Improvements to cpuidle
[*]Double tap to wake now works when either halfscreen or fullscreen is selected in KA
[*]Fix tethering on 7.1.1 ROMs
[*]Add Live Display (work with KCAL thanks to [user=4684315]@flar2[/user])
[/LIST]
[B]1.6[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=69873175]release post[/URL])
[LIST]
[*]Revert an interactive governor patch that was introducing lag
[/LIST]
[B]1.5[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=69859780]release post[/URL])
[LIST]
[*]Fixes for sdcardfs on certain ROMs like CM 14.1
[*]Upstream patches from CAF and Linux
[*]Interactive governor improvements
[*]Detect when kernel is flashed on an unsupported Android version
[*]Add support for FK Updater's performance profiles
[/LIST]
[B]1.4[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=69526781]release post[/URL])
[LIST]
[*]November security update
[*]Chill governor updates (thanks to [user=5051294]@frap129[/user])
[*]Fixed Mako Hotplug (thanks to [user=4231562]@Yoinx[/user])
[*]Updated BCL commits (thanks to [user=3292224]@franciscofranco[/user])
[*]Fixed some compiler warnings (thanks to [user=4231562]@Yoinx[/user])
[/LIST]
[B]1.3[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=69264556]release post[/URL])
[LIST]
[*]Upstream Linux patches for vmstat and libgcc
[*]Backported MDSS and GPU patches from Marlin (thanks to [user=3292224]@franciscofranco[/user])
[*]Low memory killer improvements
[*]Removed cmdline patch from 1.2
[/LIST]
[B]1.2[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=69247056]release post[/URL])
[LIST]
[*]Linux version 3.10.104
[*]Move back to a constant tickrate of 300HZ
[*]Add a patch to hide bootloader unlock from SafetyNet
[/LIST]
[B]1.1[/B] ([URL=http://forum.xda-developers.com/showthread.php?p=69183164]release post[/URL])
[LIST]
[*]Add smartmax governor
[*]Add full F2FS support
[*]Add Motorola quick wakeup driver
[*]Fix simple_ondemand GPU governor
[*]Add [URL="http://kerneldedup.org/en/projects/uksm/introduction/"]UKSM[/URL] (disabled by default)
[*]Set default I/O scheduler to zen and readahead to 128kb
[*]Start kernel at stock frequencies
[/LIST]
[B]1.0[/B]
[LIST]
[*]Initial release
[*]List of features above
[/LIST]
Frequently asked questions
1.1 Q: I am having an issue, can you help me?
1.1 A: I am not a superstar kernel developer but I will certainly try my best. First, start by reading the release posts, as I may make note of a particular issue. Also search the thread to see if I have discussed it before. If you see nothing, please provide me with a dmesg/last_kmsg and logcat, your ROM/kernel version, and a detailed description of the issue. With that, I'll do my best to assist you.
Code:
adb logcat -d > logcat.txt
adb shell dmesg > dmesg.txt
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not go digging super hard for commits and I will ignore requests that don't include this information. I won't promise that I will merge every request but I will always take it into consideration.
1.3 Q: How do I control the kernel?
1.3 A: I'd recommend using either @flar2's EX Kernel Manager or @Yoinx's Kernel Adiutor-Mod; both are extremely solid and have given me no issues.
1.4 Q: I am having Wi-Fi disconnects on a 5GHz network, what's up?
1.4 A: Try increasing the wakelock divider on the following sys paths in a terminal emulator (can also be done in EXKM in the Miscellaneous section):
Code:
echo 8 > /sys/module/bcmdhd/parameters/wlrx_divide
echo 8 > /sys/module/bcmdhd/parameters/wlctrl_divide
Thank you to @Buckmarble for pointing this out!
Thanks to:
@REV3NT3CH for showing me what a good developer and kernel looks like
The various developers for their patches (@ak, @Buckmarble, @flar2, @franciscofranco, @frap129, @imoseyon, and @Yank555 to name a few)
@osm0sis for AnyKernel2
@DespairFactor for helping me with some kernel compilation issues and the Linaro source of the toolchains I use
@kantjer for pointing me to Linaro in the first place and being a beta tester along the way!
@malybru for my nifty new signature and thread banner!
All of you guys for viewing the thread
A note about donations
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Kernel source links
7.0: https://github.com/nathanchance/shamu
DISCLAIMER: I openly welcome off topic in my threads. Mods, please do not clean off topic discussion and users, do not complain about off topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.
XDA:DevDB Information
Flash Kernel, Kernel for the Nexus 6
Contributors
The Flash
Source Code: https://github.com/nathanchance/shamu
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.8 - Nougat 7.0/7.1
Stable Release Date: 2016-12-25
Created 2016-10-11
Last Updated 2019-07-02
Reserved
Reserved
First
Amazing
Excellent kernel, and a welcome addition to the Shamu!
Hi,
Thank you Nathan!
I know MultiRom isn't working very good with N yet but still:
Does you kernel have the kexec patch inside please?
Droidphilev said:
Hi,
Thank you Nathan!
I know MultiRom isn't working very good with N yet but still:
Does you kernel have the kexec patch inside please?
Click to expand...
Click to collapse
Looking at the source, I do believe kexec is present in Flash Kernel. Multirom manager also reflects that is built in.
rebel1699 said:
Looking at the source, I do believe kexec is present in Flash Kernel. Multirom manager also reflects that is is built in.
Click to expand...
Click to collapse
Thank you! Soon time to flash
Droidphilev said:
Hi,
Thank you Nathan!
I know MultiRom isn't working very good with N yet but still:
Does you kernel have the kexec patch inside please?
Click to expand...
Click to collapse
Yes, as previously mentioned. OP has been updated to reflect this
Can you allow f2fs compatibility ?
many people use such partitions...
Thank you anyhow!
Nautilus74 said:
Can you allow f2fs compatibility ?
many people use such partitions...
Thank you anyhow!
Click to expand...
Click to collapse
Already queued up for the next update.
very good kernel
Kernel is sweet so far. Been rock solid stable in the few days I have been running it - def check this one out guys!
@The Flash
running great with PN 7.0 here.
although kernel manager doesn't show all hotplugs...kernel-aduiter shows only 2 i think and elementalX-manager doesn't show 1.....sorry forgot specifics coz i removed both and have no managers install now.
anyway, quick question:
u have better knowledge in this area than I do...whats the diff between interactive from this kernel and interactive from lean kernel...I have heard great things abt leankernel but never got the chance to run it coz by the time i bought nexus 5 he already moved to nexus 6...by the time i bought nexus 6 he already moved to nexus 6P...lol
[email protected] said:
@The Flash
running great with PN 7.0 here.
although kernel manager doesn't show all hotplugs...kernel-aduiter shows only 2 i think and elementalX-manager doesn't show 1.....sorry forgot specifics coz i removed both and have no managers install now.
anyway, quick question:
u have better knowledge in this area than I do...whats the diff between interactive from this kernel and interactive from lean kernel...I have heard great things abt leankernel but never got the chance to run it coz by the time i bought nexus 5 he already moved to nexus 6...by the time i bought nexus 6 he already moved to nexus 6P...lol
Click to expand...
Click to collapse
LeanKernel uses InteractiveX - Imoseyon's own version of Interactive with a screen off max freq. Interactive is a stock governor. This thread is GREAT for learning about all the awesome governors in this and other kernels - I personally use Darkness. http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957 Hope this helps bud!
@The Flash
Your kernel runs really great with Tesla! It seems like a rocking solid beast!
Gesendet von meinem Nexus 6
@The Flash Looks great, will it improve battery? And what kernel settings do you recommend for a 4 hrs sot?
spevil07 said:
@The Flash
Your kernel runs really great with Tesla! It seems like a rocking solid beast!
Gesendet von meinem Nexus 6
Click to expand...
Click to collapse
Glad to hear!
Yasharkhan said:
@The Flash Looks great, will it improve battery? And what kernel settings do you recommend for a 4 hrs sot?
Click to expand...
Click to collapse
It should, I've added a lot of optimization packages. The default settings should be getting you more than 4 hours of SOT but you may try tweaking the governor and hotplug settings.
Running & sleeping well on the 10/10 build of Uberstock. Thanks for sharing your work!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial DorimanX builds by Saber (formerly gsstudios)
The Background:
DorimanX development has stopped for a while now. I've been a long term dorimanx user, but I felt that a lot of features need to be implemented into the kernel. As of a result, I decided to make my own personal builds! Please note that I'm no way as good as the master himself, Dorimanx, but I try to implement features to the best of my abilities. Also, I'm not going to be a proper maintainer of dorimanx kernel, this is just what I've done in my spare time.
If you have problems or if anything goes wrong, you need to reflash your current ROM to revert kernel.
The Mission:
To continue giving support for the much loved kernel. New features and additions will be added to improve flexibility and speed to the already amazing kernel. My goal is to improve DorimanX kernel as much as I can, without sacrificing stability.
DISCLAIMER:
ONLY FOR LOS14.1 BASED ROMS
I'm not responsible for bricked devices or wrong version flashing
You are using this kernel at your own responsibility
——— !!!!!!!! YOU HAVE BEEN WARNED !!!!!!!! ———
FEATURES:
This kernel includes the following additional features over stock dorimanX kernel:
- CPU Governors: HYPER, Ondemand, pegasusQ, Intellidemand, neoX, darkness, nightmare, zzmoove, sleepy, conservative (Default: HYPER)
- IO Schedulers: ROW, Tripndroid, FIOPS, SIOPlus, BFQ, CFQ, Noop, ZEN, Deadline (Default: ZEN)
- TCP Algorithms: Cubic, Reno, BIC, Westwood, Highspeed, Hybla, HTCP, Vegas, Veno, Scalable, Lp, Yeah, Illinois (Default: Westwood)
- Built with optimised Linaro 4.9 Toolchain
- Built-in Stweaks profiles updated (All profiles suit needs for most people now)
- Trim support (Be careful if you have brickbug affected chip!)
- Updated FPBug/Musicbug fix is already included in this kernel!
- BLN and BLNWW support
- Updated Linux Kernel version to 3.15.0 stable!
- Freezefix is already included in this kernel!
- Isorec support
- MDNIE mode and scenario tuning
- F2FS support
THINGS TO DO:
- Allow users to revert kernel back to stock with everything working
THINGS I WILL NOT ADD:
- LZ4 Compression (Our Boot partition is way too small to support this)
- Useless CPU governors (such as Userspace)
- Colour tuning support (Unless someone helps me with this)
- Higher thermal limits (We all know what happens if we do this)
- Higher overclocking/Lower underclocking capabilities (So you want less stability and more SODs?)
- Synapse support (Stweaks is the only app that can fully support this kernel)
- Linux Kernel version updates (My skills need to improve first before taking on something this big)
CREDITS:
Dorimanx (the real master of the kernel)
Gokhanmoral (Siyah Kernel)
Voku1987(This Kernel)
Alucard_24(This Kernel)
STANTRC(This Kernel)
Entropy512 (CyanogenMod)
Tungstwenty (On screen gestures addon)
Torvalds (Linux Kernel maintainer)
Computoncio (This Kernel)
cybernetus (This Kernel)
stelistcristi (Contents of this post, updates)
chhapil (Kernel build support, updates)
Chet Kener (Linaro/UBER toolchain)
Lanchon (TRIM fix and Isorec for Dorimanx)
Zeitferne (FP Bug/Music Bug fix and freezefix)
Lysergic Acid (LOS14.1)
rINanDO (LOS14.1)
serenitys (LOS14.1)
Realex-fire (Marshmallow/Nougat support and kernel fixes)
Skyline (Material Stweaks and testing)
DOWNLOAD:
Refer to third post
CHANGELOG:
Refer to second post
KERNEL SOURCE:
Source code of the kernel can be found here:
https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel
https://github.com/gsstudios/initramfs3
ISSUES:
- Users will lose a lot of functionality if they dirty flash ROM to restore kernel
- If you reboot your phone, you may experience a large battery percentage drop
- All dorimanx bugs
WHAT ROMS DO I SUPPORT?
You should only flash this kernel on top of:
- LineageOS 14.1
USEFUL LINKS
CPU Governor and I/O Scheduler Guide
DorimanX tuning guide
TCP Algorithm guide
XDA:DevDB Information
DorimanX kernel for LOS14.1 by Saber, Kernel for the Samsung Galaxy S II
Contributors
Saber, dorimanx, Realex-fire
Source Code: https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel
Kernel Special Features: See post #1
Version Information
Status: No Longer Updated
Created 2017-07-25
Last Updated 2017-09-19
Changelogs:
--UNRELEASED VERSIONS (KERNEL UNDER TEST) --
For live changelogs, see my github:
Kernel: Github Link
Initramfs (Ramdisk): Github Link
--RELEASED VERSIONS (GENERAL AVAILABILITY) --
Code:
[B]DorimanX 13.0 b005[/B]
- Pulled updates for tcp, net, uksm, binder and many more from DorimanX OP3T kernel, all thanks to @Realex-fire
- Minor build script improvements
- TCP fast open control added to Stweaks
- HYPER is now the default sleep governor
- Updated busybox from Dorimanx source - Again thanks to @Realex-fire
- Minor fixes to ROM init script
[B]DorimanX 13.0 b004[/B]
- Synced scheduler and block changes from linux 3.16
- Synced security/keys and selinux changes from linux 3.16
- Synced kernel/fork, lmk and other changes from dorimanx
- Temporarily disable playready DRM to fix package manager corruption issues
- Remove powerHAL introduced in lineageOS to remove governor setting conflicts
- Various script improvements thanks to @Realex-fire
[B]DorimanX 13.0 b003[/B]
- Reverted default governor back to HYPER
- Synced ext4 updates from mainline - Thanks to @Realex-fire
- Partition checking will only check for bad blocks now
- Lower cortexbrain auto read ahead values and add 3072KB option
- Stweaks settings will be reset after flashing this build!
[B]DorimanX 13.0 b002[/B]
- Updated exfat from Dorimanx sources
- Reverted the kernel's internal tick rate back to 250
- Changed default governor to Nightmare
- Stweaks profile updates
- Enable adb autostart and insecure adb for debugging purposes
[B]DorimanX 13.0 b001[/B]
- Initial LOS14.1 Support
- Re-added Adaptive LMK and UKMS - Better for RAM usage at the cost of some CPU time
- LZO is now being used as the default compression method for ZRAM - Much better compression, worse decompression. Better for our ZRAM size limitations.
- Synced recent zzmoove updates - New profile, stability updates, some code only for SD devices
- ZEN I/O scheduler updates from Dorimanx
Downloads
--STOP!!! IMPORTANT, PLEASE READ--
It is important that you make a backup before flashing this kernel. If you want to restore the original kernel found in your ROM, you need to restore from a backup or clean flash your ROM.
MAKE SURE YOU'RE DOWNLOADING THE RIGHT KERNEL. OTHERWISE YOU COULD BRICK YOUR DEVICE!
Flashing instructions:
1. Download latest kernel build
2. Reboot to recovery
3. Flash kernel zip
4. Reboot
For TRIM users:
To use TRIM, you can download an app on the app store called trimmer or use terminal commands as directed in the troubleshooting guide.
Isorec (Isolated Recovery)
You can use either TWRP or CWM. It is important to note that the default CWM recovery has kernel specific options within the menus, so if you require to use them, be sure to flash the isorec disabler.
Download for isorec recoveries:
https://www.androidfilehost.com/?w=files&flid=47550
If you have a dualboot setup or if you want to set up dualboot, you should stay on StanTRC recovery. If you want to return to StanTRC recovery, flash the isorec disabler:
https://www.androidfilehost.com/?fid=24369303960682947
Forgot to download backup/older kernel/isorec disabler after flashing TWRP?
Go to download mode and flash a kernel .tar file OR wait until OS boots and copy required files to your phone
Main download link:
https://www.androidfilehost.com/?w=files&flid=201577
Mirror download link:
https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel/releases
In order to tweak the kernel properly, you need to install stweaks from the apk linked here, or from the XDA downloads page
Troubleshooting
Q: Why flash your kernel? - For new users of DorimanX kernel
DorimanX kernel is an aftermarket kernel (or custom kernel) that is designed to allow users to tweak their phone at the kernel or near-hardware level side of things. In other words, users get more fine-grained control over their phone, this includes overclocking, underclocking, changing behavior of CPU/GPU etc. Adjusting such settings isn't for the faint-hearted since there is many things to understand, but you aren't required to understand all of the settings. Ultimately, if you want to improve your phone experience, try DorimanX kernel!
Q: Which kernel version build should I flash?
A: Flash the latest stable version if you want the most stable experience. Beta builds will always have the latest features and should be fine to use as a daily driver. Stable builds have been thoroughly tested for issues, but are usually older than current builds. Either way, it's up to you which one you want to flash. Read the changelog for any important changes that might have occurred in a particular build.
Q: Which app should I use to tweak the kernel?
You should only use stweaks to tune DorimanX kernel.
Q: Can I use isorec recovery on DorimanX kernel?
A: Yes you can. All important information was covered in the OP already!
Q: Why should I flash your builds when the last 'real' unofficial build was v008?
A: If you don't want to enjoy awesome features that improve the experience of dorimanx kernel, then it doesn't worry me. Real or not, I don't build kernels to have bad battery life, bad stability and etc. This is my personal build of dorimanx kernel!
Q: Wifi doesn't work after I flash this kernel
A: There are several possible causes to this issue, there could be a problem with your:
- Partitions OR
- Permissions OR
- Gapps OR
- ROM OR
- Compatibility with your wifi hardware
Don't use a pit with modded preload! It will just cause issues with ROMs and Kernels. Use stock pit or use a pit with unmodded preload. Sometimes, the gapps package you flash somehow breaks compatibility with the kernel. You can fix this by flashing a different gapps (making sure to clean cache and dalvik). If you have permissions problem, you can fix this by repartitioning your internal sd card or by reflashing back to stock rom. Sometimes, the ROM doesn't fully support the wireless drivers in the kernel, this can be solved by flashing a different ROM or different kernel. But if your wifi hardware is not compatible (a way to tell this is when you have tried everything and failed), there is nothing you can do but reflash the rom or flash a different kernel.
Q: I came from a different custom kernel that used Stweaks, now the app has issues
A: Every time you come from a different custom kernel with stweaks support, make sure to wipe cache and dalvik cache after install dorimanx kernel
Q: My battery life sucks after flashing this kernel!
A: Download and install Betterbatterystats and see what is the culprit to your problem. If it is kernel related, have you made sure you have wipe cache and dalvik and reset stweaks settings? If yes, it would be nice if you posted a logcat.
Q: How do I get a logcat for the kernel?
A: In stweaks, go to BUG-REPORT and tap on KERNEL-BUG.
Q: Why do I get bootloops with this kernel?
A: If you were on a working version on dorimanx before, there is probably something wrong with the installation. Sometimes, bootloops can occur due to corruption of the kernel zip file (usually from bad download) or from corrupted partitions.
Q: What do all of the settings mean? They are all confusing!
A: Please note that DorimanX kernel isn't for users who have just rooted their device. Before jumping into the custom kernel world, try playing around with other kernels first. Once you think you have some experience, read the stweaks beginners guide I made and then attempt to tweak the kernel using stweaks.
Q: How do I trim my partitions?
BEWARE: Make sure you have read all of the precautions before attempting to trim your partitions!
A: install the trimmer app from the playstore. App link . Check for all 3 partitions, and tap on run. grant root access. the 3 fstrim operations should be successful ("partition was trimmed" means success).
alternatively, instead of using trimmer you can run one of these commands (these are better because they also trim /preload):
# on the phone in the terminal app:
su -c "fstrim -v /system; fstrim -v /data; fstrim -v /cache; fstrim -v /preload"
# on your PC if you are connected to the phone via adb:
adb shell su -c "fstrim -v /system; fstrim -v /data; fstrim -v /cache; fstrim -v /preload"
reboot.
Click to expand...
Click to collapse
Q: My device is (hard) bricked after flashing your kernel!
A: Have you read all of the precautions before installing the kernel? You made the decision to flash the kernel and now you've stuffed up your phone.
Q: I get constant FCs after flashing your kernel!
A: Have you wiped your cache partition, dalvik cache and reset stweaks settings? If you've done all of these already, a logcat would be nice
Q: How do I use dual boot?
A: There are many guides on how to dual boot roms using dorimanx kernel. Just use the search function on XDA or GOOGLE it!
Q: What's a good combination for CPU governor and I/O scheduler?
A: Have a look at the default settings, they are optimised for our phone
However, here are some settings I recommend:
CPU Governor: HYPER/zzmoove/Darkness
I/O Scheduler: CFQ/BFQ/ZEN/Deadline/SIO
Q: Why does the screen turn blank after the dorimanx logo appears during the boot process?
A: If your kernel doesn't bootloop, but the screen remains blank, there is a good chance that the ROM that you've used uses an older version of GPU drivers (Mali). This kernel only support ROMs with Maliv3 support. If you flash this kernel on MaliV2 or MaliV1 only roms, you will get a blank screen after flashing. To fix this, flash to the kernel the corresponds to your mali driver version and you should get your display back.
Q: What is a TCP algorithm?
A: Congestion control strategies (or algorithms) are used by TCP, the data transmission protocol used by many Internet applications. The main goal of a TCP algorithm is to avoid sending more data than the network is capable of transmitting, that is, to avoid causing network congestion.
Q: What is a toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Q: What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Q: Why not use XYZ toolchain?
Linaro toolchain is the only one I'm going to use. If you believe that XYZ toolchain is better, then you'd have to build my kernel yourself. I chose the toolchain that I like the most, and I've had positive experiences using Linaro.
Click to expand...
Click to collapse
First kernel build for LOS14.1 is up on AFH and github. Enjoy.
Firstly, sorry for the dupe threads. Internet was acting out and now I'll have to get the mods onto it
Also, expect bugs with this release. This is a really early build and I'm doing blind builds now.
Don't flash on any other ROM than LOS otherwise you will not receive support. This kernel is only designed for LOS.
No new features will be added because I don't use the S2 as daily driver, so I won't be able to test changes thoroughly.
Regards, Saber
Nice.
Hi @Saber
Thanks a lot for spending your spare time to work on this kernel.
I wish you the best!
Sent from my STAIRWAY using XDA-Developers Legacy app
Welcome back @Saber
EDIT: I am not able to get it work on latest LOS 14.1 build. May be something wrong on my side. Phone going back to galaxy s2 logo from dori kernel logo. This is happening in loop. Anyone???
Yeah this is cool. Maybe we can make S2 N-builds even better. :laugh:
Skyline said:
Welcome back @Saber
EDIT: I am not able to get it work on latest LOS 14.1 build. May be something wrong on my side. Phone going back to galaxy s2 logo from dori kernel logo. This is happening in loop. Anyone???
Click to expand...
Click to collapse
Can you please detail your flashing procedure? Did you try reflashing the kernel?
Saber said:
Can you please detail your flashing procedure? Did you try reflashing the kernel?
Click to expand...
Click to collapse
I get it to work after too many tries and now again I am not able to boot.
*Wiped everything other than ext sdcard
*flashed rom and gapps
*flashed kernel zip
Also tried without gapps. Weird thing is that whenever I flash gapps it gives me alot of force closes. I tried 2 gapps packages and AICP but same problem occurs(without flashing kernel) that's why I thought may be something wrong on my side
Edit: I am using I9100g display panel can it be reason for my problem?? Anyways I attached dmesg.
Nice
Nice Kernel,Works fine on los14.1 and I also have overclocked up to 1.6 MHz but would not like to add 2.0 MHz in future updates?
And is it possible to add support to the kernel dt2w ?
Sorry if I'm not writing correctly, I'm not an Englishman :laugh:
X_Svyatoslav_X said:
Nice Kernel,Works fine on los14.1 and I also have overclocked up to 1.6 MHz but would not like to add 2.0 MHz in future updates?
And is it possible to add support to the kernel dt2w ?
Sorry if I'm not writing correctly, I'm not an Englishman :laugh:
Click to expand...
Click to collapse
If you mean 2,0GHz I doubt it.
I tried F2FS and it seems cache is okay but data makes android.phone process crash all the time. Not sure if it is LOS or kernel's fault.
X_Svyatoslav_X said:
Nice Kernel,Works fine on los14.1 and I also have overclocked up to 1.6 MHz but would not like to add 2.0 MHz in future updates?
And is it possible to add support to the kernel dt2w ?
Sorry if I'm not writing correctly, I'm not an Englishman :laugh:
Click to expand...
Click to collapse
What?? 2.0 Ghz is too much and also not safe. Even overclocking more than 1.4 Ghz is not good for our old device. I think we should limit cpu clock to 1.4Ghz max on this kernel for safety @saber.
Syaani said:
I tried F2FS and it seems cache is okay but data makes android.phone process crash all the time. Not sure if it is LOS or kernel's fault.
Click to expand...
Click to collapse
This issue is actually kernel's fault as it also exists on my CM13 kernel. A reboot is a possible solution to solve this issue and it shouldn't reappear. I might pull some F2FS updates from the linux git to increase stability, however the only filesystem I recommend is ext4 for internal partitions.
Edit: I was thinking before about a kernel issue where after first flashing the kernel over stock LOS kernel, the phone process would crash where it can be solved by rebooting. Need more reports to see if its just F2FS or if its regardless of fs used.
X_Svyatoslav_X said:
Nice Kernel,Works fine on los14.1 and I also have overclocked up to 1.6 MHz but would not like to add 2.0 MHz in future updates?
And is it possible to add support to the kernel dt2w ?
Sorry if I'm not writing correctly, I'm not an Englishman :laugh:
Click to expand...
Click to collapse
2.0GHz? Not possible with our SOC. 1.6GHz is about the limits and only a lucky few are able to use this frequency. Any more and I'd suspect our tiny SOC go poof along with some bad electronic smoke.
dt2w is not optimised for our touch panel and as of a result, significant battery drainage will occur. It's the same story with sweep to wake, these features weren't even supposed to be possible with our device.
Skyline said:
I am using I9100g display panel can it be reason for my problem?? Anyways I attached dmesg.
Click to expand...
Click to collapse
I've had a quick skim over the dmesg and couldn't find anything too substantial to be the root cause of the issue (may need to go through with a fine comb). Maybe logcat? How about marshmallow? Does the same behaviour occur there?
Saber said:
I've had a quick skim over the dmesg and couldn't find anything too substantial to be the root cause of the issue (may need to go through with a fine comb). Maybe logcat? How about marshmallow? Does the same behaviour occur there?
Click to expand...
Click to collapse
If I comment last lines in init.rc then rom boots fine
EDIT: @Saber, How can I take logs during s2 bootlogo to dorimanx kernel logo? I tried to take logcat using command 'adb logcat > log.txt' on linux but device is not getting detected.
X_Svyatoslav_X said:
Nice Kernel,Works fine on los14.1 and I also have overclocked up to 1.6 MHz but would not like to add 2.0 MHz in future updates?
Click to expand...
Click to collapse
With 2.0 GHz the CPU will explode
X_Svyatoslav_X said:
Nice Kernel,Works fine on los14.1 and I also have overclocked up to 1.6 MHz but would not like to add 2.0 MHz in future updates?
And is it possible to add support to the kernel dt2w ?
Sorry if I'm not writing correctly, I'm not an Englishman :laugh:
Click to expand...
Click to collapse