yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] phonic:
AFAIK, since the screen can only handle 60fps, anything above this is a waste. I was actually getting 67-70fps (at times) using Quadrant in the 3D tests.

But I imagine that an increased GPU clocking could provide additional benefits besides just a higher FPS. In the end, as with all OCing, it all comes down to user perception. If you actually 'see' something noticeably better, that's what matters. foxorroxors seems to indicate that the 512 was giving him better performance with games. If so, that's a good thing.
[Nexus 7 Original Development] jarjar124:
hey motley..even though u didn't create the trinity kernel would it b possible to implement the color tweak the trinity kernel has on gnex or close to it? I'm just curious.

edit: also curious did anyone under clock and see any differences in performance?
[Nexus 7 Original Development] phonic:
Awesome, thanks for the info! I imagine there isn't much we can do about boosting the bus rate :(. But I don't think that's a huge problem. Even at 484, I am very happy - though I don't really play too many games.

In looking at the tegra3_dvfs.c file, it seems like it supports up to 600mhz. Is the correct, or is that just in there for other chipsets and ours is maxed at 520?
[Nexus 7 Original Development] mkiker2089:
We also have to be careful about putting too much emphasis on benchmarks. I know forcing GPU on 2d boots the score about 500 or more ( antutu) but actually makes ad based games crash between levels.
[Nexus 7 Original Development] foxorroxors:
you can tell the gameloft games dont give 60fps even at 512mhz, but to my eye atleast they are smoother, asphat 7 giving the best results, spiderman and batman show a noticeable improvement also.
[Nexus 7 Original Development] _motley:
Currently, I am not sure how to do this...not my specialty for sure. I'm sure the RGB values can be tweaked somehow or another.

One good thing I just realized...after looking at the "bandwidth maxed out" message, this is just a warning that that the calculated emc bandwidth can't be increased any further (an unsigned long variable). So, this is not as limiting as I first thought because the calculated bandwidth assumes ~35% efficiency and it requests more bandwidth than is actually needed. Nvida has this warning in place and changed their code to only warn once if this condition happens during stress tests. I'll run some more tests at these speeds and see what I see as far as performance increases. Might need some other benchmark tests.

I know some are worried about going over 60fps, but GPU performance also shows us our ability to keep up when demands are high. I don't see any need to change the voltages, they should be fine since they already are used for these clock speeds for other SoCs.

Its cool that you have this out there now and folks can report back. It would be good to hear about specific tests that can be duplicated by others to prove that 520 > 484 for certain tasks, even when EMC bandwidth requests is as high as it can go. I may do the same in the next release. It's definitely a bit more involved when you get to a certain point of increasing the clock speed as other factors will start coming into play and we want to be sure benefits are realized before committing to keeping a change and rolling it out to the masses.
[Nexus 7 Original Development] demandarin:
if you need a tester for your current kernel you working on, let me know ;)
[Nexus 7 Original Development] phonic:
Ok, so since we have motley's blessing, and since he confirmed stability in his own 520mhz testing, I decided to build another kernel that steps it up a notch (ie: 512->520 GPU OC'ing). Feel free to test it out, and please report back with feedback to help motley out with his testing!

520MHZ Version: http://core.routed.com/motley_v108_GPU520.zip

In addition to bumping the max freq to 520, I also made some frequency stepping optimizations, where it supports 484, 512 and 520.

In case anyone is interested, here is the diff:

http://core.routed.com/520.diff

This is all that was changed between motley's last github commit and the kernel above.

The prior 512mhz version is still available here: http://core.routed.com/motley-512gpu.zip

Enjoy!

Disclaimer recap:

1) I am NOT a kernel developer.

2) I am simply modifying one file in the kernel source to provide the GPU overclocking. All credit for this goes to motley who did all the actual work.

3) Just because one device can handle 512 or 520 doesn't mean yours can. It's always advisable to take baby steps to ensure compatibility.

4) I am not responsible if your tablet blows up, melts, causes (or cures) cancer, or castrates small animals who get to close to it.
[Nexus 7 Original Development] jarjar124:
wow ur on fire. tested ur kernel! works wonders but gets a bit warm when playing cs portable after 10min. do u also know how to tweak rgb values like motley mentioned?
[Nexus 7 Original Development] phonic:
Cool, glad it's working. I'm testing it on mine right now. So far, it seems about the same temperature, but I haven't really put it under heavy load yet.

