yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] t_007_v2:
sir, first i want to say that i'm a big fan. also to say thanks so much for all that you have done for the N7 and it's users. i have read all 64 pages of this thread and have witnessed the motley build become a great kernel! became a member today just to comment here.

sir i'm a gamer (; i use my N7 for many things moves, net but gaming is a large part of why it was purchased.

i'm posting to ask you not to give up on gpu overclocking concerning the N7 and the motley kernel. see i have tested the gpu 484, 500 & 520 against spiderman, nova 3, modern combat 3, dead trigger etc. i know the benchmarks really don't show it in the results. but in game the higher the gpu number goes so does performance rendering graphically intensive games. imo gpu benchmarks don't have enough events in the tests. a gpu bench should start with one building then add another and another to tax new gpu settings like a real game would. nova 3 has allot more going on than nenamark 2 does.

reading your posts i know the N7 cpu has heat protection. N7 gaming the cpu always reverts back to 1.3ghz my setcpu info tab "time in state" confirms this. so for right now the cpu is capped at 1.3 other levels don't matter. the gpu top on the other hand has not been found yet. imo if any more performance can be squeaked out of the N7 it's going to come from the gpu. so if you can add the 520 maybe plus to beta v1.0.10 would be great.

thx
[Nexus 7 Original Development] _motley:
v1.0.11 now released

v1.0.11 now released. Let me know how it goes! See OP for details.

Thanks, I just posted 1.0.11 for you with a 520 edition:)

No changes have been made as far as the compass goes as compared to the stock kernel. If you can narrow it down and think there is still an issue, let me know the build you are using and exactly to duplicate it.
[Nexus 7 Original Development] Cam2:
I just flashed motley_anykernel_nexus7_1.0.11_GPU520_build_127.zip, and it appears to have bricked my device. OS won't load, Recovery Mode won't load (I use TWRP 2.2). FYI... :)
[Nexus 7 Original Development] thracemerin:
Can you get to fastboot (power + both volume buttons)? If so you aren't bricked.
[Nexus 7 Original Development] Cam2:
You're correct, I misspoke. I can get to fastboot (green android on his back). It's just getting stuck on the Google logo. Looks like I'll just have to go through the pain of flashing back to stock and starting over. Oh well. :)
[Nexus 7 Original Development] thracemerin:
Try just pusing the stock boot.img via fastboot, that should avoid a wipe, that should get you going at least.
[Nexus 7 Original Development] _motley:
Thanks for helping thracemerin!

Cam2, also push the recovery.img again from fastboot. Unlike other devices, if I crash hard on the N7 I have had to push my recovery.img back several times to recover (I have done so several times during experimental testing:silly:)

Also, try using the stock GPU or 484 build and see if it works better for you. And, if you have any other tweaks that you typically start-up on boot (kernel module loads, scripts etc.), you will also want to disable them while trying out a new kernel.
[Nexus 7 Original Development] thracemerin:
520Mhz shouldn't be enough to fry your gpu, but with the way these things seem to get binned, there is sometimes a heavy variation in the quality of the chips that go on the boards where some can take a heavy OC and others just don't seem to be able to handle it, so yeah if 520 isn't working for you try a lower one, at least that way you know the issue is likely the GPU OC and not something else.

Edit: when i initially posted this i said 512 when i meant 520, oops :p
[Nexus 7 Original Development] Cam2:
Everything is fine now. Just wanted to let you know that your latest kernel with the GPU OC'd to 520 didn't work out for me. I didn't have any other tweaks. I suspect the last kernel may have pushed the envelope a little too far. Of course doing that is the only way to find out where the edge of the envelope is. ;)
[Nexus 7 Original Development] clemsyn:
Why do I get a feeling that 1.8 ghz is coming ;) Just kidding, great work :)
[Nexus 7 Original Development] boynamedstacy:
Thank god were on a Nexus! Gotta love it :)

