Develop Bugs

SetCPU

I have Virtuous ROM. I installed SetCPU and what I need is the best performance and best battery life save when the screen is off, and when I am using it but not charging. I have no idea where to begin. Please and thank you!

Guahan said:
I have Virtuous ROM. I installed SetCPU and what I need is the best performance and best battery life save when the screen is off, and when I am using it but not charging. I have no idea where to begin. Please and thank you!
Click to expand...
Click to collapse
This is a good place to start.
http://www.pokedev.com/setcpu/
Read through the docs so you understand how SetCPU works and you can create profiles to suit your needs. If you need help after reading through the docs, post back.

make a profile for screen off.
max/min - like 250
priority - 75-80

MMBosstones86 said:
make a profile for screen off.
max/min - like 250
priority - 75-80
Click to expand...
Click to collapse
Yesterday, for Screen Off, I put 528 max and 528 min, on demand, and it lasted me roughly 19 hours on priority 100. Now today, it's been on for only 3 hours with same stats, and it was at 13%... Why wouldn't I want to increase the max and min?

If you're not using the phone, there's no reason to have even moderately high power settings. If the screen's off, what good is that extra Mhz getting you?

What is the best setting for SetCpu?

Guys! What is the best setting for Set Cpu? I need to conserve battery. My battery lasts about 12 hours. Im using a Reflex S 2.04 rom but i shifted to Leedroid 2.4.1. My settings are 768 On demand and 245 max 245 min on demand for powersave.
What is smart ass? How does it affect the system?

On SetCpu, I run overclocked 1200 till under 80%
Then about 80
700 at 70% battery
600 at 50%
I don't wish to run lower, as the desire gets a little wonky below 500mhz
3 profiles. I can get 3 days battery

I use no frills CPU - oc 1114, ondemand governor 245-1114.
Get about 12 he's heavy use, up to 2 days light. Today I have done 3+ hrs train journey with music, browsing and SMS, checked mail, now hanging about on this forum! 41% left.

All other governors are ****. Just use ondemand.
Im set at 128-1190 ondemand.
Sent from CM7

Meaple said:
All other governors are ****. Just use ondemand.
Click to expand...
Click to collapse
Why?
I use smartass @128-768 Mhz.

remember to use screen off feature (saves a lot of battery)

I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App

MatDrOiD said:
Why?
I use smartass @128-768 Mhz.
Click to expand...
Click to collapse
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.

for the sleep off what is the best setting? screen off 245 max 245 min on demand? or 245 max 128min smart ass?

With smartass you do not have to set a profile for screen off. Smartass uses automatically the min cpu-frequency you set. So if you set smartass for screen off, you have two "screen off"-profiles. I think that could cause problems. You should set the screen-off-profile on [email protected] to avoid waking up problems, which can occur with this min 128 and max 245 for screen off-profile.

Meaple said:
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.
Click to expand...
Click to collapse
+1 Agree totally
Ondemand is the only governor which doesnt make my phone lag.

westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
You can find this in the wiki...

westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
From SetCPU-Website:
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
smartass governor – is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Click to expand...
Click to collapse
Source: http://www.ziggy471.com/2010/11/07/smartass-governor-info/

[Q] Setting clock speed to 800 -1200 mhz?

I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?

Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...

What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.

dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)

700 MHz vs 350 MHz minimum CPU setting, which one is better for battery life?

According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.

350mhz.
700mhz minimum is not more efficient.

Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
for francos kernel it might be the case...not others

I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.

ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
I've read that ondemand is more power-hungry than interactive...

anton2009 said:
I've read that ondemand is more power-hungry than interactive...
Click to expand...
Click to collapse
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone

Franco uses 700 because of the wake lag caused by 350 when using hot plug mod (shutting off cpu1)
Sent from my Galaxy Nexus using xda premium

With 350 or 700 I still get wake lag.

i'm on franco's latest and hotplug is on and my cpu gov is set to conservative and min freq is 350mhz. no lag on waking at all..

180
Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
I'm using 180 in imoseyon's Leankernel experimental builds.. works amazing, telephone spends 70% in this state on average, at 180 undervolting at 875mV.

ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.

