Related
So, I can only run my phone at a MAX 1.3 GHZ without it crashing..
How can I run it at 1.26 without it crashing?
I am running Kings Kernel #11CFS
with Virus Sense Rom RC3
Is there some setting I need to chang? or use a different kernel..
why would you want too ? i would imagine that would kill the battery and make the phone very warm ?
Not all CPU's are created equal. If yours is crashing a lot at that frequency, chances are that yours will almost never run stable.
you could try using conservative scaling but it still probably wont be stable. most evo's cannot handle it.
Heat is your enemy. I suggest you try my hardware mod to really crank up the freq.
Overclocking
I just rooted my phone and I downloaded setcpu and I want to overclock it, but the max that i get is 998. And was wondering how can i get it at 1.267GHz. Im new to the android. Can someone please help.
The stock kernel does not allow over clocking, you'll have to try out a kernel from the development section, I recommend the newest Kingz.
Hey... I think this thing makes phone calls too!
1ktmeadows said:
I just rooted my phone and I downloaded setcpu and I want to overclock it, but the max that i get is 998. And was wondering how can i get it at 1.267GHz. Im new to the android. Can someone please help.
Click to expand...
Click to collapse
Download a kernel that supports OC.
I tinkered around with OC'ing a few months ago I could never get it over 10xx without crashing. I just learned to live without setcpu.
I agree with voodoo there's really no benefit, unless you like pulling the battery. I didn't notice any better performance or speed while overclocking.
nukedukem said:
Heat is your enemy. I suggest you try my hardware mod to really crank up the freq.
Click to expand...
Click to collapse
Lol... [op]is there a particular reason why you want it that high? In all honesty there is no benefit to this.
sent from my VooDoo phone...
VOODOOTRIP said:
Lol... [op]is there a particular reason why you want it that high? In all honesty there is no benefit to this.
sent from my VooDoo phone...
Click to expand...
Click to collapse
Indeedj this will cause ecen more battery drainage and additional heat that might damage the phone
Sent from the iPhone Assassin
Mine is running very stable at 1.26Ghz and great battery life. Running BakedSnack 1.8 along with kernel #6. I'm using Overclock Widget instead of SetCpu as SetCpu was causing lagging response on my EVO.
I dont need 1.26 GHZ
I just wanted to Know why my phone wasnt running stable at 1.26 even thoug it said it was capable of doing it..
Hey
nukedukem said:
Heat is your enemy. I suggest you try my hardware mod to really crank up the freq.
Click to expand...
Click to collapse
That looks pretty sweet.. is that real though?? if so what did you do?
ins0dus said:
That looks pretty sweet.. is that real though?? if so what did you do?
Click to expand...
Click to collapse
Love the cooler pic,lol. Might have to steal that one.
Sent from my PC36100 using XDA App
I always wondered when we'll start seeing little fans in our phones, or heat sinks on the back.
bender1077 said:
Click to expand...
Click to collapse
ahahahahaha
I agree with most ppl in that this phone is wicked fast as it is and its just not worth the risk/reward
HTC EVO4G A.K.A. Usain Bolt
Linpack: 34-35 MFLOPS Avg
Quadrant: 1500+
Kernel: King's #6 BFS
FPS2D: 54-55 FPS
ROM: Fresh 3.3
PRI: 1.77
I totally agree that heat is the undesired side effect of the overclocking of the Evo. I had been running mine at 1.152MHz and the noticed a couple of different colored spots on the screen especially during boot up with the bright white splash screen. This was caused by the excess heat from the CPU. I had my screen replaced due to dust under the glass and it is perfect, so no more overclocking for me.
SetCPU. In my personal opinion, one of the best Android apps out there. It lets you overclock/underclock your phone. Here I will describe how to set it up for the Vibrant so you do not brick/crash your phone.
1. Uncheck/DO NOT Check Set on Boot (this will cause crashes in most phones if checked)
2. Set the CPU Governor type to "Conservative"
3. If you're using a kernel such as JAC's OC/UV(/VOODOO) set the MAX Clock speed at 1.2Ghz, also set the MINIMUM clock speed at 200MHz (not doing this could cause random crashes/reboots/freezes)
4. Don't underclock too low (as this could cause crashes), I recommend nothing below 750MHz (although it could *probably* run at 400MHz, no lower though!)
5. Don't blame the dev of your kernel or SetCPU's dev if you break your Vibrant, you shouldn't do something you know nothing about.
6. Set a warning up so if your Vibrant gets hotter than 115° Fahrenheit SetCPU will alert you. (125° Fahrenheit is when your Vibrant will start to get damaged.)
7. Always ask if this works on the ROM you have flashed before you try to use it on the ROM.
8. SetCPU is free for XDA members only.
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
That is all.
A couple of things:
1. It's been found that setting the minimum to 200 MHz is too low on some ROMs and can cause problems with some applications, like Pandora. Users have reported that setting the minimum to 400 MHz alleviates those problems.
2. SetCPU is and has been free for some time to XDA members. However, if you like the application, you should throw the dev some coins and buy it in the market or make a donation.
NikolaiT said:
SetCPU. In my personal opinion, one of the best Android apps out there. It lets you overclock/underclock your phone. Here I will describe how to set it up for the Vibrant so you do not brick/crash your phone.
1. Uncheck/DO NOT Check Set on Boot (this will casue crashes in most phones if checked)
2. Set the CPU Governor type to "Conservative"
3. If you're using a kernel such as JAC's OC/UV(/VOODOO) set the MAX Clock speed at 1.2Ghz, also set the MINIMUM clock speed at 200MHz (not doing this could cause random crashes/reboots/freezes)
4. Don't underclock too low (as this could cause crashes), I recommend nothing below 750MHz
5. Don't blame the dev of your kernel or SetCPU's dev if you break your Vibrant, you shouldn't do something you know nothing about.
6. Set a warning up so if your Vibrant gets hotter than 115° Fahrenheit SetCPU will alert you. (125° Fahrenheit is when your Vibrant will start to get damaged.)
7. Always ask if this works on the ROM you have flashed before you try to use it on the ROM.
8. SetCPU is not (and probably never will be) free, so DO NOT bug the dev for a free copy.
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
That is all.
Click to expand...
Click to collapse
I am interested in how you have determined this.
How legit are these instructions, im interested in this app. Since im running bionix 1.9.1 jacs oc/uv rom.
Sent from my SGH-T959 using XDA App
I agree with most of what the OP is saying, I've been using setcpu since my G1. I'm currently running Fusion 1.0 with JAC kernel. I have 200 min with 1200 max. No set on boot and no profiles. I'm not sure about the damage temp, I've ran the gps for an hour with the phone in direct sunlight and it hasnt gotten that high.
This is what works for me, as well as many other users, and the issues posted here have been reported by many users. Also to the person with JAC's OC/UV Kernel, this app is required. If it isn't used, you can experience random freezes/crashes/reboots.
opiomorph said:
A couple of things:
1. It's been found that setting the minimum to 200 MHz is too low on some ROMs and can cause problems with some applications, like Pandora. Users have reported that setting the minimum to 400 MHz alleviates those problems.
2. SetCPU is and has been free for some time to XDA members. However, if you like the application, you should throw the dev some coins and buy it in the market or make a donation.
Click to expand...
Click to collapse
Yes, this is true, but the only time time the vibrant will reach 200MHz (100MHz if SetCPU isn't used) is when the phone is idle.
Double post, apologies.
i have set on boot checked on bionix 1.9.1 with no problems. 200min,1200max, conservative.
Im running the bionix 1.9.1 with jacs oc/uv. I havent installed the set cpu app yet and my phone is running great. Im working on getting up the nerve to try it.
Sent from my SGH-T959 using XDA App
GreggoryD502 said:
Im running the bionix 1.9.1 with jacs oc/uv. I havent installed the set cpu app yet and my phone is running great. Im working on getting up the nerve to try it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Do eet! The worst that will happen is that your CPU can't handle an overclock and you'll be stuck at 200/1000. Cross your fingers!
It is worth the money for the developer, for sure.
Also, can you post your source for the temperatures you listed? Seems kind of low for Fahrenheit. Especially since where I live those temps are just above room temperature sometimes
Ok. Just installed and set 1200.max 400 min. Will post latet let everyone know.if I notice a differnce. Phone does seem snappier, or could be.my imagination. Lol
Sent from my SGH-T959 using XDA App
Quick, possibly dumb question. Do I have to reset the settings if I turn my phone off and turn back on?
Sent from my SGH-T959 using XDA App
GreggoryD502 said:
Quick, possibly dumb question. Do I have to reset the settings if I turn my phone off and turn back on?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
not if you have 'set on boot' checked. but some people claim that setting can cause problems. however i've been running bionix 1.9.1 with set on boot checked since 1.9.1 came out with 0 problems. otherwise, yes, you have to reset it every time you reboot.
Thanks. Ill check set on boot and see what happens.
Sent from my SGH-T959 using XDA App
Be careful about "Set on Boot", it someone resets SetCPU and underclocks your phone to the point of crashing shortly after it boots. This is a pretty common issue but it doesn't happen to all users.
funeralthirst said:
not if you have 'set on boot' checked. but some people claim that setting can cause problems. however i've been running bionix 1.9.1 with set on boot checked since 1.9.1 came out with 0 problems. otherwise, yes, you have to reset it every time you reboot.
Click to expand...
Click to collapse
i dont have set on boot checked, and my settings are preserved on reboot
Ive been using set on boot for several days now, and no issues so far. To be honest I cant really tell any difference in the phones performance. But im not really pushing it either.
Sent from my SGH-T959 using XDA App
NikolaiT said:
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
.
Click to expand...
Click to collapse
This does work on stock vibrant kernel. I have it on JI6 stock except for Root and mods. The OP is correct that you cannot over clock on stock.
As a battery saver for JI6 possibly. Also I am currently using it as an attemped fix for my Gallery freeze, lockup/CPU hog issue.
Sent from my SGH-T959 Gallery freezing Vibrant using XDA App
hi all been a member for a long while from HTC 8525 days, just wanna say i love this site, saw that the app was free for members, but i love supporting you guys i bought the app anyway! thanks for all the hard work all of you put in... im sure we all appreciate it!
Hey guys whats the max overclock that the Aria can be set to? I had CM6 on mine and had the overclock widget from the market and the max that the sliders went to was 600... But I have Liberty FR008 on it now and i still have the overclock widget but the max that the sliders goes to now is 864... I tried overclocking to 864 but it froze and something went wrong so i had to flash a backup i made. My overclock options right now are 245, 400, 480, 600, 768, 787, 806, 825, 844, & 864... Has anyone tried to over clock the Aria past 600? and did you have any problems with it? Thanks for any help.
-Cpl. T. King
I dont think the cm6 kernal allows for over clocking. I have the latest liberated rom and overclocked to 806 which is the recomended max setting by the dev.
Sent from my HTC Liberty using XDA App
Use the search button. The safe zone is 806.
Sent from my HTC Liberty using XDA App
andrew.cambridge said:
I dont think the cm6 kernal allows for over clocking. I have the latest liberated rom and overclocked to 806 which is the recomended max setting by the dev.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
The CM 6.1 kernel most certainly does support over-clocking. The CM 6.1 kernel was used as the basis for the Liberated FR008 kernel.
Maybe I was thinking about 6.0. Whatever one I had, I could only over clock to 600.
Sent from my HTC Liberty using XDA App
6.0 didn't allow overclocking, 6.1.1 does though. I overclock my Aria to 806mHz and underclock it to the lowest setting when the phone's screen is off so I don't tire out the processor. 806mHz is really good, it puts the phone at the level of the G2 or the Shift 4G...and because I usually run Edge w/3G when downloading, WiFi if available, my battery is really good. Probably about 14 hours of normal (good) usage.
I wouldn't overclock it higher, you risk burning the processor out.
I'm OCd to 825 on-demand and the phone runs very nicely. 245 when screen off
825 is not recommended I don't think. 806 seems to be the sweet spot.
brswattt said:
825 is not recommended I don't think. 806 seems to be the sweet spot.
Click to expand...
Click to collapse
Says who? It's dependent on the quality of the processor. Some can do it, some can't.
kaschenberg said:
Says who? It's dependent on the quality of the processor. Some can do it, some can't.
Click to expand...
Click to collapse
Attn1 said he doesn't recommend overclocking over 806, because you might fry the cpu
Sent from my HTC Liberty using XDA App
I forgot attn1 was a engineer for HTC. 806mHz is the sweet spot, I've been running it for weeks OD with Screen off at 206 and it doesn't overheat & good battery life.
tribestros said:
I forgot attn1 was a engineer for HTC. 806mHz is the sweet spot, I've been running it for weeks OD with Screen off at 206 and it doesn't overheat & good battery life.
Click to expand...
Click to collapse
Suit yourself. Just saying 806 is the sweet spot for most people around here. I've gotten force closes and reboots at 825. We don't need your attitude
Then it seems like your particular phone can't handle 825. I suggest people try it on both. every phone is different. Just don't be stupid about it. When using the phone as a gps, under clock it. under clock when screen off. and over clock on demand and I'm fine on 825. never seen any issue.
"Suit yourself." I think that was the point of his post. His phone and usage of it OCd at 825 is good for him. He was just stating an answer to the OP. No reason to go around telling him he's wrong..
Anyways, not trying to start a OC war... because that would be ridiculous (-ly funny I might add).
As for myself, when I did OC my processor, 825 didn't effect my phone's performance, but it did make it extremely hot after a bit of use. So it's up to your phone and how you want to handle your phone. I don't really need the OC anymore though; I just stick with 600 (;
Sorry for the nooby question, but whats this even do? Besides making it faster I assume?
vicmora5 said:
Sorry for the nooby question, but whats this even do? Besides making it faster I assume?
Click to expand...
Click to collapse
That's basically all it's for. d:
You get more processing power.
brswattt said:
That's basically all it's for. d:
You get more processing power.
Click to expand...
Click to collapse
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Downsides are less battery life (may be a lot or not) and not going as fast as it would be if you were OCd. It may also heat up more.
vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Overclocking is not necessary at all. We just recently became able to overclock. If you are satisfied with the speed/fluidity of your phone, then there is no need to overclock. The downsides would be less battery life (cpu running faster), and if you push your phone too hard (overclock stupidly), you run the risk of burning out your cpu. your phone should not be getting hot.
vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
It's not necessary. It's pretty damn cool to make the little Aria have a processor as fast as the one in the G2 though.
just curious really as my phone never gets warm or anything running at 768mhz the battery life is also pretty good.
hey,
i don´t think so, because in the worst case your phone will take damage. But this ~770 mhz are about 250 more then before. Im happy with this xDDD
that is true haha, i just dont see it doing much harm if the phone will run stable higher at the same voltage or the tiniest bit higher
No, that's the limit of the MSM7225. (Achieved by adjusting the PLL to its max, any higher will overrun the limits of the chip, and cause it to most likely fail)
i would like to know, if its very bad for the phone, if you let it permanently run with full speed. Ok, if it will get very hot.. thats clear, but is it bad if you have the 77mhz and it is for example in silent mode, or when you listen to some music. Should you ever take some possible speed away, if its not need? (thx)
The hardware life will probably be reduced. By how much, it cannot be said definitively, but, I am pretty sure that by the time the hardware fails because of overclocking, the phone will have been retired long back.
What you are requesting (Dynamically changing speed) is exactly what Speed Governors (Performance, Internative, OnDemand etc) do. If you are on CM7, use Smartass Governor, because it's the "smartest". If not, then use Interactive governor.
i use ginger yoshi... and sometimes it sais that the sd was removed. Could overclock be a reason for this?
I dont think so. I got the same issue once, and formatting the SDCard fixed it.
ok i will try it thanks
3xeno said:
The hardware life will probably be reduced. By how much, it cannot be said definitively, but, I am pretty sure that by the time the hardware fails because of overclocking, the phone will have been retired long back.
What you are requesting (Dynamically changing speed) is exactly what Speed Governors (Performance, Internative, OnDemand etc) do. If you are on CM7, use Smartass Governor, because it's the "smartest". If not, then use Interactive governor.
Click to expand...
Click to collapse
I have a sense rom on the wildfire, so I will try Interactive Governor. Do I still need SetCPU in order to use it?
KhurramF said:
I have a sense rom on the wildfire, so I will try Interactive Governor. Do I still need SetCPU in order to use it?
Click to expand...
Click to collapse
To use overclocking and governers on sense roms, oc kernel and application like setcpu are must. Setcpu has governers too.
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
To use overclocking and governers on sense roms, oc kernel and application like setcpu are must. Setcpu has governers too.
Click to expand...
Click to collapse
Even if it a custom rom? I am using JokerDroid 4.2.
KhurramF said:
Even if it a custom rom? I am using JokerDroid 4.2.
Click to expand...
Click to collapse
Depends whether the rom has inbuilt oc kernel or not.
Haven't used the jokerdroid. But I think it has...
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
Depends whether the rom has inbuilt oc kernel or not.
Haven't used the jokerdroid. But I think it has...
Click to expand...
Click to collapse
Looked at JokerDroid's thread and it says about version 4.2
■ Kernel : nFinity Kernel
■ Build Number : 2.37.415.1
■ CPU Overclock : 710 Mhz
Click to expand...
Click to collapse
So this means it has an oc kernel?
KhurramF said:
Looked at JokerDroid's thread and it says about version 4.2
So this means it has an oc kernel?
Click to expand...
Click to collapse
Yes, it does, and it is overclocked to 710 MHz, by default.
hello xda
this is one of my first posts, and beacuse of that, i am not permitted to post in the development section af the G2/desire z forum.
i have a little problem on my desire z running virtuous unity 2.35.
i use setcpu to overclock my phone to 1.7 Ghz, but after a while it automatically underclocks to 1.2 Ghz.. does anyone know why?
Thanks in advance
nicolaibaun said:
hello xda
this is one of my first posts, and beacuse of that, i am not permitted to post in the development section af the G2/desire z forum.
i have a little problem on my desire z running virtuous unity 2.35.
i use setcpu to overclock my phone to 1.7 Ghz, but after a while it automatically underclocks to 1.2 Ghz.. does anyone know why?
Thanks in advance
Click to expand...
Click to collapse
set cpu only overclocks to 1.7ghz when you actually need it, like when you are running graphics heavy apps or you are multitasking alot. it underclocks to 1.2ghz at times because you dont need 1.7ghz and only need 1.2ghz, this also saves battery life. if you want it to run at 1.7ghz all the time you need to set your governer to preformance. hope this helps
You shouldn't be using SetCPU if you are on Unity. There is already an OC interface built-in to the ROM, and it works better than SetCPU.
From the Virtuous website:
Virtuous. overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
But as evilcuber already mentioned, CPU clocking down when not needed is normal. The OC you are setting is a MAXIMUM, not a MINIMUM. You set how high it can go, but that doesn't affect how the CPU can clock up and down below that upper limit. If you want, you can set the minimum clock speed higher (or as evilcuber mentions, use a different governor), so its running at 1.7 GHz all the time . But you are just wasting battery life when its not needed. You might see some slight performance increase by running at max clock speed all the time, as it avoids any delays in CPU speed stepping. But the battery trade-off is probably not worth it.
Think of it as your car's engine revving at maximum RPM all the time, regardless of what speed you are actually moving at, or even when your car is parked. It makes more sense to just rev the engine up or down when the speed is needed. Not a perfect analogy, I know. But you see what I'm getting at?
also if u want a gui, u can download the virtuous overclock app
ohh i may not have expressed my self good enough.. i know about how the governors works (at least some of them), and the problem is that, i choose 1.7 Ghz, and quit the app, and then when i get back, the clock is adjusted back to 1.2 Ghz. maybe i should just uninstall setcpu, and let the daemon do the work?
evilcuber said:
also if u want a gui, u can download the virtuous overclock app
Click to expand...
Click to collapse
Ah, I just upgraded to Unity 2.35 today, and noticed the OC GUI is no longer packed in. Just find the file by using the search function in the Unity thread, to install the GUI.
nicolaibaun said:
hello xda
this is one of my first posts, and beacuse of that, i am not permitted to post in the development section af the G2/desire z
Click to expand...
Click to collapse
FYI you don't post questions in the dev section, you post them in Q&A which means questions and answers
Sent from my HTC Vision using XDA Premium App
nicolaibaun said:
ohh i may not have expressed my self good enough.. i know about how the governors works (at least some of them), and the problem is that, i choose 1.7 Ghz, and quit the app, and then when i get back, the clock is adjusted back to 1.2 Ghz. maybe i should just uninstall setcpu, and let the daemon do the work?
Click to expand...
Click to collapse
But which governor?
I would uninstall SetCPU. As I already said, the Virtuous team does not recommend it. It doesn't perform nearly as quickly as the built in daemon. Install the GUI app, if you want to tweak the daemon settings. If the dev of a ROM is as clear about recommended something as they are with the daemon (vs. SetCPU), its a good idea to follow their advice.
Got the same problem with setcpu.
You should try what they say above.
I run unity 2.37 : use virtuous OC gui(virtuous overclock controller) with temp+CPU widget to monitor your speed, temps, mem, etc.
With the new unity kernel you can OC up to 2.0 ghz
solid advice
redpoint73 said:
You shouldn't be using SetCPU if you are on Unity. There is already an OC interface built-in to the ROM, and it works better than SetCPU.
From the Virtuous website:
Virtuous. overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
But as evilcuber already mentioned, CPU clocking down when not needed is normal. The OC you are setting is a MAXIMUM, not a MINIMUM. You set how high it can go, but that doesn't affect how the CPU can clock up and down below that upper limit. If you want, you can set the minimum clock speed higher (or as evilcuber mentions, use a different governor), so its running at 1.7 GHz all the time . But you are just wasting battery life when its not needed. You might see some slight performance increase by running at max clock speed all the time, as it avoids any delays in CPU speed stepping. But the battery trade-off is probably not worth it.
Think of it as your car's engine revving at maximum RPM all the time, regardless of what speed you are actually moving at, or even when your car is parked. It makes more sense to just rev the engine up or down when the speed is needed. Not a perfect analogy, I know. But you see what I'm getting at?
Click to expand...
Click to collapse
wow thank you for this enlightening advice, you have answered all my questions i had in my mind about overclocking my android
I have the virtuous rom version 2.39.0 just 2 days ago on my mytouch 4g, i'm new to rooting & roms & still happy that i took this risk and rooted successfully i was contemplating on pushing my luck a bit further by overclocking it with setcpu but thanks to you and other experienced members in this thread i now understand a lot that i didnt know
jamgirl said:
wow thank you for this enlightening advice, you have answered all my questions i had in my mind about overclocking my android
I have the virtuous rom version 2.39.0 just 2 days ago on my mytouch 4g, i'm new to rooting & roms & still happy that i took this risk and rooted successfully i was contemplating on pushing my luck a bit further by overclocking it with setcpu but thanks to you and other experienced members in this thread i now understand a lot that i didnt know
Click to expand...
Click to collapse
You're very welcome. Be sure to click the "Thanks" button, if my post helped you!
Also, on Sept. 12, the Virtuous team recommended OC/UV Beater as a interface for overclocking the Virtuous OC Daemon. I've been using this recently, and it works great.
http://forum.xda-developers.com/showthread.php?t=1207546