Database Users

x10 uses ondemand cpu scaling 245 - 998 mhz stock, do not use setcpu

just wanted to let everyone know this, as there are still plenty of threads out there that suggest setcpu, and it's a waste of time

Thanks dan, where you been stranger?
Sent from my X10i using XDA App

so what does it mean? it's doing what setcpu does? what about battery and temperature profiles? what if i want to force the cpu to use a lower clock speed to conserve battery?

I never understood SetCPU myself. The CPU is only used when required, so creating all these settings likely does nothing.
I'd consider it for overclocking, if that was possible.

I was also informed that our phones should do this anyway but I was suspicious of how well it does, being on 1.6 and butchered by SE after all.. it made a good deal of difference before the update.
Trying it without the update now and we'll see how it goes. Completely removed it and power cycled. Will bump in a few days with my results.

I found android got extremely laggy on 1.6 with setcpu. and I use a temp/cpu widget to keep tabs on stock behavior, my cpu sits at 245 most of the time, except when I'm using the phone

Sent from my X10i using XDA App

dan-htc-touch said:
I found android got extremely laggy on 1.6 with setcpu. and I use a temp/cpu widget to keep tabs on stock behavior, my cpu sits at 245 most of the time, except when I'm using the phone
Click to expand...
Click to collapse
What widget do you use?
I took a quick look on the Market and AppBrain, and couldn't find anything to track/plot CPU clock to see what the phone's doing while in standby.
I do use SystemPanel, but it doesn't plot CPU clock over time, only usage.

Try advanced task manager it shows cpu speed...
Sent from my X10i using Tapatalk

[email protected] said:
Try advanced task manager it shows cpu speed...
Click to expand...
Click to collapse
I'm not looking for a way to see the speed. SystemPanel will do that. I'm looking for a plot that shows the cpu speed over time, so I can see how and when it changes.

saltorio said:
I'm not looking for a way to see the speed. SystemPanel will do that. I'm looking for a plot that shows the cpu speed over time, so I can see how and when it changes.
Click to expand...
Click to collapse
Try Usage Timelines Free or seepu++ (not free and dev seems to have abandoned it)
Edit: sorry I see you want clock speed not usage. I have yet to find an app for that as well.
Sent from my X10a using XDA App

so what is SetCPU doing then? draining the battery? or is it affecting the charging process?
and what about the app CoolS? its almost the same thing as SetCPU but the only thing you can do is slow the CPU down

You can use SetCPU to:
1. Overclock (but not on X10)
2. Underclock (you know you go somewhere for 2 days and forgot the charger at home)
3. Make profiles to lower CPU freq when temp is too high
For day by day use, i'm ok with android's ondemand scaling.

use android hackers apk. thereu can see theCPU over time...
Sent from my Rooted X10i using Tapatalk

i use setcpu to underclock my X10 to 5xx mhz when the screen is off.
my batt usage is better, from 3-5% per hour to below 2%.

I've been using overclock widget to keep it to 998mhz to see if it would make a difference in quadrant. Recently i uninstalled it and i still get about the same benchmark score.

Overclocking with Jrummys?

I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2

gkallivrousis said:
I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2
Click to expand...
Click to collapse
1.2 should be no problem although all phones are different. start with the low voltage at 1.1 make sure the phone is stable. a quick test is to open the browser and load a few pages. a GOOD test is to run quadrant. then just increase the speed until it locks up. pull the battery and set it down 1 or 2 speeds and thats your max stable overclock at that voltage. most people are able to run 1.2 or 1.3 with no issues. i can run at 1.3 with no issues. any higher and after a few days (or less respectively) my phone hangs. Also increasing voltage will yield higher clocks but will drain the battery faster. just play around if the phone locks up just pull the battery. also i would not play with the manual settings until you are familiar with the basic ones first.

I am most stable at 1.25ghz LV. Currently running GummyJAR2.5 with Blueberry Theme.
No issues. I would recomend installing AutoKiller. This is not same as Task Killer. It frees up memory. Same function as the one that comes with Jrummy Overclock but you can customize it more.

auto killer waste battery we have plenty of memory on our phones

so what do you recommend for a jrummy oc? i was thinkin 1.2 on lv

I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.

friguy3 said:
I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.
Click to expand...
Click to collapse
yup...some people can run 1.4 with no problems...try upping the voltage a little

1loudsvt said:
auto killer waste battery we have plenty of memory on our phones
Click to expand...
Click to collapse
I wasn't a believer until I installed it. My ram use to run low and some times made my DX run slow. Since installing the autokiller, my DX runs smoother, zippier and consistant. I have mine pre-set at extream. As for the battery, I don't notice any difference and I am semi heavy user. I been running Autokiller for a while.

Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel

