[Kernel][Sense 4] crpalmer | August 25, 2013 - HTC Droid DNA

The goal of this kernel is above all stability with the secondary goals of increased performance and increased battery life. I use this phone for several hours a day for work and therefore it must be reliable. I am not focusing on providing a million options for governors, etc. In addition to those main goals of the kernel, I have an additional secondary goal of removing as much HTC code as possible from the kernel.
This is based on the 2.04 kernel source release from HTC with a huge number of modifications. Thanks to faux123, showp, harsh, mdeejay, zarboz and dsb9938 whose kernels I have pulled some commits from.
The unique features of this kernel are:
New init.d scripts to allow some tweaking without needing any 3rd party apps
* See the next post for details.
Replaced HTC's mpdecision with a new custom hot-plug driver that I created:
* This hot-plug driver is more aggressive about bring cores on and off-line to match the load on the system.
* Bringing cores online earlier makes your phone more responsive / smooth.
* Taking cores offline earlier improves battery life.
* It ramps up very quickly on resume to avoid lag.
Replace HTC's thermald with a new custom thermal driver that I created:
* Unlike all other thermal drivers, it uses "trip-points" to let the phone tell the kernel when it is overheating. The other thermal drivers poll every X ms and read the temperature instead.
* By using trip-points, there is 0 battery consumption unless the phone is overheating.
* By using trip-points, there is an instant reaction to temperature changes.
* It's probably nearly impossible to cause thermal shutdown without being in a desert!
Replaced HTC's bluetooth drivers with Code Aurora Forums (CAF) version.
Replaced HTC's lightsensor table with one that is more sensible and that matches what other devices use. If you have custom auto-brightness settings, you'll probably need to tweak them after installing this kernel.
There are many additional changes to boost performance and battery life:
* Linaro -O3 compiled (Linaro 4.8).
* Overclocking from mdeejay's kernel.
* Underclocking to 192MHz.
* I disable tons of HTC debugging crap left enabled and needlessly consuming battery.
* Improvements to the core locking code of the kernel.
* Patches that transform traditional locks into RCU backed data structures.
* CAF version of the ondemand and conservative governors.
* hsic wakelock changes from dsb9938's kernel.
* CAF changes to power management to sleep faster and waste less CPU during suspend.
* Improved code for moving data to/from user-space and manipulating strings within the kernel.
Other features:
* Include all mainline Linux changes to keep up-to-date on bug fixes.
* Voltage control (faux123) to allow user-space under-volting.
* BFQ I/O scheduler.
* CAF lowmemorykiller.
* Force fast charge.
Links
A link to each version is included in the changelog entry. Scroll down to the changelog to download the latest version.
Source (GitHub):
* Kernel source
* Merging of upstream into the stock kernel
* Build tools
Installation Instructions:
If you are S-OFF you can flash the update.zip in recovery.
If you are S-ON, then after you flash the update.zip in recovery then, while still in recovery, you must run
Code:
adb pull /tmp/boot.img
<reboot into bootloader>
fastboot flash boot boot.img
Changelog:
Version 2.0.41: August 25, 2013: Linux 3.4.58, HTC colour "enhancement"
* Merged Linux versions 3.4.53 - 3.4.58
* Added the ability to enable / disable the HTC colour enhancement (this lets you see if you like it or not)
Version 2.0.38: July 7, 2013: Linux 3.4.52
* Linux version 3.4.51 / 52 merged in
* Reverted a small change to the PWM values used for the display (it wasn't giving any value so why change ti)
Version 2.0.34: June 24, 2013: colour enhancement, fixes, debug messages
* Toned done yet more HTC debugging messages
* Enable UTF-8 codepage support for Windows file-systems
* Fix error in HTC's light-sensor calibration table (overflows the 16-bit number they are using)
* Avoid buffer overflow in acdb driver
* Remove HTC's colour enhancement gamma correction (beaups)
Version 2.0.32: June 15, 2013: linux 3.4.49, scheduler & mutex improvements
* Linux 3.4.49
* Three scheduler performance improvements
* Move to more standard and slightly faster mutex implementation
Version 2.0.30: June 8, 2013: linux 3.4.48, small fixes
* Linux 3.4.48
* Fix CVE-2013-2595
* Decrease latency in cpufreq frequency changes
Version 2.0.27: May 26, 2013: init.d governor, 3.4.47
* Ability to specify the cpufreq governor at boot time (see second post).
* Linux 3.4.47
* Remove an annoying HTC debugging message
Version 2.0.26: May 23, 2013: init.d tweaks, 3.4.46, no default undervolting
* Added PVS information to /proc/cpuinfo in case you wanted to knoiw what it is for your phone.
* Linux upstream version 3.4.46
* Improve how I set the CPU frequences to safe levels for boot without having to reset them every time a core is hot-plugged in.
* New init.d scripts for some common tweaks (see post #2).
Version 2.0.23: May 13, 2013: Lightsensor fix, 3.4.45, faster freq. changes:
* Fix an error transcribing the lightsensor ranges into the source.
* Update to Linux 3.4.45
* cpufreq: use a high priority to target new frequencies to allow faster changes under load
Version 2.0.20: May 12, 2013: Lightsensor, 3.4.44, undervolt for "fast":
* Use a new lightsensor table to get a more granular light reading If you have custom auto-brightness settings, you'll probably need to tweak them after installing this kernel.
* Update to Linux 3.4.44
* Undervolted for devices binned "fast" by -100mV.
* CAF fix for cpufreq driver.
Version 2.0.17: May 7, 2013: Linaro 4.8.0 build, minor CAF fixes:
* Moved to updated Linaro 4.8.0 based toolchain (theoretically faster, less battery likely it's unnoticeable)
* CAF: change boot-up order for cpufreq
* CAF BT: recover from a hardware error by resetting the device
Version 2.0.15: May 2, 2013: boot hang fix, 3.4.43, CPU frequencies, brightness, misc fixes:
* Linux 3.4.43
* Small fixes from CAF (bluetooth, usb)
* Restore the CPU frequences/voltages from 1.x.y kernels (previously I was using HTC's new tables)
* simple_plug: keep cores online during boot
* use the correct brightness ranges for our display (HTC cut off the lowest brightnesses).
* fix a race condition on boot with the binder kernel services
Version 2.0.9: April 23, 2013: 3.4.41 and small fixes:
* Linux 3.4.41
* Small fixes from CAF
* Clean up some more HTC crap in the kernel
Version 2.0.6: April 17, 2013: boot changes, linux 3.4.40:
* Linux 3.4.40 (upstream).
* Limit CPU speeds during boot to stock speeds.
* Enable the thermal driver 5 seconds into the boot (previously was 30 seconds).
* Small changes to the ramdisk from the 2.04 update (I forgot these before).
Version 2.0.3: April 15, 2013: on_demand, battery, HTC spew:
* HTC insists on adding more and more debugging messages to the kernel log. Clean these up.
* OnDemand: revert a CAF change I made and disable io_is_busy.
* Remove HTC's over-volting for CPUs binned anything other than nominal.
* defconfig changes to ease building the kernel for CM10.1 (no you can't use this one for CM10.1!).
Version 2.0.0: April 11, 2013: 2.04 (OTA) source drop:
* Updated to Linux 3.4.39
* Updated to HTC's release of 2.04 source
* cgroup permissions fix
* Otherwise the same as 1.2.6
* Note: After running this for a day, I feel like the battery is draining faster and the phone is hotter than it should be. I'm looking into that.
Changelog from 1.2.x
Version 1.2.6: April 4, 2013: ramdisk fix, lowmemorykiller, hsic wakelocks:
* Fix a problem where the ramdisk was no longer disabling mpdecision and thermald. This issue causes a very minor additional battery drain that has now be fixed (Thanks t1gartist!).
* CAF updates to lowmemorykiller.
* Reapply elkay's HSIC fixes by pulling the real commits from CAF (instead of his hand copied commits) which fixes two problems in his commits.
1.2.2: April 1, 2013: linux 3.4.38, lag fixes, bluetooth drivers, cleanup:
* Undo some dubious commits (or extra code included in unrelated commits, what I meant by "early mistakes"). I reexamined every commit in the kernel to decide whether to keep it or remove it.
* Bluetooth drivers are the current CAF msm-3.4 drivers.
* Additional CPU speed and governor information added in /proc/cpuinfo.
* Cleaner patching to upstream linux (see my github repo for the clean upstream patching).
* Linaro -O3 compilation was redone from scratch because there were some problems found by kern3l in the original patches I pulled, I wanted to ensure that there were no other problems so I redid the work myself.
Changelog from the 1.0.x series:
1.0.27: Mar 25, 2013: thermald, simple_plug
* Make the previous changes to simple_plug less aggressive about turning cores back off when applications force them online. We now detect that this has occurred and give the application 2 minutes to be in charge before we force the state back to what we want.
* Change thermald default throttling to be slightly less strict.
1.0.25: Mar 21, 2013: Linux 3.4.37, simple_plug, performance
* Linux 3.4.37
* simple_plug: add a verify mode (every 5 seconds => almost 0 cost) that fixes the state when apps bring cores on/off-line (e.g. kernel tuner).
* rwsem performance improvements
* CAF improvements (correctness, performance) of the power management layer
1.0.21: Mar 16, 2013: Linux 3.4.36
* Linux 3.4.36
* Small bug fixes from CAF
1.0.18: Mar 7, 2013: Linux 3.4.35
* Linux 3.4.35
1.0.17: Mar 4, 2013: Linux 3.4.34, Linaro 4.7-2013.02, thermald fix
* Linux 3.4.34.
* Linaro 4.7: stopped using 4.8 beta builds due to stability fears and lack of apparent benefit from it. The latest 4.7 drop back-ports some optimizations anyway.
* lowmemorykiller: switch to the CAF version of the low memory killer.
* Fixed several bugs in HTC's thermal driver that could cause the termal driver to miss thermal events.
1.0.15: Feb 26, 2013: Battery optimization, performance, thermal & hotplug improvements
* governor: make ondemand the default governor
* GPU: Very minor GPU overclock to 487MHz (from mdeejay).
* msm_thermal: react better when temperature decreases.
* simple_plug: be slightly less aggressive about bringing cores online.
* New suspend mode PM_SUSPEND_FREEZE
* Oprimization for RWSEM lock handoffs.
* RCU locking in cpufreq!
* Disable more HTC debugging code.
1.0.11: Feb 22, 2013: Battery optimizations, Linaro 4.8 build, update.zip format
* Disable HTC's PNP power manager and adaptive policy services (used for thermald / mpdecision which are already disabled).
* Turn off all the kernel code that was polling to compute the state needed for thermald / mpdecision.
* Turn off a bunch of HTC statistic collection and debugging that isn't needed and wastes battery.
* Linux 3.4.33: fixes a kernel memory corruption/hang in all 3.0 and 3.4 kernels
* Sparkco's 4.8 Linaro build is now being used to compile the kernel
* Moved to update.zip format with less commonly used modules moved to loadable modules.
1.0.8: Feb 19, 2013: Switch to different OC values
* Now using mdeejay's over/unclocking (hopefully solving the L2 cache corruption panic).
* thermal driver is less aggressive about throttling the phone with an additional early step down to stock speed
(50C => 1.5GHz, 75C => 1.3GHz, 83C => 918MHz, 90C => 384MHz).
* Linux 3.4.32 (although no changes that would affect our phone).
1.0.7: Feb 15, 2013: thermal driver no longer polls for state
* Linux 3.4.31.
* Now using the 2013-01 build of the Linaro toolchain.
* Major rewrite of the thermal driver to remove polling (now uses essentially no power).
* Tweaks to the hot-plug driver to reduce CPU consumed to reduce power consumed.
1.0.5: miscellaneous optimizations
* Optimization: use optimized memcpy for user-space copies
* Update to linux 3.4.30
* Tons more cleansing of excessive debugging output
* Use RCU_FAST_NO_HZ as caf claims to have found that this improves battery life
* More linaro -O3 fixes from kern3l via dsb
1.0.2
* cm3629 driver, removed power button pocket check (sounds like a good idea, doesn't work and is a likely candidate for an infrequent sensor drain coming from the proximity sensor not turning off).
* cm3629 remove some unused functionality.
* Two small fixes from kern3l via dsb9938's kernel.
* clean some log messages.
1.0.0
* Merge linux 3.4.29
* simple_plug: a new CPU hot-plug driver (default)
* msm_thermal: a new thermal throttling driver (default)
* faux123's intelli_plug (disabled by default)
* faux123's intellidemand governor (default)
* disable mpdecision and thermald in initrd
* dsb9938's overclocking tables, GPU fix and more -O3 changes
* optimizations/fixes from faux123's mako kernel
* Based on elkay's LK kernel which is based on dsb9938's kernel.
* Includes all elkay's HSIC fixes, but nothing beyond that.
* Linaro -O3 compilation (zarboz) and other compiler flags (dsb9938).
* Disabled remote assistance because that just creeps me out.
* NTFS and CIFS.
* Various optimizations and improvements (faux123's mako kernel, similar to dsb9938's pulls from there).
* Force fast-charge (dsb9938).
* Voltage control (faux123).
* Latest OnDemand and Interactive governors from faux123's mako kernel.
* Large set of scheduler fixes / improvements (faux123).
* Underclocking (but not overclocking right now) to 192 MHz.
* BFQ I/O scheduler (default).
* Cleaned up debugging to make the kmsg more useful.
FAQ
sweep2wake: I have no plans to add that to this kernel at this time.

FAQs
init.d tweaks
I really like Zarboz's goal of trying to get rid of the need for 3rd party apps to make the common changes that we want to make to some of the configurable parameters of the kernel. I created some scripts that run on boot (init.d) because I install my kernel so many times that I would go insane if I had to use an installer. By using these scripts and configuration files on the sdcard, I can just configure it once and keep installing away to my heart's content.
After installing this kernel, there will be:
/system/etc/init.d/99crpalmer
run at boot, even if you switch to another kernel. It is safe to leave this file there and to let it run as it only makes changes if the kernel contains "crpalmer" in the version.
The tweaks are:
CPU Frequencies
* Frequencies loaded from /sdcard/crpalmer-cpufreq-min and /sdcard/crpalmer-cpufreq-max
* Governor loaded from /sdcard/crpalmer-cpufreq-governor
* If you specify either or both of these frequencies, it will lock down all of the CPU frequency controls. I had to do this because HTC overrides them in a script that is run very late in the boot process (thanks HTC!).
* E.g. adb shell su -c "echo 192000 > /sdcard/crpalmer-cpufreq-min"
* E.g. adb shell su -c "echo 1728000 > /sdcard/crpalmer-cpufreq-max"
* E.g. adb shell su -c "echo interactive > /sdcard/crpalmer-cpufreq-governor"
Undervolting
* + or - value loaded from /sdcard/crplamer-uv
* The undervolting in 2.0.23 for FAST binned CPUs would be specified as:
* E.g. adb shell su -c "echo -100 > /sdcard/crpalmer-uv"
Lightsensor
* My light sensor changes didn't sound like they worked well for everyone. If you don't like them you can disable them by:
* E.g. adb shell touch /sdcard/crpalmer-stock-lightsensor
HTC Colour "Enhancement"
* If this file is present then the stock colour "enhancement" will be used, otherwise it will be disabled.
* Introduced in kernel 2.0.41.
** E.g. adb shell touch /sdcard/crpalmer-color-enhancement
My WIFI Won't Turn On
If your WIFI won't turn on then the most likely cause is that either you didn't flash the boot.img (e.g. not S-OFF) or your modules don't match the kernel. To figure out what's wrong, first boot the ROM after having installed my kernel. Second, verify that you are running my kernel by running
adb shell cat /proc/version
and seeing that it says crpalmer in (it should match the version that you think you installed, but at least saying crpalmer is a good start). Then do:
adb shell dmesg -c
(turn on wifi)
adb shell dmesg
and look for an error that says crpalmer in it (something like a module version mismatch error). If you see that, it should tell you the version number of the modules that are installed and the version of the kernel.

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
Thanks for this. Looks good. :thumbup:
Sent from my ViperDNA

nice, moar kernel development :highfive:
welcome aboard

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
So no modules to flash?
Sent from my HTC6435LVW using Tapatalk HD

idkwhothatis123 said:
So no modules to flash?
Click to expand...
Click to collapse
That's right. No need to flash the return-to-stock modules either.

Thank you for this! I also find it hilarious that you including instructions for benchmarking. To this day I still wonder why people actually care about benchmarks as they have little to no impact on real world performance.

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
azndan2 said:
Thank you for this! I also find it hilarious that you including instructions for benchmarking. To this day I still wonder why people actually care about benchmarks as they have little to no impact on real world performance.
Click to expand...
Click to collapse
Self defense... I didn't want to deal with people getting 8K scores and blaming me.
Antutu is actually really useful for testing the thermal driver.

Very nice, does this have the latest changes that were just removed from elkays kernel? Also, could you add the lionheart gov?

Nice to see another kernel to choose from, I will give it a shot this weekend. Will you eventually put any you tweaks? Also, can this be flashed with FlashGui?

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
orangechoochoo said:
Nice to see another kernel to choose from, I will give it a shot this weekend. Will you eventually put any you tweaks? Also, can this be flashed with FlashGui?
Click to expand...
Click to collapse
just tried, flashgui won't even let you flash it. Gotta wait till I get home I guess!
Sent from my HTC6435LVW using Tapatalk 2

Thanks for giving it a shot.

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
codezzie said:
Very nice, does this have the latest changes that were just removed from elkays kernel? Also, could you add the lionheart gov?
Click to expand...
Click to collapse
I looked at elkays changes and it removes a background task that encourages a USB device to power down. This may or may not be a good thing. I'll see how elkay's testing goes before I pull in the change. If it goes well, I'll give it a try.

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
orangechoochoo said:
Nice to see another kernel to choose from, I will give it a shot this weekend. Will you eventually put any you tweaks? Also, can this be flashed with FlashGui?
Click to expand...
Click to collapse
What tweaks? It.already has a lot of improvements...
Any idea what flashgui accepts as input?

I didn't see any mention of gpu tweaks so I didn't want to make assumptions, hence my question.
EDIT: I just noticed my autocorrect changed "gpu" to "you" in my post you responded to.

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
crpalmer said:
Any idea what flashgui accepts as input?
Click to expand...
Click to collapse
Flashgui worked for me. Renamed file to "boot.img" and ignored the warnings. I like living on the edge. Booted up and shows this kernel version. Thanks for this.
Stay thirsty, my friends

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
Had a glitch with it already, phone was sleeping, got a message on gtalk and it locked full on vibration, blinking the led, wouldn't wake up and eventually rebooted after maybe 10 seconds. I've had this happen on one of the dsb kernels too, I think. Wiped caches again, hasn't occurred again so far.
Happened not 10 minutes after flashing it so I'm chalking it up to kernel making itself at home, just a note that it happened.
Edit: just rebooted again getting an email notification, UKB 1.3. Seems I can't receive a notification while the phone is sleeping or it jams up and reboots.
Sent from my HTC DNA

Re: [Kernel] [Linaro] [Linux 3.4.29] Version 1.0.0 - Feb 7
matteebee said:
Flashgui worked for me. Renamed file to "boot.img" and ignored the warnings. I like living on the edge. Booted up and shows this kernel version. Thanks for this.
Stay thirsty, my friends
Click to expand...
Click to collapse
Just did the same thing, was coming back to edit my last post lol
Sent from my HTC6435LVW using Tapatalk 2

pio_masaki said:
Had a glitch with it already, phone was sleeping, got a message on gtalk and it locked full on vibration, blinking the led, wouldn't wake up and eventually rebooted after maybe 10 seconds. I've had this happen on one of the dsb kernels too, I think. Wiped caches again, hasn't occurred again so far.
Happened not 10 minutes after flashing it so I'm chalking it up to kernel making itself at home, just a note that it happened.
Edit: just rebooted again getting an email notification, UKB 1.3. Seems I can't receive a notification while the phone is sleeping or it jams up and reboots.
Sent from my HTC DNA
Click to expand...
Click to collapse
After it reboots, can you try to get a log with
adb shell cat /proc/last_kmsg > last_kmsg.txt
and send a link to the last_kmsg.txt file?

orangechoochoo said:
I didn't see any mention of gpu tweaks so I didn't want to make assumptions, hence my question.
EDIT: I just noticed my autocorrect changed "gpu" to "you" in my post you responded to.
Click to expand...
Click to collapse
Ah, that makes more sense... I'm planning on including dsb's changes to any overclocking, etc. but I don't have the knowledge to tweak these settings myself.

Related

[Kernel][AOSP/TW] ChronicKernel - (UV/GPU/CPU-OC/dyn fsync/Linaro) [05/07/2014]

ChronicKernel for Verizon Samsung Galaxy S4​
{
"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"
}
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
Here is a initial kernel for AOSP/TW. It has all the features you would expect from a modded kernel, CPU OC, GPU OC, more CPU governors, Undervolted, Underclockable, GPU OC CPU L2 OC, and linaro -o3 optimizations
Click to expand...
Click to collapse
Screenshots
Requirements
* Rooted (obviously)
* I use CyanogenMod as my daily, so i don't test the TW version much..it should be fine though.
Installation
1: Place zip on sdcard
3: Reboot into recovery
3: Clear cache and dalvik cache
4: Flash zip
5: Reboot
6: If desired edit the init script at /system/etc/chronic-config.sh to suit your needs
7: Profit
ChronicKernel
* All-in-One kernel for all qualcomm variants (AOSP/CM only)
* Compiled with linaro
* GPU OC to 627 Mhtz (450Mhtz default - configurable though chronic-config.sh init script)
* CPU OC to 2322 Mhtz (1890 Mhtz default)
* CPU L2 cache overclocked to 1.3Ghtz
* Raised the low/med/high values for GPU governor one step each
* Added many I/O Schedulers
* Some scheduler performance tweaks
* Added CPU Governors intelidemand, wheatley, lagfree, linoheart, smartassH3, badass and smartmax (Default gov = intellidemand)
* Dynamic Fsync
* F2FS support
* User adjustable CPU uV
* frandom support
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* USB fast charge (disabled by default - configurable though chronic-config.sh init script
* Patched to Linux 3.4+
May-7
* Added back patch to ramdisk for PACMAN rom.
* Added F2FS support
* Synced ramdisk with CM
April-23
New Release v3.0 All-In-One AOSP_KK4.4 Kernel!
* Sorry for the long delay. Got burnt out on android for awhile and got some new toys as well so was busy
* All the needed updates to kernel and Ramdisk since last release and to comply with CM"s new all-in-one rom build,
because of this we can now use one flashable zip for all qualcomm variants now. I added the auto-loki patching from
CM's rom zips so loki should be done for you. let me know if you have any issues.
* Updated kernel to 3.4.82
* I'm sure there are a few small fixes I forgot since last release but basically you can expect what you did with the last release just up to date.
Dec-24
New Release v2.4 for AOSP Android KitKat 4.4! (TW to follow soon)
Changes since v2.3:
* Got rid o dcvs governor as it never worked
* Updated to offical Android 4.4.2/CM-11 Kernel source, changes include:
* We are now using the msm2 gpu driver not msm.
* Updated WiFi Drivers
* Updated Sensor drivers
* Many changes to the framebuffer and vidc driver
* Linux 3.4.75
And as always the ramdisk is synced with CM as of time of compile
Oct-28
* AOSP-JB4.3: Tagged v2.3.3 (maintenance update)
* AOSP-JB4.3: Fixed issue with latest ROM builds
Oct-26
* AOSP-JB4.3: Tagged v2.3.2 (maintenance update)
* AOSP-JB4.3: Merged all the upstream commits from CM, should help with stability
* NOTE: If your colors are off with the display. Its because your ROM hasn't been updated to latest display drivers, ask your ROM developer to update their ROM.
Oct-20
* Common: Updated to Linux 3.4.66
* Common: Added Faux123's Simple GPU governor
* Common: Fixed compatibility with PAC
* AOSP-JB4.3: Merged upstream changes for compatibility with latest CM nightlies
* TW: Tried to fix issue with LPM mode (charging while off)
Oct-6
* Bumped AOSP to v2.2 and TW to v1.2 respectivly
* Common: Fixed issue across all custom S4 kernels where the Governor is only applied to online cpu cores. They are now set regardless
* Common: More aggressive L2 Overclock, bumped max L2 freq by 100 Mhtz and have a more aggressive scaling of the L2 freqs
* Common: Updated to Linux 3.4.62
* AOSP-JB4.3: a few (minor) upstream changes
Sep-5
* AOSP-JB4.3: Merged over 200 commits from CM to bring in sync, No other changes, although seems performance is a little improved
Aug-24
* General: initial release ot the TW/GE kernel, refered to as TW-JB4.3, this is the same as the TW (now known as TW-JB4.2) just compatible with GE roms
AOSP-JB4.3
* AOSP-JB4.3: Synced Ramdisk with CM, latest nightlies should work now
* AOSP-JB4.3: Fixed a bad merge in the last version related to I/O scheduling
* AOSP-JB4.3: Added official Samsung exFAT support (thanks ktoonsez for original commit)
* AOSP-JB4.3: Updated to Linux 3.4.59
* AOSP-JB4.3: Tagged v2.1
AOSP-JB4.2
* AOSP-JB4.2: Added official Samsung exFAT support (thanks ktoonsez for original commit)
* AOSP-JB4.2: Updated to Linux 3.4.59
* AOSP-JB4.2: Tagged v2.1
TW/TW-JB4.2
* TW: Some cleanup to try and make it more stable
* TW: Added official Samsung exFAT support (thanks ktoonsez for original commit)
* TW: Updated to Linux 3.4.59
* TW: Tagged v1.1 and will be known from this point on as "TW-JB4.2"
TW-JB4.3 - TW/GE
* TW-JB4.3: Initial TW/GE kernel v1.0
Aug-16
* AOSP-JB4.3: Maintenance update - Synced with upstream CM kernel at time of compile - glitches should be gone
* Note: sorry for the delay. i was busy getting 10.2 booting on pyramid/glacier/holiday
* Took the version number out of the OP title as its not the same across all platforms
Aug-4
* AOSP-JB4.3: Added AOSP 4.3 kernel, has all the updates from CM's kernel as of this date
* AOSP-JB4.2: Sync with CM. a little clean up
* TW: TW kernel is now out of RC and v1.0, Merged a few things from the AOSP-JB4.3 kernel
* There were a good amount of updates that are kinda hard to explain. if you want more details check my github
Old Changelogs
July-20
* TW: RC2 release
* TW: tried to fix exFAT support, please let me know
* TW: Fixed an overlook that was causing the GPU to stay at a higher freq then normal
July-18
* Fixed a few little overlooks on my part in the TouchWiz beta1. Here is RC1
July-17
* inital TW build, still beta but should work fine just might have a couple things enabled (I/O schedulers that dont work or shouldnt be)
July-14
* Fixed Color temp settings not showing in Advanced Settings
* Couple tweaks to fastcharge cherry-picked from ktoonsez's kernel
* Merged JFA source
* All CM changes merged
* Added option to configure CPU OC from chronic-config.sh
* Fixed a race condition between chronic-config.sh and init.qcom.post_boot.sh setting governor
* Updated to Linux 3.4.52
* Fixed a type-o in chronic-config.sh that might have prevented dynfsync from being set to the desired setting
* Initial support for the Sprint variant
* General cleanup
July-2
* Reworked the way the config script works. it now sets gov correctly. it was renamed to chronic-config.sh and moved to system/etc/
* A few upstream updates
June-30
* Maintenance update
* Merged all upstream CM changes, should work on latest nightlies now
June-26 Stable Release
* Over 100+ upstream commits, like vidc etc, CHECK HERE for details
* Updated to MFx source/google sources
* small bugfix to screen off max gov
* wakelock fix (upstream)
* Updated to Linux 3.0.50
* Few misc bugfixes
** Honnestly the changelog doesnt do the update justice. CHECK HERE for details
June-18
* Upstream: Kernel source updated to MDL (samsung)
* Bugfix: Synced ramdisk with upstream CM to fix issue with bluetooth
* Fixes to Fast charge
* Bugfix: fix issues with workqueue (ktoonsez)
* Screen off Max freq will be disabled while in call (ktoonsez)
* Bugfix: Two EHCI: HSIC commits from caf to fix a wakelock
* Added CIFS Support
* Switch to intellidemand as default CPU governor
* Set 504Mhtz as boot freq for GPU
* GPU: Changed 544mhz to 545mhz to conform better with the pll table
* reduce some log spam (ktoonsez)
* GPU OC: Add 627mhtz step
* Linux 3.4.49
June-11
* Merged all upstream changes from CM kernel, including things like the MDM kernel source update
* Updated to Linux 3.4.48
* GPU OC now correctly reflects the current gpu freq to sysfs
June-7
* Pretty sure the intellidemand issues are fixed now
* Some bugfixes from caf for cpufreq and cpufreq stats
* GPU OC is fixed now (wasn't working correctly, would reject any freq higher then 450)
* GPU OC steps are now 504 544 and 601mhtz
* Synced with upstream (CM)
June-4
* Added in between steps to OC freqs to try and help people squeeze a little more out of the CPU (ktoonsez)
* GPU OC to 533Mhtz
* Added some missing intelidemand code to try and fix battery drain
* Some upstream changes like control screen color temp by sysfs
* Switched back to interactive as default governor
May-31
* Tweaked the GPU bandwith and governor low/med/high values for better performance
* Some bug fixes from type-o's made by samsung
* Removed CPU governors that don't support hotplugging (ktoonservativeq, dancedance)
* Min cpu freq with start at 378Mhtz for all cores
* Switched to XZ compression when making kernel to reduce size (the only impact on user end is a 1 sec longer boot time on Samsung splash)
May-29
* Reverted some cherry-picks from upstream that was causing bootloops for some
* Fix for GPU governor, it was sometimes getting stuck at 450 mhtz even with screen off (credits: ktoonsez)
* Updated the updater-script in the flashable zip to do some housekeeping before flash like remove old modules
May-28-build2
* Fixed bad zip packages
May-28
* Rebased source off of ktoonsez kernel,
* Fixed all the instability from the last releases
* CPU OC up to 2322 Mhtz (not all devices can handle this!)
* added frandom support
* Added a few Governors and I/O Schedulers
* Disabled a lot of useless debugging options
* Disabled un-needed modules
* More general build optimizations
* Other changes I forgot
May-26-build2
* Fixed all the bootloop issues from the last build
May-26
* Bugfix: cpu freqs on all cores but core0 weren't being set to desired levels
* Bugfix: a lot of block (I/O) fixes from caf and faux123
* CPU is now overclockable to 2268Mhtz but not all devices, including mine can handle this.
* CPU can now be overvolted to 1500 uV
* CPU L2 cache overclock to 1.3Ghtz (this seemed to give the most performance boost out of any overclocking so far)
* full kernel based mpdecision (there is an init.qcom.post_boot.sh script included that will disable userspace mpdecision, DON'T REMOVE IT)
* Added back all the special UID drivers that got disabled
* A lot of cleanup to the defconfig and disabled a lot of useless options and enabled some that weren't there before
* Switched to intellidemand as default governor
* Switched to ROW as default I/O scheduler
* CPU: Boot at default freq of 1890Mhtz for stability
* Probably a lot more small tweaks I'm forgetting
May-18
* Added an init.d script to zip to help control custom kernel settings
* Added CPU OC to 2106 Mhtz (1998 mhtz default)
* Set default GPU OC to 450mhtz to save battery (still overclockable via 89chronic init script)
* Adjusted the GPU Bus bandwith, seems to help with performance and battery life
* Lots of updates for CM kernel (gpu drivers etc)
* Maybe a couple other tweaks I forgot to list
May-14
* initial release
* Please keep all comments in this Discussion Thread. Any comments not in that thread will be ignored. Feel free to use the DevDB Bug reporting option as you see fit. This is critical in keeping the same question from being asked times in 5 different threads all with the same answer. It was really slowing down development.
* ]If you have problems with frequencies sticking use "No frills CPU Control" and go to Settings and prevent other apps from changing CPU settings
* Although this kernel has now reached "stable" status. bugs still could pop up. please if you find a reproducible bug and decide to post please try and provide a last_kmesg or logcat.
* Versions go as follows: AOSP-JB4.3 = CM-10.2 etc, AOSP-JB4.2 = CM-10.1 etc, TW-JB4.2 = Android 4.2 TW based ROMs, TW-JB4.3: Android 4.3/Google Edition based ROMs
AOSP-JB4.2 : ChronicKernel-JB4.2-AOSP-VZW-v2.3.zip
AOSP-JB4.3 : ChronicKernel-JB4.3-AOSP-VZW-v2.3.3.zip
AOSP-KK4.4 : ChronicKernel-KK4.4-AOSP-JFLTE-v3.1.zip
TW-JB4.2 : ChronicKernel-JB4.2-TW-VZW-v1.3.zip
TW-JB4.3 : ChronicKernel-JB4.3-TW-VZW-v1.3.zip
Goo.im Repo : CLICK HERE
* This Kernel can also be downloaded directly with GooManager *
My Github (main): https://github.com/Team-Hydra/android_kernel_samsung_jf
* First off of course cyanogen, the CyanogenMod project and all who contribute.
* A lot of this was taken/based off of flar2's Kernel for the HTC One, so thanks for the source!
* Also grabbed some things from Faux123's kernel
* All the people who have helped me learn more and more over the past 4 months (arco/dastin1018/android1234567) you guys are the best!
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
Happy Flashing
Albinoman887
XDA:DevDB Information
[AOSP/TW] ChronicKernel, a Kernel for the Verizon Samsung Galaxy S 4
Contributors
albinoman887
Kernel Special Features: * Compiled with linaro * GPU OC to 627 Mhtz (450Mhtz default - configurable though chronic-config.sh init script) * CPU OC to 2322 Mhtz (1890 Mhtz default) * CPU L2 cache overclocked to 1.3Ghtz * Raised the low/med/high values for GPU governor one step ea
Version Information
Status: Stable
Created 2013-10-09
Last Updated 2014-05-07
Reserved
Flashed this into PACman, ktoonz kernel never played nice for me. I will report back on my thoughts.
First impressions? Well it boots, strong performance, too early to tell on battery.
Sent from my Galaxy S4
Wake up delay/lag is completely gone for me since flashing this kernel. I'm on the latest CM nightly.
Sent from my SCH-I545 using Tapatalk 4 Beta
So I have been running all day on this kernel. Governor = smartassH3 1998/189 and row scheduler. All set with the native PACman performance settings. No other mods enabled. Not quite the performance I was hoping but not bad considering my slight overclock. Also I have had quite good service today.
Sent from my Galaxy S4
To offer a different perspective, intellidemand, row, 189/1890, no undervolt, CM. Insane so far.
Sent from my SCH-I545 using Tapatalk 4 Beta
might have to try this out
Working very well on pac. Too early to tell battery but based on the change log its going to vary on your set up.
Sent from my SCH-I545 using xda premium
I'm enjoying this kernel and can't wait for future updates! So far I'm getting really good battery life with this. I've noticed a couple of issues which I didn't experience when running the KT kernel. I'm not 100% sure it's kernel related, but I never experienced these with KT. 1) Sometimes wifi won't connect and when I try to access wifi settings in the settings menu it freezes and springs a settings is not responding. 2) On occasion I'll get a real system slowdown where I get a bunch of lag. Both of those issues seem to be resolved with just a regular reboot. 3) I use face unlock as my lockscreen and sometimes the camera doesn't work (including after a reboot). So I see like the white "burst" in the box like it usually does when it's opening the camera, but then the camera doesn't initialize and it just shows a black screen.
My settings:
Kernel:
189/1890
Intellidemand
Row
Haven't made any other changes to settings
Rom:
Fitsnugly's (Euroskank) CM10 from 06/07
Otherwise I think this has huge potential to be my go to kernel for battery life.
Albinoman887, just an FYI, flashed the latest kernel build on the 6/12 CM nightly and BT doesn't turn on. Behavior is consistent with what you typically see when a module is missing. Was on the go and couldn't grab a logcat, but will do so if the solution is non-obvious.
Sent from my SCH-I545 using Tapatalk 4 Beta
Might be some updates to the ramdisk cm made. I'll check it out
Sent from my SGH-M919 using Tapatalk 2
yep looks like its something to do with a CM update. i rolled back to 6/8 and BT works again. they probably changed some permissions or something in the ramdisk. (the lame thing about samsung kernel developing) i'll re-sync the ramdisk code with upstream and see what that does. it should fix it. then i'll release a revised build. until then the June 8 CM build works fine with BT and my kernel, as a temp fix
someone have the older kernel from the 8th
revolt1 said:
someone have the older kernel from the 8th
Click to expand...
Click to collapse
Not the older kernel. Older cm build with current kernel
Sent from my SGH-M919 using Tapatalk 2
albinoman887 said:
Not the older kernel. Older cm build with current kernel
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
ahh
revolt1 said:
ahh
Click to expand...
Click to collapse
I have it working now with latest builds let me try and explain it again.
With samsung phones when you flash a kernel you arent JUST flashing the kernel like on HTC. due to limitations in recovery on samsung you have to flash the full boot.img. this img file contains the zImage (kernel) plus a the ramdisk, which is things like init.rc init.cm init.qcom. these are scripts that run at boot to set permissions for radio, wifi, mount points etc.
Since we are limited to flashing the full boot.img these init scripts get flashed during kernel fash as well.
So say you have a kernel build from the 10th. but on the 15th CM changed some paths in the init scripts (which is what they did this time) and you download that update from the 15th, flash it, then the kernel. you lose all the updates to the ramdisk from the 10th on. So if there are some big changes in there it will cause issues like this BT one. usually the ramdisk doesnt get updated much. its just because the device is so new. i predict in a month or so this wont be an issue as all the scripts will be final.
Enjoying some coffee, then i'll post the new build with the updated ramdisk (fixed BT)
Biggest cup of coffee ever! Lol
Sent from my SCH-I545 using Tapatalk 4 Beta
lol sorry. got busy with life, and had to reinstall my os for various reasons. back in business now
No complaints, just seemed like a good joke
Sent from my SCH-I545 using Tapatalk 4 Beta
Just wondering is anybody knows oz this kernel had CIFS support.
Sent from my SCH-I545 using Tapatalk 2

[Kernel][AOSP/TW] ChronicKernel - (UV/GPU/CPU-OC/dyn fsync/Linaro) [05/07/2014]

ChronicKernel for Sprint Samsung Galaxy S4​
{
"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"
}
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
Here is a initial kernel for AOSP/TW. It has all the features you would expect from a modded kernel, CPU OC, GPU OC, more CPU governors, Undervolted, Underclockable, GPU OC CPU L2 OC, and linaro -o3 optimizations
Click to expand...
Click to collapse
Screenshots
Requirements
* Rooted (obviously)
* I use CyanogenMod as my daily, so i don't test the TW version much..it should be fine though.
Installation
1: Place zip on sdcard
3: Reboot into recovery
3: Clear cache and dalvik cache
4: Flash zip
5: Reboot
6: If desired edit the init script at /system/etc/chronic-config.sh to suit your needs
7: Profit
ChronicKernel
* All-in-One kernel for all qualcomm variants (AOSP/CM only)
* Compiled with linaro
* GPU OC to 627 Mhtz (450Mhtz default - configurable though chronic-config.sh init script)
* CPU OC to 2322 Mhtz (1890 Mhtz default)
* CPU L2 cache overclocked to 1.3Ghtz
* Raised the low/med/high values for GPU governor one step each
* Added many I/O Schedulers
* Some scheduler performance tweaks
* Added CPU Governors intelidemand, wheatley, lagfree, linoheart, smartassH3, badass and smartmax (Default gov = intellidemand)
* Dynamic Fsync
* F2FS Support
* User adjustable CPU uV
* frandom support
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* USB fast charge (disabled by default - configurable though chronic-config.sh init script
* Patched to Linux 3.4+
May-7
* Added back patch to ramdisk for PACMAN rom.
* Added F2FS support
* Synced ramdisk with CM
April-23
New Release v3.0 All-In-One AOSP_KK4.4 Kernel!
* Sorry for the long delay. Got burnt out on android for awhile and got some new toys as well so was busy
* All the needed updates to kernel and Ramdisk since last release and to comply with CM"s new all-in-one rom build,
because of this we can now use one flashable zip for all qualcomm variants now. I added the auto-loki patching from
CM's rom zips so loki should be done for you. let me know if you have any issues.
* Updated kernel to 3.4.82
* I'm sure there are a few small fixes I forgot since last release but basically you can expect what you did with the last release just up to date.
Dec-24
New Release v2.4 for AOSP Android KitKat 4.4! (TW to follow soon)
Changes since v2.3:
* Got rid o dcvs governor as it never worked
* Updated to offical Android 4.4.2/CM-11 Kernel source, changes include:
* We are now using the msm2 gpu driver not msm.
* Updated WiFi Drivers
* Updated Sensor drivers
* Many changes to the framebuffer and vidc driver
* Linux 3.4.75
And as always the ramdisk is synced with CM as of time of compile
Oct-28
* AOSP-JB4.3: Tagged v2.3.3 (maintenance update)
* AOSP-JB4.3: Fixed issue with latest ROM builds
Oct-26
* AOSP-JB4.3: Tagged v2.3.2 (maintenance update)
* AOSP-JB4.3: Merged all the upstream commits from CM, should help with stability
* NOTE: If your colors are off with the display. Its because your ROM hasn't been updated to latest display drivers, ask your ROM developer to update their ROM.
Oct-20
* Common: Updated to Linux 3.4.66
* Common: Added Faux123's Simple GPU governor
* Common: Fixed compatibility with PAC
* AOSP-JB4.3: Merged upstream changes for compatibility with latest CM nightlies
* TW: Tried to fix issue with LPM mode (charging while off)
Oct-6
* Bumped AOSP to v2.2 and TW to v1.2 respectivly
* Common: Fixed issue across all custom S4 kernels where the Governor is only applied to online cpu cores. They are now set regardless
* Common: More aggressive L2 Overclock, bumped max L2 freq by 100 Mhtz and have a more aggressive scaling of the L2 freqs
* Common: Updated to Linux 3.4.62
* AOSP-JB4.3: a few (minor) upstream changes
Sep-5
* AOSP-JB4.3: Merged over 200 commits from CM to bring in sync, No other changes, although seems performance is a little improved
Aug-24
* General: initial release ot the TW/GE kernel, refered to as TW-JB4.3, this is the same as the TW (now known as TW-JB4.2) just compatible with GE roms
AOSP-JB4.3
* AOSP-JB4.3: Synced Ramdisk with CM, latest nightlies should work now
* AOSP-JB4.3: Fixed a bad merge in the last version related to I/O scheduling
* AOSP-JB4.3: Added official Samsung exFAT support (thanks ktoonsez for original commit)
* AOSP-JB4.3: Updated to Linux 3.4.59
* AOSP-JB4.3: Tagged v2.1
AOSP-JB4.2
* AOSP-JB4.2: Added official Samsung exFAT support (thanks ktoonsez for original commit)
* AOSP-JB4.2: Updated to Linux 3.4.59
* AOSP-JB4.2: Tagged v2.1
TW/TW-JB4.2
* TW: Some cleanup to try and make it more stable
* TW: Added official Samsung exFAT support (thanks ktoonsez for original commit)
* TW: Updated to Linux 3.4.59
* TW: Tagged v1.1 and will be known from this point on as "TW-JB4.2"
TW-JB4.3 - TW/GE
* TW-JB4.3: Initial TW/GE kernel v1.0
Aug-16
* AOSP-JB4.3: Maintenance update - Synced with upstream CM kernel at time of compile - glitches should be gone
* Note: sorry for the delay. i was busy getting 10.2 booting on pyramid/glacier/holiday
* Took the version number out of the OP title as its not the same across all platforms
Aug-4
* AOSP-JB4.3: Added AOSP 4.3 kernel, has all the updates from CM's kernel as of this date
* AOSP-JB4.2: Sync with CM. a little clean up
* TW: TW kernel is now out of RC and v1.0, Merged a few things from the AOSP-JB4.3 kernel
* There were a good amount of updates that are kinda hard to explain. if you want more details check my github
Old Changelogs
July-20
* TW: RC2 release
* TW: tried to fix exFAT support, please let me know
* TW: Fixed an overlook that was causing the GPU to stay at a higher freq then normal
July-18
* Fixed a few little overlooks on my part in the TouchWiz beta1. Here is RC1
July-17
* inital TW build, still beta but should work fine just might have a couple things enabled (I/O schedulers that dont work or shouldnt be)
July-14
* Fixed Color temp settings not showing in Advanced Settings
* Couple tweaks to fastcharge cherry-picked from ktoonsez's kernel
* Merged JFA source
* All CM changes merged
* Added option to configure CPU OC from chronic-config.sh
* Fixed a race condition between chronic-config.sh and init.qcom.post_boot.sh setting governor
* Updated to Linux 3.4.52
* Fixed a type-o in chronic-config.sh that might have prevented dynfsync from being set to the desired setting
* Initial support for the Sprint variant
* General cleanup
July-2
* Reworked the way the config script works. it now sets gov correctly. it was renamed to chronic-config.sh and moved to system/etc/
* A few upstream updates
June-30
* Maintenance update
* Merged all upstream CM changes, should work on latest nightlies now
June-26 Stable Release
* Over 100+ upstream commits, like vidc etc, CHECK HERE for details
* Updated to MFx source/google sources
* small bugfix to screen off max gov
* wakelock fix (upstream)
* Updated to Linux 3.0.50
* Few misc bugfixes
** Honnestly the changelog doesnt do the update justice. CHECK HERE for details
June-18
* Upstream: Kernel source updated to MDL (samsung)
* Bugfix: Synced ramdisk with upstream CM to fix issue with bluetooth
* Fixes to Fast charge
* Bugfix: fix issues with workqueue (ktoonsez)
* Screen off Max freq will be disabled while in call (ktoonsez)
* Bugfix: Two EHCI: HSIC commits from caf to fix a wakelock
* Added CIFS Support
* Switch to intellidemand as default CPU governor
* Set 504Mhtz as boot freq for GPU
* GPU: Changed 544mhz to 545mhz to conform better with the pll table
* reduce some log spam (ktoonsez)
* GPU OC: Add 627mhtz step
* Linux 3.4.49
June-11
* Merged all upstream changes from CM kernel, including things like the MDM kernel source update
* Updated to Linux 3.4.48
* GPU OC now correctly reflects the current gpu freq to sysfs
June-7
* Pretty sure the intellidemand issues are fixed now
* Some bugfixes from caf for cpufreq and cpufreq stats
* GPU OC is fixed now (wasn't working correctly, would reject any freq higher then 450)
* GPU OC steps are now 504 544 and 601mhtz
* Synced with upstream (CM)
June-4
* Added in between steps to OC freqs to try and help people squeeze a little more out of the CPU (ktoonsez)
* GPU OC to 533Mhtz
* Added some missing intelidemand code to try and fix battery drain
* Some upstream changes like control screen color temp by sysfs
* Switched back to interactive as default governor
May-31
* Tweaked the GPU bandwith and governor low/med/high values for better performance
* Some bug fixes from type-o's made by samsung
* Removed CPU governors that don't support hotplugging (ktoonservativeq, dancedance)
* Min cpu freq with start at 378Mhtz for all cores
* Switched to XZ compression when making kernel to reduce size (the only impact on user end is a 1 sec longer boot time on Samsung splash)
May-29
* Reverted some cherry-picks from upstream that was causing bootloops for some
* Fix for GPU governor, it was sometimes getting stuck at 450 mhtz even with screen off (credits: ktoonsez)
* Updated the updater-script in the flashable zip to do some housekeeping before flash like remove old modules
May-28-build2
* Fixed bad zip packages
May-28
* Rebased source off of ktoonsez kernel,
* Fixed all the instability from the last releases
* CPU OC up to 2322 Mhtz (not all devices can handle this!)
* added frandom support
* Added a few Governors and I/O Schedulers
* Disabled a lot of useless debugging options
* Disabled un-needed modules
* More general build optimizations
* Other changes I forgot
May-26-build2
* Fixed all the bootloop issues from the last build
May-26
* Bugfix: cpu freqs on all cores but core0 weren't being set to desired levels
* Bugfix: a lot of block (I/O) fixes from caf and faux123
* CPU is now overclockable to 2268Mhtz but not all devices, including mine can handle this.
* CPU can now be overvolted to 1500 uV
* CPU L2 cache overclock to 1.3Ghtz (this seemed to give the most performance boost out of any overclocking so far)
* full kernel based mpdecision (there is an init.qcom.post_boot.sh script included that will disable userspace mpdecision, DON'T REMOVE IT)
* Added back all the special UID drivers that got disabled
* A lot of cleanup to the defconfig and disabled a lot of useless options and enabled some that weren't there before
* Switched to intellidemand as default governor
* Switched to ROW as default I/O scheduler
* CPU: Boot at default freq of 1890Mhtz for stability
* Probably a lot more small tweaks I'm forgetting
May-18
* Added an init.d script to zip to help control custom kernel settings
* Added CPU OC to 2106 Mhtz (1998 mhtz default)
* Set default GPU OC to 450mhtz to save battery (still overclockable via 89chronic init script)
* Adjusted the GPU Bus bandwith, seems to help with performance and battery life
* Lots of updates for CM kernel (gpu drivers etc)
* Maybe a couple other tweaks I forgot to list
May-14
* initial release
* Please keep all comments in this Discussion Thread. Any comments not in that thread will be ignored. Feel free to use the DevDB Bug reporting option as you see fit. This is critical in keeping the same question from being asked times in 5 different threads all with the same answer. It was really slowing down development.
* ]If you have problems with frequencies sticking use "No frills CPU Control" and go to Settings and prevent other apps from changing CPU settings
* Although this kernel has now reached "stable" status. bugs still could pop up. please if you find a reproducible bug and decide to post please try and provide a last_kmesg or logcat.
* Versions go as follows: AOSP-JB4.3 = CM-10.2 etc, AOSP-JB4.2 = CM-10.1 etc, TW-JB4.2 = Android 4.2 TW based ROMs, TW-JB4.3: Android 4.3/Google Edition based ROMs
AOSP-JB4.2 : ChronicKernel-JB4.2-AOSP-SPR-v2.3.zip
AOSP-JB4.3 : ChronicKernel-JB4.3-AOSP-SPR-v2.3.3.zip
AOSP-KK4.4 : ChronicKernel-KK4.4-AOSP-JFLTE-v3.1.zip
TW-JB4.2 : ChronicKernel-JB4.2-TW-SPR-v1.3.zip
TW-JB4.3 : ChronicKernel-JB4.3-TW-SPR-v1.3.zip
Goo.im Repo : CLICK HERE
* This Kernel can also be downloaded directly with GooManager *
My Github (main): https://github.com/Team-Hydra/android_kernel_samsung_jf
* First off of course cyanogen, the CyanogenMod project and all who contribute.
* A lot of this was taken/based off of flar2's Kernel for the HTC One, so thanks for the source!
* Also grabbed some things from Faux123's kernel
* All the people who have helped me learn more and more over the past 4 months (arco/dastin1018/android1234567) you guys are the best!
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
Happy Flashing
Albinoman887
XDA:DevDB Information
[AOSP/TW] ChronicKernel, a Kernel for the Sprint Samsung Galaxy S 4
Contributors
albinoman887
Kernel Special Features: * Compiled with linaro * GPU OC to 627 Mhtz (450Mhtz default - configurable though chronic-config.sh init script) * CPU OC to 2322 Mhtz (1890 Mhtz default) * CPU L2 cache overclocked to 1.3Ghtz * Raised the low/med/high values for GPU governor one step ea
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2014-05-07
Reserved
Please keep all discussion in the new Q&A thread please. otherwise your comment will most likely be ignored. Check "NOTES" section in OP for details
reserved
Interesting! Ill defintely check this out!
Sent from my SPH-L720 using xda app-developers app
Nice to see another kernel developer
Sent from my SPH-L720 using Tapatalk 2
any chance of u cooking up a TW kernel??
Anyone running this thing yet? Thoughts? I may have to flash this layer.
Sent from my SPH-L720 using Tapatalk 4 Beta
mjs2011 said:
Anyone running this thing yet? Thoughts? I may have to flash this layer.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Im getting ready too
Sent from my SPH-L720 using Tapatalk 2
---------- Post added at 09:11 PM ---------- Previous post was at 08:23 PM ----------
mjs2011 said:
Anyone running this thing yet? Thoughts? I may have to flash this layer.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK so far so good
Sent from my SPH-L720 using Tapatalk 2
lol guys just try the kernel....its really stable. ive had it on all the other variants for about 2 months i just forgot about sprint lol. its loosely based off of Ktoonsez's kernel. (we trade fixes back and forth) bot mainly based off of CM with all the additions mentioned plus a few more little ones like frandom support i think its the only kernel with L2 cache overclocked though, which gives a nice boost i think. and battery life is great, and no reboots or anything i'm aware of
albinoman887 said:
lol guys just try the kernel....its really stable. ive had it on all the other variants for about 2 months i just forgot about sprint lol. its loosely based off of Ktoonsez's kernel. (we trade fixes back and forth) bot mainly based off of CM with all the additions mentioned plus a few more little ones like frandom support i think its the only kernel with L2 cache overclocked though, which gives a nice boost i think. and battery life is great, and no reboots or anything i'm aware of
Click to expand...
Click to collapse
Do u plan to cook up a TW kernel or just AOSP/CM??
eh maybe...never messed with TW i flashed CM right when i got my phone so not sure
Been running this since last night. So far so good. Haven't changed any settings because I usually use intellidemand. Are there any settings you suggest changing?
Sent from my SPH-L720 using Tapatalk 4 Beta
albinoman887 said:
eh maybe...never messed with TW i flashed CM right when i got my phone so not sure
Click to expand...
Click to collapse
maybe is good!! yea i never liked CM/AOSP much i think the longest i ever ran a AOSP rom was a few hours tops.. When i was with HTC i ran just sense roms.and .now that im with Samsung I run TW
does camera work with this kernel? i cant seem to use my camera using kt
edit: answered my own Q it does work well with Liquid Smooth Rom
mjs2011 said:
Been running this since last night. So far so good. Haven't changed any settings because I usually use intellidemand. Are there any settings you suggest changing?
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I overclock the cpu to 1998 or 2106 depending on battery and particular phone
rhyme187 said:
does camera work with this kernel? i cant seem to use my camera using kt
edit: answered my own Q it does work well with Liquid Smooth Rom
Click to expand...
Click to collapse
it should work. i think the above poster would have mentioned that if it ididnt. i use the t mobile variant but they are all the same. i can flash your kernel and it works just fine just no radio
heres a test touchwiz version of my kernel. i dont have touchwiz installed so i havent tested it but it should work
http://tinyw.in/8WaA
rhyme187 said:
does camera work with this kernel? i cant seem to use my camera using kt
edit: answered my own Q it does work well with Liquid Smooth Rom
Click to expand...
Click to collapse
Yes camera works fine for me.
Ps: Been running great today on PAC nightly. I'll get some stats up once I have more time on it. Tks op!:thumbup:
Edit, added:
Is it possible to set gpu to stock using root explorer? I could be wrong but any feedback would be very appreciated. Tks!
Sent from my GS4 (PAC 7-15)
anyone test the TW kernel?
and to set GPU clock open /system/etc/chronic-config.sh and look for the GPU section. it has a list of values you can pick from. then just save and reboot
added tw beta
albinoman887 said:
added tw beta
Click to expand...
Click to collapse
sweet!!! flashing now boss.. thanks!!

[Kernel] [4.3.1][CM 10.2] crpalmer's kernel for the official nightlies

This kernel extends the CM kernel with some new features:
New init.d scripts to allow some tweaking without needing any 3rd party apps
* See the next post for details.
Replaced HTC's mpdecision with a new custom hot-plug driver that I created:
* This hot-plug driver is more aggressive about bring cores on and off-line to match the load on the system.
* Bringing cores online earlier makes your phone more responsive / smooth.
* Taking cores offline earlier improves battery life.
* It ramps up very quickly on resume to avoid lag.
Replaced HTC's lightsensor table with one that is more sensible and that matches what other devices use. If you have custom auto-brightness settings, you'll probably need to tweak them after installing this kernel.
There are many additional changes to boost performance and battery life:
* Linaro -O3 compiled (Linaro 4.8).
* Overclocking
* I disable tons of HTC debugging crap left enabled and needlessly consuming battery.
* Improvements to the core locking code of the kernel.
* Patches that transform traditional locks into RCU backed data structures.
* CAF version of the ondemand
* CAF changes to power management to sleep faster and waste less CPU during suspend.
* Improved code for moving data to/from user-space and manipulating strings within the kernel.
Other features:
* Voltage control (faux123) to allow user-space under-volting.
* BFQ I/O scheduler.
Links
A link to each version is included in the changelog entry. Scroll down to the changelog to download the latest version.
Source (GitHub):
* Kernel source
* Build tools
Installation Instructions:
If you are S-OFF you can flash the update.zip in recovery.
If you are S-ON, then after you flash the update.zip in recovery then, while still in recovery, you must run
Code:
adb pull /tmp/boot.img
<reboot into bootloader>
fastboot flash boot boot.img
Changelog:
The following kernels likely do not work with CM builds from before October 2, 2013:
Version 4.9.0: November 6, 2013:Linux 3.4.67, Optimizations, Underclocking, Scheduler
* Linux 3.4.67
* Various optimizations from franciscofranco's N5 kernel
* Underclocking based on faux123's N4 kernel
* Scheduler overhaul from faux123's N4 kernel
Version 4.7.4: October 21, 2013:Linux 3.4.66, Westwood+, Upstream
* Linux 3.4.66
* Switch to Westwood+ for TCP congestion control (theoretically better for wireless networks).
* Merge upstream changes to the kernel
Version 4.4.15: October 4, 2013:revert audio change
* Revert: slight changes to audio from CAF (they broke alarms!)
Version 4.4.14: October 2, 2013: merge upstream, audio, scheduling, ondemandCRP, SIP
* Slight changes to audio from CAF
* HRTICK enabled to improve scheduling responsiveness (merged)
* Fix for cisco phones (merged)
* Fix buffer overflow in printk
* Added ondemandCRP governor
* Merged all upstream changes.
** New ondemand governor, updated interactive governor
** More responsive CPU scaling
** Video updates
** Multi-touch fix
** Fix video underruns (blue flicker)
The following kernels do not work with CM builds from after October 2, 2013:
Version 4.3.3: September 20, 2013: merge upstream, camera fix
* Merged all upstream changes.
* Fix focus and possibly other camera oddities
Version 4.2.3: September 15, 2013: Fix init.d script
* Actually disable mpdecision! (thanks orangechoochoo)
Version 4.2.2: September 14, 2013: Sony panel, OTG
* Re-introduce Sony panel (merged)
* Fix USB OTG host mode (merged)
* Use invisiblek's improved splash screen fix and remove my hack
Version 4.1.1: September 10, 2013: GPU / Display / Clocks / Flicker?
* Synch the GPU code with the M7 / upstream
* Make the display code more inline with the M7 / upstream, use the proper late_init ./ early _off interface
* Add missing clocks
* These changes (most notably the clocks change) may have improved the screen flickering (only time will tell).
Version 4.0.12: September 9, 2013: First release
init.d tweaks
I created some scripts that run on boot (init.d) because I install my kernel so many times that I would go insane if I had to use an installer to configure it each time. By using these scripts and configuration files on the sdcard, I can just configure it once and keep installing away to my heart's content.
After installing this kernel, there will be:
/system/etc/init.d/99crpalmer
run at boot, even if you switch to another kernel. It is safe to leave this file there and to let it run as it only makes changes if the kernel contains "crpalmer" in the version. If run with a kernel that contains crpalmer in the version, it will rename mpdecision so it can't run. If you install another kernel it will then rename mpdecision back so that it will run in the new kernel. In addition to stopping the built-in mpdecision it will allow the following tweaks:
CPU Frequencies
* Frequencies loaded from /sdcard/crpalmer-cpufreq-min and /sdcard/crpalmer-cpufreq-max
* Governor loaded from /sdcard/crpalmer-cpufreq-governor
* If you specify either or both of these frequencies, it will lock down all of the CPU frequency controls. I had to do this because HTC overrides them in a script that is run very late in the boot process (thanks HTC!).
* E.g. adb shell su -c "echo 192000 > /sdcard/crpalmer-cpufreq-min"
* E.g. adb shell su -c "echo 1728000 > /sdcard/crpalmer-cpufreq-max"
* E.g. adb shell su -c "echo interactive > /sdcard/crpalmer-cpufreq-governor"
Undervolting
* + or - value loaded from /sdcard/crplamer-uv
* The undervolting in 2.0.23 for FAST binned CPUs would be specified as:
* E.g. adb shell su -c "echo -100 > /sdcard/crpalmer-uv"
Lightsensor
* My light sensor changes didn't sound like they worked well for everyone. If you don't like them you can disable them by:
* E.g. adb shell touch /sdcard/crpalmer-stock-lightsensor
HTC Colour "Enhancement"
* If this file is present then the HTC's colour "enhancement" will be used, otherwise it will be disabled.
* If this file contains the string "m7" then it will use one of the colour enhancement that was used in the M7 kernel for a panel most like ours.
** E.g. adb shell touch /sdcard/crpalmer-color-enhancement
My WIFI Won't Turn On
If your WIFI won't turn on then the most likely cause is that either you didn't flash the boot.img (e.g. not S-OFF) or your modules don't match the kernel. To figure out what's wrong, first boot the ROM after having installed my kernel. Second, verify that you are running my kernel by running
adb shell cat /proc/version
and seeing that it says crpalmer in (it should match the version that you think you installed, but at least saying crpalmer is a good start). Then do:
adb shell dmesg -c
(turn on wifi)
adb shell dmesg
and look for an error that says crpalmer in it (something like a module version mismatch error). If you see that, it should tell you the version number of the modules that are installed and the version of the kernel.
reserved
Note for those of you used to an existing kernel of mine.
This kernel involves reporting all of my changes to a new base. As such, it is likely to have some issues at the moment. Please let me know if something isn't working right.
This kernel is based on Linux 3.4.10 and not the latest 3.4 Linux kernel. I may change that in the future, but for the time being it makes it easier to try to move code to and from the CM repos to leave it at 3.4.10 and therefore I won't be changing that for now.
This kernel does not contain my thermal driver. I haven't spend the time to port it to this kernel yet and the stock seems to be working a lot better than the DNA one. Therefore, I may never bother porting it.
This kernel does not contain force fast-charge. I may add it again the future.
This cant work on the latest unofficial CM correct?
Sent from my HTC6435LVW using xda app-developers app
d08speed3 said:
This cant work on the latest unofficial CM correct?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
The title says they're for the official nightlies, so I'd doubt it.
Just flashed this. I'm new to your kernel init.d settings. How do I make them run exactly?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Excellent work as always. Looking forward to every new release.
Kernel is running great! Can you pleassssssse add fast charge
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 07:18 AM ---------- Previous post was at 06:40 AM ----------
d08speed3 said:
Kernel is running great! Can you pleassssssse add fast charge
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Scrolling does feel choppy
Sent from my HTC6435LVW using xda app-developers app
Not sure how relevant this is to folks, but my phone's running PPSSPP games, most noticeably Dissidia 012, much better with this kernel and CM10.2 than it was with the 4.3 roms from about a week ago.
I just posted a new release. I have been completely flicker free today running this kernel. It could be a fluke, but at the moment I am (once again) optimistic that we might have a solution.
If you have bad flickering on CM ROMs, can you let me know how this version works for you?
Version 4.1.1: September 10, 2013: GPU / Display / Clocks / Flicker?
* Synch the GPU code with the M7 / upstream
* Make the display code more inline with the M7 / upstream, use the proper late_init ./ early _off interface
* Add missing clocks
* These changes (most notably the clocks change) may have improved the screen flickering (only time will tell).
I see you added smartmax governor. I've never used it have you? Just wondering.
Sent from my HTC6435LVW using xda app-developers app
d08speed3 said:
I see you added smartmax governor. I've never used it have you? Just wondering.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
That'd coming from the stock kernel. I haven't played with it at all.
This kernel is amazing so far; it fixed the wonky boot image thingy, and most of my flickering is gone as well, and mine was pretty bad occasionally. Lets see if it holds tomorrow. Only other thought is maybe USB OTG, but thanks CrPalmer.
Rock solid on my device, but I've never had very bad flickering (knock on wood). Thanks for the great work!
Thanks, could please fix the autofocus of the camera that does not work!
Any positive or negative reports on the flickering with 4.1.1?
crpalmer said:
Any positive or negative reports on the flickering with 4.1.1?
Click to expand...
Click to collapse
none here sir..... none seen .. running cyanfox
mike_augie said:
none here sir..... none seen .. running cyanfox
Click to expand...
Click to collapse
Did you have a lot, a little, some flickering on older kernels? How long have you been running it?
Been running cyan since day of release and both Ur kernels for 4.3 l since u put them out a few days ago ... Had slight flickering nothing hard core like some had reported could see it more in bright light but seems to have almost totally took care of mine ...
Sent from my HTC6435LVW using xda app-developers app

[Kernel][CM 11][4.4.x] crpalmer's kernel for CM11 nightlies

This kernel extends the CM kernel with some new features:
New init.d scripts to allow some tweaking without needing any 3rd party apps
* See the next post for details.
Replaced HTC's mpdecision with a new custom hot-plug driver that I created:
* This hot-plug driver is more aggressive about bring cores on and off-line to match the load on the system.
* Bringing cores online earlier makes your phone more responsive / smooth.
* Taking cores offline earlier improves battery life.
* It ramps up very quickly on resume to avoid lag.
Replaced HTC's lightsensor table with one that is more sensible and that matches what other devices use. If you have custom auto-brightness settings, you'll probably need to tweak them after installing this kernel.
There are many additional changes to boost performance and battery life:
* Linaro -O3 compiled (Linaro 4.8).
* Overclocking
* I disable tons of HTC debugging crap left enabled and needlessly consuming battery.
* Improvements to the core locking code of the kernel.
* Patches that transform traditional locks into RCU backed data structures.
* CAF changes to power management to sleep faster and waste less CPU during suspend.
* Improved code for moving data to/from user-space and manipulating strings within the kernel.
* And tons of other patches such as scheduler improvements, I/O improvements, networking improvements, etc, etc, etc.
Other features:
* Voltage control (faux123) to allow user-space under-volting.
* BFQ I/O scheduler.
* Track upstream Linux changes
Links
A link to each version is included in the changelog entry. Scroll down to the changelog to download the latest version.
Source (GitHub):
* Kernel source
* Build tools
Installation Instructions:
If you are S-OFF you can flash the update.zip in recovery.
If you are S-ON, then after you flash the update.zip in recovery then, while still in recovery, you must run
Code:
adb pull /tmp/boot.img
<reboot into bootloader>
fastboot flash boot boot.img
Changelog:
Version 5.7.6: April 7, 2014: General Fixes, Linux 3.4.86
* Linux version 3.4.86
* Other changes, mostly have been merged into the CM kernel and I forget which changes weren't...
Version 5.7.6: April 7, 2014: General Fixes, Linux 3.4.86
* Linux version 3.4.86
* Other changes, mostly have been merged into the CM kernel and I forget which changes weren't...
Version 5.8.2: July 19, 2014: Upstream updates and security fixes
* Patched up to linux 3.4.99 (latest version of as now)
* Patched up to latest CM (fixes a couple of CVEs, not a whole lot else was missing)
* Update some video bandwidth parameters
Version 5.5.2: January 19, 2014: Linux 3.4.77, CM changes
* CM changes include a fix for the cpu-boost driver, smooth streaming and governor fixes
* Linux 3.4.77
Version 5.4.2: January 5, 2014: Linux 3.4.75, I/O Optimizations, CM changes
* CM changes may resolve lingering problems with min frequency set to max frequency.
Version 5.3.7: December 20, 2013: Linux 3.4.74, WiFi Optimizations, cpufreq gov. changes
* Linux 3.4.74
* Various WiFi optimizations including using less battery when suspended
* Removed ondemandCRP: It existed because it helped a2dp but, thanks to improvements upstream, this is no longer needed
* cpufreq config scripts set the governor before the frequencies
* ondemand: ignore io_is_busy, improves battery
Version 5.2.11: December 7, 2013: Initial KK release: Linux 3.4.72, Optimizations
* Linux 3.4.72
* Various optimizations
XDA:DevDB Information
crpalmer-droid-dna-5.x, Kernel for the HTC Droid DNA
Contributors
crpalmer
Kernel Special Features:
Version Information
Status: Stable
Created 2013-12-07
Last Updated 2014-07-19
Reserved
init.d tweaks
I created some scripts that run on boot (init.d) because I install my kernel so many times that I would go insane if I had to use an installer to configure it each time. By using these scripts and configuration files on the sdcard, I can just configure it once and keep installing away to my heart's content.
After installing this kernel, there will be:
/system/etc/init.d/99crpalmer
run at boot, even if you switch to another kernel. It is safe to leave this file there and to let it run as it only makes changes if the kernel contains "crpalmer" in the version. If run with a kernel that contains crpalmer in the version, it will rename mpdecision so it can't run. If you install another kernel it will then rename mpdecision back so that it will run in the new kernel. In addition to stopping the built-in mpdecision it will allow the following tweaks:
CPU Frequencies
* Frequencies loaded from /sdcard/crpalmer-cpufreq-min and /sdcard/crpalmer-cpufreq-max
* Governor loaded from /sdcard/crpalmer-cpufreq-governor
* If you specify either or both of these frequencies, it will lock down all of the CPU frequency controls. I had to do this because HTC overrides them in a script that is run very late in the boot process (thanks HTC!).
* E.g. adb shell su -c "echo 192000 > /sdcard/crpalmer-cpufreq-min"
* E.g. adb shell su -c "echo 1728000 > /sdcard/crpalmer-cpufreq-max"
* E.g. adb shell su -c "echo interactive > /sdcard/crpalmer-cpufreq-governor"
Undervolting
* + or - value loaded from /sdcard/crplamer-uv
* The undervolting in 2.0.23 for FAST binned CPUs would be specified as:
* E.g. adb shell su -c "echo -100 > /sdcard/crpalmer-uv"
Lightsensor
* My light sensor changes didn't sound like they worked well for everyone. If you don't like them you can disable them by:
* E.g. adb shell touch /sdcard/crpalmer-stock-lightsensor
HTC Colour "Enhancement"
* If this file is present then the HTC's colour "enhancement" will be used, otherwise it will be disabled.
* If this file contains the string "m7" then it will use one of the colour enhancement that was used in the M7 kernel for a panel most like ours.
** E.g. adb shell touch /sdcard/crpalmer-color-enhancement
Reserved
Giving it a go! Thanks for your continued support for this device man its much appreciated!!!
Sent from my HTC6435LVW using Tapatalk
Hell yes!!! Christmas comes early from crpalmer!!! Thank you sir!!!!!!
Sent from my HTC6435LVW using Tapatalk
---------- Post added at 02:01 PM ---------- Previous post was at 01:50 PM ----------
Running smooth as butter. Under clocked over clocked
Sent from my HTC6435LVW using Tapatalk
crpalmer said:
This kernel extends the CM kernel with some new features:
New init.d scripts to allow some tweaking without needing any 3rd party apps
* See the next post for details.
Replaced HTC's mpdecision with a new custom hot-plug driver that I created:
* This hot-plug driver is more aggressive about bring cores on and off-line to match the load on the system.
* Bringing cores online earlier makes your phone more responsive / smooth.
* Taking cores offline earlier improves battery life.
* It ramps up very quickly on resume to avoid lag.
Replaced HTC's lightsensor table with one that is more sensible and that matches what other devices use. If you have custom auto-brightness settings, you'll probably need to tweak them after installing this kernel.
There are many additional changes to boost performance and battery life:
* Linaro -O3 compiled (Linaro 4.8).
* Overclocking
* I disable tons of HTC debugging crap left enabled and needlessly consuming battery.
* Improvements to the core locking code of the kernel.
* Patches that transform traditional locks into RCU backed data structures.
* Different version of ondemand cpufreq governor
* CAF changes to power management to sleep faster and waste less CPU during suspend.
* Improved code for moving data to/from user-space and manipulating strings within the kernel.
* And tons of other patches such as scheduler improvements, I/O improvements, networking improvements, etc, etc, etc.
Other features:
* Voltage control (faux123) to allow user-space under-volting.
* BFQ I/O scheduler.
* Track upstream Linux changes
Links
A link to each version is included in the changelog entry. Scroll down to the changelog to download the latest version.
Source (GitHub):
* Kernel source
* Build tools
Installation Instructions:
If you are S-OFF you can flash the update.zip in recovery.
If you are S-ON, then after you flash the update.zip in recovery then, while still in recovery, you must run
Code:
adb pull /tmp/boot.img
<reboot into bootloader>
fastboot flash boot boot.img
Changelog:
Version 5.2.11: December 7, 2013:Initial KK release: Linux 3.4.72, Optimizations
* Linux 3.4.72
* Various optimizations
XDA:DevDB Information
crpalmer-droid-dna-5.x, a Kernel for the HTC Droid DNA
Contributors
crpalmer
Kernel Special Features:
Version Information
Status: Stable
Created 2013-12-07
Last Updated 2013-12-07
Click to expand...
Click to collapse
Server must be getting hammered... can't download my crack!!!!?!
Never mind it's coming...
How do i run the scripts?
I didn't like smartmax anyway...made me feel like I had a droid incredible again. Very VERY smooth. This on crdroid with halo 2.0 is gold. Thanks for sticking with us. Fast charge would be nice, but I'm content.
Do you take donations? Not trying to look haughty or anything...I truly don't know.
-DroidIsDNA- said:
I didn't like smartmax anyway...made me feel like I had a droid incredible again. Very VERY smooth. This on crdroid with halo 2.0 is gold. Thanks for sticking with us. Fast charge would be nice, but I'm content.
Do you take donations? Not trying to look haughty or anything...I truly don't know.
Click to expand...
Click to collapse
Actually smartmax is gone from anything using the CM kernel, not just my kernel. I think crdroid is using their own kernel so it may still be left in there (it's up to them whether or not they cherry-pick my removal of it...).
I don't accept donations. I do all my android work for fun and only for fun. Thanks for the thought though.
crpalmer said:
Actually smartmax is gone from anything using the CM kernel, not just my kernel. I think crdroid is using their own kernel so it may still be left in there (it's up to them whether or not they cherry-pick my removal of it...).
I don't accept donations. I do all my android work for fun and only for fun. Thanks for the thought though.
Click to expand...
Click to collapse
Sorry to bother you but how do i run the script.do i have to run them individually at first or just the crpalmer one?great job on the kernel.
Thanks CR
gillim74 said:
Sorry to bother you but how do i run the script.do i have to run them individually at first or just the crpalmer one?great job on the kernel.
Click to expand...
Click to collapse
What script do you want to run? You can push them using adb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Just wondering crpalmer, when you release new kernels like this, do they also contain all of the previous optimizations and such as the kernels before, like an update to work with the new android OS?
d08speed3 said:
What script do you want to run? You can push them using adb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What are the commands to push the script s because I've never used a custom kernal
Sent from my HTC6435LVW using XDA Premium 4 mobile app
d08speed3 said:
What script do you want to run? You can push them using adb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
All of them but i dont know how to push them
rejectedjs said:
Just wondering crpalmer, when you release new kernels like this, do they also contain all of the previous optimizations and such as the kernels before, like an update to work with the new android OS?
Click to expand...
Click to collapse
Yes.
thayl0 said:
What are the commands to push the script s because I've never used a custom kernal
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
See post #2, it contains example adb commands.
Chris, what are your thoughts regarding the performance options in CM where you can allow purging of assets and kernel same page merging?
I used to have those enabled but I turned them off a couple weeks ago and noticed no difference.
gillim74 said:
Sorry to bother you but how do i run the script.do i have to run them individually at first or just the crpalmer one?great job on the kernel.
Click to expand...
Click to collapse
The scripts get run every time you boot the phone. Post #2 explains how you configure what the scripts do. There is nothing that you need to run yourself.
orangechoochoo said:
Chris, what are your thoughts regarding the performance options in CM where you can allow purging of assets and kernel same page merging?
I used to have those enabled but I turned them off a couple weeks ago and noticed no difference.
Click to expand...
Click to collapse
No need to use unless you have little to no AFM (absolute free memory). On phones with less than a gig of ram, KSM is pretty much a given need, as it will merge identical bytes to free up more ram. I have never had less than 600mb AFM on this phone to need to turn on KSM.
Sent from my DNA using my mind.

[KERNEL][Fighter][AOSP][4.4][26Jul] Bubba Kernel

Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* 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.
* blah blah blah you get the point.
*/​
1# post: Disclamer - special thanks
2# post: Current release & source
3# post: FAQ - bugs - future features
Donator List: (huge thanks for support)
here
Suggested kernel control app: trickstermod
I don't know if it works because i don't own the device but i have got ville which is pretty similar
[GUIDE]How to compile a kernel
Credits and Thanks:
dsixda, showp1984, ngtools, faux123, Christopher83, franciscofranco, msm8960 team, jrior001
Features:
Based on linux 3.4.99
Compiled with linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
Linaro -O3 optimization
avaiable CPU governors: interactive, ondemand, performance, powersave, intellimand, intelliactive
avaiable GPU governors: ondemand, performance, simple
avaiable schedulers: row, deadline, noop, cfq, bfqv7r4, fiops, sio
Sleepy Plug
NTFS read & write support
exfat support
UTF8
Voltage control
Sweep2Wake
Double tap 2 wake
Pocket detection
Intelli-thermal
zRam with LZ4 compression
zCache with LZ4 compression
CPU OC to 1.7 GHz
GPU OC to 512MHz (3D) and 320MHZ (2D)
Faux sound control v. 3
Improved alghorithm: SHA1, AES, SQRT, lib/string (glibc version), lib/memcopy (glibc version), XOR (neon)
dynamic fsync by faux123
fastcharge
powersuspend driver (replace earlysuspend)
KCAL control (RGB)
heavly patched memory allocators, RWSEM and mutex (take a look at my github, too many changes to make a list here)
Changelog:
Code:
[JUL 26 2014]
Revert "prctl: adds the capable(CAP_SYS_NICE) check to PR_SET_TIMERSLACK_PID."
Revert "prctl: adds PR_SET_TIMERSLACK_PID for setting timer slack of"
add qseecom support
some defconfig changes
cpufreq: revert CAF's cpu policy save code
sched/cpuidle: reduce IPI storm. Backport upstream 3.16
mm, hugetlb: improve page-fault scalability
mm: per-thread vma caching
update compiler to linaro toolchain 4.9.1 2014.07 optimized for cortex-a15
update to 3.4.99
added KCAL control by faux and fixed by me
add F2FS support
Revert "msm: htc: update mem mapping"
[JUL 17 2014]
update to 3.4.98
sync with cm
sync with codeaurora/kk_2.7-stable
update sleepy_plug
bfq: BFQ-v7r5
bugfix from google (see github)
[JUN 29 2014]
Remove JustArchi GCC flags cos they are unstable
update to 3.4.95
sync with CM
sync with codeaurora/kk_2.7-stable
ext4: Speedup WB_SYNC_ALL pass called from sync(2)
[JUN 19 2014]
update compiler to linaro toolchain 4.9.1 2014.06 optimized for cortex-a15
update to 3.4.94
remove -fdata-sections GCC flag (cause of reboot issue)
sync with CM
sync with codeaurora/kk_2.7-stable
updated sleepy_plug
[JUN 09 2014]
sync with codeaurora/kk_2.7-stable
memset patch to fix bootloops
[JUN 08 2014]
3.4.92
reverted some KGSL CAF patches
removed -ftrace flag
sync with CM
improved int_sqrt algorithm
update bfq to v7-r4
[MAY 28 2014]
sync with codeaurora/kk_2.7-stable
update sleepy_plug
cpufreq: ondemand: Calculate load_at_max_freq based on current policy->max
sched: add do_avg_nr_running to fix avg_nr_running
[MAY 19 2014]
update to 3.4.91
merge codeaurora/kk_2.7_rb1.38
update bfq to v7-r3
sleepy_plug now supports quadcore CPUs
fix headset support (CM)
new GCC flags
update compiler
[MAY 03 2014]
block: support volname for HTC devices with proc/emmc support
[MAY 02 2014]
compiled with Linaro GCC 4.9.1 optimized for cortex-a15
sync with CM
update devices_htc from Jet jb 4.3 kernel
update headset driver from Jet jb 4.3 kernel
update memory mapping (more RAM avaiable)
update pn544 driver
update bma250 driver
OC to 1.7GHz
[APR 29 2014]
fix boot
update to 3.4.88
sync with codeaurora/kk_2.7-stable
some other CAF patches
max OC to 1.5 GHz
[APR 28 2014]
fixed boot (?)
[APR 24 2014]
first release
If you like my work please consider making a donation, I spend almost all my free time on making this kernel the best
i'll buy another phone to continue to support the android development!
Download:
androidfilehost folder: http://www.androidfilehost.com/?w=files&flid=14183
normalToQV: http://www.androidfilehost.com/?fid=23501681358544069
(if you don't see the new version just wait some minutes, it's uploading)
Kernel Source: Github
Q: What is QV version?
A: QV means "qualcomm voltages". qualcomm made a patch and stuck all voltages to 1150mv to improve stability. QV version has got all 1150 mv for each freq (like older 3.4 kernels).​Q: I plugged in my pen drive but i can't found it
A: look in /mnt/usbdisk folder.​Q: What's and how i enable/disable fastcharge?
A: with fast charge an USB charger will recognized as AC charger. it won't charge your phone faster with an AC charger. it may not charge your phone faster with an USB charger.
with the usb cable UNPLUGGED edit /sys/kernel/fast_charge/force_fast_charge:
0 -> disable
1 -> enable
than plug in the cable​Q: i've got random reboots, what do you need?
A: first read here
write this info:
kernel version
ROM
governor
scheduler
undervolted? if yes don't undervolt
QV version? if no use it
last_kmsg
Q: what's BLN and how i enable/disable it?
with BLN on when you received a notify the soft key will blink.
to enable/disable edit /sys/class/leds/button-backlight/blink_buttons:
0 -> disable
1 -> enable​Q: what's s2w and how i enable/disable it?
Sweep2wake allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep).
to enable/disable edit /sys/android_touch/sweep2wake:
0 -> disable
1 -> enable​Q: what's dt2w and how i enable/disable it?
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping the capacitive buttons.
to enable/disable edit /sys/android_touch/doubletap2wake:
0 -> disable
1 -> enable​What's sleepy_plug and how can i activate/deactivate it?
sleepy plug it's an hotplug driver (it decide when turn on the second core) i wrote. it's an experimental driver and it may have got performance problem. if you notice some decrease in performance report it.
to enable/disable edit /sys/module/sleepy_plug/parameters/sleepy_plug_active:
0 -> disable
1 -> enable​Install instruction:​S-OFF:
- flash the zip in recovery
- wipe caches (optional)​S-ON:
Windows & Linux:
flash kernel zip.
stay in recovery after flashing the zip
from command prompt (ot terminal) on PC:
Code:
adb pull /tmp/newboot.img
adb reboot-bootloader
fastboot flash boot newboot.img
fastboot reboot
OLD S-ON INSTRUCTION:
Linux:
- flash awesome kernel cleaning script: http://d-h.st/HDi (optional)
- flash the zip in recovery (obsolete, for older kernels with modules outside built outside)
- use zImage switcher to make a new boot.img
-
Code:
fastboot flash boot newBoot.img
Windows: (don't ask me how it works or everything else, i don't know and they have got tutorials on their site)
- repack your ROM boot.img with mine zImage using Virtuous Ten Studio http://www.virtuous-ten-studio.com/index.php/downloads
-
Code:
fastboot flash boot newBoot.img
Bugs 3.4:
None
If you want to use my kernel for your ROM just use it and cit me in credits
Great thread and great work. I will be flashing this tonight over a fresh install of snapshot M5 CM11! I'll let you know how it runs, hopefully smooth as butter. Thanks again
rmbq said:
Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* 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.
* blah blah blah you get the point.
*/​
1# post: Disclamer - special thanks
2# post: Current release & source
3# post: FAQ - bugs - future features
Donator List: (huge thanks for support)
here
Suggested kernel control app: trickstermod
I don't know if it works because i don't own the device but i have got ville which is pretty similar
[GUIDE]How to compile a kernel
Credits and Thanks:
dsixda, showp1984, ngtools, faux123, Christopher83, franciscofranco, msm8960 team, jrior001
Click to expand...
Click to collapse
Can you compile a 4.1.2 SENSE5 kernel? all working
Don't care about my awkward English
zhaotiantian said:
Can you compile a 4.1.2 SENSE5 kernel? all working
Don't care about my awkward English
Click to expand...
Click to collapse
I don't work on sense
Inviato dal mio One S utilizzando Tapatalk
looks great.. just flashed CV on new cm11 nightly.. bootloops htc screen
Non QV bootloops on HTC Quietly Brilliant screen. CM 11 4/14 nightly. I'll try the QV another day.
I think I used wrong voltages for you, freq it's 1.5 GHz instead 1.2. I'll make another version asap
I'm running CM11 snapshot M5, I'm not sure which version to flash. Thanks for the work!
Sent from my Incredible 4G LTE using Tapatalk
try the new version!
still no boot for me, tried new non-qv..
and this one? http://www.androidfilehost.com/?fid=23329332407590054
^^ there we go! that one works so far so good.. only thing i noticed is max cpu option is still 1728, i don't think this phone can go above 1512, but i may be wrong?
edit: also, trying to disable the button backlight is buggy. the 3 lights will still blink intermittently..
itrx said:
^^ there we go! that one works so far so good.. only thing i noticed is max cpu option is still 1728, i don't think this phone can go above 1512, but i may be wrong?
Click to expand...
Click to collapse
officially only 1242MHz even ... but it runs fine at the usual (slight) OC 1458MHz or 1512 ... but also 1674 is fine ... just consumes more battery and gets hotter. even up to 1809MHz should be stable for most, but that is way to hot and batt-sucking imho!
official booting version is up, i limited OC to 1.5, 1.7 is too much xD
rmbq said:
official booting version is up, i limited OC to 1.5, 1.7 is too much xD
Click to expand...
Click to collapse
for reference our/my: on the Infernal / Infernal-K99 (ICS-Sense custom kernel) ... 1512 / 1458 was set as the std max CPU freq, but we allowed up to 1809 on Infernal (which I admit is rather really high xD) ... and 1674 max OC on Infernal-K99 => the max OC of 1674 is usually auto-selected for the 2nd-core on demand whereas the 1st core admits to whatever limit is set (thus usually 1458)
no real heat probs at all since months with that setting ... 1809 tended to get rather hot (e.g. on reboots) ... not so with 1674 (and a not too high voltage as set in std)
oh, and limiting the "OC" to 1512 isn't really an OC limit ... as that was std for the MSM8960 on almost all devices! (just fireball got an artificial limit of 1242 to further improve on batt runtime). so from that point of view, only everything _above_ 1458/1512 should be considered OC.
just my 2c
PS: apart from that, thanks for working on fireball AT ALL ... there aren't many devs left here unfortunately
on a note: please also enable 192MHz as the lowest CPU freq while you are at it ... never heard any complaints about it for our custom-kernels ... _and_ it greatly improves on total runtime, if 192MHz as lowest for CPU is set ... instead of the regular 384MHz only
cheers,
kimba99
Kernel is pretty smooth and getting great battery life, thank you indeed! I'd agree with adding 192Mhz as well.
kimba99 said:
for reference our/my: on the Infernal / Infernal-K99 (ICS-Sense custom kernel) ... 1512 / 1458 was set as the std max CPU freq, but we allowed up to 1809 on Infernal (which I admit is rather really high xD) ... and 1674 max OC on Infernal-K99 => the max OC of 1674 is usually auto-selected for the 2nd-core on demand whereas the 1st core admits to whatever limit is set (thus usually 1458)
no real heat probs at all since months with that setting ... 1809 tended to get rather hot (e.g. on reboots) ... not so with 1674 (and a not too high voltage as set in std)
oh, and limiting the "OC" to 1512 isn't really an OC limit ... as that was std for the MSM8960 on almost all devices! (just fireball got an artificial limit of 1242 to further improve on batt runtime). so from that point of view, only everything _above_ 1458/1512 should be considered OC.
just my 2c
PS: apart from that, thanks for working on fireball AT ALL ... there aren't many devs left here unfortunately
on a note: please also enable 192MHz as the lowest CPU freq while you are at it ... never heard any complaints about it for our custom-kernels ... _and_ it greatly improves on total runtime, if 192MHz as lowest for CPU is set ... instead of the regular 384MHz only
cheers,
kimba99
Click to expand...
Click to collapse
about OC ok, i didn't know your device can handle 1.7 GHz and i'll enable it again in next version.
about 192MHz i don't know if i ever will enable it
rmbq said:
about 192MHz i don't know if i ever will enable it
Click to expand...
Click to collapse
About over/down clock/voltage CPU & GPU, please check this post:
http://forum.xda-developers.com/showthread.php?t=2217285?&p=51891887

Categories

Resources