[KERNEL][EOL][LINARO/UBER]DorimanX kernel for LP and MM - 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)​
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.

Related

[Kernel] [.38.8] intersectRaven's Kernel (AVS/CAVS)01/08/2011 22:00

This is my own personally compiled kernel based on the latest kernel from Cyanogen's Github repository with Kmobs' undervolt modifications, CodeAurora's AVS code, pershoot and rotohammer's audio gain mod and several compiler optimizations based on initial idea from psyq.
Only major releases will be advertised here.
All changes since 05/05 can be found at my Euroskank host:
http://intersectraven.euroskank.com/kernels/
*Thanks to RyanMacG for the free hosting!
Old uploads with minor changes can be found at my MediaFire folder or my Bitpad folder:
http://www.bitpad.co.uk/intersectraven
http://www.mediafire.com/intersectRaven
Major features:
- based on latest Cyanogen Mod kernel source from his GitHub repository
- numerous compiler optimizations with a custom compiler by redstar3894
- all CPU power governors for user dependent tweaking of power saving method
- Hybrid AVS (Adaptive Voltage Scaling combined with Static Voltage Scaling) support for maximum possible power savings dependent on CPU requirements and a customizable version (CAVS) for people who like to tweak how far their N1s can go
- universal update.zip template made by Koush
Instructions:
1.) Reboot to recovery and flash the update.zip directly.
OR
Instructions for zImage and bcm4329.ko driver extracted from the update.zip(from command line):
1.) adb remount
2.) adb push bcm4329.ko /system/lib/modules
3.) adb reboot bootloader
4.) fastboot flash zimage zImage
5.) fastboot reboot
OR
Use ADB GUI by minooch found here:
http://forum.xda-developers.com/showthread.php?t=666964
*please note the instructions...push the wifi driver BEFORE rebooting for flashing zImage...if your wifi is turned on when you reboot before you pushed the wifi driver for the kernel, there is a chance that you will go into a bootloop due to the incompatible wifi driver!
Changelog:
20120108_2143:
- just merged pershoot's commits
20111203_11XX:
- enabled MSM EHCI
20111114_23XX:
- integrated CM's commits (mainly bluetooth and WiFi fixes)
20111111_19XX:
- compiled using updated Mjolnir/Linaro compiler hybrid (having problems with our Mjolnir GCC)
- enabled SYN_COOKIES as requested
- some tweaks to the VFS settings
- switched network scheduler to SFB
- switched TCP congestion to Veno from YeaH (seems it's better for devices with a greater chance of random drops of packets)
20111010_11XX:
- disable CleanCache for YAFFS (too complex to change)
- more proper reapplication of changes from 3.0
20111009_22XX:
- enabled CleanCache for YAFFS, EXT3 and EXT4 (experimental)
20111008_23XX:
- ported BogoMIPS calibration from 3.0
- added CleanCache from 3.0
- switched to SIO from BFQ
- block IO batching from 3.0
- activate_pages batching from 3.0
20110904_07XX:
- added SmartAssV2 CPU governor
20110828_13XX:
- fix AVS to actually work (see previous latest post for apology... )
*this should restore the instability on some devices that can't handle AVS
20110828_00XX:
- prevent excessive suspend attempts
- optimized sha1 implementation
20110813_15XX:
- increased NAND buffer to 8k similar to codeaurora's version
- enabled 8-bit transfers for when the MMC card supports it
20110724_20XX:
- SmartAss improvement from the test kernels
- AVS code improvement also from the test kernels (hopefully improved the stability)
- RCU optimizations
- updated Mjolnir compiler
20110713_10XX:
- re-hauled SmartAss governor:
* interactive threads instead of workqueues to improve responsiveness when ramping-up frequencies
* reduced stepping frequency to use lower frequencies more
20110707_08XX:
- fixed the Voice Search problem
20110706_09XX:
- code cleanup
- additional tweaks
20110628_09XX:
- ARM improvements to memcpy and memmove operations from Wildfire (arco's kernel source)
- cherry-picked serial number commit from CM kernel
20110608_21XX:
- rebased everything together with removal of worthless commits
- added 2 new governors from SavagedZen kernel (SavagedZen & InteractiveX)
- updated code of Smartass governor to the one in SavagedZen since it seems more updated than the one I found
20110527_21XX:
- new method for addressing slow writes on USB from CodeAurora (although it's still slow using native USB mount and I didn't test using another mounter)
- some SIRC potential bug fixes
- input event handling modification from Google
20110523_08XX:
- compiled using updated Mjolnir
20110522_11XX:
- upgraded to v2.6.38.7
20110521_15XX:
- interrupt masking
- smd_tty buffer limit implementation
20110519_22XX:
- fix for potential bug and power leak improvement in DSP driver
- GPIO tweaks
20110516_19XX:
- increased DMA zone to 14MB (may speed some things or may not)
- timer workarounds have been removed as they're unneccessary on Scorpion
- prevent reading from write-only registers (just silly)
- used relaxed access functions for some functions
- remove extra interrupts sent from the SMD channel
20110515_21XX:
- added another commit from android unmerged which implements a watchdog to catch lockups during device resume
- fix for wakelocks which addresses the problem where while being connected to a computer, any attempt to power up will result in display immediately shutting off with touchscreen buttons still on
- uses an updated Mjolnir compiler
20110514_17XX:
- rebased everything
- removed some commits which were useless on the N1
- more zen branches merged
- WiFi-Fast patch has been integrated in all kernels since it seems to have no effect on battery (no more separate WiFi-Fast release)
20110511_22XX:
- reverted a change made to PMEM driver since the commit it was reliant to was reverted (sorry! didn't notice this...I wasn't too critical of my earlier cherry-picks... )
Link to a file which contains all kernels:
http://hotfile.com/dl/117478444/390f688/intersectR_-_20110511_22XX.zip.html
20110510_18XX:
- updated to 2.6.38.6
- committed some more video driver commits from CodeAurora
Link to a file which contains all kernels:
http://hotfile.com/dl/117350839/0a9a504/intersectR_-_20110510_18XX.zip.html
20110509_14XX:
- merged some commits from Android repositories that were still unmerged yet may prove useful for Ashmem and RPC
Link to a file which contains all kernels:
http://hotfile.com/dl/117209820/5b7fe7b/intersectR_-_20110509_14XX.zip.html
20110507_21XX:
- even more improvements from CodeAurora
Link to a file which contains all kernels:
http://hotfile.com/dl/117048553/0831385/intersectR_-_20110507_21XX.zip.html
20110506_15XX-16XX:
- enabled cache error reporting as this is indicative of how tolerant your N1 is to AVS undervolting
- smartass governor (from Temasek)
*this was mistakenly included in the previous release
- a minor kernel scheduling statistic commit
Link to a file which contains all kernels:
http://hotfile.com/dl/116922979/5fb2ec0/intersectR_-_20110506_15XX-16XX.zip.html
20110505_16XX-17XX:
- updated Mjolnir compiler
Link to a file which contains all kernels:
http://hotfile.com/dl/116827854/5839b43/intersectR_-_20110505_16XX-17XX.zip.html
20110505_08XX-09XX:
- AVS and CAVS now both allow changing of voltages on-the-fly. The only difference now is that AVS is undervolted by default while CAVS is undervolted to the same voltages that CM uses in his SVS kernel
- uses eviollet's on-the-fly voltage modification system instead of the previous one I had which is a lot more flexible
Link to a file which contains all kernels:
http://hotfile.com/dl/116798881/0d5b5bf/intersectR_-_20110505_08XX-09XX.zip.html
20110503_09XX:
- updated to version 2.6.38.5
Link to a file which contains all kernels:
http://hotfile.com/dl/116600585/b76a4b6/intersectR_-_20110503_09XX.zip.html
20110502_10XX:
- synced with pershoot's latest modifications which mirror CM's latest addition with regards to USB accessory function (not too important I think since it seems to be for future ADB use)
- uses an updated Mjolnir compiler (20110429)
Link to a file which contains all kernels:
http://hotfile.com/dl/116528049/1865aa6/intersectR_-_20110502_10XX.zip.html
20110424_11XX:
- reverted WiFi driver to same version CM uses for mainline kernel to fix channel 11 issues with the newest one
20110422_12XX:
- updated to 2.6.38.4
- compiler updated
20110421_15XX-16XX:
- first files to be hosted by Bitpad (http://www.bitpad.co.uk/intersectraven/)
*Thanks to MajorProbes
- just a minor release since I only updated the compiler
20110416_20XX:
- several compiler optimizations enabled (loop unrolling, peeling, etc.)
- zen-kernel cherry-picks for memory and fs optimization
20110415_23XX:
- updated to 2.6.38.3
- compiled using latest Mjolnir with an experimental merge by redstar
20110409_23XX:
- integrated a bluetooth fix and MMC quirks improvement from official Google repositories
20110407_13XX-14XX:
- integrate CM commits on futex optimization and removal of dodgy optimizations
20110403_12XX:
- fix for USB transfer speed (should now hold at 1MB/s without dropping)
20110401_22XX-23XX:
- first 2.6.38.2 release based on pershoot's 2.6.38
- added the usual mix (AVS, SLQB, CodeAurora patches, etc.)
- compiled using Mjolnir GCC 4.6.1
- changed FPU optimization to NEON
20110328_08XX-09XX:
- updated to 2.6.37.6
20110328_07XX:
- compiled using Mjolnir GCC4.6.0
- enabled Link Time Optimization and Graphite Optimization (use Google for definitions)
20110326_08XX:
- updated BFQ to v2-r1
20110324_18XX:
- updated to 2.6.37.5
20110320_17XX:
- merged Nick Piggin's RCU patches which were originally for 2.6.38 (one of the things Linux was excited about according to Phoronix)
20110319_09XX:
- merged latest CM kernel commits which enables the ff:
- enabled RCU boost
- enabled touchscreen filter (reduce CPU load made by touchscreen)
20110315_22XX:
- updated to 2.6.37.4
20110312_23XX:
- round 2 of CM's wonk fix attempt integrated
- toolchain update
*for links, go to my MediaFire folder as specified above
20110311_1623:
- integrated cyan's wonk fix attempt
- VPN "fix" (I don't like this one since it's just a backport of the old PPP interfaces)
*for links, go to my MediaFire folder as specified above
20110308_2246:
- updated to .37.3
- based on CM's latest kernel source
- with SLQB and BFQ v2
- regular and customizable AVS
- some CodeAurora patches
*for links, go to my MediaFire folder as specified above
20110213_1506:
- corrected minimum voltage value to 800mV
CFS-HAVS-CM7-NOBOOST -> http://www.mediafire.com/?m32mi1744ksb55m
20110213_1035:
- test release for new AVS-CUSTOMIZEABLE build which allows for runtime customization of AVS minimum and maximum limiters for more flexible AVS voltages depending on your CPU tolerance (/sys/module/avs/parameters/avs_adjust)
- AVS debugging outputs can also be toggled in runtime (/sys/module/avs/parameters/avs_debug -> set to 0 to not display, 1 to display)
CFS-HAVS-CM7-NOBOOST -> http://www.mediafire.com/?bt7mmtlmg407ne1
*format for avs_adjust is:
frequency,minimum voltage,maximum voltage
e.g.
echo 245000,925,975 > avs_adjust
**AVS debugging output will be enabled by default when you modify the limits
Finally created a github to store all of my kernel modifications:
http://github.com/intersectRaven/
To follow me for updates on Twitter:
http://www.twitter.com/intersectRaven
[Kernel] [.35.10, .37] intersectRaven's Kernel (HAVS-AXI-FM-720p-Zen)1/9/2011 10:13
Reserved for intersectRaven - Added 2post to allow OP to have more place for futur update
Finally a thread!
been using your kernels for some time now, good work!
---------------------------------------------------------------
Updates: I thought I'll use this space to provide some info since its right next to the OP
BFS:
BFS is the Brain **** Scheduler. It was designed to be forward looking only,
make the most of lower spec machines, and not scale to massive hardware. ie
it is a desktop orientated scheduler, with extremely low latencies for
excellent interactivity by design rather than "calculated", with rigid
fairness, nice priority distribution and extreme scalability within normal
load levels.
http://ck.kolivas.org/patches/bfs/bfs-faq.txt
CFS
Completely Fair Scheduler is the name of a task scheduler which was merged into the 2.6.23 release of the Linux kernel. It handles CPU resource allocation for executing processes, and aims to maximize overall CPU utilization while maximizing interactive performance.
http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
Comparison of BFS vs CFS: http://www.cs.unm.edu/~eschulte/data/bfs-v-cfs_groves-knockel-schulte.pdf
Conclusion
The results indicate that CFS outperformed BFS with minimizing turnaround time but that BFS
outperformed CFS for minimizing latency. This indicates that BFS is better for interactive tasks
that block on I/O or user input and that CFS is better for batch processing that is CPU bound.
Click to expand...
Click to collapse
can i use this kernel along with the desire camera app?
britoso said:
Finally a thread!
been using your kernels for some time now, good work!
Click to expand...
Click to collapse
Had my dog press the enter key to prevent me from chickening out.
jblazea50 said:
can i use this kernel along with the desire camera app?
Click to expand...
Click to collapse
I haven't tested it so I don't know if it needs something from the kernel to work.
@intersectRaven - in the http://forum.xda-developers.com/showthread.php?p=6003800#post6003800Audio Mod thread rotohammer incorporated settings that increased both the bluetooth and in-call/earpiece volume. is your audio fix for a headset/bluetooth headset and/or does it incorporate higher values for in-call volume as well? thanks!
cortez.i said:
@intersectRaven - in the http://forum.xda-developers.com/showthread.php?p=6003800#post6003800Audio Mod thread rotohammer incorporated settings that increased both the bluetooth and in-call/earpiece volume. is your audio fix for a headset/bluetooth headset and/or does it incorporate higher values for in-call volume as well? thanks!
Click to expand...
Click to collapse
Hmmm...thanks for pointing that out. I'll probably release a new version later which will have this. (loading my Nexus Compilation Environment VM now...)
*Edit: I recompiled with the .min and .max settings he specified but reading further back it seems he changed some other things so I can't be sure if just this will provide the volume increase desired.
cortez.i said:
@intersectRaven - in the http://forum.xda-developers.com/showthread.php?p=6003800#post6003800Audio Mod thread rotohammer incorporated settings that increased both the bluetooth and in-call/earpiece volume. is your audio fix for a headset/bluetooth headset and/or does it incorporate higher values for in-call volume as well? thanks!
Click to expand...
Click to collapse
Hmmm...thanks for pointing that out. I'll probably release a new version later which will have this. (loading my Nexus Compilation Environment VM now...)
*Edit: I recompiled with the .min and .max settings he specified but reading further back it seems he changed some other things so I can't be sure if just this will provide the volume increase desired.
intersectRaven said:
I haven't tested it so I don't know if it needs something from the kernel to work.
Click to expand...
Click to collapse
It works. I thought you incorporated the audio fix yesterday too!
britoso said:
It works. I thought you incorporated the audio fix yesterday too!
Click to expand...
Click to collapse
I just compiled one with higher settings based on rotohammer's research. I think I'll stick with the default ones in my previous version though so its okay to skip this latest one.
For those who wanted to try out the modified values:
http://www.mediafire.com/?dqynw1inh3y <= 2.6.32
http://www.mediafire.com/?mmjwxzjlmmw <= 2.6.33
I'm working on a mod that will allow us to change the min_vol and max_vol from a file. Kernel SOP dictates this not advised, but I don't have time to learn how to implement a procfs hook.
I also used the voltages specified by kmobs so there should be no difference with the voltages. .32 is from the android kernel source while .33 is from cyanogen's. .32 is the stable kernel while .33 is still in its experimental stage.
Thanks a lot I've been looking for something like this!
intersectRaven, any chance to release Overclock kernel ?
1267Mhz on the nexus one will be great. hahahaha
rheza02 said:
intersectRaven, any chance to release Overclock kernel ?
1267Mhz on the nexus one will be great. hahahaha
Click to expand...
Click to collapse
haha...I'll think about it...I don't have the courage to try an OCed version though so you'll have to test it yourself if ever!
intersectRaven said:
I just compiled one with higher settings based on rotohammer's research. I think I'll stick with the default ones in my previous version though so its okay to skip this latest one.
For those who wanted to try out the modified values:
http://www.mediafire.com/?dqynw1inh3y <= 2.6.32
http://www.mediafire.com/?mmjwxzjlmmw <= 2.6.33
Click to expand...
Click to collapse
i'm currently using MoDaCo Alpha 19, which reports using a 2.6.33.1 kernel. so i would use the 2.6.33 version, correct? just to confirm, are your volume values the same as used by rotohammer? also, where is the zImage stored on my device, that is if it's actually saved at all (yes, i am a newbie, lol). thanks!
cortez.i said:
i'm currently using MoDaCo Alpha 19, which reports using a 2.6.33.1 kernel. so i would use the 2.6.33 version, correct? just to confirm, are your volume values the same as used by rotohammer? also, where is the zImage stored on my device, that is if it's actually saved at all (yes, i am a newbie, lol). thanks!
Click to expand...
Click to collapse
yes u would use the .33 if ever...the links u quoted does use rotohammer's values...and lastly, the zimage is flashed onto the image/kernel area in your device's boot partition...oh and no shame being a noob...we were all noobs once...
This kernel crash on my nexus one with desire camera when I try to see a video.
Anyone can confirm this?
www1 said:
This kernel crash on my nexus one with desire camera when I try to see a video.
Anyone can confirm this?
Click to expand...
Click to collapse
I just recorded a video with the desire camera app and played it back fine.

[KERNEL][ALL ROMS][SEP 14] Glitch for Flo/Deb - r574

These kernels are provided as-is without warranty. I'm not responsible for any problem you may encounter with your phone or tablet or if your cat suddenly dies.
Although, don't expect support even if I will eventually help because I love cats.
{
"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"
}
​
Overview & features :
"With great power comes great responsibility". Don't go crazy with overclocking, only the best devices will be able to get 2.3 GHz stable or even bootable, though heat will be your main issue.
- Based on Google AOSP 3.4.0 and LineageOS's kernel sources for MSM devices
- CPU OC up to 2.3Ghz with OV/UV support / minimum frequency down to 81 MHz (configurable)
- L2/bus speed OC up to 1.49GHz / 4.8GBPS
- GPU OC up to 627 MHz with OV/UV support
- CPU governors : Faux's intellidemand, interactive, ondemand, smartmax, intelliactive, conservative, elementalx
- I/O schedulers: noop, deadline, cfq, fiops, sio, BFQ, zen
- Kernel based intelli-thermal driver by Faux123
- Kernel based msm hotplug driver by Fluxi
- tni.andro's battery life extender support
- Magnetic on/off setting
- USB fast charge support
- USB OTG charge hack support by flar2
- FauxSound support
- LineageOS's PCC color tweaking
- Fsync switch on/off
- Touchscreen patches by Showp1984
- Touchscreen wake/sleep gestures by flar2
- Kali Pwn Pad experimental support
- Optimized algorithms and libraries
- Various performance and power saving tweaks
- NTFS, NFS and exFAT support
- F2FS support up to all-F2FS with automatic ramdisk patching at flash time (reflash if you change partition format !)
- Kexec-hardboot support for Multirom compatibility
- Full package comes with Aroma installer to set core features at flash time (L2 OC level, CPU OC, etc.)
- Pure package will restore Aroma settings backup if present, or else will offer you a balanced preset for day to day usage
- Custom Synapse support with various settings and core features tweaks
- Compiled with Linaro 6.1.3 toolchain with various optimizations
- SELinux Permissive patch (Disabled by default, can be enabled in Aroma)
- Wifi firmware overrider to fix wifi on 4.4.3 & lower or on roms using old wifi firmware (up to r226 - Kitkat only)
CHANGELOGS IN #2 POST
You can tweak multiple options of this kernel with TricksterMod, FauxClock, Kernel Adiutor, Synapse(r500 and up, definitely recommended to get the most available options) or similar apps. (They are all available on the PlayStore)
Note to MultiROM users : don't use the kernel sharing feature. Flash the kernel on each rom instead. Also, it may take more time booting on secondary roms when using F2FS. Don't worry and wait for a bit ​
Downloads (all kernels are compatible with both flo and deb)
Grab your build from here :
Glitch kernel r574 download - For AOSP 6.0.1/7.x.x and LineageOS 14.1​
Mirror + older builds : Mediafire​
FAQ :
What are the differences between "Full" and "Pure" builds ?
The "Full" builds are using Aroma Installer so you can tweak various options at flash time. At the end of the process, a file containing your settings will be created (/sdcard/glitch-settings.conf). The "full" builds are also able to restore your settings from Aroma after a rom flash or wipe for example.
On the other hand, "Pure" builds aren't coming with Aroma and will try to restore your settings from your SDcard, or use a default profile if none is found. Both Full and Pure builds are coming with a custom Synapse support to let you tweak all the core options on the fly once booted.
If you flash a "Pure" build without a profile, the default preset will be applied. It's been tweaked for a good balance between performance, power consumption, stability and functionality for day to day usage. The default settings applied are as follow :
- 1.7GHz max CPU freq (from 1.5GHz stock) / 1GHz max CPU freq when the screen is off / "Balanced" L2 OC
- msm_hotplug driver in place of msm_mpdecision
- 450MHz max GPU freq (inline with other Snapdragon 600 devices - from 400MHz stock)
- Safe CPU and GPU undervolting for lower heat and power consumption
- Deadline I/O sched / Interactive CPU governor
- Doubletap to wake and fastcharge enabled (Doubletap to wake will slowly drain power during suspend, so disable it if not used)
- Everything else is kept stock
What do I have to do to use F2FS on one (or more) of my partitions ?
First, BACKUP your data if needed, especially if you're planning to use F2FS on DATA partition, as changing filesystem will wipe the partition. Change partition formats as needed in your recovery. It is NOT recommended to convert system partition as F2FS as it'll be slower than EXT4 to begin with (as the partition is mostly read only) and will alter compatibility with many roms (especially CM/LineageOS based). The last thing to do is to flash any Glitch kernel with a revision number past r150. You can restore your settings from SDcard if any, the install process will detect the partitions and modify the ramdisk accordingly so you can finally boot and use your fresh FS.
What L2/cache OC setting should I use ?
This setting will overclock bus speed and RAM so it's a bit delicate to tweak, yet it can give a nice "free" global performance boost. A simple test to check for stability is to run the camera app 3 or 4 times in a row while waiting for 10 seconds between each launch. If your device freezes, it's unstable ! It's also the only setting you can't change on the fly once booted, either from Synapse or sysfs, and requiring a reflash (using Aroma or changing the value in /sdcard/glitch-settings.conf).
Let me give you some details about the available settings so you can choose wisely :
Stock (1.13GHz-4.26GBps) is the regular, out of the box, non OC setting.
Improved (1.19GHz-4.26GBps) is the same as "ElementalX" setting in Flar2's kernel.
Balanced (1.22GHz-4.66GBps) is the same as "Ultra" setting in Flar2's kernel.
Fast (1.35GHz-4.66GBps) is a nice jump over "Balanced", yet stable for most devices. A kind of sweet spot.
Extreme (1.43GHz-4.80GBps) is were most users will start to get issues. Provides a great boost if stable.
Glitchy (1.49GHz-4.80GBps) pushes your hardware to the limits. Will be unstable for most devices.​
Thanks to everyone helping me to debug and find new useful things to integrate !
Without all of you, this kernel wouldn't be !​
XDA:DevDB Information
Glitch kernel for Flo, Kernel for the Nexus 7 (2013)
Contributors
Tk-Glitch, Google, animania260, CyanogenMod, TeamDouche, flar2, Faux123, franciscofranco, Showp1984, Team-Hydra, sixstringsg, Poondog, ZeroInfinity, Fluxi, arter97, neobuddy89, alesaiko, 228aye, AndreiLux, amarullz ,followmsi, and all my community
Source Code: https://github.com/Tk-Glitch/Flo_AOSP
Kernel Special Features: CPU OC/UV 2.3 GHz, GPU OC/UV 627MHz, FauxSound, S2W/S2S/DT2W, Bus speed OC
Version Information
Status: Stable
Created 2013-09-19
Last Updated 2017-09-13
logs
Git commits for nerdz & lolcats​
Latest release's changelog with words for humans :
14/09/2017 - r574 :
- Synced with latest LineageOS 14.1;
- Updated toolchain to Linaro GCC 7.1.1-2017.08;
- Added touchscreen-calibration fix patch by parrotgeek1;
Previous changes below :
17/07/2017 - r572 :
- Synced with latest LineageOS 14.1;
11/07/2017 - r571 :
- Synced with latest LineageOS 14.1;
29/06/2017 - r570 :
- Synced with latest LineageOS 14.1;
- Updated toolchain to Linaro GCC 7.1.1-2017.05.
03/06/2017 - r566 :
- Synced with latest LineageOS 14.1;
- Changed the behaviour of the permissive/not permissive switch to either force permissive or keep rom default (instead of forcing enforcing before) to prevent issues with some implementations;
- Added a service that restarts GMS (Google Mobile Services) post boot to fix memory leak/battery drain linked to them - Curently working in permissive mode only (like init.d and some advanced Synapse settings);
- Updated toolchain to Linaro GCC 6.3.1-2017.05.
07/05/2017 - r565 :
- Synced with latest LineageOS 14.1;
- Added a simple check for the MPDecision service starting mechanism used by your rom : If it's using the same trigger as LineageOS (init.flo.power.rc), you'll be able to enable/disable the service at will after boot. If it's using a different trigger, the binary will be nuked the old way (renamed to mpdecision_bck) if you're using the in-kernel msm_hotplug driver (effectively preventing you to play with it after boot). It's not a solution that pleases me, but it will fix cases of both hotplug drivers loaded at the same time on non-LOS-based roms, and that's all that counts for now.
14/04/2017 - r564 :
- Synced with latest LineageOS 14.1;
- Corrected HZ reference in touchscreen driver.
30/03/2017 - r563 :
- Fix potential touchscreen inconsistencies on some panel revisions
- Fix gesture switch (S2S/S2W/timeout)
27/03/2017 - r561 :
- Synced with latest LineageOS 14.1;
- Backported high-resolution support for sched-clock;
- Fixed CPU detection on subsystem_restart;
- Make rpm clocks sleeping clocks;
- Pushed updates from franco kernel regarding GPU, CPU freq and video;
- Added Zen I/O scheduler (pretty nice sched to say the least);
- Enabled I/O is busy flag for msm_hotplug driver by default (boosts CPU freq during heavy I/O load -> big smoothness gains in many apps and games);
- Added compiler fixes and optimizations from alesaiko (breakfast kernel);
- Moved to latest Linaro GCC 6.3.1 compiler (as the changes above fixed high power consumption issues on GCC5+);
- Consolidated Synapse support. The path of the generated config file is now /data/synapse instead of ramdisk to keep it safe during rom upgrades and reboots. If you get a "No UCI support" message on first Synapse launch, just kill the app and relaunch it. It'll not happen again after that unless you wipe data or I'm forcing a regen in a future update.
- Fixed init.d injection not using the correct path for busybox since a few releases and updated the execution process to N standards;
- Changed the way we get rid of mpdecision to prevent the service from starting in the init process instead of renaming the binary. This enables the possibility to enable or disable mpdecision on the fly after boot, even if using msm_hotplug as default hotplug driver.
- Fixed missing options in Synapse;
- Added various smaller performance patches and optimizations as well as a few more variables to play with for nerdz and lolcats (see github commits);
- Tweaked debugging config;
12/03/2017 - r544 :
- Sync with latest LineageOS 14.1
- Disabled backlight dimmer by default - Added a note to Aroma installer about potential issues with some panel revisions
23/12/2016 - r543 :
- Sync with latest CM14.1
18/12/2016 - r542 :
- Enable RPFILTER (CM14.1 tethering fix)
05/12/2016 - r541 :
- SElinux switch now works on boot without needing root access. As a result, also removed related post-boot script hooks
- Added prebuilt config file for Synapse for faster launch and fix possible error on first launch (clear Synapse data if you get issues)
04/12/2016 - r540 :
Due to some of the changes in this build, restoring settings from sdcard backup (by flashing Pure Edition or restoring through Aroma) may lead to different settings being applied depending on what you set before. It is strongly suggested to use the Full installation at least once to update your settings or delete glitch-settings.conf on the root of your sdcard before flash to use the default preset.
- Post CM14.1 merge cleanup pass. It was definitely needed ! Including, but not limited to :
- Removed Lazyplug and Intelliplug hotplug drivers (due to conflicts leading to performance issues)
- Removed Dynamic Fsync / Added switch to disable Fsync (after corrupting ~15 installations with DynFsync, I don't feel like it's worth the slight I/O perf boost)
- Replaced Showp1984's DT2W by flar2's S2W/S2S/DT2W (the touchscreen issues I faced with it aren't reproducible anymore)
- Removed LZ4 and use XZ compression instead
- Removed WQ_POWER_EFFICIENT (couldn't see a measurable gain with it enabled)
- Removed ROW ioshed
- Rollback'd to older Intellidemand governor​- Reworked settings application and restoration system to work with CM14.1/without SuperSU and load it early during boot by init hooking (CM14.1 PCC livedisplay related race condition "fix" included). Note : MultiROM users, you may want to disable MultiROM menu if you have it enabled to further reduce the chances to trigger the issue (completely fixed it on my side). Feel free to report your findings on the matter.
- Added flar2's ElementalX governor
- Updated default profile (the one you get while flashing Pure package or using restoration option in Aroma without sdcard backup)
- Updated thermal profiles
- Updated available options in Aroma
- Updated busybox to 1.25.1 YDS and moved from /sbin to the more convenient and standard /system/xbin
- Updated Selinux switches to work with more roms (now working on CM14.1)
- Moved Synapse files from /data/synapse to /res/synapse in ramdisk
- Updated Synapse presets
- Updated Synapse settings (Aroma installer will give more gestures-related options though, at least for now)
29/11/2016 - r534 :
This kernel will only work with AOSP 7.x and latest CyanogenMod 14.1 based roms. If you get incorrect colors and slow UI, rollback to r533 CM.
- Rebased using CM14.1 tree
- Updated color controls to mimic CM's PCC implementation (Thanks @flar2)
07/11/2016 - r533 :
- Added SDCardFS support
- Fix for CVE-2016-3903
- Fix for CVE-2016-3934
- Fix for CVE-2016-7117
- Added LazyPlug switch and settings to Synapse (hotplug tab)
- Added DT2W switch to Synapse (misc tab)
- Fix GPU voltage range formatting in Synapse
- Fixes regarding power efficiency
- Contextual fixes and speedups
- Now building CM variant of the Nougat kernel too. AICP is the first N rom on this device to require a CM compatible kernel.
14/09/2016 - r530 :
- Modified rom injection/flash time mods logic to be more robust and universal. Fixes inconsistent boot or even bootlooping on hybrid F2FS roms like CyanogenMod or PureNexus THIS CHANGE MAY FORCE YOU TO REFLASH YOUR ROM TO BE ABLE TO BOOT (even on a non-hybrid rom - no wipe required)
- Fixed settings not applying after setting them through Aroma/glitch-settings.conf
- Security patch to avoid invalid access to ashmem area
- Security patch for vulnerability CVE-2016-2059
- Removed deprecated binary injection code
- Default thermal presets calibrated for better efficiency and performance (they were too aggressive in r520)
- Little naming change for the builds. Full is still "Full", but "Restore" is now "Pure". Pure edition is now fully standalone and doesn't require a previously generated profile from Full edition (but will gladly restore it as before if found during install). It can be fully tweaked through config file and/or Synapse like Full edition.
- Nougat build "Full edition" now has a Nougat themed splash screen for Aroma
- Synapse presets are now working. Make sure to press apply when Synapse comes back if you want to keep it ! (Make sure to clear Synapse data after first boot to force a regeneration !)
- Small things you won't notice
24/08/2016 - r520 :
- Rebase from latest AOSP sources
- Synapse support with many more features and personnalization available than ever before ! Aroma settings are a joke compared to what you'll have in Synapse. Don't flash UKM on top by the way, and make sure to clear Synapse data if you've flashed one of the previews. Even more to come soon.
- Updated Neobuddy89's msm_limiter driver to latest from Nexus 6
- Updated Neobuddy89's state_notifier driver to latest from Nexus 6
- Moved to Faux123's Intelli-thermal driver
- Added some memutils optimizations and more for performance
- Updated Xbox One gamepad driver
- Removed loads of dead code and buggy merges
- Switched to Linaro 4.9.4 toolchain - After weeks of testing, my tab runs cooler, stabler, and longer than with 5.x for an invisible performance difference. Worth it !
10/08/2016 - Preview r516 is available here. More options available in Synapse which is now also enabled with the "full" build, merged android-6.0.1_r0.105, and various other tweaks for speed and power savings. Full changelog here.
04/08/2016 - A preview (r513) is available here. Synapse part still needs some work. Notably, some hotplug drivers options are missing and you can't apply presets. The kernel itself should be stable enough for day to day usage.
12/07/2016 - r499 :
- Fix for glitch settings not applying if the rom doesn't use the init.trace.rc file (Dirty Unicorns is one of them)
- Sync fstab with latest cm13 (may fix usb otg on cm13 based roms in some specific configurations)
11/07/2016 - r478 r498 :
- Synced source up to android-6.0.1_r0.98 changes (latest)
- Getting ready for rebase and Synapse-compatible release
- Removed deprecated libs from r478 installer (fixes setperm errors on some custom/recent roms)
- Fixed CM compatibility
10/12/2015 - r412 :
- Merged with android-6.0.1_r0.1 changes
- PowerHAL patch to fully disable touchboost calls when Qualcomm MPdecision isn't used. This gets rid of the touchboost log spam and (small) overhead.
- Updated F2FS
- Installer scripts fixes and cleanups
- Added back CM build - untested
02/12/2015 - r410 :
- Updated base to linux 3.4.110
- Merged with android-6.0.0_r0.1 changes
- Added Neobuddy89's MSM Limiter driver, enabling max/min/suspend frequencies tweaking on the fly. No more need to reflash for that (/sys/kernel/msm_limiter/ for who's interested). Also added his state notifier driver for further tweaking.
- Removed MSM Sleeper as it's covered by MSM Limiter already
- Changed how settings are applied (moved from init.d script to service) to prevent permission denied issues (Thx Flar2). Due to changes to the way your settings are handled, it's recommended to make a full installation. Settings aren't retrocompatible with previous Glitch kernels !
- Performance and stability improvements by removing coresight from Adreno drivers and better CPU management/scaling through MSM Limiter
- Aroma slight changes to reflect internal changes (note : CPU uV is now applied for both 384MHz step and lower ones)
15/09/2015 - r361 :
- Fixed no mobile network issue on DEB
- Disabled unnecessary debugging
13/09/2015 - r360 :
- Merged with android-5.1.1_r0.17 changes
- Added Lazyplug hotplug driver by Arter97 (you may need to make a full installation if you want to switch to this driver)
- Updated F2FS
- Updated BFQ to v7r8
- Added experimental Nvidia relaxed power savings
- More fixes and various optimizations regarding performance and efficiency
09/09/2015 - r353 :
Note : CM related issues some are encountering aren't adressed with this update. CM team is breaking more and more stuff while using AOSP bases for the kernel and I won't make a CAF based version again. The updated toolchain and added fixes in this release may or may not help, but I won't provide support for CM related issues anymore. Sorry for the inconvenience.
- Fixed SELinux switches (You'll need to use the restore function in full package or just the restore package to switch between permissive and enforcing modes. Enabling it in glitch-settings.conf isn't enough for it to work.)
- Disabled Android Logger by default for less overhead
- Updated toolchain to Linaro GCC 5.2.0 with LTO support
- Tiny fixes
02/07/2015 - r350 :
- Merged with android-5.1.1_r0.13 changes
- Fixed missing governors from previous release
- Added native support for Xbox One controller from Linux 3.17
- Fixed a potential instability case in idle state
- Updated base to linux 3.4.108
- Under the hood fixes
- CM and AOSP kernels are now sharing the exact same base for better stability and maintenance
08/05/2015 - Hotfix - r344 :
- Rolled back various GPU driver patches to fix some Chrome scrolling lockups and possible RR linked to the underlying bug linked to them
- Send enforcing=0 to kernel command line if you're using the permissive ramdisk mode (may fix boot on some non-standard roms - AICP still not booting for me though.. If you know why I'm all ears)
- Modify fstab.flo file in ramdisk even when using CM kernel (enables some non-standard CAF based roms with no "multi-mount fstab" support to boot - it mustn't exist, but better safe than sorry)
08/05/2015 - r343 :
- Merged with android-5.1.1_r0.10 changes
- Removed UKSM
- Disabled KSM
- Removed transparent compression support
- Replaced Flar2's S2W/DT2W by showp1984's DT2W
- Various F2FS changes from arter97 and Jaegeuk Kim
- Various backported drivers from arter97
- Updated Intelli-Plug
- Cleaned up base and bumped back to latest 3.4.y (3.4.107 atm)
- Enabled back kernel mode NEON
- Removed PIE bypass patch from Aroma
- Added Motorola's Qualcomm optimized memutils
- Added BFQ v7r7 ioshed
- Updated Intelliactive governor
- Fstab patching changes to fix boot on some non-standard roms
- Updated Random
- Updated toolchain to Linaro GCC 5.1.0 with LTO support
- Added LTO optimizations
19/04/2015 - r330 :
After breaking my partitions while attempting to improve F2FS mounting time, I was forced to format everything. After my backup restoration and system reinstallation, r327 F2FS implementation is now booting faster than EXT4 on my tab (with mounting times of ~5sec versus 30+ before). So I've then decided to revert the planned F2FS changes for r330 (which made it 1sec faster before formatting, but much slower after) as it didn't make sense. If F2FS mounting time is bothering you, fully formatting your partitions and restoring your data will give you a nice performance reward in return.
- Added flush_merge to F2FS mount options for faster flushing
- Added "transparent compression" support (CM sync)
- Added back optimized ARM RWSEM algorithm
- Enabled back unaligned memory access
- Switched to SIO ioshed (from ROW) at boot time as well as others small tweaks for possible further boot time improvements and smaller file size
16/04/2015 - r327 :
- Merged with android-5.1.0_r0.10 changes
- Updated F2FS implementation using Motorola's sources
- Cleaned up permissive ramdisk patches (fixed related SODs with it enabled)
- Introducing "restore" builds. You can now update your Glitch setup without Aroma using these builds. Your settings will be restored from the SDcard backup made by a previous Glitch installation, so if you don't have a "glitch-settings.conf" file in the root of your SDcard, please use a full build first to generate it ! The "full" builds are using Aroma as before.
- Updated toolchain to Cortex A15 optimized Linaro GCC 4.9.3-2015.03
07/03/2015 - r320 :
THIS UPDATE WILL NEED YOU TO REINSTALL YOUR ROM AND TO MAKE A FULL INSTALLATION OF THE KERNEL IF YOU'RE COMING FROM A PREVIOUS GLITCH RELEASE
- Updated F2FS implementation and bumped to latest
- Various scheduler optimizations - Better hardware use means potentially lower max OC !
- Improved boot times (At least with EXT4. F2FS mounting time feels a bit longer with the updated F2FS implementation)
- Reverted Slimbus OC as some users got issues with it
- Removed some ramdisk mods interfering with permissions
- F2FS/EXT4 detection script rewrite to preserve rom's fstab structure
- Added another permissive switch to disable SELinux enforcing (it will be enabled if you tick the permissive patch in aroma)
- Removed wifi patch from Aroma as it's now useless with lollipop
- Added some security patches from CM source
- CM kernel rebased on Glitch AOSP (again) - Looks good after a few days of intensive use
- A few little glitchy tweaks
- Updated toolchain to Cortex A15 optimized Linaro GCC 4.9.3-2015.02
16/01/2015 - r307 :
- Disable wake gestures by default
- Fix for a little color tweaking bug
- Updated CAF variant for CM12 support & sync with Glitch AOSP r307
Note : r307-CM is NOT compatible with CM11. It must be used with CM12 only.
12/12/2014 - r306 :
- Added vmalloc setting to command line to fix some video playback issues. Thanks to @szale9001 for pointing this out !
16/11/2014 - r303 :
- Added Chainfire's partial root ramdisk patch by default
- Added cernekee's PIE patch to Aroma (allows third party native executables to run, lowering security. Fixes various apps)
- Added SELinux permissive + sepolicy ramdisk patch to Aroma (enables full root access but lowers security. Fixes various apps)
15/11/2014 - r300 :
- Updated AOSP kernel with lollipop-release - BREAKS COMPATIBILITY WITH 4.4.x due to GPU driver changes !
- Removed interactive GPU governor
- Merged GPU patches from codeaurora & franciscofranco for better responsiveness and battery life
- Cleanups
26/09/2014 - r226-disabledAVS :
- r226 variant with disabled AVS for users with recurrent instability issues. Higher power consumption than standard build when used without uV.
Follow up to this post : http://forum.xda-developers.com/showpost.php?p=55566837&postcount=1943
22/09/2014 - r226 :
- Added experimental support for Kali Pwn Pad (as it was requested by some - Thanks for the list Flar2 )
- Disabled compaction (a little higher RAM consumption for higher performances - Doesn't seem to affect multi-tasking in a negative way)
- Disabled MSM hardware adaptive voltage scaling (should fix the last remnants of SoDs/RR happening for some even on other kernels - May lead to higher power consumption) I will make a test build with it disabled for who wants to try in the next days
- Updated Faux Sound to 3.6
- Enabled more TCP congestion-avoidance algorithms
- Enabled NFS support
- Moved exfat to built-in instead of module
- Added black magic
17/09/2014 - r223 :
- Better hotplug driver settings in 99glitchsetup script / Fix Qualcomm MPDEC activation
- Lowered "Glitchy" L2/bus settings to make it usable by more users
- Enabled various compiler optimizations (like some GCC graphite optimizations)
- Updated toolchain to Cortex-A15 optimized Linaro 4.9.2 2014.09
- Echo touch firmware version to logfile (/data/local/tmp/glitch-kernel.log)
10/09/2014 - r220 :
AOSP kernel only (CAF kernel will follow as soon as possible) :
- Rebase using latest Google source (fixing various bugs like SoD, random shutdown, slowdowns etc.) and staying on 3.4.0 base for now to prevent issues til I'm able to fix them all with latest Linux upstream
- Aroma Installer rework for less pages on fresh installation mode, similar to Flar2's presentation
- Added new options to Aroma installer
- Updated Flar2's S2W/DT2W system, enabling gesture support
- Replaced Showp1984's MPDecision by Fluxi's MSM Hotplug driver - new default
- Updated Faux123's Intelliplug hotplug driver as well as intellidemand & Intelliactive governors
- Updated/fixed Smartmax and Smartmax EPS (extreme power saving) governors
- Updated FauxSound
- Updated Flar2's msm_sleeper
- Added a backlight dimmer function
- Cleaned up/removed a vast amount of old patches
- Added release number to internal kernel naming so you know what version you're on
- Added a wlan firmware override setting in Aroma. This is basically the same as using 4.4.4 PRIMAtor to enable 4.4.3 or lower support or to fix wifi on a few roms that are using older wifi blobs
- Slight tweaking here and there
- Removed kernel-based NEON support - Needs more testing
- Switched to LZ4 kernel compression - Higher kernel size but faster boot times
- Updated toolchain to Cortex-A15 optimized Linaro 4.9.2 2014.08
05/07/2014 - r151 :
AOSP kernel only :
- Base update from Linux 3.4.86 to 3.4.96
- Removed some unnecessary Aroma pages for faster navigation
- Removed Qualcomm-Optimized Dalvik/Bionic from Aroma to prevent users from softbricks when used on incompatible ROM
- Added F2FS support
- Added F2FS partition detection script to modify ramdisk accordingly at flash time. You will need to launch Aroma installer each time you change FS on supported partitions (DATA, CACHE & SYSTEM) to refresh the ramdisk configuration (you can restore your glitch settings to do that btw, no need to clean install). You can use all of them as F2FS, or just one, you decide.
- Enabled Intelliactive governor
- Added CTCaer's patch to restore forced TS firmware update sysfs
05/06/2014 - r147 :
AOSP kernel only :
- Merged with 4.4.3
- Base update from Linux 3.4.82 to 3.4.86
- Switch to Cortex-A15 optimized Linaro 4.9.1 toolchain
25/02/2014 - r142 :
- Base update from Linux 3.4.79 to 3.4.82
- Added 81 MHz CPU frequency
- Updated ondemand governor
- Switch to Cortex-A15 optimized Linaro 4.8.3 toolchain
- Disable input-boost by default in Aroma
07/02/2014 - r140 :
- Update to Linux 3.4.79
- Switch to XZ compression
- Add kernel mode NEON support as well as NEON accelerated AES & XOR implementations
- Fix CPU load miscalculation
- jbd2 and ext4 optimizations
- Add max screen off frequency support - Thanks to Flar2 (if disabled in Aroma, changing frequency in apps won't have any effect)
- Add UKSM 0.1.2.2 support
- Add dynamic management of dirty page writebacks
- Enable Wiimote HID support
- Enable USB printer support
- Bugfixes
Aroma installer overhaul :
- Reworked installation process to be clearer and more customizable
- Added an automatic backup of your settings to the root of your internal SDcard
- Added a restoration mode to get your settings from internal SDcard backup back on any rom (cross-compatible with Glitch kernel variants)
- Renamed /system/etc/settings.conf to glitch-settings.conf to make it more obviously glitchy
- Removed the need to set CPU OC, L2/cache OC and auto-uV again when keeping previous settings (now reading it from your settings at flash time. Note : editing this part in /system/etc/glitch-settings.conf requires a reflash using the "already glitched" option)
- Added Qualcomm optimized Dalvik/Bionic libraries into the installer (bionic only on CM variant) so you can install/restore them with the kernel
- Added I/O scheduler, CPU governor, read-ahead buffer size, fast charge, max screen off frequency and maximum multi-core power savings to available settings
- Fixed how the min CPU clock is applied to make it more robust and work better with governors
- Fixed how the min CPU freq uV is applied to make it work independently of the min freq (by subtracting the uV amount to the original voltage instead of forcing plain values) - Also, make it capable of setting uV for all freqs for future use.
- Changed the auto-uV menu to reflect the internal changes
- Fixed some permissions issues
- Added hotplug driver check so it's possible to restore it as well from settings without interference
- Change theme
25/01/2014 - r132 :
Performance and stability improvements :
- Enhanced memory management
- Lower CPU overhead
- Improved I/O speed in many cases
- Improved ondemand governor behavior
- Fix a memory leak
- Fix some msm_bus bugs
- Fix a false error report in Aroma log
CM kernel only :
- Fixed the "black caterpillar" bug
- Improved GPU performance consistency
23/01/2014 - r130 :
- Faux123's LCD color control driver updated to Flo version (thanks to him to make it opensource), adding gamma control. (You'll need FauxClock to tweak it - color is still available from TricksterMod)
- Some GPU driver related bugfixes
- Implemented LoUIS API for cache maintenance operations
- Update base to Linux 3.4.77
- Revert some CAF updates (fixes some L2 corruption that could lead to random reboots / black screens)
- Battery life improvements
- Some cleaning
CM kernel only :
- Fixed color control
- Fixed random heavy GPU performance drop
- Changed memory allocation to be in line with CM
- Changed naming in Aroma to differentiate from "pure" AOSP
Older changelogs are available here
Looks like a nice kernel that will really show what this device can do
Sent from my Nexus 4 using Tapatalk 4
Thanks.
That's what I'm trying to make. And I *think* (may be wrong though) I'm the only one yet using a fully working GPU OC implementation on flo kernel. It's an adaptation of Galaxy S IV's (i9505) GPU OC code from Team Hydra.
It seems 627 MHz is around the max possible with stock voltage, probably even 600 MHz for many. I'll see what it can do with a bit more juice.
Other things to do : add more frequency steps for the CPU, lock the default freq, and make the L2/bus speed configurable.
After that I think we'll be able to push the thing to the limits if we want to.
Thanks for your hard work I'm going to try it on pacman ROM I'll let you know how it goes
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thank you, I'm curious to know what results you'll get
Awesome so far .WOW
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
I wanna show u my settings, I use trickster, so sound and faux kernel app to get the results I need was going to show you pictures but all the sudden XDA premium has no picture button I'm a little lost their. Touch responses phenomenal and just like faux kernel the sound is this did really well I can finally listened stock sound sucks on this product even know what has supposedly way better speakers, thanks to people like you I can actually hear the videos I watch without headphones now. Thank you very much I've been using it for about 5 minutes swimming around on everything and everything smooth as hell
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 12:21 AM ---------- Previous post was at 12:20 AM ----------
Add me on gtalk. [email protected]
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
I'm kinda pissed,paid XDA apk all of a sudden has no way to show pictures. Argggg
Sent from my Nexus 7 using XDA Premium 4 mobile app
The problem exists on the free app as well ^^
Try scrolling up and down away from the images and back on them, it'll eventually show up at some point.
Thanks for your work. I'll give this kernel a try.
Coming from N4 motley kernel I'll love to use init.d scripts to set up color "calibration", sleep states, etc. What do you think about implementing / documenting such features for your kernel?
Otherwise, let me see if I need something. Hm, what about USB OTG and ntfs/f2fs support?
USB OTG is working out of the box. NTFS/F2FS support isn't. I'll look into adding them =)
Your idea is nice, I'll think about it.
Thanks =)
Do you plan on adding Faux's color mod? I will give this kernel a shot and report back.
cyberprodigy said:
Do you plan on adding Faux's color mod? I will give this kernel a shot and report back.
Click to expand...
Click to collapse
When there will be some source, yeah why not =)
Tk-Glitch said:
When there will be some source, yeah why not =)
Click to expand...
Click to collapse
I am running the kernel right now. All I can say is "wow".
You did a fantastic job cherry-picking the best features from various kernels. I notice a slight increase in smoothness compared to Faux's kernel plus D2W and all the other great features you added so I think this may be my new main kernel.
I will use it over the next few days and report any issues I find and how the stability is. Thanks a lot for your work.
Edit: Also, I am running CleanROM and everything seems fine.
Thank you, so it may work with any rom then ! Good to know CM didn't break too much stuff leaving AOSP base.
sleep to wake, doubletap to wake disabled by default? don´t need it xD
need a fast stable kernel and especially want to disable fsynch. if u run a stable rom it justs takes useless power xD
i´m pretty new to the nexus7 like the most of us . is that kernel stable?
atm i´m using faux´s, also used franco. i dunno, but on franco´s i couldnt change gpu govenor and the 3dmark benchmark was about 3000points, stock is about 6000-7000. pretty strange.
i am a pretty minimalistic user, want best batterylife/performance ratio. only using psx, best rom for me
i think i´ll try that kernel
edit: what does "Snake Charmer" do?
edit2: read s2w stuff enabled by default, can it be disabled via trickster?
My N7 is running great with your kernel. Let's see what about perfomance and stability in two or three days. After checking and playing with trickster I miss a kind of dynamic fsync and a color calibration interface - compared to N4 m+ (motley) kernel.
Perhaps you can implement some upstream changes / patches directly from CAF or newer kernels.
It would be nice if you post some information about L2 speed hack, etc. So that everyone can see what this hacks do.
Which file are we supposed to use, they are all dated 20130919. I'm guessing the. 904.
airmaxx23 said:
Which file are we supposed to use, they are all dated 20130919. I'm guessing the. 904.
Click to expand...
Click to collapse
CM10.2-flo-Glitch-20130919.0904
2013 /09 /19/09:04
Year/Month/Day/time
dunno if latest point is time in this case when you compare it to upload date. but yes it seems to be latest. upload time and build date can be different, so i think it´s the time.
L-ViZ said:
CM10.2-flo-Glitch-20130919.0904
2013 /09 /19/09:04
Year/Month/Day/time
dunno if latest point is time in this case when you compare it to upload date. but yes it seems to be latest. upload time and build date can be different, so i think it´s the time.
Click to expand...
Click to collapse
Probably when it was compiled.
cyberprodigy said:
Probably when it was compiled.
Click to expand...
Click to collapse
Just a heads up for those who want to disable swipe2wake or doubletap2wake, you can turn them off with the Trickster app but I did not find a setting in the FauxClock app.

[KERNEL][UNOFFICIAL][LINARO/UBER]DorimanX KK 4.4.4

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

[KERNEL][UNOFFICIAL][LINARO]DorimanX JB 4.1.X - 4.3.X

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

[Kernel][9.0] Argon kernel v16.1

Argon kernel, for Android 8.1 & 9.0 ROM's (bacon).
Disclaimer:
use this kernel at your own risk. Flashing it without any knowledge of what you're doing may brick your device. I'm not responsible for any software/hardware damage.
Argon v11 is the last version for Oreo! Starting from v12 only Pie is supported.
Changelog:
v16.1 (August 11th)
support for OTG Y cables
minor bug fixes and security patches
Previous releases:
v16 (August 2nd)
kernel code base synced with LineageOS
lots of misc. bug fixes and small improvements
sdfat driver now replaces both vfat and exfat
some f2fs backports
v14 (April 24th)
built with the newest GCC toolchain for ARM
dynamic management of dirty page writebacks
some useless drivers have been removed (this might give us a few additional MB's of RAM)
a couple of improvements for the random number generator driver
IRQ threading is enabled by default (as suggested by Con Kolivas)
v13 (March 31st)
memory bandwidth overclock
lots of small updates and improvements (mainly for the assembly memory routines)
a few updates for the impulse CPU governor
new TCP congestion control algorithm: 'ascarex'
v12 (March 10th)
official Pie support (LineageOS 16 & Lineage-based ROMs)
small bug fixes and misc. tweaks
a few updates for the "impulse" CPU gov
memory management backports from Linux 3.8
lighter kernel (some debugging options have been turned off)
v11 (January 27th)
built with the newest ARM toolchain
power-efficient workqueues have been implemented in a couple of places
minor source updates & fixes
DDR bandwidth boost has been fixed
important updates for Sultan's CPU boost driver
v10.2 (January 19th)
synced with our LineageOS kernel (mainly bug fixes and security patches)
v10.1 (January 12th)
some source updates and bug fixes
v10 (December 29th)
built with the latest GCC 8 toolchain by Arm
some debugging options are disabled (this might slightly improve performance)
lots of small bug fixes and source updates
v9 (December 11th)
zzmoove governor updated to the latest version
boosted L2 cache frequencies
Spectrum support
Sultanxda's simple thermal driver (replaces Intellithermal)
miscellaneous kernel updates, backports and fixes
dynamic fsync has been (temporarily?) removed
v8.1 (November 23rd)
lots of kernel source updates & fixes
exFAT/sdFAT support
new CPU governors: intellimm, yankactive, zzmoove and impulse
dynamix fsync (disabled by default)
v8 (November 4th) - diff against v6:
built with GCC 8
old charging drivers (these are stable and work properly for everybody)
several improvements for the audio drivers, the memory management libraries, the CPU boosting driver, f2fs, zram, etc.
latest sdcardfs fixes from Google
Intellithermal (with configurable throttling threshold)
latest security fixes
CPU overclocking (disabled by default)
updated bricked hotplug
UKSM with automatic toggling (wip, it's not fully working as of now)
async fsync for ext4 and f2fs
v7.7 (October 23rd)
rebased on top of v7 + all the extra changes of v7.6
msm_hotplug removed (bricked is the default hotplug)
v7.6 (October 23rd)
completely rebased on top of Argon v6.1 (which seems to be the latest stable release) + the following changes
built with GCC 8.2
MSM hotplug enabled by default
cpu_input_boost improvements
latest sdcardfs updates
several other security fixes and improvements
v7.1, v7.2, v7.3, v7.4, v7.5 (October 10th - 11th - 15th - 16th - 17th)
stability fixes
v7 (October 9th)
msm_hotplug replaces bricked as the default hotplug
optimizations for msm8974 boards
older charging drivers from LineageOS 14.1 (they seem to fix all charging problems)
some more minor tweaks, fixes and optimizations
v6.1 (September 30th)
mpdecision is replaced by bricked hotplug by default
v6 (September 27th)
stability fixes
AIO optimizations reverted (this fixes filesystem errors for ext4 users)
slimbus overclock
several improvements and updates (for the ext4 fs, the LMK and many other drivers)
charging current interface
cpu_input_boost by Sultanxda (it replaces CAF's cpu_boost)
v5 (September 19th)
zram is supported
AIO optimizations & backports
minor tweaks and updates
v4 (September 15th)
Per-process reclaim
minor updates and improvements (including security fixes)
v3 (September 8th)
DDR bandwidth boost on screen unlock
misc. kernel updates, fixes and improvements
v2 (August 31st)
several secuirty fixes and kernel source updates
f2fs driver updates
new CPU hotplug: bricked hotplug
power-efficient workqueues are implemented in more drivers
v1 (August 24th)
based on idprophecy's kernel, thus it should be compatible with any Oreo ROM
built using QUVNTNM-TC, based on GCC 7.3.x
CPU underclocking (268,8 MHz)
several compiler optimizations enabled
sound contol by franciscofranco
lots of miscellaneous fixes and improvements
sysfs interface for Gentle Fair Sleepers and Arch power
power-efficient workqueues
Downloads
Latest version: here.
Argon kernel on MEGA
Argon kernel on AndroidFileHost
Thanks to:
@idprophecy
@dorimanx
@faux123
@Sultanxda
@CertifiedBlyndGuy
@osm0sis
@franciscofranco
@GalaticStryder
@nikhil18
the LineageOS team
and all the other authors of the hundreds of commits in Argon's github repo!
XDA:DevDB Information
Argon kernel for Oneplus One, Kernel for the OnePlus One
Contributors
Tomoms
Source Code: https://github.com/Tomoms/argon_kernel
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 16.1
Stable Release Date: 2019-08-11
Created 2018-08-24
Last Updated 2019-08-11
Reserved
How to set up the charging speed interface in Kernel Adiutor?
First thing, download the attached zip and decompress it. You'll find two .json files in it, place them in your internal storage and open KA. Go in the "Custom controls" tab, tap on the "+" button, choose "Import" and select the first of the files you downloaded, then import the second one too. Done! You can now delete the two files.
Keep in mind that the "0" value means that the standard charging logic will be used, and that the AC charging speed cannot be set to a value lower than 200 mAh, even though the slider allows you to set any value. If you set any value between 1 and 199, the driver will fallback to 200.
working fine with AEX 5.7.
is it compatible with oxygen os blobs or sultan blobs?
Running well for me on AEX 5.7.
antfior93 said:
is it compatible with oxygen os blobs or sultan blobs?
Click to expand...
Click to collapse
Starting from Oreo, all ROMs implement Sultan's camera, thus this kernel only supports Sultan's camera HAL.
New version is available
It's an important updates that brings lots of improvements (mainly "under the hood"), for more info I suggest you to check my Github repo!
Really nice work. Don't want to sound rude or something but is there a chance of getting a Pie build? ?
rolarocka said:
Really nice work. Don't want to sound rude or something but is there a chance of getting a Pie build?
Click to expand...
Click to collapse
Most probably, this kernel already works on Pie
You just need to flash it, then flash the Kernel Permissive Patcher (link - needed to set SELinux to Permissive before booting the OS) and you should be good to go. If you try, let me know the result!
What is the stock setting this kernel comes in? I want to try it but don't want to use root (for now). So I'm wondering what settings are default. Would kinda make this a flash and forget kinda kernel
twowheeler said:
What is the stock setting this kernel comes in? I want to try it but don't want to use root (for now). So I'm wondering what settings are default. Would kinda make this a flash and forget kinda kernel
Click to expand...
Click to collapse
The stock settings are kind of good. Not the best you could get, but close (I'll tweak the default configuration a little more in the future). If you're using idprophecy's ROM you will end up having maple as the default I/O scheduler, while if you're using other ROMs, I'm pretty sure you won't. Anyway, if you flash this kernel, I'm sure you'll benefit from the general improvements I implemented, which do not need any tweak to be enabled.
Works well on following ROMs;
-AOSiP 20180825( Argon v1 )
-TugaPower O25 ( Argon v2 )
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
tamboli007 said:
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
Click to expand...
Click to collapse
I have the same thing on all ROMs based on the LOS core. And this kernel is based, as I understand it, on the LOS core ... For example, with FranoKernel there are no such problems.
tamboli007 said:
Hi i installed it over AEX 5.7 . it works but charging is buggy. Keeps disconnecting and connecting .
Click to expand...
Click to collapse
MrYuraB said:
I have the same thing on all ROMs based on the LOS core. And this kernel is based, as I understand it, on the LOS core ... For example, with FranoKernel there are no such problems.
Click to expand...
Click to collapse
I experience the same issue when using a certain non-original (yet good-quality) cable. The weird thing is that if I charge the phone while it's turned off, it charges perfectly. Anyway, I can try to fix this issue. It shouldn't be difficult. I'll keep you informed.
Good to see you're still contributing for Bacon.
Tomoms said:
I experience the same issue when using a certain non-original (yet good-quality) cable. The weird thing is that if I charge the phone while it's turned off, it charges perfectly. Anyway, I can try to fix this issue. It shouldn't be difficult. I'll keep you informed.
Click to expand...
Click to collapse
Yesterday I tried to send you message, but it is why it is not sent... I agree
I've uploaded a new kernel!
Argon v3 is a small yet important update: it brings DDR bandwidth boost on screen unlock (basically, the RAM bandwidth is boosted when you unlock your phone so that opening an app immediately after waking the device from idle takes less time) and some general fixes & improvements for the kernel. More details are available on Github, as usual
Tomoms said:
I've uploaded a new kernel!
Argon v3 is a small yet important update: it brings DDR bandwidth boost on screen unlock (basically, the RAM bandwidth is boosted when you unlock your phone so that opening an app immediately after waking the device from idle takes less time) and some general fixes & improvements for the kernel. More details are available on Github, as usual
Click to expand...
Click to collapse
I've been loving the Kernel on AEX 5.7, but I've needed to reboot a few times because the screen won't turn on, or the screen has frozen.
Do you think that could be from the default underclock?
@Ruggerxpunk Same issue on my side since V2 version, but I don't have any logs cause I'm not using it at this moment.

Categories

Resources