adrynalyne said:
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.
Click to expand...
Click to collapse
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.

But it matters every time your phone wakes up, even if its momentarily.

Only get lag and signal loss when on 350. 700 seems to give me the best sleep and wake time with no lag. I had to learn the hard way. But figured out from reading around that 350 causes some problems on any kernel/governor.
Sent from my Galaxy Nexus using XDA Premium App

The only time 350mhz gives troubles is if you set the min/max to it for sleep.

ChongoDroid said:
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone
Click to expand...
Click to collapse
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
ArmanUV said:
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.
Click to expand...
Click to collapse
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.

Actually, stock kernel, onDemand is garbage, and Interactive is best.

EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
You're absolutely right, I had em backwards lol
Sent from my Galaxy Nexus using xda premium

Same here.

EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
it's not as simple as that. when the screen is off the phone enters deep sleep as much as possible which uses (almost) the same power regardsless of min frequency. The phone obviousely will wake up from deep sleep from time to time and that's when the minimum frequency comes into play. For example, for someone who has a lot of applications syncing every few minutes or someone who listens to music a lot with the screen off (which prevents deep sleep), setting the minimum to 350 will be better. Otherwise, the savings are negligible.
This was put to test by someone here on xda (the gnexus general section) by measuring voltage and current through the battery in different conditions.

Battery problems solved/improved!!! (Two findings to drastically improve drain)

As many of you know, battery life on the One X has been lets say, poor.
I decided to narrow down the problems and try to figure out whats causing it.
I figured i'd download voltage control (SetCPU works also) and underclock the CPU, low and behold......I may have figured out why the battery was dropping so much during screen on standby.
ONDEMAND GOVERNOR!!! It was causing crazy CPU instability. The CPU was constantly changing from 340mhz to 1500mhz (or your max speed) every single second, alternating constantly.
I've changed it to Interactive and it's been much more stable now. When not doing anything, the CPU will stay at 340mhz and no longer constantly ramps up to maxx CPU speed and back down alternating.
Try this out and see if it helps you guys. I'm going to continue experimenting with the other governors, but Interactive should be the best blend between battery and performance.
Also download CPU spy to see what steps of the Speeds have been active the most.
Edit: Changing the frequencies does not do anything sadly. Will need to wait for VoltageControl and SetCPU to be updated.
BUT changing the governor does work and makes a big difference.
Going to Interactive, my battery no longer drains at around 1% for every 1-2 minutes of screen on time leaving the screen on and idle. It drains much more normally.
Tonight I will do the HTC test where you check how much battery drains for 1 hour of screen on time at max brightness. You may feel free to try it out using the dialer *#*#3424#*#* and running battery test.
I will do this tonight and upload my results/screenshots
Update:
Here are the two main tips that I have found out now to help a lot with battery and low CPU usage that is stable
1) Use Interactive Governor, it is less aggressive at ramping up to max frequency and much more efficient. Also more stable and not erratic like OnDemand Governor
2) USE APEX LAUNCHER or something besides Sense Launcher.
I have downloaded Tegrastats to show me CPU usage and have compared between Sense Launcher and Apex. Sense is very resource hungry, and CPU usage is very high. It is almost constantly has both cores turned on and usage fluctuates between 15-70% alternating on the two cores when screen is on but idle. The frequency also stays around 400mhz on idle.
Apex launcher on the other hand, uses 1 core when idle, and usage stays around 10%. It also hovers around 102-204mhz when screen is on but idle. When swiping as fast as possible to ramp up speeds, I haven't seen it go above 640mhz and usage between the two cores is around 30-50% EVEN with both cores vs. alternating 15-70% on both cores with Sense Launcher

Thanks mate
Strange, from what I remember any CPU-tool didn't have any impact on my governor and cpu behavior. Maybe this has changed with the update. So I will have another go
(Just put it on its 7th charge, gotta wait a while..)

