Root [KERNEL] TheOC v1.7.20 kernel for MT Isaac & TG based CM7

[mantera]

Disclaimer: By downloading and installing this kernel, you are assuming all risk. There are no implied warranties of any kind.

It seems to be working for me but try this at your own risk... Don't come crying to anyone here if you fry your phone... Don't overclock if you don't feel comfortable taking the risk!

This kernel is based on Tickerguy's latest kernel in the 11-19 build with the OC tables and the minmax and smartassv2 makefiles from Isaac merged in.

Instructions:

Flash Zip file in CWM.

File (see changelog at end of post):
TheOCv1.7.20.zip

TheOCv1.7.20.zip

TheOCv1.7.19.zip

TheOCv1.7.19.zip

kernel_orig_cm7-11-19.zip - the original boot.img from the cm7 11-19 build in case you bootloop and want to restore the original

http://tinyurl.com/7hfuoap

Here's a link to a pretty good description of what seems to be most or all of the known available governors and IO schedulers in use in Android kernels by knzo at xda:
[REF] Quasar kernel governors and I/O schedulers manual - xda-developers

Governors:
His summary:
(in my (knzo's) humble opinion)

• Battery: 1st place - InteractiveX | 2nd place - Smartass | 3rd place - SavagedZen
• Performance: 1st place - Minmax | 2nd place - Smartass2 | 3rd place - SavagedZen

IO Scheduler:
To sum up:
(in my (knzo's) humble opinion)

• Performance: 1st place - VR
• Reliability: 1st place - Simple

changelog:
TheOCv1.7.20.zip
-reverted commit that prevented 2 sensors from grabbing wakelocks. Seemed to be causing sensors to not be able to grab wakelocks sometimes.

TheOCv1.7.19.zip
Just a small update
-kernel patched to version 2.6.32.21
-includes most of Whyzor's kernel updates
-uses Whyzor's latest touchscreen driver
-changed default io scheduler to sio
-changed default goveror to interactive
-using same gpu drivers as in cm9

TheOCv1.6.14.zip
http://tinyurl.com/cda83jn
- Fixed Interactive governor. SHOULD work now.
- reduced Interactive governor transition latency so it will transition faster.
- added Whyzor's wakelock fix to try and prevent times when deep sleep mode is never entered.
- disabled 184 MHz frequency.

TheOCv1.6.11.zip
- added 2way calling patch. Thanks to avs333 for the patch and DoomLord for the port of the patch.

Need to use CallRecorder app from skvalex or rVoix.apk from avs333. More info can be found on this thread on xda:
[DEV] Two-way call recording on Desire [ALMOST SOLVED][Sept. 7 update] - xda-developers

Here's the post by skvalex listing his latest trial version of CallRecorder:
xda-developers - View Single Post - [Android 2.2+] CallRecorder - record phone calls from the phone line

Here's the market link for CallRecorder:
https://market.android.com/details?id=com.skvalex.callrecorder

I tested the CallRecorder app and the sound quality was excellent for a recording--if you're into that sort of thing. I did not test the rVoix.apk yet at this time.

- enabled 61 MHz and 184 MHz clock frequencies.
- updated Interactive governor with all of the latest updates from CM.
- Added lower voltage regulator settings down to 600. It looks like 600 is the min that our boards can go from what the specs look like.
- changed default IO scheduler to NOOP.
- reverted memcopy update.

TheOCv1.5-wip-2.zip
http://tinyurl.com/7ed2wft
- added Isaac's updated touchscreen driver
- enabled swap file support
- added memcopy update and memory management tweak

TheOCv1.1-wip1.zip
http://tinyurl.com/7lywxpa
- Updated for Tickerguy CM7 11-19 build, WIFI AP now works properly
- added a few more governors: InteractiveX, Scary, smartass, SavagedZen

TheOCv1-wip-4.zip
- Added I/O schedulers cfq, vr, and sio. Go ahead and try them out if you want. I was able to set them using No Frills CPU control -- available free on the market. I tested running lots of quadrants and deadline still seemed the fastest on average than the rest but ymmv.
- Enabled detailed frequency translation statistics just so I can see the detailed stats of frequency usage.
-Added SVS for voltage control. You can set the voltage in one of 3 ways:
1. manually edit the vdd_levels file in /sys/devices/system/cpu/cpu0/cpufreq/ using either adb or a file manager.
2. Set up a script and put it into init.d to set the file upon boot.
3. The simplest way - use the IncrediControl app to set the voltage. You can read about it from this post on xda and a download link is also provided there or download it from the Market:
[MOD] IncrediControl - Easy GUI Undervolting - xda-developers
Thanks to b_randon14, chad0989, DoomLord, and Napstar whose code, posts, links and info helped a lot as well as the million posts from everyone that I read over the last few days...

- I'm using the following undervolt table on my phone in IncrediControl and it seems pretty stable; try out your own settings and see. The higher frequencies > 1.7 GHz would not undervolt for me without locking up and rebooting but your phone might fare better. I suggest that you DO NOT APPLY the settings on Boot until you are sure your phone is stable.

***If you undervolt too much and hose your phone, you can download this flashable zip in CWM to reset the Incredicontrol settings. Zip was provided by Incredicontrol site that is linked and I updated the script for the Triumph.

http://tinyurl.com/7g26rtp

more aggressive undervolting table:

   61440:  700
  122880:  700
  184320:  750
  245760:  775
  368640:  800
  460800:  875
  576000:  925
  652800:  975
  768000:  975
  806400: 1075
  921600: 1125
 1024000: 1175
 1113000: 1175
 1209600: 1175
 1305600: 1225
 1401600: 1225
 1516800: 1275
 1612800: 1275
 1708800: 1350
 1804800: 1400
 1900800: 1475
 2016000: 1500

less aggressive:

 61440:  750
122880:  800
184320:  800
368640: 850
460800: 900
576000: 950
652800: 1000
768000: 1000
806400: 1075
921600: 1125
1024000: 1175
1113000: 1175
1209600: 1175
1305600: 1225
1401600: 1225
1516800: 1275
1612800: 1275
1708800: 1350
1804800: 1400
1900800: 1475
2016000: 1525

TheOCv1-wip-3.zip
http://tinyurl.com/buotbqt
-set default max freq to 1024 MHz - hopefully oddball phones will now boot - thanks to b_randon and pwnyourace for the advice
-added 2 GHz frequency line - thanks to b_randon14, DooMLoRD, Napstar and FPX

TheOCv1-wip-2.zip
http://tinyurl.com/bmhxl7z
-Changed default governor to OnDemand
-turned off kernel debugging

TheOCv1-wip-2.zip
Original kernel

Thanks goes to: Issacj87, Tickerguy, DooMLoRD, Napstar, b_randon14, FPX, pwnyourace, avs333, and the Tiamat devs.

source:
https://github.com/mantera/WX_435_Kernel-CM7

In case anyone feels like it:

to mantera​

 

[JollyRoger87]

Lol I knew it was just a matter of time

 

[bing7625]

So glad I asked u to post this.

 

[isaacj87]

I'll bring my CM-OC branch in line with TG's kernel so you don't have to merge code from here on out.

 

[nullwake]

Beautiful work.

 

[streetpounder]

3500 at a nice leisurely 1.4GHz. Thanks a million!

 

[idbl_fanatic]

Everything was good for me, till I tried to push it to 1.9. LOL, had to do a restore.

Thanks for the kernel.

 

[tickerguy]

You're lucky you still have a working processor if you tried to crank it to 1.9.

 

[AtticTRON]

Any way we can get this to work with MIUI?

 

[marc12868]

After I flashed it I just got stuck in a bootloop so I flashed the original. Anyone have any ideas why? Ill try again and see if I can get it to boot.

 

[Chairshot215]

Is it ok to run the chainfire3d driver overclocked with this kernel? I ask because the app says it’s for 1g processor phones, not sure if overclocking technically makes it not a 1g processor for the purpose of this app.



Also, I am running at 1.5 with a but-load of setCPU profiles that includes scaling the frequency down at 35c to 1.2 & down to 1 at 40c. Also have screen off at 768 and 1 during calls. First time overclocking and am slightly terrified and would greatly appreciate a thumbs up or down regarding these settings.



Otherwise big ups to Mantera as I just got a 2900 quadrant score and my phone is flying. Outlook on life, positive.

 

[shimdachef]

After I flashed it I just got stuck in a bootloop so I flashed the original. Anyone have any ideas why? Ill try again and see if I can get it to boot.

Same here

 

[idbl_fanatic]

Same here

You guys may have one of the "odd ball" ones

 

[marc12868]

You guys may have one of the "odd ball" ones

Do you mean an "oddball" phone?

 

[idbl_fanatic]

Do you mean an "oddball" phone?

There was a problem when a kernel was first created with this phone, and he referred to them as "odd balls" not sure what it was, or how to fix it.

 

[marc12868]

There was a problem when a kernel was first created with this phone, and he referred to them as "odd balls" not sure what it was, or how to fix it.

Dang... well when I was still on stock I did have to use the oddball umph kernel since the normal one didn't boot...

 

[tusing]

Any chance of porting this to MIUI?

 

[ziggy46]

we shouldnt have that problem anymore... since we all (on this thread) are running cm7. which required us to format our systems before flashing, resulting in all of us having that same system now. so we should all be compatible for these kernels.

 

[mantera]

I think the problem is because I accidentally left the default governor in my testing to Performance. I'll rebuild this when I get home and set it to another governor as default.

 

[ziggy46]

You're lucky you still have a working processor if you tried to crank it to 1.9.

mine can run at 2 ghz without getting hot (tested playing nfs shift for 30mins)

 

[thangfish]

I think the problem is because I accidentally left the default governor in my testing to Performance. I'll rebuild this when I get home and set it to another governor as default.

I noticed it defaulted to the Performance gov, but it didn't cause a problem for me. Thanks for taking the time to do this. Special ups to tg and Isaac.

 

[bing7625]

I think the problem is because I accidentally left the default governor in my testing to Performance. I'll rebuild this when I get home and set it to another governor as default.

when you rebuild it can you include the 2ghz setting for poops and giggles? mine runs fine at 1.9 all day long and i'd like to see what quads i get at 2. I mean anyone whose phone can't run at 2ghz doesn't have to push the cpu to that limit. anyhow thanks for this!!!!

 

[tusing]

when you rebuild it can you include the 2ghz setting for poops and giggles? mine runs fine at 1.9 all day long and i'd like to see what quads i get at 2. I mean anyone whose phone can't run at 2ghz doesn't have to push the cpu to that limit. anyhow thanks for this!!!!

It's not that people's phones can't run at 2 GHz. It's that people simply won't, because running at 2GHz will fry the processor. It's a stupid thing to do. You will end up with a worse processor than you started with. It's like destroying your phone for shits and giggles.

 

[ziddey]

It's not that people's phones can't run at 2 GHz. It's that people simply won't, because running at 2GHz will fry the processor. It's a stupid thing to do. You will end up with a worse processor than you started with. It's like destroying your phone for shits and giggles.

You're funny.

OP, thanks

 

[bing7625]

It's not that people's phones can't run at 2 GHz. It's that people simply won't, because running at 2GHz will fry the processor. It's a stupid thing to do. You will end up with a worse processor than you started with. It's like destroying your phone for shits and giggles.

well technically you're wrong considering many people have posted about being able to set their cpu to 1.9, but when they do they get stuck in boot loops and have a multiplicity of other problems that prevent them from setting it so high, and therefore have to flash back to previous builds or nandroids. and can't throttle up to even 1.9 like idbl_fanatic can't.... if you read on here he even stated when he goes to 1.9 he had to do a restore because stuff started happening... therefore some phones CANNOT run above certain speeds.....

oh ya and they're called "oddball" phones, and people have been having problems with these from day one even when OCing on stock Froyo.