yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] t_007_v2:
not even close to normal... if it was me i would flash the stock N7 rom and start all over again. you just have to many variables to narrow down the cause of the lag.

install the stock rom and kernel 1.3/412 and run a test with quadrant should test around 3800. your 3d and io scores are terrible right now something is not set right why your laggin. then flash the 1800/650 kernel and test again on stock rom you should be hitting 6000. io tweaks and forcing 2d on the gpu should make your score top 7000 in quadrant.

best of luck on whatever you decide.
[Nexus 7 Original Development] Bunie89:
EDIT (Yey)

Restored to stock, installed everything properly (again) and got a score of 6312. Gonna mess with it now. wonder what was wrong before? i even did things like format /system. what did restoring to stock fix? XD
[Nexus 7 Original Development] thesisko:
Just wanted to add that I experienced exactly the same issue. Stock kernel and _motley are silky smooth but Clemsyn's shows significant stutter when scrolling between home screens with lots of widgets on them and when opening and closing the app drawer.
[Nexus 7 Original Development] Lord_Xovon:
I had a weird problem with this kernel

Clemsyn1.8GPU650

in white backrounds or fair skin people during movies i was getting red sparkly pixels dancing around i thought something might be wrong with my n7

but i switched back to Trinity Kernel just to see if it was clemsyn kernel and sure enough i am not having the problem no more.

has anyone else noticed this problem?
[Nexus 7 Original Development] t_007_v2:
if you experience what is described above use the 1.8/650 pinkfix kernel it works.
[Nexus 7 Original Development] Bunie89:
Just wanted to let everyone know i figured out my issue! it was overheating. it overheats quick from plain use. not very useful lol. But,

i did install it ontop of CM10 and im very happy with my results
[Nexus 7 Original Development] eturk01:
TWC TV app crashes after a few minutes playing a channel.

error message: "we are unable to present channel at this time"

I've read that this is caused by hardware acceleration support in custom kernels and to talk to the developer.

Works great on my GNex with Franko kernel.
[Nexus 7 Original Development] Sultanxda:
I have noticed that this behavior occurs with a GPU overclock. It does not happen when tablet mode is enabled (175 dpi).
[Nexus 7 Original Development] tubstermania:
I was only getting 5000 on my quadrants, then I bought TkT and did some stuff and worked it up to this. Still wanna get up a bit higher, what voltage is recommended for 1800mhz? I have it default (1350).
[Nexus 7 Original Development] tommykwan222:
Hey, can I control the working frequency of this kernel when I am using my Nexus 7?

As I found that it is very hot when the GPU is in 520
[Nexus 7 Original Development] demandarin:
Use an app like system tuner or trinity kernel toolbox to mess with frequencies. You could UV it bring the temps down.
[Nexus 7 Original Development] nory82688:
Running @ 2ghz on interactive with updated kernel, so far so good. I had to up the voltage on 2ghz frequency to make it more stable, but haven't had a reboot so far. I'm using system tuner to adjust everything .
[Nexus 7 Original Development] Ronaldo Forenucci:
Is there an undervolt version with either stock 416 or medium 484 GPU? Looking for better battery life with same or slightly better performance than stock. I've been told this is not possible. Read Motley, Trinity, and Clemsyn threads, but am a little confused. Looking at CleanROM, and BuglessBeast...where is AOSP? Just trying to build a battery beast with no loss in performance from stock. I admit information overload :D

RF
[Nexus 7 Original Development] tommykwan222:
thanks.for your suggestion. But i cannot find the setting about the gpu 8nside the system tuner
[Nexus 7 Original Development] simms22:
there is a "pure aosp" rom in nexus 7 development. its nice and clean, and runs great. ive been using it since the day my n7 arrived :) http://xdaforums.com/showthread.php?t=1790320

---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------