Edit: just flashed the new 484 build and had a random reboot like 10 minutes later. Stock settings

Sent from my Glazed-over Nexus 7
[Nexus 7 Original Development] Masrawy:
I know that with stock kernel, Nexus 7 will run at 1.3GHz on 1 core, or 1.2GHz on 2,3 or 4 cores. What about this kernel? Is it 1.7Ghz even with 4 cores activated or what?

BTW, just to make sure, does this kernel enables USB OTG? I put a usb key with an adapter USB A to Micro USB, and it didn't work. Am I doing something wrong?

thanks a lot!
[Nexus 7 Original Development] 850T5m:
I'm also getting random reboots, i tried upping my voltages a little, and changing io scheduler...still rebooting :(
[Nexus 7 Original Development] thracemerin:
Which GPU clock version? If its 520 you should try another.
[Nexus 7 Original Development] cookie666:
I had one random reboot (build 126) after I flashed but seems ok now.

Should we be wiping cache/dalvik when flashing these, I dont bother.
[Nexus 7 Original Development] thracemerin:
cache/dalvik wipe is redundant when flashing kernels, so you shouldn't need to.
[Nexus 7 Original Development] boynamedstacy:
Damn... lots o reboots on 484! Gonna have to flash stock GPU I guess.

Sent from my Glazed-over Nexus 7
[Nexus 7 Original Development] 850T5m:
I was running the 484 version. I flashed 1.09 back, I'll see how that goes. It might be this new Rom I'm trying out that's making it crash...
[Nexus 7 Original Development] thracemerin:
Are you undervolted at all? If so you might want to go back to stock voltages and try.
[Nexus 7 Original Development] cookie666:
Similar result here, never had a reboot on previous 484 roms.. hmmm might go back to 1.10
[Nexus 7 Original Development] jdrom:
Me as well. Went back to 1.10 and it seems to be fine.

8GB model if it matters with Team EOS July 31.
[Nexus 7 Original Development] Rafase282:
I'm fine with the new kernel and 520 GPU OC at 1.7 interactive and sio. Stock voltages not reboot or anything.

If it matters I had flashed the new update for EOS so I did a cache and dalvik wife followed by a fix permissions
[Nexus 7 Original Development] t_007_v2:
I'm sticking with a 1500mhz 102 build with GPU @ 520. It's buttery smooth on all games with no crashes. 102 has given me stability with my best Nenamark 2 score of 62.4 at 1500mhz w performance. My N7 is temperamental above 1500mhz with constant freezes on nenamark 2 benches. Blows because if I could test 1600 to 1624 I think I could match 62.7 lol. But I will settle for super buttery game play from nova 3, modern combat 3 & spiderman. The 102 build is really making those demanding games shine. Motley kernel should be per installed on all N7s. I might test the other builds tomorrow but weary to freeze this tablet over n over again.

Bought screen screendim from play today for .99 and interestingly my little bit of flicker vanished. Contrast at 39.6 with brightness at .08 with no flicker using chrome.

---------- Post added at 01:13 AM ---------- Previous post was at 01:05 AM ----------

Very jealous because you seem to own the Sherman tank of N7s. Interested in seeing what your nenamark 2 score is on performance.
[Nexus 7 Original Development] Rafase282:
62.0fps without anything in particular done to it, like turn off wifi, make sure apps and off or whatever.

How should I go about testing this to your linking?

Edit: performance governor + vr and nanemek2 or whatever the name is = crash and reboot midway.

Going back to interactive and sio

Edit: 62.3 with wifi, sync, auto brightness off. Interactive, SIO, 1.7

Going to try 1.5, and it went down to 62.0

About the reboots, use these settings, interactive for governor, sio or scheduler, and stock voltage, do not UV.
[Nexus 7 Original Development] JaZart:
Here to report that I am also experiencing random reboots.
[Nexus 7 Original Development] cookie666:
How to change the scheduler with CM10 performance interface?

