yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] hecksagon:
It depends on where you are at fps wise. At 15 fps an extra 1fps isn't going to do much. But if you are at 30fps, you might see a 3fps increase, which can be the difference between annoying and playable. None of the games out for Android are complex enough to be dropping our gpus into ranges where overclocking is really benefiting us much.
[Nexus 7 Original Development] antiochasylum:
1.0.11 - 1.7 - 520. = 6445

On my own compiled liquid smooth rom.
[Nexus 7 Original Development] hecksagon:
So after fooling around with the cpu slider and testing the different gpu ocs it seems like there is definitely a bottleneck we are hitting. Going from 416 to 484mhz, while being 15% higher in clockspeed, only resulted in an 8% increase in performance. 520 mhz fares even worse. The cpu can be ruled out as the bottleneck since my scores were virtually identical at 1300mhz and 1700mhz.
[Nexus 7 Original Development] M3drvr:
How are your temperatures all so low? Playing games i'm always at or above 60C with -125mv. Thats with a stock 1.3ghz too and 484gpu. At just sitting there its at around 40C. which is above 100 degrees. How your at 90 is beyond me. Unless your sitting in a refrigerator.
[Nexus 7 Original Development] leelaa:
Try the no oc gpu. Allthough your device can handle 484 it may struggle a but more than others to use it. After all not all devices are the same. I may be wrong but you never know.
[Nexus 7 Original Development] giveen:
1.0.11 is causing a total system lockup for me, wiped cache, still bootloop

flashed back to 1.0.10, still bootlooping

fixed by reflashing ROM and 1.0.10
[Nexus 7 Original Development] CharliesTheMan:
There could be a lot of other variables too as far as your configuration goes. And the rom I'm running may have something to do with it along with apps and a million other things. I'm running my voltage stock but the post above mine is probably spot on with it just being a difference in chips.
[Nexus 7 Original Development] DJLamontagneIII:
There also comes a point where you undervolt to much and it actually causes it to generate heat.. seeing as the chips do differ from one to another I would suggest you try a bunch of settings so you can really dial in your specific chip
[Nexus 7 Original Development] M3drvr:
Well it handles the 520 GPU no problem too with a 1.7ghz clock. Thats what puzzles me, at stock clock and only the 484 its way under its potential.

As for trying stock voltage i just get higher heat. With it being undervolted i've actually cut my heat down by a few degrees.

Maybe my device just runs hot.
[Nexus 7 Original Development] CharliesTheMan:
That 125 undervolt is kinda steep I would probably try different increments and see how it does.

What governor are you running? Oh yeah also, if you have more than one CPU control app set and they're conflicting that will cause heat. Also power saving apps, task managers, stuff like that will cause a lot of problems, and mobile security apps like lookout mobile are also famous for generating heat.
[Nexus 7 Original Development] M3drvr:
Running on interactive governor. All i use is System tuner. No other apps to control the CPU or anything for saving power or security. I like to keep it as minimalistic as possible. I'll bump up the voltage to see though. I'm just running stock frequency at the moment. I'll report back in a bit.
[Nexus 7 Original Development] daveleebond:
Does this revert to 1.3ghz after wake? (1.6 oc)

Sent from my N7
[Nexus 7 Original Development] M3drvr:
True
[Nexus 7 Original Development] DJLamontagneIII:
1.0.11 has the powerhal fix but the others don't you can flash thishttp://db.tt/VHDel8Y8 to fix it on the older builds
[Nexus 7 Original Development] M3drvr:
Tried all the way up to -25mv now. Still run around 60C sometimes high 60's when gaming. Regular web surfing between 50-55C. Idle at 41 now. All at stock clock. Stock GPU too now.
[Nexus 7 Original Development] evonc:
Hmm 41 is still pretty hot. Even running benchmarks the highest I've ever seen on my tablet is 42C. I idle around 30C usually. (temps from SetCPU)
[Nexus 7 Original Development] DJLamontagneIII:
Setcpu isn't reading the temps correctly if you can see from my screenshot I have both setcpu and system tuner widgets as a test and there off quite a bit from each other.. http://db.tt/0SemIlgq
[Nexus 7 Original Development] brizey:
Is 41 really that hot? That's about what it is outside right now, so if I go sit on my patio for a while that will be where I would be starting!

That is only a few degrees above body temperature.

