OnDemand goveterrnor changes its sampling rate after screen off? - Verizon Samsung Galaxy S III

Noticed something interesting. Using ondemand governor, when the phone boots up, the "sampling rate" reads 50000 in SetCPU. As long as the screen doesn't go off, it remains at 50000. But after a screen off and then on, the sampling rate becomes 10000, and stays this way. Is this normal that the governor changes its parameters like that?
Innitially I thought it could be a SetCPU problem so I tried Trickster Mod. Same thing happened.
The screen off could either be a screen time-out or using a wedget to turn off the screen. They all cause the sampling rate change from 50000 to 10000. This happens on both the stock MB1 kernel and the Zeus V5 kernel. Didn't tried this on other kernels so I don't know. Neither do I know if other governors change their parameter as well,
Anyone with the knowledge can explain this? Or it's supposed to work this way?

Related

[Q] CM7 performance settings?

Without setcpu or pimp installed, if I just set the max of 1000 and min of 216 in the cm7 performance settings menu to restore on boot, will I get the same effect (the only governor setting that will stick is "null")?
Or is it still beneficial to use setcpu to set a screen-off profile?
And the screen-off profile, should the min and max be the same? 216/216? Or is it better to stagger it a little, like 216/312?
I ended up still using setcpu. The built in CPU settings did not work for me.
Sent from my G2x using Tapatalk
mmapcpro said:
Without setcpu or pimp installed, if I just set the max of 1000 and min of 216 in the cm7 performance settings menu to restore on boot, will I get the same effect
Click to expand...
Click to collapse
No, because this allows the governor to change the CPU anywhere between 216 and 1000. This is the default; unrooted stock has it like this.
And the screen-off profile, should the min and max be the same? 216/216? Or is it better to stagger it a little, like 216/312?
Click to expand...
Click to collapse
I keep it 216/216 then allow an in-call profile that goes up to 312 in case when I'm calling someone and the screen is off it needs a bit more juice.
So basically, if I have setcpu installed, but I leave profiles "DISABLED", and leave the sliders alone, then I'm getting no different result from stock? The governor will decide to use the cpu at whatever frequency between 216 and 1000 that it needs at the time?
mmapcpro said:
So basically, if I have setcpu installed, but I leave profiles "DISABLED", and leave the sliders alone, then I'm getting no different result from stock? The governor will decide to use the cpu at whatever frequency between 216 and 1000 that it needs at the time?
Click to expand...
Click to collapse
The Tegra 2 chipset doesn't allow you to change the governor settings. So to answer your question, yes the CPU chooses what frequency it needs depending on load.

Overclock Question

I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.
deadhead85 said:
I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.
Click to expand...
Click to collapse
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.
reidar.ostrem said:
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.
Click to expand...
Click to collapse
+1 This is exactly what I've done
If you set the max speed to 1.4 GHz and set the governor to performance it will drain the battery faster than if you had it set to the others. You'll most likely have already upgraded the TF by the time it dies due to overclocking. It does shorten the life, not dramatically though. You can set up underclocking in profiles.

CM10.1 CPU frequencies not sticking

I'm currently using CM10.1 AOSP [KANG] from the thread here -- http://forum.xda-developers.com/showthread.php?t=2115520. In essence, I cannot raise either the minimum or maximum CPU speeds above 384MHz.
I just tried restoring my phone using a RUU recovery.exe file, then re-rooted, S-OFF'd, unlocked the bootloader and then updated the firmware. Right after flashing CM10.1, I am still having issues with changing the CPU speed. The maximum and minimum CPU speeds I can choose are either 192MHz or 384MHz. I can go into settings > performance then change the maximum CPU speed to anything higher than that, but almost instantly after I select it the maximum CPU speed drops back down to 384 MHz. The same goes for trying to raise the minimum CPU speed above 384MHz. It makes the phone nearly unusable, as it takes multiple seconds to open almost any application and also reboots randomly quite often. Is there any way I can fix this?
Thanks!
Anyone have ideas/insight? Sorry to bump this!
Right. Here's what I did last time. I used something called SetCPU. Ticked the Set On Boot then it worked. But I unticked the ones in the Performance option.
This is what I do. Hope I help.
if you want do this also
go to system>etc>init.qcom.post_boot.sh and put this line(you can edit with simple text editor)
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
do the same for cpu1 if you want to have the same frequency in both cpu

soc temperature throttle issue

So i set my max cpu freq to be 1728. And then the temperature throttle's 3 phases to be different clock speeds of 1728, 1267 and 1036. So when the temp hits a certain temp it will throttle the cpu down to the latter two. But then when the temp decreases to the values i set, then it should go back to the desired max speed i want which is 1728 however this is not the case. I often see it stuck at 1267 even though the temperature is well below the temp settings i set. It even gets stuck at 1036 at times. Any ideas how to get it to change back appropriately? I only use synapse to configure the settings. I'm also on mahdi rom which has that performance settings which I don't know if that is causing any conflicts the settings that i set in synapse.
onecrzyasian said:
So i set my max cpu freq to be 1728. And then the temperature throttle's 3 phases to be different clock speeds of 1728, 1267 and 1036. So when the temp hits a certain temp it will throttle the cpu down to the latter two. But then when the temp decreases to the values i set, then it should go back to the desired max speed i want which is 1728 however this is not the case. I often see it stuck at 1267 even though the temperature is well below the temp settings i set. It even gets stuck at 1036 at times. Any ideas how to get it to change back appropriately? I only use synapse to configure the settings. I'm also on mahdi rom which has that performance settings which I don't know if that is causing any conflicts the settings that i set in synapse.
Click to expand...
Click to collapse
It is a bug in the thermal driver code of the kernel you are using.
Report to the dev with proper logs, and readjust the clock speeds in Synapse or reboot.

Performance Governor Freezes phone after screen off

Hi,
I tried even on latest stock rom with stock kernel.
When i set the governor to performance everything is fine until the screen is turned off.
After that i cannot turn the screen back on and sometimes it restarts.
The same thing happens if i set the minimum value to maximum frequency on interactive governor
The closest i could get is to set the minimum frequency to the second highest frequency
Is it a way to get performance governor working?
Thanks in advance

Categories

Resources