Sorry, I have absolutely no idea how to adjust RGB values. If you can find out exactly what was modified in the kernel source, I can edit ours and build a test copy for you, but that's the limit to my capabilities in that regard.

Do you notice any perceivable improvement from 512?
[Nexus 7 Original Development] _motley:
That's essentially what I have too, but I skip the 512 step. I also have added a switch in the Kconfig so we don't have to adjust the numbers by hand each time to switch between between the OC frequencies. Not officially confirming stability yet, but it should be OK for most I think.
[Nexus 7 Original Development] clemsyn:
I've also built a kernel for pinoyto using _motley's kernel. Can't build my own since I have no time :) but here are the additions I made

1. CPU OC to 1.64 max (tried 1.7 but was unstable on pinoyto's Nexus 7)

2. GPU 600

3. JRCU implementation

Hope this helps with testing :)
[Nexus 7 Original Development] _motley:
Thanks! I'll PM you later hopefully.
[Nexus 7 Original Development] jarjar124:
i notice very slight improvement. i didn't oc which is probably why? if oced i might see improvements but other than getting warmer its kinda the same-ish.

edit: I'm not sure will this help but hopefully it does.. it mentions some stuff in op

http://rootzwiki.com/topic/12512-kernelgn-ltehybrid-3036-icsjbpre-uvoctuncifsotgfiopsv019jul-17/
[Nexus 7 Original Development] evonc:
I gave the 520 version a whirl and i didn't really see any difference in any of my benchmarks besides much higher temperatures than motleys official release.

Sent from my Nexus 7
[Nexus 7 Original Development] Metallice:
You won't without a complimentary increase in bus/core clock/emc to T30 levels.
[Nexus 7 Original Development] jarjar124:
pm me me 2 :) willing to test here
[Nexus 7 Original Development] _motley:
Haha, thanks clemsyn! We are all thinking along the same lines (you know what they say?!). My latest will OC to 1624...also tried 1700 and 1646 and decided to hold back on 1624 since benchmarks don't show much improvement other than warm hands LOL.

I have used JRCU in my 2.6.x kernels before. Will this still show benefits in 3.x? Would like to try a before and after to check it out.
[Nexus 7 Original Development] phydo:
On the galaxy nexus I believe stock was 307. Franco made 384 and 512 kernels. But I think the li,imitation was the bus, so the 512 is placebo at best.

Sent from my Nexus 7
[Nexus 7 Original Development] phonic:
On the bright side, that should help mitigate the ghosting/residual-image issue that we are seeing when the tablets are running cold :victory:
[Nexus 7 Original Development] evonc:
Could be but i think the 520 build is pushing too much on my nexus 7. Did a few more benches and im seeing worse performance than the official motley build. I'll try the 512 build and see if that's causing similar results.
[Nexus 7 Original Development] _motley:
What the hell, just posted 1.0.9 experimental in the OP. Others were interested too and it is just easier this way:laugh: Posting changes to git here in a minute...(done)
[Nexus 7 Original Development] jarjar124:
haha. dang im not able to test atm how the latest build is..i dont have my n7 near me atm! when i get the chance ill test it! looks good. also hope the link i posted a page back can help this kernel expand. i really think this kernel has true potential to make our n7 more fly than it was meant to be.

edit: im currently testing out underclocking and i got to say...the gpu oc pays off really well. i tried the trinity kernel underclocked had a lil lag spikes playing gta 3 but wif 1.0.8 gpu oc no lag at all..running smooth :) this edges the tk out cuz of the gpu oc..on this i get consistent 59-60 fps in cs portable..tk only 30-49...
[Nexus 7 Original Development] Rafase282:
Well if 520 was too much then lets try 500 instead =]
[Nexus 7 Original Development] phonic:
512 seems to be the happy medium so far. I don't think anyone complained about the overheating issue that 520 was having.

In any case, I'm going to flash the new 1.0.9 500mhz motley build. I think that will work well for my needs.
[Nexus 7 Original Development] Rafase282:
That's the one I'm using, UV -75mV across the board and it is working fine for me. I was playing to see the exact lowest I can UV but it was taking too much time so I decided -75 for everything, on 1.6 anything lower than -80mV was giving reboots or freezes
[Nexus 7 Original Development] phonic:
Ok, so flashed the new kernel. Weird issue (sort of).

