Database Users

SetCPU safe?

Doesn't SetCPU overclocks our device? I heard constantly overclocking your device will kill it less in a year. Is this true?
Sent from HTC HD2 using XDA app.

HeavyComponent said:
Doesn't SetCPU overclocks our device? I heard constantly overclocking your device will kill it less in a year. Is this true?
Sent from HTC HD2 using XDA app.
Click to expand...
Click to collapse
I used setcpu on my g1 (overclocked from 384mhz to 528mhz) for almost the whole time i had it and it didnt do any damage. The overclocking on snapdragons is more of a wait and see as no one has overclocked a snapdragon for that long but its HIGHLY unlikely that it will kill your cpu that quickly (ive been overclocking devices for years and never seen it happen). Leo users dont need to worry about overclocking with setcpu as it hasn't been enabled in the kernel we are using so the only thing setcpu is good for is underclocking and setting profiles.

So once it is enabled in our Kernel that's when we should be worried? What's the worse that can happen?
Thanks for the reply.
Sent from HTC HD2 using XDA app.

HeavyComponent said:
So once it is enabled in our Kernel that's when we should be worried? What's the worse that can happen?
Thanks for the reply.
Sent from HTC HD2 using XDA app.
Click to expand...
Click to collapse
I dont think we should, people on the n1 have been doing it for months and i havent seen any posts of things going wrong and even if it is enabled in the kernel you can choose weather to use it or not via apps like set cpu

JJbdoggg said:
I dont think we should, people on the n1 have been doing it for months and i havent seen any posts of things going wrong and even if it is enabled in the kernel you can choose weather to use it or not via apps like set cpu
Click to expand...
Click to collapse
It will cause lower battery life!

hazard99 said:
It will cause lower battery life!
Click to expand...
Click to collapse
if you choose to use it.

JJbdoggg said:
if you choose to use it.
Click to expand...
Click to collapse
I know I use it to underclock. I was just saying. I actually use it as a means of making the battery last. and also the reaction time at which the cpu scales.

JJbdoggg said:
I used setcpu on my g1 (overclocked from 384mhz to 528mhz) for almost the whole time i had it and it didnt do any damage. The overclocking on snapdragons is more of a wait and see as no one has overclocked a snapdragon for that long but its HIGHLY unlikely that it will kill your cpu that quickly (ive been overclocking devices for years and never seen it happen). Leo users dont need to worry about overclocking with setcpu as it hasn't been enabled in the kernel we are using so the only thing setcpu is good for is underclocking and setting profiles.
Click to expand...
Click to collapse
So if I understand this correctly, setcpu does nothing to improve performance as far as Device speed?

dbiggss said:
So if I understand this correctly, setcpu does nothing to improve performance as far as Device speed?
Click to expand...
Click to collapse
A faster cpu is generally a speed increase and at certain points the gains are null. so its usually a small mhz boost.

dbiggss said:
So if I understand this correctly, setcpu does nothing to improve performance as far as Device speed?
Click to expand...
Click to collapse
it does, keeping the device at 1ghz (998mhz in our case) at all times will provide better performance than scaling from 245mhz to 1ghz. read here for more info http://www.pokedev.com/setcpu/

hazard99 said:
I know I use it to underclock. I was just saying. I actually use it as a means of making the battery last. and also the reaction time at which the cpu scales.
Click to expand...
Click to collapse
i use it for those reasons too

[Q] SetCPU for MT4G?

Is it safe to install SetCPU on the MyTouch4G now that we have permaroot? If so, what are the settings we should use with it? Just not sure if the current kernel has been tested with SetCPU or not, and if it works what version of SetCPU... 2.0.3 or 2.0.4?
Thanks.

I am running 2.0 4 with autodetect. Set at 1024mhz performance. No issues and been running 3 days now.
Sent from my HTC Glacier using XDA App

Mr Bill Florida said:
I am running 2.0 4 with autodetect. Set at 1024mhz performance. No issues and been running 3 days now.
Click to expand...
Click to collapse
So you're not overclocking it then, correct? What is your setting for the minimum frequency?

I have it at 245mhz.
Sent from a rooted myTouch4g Glacier.

set up a profile under screen off and set max down to 3000 and minimum at 2000...saves me ton of battery power now
also download auto killer memory in market and set to optimum for even better battery life

I thought that over clocking required a custom kernel?
Sent from my anti titanic

thelamacmdr said:
I thought that over clocking required a custom kernel?
Sent from my anti titanic
Click to expand...
Click to collapse
You do.
Sent from my HTC Glacier using Tapatalk