Mine was rebooting without any voltage mods at 1.5 with 1.26 build
[Nexus 7 Original Development] rockaholic112:
Sticking with der kernel for now

Sent from my portable telecommunication box
[Nexus 7 Original Development] t_007_v2:
Thanks for the test data from 1700 w 520. I just wanted to see if 62.7 could be bested. I do leave the governor @ sio as default. There seems to be little difference between the goves when experimenting. My freezes always come about when I push above 1600mhz on Anything past the 108 builds.

What I will be looking for tomorrow is a fps logger or just something that will show fps while in game play. I will then test 484, 500 & 520. Really want to see if there is a improvement in fps as motley steps up the GPU. The city scapes in spiderman, nova 3 game play should be pretty telling. Swinging above the city is very demanding graphic wise.

Thx again!!
[Nexus 7 Original Development] foxorroxors:
just hit 91fps in pro with 1.7ghz 484.
[Nexus 7 Original Development] mkiker2089:
We've officially gone too far. The device overheats on boot at 1700 and 484. I can get good tests by putting it in the fridge but for real usage it isn't effective.

1600 is better in my opinion.
[Nexus 7 Original Development] cHarOn99:
had same with 1.0.10, I am back at 1.0.8
[Nexus 7 Original Development] David Horn:
Working well here - running stock GPU speeds and 1.4GHz, with a blanket 125mV undervolt.

Very happy with this kernel, thanks Motley! Only thing that's puzzling me is the backlight increase. I use my N7 in bed and it's a little too bright even on the stock ROM.
[Nexus 7 Original Development] _motley:
Reverted v1.0.11 beta back to alpha status after too many reports of random reboots. Please use v1.0.10 unless you are assisting with testing.

Thanks!
[Nexus 7 Original Development] Annihlist:
Edit: got the random reboot when device was sleeping hahha

Might be device specific. I was playing crash bandicoot on psxemu for 1 hour with 1700mhz and 520mhz gpu maybe I got a good SOC
[Nexus 7 Original Development] demandarin:
new build sounds interesting. Zram added is great. will likely test out after work. v.1.010 been running great w/ uv. the new build might need voltages increased for speeds above 1.6ghz+.
[Nexus 7 Original Development] leelaa:
I dont seem to have any problem @1700 520 gpu, gave asphalt 7 a good run. Went back to no gpu ocbas i was just testing the 520.
[Nexus 7 Original Development] chosen14u:
Tried latest with 484 gpu,just gives me bootloop,back to 1.0.10
[Nexus 7 Original Development] foxorroxors:
mines rock solid at 1.7 1250mv, guess were hitting the limit and finding out whos chip is the best ...

Nexus 7 @ 1.7/484 CM10

HTC Sensation @1.6/440 RevHD
[Nexus 7 Original Development] pinoyto:
I beat you...I got 1.7 at 1237mv with GPU at 600 :) with clemsyn's kernel
[Nexus 7 Original Development] leelaa:
Can u link me this 600 gpu? Would be very interested in trying it.
[Nexus 7 Original Development] :
Alright I will do some more work and duplicate it a few more times and screen shot it on maps but if no one else has this issue it could be that mine doesn't play nice with custom settings probably(your kernel). ill do it later today when I have free time (heading to bed work graveyard :{)
[Nexus 7 Original Development] phydo:
Just saying, on .11, 484 gpu, which I flashed last night, is the first time I had my N7 shut off while charging overnight. Other than that, love the kernels!
[Nexus 7 Original Development] _motley:
The 1250mV is the "core voltage" that has been raised in 1.0.11 from 1200 to 1250mV. The highest "cpu voltage" value you should use with under voltage control is 1237mV. If you set it above that, look in the kernel log and you will see an error as it tries to set the frequency. For the highest frequency, you can't raise the voltage past the initial value. For 1.6, you could if you were having an issue, but not above 1237.
[Nexus 7 Original Development] foxorroxors:
so whats next for the kernel?

