Mod type: kernel module
Requires root: yes
Mod statues: BETA!
Mod by: tekahuna
Original thread: Rootzwiki
This mod is in beta and is not ready for prime-time. It will NOT last through a reboot so you can experiment with it without the risk of a softbrick. First off, all credits to tekahuna (at rootzwiki) for working on the "Opptimizer Projekt".
-The latest files from here. Our A2's code name is "Edison" so you will want to download "MO_simple_edison_1.5-beta-XX.zip" with XX being the version number.
-A rooted Atrix 2
-Basic experience with adb and terminal
- Unzip the file you downloaded and connect your Atrix 2 to your computer
- Open up a command prompt/terminal and use adb to push "symsearch.ko" and "overclock.ko" to your sd card
- Use adb to shell into your Atrix 2. Gain root access with the "su" command. Remount /system as read/write:
Code:mount -o rw,remount /dev/null /system
- Use the cp command to copy the the .ko files to /system/lib/modules
Code:cd /mnt/sdcard cp symsearch.ko /system/lib/modules/symsearch.ko cp overclock.ko /system/lib/modules/overclock.ko
- now use the insmod command to load the .ko modules:
Code:insmod /system/lib/modules/symsearch.ko insmod /system/lib/modules/overclock.ko
- You should now have the overclock modules installed until you reboot your Atrix 2. Test that you have the modules loaded and everything is working correctly by reading all the current settings:
it should return something like this:Code:cat /proc/overclock/*
Code:freq_table index=0 frequency=300000 freq_table index=1 frequency=600000 freq_table index=2 frequency=800000 freq_table index=3 frequency=1000000 gpu_opps rate=307200000 opp_id=1 u_volt=1125000 cpumin=300000 cpumax=1122000 min=300000 max=1122000 usermin=300000 usermax=11220 00 mpu_clk_get_rate=300000 gpu_clk_get_rate=153600 mpu_opps rate=1000000000 opp_id=3 vsel=61 u_volt=1375000 mpu_opps rate=800000000 opp_id=2 vsel=55 u_volt=1313000 mpu_opps rate=600000000 opp_id=1 vsel=43 u_volt=1200000 mpu_opps rate=300000000 opp_id=0 vsel=26 u_volt=1025000 1.5-yokohama-mapphone-beta-04
- This method of overclocking supports overclocking of all slots (at least it should if not for some bugs) as well as changing voltage. This means that you can change all different frequencies that the A2 will be running at, whether it's at full-speed or while idling.
- The syntax for overclocking the CPU is:
Code:echo slot_number MHz000000 vsel > proc/overclock/mpu_opps
- The slot number is the slot you wish to over/under clock/volt. The Atrix 2 has slots 0 through 3. At the moment this method of overclocking can NOT write to the 0 slot- you will reboot.
- The megahertz (MHz) is the number of gigahertz times 1000. This method of overclocking works in hertz, so add 6 0's to the end of the amount of MHz.
- The VSEL is the voltage. The maximum VSEL (Moto put a cap on it) is 63. The top 4 VSEL values translate to:
60 = 1370000uV
61 = 1380000uV
62 = 1390000uV
63 = 1400000uV
- If your phone can not handle the frequency or voltage, it will reboot.
- I have found that the best way to overclock is to run a benchmark, bump it up a little bit, run a benchmark, bump it up a bit, and keep going until I'm at the frequency I like. Sometimes your phone won't handle instantly going from the stock frequency to a higher frequency but if you put some pressure on the CPU during the overclocking process your phone will handle it better.
- Test to make sure the values are correct:
- You can also overclock the GPU with these modules, however I have found that it does not work (yet!) on the A2. Overclock the GPU with this:
Code:echo rate > /proc/overclock/gpu_opps
Overclocking on boot
It is not recommended to do this yet as the overclock is still in beta. Once it is stable, the developer probably will release a CWM flashable zip for overclocking various values on boot. If you still wish to overclock on boot, you can edit the init.d script or use an app like Tasker.
Enjoy! I will make this thread more user-friendly once the overclock gets out of beta.
DISCLAIMER: By using this guide you agree that this is at your OWN RISK and this forum nor myself will be held responsible for anything that may go wrong - i.e. bricking your device.