you cant control gpu speeds, just cpu speeds
[Nexus 7 Original Development] flauchhaus:
I still have graphical artifacts using the 650 Pinkfix :(

Anything I can try?

Also did anyone else notice the scolling microshutter that danielsf documented? After watching the video I cant unsee it.

http://xdaforums.com/showpost.php?p=31002248&postcount=1157
[Nexus 7 Original Development] rockethot:
Is anyone else having issues with having the over clock stick with the undervolted 1.5 ghz kernel? I used SetCpu to set the frequencies at 51mhz-1500mhz but it always goes back to 100mhz-1300mhz.
[Nexus 7 Original Development] giveen:
Setcpu doesn't like our kernels. Use Trinity kernel toolkit
[Nexus 7 Original Development] brizey:
Yep. I was getting reboots with setcpu.
[Nexus 7 Original Development] Bosio91:
I took your suggestion about the Pure AOSP ROM once, and since then I've come back to it after trying any other ROM. It's simply...perfect!
[Nexus 7 Original Development] brando56894:
Ah that may be my problem! I was getting freezes with the 1.8 kernel so I went back to motley's 1.6 and was still getting them, so I switched from AOSP to a stock based ROM and was still getting them, it was confusing me. I'll switch back to CPU master to see if that fixes it.
[Nexus 7 Original Development] CharliesTheMan:
Clear the app data from set cpu and un install it, but then wipe cache and dalvic and flash kernel. Make sure you install the control apps from the play store and not a restored apk.
[Nexus 7 Original Development] Stappern:
Hi everyone ive got very low score in i/o,its normale?

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Original Development] danielsf:
Yeah, it's perfectly normal. If you want to have better I/O you can always use these commands in a terminal emulator:

echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled

mount -o remount,noauto_da_alloc /data /data

or you can make a script which is described more detail here: http://xdaforums.com/showthread.php?t=1855100

If you do these, you will get better i/o, but at the risk of data integrity. But yeah, it is perfectly normal. I hope that helps you :)
[Nexus 7 Original Development] brizey:
Took me a while to figure it out. I think that the profiles may be broken. I was getting sleep death, etc. I flashed a new rom and decided to start clean and just use the built in overclocking...and no more SOD. No issues since I got rid of setcpu. Too bad, because it has the best interface and I like profiles.
[Nexus 7 Original Development] Stappern:
OK thanks waaaaaaaay better

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Original Development] simms22:
go to the devices main settings, developer options, enable force gpu rendering. itll bring up your 2d score by 4-5 times.
[Nexus 7 Original Development] giveen:
Could someone link me to a copy of the 2ghz kernel?
[Nexus 7 Original Development] willis936:
I haven't been able to run the 1.5 or 1.8 since playing with scripts. Even when fsync is enabled and zram is disabled I still get a crash shortly after boot. Stock ROM but couldn't get it to work on a kang either.
[Nexus 7 Original Development] brando56894:
Once I got rid of setcpu everything has been fine.
[Nexus 7 Original Development] jlim0512:
I'm using set cpu and im confused on what governors are what I need to set it on. And what are I/O's and which one do I use?

I'm not even getting close to those number. I'm getting around 4800-5200.

Thank you.
[Nexus 7 Original Development] CharliesTheMan:
I recommend the SIO IO scheduler. It controls reading and writing from the flash storage.

Governors are important. The governors have different configurations on how the CPU is managed and controlled. Like on demand, when you do something on the tablet, the CPU frequency goes to the top instantly and then starts scaling itself back down really fast according to what kind of load its got on it.

Another governor will behave the opposite, when called up, the processor frequency will gradually increase until it reaches the desired CPU power for whatever the task it.

Performance governor just sets the CPU on the max frequency setting until you change governors.

I'm really tired but hopefully that made a lil sense. I'll find a good thread and link it here.

My personal settings are SIO I/o scheduler with on demand or interactive governor most of the time.
[Nexus 7 Original Development] boynamedstacy:
Man clemsyn. You freaking killed it bro. I never thought this thing could be this fast. Like stupid fast. I'm sooooo stoked I can actually run this thing. Thanks a million brother!