Nexus 7 @ 1.7/484 CM10

HTC Sensation @1.6/440 RevHD
[Nexus 7 Original Development] hanthesolo:
Well, to finally put the GPU clock controversy at rest, I tried 1.0.10 @484 and 1.0.11 @520 in the latest GLbenchmark, using the new egypt HD benchmark on-screen. 10.0.10 was at 1.6 GHZ O/C, and 10.0.11 was at 1.7 (which doesn't really matter, but I thought you might want to know. The results were quite interesting actually, as I have finally found something that will bring our device to it's knees. I merely got 15 FPS with the GPU @484, and 16 FPS with it at 520, which clearly shows that something is capping our GPU transfer speed, as I should have gotten over 10+ FPS extra with that OC. So using this data, it is my personal opinion that 484 is the highest we can go and still see a tangible benefit.

@motley, I ran V11 today for awhile, and I was completely solid at 1.7 GHZ, although a lot more heat was generated than at 1.6, due to your bumped voltages. My issue was with it rebooting as soon as I turned the screen off, at any frequency. I flashed V10, then reflashed V11 for my test, and it seemed to go away in the one time I locked/unlocked it to test, but I thought you may want to know.
[Nexus 7 Original Development] CooLoserTech:
Which is better the 484 GPU or 520 GPU. I pretty much use games on my nexus 7. Which was will give me good performance, and good battery, while maintains to keep the device from over heating. Share
[Nexus 7 Original Development] hanthesolo:
Well, 484 is the best, as it is the highest we can go before we don't see any benefits from it (as stated in my last post). You could go a bit lower to say, 460-440, lose a few fps, but gain a decent amount of battery life during gaming, and drastically cut down on heat (if you self-compiled, or if motley released a GPU oc in the vicinity).
[Nexus 7 Original Development] CooLoserTech:
Working good with 1.5 484 GPu, gave the dark knight rises a run. Better than previous version.mNow there is no lag at all.

Just had my first reboot.
[Nexus 7 Original Development] norman1080:
Zram Enabled?

Is there a way to check to see if the zram script inserted into /system/etc/init.d is working? Thanks in advance!
[Nexus 7 Original Development] Prey521:
Would anyone happen to know what the default voltages are throughout the entire CPU frequency up to 1.7ghz?

I forgot to save the default voltage in System Tuner prior to making changes and now I don't know what the defaults were. I tried to uninstall and reinstall SysTuner but that didn't help. Any ideas?

Thanks
[Nexus 7 Original Development] demandarin:
Just go into nexus 7 settings. Then apps. Then all apps. Then find system tuner then clear the data on it. Then reboot. Once you boot back into JB, open up system tuner. Then look at voltages. It will be reset back to default values. Press save defaults before you mess around with it. Therefore you can always press clear/revert back to deafulta if your UV goes bad.
[Nexus 7 Original Development] DJLamontagneIII:
Type free in terminal emulator and you can see the zram swap space
[Nexus 7 Original Development] norman1080:
Thanks! So, I checked it out and I have 0's across the swap. So I assume that zram swap isn't working?

Are there certain permissions I have to give the file? Should there be a *.sh extension on the end of the script file?

Let me know if there is something that I need to do.

Thanks again!
[Nexus 7 Original Development] demandarin:
Well I flashed the latest 1.0.11 builds both versions. Here's my take on them. First I tried the one with gpu oc to 520. Then I raised clock to 1.7ghz. During nenamark2, it froze up immediately and I had to force a reboot. Tried again and it did the same thing. Plus tablet got really hot on backside really quick while it was froze up..lol. then I tried the gpu @484 with 1.7ghz. Well as soon as I started nenamark 2 it froze up. My tablet does not like that speed. I didn't bother messing with voltages as I read something motley posted THST if we raise the highest frequency voltage it really wouldn't do anything. Like its at the Max already. Any higher and kernel log will show errors. I'm like OK, ill try gpu @ 520 again but this time ill raise CPU speed to only 1.5ghz, which my tablet runs great at. I ran nenamark 2. I scored 62.4 this time. The highest since previous 62.1fps on gpu @484. I've concluded, for me, gpu @ 484mhz is more than good enough. The 520 speed is overkill and the performance gain is minimal compared to 484. But I'm sure the increased heat and battery drain will be greater.

So i flashed back the new. Version w/ 484 gpu overclock. Its running fine at reasonable speeds. What I did notice is that I CAN NOW FINALLY RUN AT 1.6GHZ ;) it ran through all my tests fine. Previous builds kept crashing. So motleys increased core voltage helped my tablet to run stable at 1.6ghz. I tried UV it. It crashed but was likely to me doing it by too much. I started off by -75mV across the board on it. Didn't take well to it. Ill have to go back and do baby steps UV on 1.6ghz.

