desalesouche, on 20 March 2012 - 03:23 PM, said:
i could observe(if i remenber well) with setcpu in advanced option while testing rom and battery with antutu tester :
cm6.1.1-29k:sampling rate= -1 / upthreshold= -1 / ignore nice load= -1 / powersavebias= -1
cm6.1.1-32k::sampling rate= 20000 /upthreshold=76 / ignore nice load=0 / powersavebias=0
if somebody can explain difference? is it better with these change?
does flashing 32k zip on cm6.1.1-29k is making these change?
what if setting sampling rate to = 200000 tried by twrock thinking 20000 was a typo?
cm6.1.1-29k:sampling rate= -1 / upthreshold= -1 / ignore nice load= -1 / powersavebias= -1
cm6.1.1-32k::sampling rate= 20000 /upthreshold=76 / ignore nice load=0 / powersavebias=0
if somebody can explain difference? is it better with these change?
does flashing 32k zip on cm6.1.1-29k is making these change?
what if setting sampling rate to = 200000 tried by twrock thinking 20000 was a typo?
The thing about .29 kernel is that it shows up strangely in SetCPU. The first time you tap on advanced options, you get that weird set of -1 numbers. But if you click back to another tab and then back to advanced, you will see something closer to what it should be.
BUT, the numbers won't match what the boot.img should be set at. That is what I find most strange. And when I run SetCPU with .32 kernel. the numbers match what is set in the boot.img. So I feel more comfortable that things are "right" with .32 kernel boot.img. Both boot.img's are set at 76 upthreshold, and if unmodified, 20000 sampling_rate. So in theory, they should give you the same numbers in SetCPU, but they don't.
What does it all mean? I don't know.
Sampling_rate can be modified in the boot.img quite easily, so I typically just do it there for roms I modifiy.






Sign In
Create Account


Back to top








