[How-To] Overclock/Undervolt Your X in the Big 2.2

[04redgto]

Let rommanager reboot, and install, the from terminal emulater run:

su
insmod /system/lib/modules/overclock.ko
setscaling100.sh

Then check in SetCPU

Thanks AVLFive


P.S. I've been running it pretty hard for the last hour or so without a single hiccup. Quadrent score in the upper 1800's, and linpaks 19 to 20....

 

[GTvert90]

Let rommanager reboot, and install, the from terminal emulater run:

su
insmod /system/lib/modules/overclock.ko
setscaling100.sh

Then check in SetCPU

Thanks AVLFive


P.S. I've been running it pretty hard for the last hour or so without a single hiccup. Quadrent score in the upper 1800's, and linpaks 19 to 20....

With beesleys setscaling? I tried it. Had to lower it. Seems like I'm one of the ones stuck at 1.1

 

[JkdJedi]

With beesleys setscaling? I tried it. Had to lower it. Seems like I'm one of the ones stuck at 1.1

I just crashed as well.......dam. Trying 1.3 now. If that makes the stress test, I might try undervolting it (Poblano!) got it at 70 now.

 

[doctorlove316]

With beesleys setscaling? I tried it. Had to lower it. Seems like I'm one of the ones stuck at 1.1

Join the club.

sent from my RubiX

 

[GTvert90]

Join the club.

sent from my RubiX

Its sad I can't even squeeze out 1.15 LOL I haven't tried messing with voltages too much tho.

Guess we should be happy with 1.1.

Its a shame there is that big of a difference between chips.

 

[El Poblano]

Its sad I can't even squeeze out 1.15 LOL I haven't tried messing with voltages too much tho.

Guess we should be happy with 1.1.

Its a shame there is that big of a difference between chips.

You may just have bad luck, but maybe not. I couldn't get my phone stable at 1.2 even at 66 vsel, but I've been on 1.25/59 for a day and a half without ANY problems. Maybe your phone just doesn't like 1.15?

 

[DThomp]

Just installed through rom manager. MFLOPS 18.709 and quradrant 1750. Guess I will have to run a stress test next. If it does ok for what a half hour or so I should be good. Anybody tried undervolting at 1.38 or did Beesley come up with that for the stock voltage?

 

[El Poblano]

Just installed through rom manager. MFLOPS 18.709 and quradrant 1750. Guess I will have to run a stress test next. If it does ok for what a half hour or so I should be good. Anybody tried undervolting at 1.38 or did Beesley come up with that for the stock voltage?

I could be wrong but I believe Beesley set the voltage at 70 vsel. This is actually overvolting, and you run into a whole new set of unique challenges with overvolting. I would recommend that people be careful when deciding to apply any voltage over stock. A few thoughts:
1. Temperature - Undervolting allows you to run your phone at cooler temps by pushing less energy through the system. Overvolting does the exact opposite. You MUST be vigilant in watching your CPU temps. 50C is the point at which you should be alarmed, 55C can start to cause damage. 60C almost certainly will hurt the processor.
2. Lifespan - CPUs have a limited life span that is dictated by the amount of voltage that runs through it. However, the voltage vs lifespan comparison is not linear but logarithmic. A small increase in voltage can cut years off the life of your CPU. This has been a point of contention in other communities, as some have claimed the loss of lifespan of the CPU wouldn't cut into the the product's usefulness lifespan (i.e. before the consumer wants a new/better device), but I have always stayed on the safe side as I don't know what my situation might be down the road.
3. Battery drain - The power the processor pulls increases with the vsel applied. Therefore, overvolting will undoubtedly lead to worse battery life.

Moral of the story, while the higher clock speeds require a greater vsel value to remain stable, it may not be worth it for the performance gains. This is, of course, the decision of the end user, but those who want to proceed should know the risks. I don't claim to know better than anyone else- but for me it isn't worth it.

 

[DaRkL3AD3R]

Ok so an update:

I pushed for 1.3ghz @ 60, 65, 68 and 70 vsel, and even at 60 I get to fully run Quadrant, Linpack or any of my emulators and it works fine. No turtle mode. But for some odd reason, after like 30-60 minutes of idling, the second I go back to the phone and try to use it as a phone (ie - make calls, text, scroll through my homescreens etc) it instantly locks up and reboots.

Wierd, think its a voltage problem? I mean I went through a lot of voltages...

 

[El Poblano]

Ok so an update:

I pushed for 1.3ghz @ 60, 65, 68 and 70 vsel, and even at 60 I get to fully run Quadrant, Linpack or any of my emulators and it works fine. No turtle mode. But for some odd reason, after like 30-60 minutes of idling, the second I go back to the phone and try to use it as a phone (ie - make calls, text, scroll through my homescreens etc) it instantly locks up and reboots.

