Database Users

[INFO] SetCPU Settings for the Vibrant

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!

New Aria user here...

Hello there XDA I just switched to the Aria from the Captivate. I am new to Android modding, so please bear with me.
I like the phone, It doesnt bother me losing screen space. However it is a bit slow with the 600 MHZ processor.
So if there are some people kind enough to guide me to/through the following it would be appreciated.
1. I would like to overclock it a bit, maybe to 800.
2. General performance tweaks
3. Get rid of Att bloatware
4. Root ( z4root is not in the market anymore and ATT disables side loading.)
Sent from my HTC Liberty using XDA App

Everything u need is in the android Dev. Section for the aria its really simple. To find and to follow..I use cm6 rc2. It overclocks very nicely
Sent from my Liberty using XDA App

Hey Joshua, being new to the Aria as well (less than a month), I haven't looked into overclocking it... but I am running CM 6.1 RC 2, what do I need to do to start overclocking?

Install SetCPU to overclock. I wouldn't go over 825mhz as it starts getting unstable.
As for rooting, search for posts by user asiancuta. He did a really good write up that included a key point I didn't see anywhere else. It's titled NOOBZ: easy guide to rooting your aria.... Read all instructions, and make sure you understand it first.
To install cyanogenmod 6.1 rc2 do a search for That aria - she's so racy!
Sent from my Liberty using XDA App

Mike's Aria said:
Install SetCPU to overclock. I wouldn't go over 825mhz as it starts getting unstable.
Click to expand...
Click to collapse
In the other overclocking thread (or overcloking as the OP spelled it ) several people posted that they were running at 864... what type of instability is likely? Also, doesn't overclocking HAVE to have some sort of adverse effect? Like reduced reliability or an increased likelihood of hardware failure? If there are no adverse effects, why would HTC not set the CPU higher from the factory?
I want to try it, but I feel like I pushed the limits of my comfort zone just by rooting and installing CM...

911jason said:
In the other overclocking thread (or overcloking as the OP spelled it ) several people posted that they were running at 864... what type of instability is likely? Also, doesn't overclocking HAVE to have some sort of adverse effect? Like reduced reliability or an increased likelihood of hardware failure? If there are no adverse effects, why would HTC not set the CPU higher from the factory?
I want to try it, but I feel like I pushed the limits of my comfort zone just by rooting and installing CM...
Click to expand...
Click to collapse
I always lean on the side of caution when it comes to overclocking a phone. I don't want to fry the processor since I can't replace it as easily as one on a computer.
Processors are never set from the factory to run at their fastest.
Sent from my Liberty using XDA App

While it might seem odd since all these phones have the same hardware they don't all respond the same to overclocking. Some people can do 864. I can't even get my phone to do anything over 825 and even 825 gives me issues. I like to keep mine between 768-787. Over doing it can cause damage and shorten the life of the processor but keeping it around 800 is probably safe as long as you moniter temps. Heat is the real enemy here. Manufacturers are trying to balance cost, reliability, battery life. Our little phone use a smaller battery and so a lower clock speed keeps the phone running longer. And the aria is a mid range phone, they don't want it to be faster than the more expensive phones. Also Higher clock speeds will drain your battery faster. At 768 the phone is noticeably snappier and the battery drain over stock isn't even noticeable.

Huh. That's good to know, Callmearia. However I don't even know where to start on any of this. I've never 'flashed' a phone or anything like that before.
Sent from my HTC Liberty using XDA App

This is a really good guide explaining how to root your phone and install a custom recovery, Clockwork, with which you can flash ROMs, make backups, and a bunch of other stuff:
http://forum.xda-developers.com/showthread.php?t=788737
You will still not be able to sideload apps just by rooting though. You will need to flash a ROM in order to do that. Check out the Android Development section, it is all there.
L551 said:
Huh. That's good to know, Callmearia. However I don't even know where to start on any of this. I've never 'flashed' a phone or anything like that before.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse

I think most people can hit 864 now using CM6.1 RC2. I think some tweaks were made to allow it. Before I was only hitting 825mhz or 844mhz when I ran in to stability problems... but now I have none. Or, it could be due to the fact it's colder here now.

Alright, so after some adb troubles with Ubuntu 10.10, I am now rooted, woo!
So now, where to go from here?