SO as of now, I'm on 1.0.11 w/484 gpu OC. I set my CPU OC speed to 1.5ghz. And UV it -75mV across the board. Very stable at that setting. I think I will try reducing it by another -25mV for a total of -100mV across the board on 1.5ghz. I think mines will handle it. Plus it'll keep the heat down which equates to longer lasting performance before EDP kicks in and throttles the speeds down.

Update: my tablet is taking the UV by -100mV across the board very well w/ CPU set to 1.5ghz Max speed. It ran through quadrant fine. No crashing. What really amazed me was I ran nenamark2 again and I scored 62.4fps again. I only scored that before on 520mhz gpu overclock. Now I scored the exact same thing with all the UV and with the 484mhz. Gpu OC. I'm really liking this new build so far. The integrated powerhal fix working good also.

P.s. I find Motley kernel to be the best performing one out for Nexus 7 right now. Based on real world usage and benchmarks. I've tried other kernels. They are really good. But none seem to give the performance this kernel brings.

MOTLEY, you ever thought of doing a linaro based kernel for prime? Or does it need to be on JB first before you can(since it uses newer kernel)
[Nexus 7 Original Development] DJLamontagneIII:
Place this file http://db.tt/8pfJ6eqBin the init.d folder, set permissions to:

XXX

XOX

XOX

Then reboot :p
[Nexus 7 Original Development] Prey521:
Thanks, that did the trick! "Downgraded" to 1.0.10, undervolted by 125mv and OC'd to 1.5 and running good so far. Thanks again.
[Nexus 7 Original Development] norman1080:
:good: EPIC! Thanks for your help! Very much appreciated! :good:
[Nexus 7 Original Development] spdecoste:
I installed the new version 1.0.11 gpu 524 cpu 1.7

After a few minutes, while the N7 was asleep, it rebooted. Twice, in a short period of tme. So I downgraded to 1.0.10!

I guess it's a bit too much for the device

ps I'm on stock rom
[Nexus 7 Original Development] foxorroxors:
anyone noticed that order and chaos only uses one core - glad its 1.7ghz core its using =)

Nexus 7 @ 1.7/484 CM10

HTC Sensation @1.6/440 RevHD
[Nexus 7 Original Development] danielsf:
_motley I have got my replacement tab, and comparing them side by side, my new one's display looks a lot cooler and it doesn't flicker at all. My old nexus 7 used to flicker horribly. I was hoping if you could give an option to revert

as I don't have screen flickering on the new nexus 7 and I like to have the tab on lowest brightness for reading.