So before flashing, I removed any custom on-boot OC/UV settings (per the OP recommendations). Booted up, and then went into System Tuner. Here, I have the option for "1540", as well as MANY more frequency steps between 1.3 and 1.624. I set mine for 1.540, and it's showing that as my max freq for the CPUs, but in the real-time graph, the top metric is showing as "1504". Going into No Frills, it says that I am currently set as "51/51" (min/max). It only has an option for 1504, not 1540. SetCPU shows the same thing. I set the OC via No Frills as 1.504, and in System Tuner it shows as "1.5" now, but that's not even an option through that app.

So there seems to be a (possible) issue with the frequency table, since some apps are seeing it as 1.54, others as 1.504, and a few other weird issues surrounding that.

Also, even though I have the System Tuner setting enabled to keep the governor as "interactive" during screen off, it's still going back to 1.3 when the tablet sleeps and wakes up. This used to be fixed with that work around.

---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------

I've been running -100mV on mine across the board without issues. Haven't tried anything lower, since that seems to be a safe number and I'm happy with it.
[Nexus 7 Original Development] Rafase282:
-100mV is fine for anything other than 1.6 for me. Are you setting 1.6 as the max witht hat -100mv?

I know all boards are not exactly the same and so other can UV and OC at different levels but I doubt the difference would be too large.
[Nexus 7 Original Development] phonic:
Outside of testing, I normally keep my tablet set at 1500. It's fast enough for me (hell, 1300 is pretty sweet!), and I don't see any noticeable benefit at 1600. However, I did test 1600 for a day or so, and had that set to -100mV as well - no issues. I have not tried 1624 yet. Since I'm having that weird 1504/1540 issue, I figured I would leave it alone for now.
[Nexus 7 Original Development] Rafase282:
I'm using 1.0 for screen off, 1.3 for regular use and if it lags then I go to max since I dont use it as much as I expected I would anywyas, I was playing a bunch of games but they were more space and in-app purchases than the fun so currently i'm not playing any games, but I will install either GTA:III or another 3d game for testing and fun.
[Nexus 7 Original Development] clemsyn:
I guess all kernel devs have a way of thinking the same old line :) Check your PM, you might be missing something in your github, could be why you don't see improvements on benchmarks :) According to pinoyto, he has no issues with JRCU implementation and pretty stable at 1624 with 600 gpu.
[Nexus 7 Original Development] Jay Aristide:
One little request :)

Any chance we could get a flashable .zip of the ramdisk (and update-script to create /system/etc/init.d) from 1.0.5 for those of us who want to use the stock ROM and have init.d support? I know you're trying to get out of the ramdisk business, but I'm really enjoying this kernel with the stock 4.1.1 image, though I had to flash the .zip for 1.0.5 then flash the later anykernel .zips to get init.d support. Something like that added to the OP for those of us who don't want to run a custom ROM would be boss :)
[Nexus 7 Original Development] demandarin:
Flashed 1.09 build gpu500(gpu oc 500mhz). All seems good. Nenamark 2 scores higher, 62.1. One thing I noticed, I can't complete quadrant, just for stress testing, on the highest CPU speed 1.62(or 1.64 can't remember). It keeps getting stuck on CPU test near the end and then reboots. It did this several times and I had no UV set up. Now if i lower the speed, the test goes through. I set my OC on 1.48ghz with -75mV across the board and it went through all tests fine.

I might eventually try out the 520mhz gpu oc. Other than higher nenamark2 scores, what benefits is this higher gpu oc really bringing vs. Previous 484mhz? Other than raising temps..lol. temps lower with UV. But so far the experimental builds seem to hold up fine. Besides the highest CPU oc speeds, for me, not holding through stress testing/quadrant. It might be OK with regular use or gaming but haven't tried yet at the highest speeds.

Who has tried out the 520mhz gpu OC? How is it holding up? Is anyone able to get through quadrant or Antutu at CPU clocked at highest speed?

P.s. my overclocks still stick after screen off.
[Nexus 7 Original Development] leelaa:
Increase the voltage a lil bit and then try.
[Nexus 7 Original Development] demandarin:
do you mean just for highest clock speed or across the board? I forgot I could increase it also..lol

Do people run 1.6ghz fulltime? I get great performane and battery life(with Uv) @ 1.4ghz. honestly, even stock cpu speeds were good. never had any lag anywhere. nova3 & dead trigger played great on stock speeds.

