Root [KERNEL] mOCk kernel v1.7.14 for MIUI (released)

[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 is based on Isaac's latest kernel code in his MIUI build with the OC tables and Voltage controls as in the CM7 kernel. All credit goes to Isaac, Tickerguy, b_randon14, Napstar, DoomLord, and the CyanogenMod team. If I missed anyone, let me know and I'll add it.

Instructions:

Flash Zip file in CWM.

mOCkv1.7.14.zip
mOCkv1.7.14.zip

changelog:
mOCkv1.7.14.zip
A small update to bring this kernel in line with the cm9 kernel.
-Linux version 2.6.32.59
-updated to latest whyzor touchscreen driver
-includes most of Whyzor's kernel updates
-changed default io scheduler to sio
-changed default goveror to interactive
-does NOT use the same kgsl drivers as in the cm9 kernel. They decreased the performance in this GB miui.

mOCkv1.6.12.zip
mOCkv1.6.12.zip
- Allocated the extra memory to the GPU so HD games will play properly
- Updated Interactive governor with all of the latest updates from CM
and reduced the transition latency so it will transition faster.
- added Whyzor's wakelock fix to try and prevent times when deep sleep mode is never entered.
- added 2way calling patch. Thanks to avs333 for the patch and DoomLord for the port of the patch. I know that MIUI already has in-call recording but if you were using another ROM and already had the app, you can now use it in MIUI also.

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 - [DEV] Two-way call recording on Desire [ALMOST SOLVED][Sept. 7 update]

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 clock frequency.
- 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.

mOCkv1.5-wip-6.zip
http://tinyurl.com/c74vzlj
- Updated for MIUI 1.11.25-11-30-11 build. Native WIFI AP should work properly.
- added a few more governors: InteractiveX, Scary, smartass, SavagedZen
- memory tweaks
- tweaked vmalloc allocation slightly - not as much as Isaac's HD fix though- so there should still be more available memory
- added Isaac's updated touchscreen driver

mOCkv1-wip-4.zip
http://tinyurl.com/c999gva
It's basically the same as the cm7 kernel but for MIUI.

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

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:
http://forum.xda-developers.com/showthread.php?t=1242323

Governor:
To sum up:

(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

-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 Voltage Control - 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:  675
  122880:  700
  245760:  750
  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 table:

 61440: 800
122880: 800
245760: 850
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

-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
-Changed default governor to OnDemand
-turned off kernel debugging
-added tun.ko support
-added cifs support as a module
-the cifs.ko module that you can unzip and copy to /system/lib/modules using adb or es file explorer or another file manager with root read/write access can be downloaded from here:
http://tinyurl.com/6rg4hqx

source:
https://github.com/mantera/triumph-kernel-msm7x30

 

[bigvandal]

Looks interesting

 

[tusing]

THANK GOD! I was waiting for this!

What is the point of controlling the voltage? Can you overclock higher?

Also, what makes the Deadline governor different? I know Smartass is dynamic clock control to save battery, so what's Deadline?

 

[Mobstergunz]

THANK GOD! I was waiting for this!

What is the point of controlling the voltage? Can you overclock higher?

Also, what makes the Deadline governor different? I know Smartass is dynamic clock control to save battery, so what's Deadline?

Undervolting is a way to get more battery life out of your phone if you combine that with Overclocking the phone's battery wont drain so fast

 

[tusing]

Undervolting is a way to get more battery life out of your phone if you combine that with Overclocking the phone's battery wont drain so fast

Thanks! Is there any effect on overall performance?

Also, you said "coming soon". Does that mean today, in a few days, weeks?

*continues refreshing*

 

[Mobstergunz]

Thanks! Is there any effect on overall performance?

Also, you said "coming soon". Does that mean today, in a few days, weeks?

*continues refreshing*

If you undervolt too low you might lose some stability and have reboots. For me I'm going to try the volt table mantera posted.

EDIT: This is nice i get quadrant scores around 4000 undervolted and overclocked to 2ghz with smartassv2 and vr scheduler gonna keep it at 1.4ghz though

 

[tusing]

If you undervolt too low you might lose some stability and have reboots. For me I'm going to try the volt table mantera posted.

EDIT: This is nice i get quadrant scores around 4000 undervolted and overclocked to 2ghz with smartassv2 and vr scheduler gonna keep it at 1.4ghz though

Nice! That's comparable to the Galaxy S2!

 

[tusing]

Got 2449 at 1.7 GHz on my Triumph. Is that a normal score? Seems pretty high to me!

 

[viperafx]

Got 2449 at 1.7 GHz on my Triumph. Is that a normal score? Seems pretty high to me!

after a few runs i can get 3100 sometimes without overclocking...try rebooting and doing a app kill right away and then run quad 2 times what u get the 2nd time

 

[Mobstergunz]

Got 2449 at 1.7 GHz on my Triumph. Is that a normal score? Seems pretty high to me!

make sure all running apps are closed and try a setup like this - 1.7ghz, smartassv2 or performance governor, and vr scheduler score should be pretty high

EDIT: 2ghz if your phone can

 

[isaacj87]

Got 2449 at 1.7 GHz on my Triumph. Is that a normal score? Seems pretty high to me!

What governor? It should be higher than that. I have a kernel that maxes out at 1.4 GHz and I pull 3500.

Also, take out the SDCARD to get the best speed. I added a tweak to increase the read ahead speed on the SDCARD, but you'll get the best results when the card isn't in there.

 

[tusing]

My phone is very heavily themed. Also, I usually have quite a few background apps; it seems they keep on coming back when I kill them.

I ramped up Autokiller to the highest settings. Here's what I got on Performance / 1.7 GHz

With SD Card: 2774

Without SD Card: 3210

Defective processor?

 

[Mobstergunz]

My phone is very heavily themed. Also, I usually have quite a few background apps; it seems they keep on coming back when I kill them.

I ramped up Autokiller to the highest settings. Here's what I got on Performance / 1.7 GHz

With SD Card: 2774

Without SD Card: 3210

Defective processor?

try force stopping them in settings manage applications they'll stay closed that way also stop maps and market

EDIT: in autokiller try extreme preset and in advanced system tweaks turn on memory management

 

[tusing]

make sure all running apps are closed and try a setup like this - 1.7ghz, smartassv2 or performance governor, and vr scheduler score should be pretty high

EDIT: 2ghz if your phone can

EDIT: NVM found it.

 

[isaacj87]

My phone is very heavily themed. Also, I usually have quite a few background apps; it seems they keep on coming back when I kill them.

I ramped up Autokiller to the highest settings. Here's what I got on Performance / 1.7 GHz

With SD Card: 2774

Without SD Card: 3210

Defective processor?

Defective? No, lol.

I'm not sure why your score is so "low." 3210 seems like a respectable score to me. Try some of the other benchmarking apps while you're at it.

 

[Mobstergunz]

Defective? No, lol.

I'm not sure why your score is so "low." 3210 seems like a respectable score to me. Try some of the other benchmarking apps while you're at it.

i agree it cant be defective try smartbench 2011 or global quadrant rank

 

[tusing]

LOL I scored a 1337 in Global Quadrant. Coincidence? I think not.

 

[isaacj87]

LOL I scored a 1337 in Global Quadrant. Coincidence? I think not.

Believe it or not, that's actually my apartment number.

 

[tusing]

Believe it or not, that's actually my apartment number.

Not a coincidence either!

On Topic: the max I can seem to get in quadrant is 3150 or so. Must be my phone, I can live with that I guess.

 

[mantera]

Not a coincidence either!

On Topic: the max I can seem to get in quadrant is 3150 or so. Must be my phone, I can live with that I guess.

Are you undervolting? If you are, that could be affecting the scores slightly. Try at the default voltages if you are.

Edit: One more thing I just remembered. If you're trying to benchmark or stress test, I'd recommend that you change your governor to Performance while you're running your benchmarking. It'll give you the most consistent results since your phone won't be trying to downclock while running tests.

 

[tusing]

Are you undervolting? If you are, that could be affecting the scores slightly. Try at the default voltages if you are.

Edit: One more thing I just remembered. If you're trying to benchmark or stress test, I'd recommend that you change your governor to Performance while you're running your benchmarking. It'll give you the most consistent results since your phone won't be trying to downclock while running tests.

Yeah, I undervolted

 

[bigvandal]

Everything a OK with the kernel? excited to go home and try this out

 

[mantera]

Everything a OK with the kernel? excited to go home and try this out

I've been running this for the last 2 or 3 days and have not run into any issues yet.

 

[mantera]

Added info on governors and io schedulers in OP:

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:
http://forum.xda-developers.com/showthread.php?t=1242323

His summary:
To sum up:
(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

 

[johnburtjab]

some info i found on undervolting if anybody wants to know. i found it very interesting! this actually was for computers but applies to pretty much any processor
The "Undervolting" Guide

Thanks for the kernel btw!!!