[Nexus 7 Original Development] _motley:
Thanks for the feedback. Not sure what the problem is, but if you could provide a log (see OP for an easy way to grab it), which ROM you are using, and which tool you are using to OC, and if you messed with voltages, that would be very helpful. You could try tweaking voltage and see if it helps with stability, but I am not yet convinced that is the issue here if you were running forcing stock CPU speeds and still having issues. If voltage is too low, the screen will just freeze frame for a few seconds before it reboots. I have run those same benchmarks many times and never had a crash, but then again we don't yet understand the diversity out there with these units. Some may tolerate 1.6GHz while others won't. Would really like to see a log if you have the time.

Great to hear. No-Frills is fine, or you can try System Tuner. With System Tuner, you can do almost anything (i/o scheduler, OC/UV etc.) If you OC a device, it will get hotter to some extent. Higher frequency, higher voltages = more heat...no way around that. It's the CPU governor that scales the frequency, not the OC tool. All the tool does is set the min/max frequency and the governor takes it from there.If you use the performance governor for a benchmark, always remember to turn it back to "interactive" after you are done as it will generate more heat. You can also try the other governors to see how they work for you to keep the heat down. I may add other governors here very soon, but trying to decide what will best. Most seem to want to try SmartAss2, so I will likely add that soon. Other suggestions that will work nicely for a 3.1 kernel and a quad core device are welcome and I will get them added in. Some think they have to have a CPU that clocks super high, but IMO this is silly as long as you have nice smooth performance. 1.4 or 1.5GHz is plenty for a "butter-like" experience on this device.

Also, just to further elaborate from the OP, this kernel has what I call "Dyanamic EDP". I cribbed this idea from the Asus Prime kernel. If the cpu reports 60C via EDP notify, it will allow EDP to kick in until the temp drops back below 60C again. The Prime temp threshold is higher, but I always choose to go the safe route first. I may bump this up if possible (depends on EDP temp threshold notify capabilities). You can witness Dyanamic EDP by looking at dmesg output during an Antutu benchmark test if you are cooling the unit down. If it is too much of a nanny, we can try bumping the temp up a bit. During day to day usage, it typically won't hit this temp range. However, if it does, it keeps the heat/stress on your tablet down while still allowing more aggressive overclocking.

Your issue sounds like a root/su/Superuser.apk issue. You don't seem to have the proper permission to read/write to sysfs. I would recommend doing a full wipe and installing the latest recovery and a known working ROM (like Modoco r3 or a stock rom). I have issues like this no and then, and it is typically fixed by changed the version of su/Superuser.apk I am using. Sometimes newer isn't always better.

-------------

Keep the feeback and recommendations coming, they are much appreciated!