Wierd, think its a voltage problem? I mean I went through a lot of voltages...

I'm sure its a voltage problem, I'm just not sure if you could fix it without going a bit higher. The lock up is due to a kernel panic from corruption of data in transmission. Generally this only occurs under heavy loads, so I'm not sure why it would happen after running all more intense tests. Odd.

 

[GatorPT]

Let rommanager reboot, and install, the from terminal emulater run:

su
insmod /system/lib/modules/overclock.ko
setscaling100.sh

Then check in SetCPU

Thanks AVLFive


P.S. I've been running it pretty hard for the last hour or so without a single hiccup. Quadrent score in the upper 1800's, and linpaks 19 to 20....

I have done those steps , and nothing changes in CPU. after line 2 i get no such file exists then after line 3 a list of things pop up in BTE with alot of 100's. then i exit out of su then exit out of BTE. Go have a look at set cpu and no change? what am i missing?
EDIT: i figured it out thanks .
My phone just reboots after CPU showed it running 1380. i take it thats not good.

 

[Bald Steve]

Update: I hit a few reboots running 1.25 @ 59, so I bumped the voltage up to 60. We'll see if there is better stability...

Sent from my DROIDX using Tapatalk

 

[JkdJedi]

You need a special phone to handle these #s. Poblano has motivated me to try some playn and this is what I have so far.

Update- just crashed, #@$#. Back to thte drawing board...........
Sent from my DROIDX using Tapatalk

 

[DaRkL3AD3R]

It is odd. I've even got screenshots of Linpack and Quadrant at 1.3, and both ran stable and great. No stuttering or noticeable compromise of the system and components. I've pulled back on OC'ing for now until more data is out in the wild to review and test. I'm not willing to go higher than 70 vsel, this isn't a desktop where I can strap a 8 heat-pipe monster heatsink on and 2 120mm fans on Just can't mess with something as important as a phone.

 

[GatorPT]

It is odd. I've even got screenshots of Linpack and Quadrant at 1.3, and both ran stable and great. No stuttering or noticeable compromise of the system and components. I've pulled back on OC'ing for now until more data is out in the wild to review and test. I'm not willing to go higher than 70 vsel, this isn't a desktop where I can strap a 8 heat-pipe monster heatsink on and 2 120mm fans on Just can't mess with something as important as a phone.

i used the phone at 1.38 (beesleys) for 5 min, ran smooth , stress test had no errors , benchmark 4 times with quadrant (1805 avg) then just rebooted. weird . how do i manually change the values if i used beesleys method in rom manager.

 

[El Poblano]

i used the phone at 1.38 (beesleys) for 5 min, ran smooth , stress test had no errors , benchmark 4 times with quadrant (1805 avg) then just rebooted. weird . how do i manually change the values if i used beesleys method in rom manager.

Beesley's method only puts a pre-customized file in the correct location with the correct permissions (part 2 of the howto). But its the same process. Thus you can use the how to to play around with your values.
PS. I'm starting to think that beesley's files aren't such a good idea. It leaves a lot to be understood, and those values aren't nearly within the bounds of working for everyone.

 

[JkdJedi]

Beesley's method only puts a pre-customized file in the correct location with the correct permissions (part 2 of the howto). But its the same process. Thus you can use the how to to play around with your values.
PS. I'm starting to think that beesley's files aren't such a good idea. It leaves a lot to be understood, and those values aren't nearly within the bounds of working for everyone.

+1 Not all phones are the same and this just throws you to Max settings if not exaggerated ones, sorry beesley, I'm just saying.

 

[GatorPT]

Beesley's method only puts a pre-customized file in the correct location with the correct permissions (part 2 of the howto). But its the same process. Thus you can use the how to to play around with your values.
PS. I'm starting to think that beesley's files aren't such a good idea. It leaves a lot to be understood, and those values aren't nearly within the bounds of working for everyone.

what makes me mad is that SOME people can you it. and not only that but i got a taste of what it felt like....i will study the how to tomorrow and try to config something.. thanks for you help.

 

[pyroja]

I'm having an issue, and it's making me wonder if I've done something wrong.

Yesterday, when I first started messing with all of this, I was just trying to undervolt. It seemed like that was working when I would get reboots for setting the voltage too low. When I'd fire up SetCPU, I could see the speeds changing back and forth (between 300 and 1000).

Today, I decided to try overclocking, but no matter what I do, the speed seems locked at 1000. It doesn't scale, and even if I set the max to 1300 and try to lock it at that with SetCPU, it still stays at 1000.

Any ideas?

 

[dvader]

I can't get above 1.1ghz with stock freq's..
everything else slows to a crawl