[Motorola Atrix 2] Apex:
[GUIDE] Comprehensive Guide To Overclocking The ATRIX 2 (2.3.6)

PREREQUISITES:

A Rooted ATRIX 2: (for obvious reasons) Check THIS THREAD as well as THE BEGINNER'S GUIDE for references and instruction for rooting your device.

Clockworkmod Recovery (CWM): You can find the installation procedure for this in THE BEGINNER'S GUIDE as well.

If your ROM does not support init.d: download the mo_simp_1.5_edison-signed.zip and flash in CWM Recovery.

Root Explorer: This application will allow you access to the init.d folder to edit your echo table values. You can find this application HERE.

SetCPU: This application will provide verification of your CPU overclocking settings. You can find this application HERE.

Terminal Emulator: You can find this application HERE.

Instructions For Users WITHOUT init.d Support Already Running (Stock/Rooted 2.3.6. etc):

1) Download the latest mo_simp_1.5.x_YOUR_DEVICE.zip

2) Move the mo_simp_1.5.x_YOUR_DEVICE.zip to the root of your SD card

3) Flash in Clockwork Recovery

Optional for Motorola Devices:

4) If your ROM does not have init.d support, download this file and flash from CWM Recovery: moto_init_d-signed.zip

5) Reboot your ATRIX 2 after you have flashed the mo_simp_1.5.x_YOUR_DEVICE.zip and/or 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 -if any!

Basic Usage:

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

6) Switch to "SuperUser" (NOTE: All commands must be done as SuperUser. Switch from the "$" symbol that you will see when you first open the Terminal Emulator to the "#" symbol simply by typing in "su" -without the quotation marks!):

What you will see when you open Terminal Emulator initially:

app_92@edison:/$ export PATH=/data/local/bin:$PATH
app_92@edison:/$

What you should see AFTER typing in "su" (without quotation marks):​

app_92@edison:/$ export PATH=/data/local/bin:$PATH
app_92@edison:/$ su
root@edison:/#

