Does HTC DESIRE with stock FROYO use CPU THROTTLING by default or not?
If not the the SetCPU would really come in handy when the Desire is idle.
+1
I too would like to know this.
what do you mean throttling? you mean it drops speed at high temperature? or drops speed when idle?
by default the desire is set ondemand 998mhz when idle or at sleep it drops to 245mhz
hamdir said:
by default the desire is set ondemand 998mhz when idle or at sleep it drops to 245mhz
Click to expand...
Click to collapse
this is what I meant.
When you say sleep, does that mean that when the you press the power button once and the screen turns off.
Does this constitute as sleeping and thus lowers the clock to 245MHz?
ashrack0 said:
this is what I meant.
When you say sleep, does that mean that when the you press the power button once and the screen turns off.
Does this constitute as sleeping and thus lowers the clock to 245MHz?
Click to expand...
Click to collapse
yes when the screen turns off, unless a program is requesting cpu resources it will drop to 245 not only during screen off but during idle time too
you can improve all this by rooting ofcourse and installing kernel with different schedulers like interactive but ondemand is there in stock froyo
1.
So the stock HTC Froyo just uses 2 states.
When operating the phone it is at ~1GHz, but when the phone is idle it's at 245Mhz.
Correct?
2.
If the scheduler was Interactive but On Demand that would mean that the CPU clock would adapt to my usage. Such as this example:
- If I was browsing the net thru WIFI the clock would be ~1GHz.
- If I was just adding a calendar entry then the clock would probably be < 500 MHz.
Correct?
3.
Are there any slowdowns expected by using the On Demand schedular?
ondemand is in stock
schedulers like interactive, powersave and smartass can be added via root
no on demand also scales the frequencies not just two state
ondemand is good enough only sometimes late to respond to low latency like UI menus, for example interactive is more smart and responds faster there is another called smartass which is supposed to be a further modification
by the way you can notice ondemand sometimes late response while scrolling the default white messages widget in sense
HAMDIR
thx for the thorough explanation.
While browsing through this forum I noticed that the frame of mind is that interactive would give better battery life.
Why is that so?
Hamdir,
Thanks for your explanations Can I just ask you 1 more question. I have asked it on another thread but no-one took the time to give me an answer.
I have installed Richard Trip's svs V5e_1113 kernel but I do not have SetCPU installed. Which governor does this kernel use by default and is there a way (using a command from ADB shell) to use smartass governor instead? I really need to know this.
Thanks and I hope to get an answer this time.
Related
I see that several ROMs now have settings for "CPUfrec interactive, powersave, ondemand".
What do these do?
I am aware of SetCPU that was used to save battery, but how does this fit in with the above?
Do I need to use SetCPU on these ROMS, or is it automatic? Is it better with these new settings? What about Perflock?
An explanation of what all this is about would be useful.
Cheers.
Interactive is the one to toggle if you want performances with acceptable battery time. Ondemand is a little less reactive but saves more battery witout harming performances too much. Use powersave instead if you only care about battery time. That's it (i guess).
Sent from my HTC Desire using XDA App
Cheers, that explains it.
vnvman said:
Use powersave instead if you only care about battery time.
Click to expand...
Click to collapse
Keep in mind that Powersave keeps the phone running at 245 MHz. That is the very reason battery time becomes longer.
For me this is too low - the machine becomes too slow - and I did not buy a 1 GHz phone to only have it running at 245 MHz all the time.
Just play with the settings and see what works best for you.
An example of decent settings by people who know what there doing would be good.
Mine is set at screen off, 245min 245 max powersave.
Main profile is 998 max 245 min, interactive, with set on boot ticked.
Temp selected to 38 degrees, 245/245 powersave.
If battery becomes more or less important, what to change to in terms of govnor but also up threshold on advanced settings.
Thanks
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock so I have no choice to but to stay on stock kernel. I have no ext3/ext4 partition on my SD card in case you ask.
Current ROM: TB Fusion 1.1.2
Radio: 12.54.60.25U_26.09.04.11_M2
Any idea what should I do to solve this issue?
golokipok said:
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock
Click to expand...
Click to collapse
uoooo this is sooo dangerous for your handset... u can "smoke" it...
Any idea what should I do to solve this issue?
Click to expand...
Click to collapse
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
SERGI.3210 said:
uoooo this is sooo dangerous for your handset... u can "smoke" it...
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
Click to expand...
Click to collapse
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ). Is there any effect if I'm using smartass profile on those kernels I've mentioned?
golokipok said:
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ).
i hope that the processor works or not works (don´t crashes a little bit...)
but the reason of your freezes maybe (almost sure) because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
golokipok said:
there any effect if I'm using smartass profile on those kernels I've mentioned?
Click to expand...
Click to collapse
it´s possible, take this explanation, read and judge by yourself what´s the better cpu governor...
smartass (Best explanation i've found paraphrases to: based on interactive, but better.)
----
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. - SetCPU website
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. - SetCPU website
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 the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
Click to expand...
Click to collapse
Thanks for the info
SERGI.3210 said:
because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
Click to expand...
Click to collapse
You have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Anyway, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
golokipok said:
have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Click to expand...
Click to collapse
you only should do a good over/underclock & set the correct cpu governor for your daily use....
well, you know ho is @MDeeJaay? the developer of MDJ kernels and roms...
he explained smartass with this words:
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 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245.
golokipok said:
, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
Click to expand...
Click to collapse
no, no buddy... i only show the max speed nothing more... i set my cpu concretly like this;
CPU GOVERNOR:interactive
MAX SPEED:1113 MHZ
MIN SPEED:245 MHZ
PROFILE: screen off; 245 MHZ max.
245 MHZ min.
in adition i´m going to modify my syg LOL
haha..thanks again. I'm gonna try playing with the frequencies to see which will suit me
i hope someone can make a stable 1.8ghz kernel without the freeze
IT´S POSSIBLE but i don´t want to try it LOL
i love a lot my DHD
Hi,
I have installed and added setcpu profiles but i am not sure they are correct choices for me. I have virtuous unity rom with v4 kernel.
ac charging 1.7 ghz max
Battery under 70 1.5 ghz max
Battery under 50 1.2 ghz max
Battery under 30 1.0 ghz max
Temperature over 50 800 mhz max
(All of profiles have minimum 368mhz of speed)
All of them are ondemand but i dont know when to use conservative. And are these clock speeds good for us?
Can you help me about this?
Sent from my HTC Vision using XDA App
If youre using virtuous unity, you shouldnt use setcpu and use the virtuous overclock app. Its essentially the same but virtuous oc is much faster in changing your speeds.
My speeds for virtuous oc are:
Max wake: 1.5ghz
Min wake: 245mhz
Governer: ondemand
Max sleep: 368mhz
Min sleep: 245mhz
Governer: conservative
Sent from my HTC Vision using XDA App
I'm using CM7 Nightly
Latest Umaro kernel
Screen off = 280/380 powersave
<101% = 280/1.7 ondemand
<40% = 280/800 conservative
charging = 1.0/1.7 performance
temp >50c - 280/380 powersave
I don't.
As stated in the Unity notes (on their website), and as evilcuber mentions:
Virtuous overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
http://www.virtuousrom.com/p/unity_23.html
redpoint73 said:
I don't.
As stated in the Unity notes (on their website), and as evilcuber mentions:
Virtuous overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
http://www.virtuousrom.com/p/unity_23.html
Click to expand...
Click to collapse
I was using setcpu to see momentary clock speeds then decided to create profiles. So it is better to stay with virtuous OC application. I want to ask another question; does sleep clock speeds of cpu effect waking up time?
redpoint73 said:
I don't.
As stated in the Unity notes (on their website), and as evilcuber mentions:
Virtuous overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
http://www.virtuousrom.com/p/unity_23.html
Click to expand...
Click to collapse
Same here, on CM7 though (which has a built in CPU setup). I haven't used SetCPU in months. 806mhz max / 245mhz min, OnDemand governor. One less app running, the same or better battery life, and no sluggishness with profiles.
Deadly Sto(R)m said:
I want to ask another question; does sleep clock speeds of cpu effect waking up time?
Click to expand...
Click to collapse
It can. If you set a low screen off profile like 245/245 or 245/368, your phone may lock down and not wake up properly, or take time to "speed up" when you unlock the phone, which can sometimes be noticeable depending on your phone setup.
martonikaj said:
Same here, on CM7 though (which has a built in CPU setup). I haven't used SetCPU in months. 806mhz max / 245mhz min, OnDemand governor. One less app running, the same or better battery life, and no sluggishness with profiles.
It can. If you set a low screen off profile like 245/245 or 245/368, your phone may lock down and not wake up properly, or take time to "speed up" when you unlock the phone, which can sometimes be noticeable depending on your phone setup.
Click to expand...
Click to collapse
the best way is "try and see what happens" I ill try low screen off speeds and try if the hone wake up late. if so, i am going to get clock speeds higher then it was.
I searched for answers but didn't get satisfactory results, so I wanna ask my G2 peeps.
CM7 has an OC daemon, right?
Since it does, is SetCPU still needed?
How does one configure the OC daemon with profiles for screen off, battery>50% etc etc?
I am running CM7.1
convolution said:
I searched for answers but didn't get satisfactory results, so I wanna ask my G2 peeps.
CM7 has an OC daemon, right?
Since it does, is SetCPU still needed?
How does one configure the OC daemon with profiles for screen off, battery>50% etc etc?
I am running CM7.1
Click to expand...
Click to collapse
CM7 does have an OC daemon but it does not have profile settings like SetCPU. Most feel that using profiles kills the battery faster than not using profiles as the device is having to poll the system so frequently. If you just set the min and max speeds, you'll be fine.
Sent from my HTC Vision using XDA App
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Because the only reason I have setcpu is to set the profile so it goes to 500/200 mhz screen off...
I think the CM7 included OC/UC manager is pretty darn good. I wouldn't worry about using SetCPU it'll just interfere.
convolution said:
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Click to expand...
Click to collapse
Yes. You can see the exact way that each governor works, but that's pretty much the case with ONDEMAND.
convolution said:
CM7 has an OC daemon, right?
Click to expand...
Click to collapse
No, there is no background process (daemon) controlling the cpu min/max.
It only applies the settings at boot, aside from that, it does nothing.
on our devices, there are three (main) files that effect the cpu overclocking:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
writing a value to these files will make the cpu do what you want. (which is what the CM7 controls do)
You can still use SetCPU if you want... all it does is write the values to these files & the kernel handles the rest.
For example, it can be a slightly more convenient method of cranking up the max frequency if you are about to play a particularly cpu intensive game.
I also find SetCPU handy to do a quick check on the "time in state" & "memory" stats
If you want to use the SetCPU profiles, then, as OriginalGabriel pointed out, it could lead to slightly increased battery usage as SetCPU has to remain running in the background monitoring the variables.
If you don't use the profiles, then SetCPU won't consume any battery.
virtuous_oc, andrev_oc & ilwt_oc are a background process (daemon) that react to a change in screen state & write their defined settings to the above mentioned files.
The difference:
SetCPU runs in Android userspace & has to wait for the android system to send out a broadcast intent that the screen has been turned on/off before it can react & write the values to the files mentioned above.
The OC daemons do not run in userspace & detect the change in screen state at a kernel level... they will have written the values to the files well before the intent gets broadcast.
convolution said:
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Because the only reason I have setcpu is to set the profile so it goes to 500/200 mhz screen off...
Click to expand...
Click to collapse
The governor controls how the cpu steps up or down the available frequencies based on the current load.
Each of the governors use a slightly different algorithm in how the cpu steps up or down. (within Max & Min as specified by scaling_max_freq & scaling_min_freq)
The well known governors from the mainline Linux kernel:
Ondemand: at the onset of load, jumps straight to max frequency & then steps down through the frequency table.
Conservative: steps up through the frequencies & back down.
Performance: this governor just keeps the cpu at scaling_max_freq & doesn't scale down
Powersave: this keeps the cpu at scaling_min_freq & doesn't scale up
Also, there are a number of governors that have come about from the Android community, I don't have the time right now to write about all the others that I know of... but can do at a later stage if it helps?
The important thing to note, is that unless you device is staying awake when the screen turns off, the screen off profiles are somewhat pointless, as the cpu effectively gets turned off.
Sorry bout the wall of text... am at work & typed it out in a bit of a hurry... hope it all makes sense
Its not needed but u can use it
Sent from my HTC Vision using xda premium
excuse me; have question about this kernel; i couldn't post in the original thread;
by setting the min clock speed to 768MHZ & the max to 1407MHZ, How much voltage does it spend? by setting the min to 245MHZ & max to 1024MHZ how much? i overclocked to 1407MHZ , i saw more smoothness and speed; but i felt that its consuming more power!
is overclocking harmful to CPU? ( always overclocking )
Rom: MY One V RC4.0 FX
PrimoU GSM
Kernel: Latest Kiss Kernel
Hi
Political correct answer:
Of course OC "can" harm your device - like all OC´ing
Realistic answer:
Most One V devices can handle OCing up to 1.5 without problems
but since this may be specific to chip manifacturing there is no
guarantee that it is. Therefore before using any OC you should
test it very carefully.
And also - Of course running the chip at higher frequencies needs
more power. Simply physics .)
In "normal" daily use the difference is not big because the cpu will
not run at high frequencies most of the time. If you do things
like "heavy" gaming this is of course forcing the cpu to run faster.
To reduce the "effect" a little bit there is a kernel feature called
Undervolting (UV) with that you can reduce the voltage for
specific frequencies. Like OC this is device specific. So some
devices can run stable with more reduced voltage then others
BTW: why to you set the min frequency to 768?
This will limit that the frequency cannot go lower then that if the
device is idle. Running at 245 needs of course less power then 768
max
Thanks for the nice info, well, i heard that some users said that the best frequency for " My One V" rom:
Minimum: 768MHZ
MAX: 1407
I'm using "Set CPU" to OC
So setting the min frequency to 245MHZ will save more power, right?
Sent from my HTC One V using xda app-developers app
Satohiroshi said:
So setting the min frequency to 245MHZ will save more power, right?
Click to expand...
Click to collapse
Yes - especially for the time before the device can go into
"deep sleep" when beeing idle.
The only "disadvantage" is that depending on the govener that you use
there might be a small lag before the frequency scales up
Actually it depends if you notice it at all
If you use govener ondemand it should be no problem
if you use e.g. smartassV2 you might consider thinking about
using some tunables that will reduce that behaviour.
max
Thanks, yeah, i meant for normal activities, like checking Facebook,mail, watching movies ... So ondemand mode would be better
Sent from my HTC One V using xda app-developers app
maxwen said:
Yes - especially for the time before the device can go into
"deep sleep" when beeing idle.
The only "disadvantage" is that depending on the govener that you use
there might be a small lag before the frequency scales up
Actually it depends if you notice it at all
If you use govener ondemand it should be no problem
if you use e.g. smartassV2 you might consider thinking about
using some tunables that will reduce that behaviour.
max
Click to expand...
Click to collapse
What is your recommend governor to integrate with your Titanium-KISS kernel and what is your favourite I/O Scheduler tweaks, for daily use & heavy gaming?
I'm using smartassV2 & i set my I/O Scheduler to deadline until now, because it's peoples favourite
Should i change it to ondemmand to gain a better performance?
Hi
Actually there is already a lot of information about your question
in the KISS kernel thread.
Especially about how to tweak smartassV2 based on "profiles"
max
maxwen said:
Hi
Actually there is already a lot of information about your question
in the KISS kernel thread.
Especially about how to tweak smartassV2 based on "profiles"
max
Click to expand...
Click to collapse
uh, okay...i'll re-read the info once again :good: