Related
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.
{
"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.
{
"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"
}
DESCRIPTION
Hey guys, I have started a custom Kernel based on LineageOS sources with 98% CAF. So I would like to share my own performance and usability improvements with minimal feature and enhancements on top. The intention is to have a minimal light-weight kernel that is very fine tuned for the device.
FEATURES
Minimal Kernel with a stripped defconfig base to be more streamlined and have less memory footprint
User space display color calibration (KCAL) with screen calibrated against iPhone 8 Plus, also helps reducing screen retention
Schedutil governor making use of EAS features with updates from Linux 4.4 and 4.12
Up to date with LineageOS sources for maximum compatibility and security bugfixes
Memory and cache subsystem optimizations, you will feel it
Adaptive LMK enabled by default
Transparent Hugepages are enabled
ZRAM/Swap partition is disabled by default
BFQ IO scheduler set by default to avoid slow-downs on task intensive scenarios
No overclocking was chosen to avoid unnecessary heat, optimizations were focused on other different areas
Kernel Samepage Sharing enabled with deferred timer by default to gain some memory usage optimizations, the process sleeps on regular basis and I've profiled it so that there's no battery drains due to it
Simple temperature controls for msm_thermals exposed
Compiled with GCC 6.x optimized toolchain and -O3 plus other hardware specific flags
Undervolted the Adreno 530 GPU voltage rail to keep things cooler
CAF Rebase on major portions of the Kernel has helped lower the memory footprint a lot
ES9218 Quad DAC automatic toggling working inside the kernel for headphone HIFI playback, please read here for details
DOWNLOADS
AnyKernel: Click Here (Or check top of the post, download tab)
(Optional) LineageOS 14.1 Netflix Black Screen Fix : Click Here
(Optional) Updated Adreno Drivers by @BlackSoulxxx : Click Here
SOURCE
V20-Kernel-Gamma GitHub Source
NOTES
Here is a GeekbenchV4 result example : http://browser.geekbench.com/v4/cpu/7618872
These is intended to be used primarily with LineageOS, I have not tested other ROM's
Since LineageOS uses a way newer Bluetooth stack, this Kernel will most likely not work on old ROM's such as ResurrectionRemix
This will not work with LineageOS 15.1, please see the other thread
KNOWN BUGS
When using v1.0.0 will fail to boot if you had Magisk previously installed. Please install something newer if using Magisk.
When using v13.0.0 - v15.x.x infrared remote control will not work.
I would also like to thanks to various people who contribute tremendously such as:
@x86cpu
@EvilHowl
@USA-RedDragon
@savoca
@albinoman887
@emdroidle
@Rashed97
@joshuous
@RenderBroken
and many others!
<< If you like my work here is my hat, please donate! >>
XDA:DevDB Information
Gamma Kernel, Kernel for the LG V20
Contributors
Omar-Avelar
Source Code: https://github.com/oxavelar/V20-Kernel-Gamma
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: 46.0.0
Stable Release Date: 2018-07-11
Created 2017-12-10
Last Updated 2018-10-22
CHANGELOG
46.0.0 - Started msm_irqbalance by default on boot, disabled lp11 and enabled allow mdss phy powerdown during idle screen.
45.0.0 - Smoother memlat ramp and tuned the schedTune DVR cpusets a bit for better performance overall.
44.0.0 - More deep sleep enhancements.
43.0.0 - Update to Oreo TouchScreen firmware and more MDSS PLL merge fixes that help deep sleep.
42.0.0 - Missing MDSS Oreo merges are now in place.
41.0.0 - Added IPA_WS as a default in the wakelock blocker, as well as enabling CONFIG_PM_SLEEP which if missing would in turn cause some ueventd wakeups.
40.0.0 - Disabled CONFIG_RMNET_DATA_DEBUG_PKT. Full fix for USB OTG and added missing slimport drivers. Tweaked the random wakeup values, added some extra cpusets based on Marlin's android-cts-8.0_r8/init.common.rc and fixed some BFQ IO possible hang.
39.0.0 - Disabled CONFIG_RMNET_DATA_DEBUG_PKT. Full fix for USB OTG and added missing slimport drivers.
38.2.0 - Removed LGE's battery manager alarms.
38.1.0 - Fixed potential wireless packet loss.
38.0.0 - Further tweaked the wlan_rx_wake wakelock, migrated the audio and thermal workers to power efficient queues, and added an arm64 prefetching optimization for memcpy.
37.0.0 - Better deep sleep enhancements with the charger infrastructure borrowed from the V30 Kernel Oreo sources.
36.0.0 - Full fix for 6a00000.ssusb wakelocks while keeping fast charging enabled.
34.0.0 - Added boeffla_wl_blocker to tame NETLINK wakelock, this wakelock is caused by IPC between the wireless driver in the Kernel and Android. This was the reason why when on wireless the battery would drain more compared than radio. Also disabled OTG as this keeps the phone from deep-sleeping for now.
33.0.0 - Enabled OTG.
32.0.0 - Fixed a bug from Oreo merge that causes video to go green and crash sometimes. Disabled ZRAM from the compilation rather than AnyKernel patch.
31.0.0 - Merged some V20 Oreo Kernel changes in, as well as some DAC enhancements to prevent popping, better USB PD and QC 2.0/3.0 charging code.
30.0.0 - Oreo Kernel changes in, trying to unify the Kernel to keep support for a little while on 14.1.
29.0.0 - Merged msm idle from Linux 4.4 as well as full EAS 1.4 support from Linux 4.4, reduced the memory subsystem timer ramp values for speedier operation.
27.0.0 - Enabled wifi.supplicant_scan_interval on boot, and disabled IPv4 TCP Timestamps and ICMP responses as well as CCKM fast secure roaming.
26.0.0 - Full EAS 1.4 from Wahoo (Pixel 2XL) backported.
25.0.0 - Updated EAS (schedutil, walt, fair scheduler) to be in sync with Wahoo (Pixel 2XL) latest changes.
24.0.0 - Fixed another performance regression in multi-core scores within schedutil.
23.0.0 - Screen brightness is 50% while booting to reduce heat when it is regenerating cache on boot. v22.1.0 was 25% but this was barely visible if you were rebooting under direct sunlight. So went for the safe value.
22.1.0 - Reduced the screen brightness while booting to reduce the heat of the device during cache wipes.
22.0.0 - WALT and schedutil cpufreq commit fixes backported from RenderBroken.
21.0.0 - The GPU Voltage rail undrervolt is now ~60 mV, do not see any problem and games run way cooler.
20.0.0 - After feedback on frequency utilization/distribution I've put 3 WELT commits that should help alleviate this. And enabled some extra configurations from our wireless driver for better power savings.
19.0.0 - Trimmed around ~40 mV from the GPU voltage rails, and updating the wireless stack to DHD 1.80.13 - 2017.06.22, from us997 V16a.
17.0.0 - Increased the multi-core benchmark scores.
16.1.0 - Reverted the binder to be Nougat only, since Oreo support will be on a separate Kernel anyway. Fixed the Infrared Remote Control support that I had broken, and tuned the memory scaling to be more responsive.
15.0.0 - More audio fixes. This audio CAF merging has fixed the speaker-phone that suddenly stops recording or suddenly stops recieving audio from the phone call in LineageOS. Also have increased the schedutil timer values to be similar to the Pixel 2 XL (Wahoo). And finally have fixed a CONFIG_LGE_PM_LGE_POWER_CLASS_CHARGER_SLEEP problem, so that the charger module now sleeps better and uses less power in idle.
14.0.0 - Updated WALT (Window Assisted Load Tracking) fixes aggregated by RenderBroken. Fixed an audio bug introduced in 13.0.0 where headphone insertion could change the sampling rate of other audio sessions. Changed again the schedutil timer values to favor benchmarks a tiny bit and increased the external SD read-ahead and minimum number of requests so that there is better merging when using slow SD cards while keeping the internal storage device in a low-latency configuration.
13.0.0 - Merged CAF audio upstream changes and enabled transparent hugepages.
12.0.0 - Tuned the memory subsystem frequency scaling parameters further down to focus on batter savings as well as the EAS timers.
11.0.0 - Added cpuidle optimizations to idle more, bumped up the memlatency trigger.
10.2.0 - Reintroduced back QuickCharge 2.0 and QuickCharge 3.0 fast charging support into the Kernel.
10.0.0 - Bumped up the Kernel to version 3.18.71.
9.0.0 - Full arm64 arch CAF update done to the Kernel based on CAF LA.UM.6.5.r1-05300-8x96.0. Added support for H918 variant too.
8.2.0 - Partial update to get the Kernel in a big percent that of CAF LA.UM.6.5.r1-05300-8x96.0, no bugs introduced and using a CAF / LineageOS kernel base. Using the binder interface that works both for Android Oreo and Nougat to be prepared for Lineage15. Also fixed a bug that I had introduced in previous versions related to wireless access point, hence why I had pulled versions 7.x from the server.
4.1.0 - Reintroduced into the LineageOS kernel the partial-update in the panel, to gain some power savings and overall performance feeling when refreshing the panel and screen elements.
4.0.0 - Raised the EAS schedutil timers and the memlat governor threshold to kick in faster. This will bring up the responsiveness to similar levels to HMP even when still using EAS. Brought back KSM after profiling on battery utilization, it doesn't hurt as long as a the timer value is between 4000.
3.0.x - Bugfixes and testing with Magisk compatibility, I think there are no more compatibility problems with Magisk after this, had to remove KSM for testing.
1.0.0 - Initial version, with KCAL, and streamlined defconfig based on cm-14.1 kernel sources and minor commits on top.
Omar-Avelar said:
DESCRIPTION
Hey guys, I have started a custom Kernel based on LineageOS sources to get and share my own performance improvements up and adding minimal feature and enhancements on top. The intention is to have a minimal light-weight kernel that is very fine tuned for the device.
FEATURES
Minimal Kernel with a stripped defconfig base to be more streamlined and have less memory footprint
User space display color calibration (KCAL) with less blue tints by default
Schedutil governor making use of EAS features
Up to date with LineageOS sources for maximum compatibility and security bugfixes
Memory and cache subsystem optimizations, you will feel it
Adaptive LMK enabled by default
ZRAM/Swap partition is disabled by default
BFQ IO scheduler set by default to avoid slow-downs on task intensive scenarios
No overclocking was chosen to avoid unnecessary heat, optimizations were focused on other different areas
Kernel Samepage Sharing enabled with deferred timer by default to gain some memory usage optimizations, the process sleeps on regular basis and I've profiled it so that there's no battery drains due to it
Compiled with GCC 6.x optimized toolchain and -O3 plus other hardware specific flags
Re-introduced stock thermal values and engine for a safer device operation
DOWNLOADS
1) AnyKernel: Click Here (Or check top of the post, download tab)
2) EAS-Project OP3 Prebuilts Flashable : Click Here
3) Thermal Engine Flashable : Click Here
SOURCE
V20-Kernel-Gamma GitHub Source
NOTES
These is intended to be used primarily with LineageOS, I have not tested other ROM's
Please flash all *.zip's mentioned in the download sections for optimal results
KNOWN BUGS
Hopefully none
I would also like to thanks to various people who contribute tremendously such as:
@x86cpu
@EvilHowl
@USA-RedDragon
@savoca
@albinoman887
@emdroidle
@Rashed97
and many others!
<< If you like my work here is my hat, please donate! >>
XDA:DevDB Information
Gamma Kernel, Kernel for the LG V20
Contributors
Omar-Avelar
Source Code:https://github.com/oxavelar/V20-Kernel-Gamma
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: 1.0
Stable Release Date: 2017-12-09
Created 2017-12-10
Last Updated 2017-12-09
Click to expand...
Click to collapse
I don't know how 'in-depth' testing I can do. But I'll be willing to do what I can!
I'll be flashing this soon.
I'm on Desolation ROM, VS995. I'll report back. Thanks for your hard work!
Edit: not necessarily a problem, but it has static on boot.
nightra88 said:
I don't know how 'in-depth' testing I can do. But I'll be willing to do what I can!
I'll be flashing this soon.
I'm on Desolation ROM, VS995. I'll report back. Thanks for your hard work!
Edit: not necessarily a problem, but it has static on boot.
Click to expand...
Click to collapse
Oh, I didn't compile specifically for VS995 so it will have static on boot. Since these two are mostly the same devices I might give u a VS995 Kernel next week with that static gone.
Here are some Geekbench results in case anyone is interested : http://browser.geekbench.com/v4/cpu/5506983
Great to have someone finally building an AOSP kernel!
Any chance you'll be compiling for the H918 sometime in the future? No worries if you aren't. I'm just curious =p
Omar-Avelar said:
Oh, I didn't compile specifically for VS995 so it will have static on boot. Since these two are mostly the same devices I might give u a VS995 Kernel next week with that static gone.
Click to expand...
Click to collapse
That sounds great! I'll look forward to it! But I'm about 12-14hrs in the kernel now, and so far so good! With normal usage.
Have updated Kernel to 1.1.0 version with two minor changes that improve the performance by quite a big. Figured out the OP3 and the Marlin Kernel was using 300 Hz tick timers. But for some reason our Kernel was only using 100 Hz tick's. So two changes in this version.
1. Enable high-res timers for schedulercks
2. arm64: hz: make it configurable
Click to expand...
Click to collapse
Plus I have decided to go on and change the perfd binary again. I was not aware how much of impact this has to EAS and the fluidity, since with EAS the input freq boost in the Kernel is now gone. You can read more about it here : https://github.com/EAS-Project/android_device_voxpopuli in the README.md. I am not yet using 100% of the capabilities of Vox Populi Power HAL but a lot of features from it turned off for now.
NippleSauce said:
Great to have someone finally building an AOSP kernel!
Any chance you'll be compiling for the H918 sometime in the future? No worries if you aren't. I'm just curious =p
Click to expand...
Click to collapse
Most likely yes, but after I polish a few features and once I am 100% happy with the performance
Hmm... Oddly enough if I install I get stuck into a boot loop. Not even a LineageOS boot animation. I am and will continue to use Magisk, even flashed all 3.
x86cpu said:
Hmm... Oddly enough if I install I get stuck into a boot loop. Not even a LineageOS boot animation. I am and will continue to use Magisk, even flashed all 3.
Click to expand...
Click to collapse
Oh shoot... I haven't tested it with Magisk on top myself, I wonder if I removed some thing in the defconfig that Magisk needs... Mmmm, both versions give u that same outcome ? Thx for the report!
Omar-Avelar said:
Oh shoot... I haven't tested it with Magisk on top myself, I wonder if I removed some thing in the defconfig that Magisk needs... Mmmm, both versions give u that same outcome ? Thx for the report!
Click to expand...
Click to collapse
I only tried the latest one. I did not try without Magisk though or the older version, the all 3 reference was all 3 files you had. gamma/vox/thermal.
I noticed in your thermal, that the camera files are the same as Lineage, so you could take those out. I also took out the mixer one as I bumped those VOL up as it was hard to hear on calls without it. If you do find any adjustments that the op3 or marlin did, we might be able to get those into the Lineage msm8996 kernel. Ideally, the commits from op3 in the Lineage tree, then I can cherry pick it to preserve history. I'm all for getting things into Lineage where we can.
Omar-Avelar said:
Oh shoot... I haven't tested it with Magisk on top myself, I wonder if I removed some thing in the defconfig that Magisk needs... Mmmm, both versions give u that same outcome ? Thx for the report!
Click to expand...
Click to collapse
I flashed with Magisk, on the first version, and everything is going fine for me
nightra88 said:
I flashed with Magisk, on the first version, and everything is going fine for me
Click to expand...
Click to collapse
Thanks man, let me re-upload the 2nd version just in case then and will verify the MD5 hash...
Omar-Avelar said:
Thanks man, let me re-upload the 2nd version just in case then and will verify the MD5 hash...
Click to expand...
Click to collapse
No problem! Glad to help.
x86cpu said:
Hmm... Oddly enough if I install I get stuck into a boot loop. Not even a LineageOS boot animation. I am and will continue to use Magisk, even flashed all 3.
Click to expand...
Click to collapse
So I got home to try just in case @x86cpu and I was able to flash Magisk-v14.5(1456).zip after all of the 3 files had been flashed on my system and it booted fine.... so I've re-uploaded the Kernel as v1.1.1 in the downloads section just in case...
Wiped /system (as I had su from LineageOS flashed before)
Flashed system with lineage-us996-*.zip
Flashed OpenGapps
Flashed perfd update (2nd of my zips)
Flashed the 'hotfixes' (3rd of my zips)
Flashed gamma-kernel (1st zip)
Flashed Magisk-v14.5(1456).zip
Hit reboot
If you can let me know if the v1.1.1 version works on your side then I can blame the bad upload. If not I can do more experiments to see if there is some other condition that depends on the order of flashing with my AnyKernel approach... and then I can try and replicate and fix it , please do let me know...
UPDATE: I am able to hit the failure now @x86cpu... let me see if AnyKernel needs any update or something to allow to re-install the Kernel if Magisk is already pre-installed. In order to hit it I had to:
Wiped /system (as I had su from LineageOS flashed before)
Flashed system with lineage-us996-*.zip
Flashed OpenGapps
Flashed perfd update (2nd of my zips)
Flashed the 'hotfixes' (3rd of my zips)
Flashed Magisk-v14.5(1456).zip
Flashed gamma-kernel (1st zip)
Hit reboot
Essentially flashing the Kernel last... which might be a common thing that could happen, let me polish that up...
I've uploaded flashable-us996-gamma-kernel-v1.2.0.zip now with an updated AnyKernel script that seems to now be working even with Magisk installed previously. Thanks to @x86cpu for reporting this bug.
U
Omar-Avelar said:
So I got home to try just in case @x86cpu and I was able to flash Magisk-v14.5(1456).zip after all of the 3 files had been flashed on my system and it booted fine.... so I've re-uploaded the Kernel as v1.1.1 in the downloads section just in case...
Wiped /system (as I had su from LineageOS flashed before)
Flashed OpenGapps
Flashed the 'hotfixes' (3rd of my zips)
Flashed Magisk-v14.5(1456).zip
Wiped /system (as I had su from LineageOS flashed before)
Flashed OpenGapps
Flashed the 'hotfixes' (3rd of my zips)
Flashed gamma-kernel (1st zip)
Hit reboot
Essentially flashing the Kernel last... which might be a common thing that could happen, let me polish that up...
Click to expand...
Click to collapse
I just installed the v1.1.1 before the fix. So. In other words before I saw this update, I just flashed it with no wiping, Desolation rom, and it booted fine, it's just now, in Magisk I can't pass cts or basic integrity. I'll try your updated method and see if that fixes the problem.
Edit: did the above steps, minus wiping twice and flashing the hot fixes twice. Rebooted it. And now I can successfully pass safetynet on the latest gamma kernel!
Edit#2: false hope, my apologies, safetynet apparently isn't passed.
Edit#3: okay. I had a blonde moment. I forgot to wipe my dalvik. It passes now.
What do the HAL's do? And what order should I flash the zips?
Obamaloominaty said:
What do the HAL's do? And what order should I flash the zips?
Click to expand...
Click to collapse
The order doesn't matter as they are independent. And I would suggest you read about the EAS perfd HAL in here : README.md
However keep in mind that I haven't implemented all of the VoxPopuli features from the HAL in the AnyKernel as it needs some SELInux permissions updates (which I can do later on). But without all of those enhancements it will behave like the Pixel HAL.
DxT Kernel
* Your warranty is now void.
* I am not responsible for bricked devices, strained relationships,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration.."
This kernel is only for Payton
Features
1. Built with Clang 13 + Polly optimize
2. Merge Linux kernel and driver as soon as possible
3. DxT is CAF based and uptodate with latest tag
4. Fixed all compile-time warnings
Other Features
1. kcal, sound gain control
2. CPU OC using some sdm660 frequencies ,[Little cores = 2.0ghz ,Big cores = 2.5ghz]
3. Added & Updated LZ4 for ZRAM (Enabled by Default)
4. AnyKernel3 Installer Script
5.Compiled With Latest Proton CLANG 12
6. Exfat driver comes from arter97
7. Available I/O scheduler: bfq, cfq(default), deadline
8. Available TCP congestion algorithm: westwood(default)
9. Merge some optimization commits from Sultan
10. Kernel-level cpusets parameter optimization, optimize CPU core calls
11. Latest Wireguard driver
12. Adreno GPU boost
13. Some other visible and invisible optimizations...
Due to different moto action implementation on different roms i made two versions
* normal version support roms like superior,pixel experience,msm-xtended,ancient
* L version support roms like LOS,crdroid,havoc,derpest
DOWNLOAD
DxT v4.2
DxT v4.2-L
DxT UC
OTA SUPPORT:
# DxT Kernel FKM Manager Support
This kernel has FKM Manager support for autoflash updates directly from the app.For this to work you must import the configuration link in the section "Flasher" of the app:
Then you must select the option: "Import a kernel download configuration"
This are the URLs for the two versions,just copy,paste and save. (You must add and save one first and if you want both versions available add the other after)
DxT = https://raw.githubusercontent.com/DhineshCool/Dxt_downloads/new/dxt.json
DxT-L = https://raw.githubusercontent.com/DhineshCool/Dxt_downloads/new/dxt-L.json
Telegram Group
Use the app EXKM, FK Manager, kernel adiutor or smartpack to tweak the kernel!
special thanks to all contributators
attack11, nathanchance , joshuous , akhilnarang , flar2 , kerneltoast , GuaiYiHu , Pzqqt
if u like my works u can donate
[email protected] - upi
https://www.paypal.me/cool585 -paypal
XDA:DevDB Information
DxT kernel, Kernel for the Moto X4
Contributors
dhinesh_cool
Source Code: https://github.com/DhineshCool/Dxt_payton
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v4.2
Created 2020-06-22
Last Updated 2021-07-25
## DxT Changelogs ##
v4.2
*upstreamed to v4.276
*merged latest caf tags
*latest proton clang
*improved cpu frequency
*clean up rarely working freq
*improved cpu idle
*fixed battery drain on idle
*removed prlmk to prevent twrp crash
*more code cleanup fro stability
V4.1
*Fixed battery drain issue
*Fixed some bugs
v4.0
*upstreamed to v4.270
*latest proton clang
*fully rebase
*rework thermal engine
*rework ram-managment
*lot see my git
ota json has been changed
DxT = https://raw.githubusercontent.com/DhineshCool/Dxt_downloads/new/dxt.json
DxT-L = https://raw.githubusercontent.com/DhineshCool/Dxt_downloads/new/dxt-L.json
v3.6
*upstreamed to v4.258
*latest proton clang
*added anxiety io for faster app opening
*added z3fold from sony
*improved zram performance
*updated ashmem
*fixed some thermal sensor spamming on logcat
*more fixes see my git
v3.5
*upstreamed to v4.253
*Merged tag LA.UM.9.2.r1-02000-SDMxx0.0
*latest proton clang
*Backport new vmalloc for "large performance benefits"
*selinux: Allow audit to be disabled
* page_alloc: double zone's batchsize
*nuke more debloat
*more optimation for better smoothness
now ui will be more smooth
*Updated wireguard to "1.0.20210124"
v3.4
*DxT rebased to caf base
*upstreamed to v4.251
*added persist bug fix
*latest proton clang
*Gpu added 710 freq
*more ion fixes from sultan
*Enable CONFIG_HID_NINTENDO
*Updated wireguard to "1.0.20201221"
v3.3
New Year Release
*upstreamed to v4.248
*latest proton clang
*Gpu oc to 800mhz
*no thermal throttling on gpu
*more ion fixes from sultan
*Updated wireguard to "1.0.20201221"
note uc version pushes to bimonthly release
v3.2
*upstreamed to v4.247
*fix payload calculation
*usb: Add Drivedroid Support
*power: msm-core: Fix mutex not getting unlocked in error path
*cpufreq: stats: optimize proc files
*mm: speed up mremap by 20x on large regions
*work on cpu idle
*lot of work done see my git
(https://github.com/DhineshCool/Dxt_payton)
*latest proton clang
**** rework on uc version -it now fully stable no thermal throttling ****
*for the people on xda i released v3.1 on my telegram group , i forget to update on xda
that why directly releasing v3.2
v3.1
*upstream to v4.244
v3.0
*upstreamed to v4.240
*clean up codes
*fixed build warning
*added additional safetynet patch
*rework on thermals
*work on cpu idle
*work on ram managment
*lot of work done see my git
(https://github.com/DhineshCool/Dxt_payton)
*latest proton clan
v2.8
*upstreamed to v4.239
*power: bcl: Improve power efficiency of the workqueue
*used latest proton clang (20201010)
v2.7
*upstreamed to v4.238
*qcacld-3.0: Disable Wifi SAE by default
*optimizations for block
*used latest proton clang (20200930)
v2.6
*upstreamed to v4.237
*New OC for payton (thnx to seba3567)
*Remove some scheduler
*ipc logging disabled
*changes on debugfs
*increase thermal trip points
*optimize gpu
*used latest proton clang (20200923)
Reserved
Much appreciated! I've been wanting a custom kernel for Moto x4!
Running on HavocOS 3.6, seemingly no issues. Definitely feels snappier than the base kernel. Will update after a couple days use.
Thanks again!
Installation instructions?
Zohaibzx said:
Installation instructions?
Click to expand...
Click to collapse
Method 1: Download and install the zip for your rom from the download links, then flash in twrp
Method 2: Use Franco Kernel Manager (requires root) and configure it to use the proper link listed under OTA support. FKM will read any new releases in Dhinesh's github, and update the kernel without a need to flash in recovery.
Hope that helps!
I tried to flash it in twrp but after flashing the phone just reboots to recovery instead of system. I'm using pixel experience and have used the proper variant of your kernel.
I've tried to flash this (Using FKM Manager), to both of my X4's, one is running Havoc 9, and one is running the latest version of Havoc 10.
Both gave the same error message: "Unsupported device. Aborting..."
Flashed using fkm in pixel rom. No issues
Is there anyway to increase the minimum cpu frequency? Whenever i do with fkm it goes back to 300mhz. 300mhz seems too low causing some stuttering while scrolling and in some system animations
helo123 said:
Is there anyway to increase the minimum cpu frequency? Whenever i do with fkm it goes back to 300mhz. 300mhz seems too low causing some stuttering while scrolling and in some system animations
Click to expand...
Click to collapse
U can manually set minimum freq
Zohaibzx said:
I tried to flash it in twrp but after flashing the phone just reboots to recovery instead of system. I'm using pixel experience and have used the proper variant of your kernel.
Click to expand...
Click to collapse
Some people had this issue on pe
I don't know why this happening I will try to fix
Tell your variant with ram
dhinesh_cool said:
U can manually set minimum freq
Click to expand...
Click to collapse
I tried many apps to change minimum frequency. It still goes back to 300.. only i can change the maximum frequency now
RBJ26 said:
I've tried to flash this (Using FKM Manager), to both of my X4's, one is running Havoc 9, and one is running the latest version of Havoc 10.
Both gave the same error message: "Unsupported device. Aborting..."
Click to expand...
Click to collapse
U need clean flash latest havoc then install
helo123 said:
I tried many apps to change minimum frequency. It still goes back to 300.. only i can change the maximum frequency now
Click to expand...
Click to collapse
Weird I will check ,but lag is due to ram management
I added some tweaks for ram management that was causing lag after sometime for 3gb variant I was aware of this issue I will fix soon
dhinesh_cool said:
Some people had this issue on pe
I don't know why this happening I will try to fix
Tell your variant with ram
Click to expand...
Click to collapse
1900-7 Dual Sim 3GB 32GB
dhinesh_cool said:
U need clean flash latest havoc then install
Click to expand...
Click to collapse
Sorry, I should have given more info.
I should have said I had two clean installs of Havoc. On one phone is with Havoc 2.7 (which you say is not supported - OK).
The other phone is a clean install of Havoc 3.6
I have not tried to flash through TWRP would this help? or could there be another issue with my phone.
ETA: I think I understand now. Do you mean without root, etc?
Thanks,
R
RBJ26 said:
Sorry, I should have given more info.
I should have said I had two clean installs of Havoc. On one phone is with Havoc 2.7 (which you say is not supported - OK).
The other phone is a clean install of Havoc 3.6
I have not tried to flash through TWRP would this help? or could there be another issue with my phone.
ETA: I think I understand now. Do you mean without root, etc?
Thanks,
R
Click to expand...
Click to collapse
Flash through twrp
Or u need root to flash via fk manager
dhinesh_cool said:
Flash through twrp
Or u need root to flash via fk manager
Click to expand...
Click to collapse
Flashing via TWRP worked fine, Thanks!
For some reason flashing from FKM would not work, even with root.
RBJ26 said:
Flashing via TWRP worked fine, Thanks!
For some reason flashing from FKM would not work, even with root.
Click to expand...
Click to collapse
On FKM u need to give proper permission to storage then on flasher u need select storage and give access
Hello!
I want to introduce my first custom kernel for the SM8250 family of Snapdragons. This is based of latest Samsung OneUI 2.5 Sources and I cherry-picked commits to make improvements to the stock base. I'm not a developer, but i really like to port stuff over .
I will try to have this Kernel updated as soon as new source tarballs are drop by Samsung. If you want to request for specific features, let me know and i'll do my best to bring them over.
Special Features:
Changelog is in post #2
How to Install:
First, make sure you are in any OneUI 2.5 (BTH* or BTI*) ROM and have TWRP on the device. Make sure you take a backup of your current boot partition in twrp, now install either the boot.img (extract from the tar file) or use ODIN to flash in Dowload mode. Please make sure to read Post #3 regarding issues with the current OS Patch Level. Images from 1.5.0 onwards are pre-rooted but you will probably need to update magisk either manually or by flashing latest magisk.zip file.
Keep in mind the following table to determine your phone model:
x1q = S20 - G981X
y2q = S20+ - G986X
z3q = S20U - G988X
r8q = S20 FE - G781B
c1q = Note 20 - N981X
c2q = Note 20U - N986X
IMPORTANT NOTE: It seems some users need to flash a vbmeta image file provided by Google in order to boot and user the Custom Kernel. If you find yourself in a situation were you are not able to boot, please flash the attached vbmeta img along with the Kernel and if still bootlooping share the last_kmsg to determine what's driving the issue.
Download:
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
You can use THIS link to get the latest builds. These and other downloads can also be found in the Telegram Group.
Sources for Q? https://github.com/Jimbo77/JimboK_common_sm8250
Sources for R? https://github.com/Jimbo77/Jimbok_common_sm8250-R
Join the Telegram Group for additional discussions and downloads - HERE
Special thanks to:
Afaneh
Ianmcd
0smosis
flar2
Lord Boeffla
jesec
elliwigy
pappasmurf
For their work and dedication to development!
Changelog or features or whatever
04.10.21 - JimboK-R-2.6.0
Upstreamed to .185
04.05.21 - JimboK-R-2.5.0[/B]
Sync code to add missing changes in upstreamed branch
Reworked the DEVFREQ_BOOST driver
Tweaked SchedHorizon default freqs
Tweaked DEVFREQ_BOOST defaults in defconfig
03.31.21 - JimboK-R-2.4.0[/B]
Upstreamed to Stable Linux 4.19.184
Built with cortex-a55 specific optimizations
removed facebook process from 'kill-in-the-background' mod. This was affecting the user experience (for those that use Facebook a lot, like my wife lol)
02.24.21 - JimboK-R-2.3.0[/B]
Upstreamed to Stable Linux 4.19.176
Switched from G988U source as base to N986N source drop for OneUI 3.1
Removed a lot of unused configs from defconfig. This resulted in a reduction of Kernel size and will have an impact on the overall performance and resource utilization.
Reworked the DEVFREQ and CPU_INPUT_BOOST drivers
Added and Enabled schedhorizon governor
Imported the option to edit the CPU Frequency table
Performance Governor is default for LITTLE Cluster now
02.03.21 - JimboK-R-2.1.0[/B]
Upstreamed to Stable Linux 4.19.172
Moved to KOR dts to improve on stability for custom DTBO's
Added Flicker-Free or DC Dimming. There are two versions of the Kernel and this will be the only version with Flicker Free. After this, there will not be added since i don't like how it messes the Screen Colors/Performance.
Disabled Bootstats
Enabled MPTCP
01.25.21 - JimboK-R-2.0.0[/B]
Upstreamed to Stable Linux 4.19.169
Disabled several not needed debug Samsung Configs
CPU ASSIST Feature
Disabled ZRAM and SWAP
DTS (dtb and dtbo) updates for all variants to their latest source drops
General CLANG and LLVM optimizations
01.01.21 - JimboK-R-1.8.0
Reworked both DEVFREQ and CPU_INPUT Boost functionalities
finetuned for SM8250 (Samsung) specific frequencies/values
added and enabled Simple Low Memory Killer (SLMK)
added: CIFS, NTFS and ISO9660 FS in-kernel Support
added Wireguard Support
Several 'under the hood' improvements to task/memory management.
12.28.20 - JimboK-R-1.7.0
Added BBR2 TCP Config and made Default
Several updates to NET protocols and BBR2
Added PROC_MAGISK_HIDE_MOUNT
Added a script to fix Shealth, Smart View and set ZRAM parameters.
12.25.20 - JimboK-R-1.6.0
Added Dynamic Fsync
Tweaks for Memory Management
Updated LZ4 compressor
Enabled ZSTD Compressor for ZRAM - Default now
12.21.20 - JimboK-R-1.5.1
Fixed Wifi Calling
12.20.20 - JimboK-R-1.5.0
Fsync On/Off Support
Readahead 0
Slimbus OC
Toggle to enable/disable CRC
Turned off several debug options within the tree
added EAS related commits
12.16.20 - JimboK-R-1.4.0
Added Kcal Color Control Driver
Added KLAPSE Driver
Disabled Gentle Fair Sleepers
Added Boeffla Wakelock Blocker
Disabled AVB Flag for better protector in terms of SafetyNet
Misc fixes and addons to dtb
12.15.20 - JimboK-R-1.3.0
Skipped, no public Release xD
12.13.20 - JimboK-R-1.2.0
Added IO-SCHED drivers like: ZEN, FIOPS, MAPLE etc...
Added DevFreq Boost Driver and tuned based off OP8
Added Adreno Boost Driver
12.12.20 - JimboK-R-1.0.0
Initial Android R (OneUI 3.0) bring up
Source is based off the G988U source drop. This includes all other variant files, i have added support to all previous phones from day one now
Disabled Samsung Security useless stuff (DM Verity for example)
11.01.20 - JimboK-1.6.3
Added a fix to hide Magisk Mount for Isolated Processes. This is a critical leak in MagiskHide that can be exploited by apps trying to determine if the device is rooted. I had an issue with two payment apps that after applying this fix, they work. Not sure if they were finding magisk with this method lol. Read more here https://darvincitech.wordpress.com/2019/11/04/detecting-magisk-hide/
Finally removed the warning upon boot. EdXposed compatibility was not affected by the removal of it.
10.27.20 - JimboK-1.5.0
Rebased to S20 FE source as baseline for all models. This is to ensure support for the S20 FE is added and to keep the most up date source from Samsung
Streamlined even further the 'common' defconfig and updated all other variant defconfigs to make it easier to build individual Kernels.
Removed GPU OC - This is to test drive if performance takes a small hit but battery is gained. I have this as *temp change* consider it a 'test' phase so i will need your feedback on it to see whether if we keep it or not. Also, the OC was causing issues to boot in N20 units and some weird hiccups in the System-UI for my S20U.
Added BBR2 TCP CONG protocol. By far, the best TCP CONG to speed up the network connections overall. Read out more here: http://dl.ifip.org/db/conf/networking/networking2018/2B1-1570416152.pdf
BBR2 is now default TCP CONG for the Kernel. I recommend ya'll to make the switch
Several Upstreams to NET/TCP in order to improve Network Connectivity and Speed.
Kernel comes pre-rooted now (via ramdisk). In the event of a magisk update you will only need to update through Magisk Manager. This is for the sake of simplicity
10.16.20 - JimboK-1.4.0
Removed several DEBUG options from defconfig that should not be present in a Production Kernel
Disabled ZSWAP and VBSWAP (this will create conflict with ZRAM) and ZRAM has proven to be more effective and create less wear than ZSWAP
Disabled LZO, updated LZ4 compression algorithms
Enabled ZSTD Compression, it is recommended to enable this for ZRAM moving forward
Disabled KPERFORM in defconfig
Enabled .gz compression for Kernel. Kernel is now almost 1/3 in size of what it used to be
Added and Enabled HID: NINTENDO SWITCH controllers support
10.13.20 - JimboK-1.3.0
Unified Sources a bit more. Removed the individual defconfigs to have one single plus each variant
for X1Q and Y2Q moved dts sources from CHN OPEN to KOR to keep it in line with main (Z3Q) sources and also for CXQ sources. BTI3 (latest software release) is now used for those models.
Enabled a few drivers inside of Kernel: CDC, NTFS, CIFS and some native gaming devices as well
Disabled DM_VERITY checks. This will help with the booting times
JimboK-1.2.0 and before:
Build with latest LLVM Clang 11
Disabled Samsung Security useless stuff (DM Verity for example)
GPU OC up to 895mhz
Adreno Boost
Boeffla Wakelock Blocker Driver
Disabled ZRAM and moved to ZSWAP and VBSWAP
KCAL Color Control Driver (Up to date)
KLAPSE Driver (check out https://forum.xda-developers.com/an...apse-kernel-level-livedisplay-module-t3907025)
Added IO-SCHED drivers like: ZEN, FIOPS, MAPLE etc...
Latest Wireguard Driver
BBR TCP Congestion algorithm by Default
built-in Kernel Westwood and other modules
SLIMBUS OC to improve the Audio Mods
Several Debug Options removed from driver and all over the Kernel itself
QCACLD-3.0 Support
Dynamic Sync Control
Fsync On/Off Toggle
Several EAS commits for balancing power+efficiency
OS PATCH LEVEL set as 2099-12 (Read post #3 - Mandatory)
OS PATCH LEVEL PROBLEM
This is a modified version of @evdenis post HERE
My Kernel uses an OS Patch Level of 2099-12 to maximize its compatibility among all releases by Samsung across all the supported phones. That's it. No other reason as to why choose that date, now, when you continue using my Kernel update after update there will be no issue, but if you change the kernel to any other (specially stock) chances are that Kernel is using the current month OS PATCH LEVEL which will cause two things:
You will not be able to pass beyond your lockscreen. No matter what you try, it won't let you unlock upon reboot
Your Samsung Account will warn you to log off and log back in but you will not be able to do so
The problem is not in sources. It's due to os_patch_level mismatch with you current kernel. As mentioned JimboK Kernel does not uses common security patch date to be in sync with the official samsung firmwares. You can check the default os_patch_level in build.mkbootimg.* files. However, this date can be higher than other kernels use. When you flash a kernel with an earlier patch date on top of the previous one with a higher date, android activates rollback protection mechanism and you face the problems stated earlier. It's impossible to use a "universal" os_patch_level because different users use different custom kernels and different firmwares. JimboK Kernel uses a highest date by default in order to suite most of users.
How can you solve the problem? 6 ways:
You can restore my kernel and the problems will be gone
You can flash the attached zip file. backtothefuture-2099-12.zip, it will make your new Kernel Patch OS Level 2099-12 thus avoiding the issues above. - read more about the zip HERE. You will have to flash this with any new kernel if you ever use mine (unless you do a full wipe as mentioned at the end of this list).
You can check the os_patch_level date of your new kernel here https://cruelkernel.org/tools/bootimg/ and patch the kernel image image to the same date. If your previous kernel is mine (JIMBOK), patch your new Kernel to 2099-12 date.
You can reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin. To fix samsung account login, reinstall the app
You can rebuild JimboK Kernel with os_patch_level that suites you. To do it, you need to change the OS PATCH LEVEL to the desire date when using mkbootimg.
You can do the full wipe during the new Kernel flashing
Update 10.20.20
Updated the zip file to add support for W models.
Update 10.19.20
Updated the zip file to remove Exy devices and focus solely in N20 and S20 Snap line.
Finally kernel for s20 thanks a lot.
Works great!
I've got bootloop with my S20U G9880 after flashing this kernel even with a full wipe
Working
It works on my G9810 Thanks!!!
stszf9124 said:
I've got bootloop with my S20U G9880 after flashing this kernel even with a full wipe
Click to expand...
Click to collapse
Strange I have G988N which is just about the same and I don't have that issue. Did you come from a rooted device? Were you in a custom ROM before?
Can you tell me a bit more of your setup?
Are there any other G9880 users with the same issue?
I have s20+ 5g g986u
Unlocked bl
Flashing twrp
Flashed the kernel
Flashed vmbeta disabler
Flashed magisk
Boot
All ok
Thank you
thank you
my device is running custom Rom and stock kernel, the firmware is BTH6 , last night I installed the latest version of TWRP and format data and flashed the multiple disabler, the device booted , but it got this issue after the kernel was installed even with a full wipe again
has battery life been improved?
can i flash this and then magisk to get root?
Smartphones13 said:
can i flash this and then magisk to get root?
Click to expand...
Click to collapse
Yes, you can do that.
Viet.molet said:
has battery life been improved?
Click to expand...
Click to collapse
I flashed this and did a minor debloat and gained roughly 30 minutes of screen on time.
I also noticed the animation from recents to home screen is slightly snappier.
Could be placebo but I like it.
@jimbo77 what kind of benefits do I get by flashing your Kernel?
chieco said:
@jimbo77 what kind of benefits do I get by flashing your Kernel?
Click to expand...
Click to collapse
Disabled some Samsung Security, you will be able to run edxposed if you are into that. Also a few changes and add-ons, read the op for some of the features added to the Kernel
Works on sm-g9810?
jucin said:
Works on sm-g9810?
Click to expand...
Click to collapse
It should. Although I haven't personally tried since I own a G988N
jimbo77 said:
Yes, you can do that.
Click to expand...
Click to collapse
Hey man, how's it going? Did you do anything special to get kcal working on the kernel? Mental made a kernel for the Note 20 Ultra but said he could not get Kcal working.
Also, even better, would you consider making a common kernel for the Note 20 Ultra Snapdragon? I'd definitely send a donation your way.