Also, do you think it would be possible to change individual core clock speeds like how the stock kernel had it. Like 1.3ghz single core or 1.2 for dual, tri & quad. So there could be a user adjustable way of setting it up to have single threaded application which only use one core to have a certain max frequency of say. 1.5ghz and for dual, tri and quad core modes used by multi-threaded applications to have a max frequency of 1.3gh or something please? I just think it would be kind of cool to do. As single threaded apps could benefit, whilst being more heat friendly when using more than one core. :)
[Nexus 7 Original Development] demandarin:
speeds couldn't be changed on stock kernel. what you described is how the kernel behaves based on demand. if app or games or browser needs more power/cores,it will adjust so. this latest kernel does the same thing. just make sure your governor is set on interactive. I do get what you're saying. what would be better is nexus 7 allowed you to choose power modes like on the prime or infinity pad. able to choose power modes/CPU speeds on the fly through quick settings.
[Nexus 7 Original Development] hecksagon:
If you were getting 15fps at 484mhz, why would you expect a 10fps improvement at 520mhz? This is only a 7% increase in clock rate and therefore fillrate. This compares well with your 16fps result.
[Nexus 7 Original Development] Highland3r:
Not sure if this has been asked before, but is anyone seeing warming of the bottom left portion of the tablet (when held with power/volume buttons at top right)?

Seeing this both with the tablet "idle" and the heat increases when playing games.

This has been seen with the 484 GPU overclocks running the 1.0.11 stable release. CPU set to interactive with a 0.25mv undervolt. Issue seemed unchanged by altering the max CPU speed.

Currently running the 1.0.11 release with no GPU overclock at 0.75mv undervolt - too early to tell whether this has helped the warming at all!

Not complaining etc, just trying to establish what's causing it!

Cheers!
[Nexus 7 Original Development] foxorroxors:
more mhz = more work = more heat.

Nexus 7 @ 1.7/484 CM10

HTC Sensation @1.6/440 RevHD
[Nexus 7 Original Development] Highland3r:
Yup I know ;)

I figured kernel running stock CPU (1.3ghz) and stock GPU speed (assuming voltages are the same) would result in the same amount of heat as stock (give or take).

0.75 undervolt across the board seems to have helped somewhat - again probably been stated somewhere but does this kernel overvolt the CPU/GPU from stock?
[Nexus 7 Original Development] foxorroxors:
i dont think it does, maybe on the gpu side, im sure motley will be around shortly to clear things up =)

Nexus 7 @ 1.7/484 CM10

HTC Sensation @1.6/440 RevHD
[Nexus 7 Original Development] demandarin:
Only time my device really heated up was when I tried to the cpu @ 1.7ghz on performance mode w/ gpu Oc @ 520mhz. Tablet froze up got hot very quick on area described. Lol

Now with my current setup, 1.0.11. 1.5ghz overclock w/gpu Oc to 484mhz. With -100mV undervolt across the board, heat is not an issue for me ;)
[Nexus 7 Original Development] CharliesTheMan:
Mine gets a little warm on stock voltages, the lower left corner when holding the tablet is where they all get warm. But even when it's warm me temps are cooler than my smart phone runs most of the time when I'm using it with the screen on, with the stock kernel and stock voltages and kernel settings on phone.

When it feels real warm back there my temps are still below 90 degrees Fahrenheit.

What kinda temps are you getting?
[Nexus 7 Original Development] Highland3r:
CPU temp was showing in the 60's. Seems a fair bit better with the UV settings now in place.

From the teardown, the tegra chip is bottom left so not gonna worry. If it continues to annoy back to stock kernel - not that it's an actual problem by all accounts anywho!

Cheers for the feedback from everyone <3
[Nexus 7 Original Development] hanthesolo:
Yeah, I may have been overly optimistic, since I just guessed to what I thought would be an accurate no. :o. Still, if what you say is true, and only an extra 1 fps would be feasible, I still think that losing extra battery life and generating a bit more heat isn't worth it for 1 fps, and I still believe that you would get at least 3-5 more fps at that clock, unless, as motley said, the transfer rate (for lack of knowing exactly what part motley was talking about) is maxing out, I digress, though.