Where do the kernel logs start to show thermal throttling?
[Nexus 7 Original Development] M3drvr:
I didn't think it was, but according to everyone elses tablet mine is steaming!
[Nexus 7 Original Development] CharliesTheMan:
It could just be differences in readings. How are you measuring yours, we need to compare with the method.
[Nexus 7 Original Development] M3drvr:
System tuner Pro is what im using with the temperature reading out in the notification bar at 1 second interval.
[Nexus 7 Original Development] demandarin:
use system tuner for cpu temps or just use root explorer to look at it manually.
[Nexus 7 Original Development] brfsa:
Motley, i wonder if this kernel has wifi pm_max power saving features.

I just noticed my nexus uses quite a lot of battery on wifi.

Cheers.
[Nexus 7 Original Development] David Horn:
With stock my CPU temperature sits at about 40C. With this kernel and a 125mV under volt it's about 37C. I consider this normal; the only way you'll get it lower is to put the thing in a fridge.
[Nexus 7 Original Development] GreyCelt:
Anyone else having problems with Pandora not working with this Kernel? I'm not sure if it's the ROM or the Kernel but Pandora just sits there with the "thinking circle" spinning and never actually plays a song. I'm using the CM10 Kang grouper ROM from this post: http://xdaforums.com/showthread.php?p=29694736#post29694736

Nevermind... :o I must have just had a bad WiFi connection because it's working fine now on a different WiFi.
[Nexus 7 Original Development] M3drvr:
According to previous people, theirs idles below 20C though. Lol. Thats what i don't understand. And then tops out at 37 under stress. Mine idles at ~40C. In deep sleep it will be around 22C. i thought i have some sort of freak tablet.
[Nexus 7 Original Development] giveen:
This kernel and Modaco JR5, pandora works fine.
[Nexus 7 Original Development] demandarin:
Those people must be reading the temps wrong. Lol. I seriously doubt anyone is idling at 20C unless they live in Antarctica or something. Or have ac constantly blowing on tablet.

Mines idle around the same as yours, 40C or Lil less. I've seen mines go as high as 65C though. From benchmarking performance mode with highest speed.

@motley. I ended up reverting back to the 1.0.10 build. I'm not sure what happened. New build ran fine for a day or 2. Then started rebooting randomly. Especially when I turned the screen off. I tried reflashing that kernel but didn't help. So I reverted back to latest stable release and everything working great. Just a f.y.I.
[Nexus 7 Original Development] thracemerin:
Mine idles in the upper 30s most of the time, it's idle at 36 right now while I'm in this server room at work (which is essentially a gigantic freezer), anyone saying their tablet idles at 20C is either wrong or getting wrong information from the software they are using to get the data.

Also M3drvr is above the arctic circle , so its essentially the same as being in Antarctica only North rather than South :p
[Nexus 7 Original Development] DJLamontagneIII:
Same here 40 at idle and up to 60 with heavy use tested with system tuner.... its setcpu its off by like 20c so if you take that into effect ours would be reading the same as theirs 20 and 40
[Nexus 7 Original Development] crg31953:
I'm currently running 1.0.10 and my temps are always in the 40-50°C range.

I'm running max at 1.6, min at 204, on demand and an across the board -75mV.

I play around a little bit, but seems to be a pretty normal temp range.

FWIW

It's A Long Way To Nowhere........

It's The Only Road I Know!
[Nexus 7 Original Development] M3drvr:
Its currently 9C out. Not that cold. At night it gets into the negatives though. And i've seen my phones cpu temperature read -50 once. Left it in the car for 2 hours by accident once.
[Nexus 7 Original Development] evonc:
Looked into the temp differences and setcpu/antutu are reading battery temp where as system tuner is reading the cpu temp.

Sent from my Nexus 7
[Nexus 7 Original Development] M3drvr:
Thats what i figured was happening! Cause my battery temps were more on board with what others were reporting in the 20s and topping out at 35ish.
[Nexus 7 Original Development] evonc:
I was going with the general feel of touch since it always felt very cool to touch so I assumed SetCPU was reporting correctly.

Sent from my Nexus 7
[Nexus 7 Original Development] _motley:
v1.0.12 now released

v1.0.12 is now released:cowboy:

Please see OP for details. Let me know how it goes. Thanks for all the feedback! I'll check back later tonight when I have some free time. I am on vacation with the family ATM, so I have to grab free time here and there when I can.
[Nexus 7 Original Development] luke05dee:
Thank you very much. One quick question though. May I ask what this means

