• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root safe cpu speed

Lanman1978

Android Enthusiast
I have my Triumph overclocked with set cpu. My min is 1.3 GHz and max is 1.5 GHz. Is this a safe range to stay in? My Triumph seems really fast at these speeds so I don't really think there is a need to push it any further. I just don't want to do any damage to my phone. I know that when you overclock you run the risk of damaging your device, but my Triumph has been running great since I started overclocking the cpu. Any advice will be appreciated.
 
The min should be a lot lower than that, in my opinion. You'll definitely have worse battery life, and possibly fry the thing. The normal mininum speed is like 200MHz. It doesn't need to be running overclocked just to perform little background tasks while the phone isn't in use.

I ran mine OC'd at 1.2GHz for about a week. Didn't have any issues or higher temps, but it also didn't seem any different. Even OC'd at 2GHz, the general experience was the same, though benchmarks scored a lot higher.

Do you game on your phone? If not, I'm not sure you are doing much except adding risk by OC'ing it all the time.
 
The min should be a lot lower than that, in my opinion. You'll definitely have worse battery life, and possibly fry the thing. The normal mininum speed is like 200MHz. It doesn't need to be running overclocked just to perform little background tasks while the phone isn't in use.

I ran mine OC'd at 1.2GHz for about a week. Didn't have any issues or higher temps, but it also didn't seem any different. Even OC'd at 2GHz, the general experience was the same, though benchmarks scored a lot higher.

Do you game on your phone? If not, I'm not sure you are doing much except adding risk by OC'ing it all the time.

Yeah I game on my phone somewhat. I noticed my phone seems to fly and perform better with it overclocked. I feel the need for speed I guess.
 
I believe the highest stock clock for the MSM8655 is 1.4ghz. However, the MSM8255, the sibling without cdma support, is clocked as high as 1.5ghz stock.

The dual core sibling, the MSM8660, has just been used in a phone clocked at 1.7ghz stock (Asia Market One S, C2).

I haven't compared voltage tables, but if you find out what these phones are using for 1.5-1.7v, and can manage it on your Triumph, it should be fine (of course, I'm not taking into consideration any revision/stepping updates, etc). And it could very be the same voltage table as it is.

And yes, you shouldn't need that high of a min clock. If anything, you may need a better governor.


When I had a Triumph, I always set max speed to 1.7ghz.

If you're worried about stability, get the Stability Test app from the play store.

And if you're wanting to go higher than 1.7ghz, clamp your voltages and see if you are stable. I'd just take a 70% overclock and run with it though.
 
I believe the highest stock clock for the MSM8655 is 1.4ghz. However, the MSM8255, the sibling without cdma support, is clocked as high as 1.5ghz stock.

The dual core sibling, the MSM8660, has just been used in a phone clocked at 1.7ghz stock (Asia Market One S, C2).

I haven't compared voltage tables, but if you find out what these phones are using for 1.5-1.7v, and can manage it on your Triumph, it should be fine (of course, I'm not taking into consideration any revision/stepping updates, etc). And it could very be the same voltage table as it is.

And yes, you shouldn't need that high of a min clock. If anything, you may need a better governor.


When I had a Triumph, I always set max speed to 1.7ghz.

If you're worried about stability, get the Stability Test app from the play store.

And if you're wanting to go higher than 1.7ghz, clamp your voltages and see if you are stable. I'd just take a 70% overclock and run with it though.

I ran the stability test at 1.5 Ghz for an hour with no errors so I guess I can run my cpu at this speed with no problems.
 
Oh and another thing I changed my min to 1 GHz with a max of 1.5 and my governor is interactive with noop.

If you have any, any, any desire to have some battery life, then I would drop the min clock to something much lower. The basic governors do a very good job in handling the processor clock when sleeping and when awake. I use OnDemand myself, with my tweaks. And with all of that, I get around 18 hours of useful life. As for gaming? I don't do a bunch, but when I do, I can run warm.

If your processor is only loaded around 10%, then you are still running at the higher clock rate with the higher voltages needed for that clock rate. At the lower rates you will run lower voltages, thus save battery life.
 