Were not overclocking... simply managing the CPU more efficiently at its existing speed set
Sent from my HTC Glacier using XDA App

awdlexusis said:
set up a profile under screen off and set max down to 3000 and minimum at 2000...saves me ton of battery power now
Click to expand...
Click to collapse
The closest options for this are the following:
368640 max
245760 min
What did you use for the scaling and priority settings?
EDIT - Added a screenshot to this post. I've tried both 2.0.3 and 2.0.4, and no matter what I set for the minimum setting it stays at 245 (not what I defined). Does it not work then on this stock kernel?

I was going to say the same thing, from what I have seen on my phone setcpu is not doing anything. It won't change any of the clock speeds whether boosting the low end or limiting the high end.
I have tried a few things like setting profiles for less than 75% battery to lower the max clock speed and that doesn't work either. Am I crazy or are others experiencing a placebo effect on profiles lowering clock speed when screen is off?
Sent from my HTC Glacier using XDA App

slowestcivic said:
I was going to say the same thing, from what I have seen on my phone setcpu is not doing anything. It won't change any of the clock speeds whether boosting the low end or limiting the high end.
I have tried a few things like setting profiles for less than 75% battery to lower the max clock speed and that doesn't work either. Am I crazy or are others experiencing a placebo effect on profiles lowering clock speed when screen is off?
Click to expand...
Click to collapse
For HTC phones need to be rooted and also disable perflock. In setcpu: menu->perflock disabler. I set my perflock to disable on boot.

vels13 said:
For HTC phones need to be rooted and also disable perflock. In setcpu: menu->perflock disabler. I set my perflock to disable on boot.
Click to expand...
Click to collapse
Hot damn, that fixed it! Now to test it out further to see how well it works here. I'm not looking to overclock, just underclock when I'm not using the phone. Thanks for the tip!

dustrho said:
The closest options for this are the following:
368640 max
245760 min
What did you use for the scaling and priority settings?
EDIT - Added a screenshot to this post. I've tried both 2.0.3 and 2.0.4, and no matter what I set for the minimum setting it stays at 245 (not what I defined). Does it not work then on this stock kernel?
Click to expand...
Click to collapse
yes thats the correct setting i didnt know off hand the exact.will stay at minimum untill needed,im on on demand

Best settings for battery life?

Here are my settings and have worked very well. Almost adding 24 hours of battery life.

CBConsultation said:
Here are my settings and have worked very well. Almost adding 24 hours of battery life.
Click to expand...
Click to collapse
wow... what kind of use are you putting on it? Also are you having any issues with lag or slow response?

Daguse said:
wow... what kind of use are you putting on it? Also are you having any issues with lag or slow response?
Click to expand...
Click to collapse
Just an average power-user. I email and text a lot as I own a consulting business. I am constantly on the go and need my battery to stretch as long as possible.
That is why I kept the stock kernel and didn't over-clock. I simply removed all the bloatware and non-essential apk's that I didn't need and set up a few profiles in SetCPU and now I can get an easy 2 days of power use out of it.
As I still employ the stock kernel and stock ROM I have no lag what-so-ever. Response is perfect IMHO.

CBConsultation said:
Just an average power-user. I email and text a lot as I own a consulting business. I am constantly on the go and need my battery to stretch as long as possible.
That is why I kept the stock kernel and didn't over-clock. I simply removed all the bloatware and non-essential apk's that I didn't need and set up a few profiles in SetCPU and now I can get an easy 2 days of power use out of it.
As I still employ the stock kernel and stock ROM I have no lag what-so-ever. Response is perfect IMHO.
Click to expand...
Click to collapse
SO I am new to this... I used your same settings and my bat shows 56%. On the my screen it still shows that its jumping from 1024-245. Am I missing something?
EDIT: N/M I am just dumb and forgot to preflock!
So I set my profile to have
Screen Off Pri 75 Max 3K Min 2K
Bat 75% Pri 50 Max 7K Min 2K
Bat 50% Pri 50 Max 3K Mn 2K
I will let you know how it goes but I am hoping for some good bust in bat life.
Had some issues when waking the phone, so I changed the settings on the screen off to Max 768. Going to test.
I also moved the 50 Bat to 30 and still getting good life out of it.

Well I have been experimenting with some profiles in setcpu and I have noticed a great increase in battery life especially when in standby a lot.

So i have done this according to what works for everyone else. But... my battery still drops from 100 down to 40 in about 5hours and it has been this way since the 2.2.1 smh. I dont kno what to do. I do text alot and get on facebook mobile semi frequently but mainly text and omg the phone gets up to 104 degreez wen using or charging. Any suggestions ? Or anythjng i may be doing wrong
Sent from my HTC Glacier using XDA App

