[KERNEL][UNOFFICIAL][LINARO/UBER]DorimanX KK 4.4.4 - Galaxy S II Android Development

{
"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.