Jump to content

  1. 0
  2. 0
  3. 0/5

Rate this Topic

* * * * -
6 votes

OPPtimizer Projekt - Milestone Overclock for OMAP4 Devices

Overclocking Kernel Module
  • Please log in to reply

OP tekahuna

tekahuna

teh-kuh-hoo-nuh Overclocking & Tether Guy

Posted 07 January 2012 - 01:35 PM #1

Mod Type:: Kernel Module

Difficulty:: Moderate

Mod Status:: Stable

Apply In:: CWM Recovery

Optional:: Overclocked

Requires Root:: Yes

Optional:: Overclocked

Source:: http://www.github.co...stone_overclock
Milestone Overclock 1.5 Kernel Modules for OMAP4 Devices

Aloha Kakou,

Here we have Overclocking Kernel Modules for OMAP4 devices. These modules are based off of nadlabak & Skrilax_CZ's simplified Milestone Overclock module for CM7 on Motorola Milestone, which itself is an offshoot of Milestone Overclock by Tiago Sousa. To accomplish the task of accessing the structures that hold frequency and voltage data, I've made use of SYMSEARCH by Skrilax_CZ. The rewriting(90%+ new code) of Milestone Overclock for OMAP4 kernel 2.6.35-7 was done by myself, tekahuna.

For more information, please visit: http://opptimizer.googlecode.com

*** Please Support this Projekt by Following me on Twitter, and if you're able to, by donating ***

Aloha,
tekahuna


Current Version: 1.5

Supported Devices:

Motorola Droid RAZR/RAZR MAXX
Motorola Droid 4
Motorola Bionic
Motorola Atrix 2
Motorola Droid 3/Milestone 3
Motorola Xyboard/Xoom2

LG Thrill 4G
LG Optimus 3D

Samsung GT-I9100G

Barnes & Noble Nook Table

Amazon Kindle Fire


Known Bugs/Issues:

- On LG Thrill/Optimus 3D, certain frequencies will cause the SmartReflex to complain about mismatched frequecies. Verifiable with "dmesg" This is an issue with its early 2.6.35-7 kernel not rounding a certain value. Sticking to even numbers like 1150, 1180 or 1200, will help to avoid this issue. Do run "dmesg" on these devices when testing new a frequency to be sure you don't have this issue.


Installation:

1. Download the latest mo_simp_1.5.x_YOUR_DEVICE.zip from:
http://code.google.c.../downloads/list

2. Flash in Clockwork Recovery

Optional for Motorola Devices:
3. If your ROM does not have init.d support, download this file and flash from CWM Recovery.
moto_init_d-signed.zip

*** note, this will remove any old kernel modules, or init.d script you may have. Backup your old init.d script before flashing.


Basic Usage:

These are the basic terminal commands, to be entered as Root or "su". The Milestone Overclock interface exists as four individual file located at /proc/overclock/*

Switch to SuperUser(All commands must be done as Super User, switch from the $ to the #):
$ su

Read all current settings(useful for verifying that the frequency table and opp tables match):
# cat /proc/overclock/*

//RAZR Stock
freq_table[0] index=0 frequency=300000
freq_table[1] index=1 frequency=600000
freq_table[2] index=2 frequency=800000
freq_table[3] index=3 frequency=1000000
freq_table[4] index=4 frequency=1200000
cpumin=300000 cpumax=1200000 min=300000 max=1200000 usermin=300000 usermax=1200000
clk_get_rate=300000
mpu_opps[5] rate=1200000000 opp_id=5 vsel=61 u_volt=1375000
mpu_opps[4] rate=1000000000 opp_id=4 vsel=61 u_volt=1374000
mpu_opps[3] rate=800000000 opp_id=3 vsel=55 u_volt=1313000
mpu_opps[2] rate=600000000 opp_id=2 vsel=43 u_volt=1200000
mpu_opps[1] rate=300000000 opp_id=1 vsel=26 u_volt=1025000
1.5-mapphone-yokohama

//Droid3, Bionic, Atrix2 Stock
freq_table[0] index=0 frequency=300000
freq_table[1] index=1 frequency=600000
freq_table[2] index=2 frequency=800000
freq_table[3] index=3 frequency=1000000
cpumin=300000 cpumax=1000000 min=300000 max=1000000 usermin=300000 usermax=1000000
clk_get_rate=300000
mpu_opps[3] rate=1000000000 opp_id=3 vsel=61 u_volt=1375000
mpu_opps[2] rate=800000000 opp_id=2 vsel=55 u_volt=1313000
mpu_opps[1] rate=600000000 opp_id=1 vsel=43 u_volt=1200000
mpu_opps[0] rate=300000000 opp_id=0 vsel=26 u_volt=1025000
1.5-mapphone-yokohama

Read just mpu_opps info:
# cat /proc/overclock/mpu_opps
// RAZR stock
mpu_opps[5] rate=1200000000 opp_id=5 vsel=61 u_volt=1375000
mpu_opps[4] rate=1000000000 opp_id=4 vsel=61 u_volt=1374000
mpu_opps[3] rate=800000000 opp_id=3 vsel=55 u_volt=1313000
mpu_opps[2] rate=600000000 opp_id=2 vsel=43 u_volt=1200000
mpu_opps[1] rate=300000000 opp_id=1 vsel=26 u_volt=1025000

////Droid3, Bionic, Atrix2 Stock
mpu_opps[3] rate=1000000000 opp_id=3 vsel=61 u_volt=1375000
mpu_opps[2] rate=800000000 opp_id=2 vsel=55 u_volt=1313000
mpu_opps[1] rate=600000000 opp_id=1 vsel=43 u_volt=1200000
mpu_opps[0] rate=300000000 opp_id=0 vsel=26 u_volt=1025000

Write Frequency & Voltage(format: echo <opp_id> <freqquency_in_hz> <uV_voltage> /proc/overclock/mpu_opps):
***note: The max operating spec of most voltage regulators is 1400000uV***
// Change top frequency/voltage on RAZR
# echo 5 1255000000 1390000 > /proc/overclock/mpu_opps

//to verify
# cat /proc/overclock/mpu_opps

mpu_opps[5] rate=1255000000 opp_id=5 vsel=62 u_volt=1390000
mpu_opps[4] rate=1000000000 opp_id=4 vsel=61 u_volt=1374000
mpu_opps[3] rate=800000000 opp_id=3 vsel=55 u_volt=1313000
mpu_opps[2] rate=600000000 opp_id=2 vsel=43 u_volt=1200000
mpu_opps[1] rate=300000000 opp_id=1 vsel=26 u_volt=1025000

* note: Voltage can be set as a VSEL or uV value. Max VSEL for Motorola devices is 63.

Motorola VSEL Values:
63 = 1400000
62 = 1390000
61 = 1380000
60 = 1370000
59 = 1360000
58 = 1350000

Set GPU Frequency(valid values, 256000000, 307200000, 384000000):
# echo 384000000 > /proc/overclock/gpu_opps

Load Modules(this kind of isn't necessary anymore, but none the less, always load symsearch.ko first):
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/overclock.ko


Loading at Boot/Scripts:

The new update.zip's will install a basic init.d script to "/system/etc/init.d/00opptimize". If you've found settings that are "stable" for your device, and you'd like to run these at boot, you may edit this file accordingly. Be default, this script only loads the kernel modules. This requires your ROM to have init.d support to work. If you cannot find a method of getting init.d working, you can use Script Manager to execute this file at boot.

This file should only contain stable setting. If you're trying to hit 2.0GHz, I suggest using terminal, or a script via Script Manager that isn't run at boot to make the adjustment.


Other Notes:

You can play around with this in Quickclock Advanced to Stress Test, edit Frequency and VSEL(go to Advanced, then enable Full Editing to edit VSEL), and save your settings to profiles. ***Calibrations, and Enabling on Boot DO NOT WORK*** Trying to enable on boot will force you to clear App data to open QuickClock again. The calibration routine tries to load kernel module for a different device and freezes the app. Android Overclock just doesn't recognize it at all.


Attention Devs:

Please, No Mirroring or RePackaging of binaries. Rather, Apps/Scripts should download modules and unpackage from the http://opptimizer.googlecode.com site. Also, notification of the download, and a link to the OPPtimizer Projekt site, for further support/bug reporting of the kernel modules would be helpful to users.

Edited by tekahuna, 04 March 2012 - 10:26 AM.

  • 13 Likes

OP tekahuna

tekahuna

teh-kuh-hoo-nuh Overclocking & Tether Guy

Posted 07 January 2012 - 01:36 PM #2

Useful Links:
Howto: Activating Both Cores in Performance, OnDemand, and Userspace Governor by razz1

Edited by tekahuna, 29 February 2012 - 10:57 PM.

  • 1 Likes

OP tekahuna

tekahuna

teh-kuh-hoo-nuh Overclocking & Tether Guy

Posted 07 January 2012 - 01:36 PM #3

three

Edited by tekahuna, 29 February 2012 - 02:40 PM.

  • 1 Likes

OP tekahuna

tekahuna

teh-kuh-hoo-nuh Overclocking & Tether Guy

Posted 07 January 2012 - 01:36 PM #4

four
  • 0 Likes

OP tekahuna

tekahuna

teh-kuh-hoo-nuh Overclocking & Tether Guy

Posted 07 January 2012 - 01:37 PM #5

5, I was born in may...
  • 0 Likes

frostincredible

frostincredible

Teenage Hacker >:)

Posted 07 January 2012 - 04:07 PM #6

Testing in a few minutes! Out of curiosity, will the changed clock speed be visible in apps such as SetCPU? Or will those still display 1GHz as the fastest?
  • 0 Likes
Device: iPhone 5 32GB, Nexus 7
Current ROM: Custom AOSP

Patgt500

Patgt500

Member

  • 44 posts

Posted 07 January 2012 - 06:23 PM #7

Sorry to steal your thunder Tekahuna, but I just couldn't help myself.
  • 0 Likes

Patgt500

Patgt500

Member

  • 44 posts

Posted 07 January 2012 - 06:37 PM #8

Rom Toolbox shows 1200 when i tried that, sweet.
  • 0 Likes

frostincredible

frostincredible

Teenage Hacker >:)

Posted 07 January 2012 - 07:35 PM #9

Works for me. Showing 1200MHz in SetCPU as well.
  • 0 Likes
Device: iPhone 5 32GB, Nexus 7
Current ROM: Custom AOSP

frostincredible

frostincredible

Teenage Hacker >:)

Posted 07 January 2012 - 07:51 PM #10

Anyway to get a script to run the commands at boot? I just tried editing a init.d script but it was a no go...idk what I did.
  • 0 Likes
Device: iPhone 5 32GB, Nexus 7
Current ROM: Custom AOSP