Sorry for the stupid question, just not to sure what it means, like does 520mhz work now? As I thought it was useless frequency as the GPU clock speed wasn't the bottleneck of gaming performance anymore. So does 520mhz work? :) Thanks, sorry if it's a stupid question.
[Nexus 7 Original Development] V8vroom:
128 1700/no GPU oc is rocking for me!! And now new builds?!? :)
[Nexus 7 Original Development] brizey:
lol, it is 40C here right now (Dallas).
[Nexus 7 Original Development] mkiker2089:
As for 520 we are seeing improvements at it but if it justifies the heat and battery drain are unclear. He seems to have put extra magic in this one as 520 works well. Seems as if they cleared some bottlenecks to make it so.
[Nexus 7 Original Development] brizey:
Looks like thermal control sets in at 70C. I ran the setcpu stress test with both freq and temp notifications from system tuner on and it ramped up to 70C at 1.62GHz then dropped back to 1.2GHz where the temp came back down.
[Nexus 7 Original Development] bschrib:
Holy smooth batman! This is buttery compared to your 1.0.10 (480), and I thought that was quick!

Thanks, sending a beer your way!
[Nexus 7 Original Development] leftfork:
1.0.12 is super snappy my friend ty :thumbup::thumbup:
[Nexus 7 Original Development] brizey:
Cracked 63 fps
[Nexus 7 Original Development] evonc:
Need more of whatever you did in this new version. results with 520 version.

Sent from my Nexus 7
[Nexus 7 Original Development] _motley:
Thanks for the feedback, glad to hear it!

Yes, I took a quick glance a the BCMDHD driver and it appears to be using it.

Thanks, let me know how the new build is working. I think it is a bit better than 1.0.10 stable, but I am still waiting on the verdict:fingers-crossed:

Also, I think I saw a post where you asked...yes, I hope to take what I learn here and apply some of it to the Prime kernel when I get a chance:good:

The last two versions do not and there is a zip a few pages back for earlier versions. Give v1.0.12 a try and you should be good to go.

You will see the throttle kicking in at 60C (cpu temp, not battery temp as SetCPU apparently reads). System Tuner shows temp in a nice graph so you see it action. In the kernel log (type dmesg from a command prompt as su), you can see it kicking on at 60 and throttling back until the temp drops.

I have reverted this back as a few have been asking about it. I hear there is a hw fix for those with the issue, so I hate to try to fix it this way since it affecting others ability to go with a dimmer setting.

You idea is an interesting one, but it would take some work to implement and test. You may be able to do some of with sysfs (see /sys/devices/system/cpu), but I am not 100% sure since cpu0 is kind of the master when it comes to a lot of policies etc. The algorithms and hotplugging already in place work pretty good to startup/shutdown cores etc. , so I won't likely be implementing anything beyond tweaking what we already have in place.

Nice scores, thanks for sharing. Keep these v1.0.11 zips handy if you still have them and they work for you.

In the latest version v1.0.12, while we will lose a tad in the OC department, we will gain a bit in the GPU department, save some battery, make a little better use of the quads, and generate quite a bit less heat. And, hopefully this version will be stable for everyone.
[Nexus 7 Original Development] demandarin:
Breaking personal records on new build!

these builds just get better and better. flashed latest 1.0.12 build with GPU OC @ 520mhz. I ran nenamark2 and scored an all time best of 64.7FPS this was @ 1.5ghz CPU speed on performance governor. then I ran quadrant @ 1.6ghz on performance governor and got an overall all time best of 6286. so this kernel kicks a$$ for me. I'll keep running this GPU @520mhz and see how battery life is. I'll eventually try under voting it. to help keep temps. down. I'll take baby steps though going in increments of decreasing it by -25mV.

keep up the great work motley! very glad you own a nexus 7 also. your kernel work fabulous with stock ROM. we are still in the beginning phase f nexus 7 and already making leaps & bounds in performance and stability.

so far new kernel is very stable. I will play some games like Nova3 online multiplayer to see how it likes the GPU OC @520mhz. I'll report if anything acts weird.

THANKS!

@other users Report battery life you noticing on GPU OC @ 520mhz
[Nexus 7 Original Development] DJLamontagneIII:
1.0.12 is so smooth and snappy.. I'm currently using this with latest paranoid and its awesome ... this is the real project butter ;):D
[Nexus 7 Original Development] fr4nk1yn:
Insane! X.11 wasn't stable at all for me, x.10-484 WAS the fastest.

X.12-520 got me a nenamark score of 64.7 at 1.5ghz. Played modern combat 3 all night, seems stable but it's a battery good playing games, but it's always been.

