[Kernel][CM7][CM9][MIUI][CTMOD/H.A.R.] Kato Kernel Beta 0.4 - Overclocked 946MHz[Update 3/30/12]

Last Updated:

  1. trenchkato

    trenchkato Well-Known Member


    Thanks to: Hroark13, zcop, Koumajutsu, The~Skater~187, PlayfulGod, thachtunganh, Shabby and Interdepth. And the crash test dummies for putting their hardware in harms way Johnny424, Wetbiker7, thomasmbl, Slayer72.

    DISCLAIMER: Extremely low or higher than normal frequencies may freeze your phone. Especially high frequencies (such as those enabled in certain custom kernels) have a risk of shortening the life of your phone. If your phone freezes, just yank out the battery. I CAN NOT BE HELD RESPONSIBLE FOR ANY DAMAGE THIS KERNEL MAY DO TO YOUR PHONE.

    I have made a kernel that has been overclocked from 800MHz to 944Mhz (I was able to play angrybirds space with no lag, no reboots). Everyones phone is different an will respond as such to this kernel.

    Our cpu Qualcomm S1 MSM7627-3 is recommended at a 600mhz (stock 800 speed could technically be seen as an overclock) so I would like to progress slowly upwards in frequency... hopefully twards 1000mhz

    For information on what each IOScheuler and CPU Governor does
    [REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs - xda-developers
    Thanks to The~Skater~187 for this info :cool:

    1. Make sure you have a working version of cm7, cm9, or MIUI (if you are coming from another ROM allow the ROM to boot first!)
    2. Reboot into Recovery mode
    3. Flash the respective .zip
    4. Reboot
    5. Use Voltage Control to change your CPU governor to "Ondemand (or whatever you see fit)

    **I cant stress enough, Make sure your ROM boots before adding this kernel**

    Note: This kernel is based on the cm7 mapfix kernel. There is no need to install it. If you do it will remove oc


    Version 0.4
    Changed max frequency to 946MHz (Improved stability)
    Added I/O Scheduler -> Cfq
    Tweeked OC script
    Changed CPU Governor polling to 50 ticks (hopefully improves stability by increasing time between frequency changes)
    Added Active Voltage Selection ::shrugs::
    Added sd-ext version for CM7
    Default frequency 800MHz
    Changed default I/O scheduler to S(IO)

    Version 0.3:
    Added clocking slots up to 944Mhz
    Added I/O Schedulers > V(R) and S(IO)
    Added CPU Governors > Brazillianwax, interactive, scary, lazy, smoothass, savagedzen, interactivex, lagfree, minmax, smarassV2, and Lionheart

    Version 0.2:
    Updated to kernel version
    Resolved bootloop some users were experiencing
    Cleaned script and added parts from thachtunganh's script.
    Added clocking slots up to 900MHz
    Removed 19MHz slot (19MHz can still be used for power collapse if you have it enabled in your build.prop)

    Version 0.1
    Initial Release

    I would like testers to file reports in this format:
    Battery life:
    Phone temperature:


    The CTMOD/STOCK (halfassed ROM) kernel is nothing more than a kanged KoumaKernel 2.3
    to configure sd-ext support you must visit his thread: http://androidforums.com/galaxy-prevail-all-things-root/429740-kernel-gb-koumakernel-2-3-a.html


    CM7 with sd-ext: Kato Kernel Beta 0.4 for CM7 with sd-ext
    CM7 without sd-ext: Kato Kernel Beta 0.4 for CM7 without sd-ext
    CM9/MIUI without sd-ext: Kato Kernel Beta 0.4 for CM9/MIUI
    CTMOD/HalfAssedROM: Kato Kernel Beta 0.4 for CTMOD and HalfAssedROM

    Old Releases

    Beta 0.3
    CM7: Kato Kernel Beta 0.3 for CM7
    CM9 and MIUI: Kato Kernel Beta 0.3 for CM9 and MIUI

    Beta 0.2
    CM7: Kato Kernel Beta 0.2 for CM7
    CM9 and MIUI: Kato Kernel Beta 0.2 for CM9/MIUI

    creed10, ARocker, clyde4210 and 22 others like this.
  2. hroark13

    hroark13 Well-Known Member Developer

    nice job

    I have not tested it yet, but I will

    any chance I can see your source code ?
  3. PhoneMan93

    PhoneMan93 Well-Known Member

    only cm7?
  4. hroark13

    hroark13 Well-Known Member Developer

    is this kernel for stock, CT, CM7, or CM9

    I see that it is

    have you seen this yet


    I have patched that kernel to

    does you kernel have the MAPS fix in it?

    I am glad you have done this, very cool
  5. PhoneMan93

    PhoneMan93 Well-Known Member

    hey don't be stealling my questions man lol
    mine was a compressed version of your question
  6. trenchkato

    trenchkato Well-Known Member

    Only cm7 for now. I could make a kouma 1.3 but I didn't because it is such a old version.

    @hroark I will share my source when I make it back home
    J6Remy likes this.
  7. PhoneMan93

    PhoneMan93 Well-Known Member

    thanks man!
  8. J6Remy

    J6Remy Well-Known Member

    Epic man, epic!.. I might flash to CM7 to check it out! I'm stoked...
  9. hroark13

    hroark13 Well-Known Member Developer


    i will help you make versions for CT and stock if you want
  10. Koumajutsu

    Koumajutsu Well-Known Member

    i could zip up my KK2.2 folder for you too, if you wanted it
  11. trenchkato

    trenchkato Well-Known Member

    No problemo

    No mapfix. this comes directly from the hkpf. i coulndt figure how to get from github without breaking hkpf. EDIT: nvm I figured it out

    Sure send it on over

    Check your pm (I cant send you a pm...)

    Matter o' fact I think that it is time to update your kernel factory lol
  12. hroark13

    hroark13 Well-Known Member Developer

    the only problem that I see with updating it is that when we use any other kernel string than

    we have to hex edit the FSR and RSF modules

    I was able to find other modules that work with a longer string name but it has to be exactly 12 characters
  13. johnny424

    johnny424 Well-Known Member

    hey kato does it matter if were using beta 4?... i imagine any cm7 kernel should be fine?

    i was wondering if this was gonna happen...great job bro..big things happening around here:D
  14. It makes my fone keep restarting
  15. trenchkato

    trenchkato Well-Known Member

    Havent tested with beta 4... I would defer to hroark on that one...
  16. trenchkato

    trenchkato Well-Known Member

  17. johnny424

    johnny424 Well-Known Member

    Ill test it now and post back..for anyone still using beta 4
  18. Koumajutsu

    Koumajutsu Well-Known Member

    I found that the RFS modules seem to load and run, but can't/won't mount our device
  19. 1kyon1

    1kyon1 Member

    I don't know if this happens to other people but when I start a song using a music player (google play music) I hear a pop on my head phones then it reboots :/
  20. hroark13

    hroark13 Well-Known Member Developer


    well the only ROM that is still using RFS is the pure stock ROMs I think

    so basically we have to keep the string if we want RFS

    but I really do not want or need RFS support in any of my ROMs
  21. johnny424

    johnny424 Well-Known Member

    Confirmed-OC Kernel works on Beta4..

    Wiped cache and dalvik before flashing .. no problems except when i booted up Titanium Backup had frozen the market for some reason..had to unfreeze to use market..everything els is good so far

    Edit- Dont think kernel will work on b4..after first reboot phone bootloops
  22. Koumajutsu

    Koumajutsu Well-Known Member

    yeah, RFS is junk
    I built some YAFFS drivers because some people were wanting to build roms based on the older FS, but I found no way to test it.

    You use flash_eraseall to format a device as yaffs, and it requires a character device. The FSR drivers seem to only support Block mode.
    I'm thinking of trying the onenand driver since it's claimed that it's FSR turned Opensource, but they don't seem to work for block mode
  23. trenchkato

    trenchkato Well-Known Member

    EDIT: Screnshot taken down

  24. hroark13

    hroark13 Well-Known Member Developer

Share This Page