Sent from my Glazed-over Nexus 7
[Nexus 7 Original Development] jarjar124:
hows the battery life so far? someone should underclock this baby and see how it runs. i would but i dont have my n7 with me at the moment :(
[Nexus 7 Original Development] Rafase282:
Feast on this!

---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------

Also I have my N7 on a leather case. Would that have a huge impact on temperature? I have never bothered to either think about it or monitor the temps.
[Nexus 7 Original Development] evonc:
Haha i meant as it system tuner showed a spike to 82C so actual would have been 72 before it rebooted. I'll try popping the back off and putting it on the ac vent tomorrow when i get some time to bench it.
[Nexus 7 Original Development] boynamedstacy:
your not serious are you? Lol. Battery life after only an hour at most?

Nice bench but I nearly doubled that FPS. What settings?

Sent from my Glazed-over Nexus 7
[Nexus 7 Original Development] jarjar124:
yea how much % has gone down within an hour..
[Nexus 7 Original Development] Rafase282:
Interactive with SIO, stock voltages 1.7 max, 0.1 min

Then I have the IO script, zram, and fsync off
[Nexus 7 Original Development] leftfork:
What's with the pink cast on some gapps? Anyone else experiencing this?
[Nexus 7 Original Development] Rafase282:
On stock and at max, I have seen it go down a few % while running benchmarks and so.

If you are not going to play games then put it back to 1.1 max and even less on screen off and i guess you wont have to worry about battery life, I can last days if i'm not playing games with the mortley's kernel.

Also I spent almost a whole day with the device streaming music, at night i just turned it off and it was about 49% or a bit less. I stopped the test right there.

Without heavy use, I could go easily into the 3 days mark and maybe more depending on the clock speeds.

Unlike my G2X, I really dont have to worry about battery life unless im playing dead trigger or a similar taxing game.
[Nexus 7 Original Development] rohan32:
Holy mother of god this thing is fast.

Heats up in like 5 minutes though. Definitely not a daily but insanely cool. Very nice work, OP. Really, really, cool.
[Nexus 7 Original Development] leelaa:
Should be getting a better score than that considering the power this kernel is throwing out.
[Nexus 7 Original Development] Rafase282:
What settings did you use?
[Nexus 7 Original Development] jarjar124:
thanks. on trinity underclocked at 1.1ghz my n7 battery doesnt even go down when i use it. used it for browsing for about 30min? still 100% :) cant wait to try this beast
[Nexus 7 Original Development] demandarin:
I spiked as high as 114fps during quadrant. I had to increase voltage on 1.7ghz freq. though. my quadrant scores were horrible..lol. waiting for tablet to cool down some before running it again.

I did kill nenamark 2 though with 69FPS

device does heat up very fast during benchmarks. for regular use, if if someone device rebooted during benches, it can handle the 1.7ghz with normal use.

time to attempt quadrant again. my fps stayed above 106. as I ran more tests, they kept spiking then dipping really low. I guess heat was getting to it. but I never crossed the threshhold above 68c to make it downgrade performance.
[Nexus 7 Original Development] boynamedstacy:
Damn, quadrant just peaked at 117 FPS!! Only a 6900 bench, though. What am I saying. Only? That's still pretty damn good! Loving this ish!

Settings:

1700 min/max

Deadline I/O

Performance governor

SD boost 2048

Edit: No reboots, freezes or FC,s since flash. Temp running at 138°F after a few bench tests, 115°F with normal use. Loving the lower brightness too BTW.

Sent from my Glazed-over Nexus 7
[Nexus 7 Original Development] demandarin:
this kernel underclocked to 1.1 or 1.2ghz with 600mhz gpu could be interesting. should get decent battery life like that.
[Nexus 7 Original Development] clemsyn:
Thanks for this, Ill try to decrease a few timings for you to fix this but I suggest you revert back to your last kernel till I fix this.
[Nexus 7 Original Development] Rafase282:
I'm going to try these settings and watch for the FPS to see the max it gets.

Also I'm taking the leather case out to see if I can feel some heat.
[Nexus 7 Original Development] boynamedstacy:
Definitely take it out of a case. That will increase heat and could cause a reboot while benching. Tegra 3 also has a temp safety that will throttle back speeds once it gets to high. You'll definitely feel her get warm though!

Sent from my Glazed-over Nexus 7

---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------

Yo Clem, what's the VR scheduler? That's a new one for me.

Sent from my Glazed-over Nexus 7
[Nexus 7 Original Development] meatlocker:
Clemsyn, nice to see you back at work, bro. I've absolutely LOVED your prior work. Can't wait to try this.
[Nexus 7 Original Development] clark707:
6828 1.8ghz minimal and 1.8ghz max performance gov

I will be switching to another kernel though because the pink made me think my tablet was done for lol.

edit: did some scanning around this thread realized i didnt break jack.

Also, i would like to be a tester for the 2ghz Kernel, i've been a flash junky since i got my first android device.. ( tbolt...)

I want to push my N7 like it has never been pushed before.
[Nexus 7 Original Development] boynamedstacy:
This is for those of you who used the 2.0 kernel in the beginning and couldn't get into recovery.... How the hell did you get in finally? I know hooking up to the PC with the stock cable was recommended but that doesn't even work for me. I've literally tried everything at this point and I'm looking for some help. Anyone have any crafty suggestions? Please and thank you :)

Sent from my KRAKD-out Nexus 7
[Nexus 7 Original Development] masterg0g0:
If nothing works you can flash recovery using the root tool and get into it with the cable attached to the device
[Nexus 7 Original Development] clark707:
dang theres a 2ghz kernel?? thats insane. I would try it but the 1.8ghz was crazy enough for now. Besides looks like its very unstable.
[Nexus 7 Original Development] CharliesTheMan:
I just booted to my rom, copied the sdcard directory to my computer, then used the toolkit to flash stock, root and install recovery, then flashed my rom ans restored my sdcard contents back to the device. Three days thinking about it and 15 minutes to backup, reflash, and start over.
[Nexus 7 Original Development] boynamedstacy:
Thanks guys. I never really thought about using the root tool again...That's why I asked you :D

