Related
MiRaGe is a lean and efficient kernel for the stock Nexus 4 ROM with the optimizations and updates that are not included in Google's stock kernel. MiRaGe kernel fits squarely in the stock Nexus 4 ROM; all of the modules are integrated in the kernel just like the stock kernel and it should work with all AOSP ROMs that work with the stock kernel and boot image. However, only the current stock ROM is tested. If you decide to use MiRaGe, just flash and forget it since I have avoided adding more sysfs parameters. It is not my goal to enable all possible tweaking options and add every possible feature to the kernel such as multitude of governors, io schedulers, sweep2wake, fastcharge, etc. This kernel is not intended as a tweaker's kernel. You can, of course, tweak it as much as you want since that is your phone and kernel. But please try removing your tweaks before posting any problems. I always test the latest builds with the current stock ROM before posting here.
I am sharing exactly what I have developed for myself and posting here so that I can return at least a small part of what I have received from the open source community. I thought the amount of time I have spent for MiRaGe could be useful for others as well. In short, take it if you want it, leave it if you don't. But comments, suggestions are always welcome when they make sense.
Source Code:
Source code is based on Google's msm kernel source (currently android-msm-mako-3.4-lollipop-mr1.1) and a summary of my changes are below. You can find the full details of my changes and the complete source code in my repo.
Changes:
- synced with mainline Linux 3.4.110
- cleaned up kernel configuration and removed many unnecessary options
- removed kernel debugging options
- built with the Linaro toolchain (gcc 4.9.4 - 15.06) using standard krait and -O2 optimization
- removed AOUT and OABI support
- disabled both user-space msm_mpdecision and kernel-space msm_mpdecision
- removed msm_run_queue_stats, dcvs, and stock msm_mpdecision in the kernel
- added autosmp, a simple and efficient (by me) multi-core cpu hotplug driver
- disabled the user-space thermald and switched to kernel-based msm_thermal
- replaced CFQ with the latest BFQ as the default IO scheduler
- backported random and prandom updates from Linux 3.13 (no entropy depletion anymore)
- backported workqueue from Linux 3.8 to include many important improvements
- backported rwsem from Linux 3.11 to include lock stealing improvements
- backported mutex and rcu locking from Linux 3.10 and 3.8, respectively
- backported slub memory allocator updates from Linux 3.8
- backported cpufreq driver, ondemand, and conservative governors from Linux 3.12
- updated interactive CPU governor from AOSP and CAF
- disabled userspace CPU governor,
- enabled callback-free CPUs (RCU_NOCB_CPU)
- backported TCP Small Queues and CODEL net scheduler from Linux mainline and set as default
- updated kernel scheduler, msm-hotplug, msm-idle, msm-pm code from CAF and Linux mainline
- applied patch [v4] binfmt_elf.c: use get_random_int() to help with entropy depleting
- enabled autogroup scheduler and applied patch per-uid task group for Android
- added optimized ARM RWSEM algorithm
- added optimized ARM SHA1/AES routines
- enabled CPU-supported unaligned accesses
- disabled gentle fair sleepers in scheduler
- updated Qualcomm HW RNG driver from CAF
- enabled BPF JIT compiler for packet filters
- applied glibc patch to improve the performance of memcpy and memmove
- applied word-at-a-time ARM API patches
- enabled CPU overclocking up to 1.728 GHz with user-space vdd control
- optimized vdd curves, L2 and bus speeds for better performance and efficiency
- removed unneeded a2xx and a4xx components from kgsl driver
- modified the prima wifi driver to disable debug code
- removed PMEM completely, MiRaGe is pure ION
- add support for kernel mode NEON and NEON acceleration
- add NEON optimized SHA1, SHA256, and SHA512 crypto code
- add LoUIS API for cache maintenance ops to improve cpu hotplug latency
- added and enabled power_efficient workqueue
- added and enabled msm memutils
- added screen gamma, user space cpu voltage control, and dt2w
- backported devfreq driver from CAF and switched kgsl 3d governor to simple_ondemand
- backported many other fixes/updates/optimizations from CAF and Linux mainline, see the repo for details
- init.d supported if /etc/init.d and busybox are available
- a diff file of changes to ramdisk is here
Downloads:
Boot image for stock ROM:
LMY standard kernel Built: 10/25/15 MD5sum: a315cc446499d60cb4b3a61ea7bfa8f8
LMY overclock kernel Built: 10/25/15 MD5sum: 7c72a66830f511b025968db2bb743429
Anykernel updater for custom ROM:
Revert back to stock kernel to restore the original ramdisk and flash anykernel package of MiRaGe after that. This is not needed in the next anykernel update.
LMY standard kernel Built: 10/25/15 MD5sum: 85b4136ac0ada793da7b80763193095a
LMY overclock kernel Built: 10/25/15 MD5sum: 2924fb6a963b40087c296a7b1abfc1d3
KTU standard kernel Built: 10/31/14 MD5sum: dca7d06933eb43c8da3ba7941bb6ac88
KTU overclock kernel Built: 10/31/14 MD5sum: dca7d06933eb43c8da3ba7941bb6ac88
The only difference between the standard and overclock builds is the ~100mV undervolt in the overclock build. Both kernels have maximum CPU_freq = 1.728 GHz, default CPU_freq = 1.512 GHz, overclocking, and user space cpu voltage control enabled. Since the CPU gets hot quickly in Nexus 4, I only recommend overclocking with the overclock build that has built-in undervolt. If the phone doesn't boot with overclock kernel, it means that your CPU is not able to handle the undervolt settings. In that case, you can just reboot into recovery and flash the standard kernel. No-frills CPU Control is recommended to set the max overclock frequency. Each CPU has different overclock/undervolt ability. Don't get disappointed if the OC build doesn't work for you.
Installation:
You can do one of the followings
- Flash the zip files in recovery, there is no need to wipe cache or dalvik-cache
- Flash the boot image in the zip file using either Flash Image GUI or fastboot
- Here is the original boot image for LMY48I build, in case needed for going back to stock. Either flash in the recovery or open the zip file to extract the boot image.
Credits:
- Special thanks to Linux, Google, CAF, Linaro developers in general.
- @tvall, @bedalus, @xboxfanj, @ihancioglu, @xenyz for collaboration
- @stratosk for the screen gamma interface and dt2w
- @defconoi for collaboration (see Unleashed Kernel Series)
- @mathkid95 for the any-kernel updater package
- @joeykrim for FlashImageGUI
- @Christopher83 for the optimized Linaro toolchain builds
- Other credits are given in the repo for each commit
Recommendations:
I am frequently receiving requests to add sound patches in the kernel. I agree that the sound is not very good but there are solutions. I am using the Viper4AndroidFX as a replacement sound processor. I recommend giving it a try. You need to go to the sound options and select ViPER4AndroidFX to use this sound processor or freeze MusicFX (I use Link2SD for this). There is plenty of information at the above link. With this available, I am not planning to add any sound patches.
Another frequent question is about choosing CPU governor and IO scheduler. In the earlier builds, interactive governor had the best balance of performance and battery life among other CPU governors and it is still available. In the latest builds, ondemand governor was backported from Linux 3.12 and replaced interactive as the default. The latest patches in the mainline Linux, especially stratosk's patch that optimized the load calculations made the new ondemand governor the better option regarding both power and performance. Regarding IO scheduler, BFQ scheduler has the best overall real-use performance and it is actively maintained/improved. You can use Nofrills CPU Control to change the governor and scheduler. But I would leave the defaults as BFQ scheduler and ondemand governor.
Since all of the cpu power control functions are contained in the kernel with MiRaGe, the userspace PowerHAL library will be giving the following messages in the logcat.
Code:
E/PowerHAL( 511): touch_boost: failed to send: No such file or directory
E/PowerHAL( 511): touch_boost: failed to send: No such file or directory
E/PowerHAL( 511): touch_boost: failed to send: No such file or directory
These are harmless but if you want to eliminate them, just make a backup and delete/rename /system/lib/hw/power.msm8960.so and power.mako.so. The single purpose of touch_boost is to enhance the system response to the user interaction. But using a service in the user space to send a touch boost signal to the kernel via slow sysfs file system is the wrong way of trying to achieve lower latency. In addition, every touch input doesn't need a CPU frequency boost which wastes battery power. The best way of achieving the low-latency system response to user interaction is improving the efficiency of existing CPU governor which raises the CPU frequency and hotplug driver which enables off-line cpu cores when needed. In MiRaGe, CPU freq is only controlled by the CPU governor based solely on the CPU load and the latency is low since efficiency is improved by reducing such unnecessary bloat. Additionally, highly-efficient autosmp hotplug driver works in-sync with the CPU governor to enable off-line cpu cores when the the CPU frequency reaches a high threshold and still more compute power is needed. Therefore, touch boost bloat is removed.
With some of the custom ROMs, root is lost after flashing MiRaGe because of using the init scripts in the ramdisk for starting the su daemon. SuperSU is the recommended solution. I might switch to any-kernel-updater to address this problem but as written in the OP, MiRaGe is primarily for the stock ROM. Also, having the full boot image in the zip file is more reliable than expanding/processing/repacking the boot image.
MiRaGe supports init.d if it is setup. To setup init.d do the followings either within ES File Explorer or terminal .
- install busybox (I use busybox on rails)
- create /system/etc/init.d and chmod to 755 (rwxr-xr-x)
- create your init scripts in the /system/etc/init.d directory. Name them 01yourscriptname (e.g. 01mysettings) and chmod 755. Make sure they are UNIX format (not in DOS/Windows).
example:
Code:
#!/system/bin/sh
echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_enabled
- reboot
Here is how to add multiROM support
How to build:
If you are going to distribute your builds, please don't build your binaries with the same name (i.e. MiRaGe) and distribute in this thread. I would recommend you to start an alternative thread. Otherwise the problem reports will be too confusing for everyone.
First requirement is an ARM toolchain for cross compiling, i.e. using an X86 computer to generate ARM binary. I use Linaro tool chain for cross compiling like many others since Linaro specifically develops tool chains that produce optimized binary for ARM architecture.
Linaro toolchains can be downloaded from Linaro binary page. Christopher83 has built the latest Linaro-14.08 toolchain based on gcc-4.8.4 which is stable/reliable and I recommend starting the development with this toolchain.
The binary Linaro toolchain for Linux package needs to be expanded in a certain directory, probably inside the home directory. The source code for kernel is available in my Github repo, You can either download the kernel source as a compressed package or you can git-clone it with the following command (you will need git installed in your Linux computer)
Code:
git clone https://github.com/mrg666/android_kernel_mako.git
The kernel source can again be in a specific home directory.
After the source and toolchain are prepared, copy the configuration file for shooter, arch/arm/configs/mako_config, as .config to the root of the kernel source and use the following command to build the kernel
Code:
make ARCH=arm CROSS_COMPILE=~/untarred-toolchain-dir/bin/arm-linux-gnueabihf- zImage -j8
Replace j8 in the above command according to the number of cpus you have on your computer.
Also set CROSS_COMPILE based on the directory you have expanded the binary toolchain package in your home directory.
I always use the latest version of Xubuntu x64 (with custom built kernel) on my Linux workstation that has a AMD FX-8320 (overclocked to 4.2 GHz), 8 GB RAM, 500 GB HD. The compile time is about 2 minutes for me using all 8 cores. I have been using Ubuntu since version 10.04 to build Gingerbread, Jellybean, and Linux kernel and updated the OS to each and every new version, all of them worked just fine. There is no magic version of Ubuntu. The build problems arise from the package requirements not the OS version.
The flash package is easy. Just use any-kernel updater package in the OP as a template and replace zImage in /kernel directory with your build. If you want to create a boot image, see this post
Now that you have source and can build the kernel, you can add all the features you want to your own kernel
Woww greatt, thanks mirage
many thanks Mirage!
Does JSS come with caf video driver or it can be flashed on non-cm roms without problems?
Inviato dal mio Nexus 4 con Tapatalk
Good to see new kernel which goal is simplicity, not many of them are here. ill try it when clean instal comes to repertoar. just one question, you didnt mention -O3 and gcc 4.8.2, so i asume you didnt use them? Thanks.
Poslano sa mog Nexus 4 koristeći Tapatalk
I haven't updated the video driver from CAF ... yet. I will do after the 4.4 update if Google hasn't done yet.
Kernel is compiled with gcc 4.7.4 using -O2 optimization. gcc 4.8 was not giving me reliable builds yet. I will switch when 4.8 becomes stable. I have tried O3 optimization in the past and I didn't see any benefit of it. Plus, O3 optimization caused reliability issues especially with the latest gcc compilers.
MiRaGe should be compatible all AOSP-based ROMs, as long as the same user-space libraries are used with the stock 4.3 ROM. I can't claim universal compatibility since even stock JSS and JWR builds need different kernels.
Would you consider making a ZIP?
I found your kernel to be quite interesting, but I don't really like flashing via IMG file.
C.T.Richter said:
Would you consider making a ZIP?
I found your kernel to be quite interesting, but I don't really like flashing via IMG file.
Click to expand...
Click to collapse
you can download one of 1000 kernels around here and replace the kernel.img ... and wholà you have a zip version.
anarkia1976 said:
you can download one of 1000 kernels around here and replace the kernel.img ... and wholà you have a zip version.
Click to expand...
Click to collapse
Can't agree with you more but the problem with so many people on xda is that they rarely even open up a zip file to see how it operates. Guarantee most of the people will shy away simply because of the lack of a zip. Again I agree its not that hard to do but lets be honest here most have problems searching so taking a boot.img and putting it in a zip probably aint happening
I have just uploaded the alternative flashable zip files. I will remove the image files since they are in the zip files now.
Just flashed on slim and lost root... Just a heads up
Sent from my Nexus 4 using XDA Premium 4 mobile app
anarkia1976 said:
you can download one of 1000 kernels around here
Click to expand...
Click to collapse
LOL that's right!
QUIETLYloud said:
Just flashed on slim and lost root... Just a heads up
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That can't happen due to flashing the zip files in the OP since there is nothing in the zip file that touches /system, it is not even mounted.
Gonna give it a go on Vanir. I'll report back of my root gets effected. Happened a lot with 4.3 when it first came out
Sent from my Nexus 4 using Tapatalk
DontPushButtons said:
Gonna give it a go on Vanir. I'll report back of my root gets effected. Happened a lot with 4.3 when it first came out
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I am using CWM 6.0.4.4. It is constantly suggesting to restore my root although it is not lost. If this is what is mentioned here, just ignore it; root is not lost. SuperSU, su keep working. Actually, I am losing my patience with CWMT lately. Maybe it is time to switch to TWRP.
mrg666 said:
I am using CWM 6.0.4.4. It is constantly suggesting to restore my root although it is not lost. If this is what is mentioned here, just ignore it. Root is not lost. SuperSU, su keeps working. Actually, I am loosing my patience with CWMT lately. Maybe it is time to switch to TWRP.
Click to expand...
Click to collapse
I'd say it's long overdue to switch to twrp lol. Ever since I switched to twrp back on my rezound, I have NEVER looked back to cwm. Not to say cwm isnt/wasn't great.. But you know how it is lol.
Sent from my Nexus 4 using Tapatalk
DontPushButtons said:
I'd say it's long overdue to switch to twrp lol. Ever since I switched to twrp back on my rezound, I have NEVER looked back to cwm. Not to say cwm isnt/wasn't great.. But you know how it is lol.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I just don't like the "overdesigned" interface of TWRP. It is too fancy for my taste. But as long as it works when needed, it would be fine with me. I don't boot into recovery so frequently anyway since I flash the kernel in fastboot or Flash Image GUI.
Oddly enough, I lost root. I'm currently running the latest version of Paranoid Saberdroid.
C.T.Richter said:
Oddly enough, I lost root. I'm currently running the latest version of Paranoid Saberdroid.
Click to expand...
Click to collapse
Is it just what the recovery says? I use the stock JWR ROM and root is preserved when I flash although CWMT falsely complains about it.
Edit: I just tested with TWRP as well. Root is still preserved.
mrg666 said:
Is it just what the recovery says? I use the stock JWR ROM and root is preserved when I flash although CWMT falsely complains about it.
Edit: I just tested with TWRP as well. Root is still preserved.
Click to expand...
Click to collapse
Using TWRP there is no error message, it just says it was installed successfully.
I just tried it on a clean install, and the same thing happened.
TDH Kernel for the Moto X Unified (CAF)
The kernel is that which manages the phone at a fundamental level. To learn more, see the "Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel."
How I Support This Work:
Donations always work
Thanks buttons also work wonders. Don't forget to hit the Thanks button for those whose work benefits you.
If I don't respond to a question, there is a very high likelihood the answer already exists in this thread -- use search as I rarely forget what's already covered.
Working Features:
AOSP
Best battery life (kernel installs init.d script to setup SmartMax governor)
Governors: SmartMax, Intelliactive, interactive, ondemand, userspace, powersave, performance (more coming if relevant -- 'marketing checkmarks' -- a.k.a. useless but stuck in just for feature count -- won't get into this kernel)
Optional IOSched: Noop, Deadline, CFQ, BFQ, FIOPS, SIO (more coming if relevant -- same comment applies as for Governors)
Optional GPU Governors= Performance, Ondemand, Simple, Interactive
User voltage control
Kexec support
Initial Kexec support
ExFAT support
KSM optimizations
Enhanced NEON support
Reduce kswapd schedule enhancement
EXT4 file system speed ehancements
Many stability and optimizations upgrades.
In progress / futures (not stable yet) ...
Overclocking/underclocking options (in progress ... sigh , coming soon)...
Optional GPU overclocking
Doubletap2wake
Logo2wake
Pocket detection
Logo2menu.
Credits go to many, but most particularly:
Linus Torvalds (for Linux itself)
Flar2
Faux123
ThickLizard
TBaldin
A lot of other kernel devs whose code I read regularly to learn
All the Moto X Community
Instructions:
READ THE DISCLAIMER.
Download the kernel
Reboot into Recovery
Nandroid backup
Flash the kernel
Enjoy
Things to Know:
The flash uses standard 'by-name' partitions, so should install correctly on most AOSP based ROMs
The flash supports the CM11 standard /data/local/userinit.d init script (99-tdhk)
That script will delay one minute after boot and force the SmartMax governor on all cores
FIOS is the default IO scheduler
No need for Trickster or Performance Settings if you want those defaults (which you should)
KERNEL SOURCE
Enjoy.
XDA:DevDB Information
TDHK, Kernel for the Moto X
Contributors
tdhite, skiwong20
Source Code: https://github.com/tdhite/android_kernel_motorola_msm8960dt-common
Kernel Special Features: Governors, schedulers, sleep/wake options, battery tweaks, performance tweaks.
Version Information
Status: Stable
Current Stable Version: KitKit: 12/21/2014;
Stable Release Date: 2015-09-20
Created 2014-07-19
Last Updated 2015-09-20
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use any of the software provided by this thread, or convey such software to
someone else, you and all subsequent conveyees are bound by the following:
# LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
# Assumption of the Risk of Use
# YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS
# PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY,
# IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY
# MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE
# ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE
# RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT
# TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
#Disclaimer of Warranty.
# THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
# LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
# OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND,
# EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
# THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
# YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND
# AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR
# EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR,
# CORRECTION OR OTHERWISE.
#Limitation of Liability.
# IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
# ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
# PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE
# RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
# ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
# LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
# BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
# PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGES.
Downloads
KERNELS (Current):
Download: TDHK-Ghost Lollipop 09-20-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost KitKat 12-21-2014
This kernel is for KitKat AOSP ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-MotoX 08-31-2014
This kernel is for ROMs *before* the unified 'ghost' model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'msm8960dt' AOSP rom -- of course read the DISCLAIMER post.
IMPORTANT:
If you wipe Dalvik Cache, let the phone boot completely once, then reboot again (long story, but AOSP roms set a property on Android that triggers your selected 'performance' settings (e.g., performance, balanced, whatever), when you clear Dalvik that property set trigger runs rather late and the init.d script delay setup by this kernel to force smartmax onto the CPU cores might already have happened, so you end up with the old governors (ick!). Reboot and all should be fine.
Another option is to open a terminal window and 'su' to root privileges, then type "set prop sys.perf.profile 99". No need to reboot if you do this.
OLD Releases:
Download: TDHK-Ghost Lollipop 09-17-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
B]Download: TDHK-Ghost Lollipop 08-07-2015[/B]
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 07-20-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 06-28-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 05-24-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 04-06-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 01-11-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.3.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 12-21-2014
This kernel is for LolliPop AOSP ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-26-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-16-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-05-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 09-20-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
KERNEL (Enhanced -- no longer needed as integrated into standard kernel):
Download: TDHK-MotoX 08-10-2014
KERNEL):
Download: TDHK-MotoX 07-28-2014
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any AOSP rom -- of course read the DISCLAIMER post.
IMPORTANT!!!
If you wipe Dalvik Cache, let the phone boot completely once, then reboot again (long story, but AOSP roms set a property on Android that triggers your selected 'performance' settings (e.g., performance, balanced, whatever), when you clear Dalvik that property set trigger runs rather late and the init.d script delay setup by this kernel to force smartmax onto the CPU cores might already have happened, so you end up with the old governors (ick!). Reboot and all should be fine.
Another option is to open a terminal window and 'su' to root privileges, then type "set prop sys.perf.profile 99". No need to reboot if you do this.
Custom Kernel 07/17/2014
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
[*]SmartMax Tweaks (better battery credit: Rad Ryan);
[*]Startup (/data/local/userinit.d/99-tdhk) handling to force SmartMax governor on all cores;
[*]Rebased onto CM-11 MSM8960 Kernel Sources as of 07/17/2014;
[*]Make Nandroid backup;
[*]Flash in recovery after flashing ROM;
Change Logs
TDHK-Ghost Lollipop 09-20-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost KItKat 12-21-2014
Synced with CM11 sources as of the date of the build.
Use this if you download a KitKat 'ghost' ROM.
TDHK-MotoX 08-31-2014
Fixes intermittent data drops for very latest ROM versions, as well is failures to load WiFi on the same.
Contains all updates to base kernel, CM11 and prior 'enhanced' version -- all as of date of build.
Use this if you download a msm8960dt based ROM.
Prior Releases
TDHK-Ghost Lollipop 09-17-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 08-07-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 07-20-2015
Fix multi-core governor (not)stickiness when cores go offline.
Synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 06-28-2015
Maintenance release.
Synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 05-24-2015
Maintenance release.
Synced with CM12.x sources as of the date of the build.
Disabled quickdraw (which was the brunt of CM12.x updates).
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 04-06-2015
Maintenance release.
Synced with CM12 sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.0 ) .
TDHK-Ghost Lollipop 01-11-2015
Intelliactive governor
Initial Kexec support
ExFAT support
KSM optimizations
Enhanced NEON support
Reduce kswapd schedule enhancement
EXT4 file system speed ehancents
Many stability and optimizations regarding buffer overruns and similar
Synced with CM12 sources as of the date of the build -- includes fix for NFC.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.0) .
TDHK-Ghost Lollipop 12-21-2014
Synced with CM12 sources as of the date of the build -- includes fix for NFC.
TDHK-Ghost 10-26-2014
Synced with CM11 sources as of the date of the build -- includes fix for NFC.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 10-16-2014
Synced with CM11 sources as of the date of the build to pick up WiFi enhancements.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 10-05-2014
Added user level CPU Voltage Control.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 09-20-2014
Based on Ghost unified sources (should work on effectively any AOSP based ROM);
Contains all updates to base kernel, CM11 and prior 'enhanced' versions -- all as of date of build.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-MotoX 08-10-2014
Contains all that is in the Stable version.
Enhancements include upstream commits bringing the kernel up to 3.4.101.
Additional thanks to @dhacker29 for much of the upstream commits -- they're just not in CM yet, maybe one day ...
TDHK-MotoX 07-28-2014
Fixed SmartMax governor bug that caused screen to stay off after some reboots.
Changed bootup and governor setting model to support Android property model (sets up /init.target.rc to import /init.tdhk.rc, the latter of which triggers to set smartmax whenever the Android property "ro.perf.profile" is set to "99".
Yay! AOSP kernel..
Booted up great!
XT 1058 running leonardoafa unofficial carbon rom!
Thanks. Downloading to test on XT1053.
Flashed great. XT1058 on Dirty Unicorns
Can i install it on stock 4.4.2? Or just 4.4.4?
Sorry, dude. Not looking backwards, I doubt less than 4.4.4 will work but you can always flash any try.
Do me a favor and turn on the CPU options in the developer's options. See that the smartmax governor is on all cores.
Want to be sure the init.d script is properly executing on that ROM (DU).
Wi-Fi and Signal lost after installing on XT1053 (Stock 4.4.3)
Im just making sure, this only works on AOSP roms and not stock, right?
Kittiesoncrack said:
Im just making sure, this only works on AOSP roms and not stock, right?
Click to expand...
Click to collapse
Yip, that's right.
kenosis said:
Wi-Fi and Signal lost after installing on XT1053 (Stock 4.4.3)
Click to expand...
Click to collapse
4.4.4, not 4.4.3. Maybe one day I'll look at building backwards to others, but while stabilizing some new features, it's 4.4.4 or up.
Works great on the Droid Maxx!! Thanks man... Much needed!
What 4.4.4 rom is everyone using?
tdhite said:
Yip, that's right.
4.4.4, not 4.4.3. Maybe one day I'll look at building backwards to others, but while stabilizing some new features, it's 4.4.4 or up.
Click to expand...
Click to collapse
Thanks. Hope to see it for 4.4.3.
tdhite said:
Do me a favor and turn on the CPU options in the developer's options. See that the smartmax governor is on all cores.
Want to be sure the init.d script is properly executing on that ROM (DU).
Click to expand...
Click to collapse
{
"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"
}
Remember to quote so I'll get the notifications
@tdhite, can you provide the sources...
Sent from my GT-I9082 using Tapatalk
awesome job tdhite. thanks for your time on this project, so happy to see a CAF kernel available. ?
##W4TCH0UT## said:
@tdhite, can you provide the sources...
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
kernel source add to OP
Sent from my AOSP on Flo using XDA Free mobile app
skiwong20 said:
awesome job tdhite. thanks for your time on this project, so happy to see a CAF kernel available. ?
https://github.com/tdhite/android_kernel_motorola_msm8960dt-common
i will tell him later to add to op
Sent from my AOSP on Flo using XDA Free mobile app
Click to expand...
Click to collapse
It's not the source. It doesn't include the commits of features he has mentioned in the op. So he hasn't uploaded the kernel source.
Sent from my GT-I9082 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.
Jesse's Kernel (I am not good at naming sth.)
for Galaxy S8 and S8+ (Exynos)
(G950F/FD/X/N) and (G955F/FD/X/N)
This kernel is designed to be SIMPLE and STABLE with improved performance and battery life.
Just flash and enjoy your phone. No additional setting required.
This kernel has 3 series,
Early-Testing: Contains latest changes, experimental features. This build will be released to testers only.
Stable: Changes, features in early-testing build will be picked into stable once they are confirmed to be stable.
Semi-Stock: For those who want maximum stability or ROM developers who want to integrate with their ROMs. This build is very similar to stock but it will have some useful changes like SELinux permissive, disabled security features, etc. This build will be released to public in low update frequency(usuallly based on stock kernel changes).
LICENSE:
Kernel sources:
GPL 2.0: https://www.gnu.org/licenses/gpl-2.0.html
Kernel binaries, patches to system, ramdisk modifications, etc.:
Code:
You can use, mirror, modify and/or integrate it/them with your own works, WITHOUT inform me, subject to the following conditions:
1. Credit MUST be given. (a possible form: thanks *** for ***)
2. Warranty is NOT provided. I am not responsible for any possible losses.
3. Authorization may be TERMINATED for selected person without prior notice under certain conditions (subject to my sole discretion).
4. Above conditions must be preserved. (You have the responsibilities to inform your users about these conditions. A possible way is to add "LICENSE: (link to this post)" to "thanks *** for ***")
Features:
STABLE: (Mainline)
Toolchain: Linaro GCC 7
Linux 4.4.79 (updated from 4.4.13)
Always SELinux Permissive (with fake SELinux Enforcing status.)
Kernel Security Features, Root Restrictions are DISABLED
Linux mainline random generator driver backported
Max frequency of big cores set to 2.5GHz
Other optimizations, backports for best performance and power efficiency
BFQ I/O scheduler
Versioning: VERSION x.x
Release Frequency: Regularly
SEMI-STOCK:
Toolchain: Linaro GCC 7
Linux 4.4.79 (updated from 4.4.13)
Always SELinux Permissive (with fake SELinux Enforcing status.)
Kernel Security Features, Root Restrictions are DISABLED
Versioning: RELEASE x
Release Frequency: Rare (only stock kernel updates and bug fixes)
NOTE: As of VERSION 0.3 and SEMI-STOCK RELEASE 6, AQG5 or newer bootloader is required.
Download:
STABLE:
VERSION 0.3: (Source Tag)
https://www.androidfilehost.com/?fid=673368273298975229
SEMI-STOCK:
RELEASE 6: (Source Tag)
https://www.androidfilehost.com/?fid=889764386195919462
NOTE:
1. Existing Bluetooth Pairs, Wi-Fi Passwords will be forgot when you flash this kernel for the first time.
2. You need to flash root package (Magisk or SuperSU) AFTER flash kernel if you want root access.
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
Get informed about news and updates:
Join Official Telegram Channel
AND/OR
Follow this project on XDA
XDA:DevDB Information
Jesse's Kernel for Galaxy S8 and S8+, Kernel for the Samsung Galaxy S8+
Contributors
jesec
Source Code: https://github.com/jesec/android_kernel_samsung_universal8895
Kernel Special Features:
Version Information
Status: Stable
Created 2017-05-08
Last Updated 2017-07-30
Changelog:
STABLE:
VERSION 0.3, July 29th:
Merge AQG5 kernel updates from Samsung
Merge Linux 4.4.79
Merge BFQ-v8r12
Backport latest F2FS
Switch to latest Linaro GCC 7 toolchain with processor specific tunes.
Use -Ofast optimization.
VERSION 0.2.2, June 26th:
Merge AQF7 kernel updates from Samsung
Merge Linux 4.4.74
VERSION 0.2.1, May 27th:
Merge AQE5 kernel updates from Samsung
Merge Linux 4.4.69
Update system patches
VERSION 0.2, May 19th:
Updated to Linux 4.4.68
Full F2FS file system support (with latest driver backported from Linux 4.12) is added.
Possible kernel panic (random reboots) addressed.
Possible battery life improvements for CPU frequency boosts.
BFQ is added and set as the default I/O scheduler.
VoLTE & VoWiFi problem fixed. (verified by testers)
NOTE: VoLTE logo may not be an accurate indicator of VoLTE support.
VERSION 0.1, May 11th:
Initial Release.
SEMI-STOCK:
RELEASE 6, July 29th:
Merge AQG5 kernel updates from Samsung
Merge Linux 4.4.79
Backport latest F2FS
Switch to latest Linaro GCC 7 toolchain with processor specific tunes.
Use -Ofast optimization.
RELEASE 5, June 26th:
Merge AQF7 kernel updates from Samsung
Merge Linux 4.4.74
RELEASE 4, May 27th:
Merge AQE5 kernel updates from Samsung
Merge Linux 4.4.69
Update system patches
RELEASE 3, May 19th:
Updated to Linux 4.4.68
Switched to GCC 8.X
Full F2FS file system support (with latest driver backported from Linux 4.12) is added.
Possible kernel panic (random reboots) addressed.
VoLTE & VoWiFi problem fixed. (verified by testers)
NOTE: VoLTE logo may not be an accurate indicator of VoLTE support.
RELEASE 2, May 11th:
Storage and CPU performance problems fixed.
Guides:
HOW-TO FLASH THIS KERNEL:
1. Make sure TWRP is installed. (https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3)
2. Download the flashable zip from download section in OP.
3. Transfer the zip to your phone.
4. Go to "Install" menu of TWRP and flash the zip.
(for devs) HOW-TO PROPERLY INTEGRATE THIS KERNEL TO YOUR ROM:
1. Download the flashable zip from download section in OP.
2. Rename the downloaded zip to "jesse-kernel.zip".
3. Delete original boot.img of your ROM.
4. Place the zip to kernel (create if not exists) folder of your ROM.
Example Structure:
->META-INF
->->com
->->...
->system
->->app
->->priv-app
->->...
->kernel
->->jesse-kernel.zip
->...
5. Delete original kernel flashing lines from installation script (META-INF/com/google/android/updater-script) of your ROM.
tip: usually start with package_extract_file("boot.img" after "ui_print("Extracting boot image...");".
6. Add these lines to the installation script of your ROM:
Code:
ui_print("Installing Jesse's Kernel...");
package_extract_dir("kernel", "/tmp/kernel");
run_program("/sbin/busybox", "unzip", "/tmp/kernel/jesse-kernel.zip", "META-INF/com/google/android/*", "-d", "/tmp/kernel");
set_perm(0, 1000, 0755, "/tmp/kernel/META-INF/com/google/android/update-binary");
run_program("/tmp/kernel/META-INF/com/google/android/update-binary", "3", "1", "/tmp/kernel/jesse-kernel.zip");
ui_print("Jesse's Kernel Installed");
(for devs) Tips about kernel compile: (Note: NO technical support for such things. Inquires will be ignored.)
1. There is a kernel build script in my kernel. (build_kernel.sh)
2. Two variables must be specified before you can run it.
export $KERNEL_TOOLCHAIN=/path/to/your-toolchain/bin/toolchain-prefix-
export $KERNEL_DTBTOOL=/path/to/dtbtool/dtbhtoolExynos
3. If you are building for Galaxy S8 (dreamlte), run it with "bash build_kernel.sh dreamlte".
If you are building for Galaxy S8+ (dream2lte), run it with "bash build_kernel.sh dream2lte".
4. Default output dir is "../kernel_out". "dt.img" and "Image" will be generated.
That's what I'm talking about! Thank you!!
Thanks @jesec for this and twrp. Without u development would be so far behind
sent from the R.I.C.E powered V8+
Great work mate :fingers-crossed:
State-wide provider blackout the very second i flashed. No worries!
Thanks for your hard work. Great job as always.
Sent from my SM-G955F using Tapatalk
what is the difference between stock and semi stock?
GreyFox777 said:
what is the difference between stock and semi stock?
Click to expand...
Click to collapse
Got the same question.. I've installed it, but it doesn't seem to have any advanced governors, etc on board.
But still very nice to have the first kernel on!!!!!
Jesec, you're just great
Btw: does the name Jesse's kernel was chosen on purpose or just a mistake?
GreyFox777 said:
what is the difference between stock and semi stock?
Click to expand...
Click to collapse
This kernel look like a basic kernel update from 4.4.13 to 4.4.66
@jesec
Awesome, thanks a lot bro!
Thank you for the first custom kernel
Can we expect a permissive kernel for this device soon?
tiho5 said:
Thank you for the first custom kernel
Can we expect a permissive kernel for this device soon?
Click to expand...
Click to collapse
Per github commit, the big news here is that this kernel is permissive!
@jessec, you are totaly awesome:good:
Thank you for being here!
Update; appear kernel selinux is still enforcing
It is SELinux permissive. That enforcing is fake actually. (just let userspace think status change is successful)
Changelog: (May. 9th)
I fixed a bug of script. Now new build (May. 9th) should work fine on non-plus variants.
finally i can use ARISE completely. thx a lot
Great one. Many thanks. I will try and report.
Sent from my SM-G955F using Tapatalk
Feels good to see development here, used to love ur work on GS7.
One question, where can I get the Magisk Flashable? I got it when flashed the ROM but I cant flash the ROM over the kernel or I will lose the kernel
jesec said:
It is SELinux permissive. That enforcing is fake actually. (just let userspace think status change is successful)
Changelog: (May. 9th)
I fixed a bug of script. Now new build (May. 9th) should work fine on non-plus variants.
Click to expand...
Click to collapse
Great.
Thanks. That's what I've been waiting for.
metuskale said:
Feels good to see development here, used to love ur work on GS7.
One question, where can I get the Magisk Flashable? I got it when flashed the ROM but I cant flash the ROM over the kernel or I will lose the kernel
Click to expand...
Click to collapse
here it is:
{
"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