This worked flawlessly and easy. Less than 5 minutes
http://forum.xda-developers.com/showpost.php?p=7449486&postcount=1
EDIT : I see that you already got rooted.
You have two choices for Attn1's custom ROMS
Liberated or Cyanogenmod
http://forum.xda-developers.com/showthread.php?t=819715
http://forum.xda-developers.com/showthread.php?t=821642
Take in mind that CM has more customizable features, INCLUDING OVERCLOCKING. Liberated doesn't.
Place the .zip on your SD card. Enter clockworkmod recovery by holding down the volume down button after restarting phone. Wipe Data, Cache, Dalvik Cache. Go to install zip from Sdcard. Pick the file. It should install. wait, and reboot and continue.
Customize it to your liking. Download apps/widgets
Turn off unnecessary background items. (Auto Sync)
Decrease Brightness
Only use GSM networks
(these are battery saving tips....lots more)
http://forum.xda-developers.com/showthread.php?t=505419
That is the SetCPU for XDA members.
To install, go through ADB in the command line, or download FASTAPP Install from the Market and place the .apk on your sd card and install it from there.

kaschenberg said:
I think most people can hit 864 now using CM6.1 RC2. I think some tweaks were made to allow it. Before I was only hitting 825mhz or 844mhz when I ran in to stability problems... but now I have none. Or, it could be due to the fact it's colder here now.
Click to expand...
Click to collapse
That's probably true. I haven't tried going over 825 since way back with dumfuqs kernel.

Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App

L551 said:
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Make sure you install the google apps package.
Also, Not too sure.
I use windows. Works perfectly on there. try that

Yup I made sure to install that. Need my market.
I'll see if it works on windows later.
Sent from my Liberty using XDA App

L551 said:
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Try leaving the OC alone after the reflash.. It's defaulted to 864mhz and it works flawlessly for me.

It was default 600MHz for me.
EDIT: Holding down 1 to access voicemail no longer works, as there is no voicemail number in the options. What is it?
Sent from my Liberty using XDA App

L551 said:
It was default 600MHz for me.
EDIT: Holding down 1 to access voicemail no longer works, as there is no voicemail number in the options. What is it?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Its different for every one. My VM is a local number. You can always just use your phone number.
I recently set my VM to go thru my Google Voice number now.
Sent from my Liberty using XDA App

Using my own number worked.
However, now my phone is freezing randomly, and causing the launcher to hang. (ADW and LauncherPro both do this)
It seems android.process.acore always takes alot of CPU time when it does this.

A tip for a faster transformer

I just wanted to let everyone know I found that if I installed cpu master free version and set it to 608 / 1000 set to boot on and performance selected, my tab runs a whole lot smoother. My wife is able to play bejewelled blitz on facebook with it now so she is happy.
Seems the stock kernels are very Conservative on the scaling and never really run at 1000mhz till you really nail them.
If the battery life sucks a little more, which to me wasn't a biggie cause I get 3 days out of it you can buy CPU Master full version for 1.99 and it will allow you to run a screen off setting too.
Setcpu has done nothing but bogged my transformer down and my nexus S so I tried this one and it doesn't so I am passing on the info.
I am not associated with Cpu Master in any way.
If I helped you click on my THANKS button!

I assume you need to be rooted for this ?

Sounds very interesting ...I may have to try this out.
Sent from my Transformer TF101 using XDA Premium App

blankers said:
I assume you need to be rooted for this ?
Click to expand...
Click to collapse
yes root is required

thanks for the tip...it does seem snappier....

SetCPU no longer underclocking at low usage?

I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks

Try a different kernel.
Sent from my CM860

ishamm said:
I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks
Click to expand...
Click to collapse
This is a known issue with the OC faux kernel. I was running into the same problem with his enhanced stock kernel after using webtop. After reflashing the enhanced stock 0.2.0 it would still get stuck at max 1Ghz after using webtop, but a reboot would get the underclocking working again.
I only tried the webtop hack to see if I could get it working. I haven't gone back into it at all so I don't know if this is something that will reoccur. Although I will say that with my day to day use I have not run into any clocking issues since.

Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium

ishamm said:
Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
This is the page for faux's kernels. As far as details, start reading and searching through that thread as well as the threads for any ROMS you are using. 99% of the time people will either have the same problem (and possible fix), the other 1% of the time they will identify a bug (i.e. maxed out CPU).
Keep in mind faux does have different kernels for Froyo, GB, and CM7.

For some reason even if I move the slider from 1300my to 1000, when I touch the screen with at least 3 fingers for a few seconds it pegs out at 1300. I read our cpu's are daisy chained so to speak
so the 2nd core kicks in when needed. I tried cpu tuner and it gives the option to powersave and only use one core or if you choose performance it will allow Both cores. Just might be setcpu isn't designed fully for our dual core setup.

thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks

ishamm said:
thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks
Click to expand...
Click to collapse
Get the 1.3 from the faux thread that I linked to. They're in the very first post...
CM7 is the only ROM that has its own custom faux kernel. For all other ROMS just match the kernel to the build the ROM is based off of (Froyo or GB). If you're using V.2 of Homebase then use the GB one.
Update: Also, there are other kernels out there. I was only using faux's as an example since you were using CM7 and Homebase.

thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again

ishamm said:
thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again
Click to expand...
Click to collapse
Lack of underclocking is a known issue with the latest OC kernel. I'm unclear whether it's actually a bug with the kernel or with setCPU not supporting dual core devices. But yeah, there's a problem with it right now. I'm on the stock enhanced, and other than the webtop issue I mentioned above, it works fine.
Scaling/advanced are not available, this is something that is determined by the kernel you are using not the app.

ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?

ishamm said:
ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?
Click to expand...
Click to collapse
It's working perfectly for me, except after webtop use (which I don't normally use).

I'm still having the same issues regardless of weather I choose power save or performance it will not underclock, and those are the only governors I get the option of :s
Sent from my MB860 using xda premium

[Q] Cyanogenmod 10 with Trinity 7 CPU overclocking

So I'm kind of new to messing around with tablets but learning a few things. On my Nexus 7 I decided to put Cyanogenmod 10 on it so I could customize a few things. I then decided I wanted to overclock the max CPU frequency past 1300 MHz so I installed Trinity 7 kernel. Now I'm able to run it at 1700 MHz which runs a few apps much faster but after exiting out of the apps and going back to check on the max CPU frequency and it's set back down to 1300 MHz.
Does anyone have an idea what could be causing this? So far there's only one app I'm overclocking for so it's not a big issue but it would still be nice to figure out the issue.
Thanks

I down loaded too. I just changed the governer to performance and it stays on 1600 etc on set cpu

EsX GingaNinja said:
So I'm kind of new to messing around with tablets but learning a few things. On my Nexus 7 I decided to put Cyanogenmod 10 on it so I could customize a few things. I then decided I wanted to overclock the max CPU frequency past 1300 MHz so I installed Trinity 7 kernel. Now I'm able to run it at 1700 MHz which runs a few apps much faster but after exiting out of the apps and going back to check on the max CPU frequency and it's set back down to 1300 MHz.
Does anyone have an idea what could be causing this? So far there's only one app I'm overclocking for so it's not a big issue but it would still be nice to figure out the issue.
Thanks
Click to expand...
Click to collapse
There might be an option for "set at boot." Try that.
mccolvinj said:
I down loaded too. I just changed the governer to performance and it stays on 1600 etc on set cpu
Click to expand...
Click to collapse
That's not the solution. The performance governor keeps the cpu speed at max frequency at all times (even when screen is off). That will eat up your battery quick.

v9s said:
There might be an option for "set at boot." Try that.
Click to expand...
Click to collapse
Thanks that seemed to have fixed it though I figured out you have to turn that on THEN pick the max CPU frequency. Doing it the other way around won't change anything, I think that's what I tried before.
Also mccolvinj I'd personally leave it on interactive so it will just use the max CPU when needed or at least that's what I got out of the descriptions of governors I looked up.
EDIT: Nevermind...that only temporarily fixed it, it went back to 1300 after a bit. Maybe I installed Trinity 7 wrong?

Does trinity have superuser permissions?
Sent from my Nexus 7 using xda app-developers app

winged mantis said:
Does trinity have superuser permissions?
Click to expand...
Click to collapse
I think so since it's rooted, is there a way I can check or give it permissions?

you need the powerHAL "fix". your rom should include it, but i guess it doesnt. search the n7 forums for a flashable. or, the trinity kernel toolbox app includes the "fix" just in case your rom doesnt.

EsX GingaNinja said:
I think so since it's rooted, is there a way I can check or give it permissions?
Click to expand...
Click to collapse
Check in the superuser app
Sent from my Rezound using xda app-developers app

kernels arent rooted, your roms are. you can flash a custom kernel on a rom without root. the only difference is that you wouldnt be able to control the cpu with ant cpu control apps, the apps need root.
ive posted the solution already. either find the flashable powerHAL fix or use the trinity kernel toolbox to control the kernel. tkt includes the powerHAL fix.