Random lockups

As per the title, I have started experiencing random system lockups since yesterday. I have had to perform two battery pulls and I'm starting to worry that my ext partition won't be so lucky next time...
I have no idea what is causing the lockups, though both have occurred while using Swype. Coincidence?
For now I'm going to set my system clock back to 600Mhz and use the default input method for a while and see if I still get lockups, at which point I will probably flash another ROM unless I can find a solution, which is where you guys (hopefully) come in. Is there anything else I can do to diagnose and/or solve the problem?
- Typed from my rooted HTC Legend -

It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version

Try interactive governor or flash latest kernel from the other thread.

TheGrammarFreak said:
It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version
Click to expand...
Click to collapse
That's peculiar, as I've had the processor on 768Mhz for a while now and I've had no problems at all before now.
As for Swype... it could be. ;P
BlaY0 said:
Try interactive governor or flash latest kernel from the other thread.
Click to expand...
Click to collapse
I'll try that, but what exactly does each governor do?

segphault said:
I'll try that, but what exactly does each governor do?
Click to expand...
Click to collapse
It manages when the processor speeds up. It doesn;t run at 768MHz all the time, that's just the highest you allow. Ondemand scales the frequency up when it's needed, and lowers it again afterward. It seems to be a little bugged in our kernels though, and causes crashes.
Interactive does a similar thing, but without polling the CPU. It also ramps the frequency up a little more quickly. I use it, it makes the phone more responsive (IMO), and also eliminates the need for profiles in setCPU (to a degree)

Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.

segphault said:
Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.
Click to expand...
Click to collapse
You'd have to mess around with kernel source code. I wouldn't know where to begin, sorry

Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App

MaBlo said:
Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
That did cross my mind but other users have reported success with it, so I figured I might as well give it some investigation.

I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows

TheGrammarFreak said:
I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows
Click to expand...
Click to collapse
Maybe not quite 19Mhz, then.
Perhaps we should do some testing to see how much processing power is needed to wake the phone quickly? Is there any way to test that?

Back on topic, I just had another lockup while using the interactive governor. This time I froze up while loading Fruit Ninja.
Now I'm at a total loss for what could be causing the lockups.
- Swyped from my rooted HTC Legend -

Seeing as nobody can seem to pin-point the problem, I'm moving to CM7 permanently as soon as it's released as stable.

SetCPU vs. CMSettings Built-in CPU manager

For those of you on CM7 (preferably RC2 or later nightlies), are you using SetCPU or the built in CMSettings CPU manager? Which is giving you better performance/battery life?
I can't help but think that the built in CM Settings CPU tuner is going to be conflicting with my SetCPU profiles.
Been using nightlies since #30 or so, and I currently run SetCPU with a normal profile, a screen off profile, and a profile for <10% battery and haven't touched CMSettings' CPU manager.
I'm contemplating just uninstalling SetCPU for a day or two and seeing what a 1017max / 245min Ondemand or Powersave governor via CMSettings ends up doing to my battery life considering there will be no screen off profile.
Any thoughts?

I dumped setCPU after a lot of testing (and even bought it on market)
I'm finding I'm much happier using inbuilt CPU settings. I think battery life is the same but performance is better due to the fact that SetCPU would sometimes get stuck in my screen-off profile when turned on causing the phone to be really slow.
I recomend uninstalling setCPU, set your ONDEMAND governor with ~1Ghz and run it... You'll find your battery about the same but much less hassle.

I have yet to try that, I somewhat feel obligated to use SetCPU since I purchased it lol. But it probably won't be the last time I waste money at the market.

Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App

Utorrent76 said:
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
its the same thing :facepalm:
Try the inbuilt one... I think its way easier

I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?

Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.

I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2

DJAeroX26 said:
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Definitely. This is the one thing I like about SetCPU is having the 10% and 5% profiles so that I can get the last few % to last forever if I need it. Although in normal day-to-day use I'm never pushing it below 20%.

ScooterG said:
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
Click to expand...
Click to collapse
Yea I see this, as far as the governor changing etc.. This is why I'm wondering if it would be easier on my phone to just run only the CM Settings one.
I notice that every 5th or so time I unlock the phone, there is an obvious lag switching from the screen off profile, and my unlock sliders jitter around and it takes 4-5 tries to unlock the phone. I think this is probably partially due to both settings switching over trying to change.
I think I might try backing up and uninstalling SetCPU for tomorrow to see how it goes.

colonelcack said:
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Click to expand...
Click to collapse
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.