Alot of times ill run stock cpu speeds w/gpu overclock & Undervolting. device runs very well for me like that also. with all the kernel optimizations + features, it runs stock speeds well. I Oc cpu speeds because device lags. which it never did, even out the box.

I do like pushing device to limits to see what its capable of though ;)
[Nexus 7 Original Development] leelaa:
Just for the highest, the same was happening to me @1.6 so i increased 1.6 vol a little.
[Nexus 7 Original Development] fr4nk1yn:
I get better nenamark2 scores with the 500mhz kernel.

The 512 and 520 not only scored lower than 484 but caused what seemed to be a touch lag.

Start up also took, maybe 3x, longer to load desktop Widgets.

Found my sweet spot.
[Nexus 7 Original Development] mkiker2089:
I'm running the 500 as well and see no improvement at all. What am I doing wrong? Neither CPU master or the Trinity toolbox show GPU speed so how do I verify it?

Edit---- I get better results with 484.
[Nexus 7 Original Development] phonic:
When you say that you "see no improvement at all", are you referring to benchmarks or 'real world' usability? (or both)?
[Nexus 7 Original Development] pinoyto:
have tried clemsyn's GPU OC from 484, 520 and 600...I have to say that I get just minimal increase from 484 to 520 in Antutu benchmarks and no improvement from 520 to 600..Not sure if Vsync has something to do with it though.
[Nexus 7 Original Development] mkiker2089:
Both. Nenamark2 and Antutu both say that build 77 was peak. The new build with 484 GPU is the same. Stock voltages and tkt. Should I change the I/o scheduler.
[Nexus 7 Original Development] foxorroxors:
anyone shed some light onto which i/o is the best?
[Nexus 7 Original Development] _motley:
v1.0.10 released

Thanks for all the testing....v1.0.10 beta is now released, see OP.

Going to stick with 484MHz for the official releases for now. My best Nenamark2 scores are still at 484MHz and others are reporting the same thing. Research will continue...all this testing shows us where we stand and what may need to be done to see further improvements.

Let me know how v1.0.10 goes!
[Nexus 7 Original Development] flauchhaus:
1.0.9 results

CPU:1.5GHz -100mV GPU:Stock Vellamo:2141 Nenamark2:57.2fps (tested once)

CPU:1.5GHz -125mV GPU:520 Vellamo:2141-2152 Nenamark2:61.9fps (tested Vellamo twice)

CPU:1.5GHz -150mV GPU:500 Vellamo:2126-2217 Nenamark2:61.8fps (tested Vellamo twice)

It seems to me that the differences are really just the margins of the benchmarks and vsync - not the frequencies. My N7 freezes when I clock it at 1.6GHz when I test it with Nvidias demo game "Glowball" which should tax the Tegra 3 fully even when I increase the voltage at 1.6GHz. However if I restrict it to 1.5GHz it works nicely with an undervolt of -150mV.

damn motley you're fast - 1.0.10 already out
[Nexus 7 Original Development] Jay Aristide:
Thanks, m8

Flashing now :)

Thanks for re-adding the 1.0.5 .zip with ramdisk. A few people over on AF are starting to take a pretty big interest in your kernel builds (after seeing my benchmark results). Would you mind terribly if I started repackaging your nightlies (4 packages/night; two with GPU OC (one with ramdisk, one without), and two without (same setup), giving you credit and linking back here, or would you prefer I just link them back to this thread to sort out, themselves?

Your work is EXEMPLARY!
[Nexus 7 Original Development] pinoyto:
Good decision. I think 484 is the sweet spot for the GPU.
[Nexus 7 Original Development] Character Zero:
Is there still the bug with the OC being reset to 1.3 on a Screen On? I don't really want to fool with having the Trinity toolkit thing along with System Tuner.
[Nexus 7 Original Development] demandarin:
looking forward to flashing this when I get off in a few hours.

Question: Whats powerhal? Also what benefits are being seen from using stuff from newer 3.3+ kernel? I ask this because I seen that other new kernel released by faux123. his changelog shows alot of newer things ice never seen or heard before. is the difference between that kernel and this one major?
[Nexus 7 Original Development] fr4nk1yn:
Y'all do know the IO trick makes benchmarking look better with no real world performance boost?
[Nexus 7 Original Development] CharliesTheMan:
I switched from system tuner back to CPU Master. I'm really liking it a lot. But system tuner has the same functionality I use CPU master for, I'm pretty sure. I have the widget on my homescreen that let's me change CPU speed on the fly without opening the whole app.

So if I left my nexus on, when I wake it up to the first home screen, I just tap the widget and move the sliders and continue on about my business.

I know this isn't a solution but it's been handy for me to work with for now, just in case it's useful.
[Nexus 7 Original Development] Jay Aristide:
You mean other than significantly increasing throughput to and from /data which greatly reduces load time for your apps? Yeah, I knew that :)
[Nexus 7 Original Development] phonic:
Yes and no.