Sent from my SGH-I535
[Nexus 7 Original Development] clark707:
What can I do to get my hands on a 2ghz Kernel. I would like to test it.
[Nexus 7 Original Development] 1loudsvt:
Where is this 2ghz kernel I would love to try it. The 1.8 is great and running very smooth on my nexus. Thanks.
[Nexus 7 Original Development] Mimsy:
Awesome kernel! I'm using 1.5 undervolt final version. I've even been able to reduce all voltages by -25 mV and everything seems stable so far. The only problem I have is that kernel doesn't want to stay at 1.5 GHz, I always need to set it manually (using system tuner).

EDIT: I've UVed all steps by 100mV and everything is stable (playing games, web browsing and benchmarking) so I thought something was wrong with system tuner and I decided to UV to 900 mV (just to test if it's working properly) and it froze, meaning system tuner works as intended. Do I have a golden chip or what? lol
[Nexus 7 Original Development] simms22:
pm clemsyn. hes only sharing the 2ghz kernel by request, by pm.
[Nexus 7 Original Development] cobhc:
@Clemsyn have you tried pushing the GPU more and leaving the CPU at or near stock? I personally would love a kernel with a high GPU clock and a small or no GPU over clock as I feel that's the place where we're lacking performance. And gaming wise it should make the most difference.
[Nexus 7 Original Development] Encerspay:
Dat benchmark O_O

But wouldn't this murder the lifespan of the processor?

And battery life??

And, could I run this and paranoid android? Because that'd be a pretty impressive $200 tablet!
[Nexus 7 Original Development] clemsyn:
How about a 700 gpu? I'll make one soon.

BTW, I apologize for the lack of updates. Been very busy with life at the moment and busy helping TeamDRH with Gtablet in Jelly Bean. It is easier to work on a device if you actually have it to fix issues. Will update though. The 2 ghz has been a very tough nut to crack but 700 gpu should be OK. Would need a few beta testers for the 700 mhz GPU please to know if it is working. Please PM me for the 700 GPU testing. Thanks.

Due to high demand of the 2gh trial kernel, I am posting it here

https://rapidshare.com/files/2786469416/KernelSimmsver2.zip

Please be advised that these kernel is a work in progress and that voltages is very high. Please be very familiar in backing up the device.

Was looking at the code in increasing the GPU closely and it doesn't seem simple as I thought. It seems like clocks of 600 atabove 600 (like 625 or 650) seems to be staying at 600. Looks like the base controller for the GPU needs to be increased too. Will update soon.
[Nexus 7 Original Development] luke05dee:
May I ask if you would consider a none pixel clock increase 600mhz gpu builds as I seem to get input lag and micro stutters with any kernel with a pixel clock increase. The higher the pix clock the worse it seems to get. The only kernel that doesn't seem to have a problem is faux123 which has no pixel clock increase. As the pixel clock increase doesn't add to performance, it just makes low intensity GPU benchmarks like nenamark 2 or quadrant get higher scores, we could just use basemark es2 to show the performance difference as it never gets close to stock max of 60fps. Please would you consider this? :)
[Nexus 7 Original Development] leonbarroso:
what is the GPU clock in the 2GHz testing kernel ?
[Nexus 7 Original Development] clemsyn:
600
[Nexus 7 Original Development] clemsyn:
Sure, check your PM
[Nexus 7 Original Development] Sultanxda:
700MHz GPU kernel boots and ran well for the first part of Quadrant (20+ more fps than with the 650MHz GPU) but the screen froze at the 3D test with the planets.

EDIT: Ran Quadrant again with CPU only at 1.7GHz and it completed successfully. After that I tried 2 more times at 1.8GHz to run Quadrant but both times ended with the exact same result: at the DNA double helix graphics test white lines appeared through it and the screen froze at an image of the 3D planets test that it was running before it. Perhaps there are CPU overclock limitations with a higher GPU overclock (this behavior is not present at 650MHz GPU) or my tablet just can't handle it.

EDIT2: Nenamark 2 crashes my tablet as well and I'm also getting random shell restarts.

EDIT3: I have pink artifacts.
[Nexus 7 Original Development] flow78:
The link for 2ghz trial kernel is dead. Someone can post an other link please?
[Nexus 7 Original Development] cobhc:
Still works for me...
[Nexus 7 Original Development] leonbarroso:
2GHz freezes Quadrant (AOKP ROM)

