{
"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.
Related
{
"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 resurrection of kitkat 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 Cybernetus
You can download from his official website:
http://dorimanx.cybernetus.com/
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.4.X KITKAT ONLY!
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, sleepy, conservative (Default: HYPER)
- IO Schedulers: ROW, Tripndroid, FIOPS, SIO, BFQ, CFQ, Noop, ZEN, Deadline (Default: ZEN)
- 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) - Main toolchain
- Built with Latest UBER 6.1 Toolchain (Smooth, fast and fluid) - Secondary 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 fix is already included in this kernel!
- Updated Linux Kernel version to 3.15.0 stable!
- Freezefix is already included in this kernel!
- Isorec support
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)
Christopher83 (For Linaro custom toolchain)
Lanchon (For TRIM fix and Isorec for Dorimanx)
Zeitferne (For FP Bug/Music Bug fix and freezefix)
Realex-fire (Linux Kernel Updates and other ramdisk fixes)
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?
Click here for Q&A Thread
HOW TO FLASH?
Check the troubleshooting guide
XDA:DevDB Information
DorimanX Unofficial 4.4.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: 10.50v009
Stable Release Date: 2017-01-14
Current Beta Version: 10.50v004
Beta Release Date: 2016-02-06
Created 2015-06-03
Last Updated 2017-01-13
Changelogs:
--UNRELEASED VERSIONS (KERNEL UNDER TEST) --
Code:
No more build from me :)
--RELEASED VERSIONS (GENERAL AVAILABILITY) --
Code:
[B]DorimanX 10.50 v009 (STABLE)[/B]
- Additional security updates from LineageOS kernel source
- Force Deadline to be used as the default scheduler while not in OS
- Updated stweaks descriptions from previous commits
- Re-enabled Software CRCs. DorimanX kernel does experience corruption issues so it is better to keep this enabled.
[B]DorimanX 10.50 v008 (STABLE)[/B]
- Security updates from LineageOS (formerly Cyanogenmod) kernel source
- Change default I/O scheduler to ZEN - CFQ better for hard disks, ZEN is good for flash storage
- Remove UKSM - The kernel needs to be more in-line with the linux kernel
- Remove toggle for Software CRCs and disable by default - Tested safe by other devs so why not?
- Remove power saving workqueues control - Had little to no effect
- Remove Powersave and Performance governors - I don't keep garbage :)
[B]DorimanX 10.50 v007 (STABLE)[/B]
- Fixed TRIM on /data partition - Looks like I forgot to remove discard option, hence TRIM wasn't working properly in all previous builds. My bad :(
- Stweaks profiles will be reset
- Synced many updates from MM kernel
- zzmoove will now use alucard hotplug as the default hotplug
- UKSM support with tuning support in stweaks
- Software CRCs re-enabled and toggle added to stweaks
- General stability fixes and performance improvements
- Cleanup to initramfs
- UBER 6.1 support
- Updated UBER and Linaro toolchain
[B]DorimanX 10.50 v006 (STABLE)[/B]
[COLOR="Red"]I found that I have missed some changes in the previous build, so this build aims include them[/COLOR]
- Synced most updates from LP kernel
- UBER 6.0 support. UBER 5.3 builds discontinued.
- Reverted VM tweaks
- Updated Stweaks descriptions, synced reorganized hotplug tab
- General performance improvements and fixes
- CFQ is the default I/O scheduler for all profiles
- Added missing optimizations from LP kernel
- LMK profiles now properly enforced
- zzmoove will now use intelliplug as the default hotplug method
[B]DorimanX 10.50 v005 (STABLE)[/B]
- This is just a little treat to all the people who still use my KK kernel :) I'm releasing this because I'm not truely satistfied with the experience on KK.
- Added MDNIE changing support
- Removed VFS cache tuning
- Updated HYPER, SIO updated to SIOPlus, plus many more changes from LP kernel.
- General performance improvements and fixes
- Synced most updates from LP kernel
[B]DorimanX 10.50 v004 (BETA)[/B]
[COLOR="Red"]- This is a kernel end of life build mainly built to fix some kernel issues that still exist after the last official kernel release. No additional features will be added to these releases.[/COLOR]
- Freezefix has been implemented from LP branch. Evidence shows that earlier versions of android are also affected by the 150mhz bug. This will solve some rare random freezing and will provide additional stability. I didn't add this in earlier builds because I thought there was no need to for an already stable kernel :)
[B]DorimanX 10.50 v003 (BETA)[/B]
[COLOR="Red"]- This is a kernel end of life build mainly built to fix some kernel issues that still exist after the last official kernel release. No additional features will be added to these releases.
[/COLOR]- Low latency audio fix will be applied on boot. DorimanX doesn't support low latency audio which causes games using recent unity versions to sound horrible. Thanks to @dualjoe. If you want to re-enable low latency audio, reflash rom and use different kernel!
- NON-TRIM builds and UBER 4.9 builds will not be released!
[B]DorimanX 10.50 v002 (BETA) - LAST NON-TRIM AND UBER 4.9 BUILD[/B]
- sched: Set MC (multi-core) sched domain's busy_factor attribute to 1. This will increase CPU performance.
- fixed compilations warnings thanks to @chhapil
- Changed swappiness drop down to slider. Allow users to select a more precise percentage.
- Limit boot booster frequency to a max of 1.4Ghz. Anything higher will cause many devices not to boot :) Plus there are very few CPUs out there that can run higher than this config.
- Added lowmem_reserved_ratio tuning to stweaks thanks to @dorimanX. A higher ratio will give you more free RAM if you see that your free RAM is always loaded and device LAG, but it's also uses more battery to gain more free RAM with loaded system. Please don't use the relaxed setting as you will run out of RAM very easily.
- Isorec recovery support. Many thanks to lanchon who has been working with me for the past few days. If you require to dualboot, don't use isorec recovery. I have linked the isorec disabler for people who want dualboot/dorimanx recovery. Also, TWRP can't mount USB storage so you won't be able to transfer files between PC, go back to CWM to fix this. We have isorec on DorimanX :) However this is still a WIP.
- zzmoove will now use alucard as the default hotplugging driver.
- Add toggle for power efficient workqueues. Enable to save power, disable for performance. Fixed parameter permissions. If you disable this, Cortexbrain will automatically switch on this during sleep state to save battery. Avoid using Kernel Adiutor to set this value as stweaks can do this properly.
- Set profiles with "medium" OOM values to "default"
- Synced some VM and memory tweaks from LP branch
- Minor fixes to some stweaks descriptions
[B]DorimanX 10.50 v001 (BETA)[/B]
- GCC 5.x support. Starting from this build, we will see UBER 5.3 experimental builds for those who want the best performance they can get. Thanks @chhapil
- Toolchain GCC Version is also included now in zip file name so we don't get confused
- Synced missing futex updates from Linux 3.15 stable
- UBER toolchain updated to 2016-01-11 build
- This build will be built with Linaro and UBER (From now on, I will be naming builds with the selected toolchain)
- tick: Fix a bug which impacts CPU frequency scaling
[B]DorimanX 10.45 v040 (BETA)[/B]
- 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! ;)
[B]DorimanX 10.45 v039 (STABLE)[/B]
- Various updates to net, ipv6 and futex
- Change the VM_MAX_READAHEAD value to 512KB for best throughput
[B]DorimanX 10.45 v038 (STABLE)[/B]
- Updates to net, ipv4 and TCP Cubic
- Linaro 4.9 toolchain from Christopher83 is being used on all future builds starting from this build
- Last build using UBER toolchain
[B]DorimanX 10.45 v037 (STABLE) - Linaro[/B]
- This build is built with latest Linaro 4.9 from Christopher83
- Comes with all changes from original v037 release
[B]DorimanX 10.45 v037 (STABLE)[/B]
- Updated UBER toolchain to 20151031 build
[B]DorimanX 10.45 v036 - 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 v036 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 10.45 v036 (STABLE)[/B]
- Reverted I/O scheduler updates
- Tuned I/O scheduler fifo batch and other tweaks
[B]DorimanX 10.45 v035 (STABLE)[/B]
- Updated UBER toolchain to 20151025 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 :) )
[B]DorimanX 10.45 v034 (STABLE)[/B]
- Removed interactive and lionheart CPU governor (Should fix all, if not most, SOD issues)
- Fixed zzmoove fast scaling variable number range (should be from 0 to 5, not 0 to 8)
[B]DorimanX 10.45 v033 (BETA) - Changed to BETA because of issues with SODs[/B]
- Added lionheart CPU governor from chhapil's source
[B]DorimanX 10.45 v032 (BETA) - Changed to BETA because of issues with SODs[/B]
- 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 10.45 v031 (BETA) - Changed to BETA because of issues with SODs[/B]
- Added back interactive CPU governor from slimsaber source
[B]DorimanX 10.45 v030 (STABLE)[/B]
- Reverted updates to zzmoove tunables (fixes broken zzmoove tuning of some variables in stweaks)
[B]DorimanX 10.45 v029 (STABLE)[/B]
- Changed toolchain back to UBER 4.9 and updated to latest version
[B]DorimanX 10.45 v028 (STABLE)[/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
[B]DorimanX 10.45 v027 (STABLE)[/B]
- We're moving back to UBER 4.8 toolchain (should be more battery friendly than linaro)
[B]DorimanX 10.45 v026 (STABLE)[/B]
- Updated zzmoove to 1.0 beta 8
[B]DorimanX 10.45 v025 (STABLE)[/B]
- Restore Linaro 4.9 toolchain
[B]DorimanX 10.45 v024 (STABLE)[/B]
- Reverted WiFi driver
- Reverted Linaro toolchain to 4.8 for the time being
[B]DorimanX 10.45 v023 (BETA)[/B]
- More work on Wifi-driver to get Ad-hoc networks working (Still not working yet)
- Many minor changes to stweaks descriptions and updates to default profile again
- Updated kernel update check function (Doesn't work yet, I think it's because there is 2 'v' in the kernel version and build version, in other words it is a WIP!)
- We're moving back to Linaro 4.9 (Less bugs, more performance!)
[B]DorimanX 10.45 v022 (BETA)[/B]
- Updated to latest UBER toolchain
- Switched to UBER 4.9 toolchain instead of 4.8
- Revert: "allowed IO Read Ahead up to 4096KB"
- Allow mod of vfs cache pressure - This is used by cortex background service, don't modify if you don't know what you are doing
[B]DorimanX 10.45 v021 (BETA)[/B]
- Wifi drivers updated to 1.141.44 thanks to @stelistcristi
- Now this kernel surpasses stelistcristi's builds
[B]DorimanX 10.45 V020 (STABLE)[/B] - Tweak your GPU beyond belief :)
- More overclocking and underclocking of GPU! (All steps can have higher or lower frequencies and voltages)
- Revert boot boost limits
- Fixed file permissions
[B]DorimanX 10.45 V019 (STABLE)[/B]
- Added back powersave governor
- Rearranged root actions in ROOT tab to prevent accidental installation/deletion of root
- zzmoove tunables fixed
[B]DorimanX 10.45 V018 (BETA)[/B]
- Revert AES updates (this fixes the installation issues)
[B]DorimanX 10.45 V017 (BUGGED) - REMOVED[/B]
[COLOR="Red"]- Please note that there are some installation issues with this build for some users. The kernel itself is fine, I will have to investigate what is the root cause. [/COLOR]
- zzmoove profile support
- moved zzmoove tunables into awake section (why was it in sleep???)
[B]DorimanX 10.45 V016 (BUGGED) - REMOVED[/B]
- arm/aes update NEON AES module to latest OpenSSL version
- Added zzmoove 1.0beta7a to replace zzmanX! No profile switching for now.
[B]DorimanX 10.45 V015 (STABLE)[/B]
- Separated CRON tasks into own tab in stweaks
- Separated partitions fixes into own tab in stweaks
- Separated root actions into own tab in stweaks
[B]DorimanX 10.45 V014 (BETA)[/B]
- Updated profiles once again (this should help with battery drainage)
- Fixes to wifi module (thanks to ruleh)
- Re-add performance governor to stweaks
- Allow users to debug stweaks again
- Fixes to custom profile reset (in recovery)
[B]DorimanX 10.45 V013 (STABLE)[/B]
- Reverted busybox version (This should fix all of the app incompatibilities and errors)
- Updated BFQ to v7r8 (Bug fixes, speed improvements, etc.)
[B]DorimanX 10.45 V012 (BUGGED)[/B]
- Added 3 user profiles to stweaks
- Added descriptions to all profiles
- Apps that require busybox may not work properly in this build
[B]DorimanX 10.45 V011 (BUGGED)[/B]
- I/O Schedulers updated
- Busybox updated to 1.23.2
- Apps that require busybox may not work properly in this build
[B]DorimanX 10.45 V010 (STABLE)[/B]
- Updated FPU Bug fix thanks to [user=4913978]@oberon0[/user]0
- Stweaks TCP algorithm cleanup and allowed IO Read Ahead up to 4096KB (Better than the weird option of 2548KB)
[B]DorimanX 10.45 V009 -TRIM (STABLE)[/B]
- Trim now fixed thanks to [user=4354573]@chhapil[/user]
[B]DorimanX 10.45 V008[/B]
- [COLOR="Red"]TRIM is apparently broken in my builds. I will have to fix this in the next build. Thanks chhapil for telling me![/COLOR]
- TCP Algorithm settings fixed now
- Westwood now set as the default algorithm
[B]DorimanX 10.45 V007[/B]
- Added options in stweaks to choose tcp algorithm (NOTE: The next time stweaks opens, it will ask to discard or apply settings, select DISCARD. In other words, Cubic is set in app everytime the app is reopened)
- TRIM is broken on this release
[COLOR="Red"][B]DorimanX 10.45 V006[/B]
- TRIM is broken on this release
- TRIM is still enabled and will be for all future builds - Use this at your own RISK![/COLOR]
- TCP algorithms finally fixed!!!! You can change TCP algorithms with apps like trickstermod
[COLOR="Red"][B]DorimanX 10.45 V005[/B]
- TRIM Enabled - Use this at your own RISK![/COLOR]
- TRIM is broken on this release
- Reuploaded with extra safety measures for trim
[B]DorimanX 10.45 V004 (STABLE)[/B]
- Built with Latest UBER toolchain 4.8
- VR and FIFO I/O schedulers removed (As per DorimanX G2 changes)
- All built in profiles have been tuned! Make sure to reset stweaks settings if you can.
- Max boot frequency limited down to 1.2Ghz
- Multiple changes to stweaks (Update tab, etc)
[B]DorimanX 10.45 V003[/B]
- Tripndroid and FIOPS can be set now
- Default profile has been tweaked for better stability and performance
[B]DorimanX 10.45 v001[/B]
- Added Tripndroid scheduler. Fiops scheduler was also readded. Can't be set in stweaks yet.
- SuperSU 2.46
- Forgot what else I added XP
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.
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.
Isorec (Isolated Recovery)
Starting from build v002, I have introduced isorec into dorimanX kernel. CWM works perfectly, whereas TWRP can't mount USB storage. More work will need to be done to get TWRP fully working.
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
Which build should I use?
Linaro 4.9: Use this build for best stability. Battery life is not as good as UBER 4.9. This build should only be used as a fallback if all other builds fail to meet expectations or when the other builds give problems.
UBER 6.1: Use this build for best performance. Performance difference is small and battery life is slightly worse than Linaro 4.9. This build should only be used by advanced or more experienced users (beta testers).
Main download link:
https://www.androidfilehost.com/?w=files&flid=43488
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)
For general help, please use the Q&A thread
Take me to the Q&A Thread
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!
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: 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: 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: 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 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 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
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
thanks
will give a try as usual
Green light, all is go. There are issues where new scheduler or algorithm can't be set yet, but no major issues
gsstudio, dorimanx kernel was my kernel for kk for a very long time until LP appear. But for now I just can't go back again for KK...it's way behind LP in performance and speed. I left a private message for you, if you have time answer me. Thanks gsstudio. Cheers.:good:
gsstudios said:
Green light, all is go. There are issues where new scheduler or algorithm can't be set yet, but no major issues
Click to expand...
Click to collapse
Nice work! Keep it up!
Very hopeful here bro, reallly really looking forward to a dori like lp kernel its realllly really needed, get good soon
Tripndroid and FIOPS should be fixed now. Was missing a few strings to add
Will fix problem with tcp algorithm later.
What do you guys think about the default io scheduler? Should I change it to zen (like in dorimanx g2), tripndroid or something else? I've been testing tripndroid for a while now, very smooth and fast.
If you wanted to know the specific changes to the default profile, I changed threshold values so they are slightly higher (screen on up threshold 60-->70 and screen off up threshold 60 --> 75). LMK for screen on changed to medium, io schedulers changed to SIO. I might remove zzmanx and put zzmoove so that it is up to date. Possible add an option to change profiles if possible.
I have successfully built dorimanX with Uber toolchain. Lots of new improvements and adjustments made to the kernel. Look at post 3 for changelogs: Link
Keep up the good work
I love your work gsstudios! I pm you. Are you needing any help? Has the pool is clear, Lollipop support is the way now. Of course there's people that likes KK, but imho kk has many probs in RAM management. Are you going to work full in KK and then convert it to lollipop? It's that the way?
Have some questions:
1. Does this have the Fuse Bug Fix? Well... since no one updates latest Dori and such...
2. Is the "Speedup Key Resume" feature on Apolo added here as well? This makes S2W more responsive, so I like it...
3. Is Swap feature enabled? I'm trying to Swap from /preload but Apolo and Gustavo doesn't have one. Forgot wether Dori has it...
4. Will you add the screen-color-changing feature from Gustavo to here as well?Or is it already in here?
Thanks for the continuing the development, man... :good:
:good:
I simply just wanted to post a "thanks you", instead of just hitting the thanks button, which I 've done many times, for keeping alive and updating the best (for me) kernel ever developed for S2.
V005 works great with trim enabled.:thumbup:
And UBER makes it even smoother lets see how the battery will go...
Sent from my GT-I9100 using XDA Free mobile app
souler456 said:
Have some questions:
1. Does this have the Fuse Bug Fix? Well... since no one updates latest Dori and such...
2. Is the "Speedup Key Resume" feature on Apolo added here as well? This makes S2W more responsive, so I like it...
3. Is Swap feature enabled? I'm trying to Swap from /preload but Apolo and Gustavo doesn't have one. Forgot wether Dori has it...
4. Will you add the screen-color-changing feature from Gustavo to here as well?Or is it already in here?
Thanks for the continuing the development, man... :good:
:good:
Click to expand...
Click to collapse
Fusebug and screen color changing is big thing I want them too. But I did not notice anything about speedup key resume on apolo. It's just like old builds
Latest DorimanX v10.44 v008 has fusebug fix.
TCP algorithms finally fixed. Can be changed in apps like trickstermod.
Edit: You can now select TCP algorithm in others tab.
{
"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)
Development has ended.
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 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, 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 Latest Linaro 4.9/UBER 6.1 Toolchains
- 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
- Low Latency Audio bugfix is included in this kernel
- MDNIE mode and scenario tuning
- F2FS support
THINGS TO DO:
- Provide an actual fix for device off battery charging animation
- Allow users to dirty flash ROM to restore original kernel
- Fix cache partition wipe on Resurrection Remix ROM
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)
- 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)
Christopher83 (For Linaro custom toolchain)
Lanchon (For TRIM fix and Isorec for Dorimanx)
Zeitferne (For FP Bug/Music Bug fix and freezefix)
Lysergic Acid (For CM12.1, source and fixes)
Realex-fire (Marshmallow support and kernel fixes)
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 can not dirty flash ROM to restore original kernel
- Resurrection Remix users can not wipe cache partition as it will cause bootloops
- MM support limited to CM13 based roms
- LP support limited to CM12.1 based roms (Doesn't work with Slimsaber, SlimLP, Omni, Paranoid Android yet)
- If you reboot your phone, you may experience a large battery percentage drop.
- All dorimanx bugs
WHAT ROMS WORK WITH THE KERNEL:
So far, the kernel works with:
- Cyanogenmod 13
- Cyanogenmod 12.1
USEFUL LINKS
CPU Governor and I/O Scheduler Guide
DorimanX tuning guide
TCP Algorithm guide
HAVING PROBLEMS?
Read post 4 before posting questions!
GOT QUESTIONS?
Click here for Q&A Thread
HOW TO FLASH?
Check the troubleshooting guide
XDA:DevDB Information
DorimanX kernel for LP and MM by Saber, 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: 12.0b013
Stable Release Date: 2017-01-14
Current Beta Version: 12.0b011
Beta Release Date: 2016-08-07
Created 2015-06-29
Last Updated 2017-01-13
Changelogs:
--UNRELEASED VERSIONS (KERNEL UNDER TEST) --
For live changelogs, see my github: Github Link
Code:
[FONT="Arial"][COLOR="Red"]Development has been stopped. No more builds.[/COLOR]
[/FONT]
--RELEASED VERSIONS (GENERAL AVAILABILITY) --
Code:
[FONT="Arial"][B]DorimanX 12.0 b013 (STABLE)[/B]
- Additional security updates from LineageOS kernel source
- Updated stweaks descriptions from previous commits
- Re-enabled Software CRCs. DorimanX kernel does experience corruption issues so it is better to keep this enabled.
[B]DorimanX 12.0 b012 (STABLE)[/B]
- Security updates from LineageOS (formerly Cyanogenmod) kernel source
- Change default I/O scheduler to ZEN - CFQ better for hard disks, ZEN is good for flash storage
- Set swappiness to 60 - Should help with low memory problems
- Remove UKSM - The kernel needs to be more in-line with the linux kernel
- Remove Adaptive LMK - Drains more battery without making much of a difference to memory savings
- Remove toggle for Software CRCs and disable by default - Tested safe by other devs so why not?
- Remove power saving workqueues control - Had little to no effect
- Remove Powersave and Performance governors - I don't keep garbage :)
[B]DorimanX 12.0 b011 (BETA)[/B]
- Synced MM and LMK updates from Dorimanx's LG G2 kernel
- Adaptive LMK and tuning support in stweaks
[B]DorimanX 12.0 b010 (BETA)[/B]
- Reverted nr_requests to 64 to reduce RAM usage on I/O load
- Fixed md5 generation on nandroid backups
- Bring back relaxed LMK profiles to allow better selection between aggressive and non-aggressive RAM management
- UBER toolchain updated
[B]DorimanX 12.0 b009 (BETA)[/B]
- Fifo batch tuned for sioplus and tripndroid
- nr_requests increased to 128 for better throughput - The downside is that we have less RAM to work with when I/O requests are full
- Hack to get power off charging animation working - Thanks Realex-fire. This is only a temporary solution.
- More cleanup to initramfs
- UBER toolchain updated
[B]DorimanX 12.0 b008 (BETA)[/B]
- Merged net updates
- UKSM support and initial UKSM tuning support in stweaks - UKSM can help free more RAM but at the cost of extra battery drainage. UKSM is off by default.
- General performance improvements and stability fixes
- Profiles will be reset after flashing this build
[B]DorimanX 12.0 b007 (BETA)[/B]
- Added back IPV6 toggle
- Synced sched, LZ4 and LZO updates from Linux 3.16
- Merged a wifi security fix
- Reverted back to aggressive LMK profiles - Phone felts smoother with more aggressive LMK
[B]DorimanX 12.0 b006 (BETA)[/B]
- Fixed mounting of F2FS partitions
- Many bug fixes and small cleanup to initramfs
- Partitions check and fix function for F2FS is now working properly
- Reverted LMK profiles back to CM defaults. Optimized profile is now the old default profile - This should bring better battery life
- Linaro and UBER toolchain updated
[B]DorimanX 12.0 b005 (BETA)[/B]
- Fixed partition error boot popup when /data or /cache was formatted as F2FS
- Fixed wifi hotspot - Thanks to Realex-fire
- Change default I/O scheduler to CFQ
[B]DorimanX 12.0 b004 (BETA)[/B]
- Fixed mass storage mount on LP
- Full support for F2FS partitions - error log still may show on boot, but can be safely ignored
- Updated exfat modules from Dorimanx's source
- Added and enabled temperature export for zzmoove
- Changed the default hotplug method for zzmoove to Alucard. Force native zzmoove hotplug disabled - Intelliplug doesn't hotplug for zzmoove, only Alucard works.
[B]DorimanX 12.0 b003 (BETA)[/B]
- More ZRAM tweaks have been added for better ZRAM performance - max_comp_streams=2 and force LZ4 algorithm
- Disabled panic and reboot on oops bugs. According to Dorimanx, the kernel will recover 99% of the time when kernel encounters a problem.
If not, kernel will hang making it possible to diagnose random reboots
- Merged many f2fs fixes and improvements from mainline linux kernel - F2FS is functional, but there are some problems we need to fix
- Minor selinux fixes
- Removed broken features from stweaks - Root options and kernel update check
- Fixed mass storage USB mount mode
- General performance improvements and stability fixes
[B]DorimanX 12.0 b002 (BETA)[/B]
[B]Starting from this build, kernel will support CM12.1 and CM13 at the same time![/B]
- CM13 Support - Many thanks again to realex-fire for his hard work
- Selinux is now enabled and set to permissive by default
- Wifi driver updated to version 1.141.44
- VPN fixed
- General performance improvements and stability fixes
- UBER toolchain updated
[B]DorimanX 12.0 b001 (BETA)[/B]
[COLOR="Red"]CM13 is not supported yet, only CM12.1 support for now![/COLOR]
[B]Most of the changes were done by realex-fire. Big thanks for his contribution[/B]
- Many changes from CM have been merged
- Major rework of init and ramdisk - Bugs fixes, a lot of unused code deleted. Kernel size reduced!
- Mali driver updated (CM12.1 will still work)
- General fixes and performance improvements
- UBER toolchain updated
[B]DorimanX 11.0 b042 (BETA)[/B]
- Merged several broadcom wifi security fixes
[B]DorimanX 11.0 b041 (BETA)[/B]
- Switched to self-built Cortex-A9 optimized Linaro 4.9 toolchain from Cl3Kener's sources - Includes latest fixes and changes from Linaro. Linaro 4.9 is the sweet spot for our device :)
- Add TRIM function to stweaks and other TRIM related fixes from @chhapil's initramfs
- VM parameters have been tuned again - Now it matches Dori G2 LP values for better balance between performance and stability
- Increased swappiness to 40% - This should help prevent RAM drain under heavy load
- Updated UBER toolchain with latest changes
- Full tuneup to LMK profiles synced with Dori's G2 kernel. New optimized profile. Low profile removed - RAM management is now very aggressive and will not allow kernel to have less than 200MB of RAM
- Fixed incorrect file permissions for lowmemorykiller minfree and adj files
- Entropy tuned for better performance. Kernel will now tune entropy on boot.
- General stability fixes
- Your profiles will be reset after flashing this build!
[B]DorimanX 11.0 b040 (BETA)[/B]
- Re-enabled mmc software CRCs - We should value data integrity over performance
- Allow users to enable or disable mmc software CRCs via sysfs. Added software CRCs toggle in stweaks - If you do feel that having it disabled is better, I will let you do so.
- Fixed workqueue control not running in cortexbrain service
- Re-enabled CONFIG_ANDROID_LOW_MEMORY_KILLER_AUTODETECT_OOM_ADJ_VALUES
- Updated UBER toolchain with latest changes
[B]DorimanX 11.0 b039 (BETA)[/B]
- Fixes to zzmoove profiles
- Merged a few of missing and recent updates from CM13
- Changed config_hz to 300 (from 250) - This should give a small boost in interactivity with no cost in battery life
- sched.h: Changed LOAD_FREQ calculation
- UBER builds are now being built with latest UBER 6.1 with Cortex-A9 optimizations - I forgot to change the UBER version string from 6.0.0 to 6.1.0, but you can just look at GCC version for proof :)
[B]DorimanX 11.0 b038 (BETA)[/B]
- OOM and LMK fixes thanks to realex-fire
- HYPER cpu gov synced with latest changes from Dorimanx's G2 kernel
- Changed the default I/O scheduler to BFQ - After some testing, I have found BFQ to be slightly more responsive compared to CFQ
[B]DorimanX 11.0 b037 (BETA)[/B]
- Reverted o3 flags - This fixes the high power consumption from the last build and large kernel size
- We will no longer see UBER 5.3 builds.
- Reverted more VM tweaks
- General stability fixes
[B]DorimanX 11.0 b036 (BETA)[/B]
- Default I/O scheduler changed back to CFQ
- Compiler optimisations thanks to @chhapil - Dori kernel was missing a lot of optimisation flags after kernel was updated past 3.12 linux kernel. Now we finally get them back :)
- The kernel is now compiled with the -o3 optimization flag - Increased kernel size, better performance
[B]DorimanX 11.0 b035 (STABLE)[/B]
- Various security updates and stability fixes pulled from CM13 kernel
- LMK will now kill system and protected (root) apps and services to prevent kernel crash - This fixes Launcher FC bug and poor RAM performance
- Stweaks updated with material design thanks to @Skyline!
[B]DorimanX 11.0 b034 (BETA)[/B]
- Added support for GCC 6.0 toolchains. We will see how UBER 6.0 experimental builds go
- Default I/O scheduler changed to ZEN
- lowmemreserve ratio changed back to default values
[B]DorimanX 11.0 b033 (BETA)[/B]
[COLOR="Red"]Your stweaks profile will be reset automatically once you flash this build[/COLOR]
- Restored aggressive LMK changes (After reverting the LMK changes, phone felt noticeably more laggy and system would lock up more frequently)
- Reduced swappiness back to 20% to reduce CPU usage and to improve performance
- Reverted VM changes (VFS cache pressure, dirty background ratio) - This might restore stability and performance
- Merged a few updates from CM - Minor stability fixes and security fixes
- Updated UBER toolchain
[B]DorimanX 11.0 b032 (BETA)[/B]
[COLOR="Red"]It is recommended to reset your stweaks profiles to ensure you get the best stability [/COLOR]
- Fixed lots of stweaks descriptions. Matched all non-matching default value descriptions
- Removed relaxed lowmem_reserve_ratio option. Our device doesn't have more than 600MB of free RAM :)
- Merged many changes from CM13 kernel
- Reverted LMK profile and made it less aggressive. We'll see if this helps with Launcher FCs. Note: It is not recommended to decrease swappiness!
- Increased swappiness to 50. We need LMK to do less work otherwise apps will just suddenly close. - Slightly less battery life, better multitasking
- UBER 5.3 Toolchain updated to March build
- zzmoove will now use intelliplug as the default hotplug method
[B]DorimanX 11.0 b031 (BETA)[/B]
- Added MDNIE override toggle. If your settings don't apply, just re-enable this toggle and make changes again.
- hyper gov updated with DorimanX LG G2 LP thanks to realex-fire - Better balance between performance and battery life.
[B]DorimanX 11.0 b030 (BETA)[/B]
- Updated sio to sioplus iosched - Thanks to DorimanX. Now it is working as it should and stweaks doesn't freeze anymore! :) - Better performance and multitasking
- Merged many changes to zzmoove. Thanks to @zanezam - Bug fixes, performance/battery life improvements
- A few other minor kernel changes were merged from linux mainline kernel - Bug fixes, stability improvements
- MDNIE mode and scenario changing support added to stweaks. Note: This will override the ROMs values. Also, other scripts will be able to override this as well.
[B]DorimanX 11.0 b029 (BETA)[/B]
- Match stweaks descriptions with actual default values
- Merged updates to CFQ io scheduler - Better performance
- Disabled MMC CRC check - Better I/O performance
- Deleted all zipalign functions! it's no longer supported with ART in LP. - Fixed possible nasty bug that would have deleted all app symlinks in /data/app. Before zipalign was enabled by default for performance profiles! Now all good :)
- Stweaks profile will be reset!
- Remove all fix permissions functions. It is old and broken. Lollipop is much more advanced compared to jellybean 4.3 so there is much less chance of apps breaking after a ROM update.
- CORTEX: move OOM fix to cortex to set on each wakeup. Thanks to DorimanX. Before this, the default ROM OOM values were being used after boot, the kernel was not always overriding ROM values and causing slower performance. This fixes this issue.
[B]DorimanX 11.0 b028 (STABLE)[/B]
- Merged a few kernel updates from CM13
- Removed ability to tune vfs_cache_pressure. This is required for cortexbrain to function properly. If you tune it, the kernel script will not run!
- Adaptive vfs_cache_pressure values synced with DorimanX LG G2 LP values. - Better performance, more free RAM, slightly less battery life
[B]DorimanX 11.0 b027 (STABLE)[/B]
- Updated OOM profiles to better match CM Marshmallow and DorimanX LG G2 LP values
- UBER 5.3 Toolchain updated to 01/02/16 build
- Added HOTPLUG tab to stweaks. All hotplug config is now grouped together, minor fixes to spelling
[B]DorimanX 11.0 b026 (BETA)[/B]
- Merged many workqueue updates from linux mainline kernel - Improvements to stability, performance and battery life
- Merged updates to tcp_yeah
- Disabled auditd service to remove selinux related logspam
- Low latency audio fix will be applied on boot. DorimanX doesn't support low latency audio which causes games using recent unity versions to sound horrible. Thanks to @dualjoe. If you want to re-enable low latency audio, reflash rom and use different kernel!
[B]DorimanX 11.0 b025 (BETA) - LAST BUILD FOR NON-TRIM AND UBER 4.9[/B]
- Synced chhapil's zram updates
- LZ4 is set as the default algorithm for zram. I have properly checked now and it is all good. You can see this under /sys/block/zram0/comp_algorithm, where the algorithm inside the brackets is the active one.
[COLOR="Red"]- This will be the last build for NON-TRIM and UBER 4.9. TRIM should be used by everyone and UBER 4.9 is just unnecessary extra toolchain.
[/COLOR]- Changed default I/O scheduler to CFQ. This was Samsung's default choice and it was a good choice. LP needs as much I/O performance we can get, so simpler schedulers are not that great :)
- Merged many zram updates up to what the kernel can allow. This is the max zram can update to before causing build errors.
- UBER 5.3 builds will be moved to the UBER main folder. Not experimental anymore :)
[B]DorimanX 11.0 b024 (BETA)[/B]
- BLN is properly fixed now without having to modify install script thanks to realex-fire
- Fixed stweaks not installing on kernel install thanks to realex-fire
- Many other changes to kernel init system thanks to realex-fire
- LZ4 support on the ZRAM thanks to @chhapil. Changed default compression to LZ4. Before we were using LZO which was slower but gave slightly better compression. LZ4 is much faster but gives slightly worse compression. TL;DR, better performance :) Edit: Wasn't sure if it was really enabled by default because there was no way to check.
[B]DorimanX 11.0 b023 (BETA)[/B]
- BLN is now working!!! I simply updated the updater-script to delete old lights.exynos4.so from ROM and add new one to /system/lib/hw. Thanks @charlie8104 and @arnab If BLN doesn't work, reflash the kernel and make sure to reapply BLN after boot. This should fix BLN for most people :)
- sched: Set MC (multi-core) sched domain's busy_factor attribute to 1. This will increase CPU performance.
- fixed compilations warnings thanks to @chhapil
[B]DorimanX 11.0 b022 (BETA)[/B]
- Changed swappiness drop down to slider. Allow users to select a more precise percentage.
- Limit boot booster frequency to a max of 1.4Ghz. Anything higher will cause many devices not to boot :) Plus there are very few CPUs out there that can run higher than this config.
- Added lowmem_reserved_ratio tuning to stweaks thanks to @dorimanX. A higher ratio will give you more free RAM if you see that your free RAM is always loaded and device LAG, but it's also uses more battery to gain more free RAM with loaded system. Please don't use the relaxed setting as you will run out of RAM very easily.
- Isorec recovery support. Many thanks to lanchon who has been working with me for the past few days. If you require to dualboot, don't use isorec recovery. I have linked the isorec disabler for people who want dualboot/dorimanx recovery. Also, TWRP can't mount USB storage so you won't be able to transfer files between PC, go back to CWM to fix this. We have isorec on DorimanX :) However this is still a WIP.
[B]DorimanX 11.0 b021 (BETA)[/B]
- Synced missing cortexbrain changes and typo fixes from KK initramfs
- zzmoove will now use alucard as the default hotplugging driver.
- Add toggle for power efficient workqueues. Enable to save power, disable for performance. Fixed parameter permissions. If you disable this, Cortexbrain will automatically switch on this during sleep state to save battery. Avoid using Kernel Adiutor to set this value as stweaks can do this properly.
[B]DorimanX 11.0 b020 (STABLE)[/B]
- Full update to 2016 January CM12.1 Ramdisk - Stability improved, smoother operation and better experience. Thanks realex-fire!
- Bugs fixes and dorimanx features fixed from previous ramdisk updates
[B]DorimanX 11.0 b019 (BETA)[/B]
- GCC 5.x support. Starting from this build, we will see UBER 5.3 experimental builds for those who want the best performance they can get. Thanks @chhapil
- Toolchain GCC Version is also included now in zip file name so we don't get confused
- Ramdisk updated once again to CM12.1 October 15th build
- Remove root installer and remover from stweaks to prevent people from breaking root
[B]DorimanX 11.0 b018 (STABLE)[/B]
- Many changes to the LMK/OOM management. Synced values with DorimanX LG G2 and CM12.1. Now much more aggressive than before. Prior to this was the reason why we had such bad RAM management.
- All profiles are now set to default OOM settings. Default is now the same as the settings found in stock CM12.1.
[B]DorimanX 11.0 b017 (BETA)[/B]
- Fixed all issues found in previous build
- Bring back SIO scheduler, deleted SIOPlus (Doesn't work on DorimanX)
[B]DorimanX 11.0 b016 (BETA) - BUGGED AND REMOVED[/B]
- Synced missing futex updates from Linux 3.15 stable
- Reduced swappiness from 40 to 20 (ZRam will only be used under heavy load, rather than in medium loads)
- UBER toolchain updated to 2016-01-11 build
- This build will be built with Linaro and UBER (From now on, I will be naming builds with the selected toolchain)
- Updated SIO to SIOPlus
- tick: Fix a bug which impacts CPU frequency scaling
[B]DorimanX 11.0 b015 (BETA)[/B]
- Reduced swappiness from 60 to 40 (Will only swap when under heavier loads, before it was too aggressive)
- Includes latest LP freeze fix patch from Zeitferne (Note: This is not the final fix, this is an attempt to solve current freeze issues. If you want to help debug, use the proper kernel given by Zeitferne!)
- This build will be built with Linaro and UBER
[B]DorimanX 11.0 b014 (BETA)[/B]
- Enabled zram and set zram to 300MB by default
- Synced all net, TCP Cubic, ipv4, ipv6 and mutex updates from KK branch
- Change the VM_MAX_READAHEAD value to 512KB for best throughput
- 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! ;)
[B]DorimanX 11.0 b013 (BETA) - Linaro[/B]
- This build is built with latest Linaro 4.9 from Christopher83
- Comes with all changes from original b013 release
[B]DorimanX 11.0 b013 (BETA)[/B]
- Synced missing changes from KK branch thanks to @Realex-fire
- Reverted initramfs changes from CM12.1 (Not required to get CM12.1 running smooth, I think this introduced issues)
- Updated UBER toolchain to 20151031 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
- Changed OOM behavior so it is more aggressive, this would be a big advantage for people with lots of apps running!
- Last release built with UBER toolchain
[B]DorimanX 11.0 b012 (BETA)[/B]
[B]This is a long awaited update that should make cyanogenmod experience better again!!![/B]
- Changed toolchain back to UBER 4.9 and updated to latest version
- Updated Cyanogenmod ramdisk to October 15th
- 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 11.0 b011 (BETA)[/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
[B]DorimanX 11.0 b010 (BETA)[/B]
- We're moving back to UBER 4.8 toolchain (should be more battery friendly than linaro)
[B]DorimanX 11.0 b009 (BETA)[/B]
- zzmoove updated to 1.0 beta 8
[B]DorimanX 11.0 b008 (BETA)[/B]
- Restore Linaro 4.9 toolchain
[B]DorimanX 11.0 b007 (BETA)[/B]
- Reverted WiFi driver
- Reverted Linaro toolchain to 4.8 for the time being
- Deleted sharpness tweak again (I forgot to delete the tweak in the previous build)
[B]DorimanX 11.0 b006 (BETA)[/B]
- More work on Wifi-driver to get Ad-hoc networks working (Still not working yet)
- Many minor changes to stweaks descriptions
- Updated kernel update check function (Doesn't work yet, I think it's because there is 2 'v' in the kernel version and build version, in other words it is a WIP!)
- We're moving back to Linaro 4.9 (Less bugs, more performance!)
[B]DorimanX 11.0 b005 (BETA)[/B]
- Wifi drivers updated to 1.141.44 thanks to @stelistcristi
- Updated to latest UBER toolchain
- Switched to UBER 4.9 toolchain instead of 4.8
- Revert: "allowed IO Read Ahead up to 4096KB"
- Allow mod of vfs cache pressure - This is used by cortex background service, don't modify if you don't know what you are doing
[B]DorimanX 11.0 b004 (BETA)[/B] - Tweak your GPU beyond belief :)
- More overclocking of GPU! (All steps can have higher or lower frequencies and voltages)
- Revert boot boost limits
- Fixed file permissions
[B]DorimanX 11.0 b003 (BETA)[/B]
- Separated root actions into own tab in stweaks
- Added zzmoove 1.0beta7a to replace zzmanX! Profile switching is included!
- Added back powersave governor
- Temporary workaround for root check (will not say if root is enabled or not)
[B]DorimanX 11.0 b002 (BETA)[/B]
- Optimize default profile for LP
- I will build trim and non trim builds for now on
- Remove sharpness tweak temporarily to prevent bootloop
- Still only supports CM12.1 based roms
- Fixes to custom profile reset
- Re-add missing performance governor in stweaks
- Allow users to debug stweaks again
- Separated CRON tasks into own tab , separated partitions fixes into own tab
[B]DorimanX 11.0 b001 - TRIM (BETA)[/B]
- Initial lollipop support thanks to lysergic acid
- All features from my dorimanx kk builds[/FONT]
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!
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)
Starting from build b022, I have introduced isorec into DorimanX kernel. 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
Which build should I use?
Linaro 4.9: Use this build for best stability. Battery life is better than UBER 6.1 and is the smoothest. Most users should use these builds.
UBER 6.1: Use this build for best performance. UBER 6.1 contains bleeding edge optimizations that may not be fully reliable yet, so this toolchain is better suited for advanced users.
Go with the build that is the best for you. You are the one that is making the changes so you are responsible for choosing what experience you want with the kernel! If you are still not sure which build to choose, use the Linaro 4.9 build first.
Main download link:
https://www.androidfilehost.com/?w=files&flid=43490
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.
In order to tweak the kernel properly, you need to install stweaks from the play store, or from the apk linked here, or from the XDA downloads page, or from the apk in the attachments below:
Troubleshooting
For general help, please use the Q&A thread
http://forum.xda-developers.com/galaxy-s2/help/qa-dorimanx-lp-5-x-x-t3161661
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:How do I flash your kernel?
A: You flash kernels like flashing ROMs, except you don't have to factory reset your phone. However, if you are official CM12.1 nightly, you will have to flash the kernel differently (if you want to flash my old unsigned builds).
Method A: If you get signature verification errors, you need to sign the zip with a program like Sign-em or Sign+.
Method B: To flash this kernel on official CM12.1 nightly, you first need to flash Philz recovery on your phone via ODIN. Here is the link to the for philz recovery: Philz Touch Recovery After that, you can flash the kernel like normal.
Method C: Another way is to create a kernel .tar file by extracting the zimage file located in /boot folder of the kernel zip then create a .tar archive. Then flash it in ODIN. Here is the guide to create your own kernel tar file: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381 For your convenience, I've create a tar file of build b002 in the guide linked.
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 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
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
let me try your kernel, btw where is download link ?
haris1976 said:
let me try your kernel, btw where is download link ?
Click to expand...
Click to collapse
I'm still building it right now. Will upload soon, will have my features from my personal builds on top of lysergic acids fixes.
First build up. Can't test since I'm on kitkat rom right now. Will update to LP when I have the chance to.
Ah man...... Here It is, great can you make a non trim version, pretty plsí*½í¸Š
NoctisBlade said:
Ah man...... Here It is, great can you make a non trim version, pretty plsí*½í¸Š
Click to expand...
Click to collapse
I'm not on my PC right now. Probably will upload new build tomorrow (running out of space in my build machine). Would be great if someone reports the issues they encounter and what's working.
Great to see a dedicated thread for Dorimanx Kernel for S2's lollipop support.....Subscribed and will be testing whenever I get time....Great job man....Good luck....
I tried it so far both on SlimLP and Omni and failed to boot on both. Bootloop on SlimLP and stuck on boot on Omni. Gonna keep on testing though.
Edit: Managed to boot on CM12.1 finally. Let's see how it goes.
kostelo said:
I tried it so far both on SlimLP and Omni and failed to boot on both. Bootloop on SlimLP and stuck on boot on Omni. Gonna keep on testing though.
Edit: Managed to boot on CM12.1 finally. Let's see how it goes.
Click to expand...
Click to collapse
Only cm12.1 ramdisk was merged. I'm working with lysergic acid and hopefully warrior to get it working on more roms.
little report about dualboot
Hi all, i quoted myself and about what i have done.
maybe that can help for more test, i found one rom that dualbooted, didnt test another for now.
And , i forgot to add yesterday that sdcard (int card) wasnt mounted when i ran 2nd LP rom.
thanks.
Troubadour666 said:
Hi @Lysergic Acid, sory for OT, little report about DUALBOOT i gave a try about it right now
i was on SlimLP build#12 from @warrior1208, runing Apolo 8 beta9 EXTv2.
i backuped SlimLP and formatted cache/dalvik/data
then i flashed pac_i9100_LP-MR1.Beta-2.Unofficial_20150628-122342 , new release from @phenomarc.
i rebooted the rom with his stock kernel and let it run 15min.
then, reboot recovery and i flashed your DORIMANX LP version and rebbot, the pac_i9100_LP-MR1.Beta-2 booted fine.
then , i rebooted again recovery (STANtrc) and restored the previous build from @phenomarc with my TBO black modified i have , on 2nd rom space i have kept with old SPIRIT 4.4.4, and rebooted .
At boot, this time i choose 2nd rom , and 2nd rom booted !
Thanks , You save dualboot for US , Man , ITS ENORMOUS
Click to expand...
Click to collapse
Lysergic Acid said:
Good to know that feature is already working mate, I had no clue about that honestly, cause the ramdisk for that needs two inits, two fstabs, etc
Click to expand...
Click to collapse
Troubadour666 said:
Hi all, i quoted myself and about what i have done.
maybe that can help for more test, i found one rom that dualbooted, didnt test another for now.
And , i forgot to add yesterday that sdcard (int card) wasnt mounted when i ran 2nd LP rom.
thanks.
Click to expand...
Click to collapse
@Troubadour666 can u give me link ROM from PAC_I9100_LP-mr1
haris1976 said:
@Troubadour666 can u give me link ROM from PAC_I9100_LP-mr1
Click to expand...
Click to collapse
http://www.darksideteam.com/threads/2010-5-0-2-UNOFFICIAL-SABERMOD-PAC-MAN-ROM-5-0-la-ROM-definitiva
No idea which language it is.
Dori for LP on S2, didn't see that coming, but will test asap with Slimsaber LP, and check if it works. Pedestre stopped apolo development and gustavo's kernel is also kinda dead so it's the only one left.
Don't drop it please!
Facuu said:
Dori for LP on S2, didn't see that coming, but will test asap with Slimsaber LP, and check if it works. Pedestre stopped apolo development and gustavo's kernel is also kinda dead so it's the only one left.
Don't drop it please!
Click to expand...
Click to collapse
It won't boot on Slimsaber LP at the moment, only CM12.1 based ROM, ramdisk incompatibility.
Edit : Apolo 8 beta 9 Omni boots slimsaber fine by the way, sorry didn't mean to speak of another kernel here.
Sorry for stupid question... Is this twrp based?
Or is that complete other?
Works for AOSP roms, right?
I9100 Tapatalk, DU AOSP 5.1.1 Lollipop
089man said:
Sorry for stupid question... Is this twrp based?
Or is that complete other?
Works for AOSP roms, right?
I9100 Tapatalk, DU AOSP 5.1.1 Lollipop
Click to expand...
Click to collapse
CWM 6.0.4.8
CM12.1 roms (RR,bliss....)
089man said:
Sorry for stupid question... Is this twrp based?
Or is that complete other?
Works for AOSP roms, right?
Click to expand...
Click to collapse
It's indeed for AOSP ROMs It's CWM based. I'm currently using it with CM12.1 by @Lysergic Acid.
EDIT: Oops, you beat me to it, @NoctisBlade. Perhaps what I can add is that so far I've been having great stability and battery life.
FP Bug fix and TRIM on older kernels
The Background:
Kernel development for older android versions have stopped for a while now. With the release of the FP Bug fix and TRIM enabled kernel, I decided to make my own personal builds! Please note that in no way I am going to maintain these kernels. I have enough kernels to maintain anyway!
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.
NO JELLYBEAN, KITKAT AND LOLLIPOP SUPPORT HERE!
DISCLAIMER:
ONLY FOR AOSP/STOCK 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 kernels includes the following additional features over stock kernel builds:
- Built with Latest Linaro 4.9 Toolchain (Smooth, fast and fluid)
- Updated FPBug fix is already included in 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)
Lysergic Acid (For Source and fixes)
DOWNLOAD:
Refer to third post
CHANGELOG:
Refer to second post
ISSUES:
Code:
- All bugs from original releases
USEFUL LINKS
- CPU Governor and I/O Scheduler Guide
- DorimanX tuning guide
TCP Algorithm guide
XDA:DevDB Information
FP Bug fix and TRIM on older kernels, Kernel for the Samsung Galaxy S II
Contributors
gsstudios
Kernel Special Features: See post #1
Version Information
Status: Testing
Created 2015-08-02
Last Updated 2015-08-02
Changelogs:
--UNRELEASED VERSIONS--
Code:
- Nothing here to see :)
--RELEASED VERSIONS--
Code:
Downloads
I will mostly work on this LP kernel since I have LP ROM installed. I will test each build before uploading it onto XDA. 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.
All builds with '-signed' at the end can be flashed using Cyanogen recovery, these zips are signed and should flash without errors.
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.
In order to tweak the kernel properly, you need to install stweaks from the play store or from the apk in the attachments below:
Troubleshooting
(Probably one of the most detailed troubleshooting guides for kernels on XDA)
Q:How do I flash your kernel?
A: You flash kernels like flashing roms, except you don't have to factory reset your phone. However, if you are official CM12.1 nightly, you will have to flash the kernel differently.
Method A: If you get signature verification errors, you need to sign the zip with a program like Sign-em or Sign+.
Method B: To flash this kernel on official CM12.1 nightly, you first need to flash Philz recovery on your phone via ODIN. Here is the link to the for philz recovery: Philz Touch Recovery After that, you can flash the kernel like normal.
Method C: Another way is to create a kernel .tar file by extracting the zimage file located in /boot folder of the kernel zip then create a .tar archive. Then flash it in ODIN. Here is the guide to create your own kernel tar file: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381 For your convenience, I've create a tar file of build b002 in the guide linked.
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: Which app should I use to tweak the kernel?
To have access to all of the tunables, you need to install stweaks from the playstore or from the apk linked in the downloads post.
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 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: 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: 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: 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
Good Job...If u need any help...plz let me know...Thanks.
Here is a highly experimental build based on Siyah 5.0i. It has the FP Bug fix included on it. Please, if someone has ICS installed, can someone test it. Proper build will have ICS included in the file name.
Thanks, gsstudios
Edit: Download link removed. Due to lack of compatibility updates done on siyah kernel, the kernel doesn't natively support linaro 4.9, therefore it will not be stable
{
"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"
}
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