</li>
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>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>When the current CPU frequency setting 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™.</li>
<li>On official kernels the CPU temperature is very inaccurate.</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>
-
+<br><br>
<strong>Notes for power kernel users:</strong>
<ul>
- <li>In order to set the current maximum frequency as default, select <strong>Save</strong> in the QCPUFreq menu.</li>
+ <li>In order to keep the current maximum frequency after reboot, select <strong>Save</strong> in the QCPUFreq menu.</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™.</li>
<li>The CPU temperature might be very inaccurate. To get a much more precise value, you can enable automatic <em>bq27x00_battery</em> module loading in QCPUFreq settings.</li>
projects / qcpufreq / blobdiff