I could never get over 1.1 using jrummy untill I changed the gov, use anything but "on demand" and I can get 1.4 all day. The stock settings work well using the "performance" gov but battery life can suffer if you get crazy. Performance keeps it running at top speed all the time. Hope this helps.
Sent from my DROIDX using XDA App

Droid-Xer said:
Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel
Click to expand...
Click to collapse
Ive used similar settings and worked fine on my phone running Rubix.

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.

Old battery.

As batteries get older do they tend to run hotter? Or just make the phone hotter in general? I remember the phone running pretty cool in the beginning now it gets quite toasty from time to time.
Sent from my HTC Vision using xda premium

Do you use it more? Changed any CPU setting? I am also inclined to think that they would run hotter as they get older
Sent from my SilverBullet 'HTCDesireZ running CM7'

yes i think they run hotter and they hold less of a charge so you will see a decrease in battery life

evilcuber said:
yes i think they run hotter and they hold less of a charge so you will see a decrease in battery life
Click to expand...
Click to collapse
this is true...sometimes mine gets so hot i cant even hold my phone...no joke

smokeuout said:
this is true...sometimes mine gets so hot i cant even hold my phone...no joke
Click to expand...
Click to collapse
whats the temperature on your battery? are you overclocked?

smokeuout said:
this is true...sometimes mine gets so hot i cant even hold my phone...no joke
Click to expand...
Click to collapse
Well thats not good whether your battery is brand new or a couple years old. Are you OC'd? If so, do you run temperature profiles? How long / hard do you use the phone before it gets that hot?

Any li-ion battery will eventually be useless over time. My phone has always run very hot when using gps(rooted with oc's and all that jazz or unrooted).
Sent from my HTC Vision using XDA Premium App

Spastic909 said:
Any li-ion battery will eventually be useless over time. My phone has always run very hot when using gps(rooted with oc's and all that jazz or unrooted).
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Mine also gets hot when using gps

evilcuber said:
whats the temperature on your battery? are you overclocked?
Click to expand...
Click to collapse
yeah im oc to 1305 an it really only happens when im playing a game and charging at the same time....but battery temp always stays in the green and batt health is good ive had it tested before

smokeuout said:
yeah im oc to 1305 an it really only happens when im playing a game and charging at the same time....but battery temp always stays in the green and batt health is good ive had it tested before
Click to expand...
Click to collapse
well thats to be expected. remember the phones default clock speed is only 800mhz, so with that big overclock+gaming+charging you shouldn't be surprised to get a hot battery.

Never seen a g2 get hot to the touch myself. The battery warms when discharging heavily, but not hot. What's the point of overclocking past 1024mhz ?

ohgood said:
Never seen a g2 get hot to the touch myself. The battery warms when discharging heavily, but not hot. What's the point of overclocking past 1024mhz ?
Click to expand...
Click to collapse
ive been oc at low levels and extremely high levels and i found a spot where it seems i get the best all around performance....each phone will vary but you should try oc to higher levels if u havnt yet...careful around 1497 though, my phone just gets weird

ohgood said:
Never seen a g2 get hot to the touch myself. The battery warms when discharging heavily, but not hot. What's the point of overclocking past 1024mhz ?
Click to expand...
Click to collapse
Mine would get warm to the touch using it heavily on the charger and overclocking to 1.2ghz or so.
Not sure why you'd overclock past 1ghz. I've never seen my phone bog down with anything at 1ghz. Some like to do it though. The usual level for overclockers is probably 1.2ghz. I personally keep it at 806mhz...

martonikaj said:
Mine would get warm to the touch using it heavily on the charger and overclocking to 1.2ghz or so.
Not sure why you'd overclock past 1ghz. I've never seen my phone bog down with anything at 1ghz. Some like to do it though. The usual level for overclockers is probably 1.2ghz. I personally keep it at 806mhz...
Click to expand...
Click to collapse
so u dont see much of a increase in speed when oc above 1ghz...i think i might mess around with the numbers again just to make sure....thanks for the tip

smokeuout said:
so u dont see much of a increase in speed when oc above 1ghz...i think i might mess around with the numbers again just to make sure....thanks for the tip
Click to expand...
Click to collapse
Well I'm sure if u run benchmarks you'll of course see better performance at higher clock speeds. I'm just expressing that in my uses, I've never seen any reason to clock past 1ghz, not to mention the increased battery drain of overclocking in most cases
Sent from my CM7-powered T-Mobile G2

Somwletimes custom roms includes a different kernel that are already overclocked. Some people tend to missed this.
Sent from my HTC Vision using Tapatalk