We are all tweakers on this site when it comes to getting the best performance out of our devices. For myself personally I use the stock clock speed. Using computers for years and doing over clocking I find your greatest stability and usability is going with what the manufacturer releases. I have never had problems with my triumph and it does its job each day. Like anything YMMV from mine.
 
My first Triumph was a beast, I could set the max at 2ghz at that mother would shred no prob for as long as that poor helpless battery would allow but I sent it back for a new one in hopes to get one with better softkey responsiveness and this POS cant handle anything over 1.5... also has the same problem with the softkeys too... I is depressed now :(
 
I run 122 min, 1700 Max, on the interactive x gov. Not a single problem, nothing, if you look up how the interactive x gov works it runs excellent with this oc. Slow when the screens off to preserve that battery juice, screen on, BLAST speed to get what needs done done, quicker to get your screen off, one more tip, no frills CPU is the best free app for overclocking as it has the options for set on boot, and if your phone powers off with out you power button shutting it down it wont reapply the oc, so you can fix your problem without desperate measures and simply, happy day speed demons
 
I am not considered to be a super user, I game a little on my phone (Angry Birds, Drag Racing and Jewels Legend), I don't do it a lot because it's hard on my eye's due to the size of the screen. I never overclock my phone and never overclock my PC's. I have a friend who loves to "Tinker" with overclocking and he is always rebuilding/replacing components on his PC. I, on the other hand, have used my PC's for 5-6 years before even thinking about upgrading (I am an Intel guy, he is an AMD guy). Is this due to overclocking? Who knows.

I guess what I am trying to say is overclock, but do it in stages. I am sure that CPU's on our phones are quality checked like PC CPU's and must meet minimum requirements to pass, but they do not get tested for their maximum abilities. Hence the better overclocking of one phone verses another.

Have fun, but don't be too surprised IF your device fails ;)

I remember when a 300mHz processor was thought to be a super fast CPU and a Gb hard drive was huge. I am truly amazed at the performance and capabilities they cram into these small devices. My first PC had a 40MB HD and 8 MB of RAM and ran MS DOS, no mouse.
 
For my phone I've always had my min set to 122 MHz and the max set to 1401 MHz using the interactive governor. I'm running the MTDEV CM7 ROM. I've never run into any problems personally with this set up and my phone is stable as a rock. I have heard of people setting their max much higher, but I'm not really comfortable trying to push it any further.

Prior to using 1401 MHz as my max, I ran my phone for a few weeks at 1209 MHz just to test the water and make sure it was stable.
 
For my phone I've always had my min set to 122 MHz and the max set to 1401 MHz using the interactive governor. I'm running the MTDEV CM7 ROM. I've never run into any problems personally with this set up and my phone is stable as a rock. I have heard of people setting their max much higher, but I'm not really comfortable trying to push it any further.

Prior to using 1401 MHz as my max, I ran my phone for a few weeks at 1209 MHz just to test the water and make sure it was stable.

This is a GOOD config. Lanman your min CPU is much too high. You will save a ton of battery turning it much lower. Going all the way down to 64mhz may cause stability issues, so 122 is a good point. Personally I clock all the way up to 1.9 Ghz (that is the highest stable i've used) but over 1.4 is really kind of overkill since this can cause overheating issues. You can look into more aggressive governors to speed the transition from the CPU low to high, and different schedulers give different performance / stability capabilities with different governors.

Undervolting can help with the heat issue if you find a stable point, which in my experience on MTDEV-CM7.2 is all values down 50mv. Not only will the phone say cooler on idle, but it will cool down faster after you run it hot.

Also, overclocking won't make too much a difference if you're not pushing the phone hard by running a bunch of background apps or using it for gaming. This is where you're choice of I/O scheduler comes into play as far as organizing the priority of which apps get the most power.

My daily phone usage tends to be on idle most of the time until I pull it out, run it hard for a few minutes, then back in my pocket for a while. If you're constantly on your phone then overheating is a bigger concern and you should take a more conservative approach to overclocking.
 
Back
Top Bottom