The overclock values won't change. Its noted in the kernel thread. It is being worked on. I'm testing out andrev o/c daemon script. The values are sticking or so it said even though it shouldn't. I just have to enable it after reboot. Check it out. Its so much better than setcpu or any o/c app. I always used it before in my other ports. Do not use any o/c app with it because it will override the script. http://forum.xda-developers.com/showthread.php?t=1949502
The overclock values won't change. Its noted in the kernel thread. It is being worked on. I'm testing out andrev o/c daemon script. The values are sticking or so it said even though it shouldn't. I just have to enable it after reboot. Check it out. Its so much better than setcpu or any o/c app. I always used it before in my other ports. Do not use any o/c app with it because it will override the script. http://forum.xda-developers.com/showthread.php?t=1949502
I should have put this in the thread but I didn't because I haven't tested scripts yet.
DVFS is what stopping the frequency change: Dynamic Voltage and Frequency Scaling. Pretty self explanitory but it will always change back if you try to set the clock manually, I would be careful using scripts as well, but they probably won't work.
Anyway, I disabled DVFS once I found out thats the problem changing the clock (verified by a few XDA threads) but then once I flashed that build, it boots but android.system.phone and system_ui processes just crash over and over and you can't do anything.
I have to rip out all the DVFS code and replace it with older code.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.