gr33nd3vil

[Kernel][AOSP/TW] ChronicKernel - (UV/GPU/CPU-OC/dyn fsync/Linaro) [Sep-5th]

Recommended Posts

Best AOSP Kernel I have used.  Now onto the goodies! Please give all Credit to Albinoman887

 

 

Updates: Added TW RC1 & Android 4.3 please post results smile.gif smile.gif


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, CPU L2 OC, and linaro -o3 optimizations

 

y9e4evyh.jpg

 

Installation Instructions

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 smile.gif


Kernel Features

ChronicKernel

* 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
* User adjustable CPU uV
* 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+


Changelog

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 smile.gif
* 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

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


Notes

If you have problems with frequencies sticking use "No frills CPU Control" and go to Settings and prevent other apps from changing CPU settings

This is pretty much my first kernel and is still very much in development. there most likely will be bugs. 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


DOWNLOAD

AOSP-JB4.2 : ChronicKernel-JB4.2-AOSP-SPR-v2.1.zip
AOSP-JB4.3 : ChronicKernel-JB4.3-AOSP-SPR-v2.1.1.zip
TW-JB4.2 : ChronicKernel-JB4.2-TW-SPR-v1.1.zip
TW-JB4.3 : ChronicKernel-JB4.3-TW-SPR-v1.0.zip
Goo.im Repo : CLICK HERE
* This Kernel can also be downloaded directly with GooManager *


Source Code

My Github (main): https://github.com/Team-Hydra/android_kernel_samsung_jf


Credits

* 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 smile.gif (arco/dastin1018/android1234567) you guys are the best!

Edited by gr33nd3vil

Share this post


Link to post
Share on other sites

PSA: don't download from his direct links in the thread, those are for the international variant. Check his goo.im repo.

http://goo.im/devs/Albinoman887/jf

As far as i know, vzw and spr work for us. Somebody else should confirm that.

Repeat: do not download anything with "JFeur" in the file name!

Sent from my SCH-R970 using Tapatalk 4 Beta

Share this post


Link to post
Share on other sites

PSA: don't download from his direct links in the thread, those are for the international variant. Check his goo.im repo.

http://goo.im/devs/Albinoman887/jf

As far as i know, vzw and spr work for us. Somebody else should confirm that.

Repeat: do not download anything with "JFeur" in the file name!

Sent from my SCH-R970 using Tapatalk 4 Beta

I'm on the kernel as we speak on s4 for uscc this is why I don't post on team us cellular ppl jump all over others when they try good good ... *sigh*

Sent from my SCH-R970 using Tapatalk 2

Edited by gr33nd3vil

Share this post


Link to post
Share on other sites

the one made for the international variant?

can you give me the exact name of the file you flashed? if you're running something made for JFeur then that is huge for our community as well as others.

like seriously based on all of my android experience the only thread you should be in right now is the one where we figure out how you can convince your local uscc store to give you a replacement and that your phone just wouldn't turn on and you don't know what happened!

Sent from my SCH-R970 using Tapatalk 4 Beta

Share this post


Link to post
Share on other sites

the one made for the international variant?

can you give me the exact name of the file you flashed? if you're running something made for JFeur then that is huge for our community as well as others.

like seriously based on all of my android experience the only thread you should be in right now is the one where we figure out how you can convince your local uscc store to give you a replacement and that your phone just wouldn't turn on and you don't know what happened!

Sent from my SCH-R970 using Tapatalk 4 Beta

Um ya I flashed the asop international kernel its not rocket science if it didn't flash I'd revert to stock.

And my uscc store will give me whatever I want since I'm a business account an know everyone ;)

Sent from my SCH-R970 using Tapatalk 2

Edited by gr33nd3vil

Share this post


Link to post
Share on other sites

no man I'm not calling you dumb, it is just completely new to me to see anyone on a us variant of any device flash something from an international variant and ever use their device again.

Sent from my SCH-R970 using Tapatalk 4 Beta

Share this post


Link to post
Share on other sites

no man I'm not calling you dumb, it is just completely new to me to see anyone on a us variant of any device flash something from an international variant and ever use their device again.

Sent from my SCH-R970 using Tapatalk 4 Beta

I've done it a lot on the note 2 lol. Anything can be fixed :)

Sent from my SCH-R970 using Tapatalk 2

Share this post


Link to post
Share on other sites

weird, you're a lucky man then.

Sent from my Nexus 7 using Tapatalk HD

I guess just like to tinker

Sent from my SCH-R970 using Tapatalk 2

Share this post


Link to post
Share on other sites

Flashing GT9505 kernels should be safe. Same specs found in the US verison. Worse that could happen is bonked wifi / data / calling. GT9500 on the other hand stay away unless you want a 200 dollar brick. GT9500 has exynos octa core processor with 2gb ram.

Sent via SCH-I925U Note 10.1 LTE

Edited by xonone

Share this post


Link to post
Share on other sites

Flashing GT9505 kernels should be safe. Same CPU and RAM like the US verisons. Worse that could happen is bonked wifi / data / calling. GT9500 on the other hand stay away unless you want a 200 dollar brick.

Sent via SCH-I925U Note 10.1 LTE

What's wrong with a paper weight ;)

Ya the chronic vzw version wouldn't boot it was odd...

Sent from my SCH-R970 using Tapatalk 2

Share this post


Link to post
Share on other sites

Flashing GT9505 kernels should be safe. Same CPU and RAM like the US verisons. Worse that could happen is bonked wifi / data / calling. GT9500 on the other hand stay away unless you want a 200 dollar brick.