The I/O "trick" isn't really a "trick" since it does improve overall performance. By changing how the system writes out to the data partition, it will give some noticeable benefits with very little negative side effects (unless your tablet crashes while it's in the process of a write).

However, the impact it has to many benchmarking apps (ie: Quadrant) gives a much greater boost to the score than you would actually see in a real-use environment. But that doesn't negate that it does actually improve I/O performance.
[Nexus 7 Original Development] brizey:
I got repeatable, if minor, improvements in nena when OCed above 484. Like from just under 60 to more like 61.7
[Nexus 7 Original Development] _motley:
powerhal is the OS fix for the frequency reverting back to 1.3 on screen off. This is what I talked to imoseyon back a week or so ago and was working with aaronpoweruser. At first, I was replacing the wrong file and didn't realize it. Here is my power.grouper.so that I compiled back on July 20. This is surely the same thing faux123 is supplying in his kernel install, although his code could be different. This has been discussed in this thread and the cookies and cream thread as well if you want more info to see what code I changed. Credit goes to imoseyon for leading me towards the same fix that worked on the GN. All I did was remark out the sysfs call that set the frequency to 1.3 on screen off and left the rest the same.

Give it a try and let me know if it fixes the issue. This zip has to be flashed once after a JB ROM install, if the ROM doesn't fix it already. I guess it is safe to always flash with the kernel unless changes are made in this area within JB, but this is doubtful I think. Hopefully most ROMs will be supplying this soon and kernel devs won't have to worry about it. Most of us had workarounds going for it and I kinda forgot about the fix.

Not sure about the 3.3 kernel stuff, I haven't looked at his repo since he released to see if they are backports or a 3.3 base. Faux knows his stuff, so he is doing what he thinks is best. Development is hopping on the little N7!
[Nexus 7 Original Development] _motley:
You are very welcome. Feel free to use the kernel as you see fit. All I ask for is a link back to the OP. Thanks!
[Nexus 7 Original Development] seros:
Thanks motley, that powerhal fix appears to be working with cm10 and your latest kernel! Although on first boot after flashing it, it set the CPU freq to max for some reason...
[Nexus 7 Original Development] DJLamontagneIII:
Same here running paranoid and b10 and seems to be staying where I set it after flashing the zip thanks :D.. so this should be safe to flash on all the n7 roms?
[Nexus 7 Original Development] mkiker2089:
Some have asked what speed we run at and battery life. I run at 1.6 all the time and let the gov. decide what to do. The idea being it only uses full power if it needs it.
[Nexus 7 Original Development] antiochasylum:
SO close to your score _motley :P - v1.0.10
[Nexus 7 Original Development] 123egg:
Noon question... are these frequency stock?
[Nexus 7 Original Development] phonic:
The stock kernel only supports up to 1300mhz. One of the main benefits of motley's custom kernel is the ability to overclock up to 1624mhz. Installing the kernel alone won't change that, you have to manually enable it too, which gives you the flexibility to say how high or low you want to go (which isn't available on the stock version). The plus many other benefits.
[Nexus 7 Original Development] demandarin:
cool thanks!

IM on stock rom. plus I use trwp. so first ill clear data from system tuner(so any previous data like voltages & screen off governor will reset.). then ill go into twrp and flash both files in one session. New kernel first then this powerhal fix.
[Nexus 7 Original Development] Whiskey_Tango:
I flashed the 1.6 GHz and GPU oc kernel yesterday and it crashed twice on me in quadrant standard so I decided to get rid of it...

Edit: I was on stock with min and max frequencies at 1.6 GHz and the governor set to performance
[Nexus 7 Original Development] phonic:
Maybe your particular tablet can't handle 1.6ghz. Did you try a lower max freq? The kernel itself is solid, and even if you keep it at 1.3, still better than stock.