Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

myn crashes 5 secondes after i run it it set it to 1000mhz an boom Reboot
deleting it:P i'll go to xterminal next time

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

That's kinda bad. I'm sure this is a kernel issue, though. How du you normally set your device to 1GHz?

I do not have any experiences with overclocking but I can imagine that you cannot overclock your device by only setting a new "maxfreq". As I said earlier it would probably be good if someone could assist me in the overclocking part.

BTW: actually QCPUFreq's original intention was "underclocking" on vanilla kernels :)

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

You should really go through documentation before pushing the device at twice the original intended speed.

Have a look at voltage, for starters.

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

it would be luvly if i can able to change min freq. same as maximum(500 900 MHz is what i need) using this apps,hope u do it in next update.

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

I have no experience with this but when I use QCPUFreq and set the max CPU speed to 800, I do see speeds of up to 800 in Conky. Does this mean I can overclock the device with this app? Or is it fooling Conky?

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

I personally do not see the point in changing the minimum frequency. QCPUFreq's intention is to save battery power and you won't save any battery power if your CPU only scales down to 500MHz instead of 250MHz.

If you are using the power kernel you should be able to overclock the device with this app (of course you somehow have to configure the voltages before - I do not know how to do that). And I guess if 800MHz is a choice for you in QCPUFreq you have already set up your power kernel correctly :)

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

direx,

So does your application change the default values, and do these value remain after closing the app? or do the app need to remain open for the changes to last?

I ask becuase I changed my max setting to 250mhz and closed the app. Was running Conky in the background to just verify changes. Thought it worked but came back after some browsing to discover the frequency jumped to 500MHz.

Is this just a fluke? How are you verifying that your app is actually changing the paramters on the clock speed?

2d

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

You can close the application and the settings should be saved until you reboot the device or plug/unplug the charger.

The easiest way: play a CPU-intensive game (like Bounce Evolution) and log on to your device using SSH. While playing the game issue this command:
and watch the speed of your CPU.

However 250 MHz seems to be a very low speed. I just noticed that for some reason the frequency goes up one level if you set minspeed=maxspeed. If you'd set your maxspeed to 250MHz then your CPU will effectively use 500MHz (the next step on the scaling scale) as maxfreq. This is very strange - maybe it's a kernel bug (or feature :) ).

I guess I am going to remove the lowest scaling step (250MHz on vanilla kernel) in the next version as it might confuse people.

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

Hi. :)

Enhancement request here: could you translate the raw temperature value? I almost had a heart attack. Other similar apps do this, so it shouldn't be too hard, it displays 57 or so usually (58?) which I understand is about 37C?

I assume it's already on the list, but JIC.

Re: [Announce] QCPUFreq - save battery power by adjusting your maximum CPU speed
 

OK, I understand. I should have warned you that this is a raw value :)

I have one problem, though. There are two possible temperature values and both do not seem quite correct:

• temp1_input ("17" on my N900 -> way too low)
• temp1_input_raw ("44" on my N900 -> a bit too high, but seems OK)

I chose to display the raw value as this value could possibly be a real CPU temperature in Celsius. But I guess you are right that this should not be the *actual* temperature which is why I did not put a unit behind the value in the UI.

If anyone could provide a formula how to calculate the real temperature from temp1_input or temp1_input_raw I would be happy to implement the requested feature.