7) Next, type this command in Terminal Emulator: cat /proc/overclock/*

cat /proc/overclock/*

Below is what you should see in Terminal Emulator after entering: cat /proc/overclock/*​

app_92@edison:/$ export PATH=/data/local/bin:$PATH
app_92@edison:/$ su
root@edison:/# 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

8) Read all current settings: (useful for verifying that the frequency table and opp tables match)

9) Next, read just mpu_opps info for the Droid 3, Bionic, and ATRIX 2 Stock:

[COLOR="DarkOrange"]Droid3/Bionic/Atrix2 stock Settings
echo 3 1000000000 1375000 > /proc/overclock/mpu_opps
echo 2 800000000 1313000 > /proc/overclock/mpu_opps
echo 1 600000000 1200000 > /proc/overclock/mpu_opps
echo 0 300000000 1025000 > /proc/overclock/mpu_opps[/COLOR]

10) Write the new frequency & voltage: (Format: echo /proc/overclock/mpu_opps)

*Note: Change only the top frequency/voltage on ATRIX 2 by typing in the full code line "echo 3 1125000000 1375000 > /proc/overclock/mpu_opps" (without quotation marks)

echo 3 1125000000 1375000 > /proc/overclock/mpu_opps

11) To verify the changes made to echo 3, type in "cat /proc/overclock/mpu_opps" (without quotation marks)

root@edison:/# cat/proc/overclock/*

echo 3 1125000000 1375000 > /proc/overclock/mpu_opps
echo 2 800000000 1313000 > /proc/overclock/mpu_opps
echo 1 600000000 1200000 > /proc/overclock/mpu_opps
echo 0 300000000 1025000 > /proc/overclock/mpu_opps

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

# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/overclock.ko

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

11) Reboot after making changes.

12) Open SetCPU to confirm whether your CPU echo values stuck through rebooting. Also, make sure that the "Set On Boot" box is left un-ticked, so as to not have the changed CPU clock speed set upon reboot, and to further test to make sure you are able to run higher CPU clock speeds.

Instructions For Users WITH init.d Support Already Running (Custom ROM WITH init.d Built-In):

1) Open Root Explorer, and navigate to: system>etc>init.d>00pptimize (See Explanatory Images Below)

​

2) Next, open the 00pptimize file and open using Text Editor (See Explanatory Image Below)

​

3) Then, after opening the 00pptimize file using text editor, scroll down until you see the section of code highlighted in red below:

4) Make sure your permissions are set to "R/W" instead of "R/O" in Root Explorer!

# RAZR stock Settings
# echo 5 1200000000 1375000 > /proc/overclock/mpu_opps
# echo 4 1000000000 1374000 > /proc/overclock/mpu_opps
# echo 3 800000000 1313000 > /proc/overclock/mpu_opps
# echo 2 600000000 1200000 > /proc/overclock/mpu_opps
# echo 1 300000000 1025000 > /proc/overclock/mpu_opps
[COLOR="Red"]# Droid3/Bionic/Atrix2 stock Settings
echo 3 1000000000 1375000 > /proc/overclock/mpu_opps
echo 2 800000000 1313000 > /proc/overclock/mpu_opps
echo 1 600000000 1200000 > /proc/overclock/mpu_opps
echo 0 300000000 1025000 > /proc/overclock/mpu_opps
# LG Thrill 4G/Optimus 3D Froyo stock Settings[/COLOR]
# echo 3 1008000000 1350000 > /proc/overclock/mpu_opps
# echo 2 800000000 1260000 > /proc/overclock/mpu_opps
# echo 1 600000000 1100000 > /proc/overclock/mpu_opps
# echo 0 300000000 930000 > /proc/overclock/mpu_opps

5) Now, using the Text Editor in Root Explorer, change the echo 3 table value from "echo 3 1000000000 1375000 > /proc/overclock/mpu_opps" to something like: "echo 3 1100000000 1375000 > /proc/overclock/mpu_opps" (without the quotation marks)

6) Next, click the "back" button.

7) Root Explorer will ask you to save changes. A window will show after you have made changes, and will say:

Warning

You have made changes to this file.

Do you want to save these changes before exiting?​

Click "Yes" to save. The newly made changes will be saved to a file that will be called "00pptimize.bak".

8) Now, find and delete the "00pptimize.bak" file created after you made your changes by long pressing this file and choosing the "Delete" option.

9) Finally, exit out of Root Explorer and reboot your device.

10) Once you have rebooted, open SetCPU and you should see your CPU frequency scaling value you changed from 1000000000 to 1100000000, or check the settings by using Terminal Emulator and typing "cat /proc/overclock/*" -what you should see is a clock speed that was 1GHz and is now 1.1GHz. Also, leave the "Set On Boot" box un-ticked until you have fully tested the new CPU clock speeds and are certain they are at a stable frequency.

​

11) You can continue this process using small incremental jumps from 1.1GHz to 1.12GHz, to 1.14GHz, to 1.16GHz, etc. until you find a your highest stable running CPU clock speed.

*I have been able to slowly work my way up to run my CPU at 1.25GHz stably, but you may find that your device can either handle more or less clock speed. Again, handle with care, and patience in achieving your highest stable clock speed is something you need to take into consideration throughout this entire process!

​

UNDERVOLTING GUIDE:

Updated: 08/09/2012

Please Reference THIS THREAD For Loading/Changing CPU Voltages.

Credit Goes To:

whirleyes​

CPU GOVERNOR SETTING EXPLANATION:

Updated: 08/09/2012

Please Reference THIS THREAD For CPU Governors Explained.

Credits goes to:

http://icrontic.com/discussion/95140...m-tuner-tegrak

http://xdaforums.com/show....php?t=1369817​

*I recommend that after you make changes to the clock speed, you run your device for 5-10 minutes. Open applications, play a quick game, browse the web, etc. to make sure that your device can handle the new clock speeds before making any further increases to the CPU.

**You can also underclock in the same manner that you have used to overclock, but by changing the echo table values at echo 0 to something like "echo 0 240000000 1025000 > /proc/overclock/mpu_opps" -which is always a good idea when overclocking to give the CPU a load relief when using CPU settings like "performance". This will run your CPU at its lowest frequency scaling to 240MHz rather than at 300MHz, but again, experimentation/patience/extensive testing is a must!​

Credits: tekehuna,cogeary, JRW 28, alteredlikeness, whirleyes, 00pptimizer Project via RootzWiki, and probably more to come to credit. Please let me know if you can add to/provide more info/correct me on misinformation/or should be listed in credits also and I will update the OP!​