---------- Post added at 04:42 PM ---------- Previous post was at 04:38 PM ----------

Having FC and freezes in Antutu benchmark too
[Nexus 7 Original Development] Sultanxda:
Clemsyn, on your 2GHz kernel I increased the voltage of 1.9GHz from 1450mV to 1550mV and 2GHz from 1550mV to 1700mV and I can finally run benchmarks without it crashing.
[Nexus 7 Original Development] clemsyn:
Would be interested with yours scores :) BTW, I really think the increase of GPU to 700mhz needs a bump of voltage for stability.

Also, you might want to be careful with those voltages. They are pretty high ;)
[Nexus 7 Original Development] pinoyto:
Clemsyn

I am pretty stable with your 700 gpu. Scored over 72 fps in nenamark 2. Easily grabbed the top spot from slacker.

I attached a png file with my result. Also there are a bunch of errors on dmesg. Its about some clock limits on host1x.
[Nexus 7 Original Development] simms22:
I did the opposite to get stable, I dropped voltages at 1.9 and 2ghz. then I could run it all day. BTW, be very careful with the 1700mV, THAT can destroy your device. I won't even touch that high of a voltage, unless I want to cook something inside my device :p
[Nexus 7 Original Development] Sultanxda:
At 1700mV it only lasted a little longer but still crashed in the long run. The highest I went to was 1775mV for 2GHz (wonder how many years I took off its life... :p) where it completed 40% of Antutu until the screen went black. Tried going lower for 1.9GHz and 2GHz but it always crashed just by opening Quadrant/Antutu.
[Nexus 7 Original Development] simms22:
try dropping the top end voltages by 50mV or so.. 1900 at 1425-1475mV and 2000 at 1450-1500mV work nice for me.
[Nexus 7 Original Development] nemesis93:
Where is the link to the 2ghz kernel please? :)

EDIT: Nvm I found it :D
[Nexus 7 Original Development] Sultanxda:
Just tried that, froze when opening Temple Run. Doesn't happen when I'm at 1700mV+... guess my CPU isn't as good as yours
[Nexus 7 Original Development] simms22:
na, doesnt mean that. it means that your cpu doesnt like what my cpu likes :p
[Nexus 7 Original Development] Sultanxda:
It runs 1.9GHz fine at 1475mV though... so close to 2GHz!
[Nexus 7 Original Development] simms22:
nice number
[Nexus 7 Original Development] Sultanxda:
I guess it really doesn't want to go to 2GHz :p
[Nexus 7 Original Development] Sultanxda:
BTW Clemsyn, I'm getting pink artifacts with your 2GHz kernel.
[Nexus 7 Original Development] simms22:
so close

oh no, set it down and run. its going to blow..!
[Nexus 7 Original Development] Encerspay:
Wouldn't this kill the processor?
[Nexus 7 Original Development] Stephen.k.spear:
Whenever all 4 cores are being used the tegra will always step down one step. It will hit 2.0 when only 1 or 2 cores are used.
[Nexus 7 Original Development] Metallice:
Not entirely true. Only if EDP is enabled and faux's fix isn't applied. I believe motley has edp enabled based on temperature.
[Nexus 7 Original Development] clemsyn:
Too all the testers of the 700mhz GPU, thanks. It seems like there are more devices not hitting the 700gpu, but this could be related to the dmesg issue that simms sent me. I am currently looking into it and when I get that fixed, I'll let you know.
[Nexus 7 Original Development] cobhc:
Running stable for me, but I have the pink artifacting. Real shame as it runs so nicely.
[Nexus 7 Original Development] Sultanxda:
When I took that screenshot it just happened to be using all 4 cores; before that it was running 1 core at 1.9GHz. Also, when i set my max frequency to 1.9GHz it goes to 1.9GHz regardless of how many cores are on. To overclock I'm using No-frills CPU Control with the "Prevent changes from other apps" setting enabled.
[Nexus 7 Original Development] clemsyn:
K, I think I fixed the dmesg issue. 1.8ghz kernel with 700 gpu to be released after beta testers testing ;)
[Nexus 7 Original Development] Sultanxda:
With the 700MHz pink fix kernel my GPU score in quadrant is sliced in half (2,000 for 3D) but with the regular 700MHz kernel my GPU score is over 4,000. With the current 650MHz stable pink fix release I get ~3,600 for 3D. Both of the version 3 700MHz kernels crash my device when running NenaMark2.