This is driving me crazy. I just noticed that after locking/unlocking the screen the minimum frequency jumps from 300MHz (value at boot) to 787Mhz. I did some little digging and I've found out that the script
does indeed set the scaling_min_freq at 787Mhz:
So I tried to modify the value 787200 to 300000 but the "issue" is still there. If I reset the min freq. to 300MHz from a specialized app then it switches again automagically.
I doubt this is done by the ondemand governor, since usually the scaling_min_freq parameter is out of governors scope, but I can't be sure about it, I see it has quite a large number of parameters compared to the ondemand governor I've seen in other phones.
My phone is rooted. Any chance anyone can give it a check with rooted or unrooted phones? To check it one must have SetCPU/Voltage Control/ROM Toolbox (pro) or any similar application. Also CPU Spy would help since it would show nearly 0% of usage for the frequencies below 787MHz, but it wouldn't help checking this on real time.
Code:
/etc/init.qcom.post_boot.shCode:
echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freqI doubt this is done by the ondemand governor, since usually the scaling_min_freq parameter is out of governors scope, but I can't be sure about it, I see it has quite a large number of parameters compared to the ondemand governor I've seen in other phones.
My phone is rooted. Any chance anyone can give it a check with rooted or unrooted phones? To check it one must have SetCPU/Voltage Control/ROM Toolbox (pro) or any similar application. Also CPU Spy would help since it would show nearly 0% of usage for the frequencies below 787MHz, but it wouldn't help checking this on real time.
Aucun commentaire:
Enregistrer un commentaire