Hate to break up the love fest, but there are at least 5 other threads that have already had this overclock debate. Can we not debate it every time it comes up, and stick to the thread topic? The topic was asking for a widget or app that can help the user control the processor speeds from the desktop, it was not asking for your opinion of using such a tool.

I like the look of the widgets in your post Baron. Could you please post the code/scripts behind it and/or give a small tutorial on how to set them up with queen beecon for those of us that would like to have something similar on our desktops?

Good thing you came along, we would be stuck here for days in our decadent love fest. Thanks!

I posted an export code of my beecon a while back. Here:

http://talk.maemo.org/showpost.php?p...postcount=2864
http://talk.maemo.org/showpost.php?p...postcount=2867

But change the following lines to what you want. (change the Title for each new instance and change the Cmd to reflect that title) Also I've updated the script below so it doesn't output anything. (better than piping it out to sudo gainroot as I did originally)

What I do is copy the /usr/share/kernel-power-settings/ideal file elsewhere with a new name and just modify the max frequency to 1000 or 1100 for each new file. (ideal by default is 500-850mhz)

Right now, I have 3 buttons. 850, 1000 and 1100 and change as needed. when i reboot, it goes back to default of 250-600 but soon as it boots up, i change to ideal default of 500-850. =P

and to answer this thread's title question:
- yes, you can fix the cpu to 500Mhz. But why would you. ideal profile is 500-850. It never goes below 500Mhz already.

thanks for proving my point that "device running cooler" is 110% speculation.

You keep repeating this invalid argument. Why?
http://talk.maemo.org/showpost.php?p...9&postcount=33

Where did I say the quoted "device running cooler" statement?
Anyways. It's not 110% speculation. It's scientific based theory.

i apologise for going off topic here but it really annoys me when people feel the need to rant about the negatives of oc'ing, if you dont believe its safe then simply dont do it, for people who do want to overclock there are warnings to acompany every method and we all know the risks, so realy what i'm saying is if oc'ing isnt for you then dont do it and leave the threads about it for the people who want to push the boundaries of what there device can do.

Because someone needs to offset the ever-believer that recommends everyone can take up their CPU to 4.5 GHz on air, he totally did it.

Nah, kidding. But if one hopes for the forum to be a source of information and not of speculation and hearsay, a discussion is necessary and specs, expertise and experience should have their way into the discussion.

There should be two sides to every story. Al least.

Also, don't mistake ranting for warning. Do what I do. Skip over the zealots and you'll be fine. Hell, it'll save you entire threads.

I didn't think when i asked the question it would be so active a thread!
Anyway, I did find some information that might be useful to some of you. First off, i'm no expert so you geniuses take it in strides.
Why i found myself wanting more out of the original specs of the os?
Well i just hated anything that had to do with scrolling, either files or desktops, and, music playing, simple as that! Lockups and more lockups.
Ok the good, the os and hardware are tuneable, yeah! Thanks to open source!!
I found out in 2 very distinct way:
-processor speed, and
-response time
The first one being pure raw power in crunching data the other well just responding when i need it to!
Now the bad, and everybody knows, the battery.
The bad is more about me not having found the middle ground yet, but i'm close, in having a fast and responsive machine with reasonable battery life. My n900 is running with these specs:
-Titan 250 and 850 mhz most of the time. If i want to use debian i bring it up to 950
-the response time is 80 instead of 95, meaning the processing only needs to go to 80 percent to activate higher processing power instead of 95.
-and 150000 instead of 300000 to answer in time lag to the demand. Twice as fast.
I will link to the info I found on this site for this when i find it again!!
Knowing this, i decided to test it all out at different speeds and response time. Again, not over yet. I have scripts that just change these configs to match the requirements. If i intend to use the machine alot i just maxitout!! hihih But if it's just waiting for email, sms basically not using it, well then i bring it down to lowest possible settings to save the battery life. I've also noticed that playing with the response time did make a big difference for the battery. So right now i just change that value to 300000 and it's good enough until i can manage all this maybe with a script to detect screen or keyboard touch!? Well i figure that this is where the geniuses come in and help out in the making of such a thing!!

Some examples rooted,

echo 2500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 9000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq


echo 95 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold default
tried 75 eats battery,
as you go up it gets better.
echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate default
i like 1500000,
response time!!
I have scripts named accordingly to activate the different setinigs so it matches my needs. Wouln't it be great to have all this in a smart script, as I said before to know itself when to go all out and when not to.
By all means be careful with all that.
Enjoy!

echo 95 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold default
echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate default

Note the word default is not part of the line !!!!!!

oh by the way, this is so useful.



#!/bin/sh

currfreq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`
idlefreq=`awk '{if ($2 > 0) print $1}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | tail -n 1`
tis1=`awk '{sum += $2} END {print sum}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`
tis2=`awk '$1 == "'"$idlefreq"'" {idle = $2} {sum += $2} END {print sum-idle}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

echo -e "
SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking


FREQUENCY\tUSED\t\tWHEN BUSY\n"
awk '
{if ($1 >= 1000000) printf ("%.0f MHz\t",$1/1000); else printf ("%.0f MHz\t\t",$1/1000)}
{if ($2 == 0) printf "unused"; else printf ("%.1f %\t\t",($2*100)/"'"$tis1"'")}
{if ($2 == 0 || $2/"'"$tis2"'" > 1) printf "\n"; else printf ("%.1f %\n",($2*100)/"'"$tis2"'")}
' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

echo -e "
Current frequency: $(($currfreq/1000)) MHz
Idle frequency: $(($idlefreq/1000)) MHz
Kernel: `uname -r`
kernel-maemo: `dpkg -l kernel* | awk '/kernel-maemo/ {print $3}'`
Uptime: `uptime | sed -e 's/.*p *//' -e 's/, l.*//' -e 's/ / /'`
Load: `uptime | sed 's/.*e: //'`
Boot reason: `cat /proc/bootreason`
Temperature: `cat /sys/class/power_supply/bq27200-0/temp` °C\n"

SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking


FREQUENCY USED WHEN BUSY

1200 MHz unused
1100 MHz unused
1000 MHz unused
950 MHz unused
900 MHz unused
850 MHz unused
810 MHz 1.6 % 56.7 %
750 MHz 0.0 % 0.8 %
700 MHz 0.1 % 1.9 %
600 MHz 0.0 % 1.5 %
550 MHz 0.0 % 1.2 %
500 MHz 1.0 % 37.8 %
250 MHz 97.3 %
125 MHz unused

Current frequency: 250 MHz
Idle frequency: 250 MHz
Kernel: 2.6.28.10maemo-ulv-omap1
kernel-maemo: 2.6.28-maemo21
Uptime: 2 days, 2:27
Load: 0.11, 0.04, 0.01
Boot reason: pwr_key
Temperature: 25 °C

could someone post the script to use with desktop command execution widget to load ideal overclocking settings please