redpoint73 said:
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
Click to expand...
Click to collapse
I'm not sure about CM's kernel with the over-volting but I do know that Pershoots kernel can be overclocked to 979mhz without over-volting (Pershoot told me himself).

At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted

Daughain said:
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Click to expand...
Click to collapse
Well obviously.... But why the hell would you ever need to be running at 1.8ghz? The fact that you are always using a temp-specific profile method should show you that consistent 1.8ghz isn't good for the phone...

Okay so I uninstalled SetCPU last night and I'm going to run just the CM Settings CPU manager all day to see how it goes. Running like this:
ONDEMAND governor
Min CPU: 245 mhz
Max CPU: 1017 mhz
On nightly #19 also.
Okay so its midnight almost, and I'm at 13hrs unplugged and 52% battery still. Pretty general/light use, phone is just as snappy and the lack of a screen off profile doesn't seem to effect battery at all. Liking it so far! very interesting to see the screen off profile not mattering much.

SetCPU for me. I like to have a temperature and charging profile, to prevent the phone from overheating. Even at 1ghz the possibility exists, nice to have a backup incase.

I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison

tackleberry said:
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
Click to expand...
Click to collapse
With multiple tries... If you change the settings on one, it cancels the settings on the other... Maybe it's because you had set on boot enabled on both?

im going to run the CM tuner and uninstall Setcpu and see how it runs. i never thought about this but i do get that lag when i turn my screen on sometimes. im gonna miss having the profiles but ill see how it runs over the coarse of a couple days.

overclocking

how do I overclock my vibrant safely without destroying it??

Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Try installing an overstock kernel, like Eugene373's Deadhorse Kernel, then you can download One Click Lag Fix from the market.

Just install a kernel that has oc capabilities and use set CPU to adjust the frequencies
Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA Premium App

I have overstock 2.2 with minimum at 400mhz and used spare parts to set windows to fast. This thing HAULS ASS!
Sent from my GT-I9000 using XDA App

If he asks how to install an OC kernal I'm reporting this thread to be closed.

LOL
Sent from my SGH-T959 using XDA App

after you have the oc kernel installed go into set cpu and set an audible alarm and for when your temp goes above 115 Fahrenheit, in that profile have it drop your clock speed down to 1000 or 800 to help your phone cool off before reactivating the full oc. Ive never had any problems with the cpu getting to hot oc'd to 1.2 thats not to say you wont.
Cheers

I don't think that overclocking and not destroying can be done at the same time.
Sent from my SGH-T959 using XDA App

Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Flash it, set clock speed with setcpu or voltage control, cross your fingers and hope for the best.
Sent from my SGH-T959 using XDA Premium App

All you need is a kernel that supports OC ie. (DoW, Tigersblood, Overstock, Dragon) you should be golden but double check compatibility with whatever ROM ur running.
I use "set cpu" to torque it up to 1.2(or whatever the kernel OC's to) Then i use "SystemPanel Lite" to check and make sure its actually OCing. In the system app it has a CPU Clock in the top right corner which monitors ur current cpu. When the system app opens it has a list of active applications i simply move the list up and down repeatedly really fast and watch the "CPU Clock" if it maxes out at 1.2 or whatever its good to go. I remember one time(cant remember what kernel)but set cpu showed 1.2 or 1.4 and even in system CPU info it showed OCed but if you did like i just described the CPU Clock never went above 1000Mhz. Like it was just showing as OC even tho it really wasn't it was really weird the clock would max out at 1000Mhz with dead space above it like it could go over but never would.
shreddintyres said:
after you have the oc kernel installed go into set cpu and set an audible alarm and for when your temp goes above 115 Fahrenheit, in that profile have it drop your clock speed down to 1000 or 800 to help your phone cool off before reactivating the full oc. Ive never had any problems with the cpu getting to hot oc'd to 1.2 thats not to say you wont.
Cheers
Click to expand...
Click to collapse
i never knew you could set audible alarms(guess i never really looked into it) thanks for that! running DoW221 OC to 1.4 i used to see my temps hit 120-130 it would freak me out! but never had any problems except for batt life avg 6-7hrs.
Personally my best OC ROM/kernel setup to this date has been MALICE[EDT]+Tigersblood(any release) everything works and great batt life for a OC kernel

Binary100100 said:
If he asks how to install an OC kernal I'm reporting this thread to be closed.
Click to expand...
Click to collapse
LOL
funny

Just make sure you backup before trying. Some Vibrants cannot handle overclocking (and there's no real way to know until you try). Mine is one of those, and if it can't handle it, an Odin to stock will be in your immediate future.