This application allows you to lower your maximum CPU speed.
<br><br>
-This might be useful for some applications (like emulators), which cause your CPU to always run at full speed when it is really not required. You can save quite a lot of battery power if you use such applications frequently. Please note that you won't always be able to save battery power!
+This might be useful for some applications (like emulators), which cause your CPU to always run at full speed when it is really not required. You can save some battery power if you use such applications frequently. Please note that lowering the maximum CPU frequency does not always save battery power and is not always the best choice!<br><br>
+
<hr>
-IMPORTANT:
+<strong>IMPORTANT:</strong>
<ul>
- <li>Changes are <strong>NON-permanent</strong><br>
- If you want to change your CPU frequency or SmartReflex™ settings permanently, you need to edit /etc/pmconfig. Only edit this file if you know what you are doing!
+ <li>Changes are lost after:</li>
+ <ul>
+ <li>Reboot</li>
+ <li>Unplugging battery charger</li>
+ <li>Making or receiving a call</li>
+ </ul>
+ If you want to change your CPU frequency or SmartReflex™ settings permanently, you need to edit <em>/etc/pmconfig</em>. Only edit this file if you know what you are doing!
</li>
- <li>After unplugging the charger from your device the CPU will always use the full maximum speed setting. Use QCPUFreq after charging for lowering the speed again!</li>
+ <li>When the maximum CPU frequency is equal to the minimum CPU frequency the kernel might use the next frequency scaling step as the maximum frequency. For instance, if you set your maximum frequency to 250MHz the official kernel will actually use 500MHz as the maximum frequency. This is a kernel problem.</li>
<li>SmartReflex™ is known to be unstable on some devices and may cause random reboots.</li>
<li>Starting with PR 1.2, Nokia has disabled "VDD2 SR" in order to make the device more stable. This is why QCPUFreq only enables VDD1 SmartReflex™ on newer firmwares.</li>
- <li>The value of the CPU temperature might sometimes be "0". This is actually a kernel problem and not a bug in QCPUFreq.</li>
+ <li>On official kernels the CPU temperature is very unaccurate. On power kernels the temperature is much more precise.</li>
+ <li>The value of the CPU temperature might sometimes be "Unknown". This is yet another kernel problem and not a bug in QCPUFreq.</li>
</ul>
projects / qcpufreq / blobdiff