[Motorola Atrix 2] Apex:
​

*If you find this Guide Thread helpful, feel free to hit the "thanks" button below!​

I know there are several posts that have been made regarding the overclocking method(s) for the ATRIX 2 both on this forum, as well as some others, however; many of these posts are somewhat old, and I am just providing a guide thread here on XDA since most of the original threads were still beta at the time. This being the case, I take no credit for the instructions I will outline below, but will credit those who deserve to be credited for their efforts they have made in getting these methods to work stably. I am simply compiling some information that users may find helpful in the overclocking process. This is specifically geared toward ATRIX 2 owners who want to have a working knowledge of overclocking and how to accomplish this. If I have missed anything, or if the information is either A) outdated, or B) there is another "newer" more approved method in achieving overclock WITHOUT init.d support, please let me know and I will update the OP...

*Make sure you have a backup in place before attempting any of the following steps, and PLEASE understand how to flash the FXZ file to return to stock if you run into any surprises -though, if you follow the instructions exactly, I would be surprised if you would find the need to do so...​

First & Foremost:​

*DISCLAIMER: I cannot be held responsible for any and all damage related to Hardware loss or data or Software, which the user might cause while overclocking there device. Additionally, I am taking the liberty to assume that anyone who attempts to Overclock their device understands the risks involved. Such risks include, but aren’t limited to: failure of hardware, voiding warranties, and data corruption. While many users enjoy overclocking their own devices, they should do so knowing such risks involved.​

*CPU overclocking is something that you should fully understand BEFORE attempting! Remember that the ultimate goal is speed with stability. Extreme clock speeds are merely academic exercises if the overclocked system can't run your device's operating system and/or applications reliably.

*Please note that the guide thread is based on a more generalized approach to give best results for the majority of users; just because someone's CPU processor runs at 1.25 GHz (or even higher) DOES NOT ENSURE that yours will!​

CPU Overclocking Overview:​

What Is "CPU"?

The term "CPU" is an abbreviation for Central Processor Unit. Essentially, the CPU is the brains of your device's system. It is the internal component which carries out the instructions of a program by performing the basic arithmetical, logical, and input/output operations of the system. Your Android's CPU is responsible for handling all instructions it receives from hardware components and applications running on your device. The CPU performs operations on data held in the computer memory -the RAM. The CPU relies on an "Operating system" (Android OS) for input and output of data, interaction with the user and for storing information.​

What Is CPU Overclocking?

If you think overclocking sounds like an ominous term, you may have the right idea. Basically overclocking means to run a microprocessor faster than the clock speed for which it has been tested and approved. Overclocking is a popular technique for getting a little performance boost from your system, without making any changes to the actual device's hardware. Because of the performance boost found in overclocking, it seems to be something desired by users who demand more from their device, such as heavy gamers, and may perhaps be even somewhat of a novelty for those that really don't need such performance increases. All CPUs have a fundamental clock rate, from which all of the other clock rates inside the CPU are derived. Various sections of the processor take this fundamental clock rate, which acts as a kind of standard timekeeper, and multiply it to get an internal clock speed for a particular section of the CPU. In conjunction with overclocking, the CPU core voltage (VSel or uVolt as it may be referred to) is sometimes raised above the default setting to stabilize an overclocked CPU.​

What Is "Clock Speed"?

Clock speed: Given in megahertz (MHz) or in gigahertz (GHz), the clock speed determines how many instructions per second the processor can execute. The higher the value, the more powerful the CPU. In overclocking your device's CPU, you must be somewhat familiar with it's hardware, and it is always a procedure conducted at your own risk. When overclocking there are some problems and issues you'll have to deal with, such as excessive heat, random reboots, and/or operating system freezes. Even though your device's CPU can be overclocked, it doesn't mean your RAM modules will stably support some of the higher CPU clock speeds that others have seen.​

What Are The Risks Involved?

Overclocking comes with many risks, such as overheating, random system rebooting, and system freezing, so you should become familiar with all the pros and cons before you attempt it. Additionally, overclocking isn't supported by some of the Android Operating System kernels (ICS/JB -at least not as of yet) which means overclocking your CPU may not work on all Android versions -and will obviously void your warranty and leave you with an inoperable CPU if you overclock too high and damage the CPU in the process. Overclocking may also decrease the lifespan of the CPU, cause failure in critical components and may even result in some data corruption, as well as an increase in unexplainable crashes and freezes, as previously mentioned.​

VSel & uVolt (Undervolting) Overview:​

What Is Undervolting?

Undervolting is the practice of modding an Android device to run at a lower voltage than the stock settings. The idea behind kernel undervolting is to reduce that stock voltage to the bare minimum required to run the phone at factory settings. The main battery saver is a low VSel1 (the lowest voltage at the lowest speed), because your phone runs at this speed most of the time. Underclocking VSel1 is not a good idea, because below the default 300 MHz it takes noticeably longer before your phone responds to an incoming call in standby mode. Reducing VSel1 too much makes your phone hang or reboot when it's idle, but you can reduce VSel1 within reason to increase standby time. If you cut VSel1 from 33 to 20 the processor uses 40% less power most of the time, which can make the difference between your phone lasting a full day or blacking out before you get a chance to plug it in. (There are more ways to stretch your battery without "dumbing" down your smartphone)

Lowering the intermediate voltage at medium speed (600 MHz by default) saves a bit of juice when you're playing with your phone a lot, because VSel2 is the typical setting when you're using your phone. If you use your phone as an mp3 player on a long trip you may notice the difference. Your phone rarely runs, or should rarely, at top speed. It spikes at VSel3 occasionally, but even with QueueTube streaming, Wi-Fi Ruler scanning, GPS Status looking for satellites, and Dolphin HD loading pages in the background my processor spent most of the time at 600 MHz instead of the default maximum (800 MHz) or my custom 1.25 GHz CPU frequency scaling.​

What are the "Pros" Regarding Undervolting?

The pros, as mentioned before, are increased battery life and cooler temperatures. It should be noted at this juncture that there is controversy regarding whether or not undervolting truly provides increased battery life; there are those that believe it makes no difference, and unfortunately much of the evidence is circumstantial or based on hearsay, since usage patterns, rogue apps, and any number of other factors can contribute to a perceived difference in battery drain or conservation. Undervolting can help battery life, up to a point, although once the voltage drops below a certain threshold, the battery life actually suffers due to errors caused by the baseband radio not getting enough power. Suffice it to say, it is possible to safely take it to mean that undervolting does in fact provide better battery life than stock settings.​

What Are The "Cons" Regarding Undervolting?

On the flip side, undervolting has its pitfalls. Undervolting a phone too much can cause serious errors to appear as the power-starved processor starts to error out. The radio from above is a perfect example, but there have also been numerous other errors that result from extreme undervolting. These errors can range from random reboots to the phone locking up when the WiFi is turned on, and quite often there is no indication that the undervolting is the cause. The very worst case scenario for undervolting your Android device is that you may in fact "soft brick" the phone; the lack of voltage during boot could conceivably corrupt the phone’s firmware, leaving the phone unusable.​