pewpewbangbang said:
As many of you know, battery life on the One X has been lets say, poor.
I decided to narrow down the problems and try to figure out whats causing it.
I figured i'd download voltage control (SetCPU works also) and underclock the CPU, low and behold......I may have figured out why the battery was dropping so much during screen on standby.
ONDEMAND GOVERNOR!!! It was causing crazy CPU instability. The CPU was constantly changing from 340mhz to 1500mhz (or your max speed) every single second, alternating constantly.
I've changed it to Interactive and it's been much more stable now. When not doing anything, the CPU will stay at 340mhz and no longer constantly ramps up to maxx CPU speed and back down alternating.
Try this out and see if it helps you guys. I'm going to continue experimenting with the other governors, but Interactive should be the best blend between battery and performance.
Also download CPU spy to see what steps of the Speeds have been active the most.
Click to expand...
Click to collapse
What have you set your min frequency to? I take it 340?
Sent from my HTC One X using xda premium

pewpewbangbang said:
As many of you know, battery life on the One X has been lets say, poor.
I decided to narrow down the problems and try to figure out whats causing it.
I figured i'd download voltage control (SetCPU works also) and underclock the CPU, low and behold......I may have figured out why the battery was dropping so much during screen on standby.
ONDEMAND GOVERNOR!!! It was causing crazy CPU instability. The CPU was constantly changing from 340mhz to 1500mhz (or your max speed) every single second, alternating constantly.
I've changed it to Interactive and it's been much more stable now. When not doing anything, the CPU will stay at 340mhz and no longer constantly ramps up to maxx CPU speed and back down alternating.
Try this out and see if it helps you guys. I'm going to continue experimenting with the other governors, but Interactive should be the best blend between battery and performance.
Also download CPU spy to see what steps of the Speeds have been active the most.
Click to expand...
Click to collapse
I`m not seeing this at all.My phone has been on standy for a few hours..wifi on/auto sync on..ondemand governor.Battery loss about 4% in 3 hours. CPUspy reports no high frequency spikes..highest shown is 475MHz.

I believe in ARHD mike has already set to Interactive Governer.

Set CPU doesn't work it will still go over the max set. I have contacted the maker and he is looking into it hard without kernel sources. Screen shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One X using xda premium

ttav said:
I`m not seeing this at all.My phone has been on standy for a few hours..wifi on/auto sync on..ondemand governor.Battery loss about 4% in 3 hours. CPUspy reports no high frequency spikes..highest shown is 475MHz.
Click to expand...
Click to collapse
You have got the best one.
Sent from my HTC One X using Tapatalk 2

I wouldn't lose battery with screen off. But with the screen on and not doing anything. Just watching the speeds in voltage control I watched it constantly alternate with 340 and 1500.
My min is the lowest I can set, around idk 50? I don't remember. But it doesn't go that low unless screen off standby. Probably for companion core.
This is just to let people know that ondemand governor acts funky and interactive is probably the best to use.
Sent from my HTC One X using XDA

treebill said:
Set CPU doesn't work it will still go over the max set. I have contacted the maker and he is looking into it hard without kernel sources. Screen shot
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Sadly true. Don't know how these other people can claim that it's working.

Fruktsallad said:
Sadly true. Don't know how these other people can claim that it's working.
Click to expand...
Click to collapse
Use voltage control, it's free from the play store.
You can tell the difference between OnDemand and Interactive or w/e governor you choose. OnDemand not touching the screen, you can watch in VoltageControl it alternates constantly between your max CPU and 340mhz (This is about the lowest it goes while screen is on). Then apply Interactive and it will stay at 340mhz and not jump up to the max speed anymore.

pewpewbangbang said:
Use voltage control, it's free from the play store.
Click to expand...
Click to collapse
OK, I'll check it out!
EDIT: Not working at all. Sorry. You can check that it goes over your set values using CPU Spy.

Fruktsallad said:
OK, I'll check it out!
Click to expand...
Click to collapse
Yup, I just checked again and watched OnDemand be very unstable as the Governor itself is somewhat like that.
OnDemand ramps up to the high frequences so that everything is smooth, the only problem is that it's doing it way too easily. Leaving screen on and not touching it, something causes it to constantly jump back and forth between low and max frequencies.
Setting to Interactive or even Conservative makes it much more "stable"
Conservative is really good at staying on low frequences (takes longer to ramp up speeds) but as a result feels very laggy so Interactive is what I recommend as the best blend. (In general, Interactive governor is becoming the standard for most phones. I remember it being very popular on the i9100 and Galaxy Nexus)
So yea, just try out Interactive and see how it works for you. I am no longer draining battery at like 1% for ever 1-2 minutes of screen on time leaving it