Stellar work!
[Nexus 7 Original Development] t_007_v2:
who fed my N7 the spinish???? v12 is impressive THX motley!!!!!!!!!!!!!!!!!!!! going to do some web slinging "testing" above NY with spiderman.

64.5fps on nena2 at 1.5, 520
[Nexus 7 Original Development] demandarin:
Update: gaming with nova3 online multplayer was flawless with gpu @ 520mhz. I dialed the CPU OC down to 1.4ghz(its still plenty fast but better on battery/heat). So far I'm able to undervolt it by -75mV across the board. Undervolting worked good on 1.5ghz but I decided to try 1.4ghz. I'm shooting for great battery life and great performance. Best of both worlds. So even if I keep the CPU oc not as high, I still have the gpu @520mhz to beef things up.

NEXUS7 is my new favorite device. ;)
[Nexus 7 Original Development] V8vroom:
Getting some launcher redraw on the newest kernels. Anyone know of a script for the N7 to lock in the launcher? Found some for the Galaxy Nexus, but not for the 7. Could a kernel cause this? Thanks.
[Nexus 7 Original Development] LINKSLOVESANDROID:
amazing kernel. tried batman dark knight rises on stock kernel and it was lagg. tossed on this badboy, butter smoothL:p
[Nexus 7 Original Development] mrRobinson:
Yep been on 12 all last night with no issues. Use 1.4 CPU and no gpu Oc. Seems stable to me.
[Nexus 7 Original Development] crg31953:
I'm currently running 1.0.12 with 520 gpu oc. Max at 1.6, min at 204, and interactive. Also an across the board - 75mV.

This kernel is super fast and super smooth, also seems to be running cooler!

Excellent job Motley, Thanks!! :D

It's A Long Way To Nowhere.........

It's The Only Road I Know!
[Nexus 7 Original Development] danielsf:
Been running 1.0.12 and everything seems to be running well. I decided to flash the 484mhz zip and ran some benchmarks and then the 520mhz and repleted the tests. The 520mhz was consistently faster in every GPU benchmark than the 484mhz, and the 484mhz never beet or matched the 520mhz once. This tells me that 520mh does defiantly work on my tab, but the performance difference isn't as large as I would have expected, which I am guessing is due to bottle necks. But for me, as I have recorded consistently that 520mhz out performs 484mhz I'm going to stick with it.

