[Nexus 7 Original Development] demandarin:
my overclock sticks now, even after screen is turned off

My 1.6ghz overclock is sticking even after screen turns off. I use CPU spy to confirm. Plus before if I cut screen off n on, the system tuner slider will go back to 1.3ghz. Same with trinity kernel toolbox. Now it sticks and both of those apps show the slider all the way over to 1.6ghz.

Now what I did earlier was use system tuner to slide the Max freq. Slider to 1.6ghz. Then I opened Trinity Kernel toolbox. I opened it to automatically enable that increased I/O performance(like i mentioned before in other post) and to see if the slider was on 1.6ghz. Which it was. Then I ran quadrant. Which gave me the highest scores I've ever had, to date, and that I've seen. Only seen 1 or now 2 others who scored just as high as me. This was earlier. Tablet screen timed out several times and I've used tablet off n on since then. So I noticed my elixir 2 widget still showed 1.6ghz(I have a bunch of system things set to that widget so I see everything with how my device is performing in real-time, on my homescreen). I'm like hold up. I never reactivated the overclock after the initial time(when I benched). Screen has been off and on several times since then. The freq. Should've resetted back to 1.3ghz Max. As this how it was before since motley trying to figure out how to change this. So I go into CPU spy to see if this is a fluke or maybe my widget stuck. Well I reset the timer then refreshed. CPU spy shows the 1.6ghz still active. If I keep refreshing it, it shows more time elapsed at 1.6ghz. I look back at widget and its showing 1.6ghz.

So I'm thinking its the combo of what I did that's keeping it still on 1.6ghz. Also, I didn't set anything to apply on boot. I think by using system tuner to apply overclock, then immediately opening Trinity kernel toolbox, its keeping my 1.6ghz active. No matter if screen cuts off or not. Now I'm almost positive if I reboot my nexus 7, it'll default back to 1.3ghz. Haven't tried THST aspect out yet. But for right now, my 1.6ghz is sticking without me having to re-implement it every time screen cuts off. Even after deep sleep the overclock is sticking. I thinking maybe by system tuner being used tl enable the overclock. Then opening up trinity kernel toolbox, TKT Might be keeping it active. Either way, it's working for Me.

Only other thing I did, in addition to that, which I DONT even think is related, is I went into developer settings. I decrease speed windows animation and transition. Instead of 1x, I put it on 0.5x. UI is faster like that. Speeds those things up. Then, I disabled HW overlay. Underneath it it says always use gpu for screen compositing. Then I enabled force gpu rendering. Which force use of gpu for 2D drawings. With that combo and what I mentioned before, is how I scored so high on quadrant. Not sure if this developer settings I changed had any influence on the overclock sticking but thought I would mention it also.

Any thoughts on why it may be sticking on my device? I have no complaints though about it ;)

---------- Post added at 09:40 PM ---------- Previous post was at 09:30 PM ----------

I don't have Trinity toolbox installed on my prime. I was talking about that script CWC made to flash. I flashed it on my prime and didn't improve its I/O scores/performance.

Plus I asked around and its said Trinity kernel toolbox will likely work on any kernel, as long as features are supported in the kernel. Its not a tool to only control trinity kernels. There are others who use the toolbox with other kernels also.

Not related to what I posted on my Overclocking sticking, but i used the toolbox on this motley kernel and it works also. Allowing me to change things. So the toolbox is not trinity kernel specific. Only thing is whatever kernel you using needs to habe features or some lf them, thsts adjustable in the toolbox.