Fruktsallad said:
OK, I'll check it out!
EDIT: Not working at all. Sorry. You can check that it goes over your set values using CPU Spy.
Click to expand...
Click to collapse
Yea I just realized messing with the frequencies isn't working
I will edit my OP
But setting to Interactive Governor DOES make changes

pewpewbangbang said:
I wouldn't lose battery with screen off. But with the screen on and not doing anything. Just watching the speeds in voltage control I watched it constantly alternate with 340 and 1500.
My min is the lowest I can set, around idk 50? I don't remember. But it doesn't go that low unless screen off standby. Probably for companion core.
This is just to let people know that ondemand governor acts funky and interactive is probably the best to use.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
OK i assumed standby = screen off.Switched to interactive on System Tuner Pro....i see less spikes at 475 MHz.
I don`t have time but maybe someone could test for lag between the onedemand and interactive governors. I know for sure that the Tegra 3 works better using ondemand on my prime.
Anyway interesting things gould come from this.
---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------
We really need the kernel source released so the devs can get to work.

ttav said:
OK i assumed standby = screen off.Switched to interactive on System Tuner Pro....i see less spikes at 475 MHz.
I don`t have time but maybe someone could test for lag between the onedemand and interactive governors. I know for sure that the Tegra 3 works better using ondemand on my prime.
Anyway interesting things gould come from this.
Click to expand...
Click to collapse
Interactive is very similar to OnDemand, but it is not as "aggressive" in it's frequency changes.
It is a very popular Governor on other phones and Kernels. So far, I've experienced no lag as it still hits those high frequencies, but less often and only when it needs to.
My main issue was leaving screen on and in standby with OnDemand and watching it constantly jump from low to max frequency which is definitely not correct.
Using interactive, battery drain has been much better and to the norm.
Can't wait for kernels to come out and optimize battery and performance.

pewpewbangbang said:
Interactive is very similar to OnDemand, but it is not as "aggressive" in it's frequency changes.
It is a very popular Governor on other phones and Kernels. So far, I've experienced no lag as it still hits those high frequencies, but less often and only when it needs to.
My main issue was leaving screen on and in standby with OnDemand and watching it constantly jump from low to max frequency which is definitely not correct.
Using interactive, battery drain has been much better and to the norm.
Can't wait for kernels to come out and optimize battery and performance.
Click to expand...
Click to collapse
I suggest everyone head over to HTCdev.com and post a comment asking for the One X kernel source code release.

I was going to make a new thread until I saw this.
I was able to override the Tegra 3 system using a few tricks which allowed me to change the frequency to my own, plus only allowing 2 cores to come on.
I'm at work but ill post a video soon, you only need setCPU and patience to get it to work.
I monitored this by TegraSTATS in the market for free

MrPhilo said:
I was going to make a new thread until I saw this.
I was able to override the Tegra 3 system using a few tricks which allowed me to change the frequency to my own, plus only allowing 2 cores to come on.
I'm at work but ill post a video soon, you only need setCPU and patience to get it to work.
I monitored this by TegraSTATS in the market for free
Click to expand...
Click to collapse
Great!, would be awesome if you can post it up here later

pewpewbangbang said:
Great!, would be awesome if you can post it up here later
Click to expand...
Click to collapse
Here's a small evidence for now, my CPU is set from 102mhz to 1000mhz. The bottom monitor is Tegrastats, as you can see only 2 cores are running max at 100% at 1Ghz on the CPU benchmark.

MrPhilo said:
Here's a small evidence for now, my CPU is set from 102mhz to 1000mhz. The bottom monitor is Tegrastats, as you can see only 2 cores are running max at 100% at 1Ghz on the CPU benchmark.
Click to expand...
Click to collapse
Yea similar to hotplug governor except is it always 2 cores for your mod?
Hotplug governor enabled however many cores were needed and disabled when not in use.
Either way, awesome work.
Sent from my HTC One X using XDA