This has been a good day for GPU overclocking, my international s3 has one, if not the most powerful gpu in the android ecosytem today, and a way to overclock the GPU has just been found and I can safely overclock the s3's GPU from 440mhz to 700mhz (this isn't a typo) with a safe amount of heat at this frequency (I'm guessing due to the new 32nm construction) and the GPU clock speed at this frequency is still the bottleneck so you do get a great performance increase. :D Sorry for that tangent, I am just happy. I like overclocking the GPU, as unlike overclocking the cpu, from a user experience stand point you can notice it straight away when playing good games and never been much of a fan of CPU overclocking. Anyway, I'm happy, everything is working great. Thank you very much again :)
[Nexus 7 Original Development] phonic:
I don't think there's any doubt that 520 > 484 > 416 as far as benchmarking and performance goes. The question that was raised was whether the slight boost in performance is worth the cost (ie: heat and battery life). If you get a 4% performance boost, but get a 10% higher battery drain (I'm making these numbers up by the way), is it worth it? That's a subjective question and up to each person.

Based on earlier posts, it seems the best bang for the buck is the 484, which is what I'm staying at - quite happy too. I personally don't have a need for more GPU OC. In fact, I also stay at 1.5, even though I tested 1.624 without issue. I personally prefer a more moderate performance-battery mix.
[Nexus 7 Original Development] t_007_v2:
using 520 gives me better performance in games hands down. my N7 is plugged in when gaming so battery use is moot, more horsepower please (:. the most taxing game seems to be spiderman on my N7. the stock kernel gives very obvious lag with the 520 gpu it's a fun game to fly around the city now. nova 3, dead trigger are silky smooth and the same with modern combat 3 on the N7.

others like Auralux, Samurai II Vengeance THD, Zen Pinball THD, Siegecraft THD imo just don't tax the gpu enough to show a meaningful difference.

avadon

wasted land

world of goo

airattack hd

riptide gp

sentinel 3 is a favorite

zen pinball

i have like 45 games on my N7 haha.

demos like glowball and kernels like motleys v12 show the future is very bright for tegra 3 tablet gaming.
[Nexus 7 Original Development] fatboy547:
I flashed the 520 version. Is the gpu overclock to 520 by default? How do I check?
[Nexus 7 Original Development] thracemerin:
Yes, it's overclocked to 520 by default.
[Nexus 7 Original Development] ivwonka:
Though it would be cool, if we had an app to control the gpu clock speed on the fly like we can with cpu.
[Nexus 7 Original Development] thracemerin:
Sysfs for CPU control is in the default kernel, GPU clock control is not, someone would have to code this from basically scratch or find another tegra3 kernel that already has it and port it over.
[Nexus 7 Original Development] czater:
Like I see I/O results from Quadrant benchmark are so good! :D how did u do that? :P

Also is o/c to all cores 1.7 or only for core0? I hope for all :D
[Nexus 7 Original Development] brizey:
Look in the trinity thread for the script or but the trinity kernel toolbox which automagically runs the scripts.
[Nexus 7 Original Development] superleeds27:
Any decent apps to control UV etc. System tuner isn't the best!
[Nexus 7 Original Development] DJLamontagneIII:
Put this http://db.tt/0zxtYDOk file in your init.d folder then set permissions to :

XXX

XOX

XOX

Reboot and enjoy your io scores ;)
[Nexus 7 Original Development] :


What does the file do?
[Nexus 7 Original Development] thracemerin:
Optimizes the file system mounts.
[Nexus 7 Original Development] :
How safe do you think it is long term wise snyways
[Nexus 7 Original Development] thracemerin:
Essentially 0 risk, anything is possible, but I've been running similar mount optimizations on all my android devices for ages without ever having any filesystem corruption or anything bad happen.
[Nexus 7 Original Development] demandarin:
It doesn't get much better than system tuner. System tuner does everything the other apps do and alot more.

You could try out rom tool box for UV. But system tuner is more in depth with those sorts of things. Try out rom tool box or trinity kernel toolbox. Both allow you to UV. I have them all bit use system tuner for majority of kernel tweaking. Good thing about rom toolbox is that it has a built in build.prop editor that works great. Does all proper formating and everything. Makes editing build.props very easy and makes a backup of original file.
[Nexus 7 Original Development] Stevenator21:
Looks like an amazing kernel, just wondering about one thing. By how much will it shorten the lifespan if over clocked and All the performance mods.
[Nexus 7 Original Development] brizey:
Probably not enough to matter. I had a pc run oc'ed for six years, and it was on 24x7 with no governor. In an old school case with just 2x 120mm fans and the stock amd heatsink. A little bit apples to oranges and anecdotal, but really, you will have some shiny new tablet in maybe two or three years. The battery will probably give up the ghost first. I think it is more like a reduced from fifteen to twelve years thing than a five to two thing.
[Nexus 7 Original Development] jaysmi32:
Where about is the init.d folder....can't seem to find it, also does it matter what rom and or kernel I'm running to apply this?
[Nexus 7 Original Development] thracemerin:
Need to have a ROM that has a boot.img that supports init.d, if you don't have an /etc/init.d folder yours probably doesn't, the stock boot.img does not.

I think if you flash 1.0.5 you will get this, then you can flash the latest again.
[Nexus 7 Original Development] evonc:
Path is /system/etc/init.d/

And its not a kernel specific command so it should work regardless of what kernel you're on automatically at boot as long as the kernel supports init.d which almost every custom kernel supports afaik.
[Nexus 7 Original Development] thracemerin:
init.d support is part of the kernel ramdisk which if all you did was root the stock kernel, you will not have. You need to flash a kernel that has a ramdisk that supports it, since motley uses anykernel it just injects his zImage into the existing ramdisk so it won't activate it.
[Nexus 7 Original Development] jaysmi32:
I have that folder, do I need to change the .txt or just throw the file in there and change the permission to what's stated?
[Nexus 7 Original Development] thracemerin:
just put it in there with the correct permissions and you should be good to go, you can remove the .txt extension.
[Nexus 7 Original Development] t_007_v2:
I'm using the stock ROM and I flashed the 105 and rebooted. I then went into system / etc and there is no init.id folder. So I go back and read the instructions to flash 105 and then immediately flash the kernel you want to use v12 GPU 520. rebooted system after flashing both kernels check with es file explorer to see if init.id has materialized & No folder by that name exists. Is there a option 2 for installing that folder?? Thx
[Nexus 7 Original Development] thracemerin:
Try just making the folder and setting the permissions to rwxr-xr-x
[Nexus 7 Original Development] DJLamontagneIII:
Option 2 flash a custom rom :p