Sent via SCH-I925U Note 10.1 LTE

What's wrong with a paper weight ;)

Ya the chronic vzw version wouldn't boot it was odd...

Sent from my SCH-R970 using Tapatalk 2

VZN kernels are flashed into a different part of the system if i remember right. Pretty sure AT&Ts as well due to locked bootloaders on both carriers.

Sent via SCH-I925U Note 10.1 LTE

Edited by xonone

Share this post


Link to post
Share on other sites

 

PSA: don't download from his direct links in the thread, those are for the international variant. Check his goo.im repo.

http://goo.im/devs/Albinoman887/jf

As far as i know, vzw and spr work for us. Somebody else should confirm that.

Repeat: do not download anything with "JFeur" in the file name!

Sent from my SCH-R970 using Tapatalk 4 Beta

I'm on the kernel as we speak on s4 for uscc this is why I don't post on team us cellular ppl jump all over others when they try good good ... *sigh*

Sent from my SCH-R970 using Tapatalk 2

 

 

I know how you feel, people give me crap every day for bringing issues to light.  Everyone says I'm wrong, or crazy, or it's only me.  Then a few days later, others will finally step forward and admit they have the same issues. 

 

Try to have a thick skin.  No one was jumping on you.  It's good that you posted it, as we did not know that was safe to flash.  But be careful, because "anything can be fixed" is not always true.  With the S3, people hard brick their phones when they flash international ROMS and kernels.  So be careful, but good find!

Share this post


Link to post
Share on other sites

PSA: don't download from his direct links in the thread, those are for the international variant. Check his goo.im repo.

http://goo.im/devs/Albinoman887/jf

As far as i know, vzw and spr work for us. Somebody else should confirm that.

Repeat: do not download anything with "JFeur" in the file name!

Sent from my SCH-R970 using Tapatalk 4 Beta

Unless I messed up some how, neither the vzw or sprint kernels worked. Again, it could very well be user error though.

Share this post


Link to post
Share on other sites

PSA: don't download from his direct links in the thread, those are for the international variant. Check his goo.im repo.

http://goo.im/devs/Albinoman887/jf

As far as i know, vzw and spr work for us. Somebody else should confirm that.

Repeat: do not download anything with "JFeur" in the file name!

Sent from my SCH-R970 using Tapatalk 4 Beta

Unless I messed up some how, neither the vzw or sprint kernels worked. Again, it could very well be user error though.

All sprint kernels work I can vouche for that. However the Verizon do not.

Sent from my SCH-R970 using Tapatalk 2

Share this post


Link to post
Share on other sites

PSA: don't download from his direct links in the thread, those are for the international variant. Check his goo.im repo.

http://goo.im/devs/Albinoman887/jf

As far as i know, vzw and spr work for us. Somebody else should confirm that.

Repeat: do not download anything with "JFeur" in the file name!

Sent from my SCH-R970 using Tapatalk 4 Beta

Unless I messed up some how, neither the vzw or sprint kernels worked. Again, it could very well be user error though.
All sprint kernels work I can vouche for that. However the Verizon do not.

Sent from my SCH-R970 using Tapatalk 2

What did I do wrong then? What's your process of flashing the sprint one? Which file did you flash?

Sent from my SCH-R970U using Tapatalk 4 Beta

Share this post


Link to post
Share on other sites

PSA: don't download from his direct links in the thread, those are for the international variant. Check his goo.im repo.

http://goo.im/devs/Albinoman887/jf

As far as i know, vzw and spr work for us. Somebody else should confirm that.

Repeat: do not download anything with "JFeur" in the file name!

Sent from my SCH-R970 using Tapatalk 4 Beta

Unless I messed up some how, neither the vzw or sprint kernels worked. Again, it could very well be user error though.
All sprint kernels work I can vouche for that. However the Verizon do not.

Sent from my SCH-R970 using Tapatalk 2

What did I do wrong then? What's your process of flashing the sprint one? Which file did you flash?

Sent from my SCH-R970U using Tapatalk 4 Beta

There isn't a sprint chronic... However always flash kernel after flashing ROM. Or load ROM then reboot an flash kernel

..

Sent from my SCH-R970 using Tapatalk 2

Share this post


Link to post
Share on other sites

Yeah did not intend to jump on anyone, as far as I knew international kernels would cause major issues, I assumed OP was using one built for US devices and forgot to say something so I made my post to make sure other people knew the risks.

Sent from my SCH-R970 using Tapatalk 4 Beta

Share this post


Link to post
Share on other sites

So the international Chronic kernel is safe to flash then, if I read everything correctly?

Yes.

Sent from my SCH-R970 using Tapatalk 2

Share this post


Link to post
Share on other sites

I guess I should have said the jFer version.

 

Cool flashing it right now and I'll see how it goes. 

Share this post


Link to post
Share on other sites

Flashed it, and I have to say it's very responsive.

 

Thanks Gr33n for the find, and your help.

Share this post


Link to post
Share on other sites

Flashed it, and I have to say it's very responsive.

Thanks Gr33n for the find, and your help.

Anytime

Sent from my SCH-R970 using Tapatalk 2

Share this post


Link to post
Share on other sites

Greeny, can you try the JFeur Faux kernel? He's one of the most respected kernel developers.

Sent from my SCH-R970U using Xparent Skyblue Tapatalk 2

Edited by HikingMoose

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now