yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Rafase282:
Even -100 across teh board gives me a reboot if I use the cpu for something like getting into sdcard settings on the app.
[Nexus 7 Original Development] thracemerin:
Not every CPU and GPU is exactly the same, slight manufacturing differences can mean that one CPU can take heavy OC and UV while another can't.
[Nexus 7 Original Development] katestar:
_motley I have noticed in benchmarks that the gpu isn't limited to 60fps. I thought it was standard practice to do this as it saves a large amount of power at no expense of performance as our displays can't display more than 60fps, the only thing that suffers is benchmarks? Would you be able to maybe to include a frame limiter option please as from things I have read in passing it can save a lot of power, or at least consider it please? Thank you so much :)
[Nexus 7 Original Development] lightninbug:
Definitely! Couldnt of asked in a better way myself.. +1
[Nexus 7 Original Development] brizey:
Why do the voltage control apps only go down 520 Mhz?
[Nexus 7 Original Development] rockaholic112:
I took notice. Notice one post above, how I stole your idea (except the set on boot part, I figured that out ;)

Sent from my portable telecommunication box
[Nexus 7 Original Development] Rafase282:
Would it be possible to implement smartassv2?
[Nexus 7 Original Development] thracemerin:
SmartassV2 is optimized for 2 cores, N7 has 4+1 cores.
[Nexus 7 Original Development] Rafase282:
oh I didnt know that. =b
[Nexus 7 Original Development] thracemerin:
Not that it wouldn't work, its just not the optimal governor for this particular chipset.
[Nexus 7 Original Development] clemsyn:
This issue might be due to the dynamic cpu frequency changing implemented by Nvidia in the kernel when the screen is off to save power. One way to make it stick is to use System Tuner and go to Boot Settings...the click on Screen-off Behavior then change the governor to Interactive (or to whatever you have it on). You don't have to change the Max frequency.

If I remember correctly (yeh, I'm an old kernel dev from tegra 2), nvidia implemented conservative cpu governor when the screen is off and reverts back to default when screen is on but unfortunately doesn't save the max frequency that we set so keeping the governor to interactive (same as your default) will keep the max frequency you set.

Just my 2 cents. I could be wrong since I don't have this device and I'm too busy keeping up with my 4 boys to even think about kernel developing :)
[Nexus 7 Original Development] _motley:
v1.0.7 released

Hi everyone,

v1.0.7 is now released. See the OP for details. Also see post #2 below for info on voltage control. We still have one remaining issue, and this appears to be an Android OS issue. Reverts back to 1.3GHz on screen off. Still going to look into this when I have time.
[Nexus 7 Original Development] _motley:
Hi clemsyn, thanks for stopping by. I remember this as well with tegra 2 and pulled my hair out over it once, LOL. We have a nice kernel config for this now CONFIG_TEGRA_CONVSERVATIVE_GOV_ON_EARLYSUPSEND, so I don't think this is the case. I have this turned off like Asus/Google had it, so I don't think this is coming into play. We think we have found the source and the code that calls the source in Android, but I still haven't had a chance to finish researching with aaronpoweruser who building ROMs with some tweaks in this area with hopes that we can fix it. See here for more info: http://xdaforums.com/showpost.php?p=29218456&postcount=35

I don't know how to do this, but I can look into it. If anyone has any links or info on this, please let me know. The GPU (at least 3D) scales up and down, so we are not pegged all the time.

Someone else was asking...sorry I forgot to include that post. I didn't have to raise any of the core voltages used for the axis of the CORE_DVFS voltage table to achieve the GPU overclock frequencies.

Hopefully post #2 and my last update will clear some of this mystery up for everyone.

http://xdaforums.com/showpost.php?p=28834197&postcount=2

520MHz is cpu_process_id "2" and that is the lowest frequency we can tweak for the high powered "g" cores.
[Nexus 7 Original Development] k1ska:
Is anyone else having an issue with the download links? I can't download either one D:
[Nexus 7 Original Development] demandarin:
I flashed latest 1.07. After prolonged use, ill let you know how it goes. Everything seems OK so far. Thanks!
[Nexus 7 Original Development] friedsonjm:
Me too, will put it through its paces today... one question - minimum speed defaults to 100, but can be set as low as 51. Is there some reason for not having it default to the lowest speed?

regards, jf
[Nexus 7 Original Development] CooLoserTech:
What are those tweaks you guys are talking about

How do I install them
[Nexus 7 Original Development] pinoyto:
Thanks clemsyn, this fixed the issue of reverting back to 1.3 after the screen turned off. I simply changed the Screen Off governor in Simple Tuner to interactive (from no change) and whoala...it keeps the speed to 1.6 ghz. Thanks to _motley and clemsyn!
[Nexus 7 Original Development] friedsonjm:
Minimum also reverts from 51 back to 100 on screen off....
[Nexus 7 Original Development] CooLoserTech:
The mount cw3 gives a 500 pt lower bench but better performance. OK I'll keep it
[Nexus 7 Original Development] pinoyto:
Try clemsyn's fix. This fixed the reverting issue.
[Nexus 7 Original Development] DJLamontagneIII:
In setcpu hit menu,device selection and hit auto detection
[Nexus 7 Original Development] parcsalooc:
It's odd it doesn't show it as that. Only gives Continue Rcommended and Custom advanced. I hit Recommended and it shows max of only 1300. I hit Custom and it gives 2 options of Nvidia Tegra 2 T20/AP20H which results in max of 1000 and Custom Freq reading from sd card which results in max 0 and min 0 . I know the option you are talking about as I use them on all my other devices.
[Nexus 7 Original Development] DJLamontagneIII:
That is odd.. I'm using the same ROM and can oc
[Nexus 7 Original Development] bsw11:
Help..

Well I messed up and installed your Kernel without doing a backup!

And of course it gets stuck on the boot screen.

And of course I don't have another kernel on the device.

Can you please instruct me how to get back to stock - can I use ODIN?

I am on W7, I had it rooted and unlocked.

Thanks!

Edit: I wiped everything and loaded a custom ROM and it seems to be booting up OK again. WHEW!
[Nexus 7 Original Development] h3r3tic:
Same issue but I had a back up and I can't get my PC to recognize it. Bootloader freezes when i connect it. Recovery won't boot. Wug tools won't work. I cant do anything. And times a factor. I'm acrid if this battery dies I'm screwed.

Having trouble with six axis? check this out.

http://xdaforums.com/showthread.php?t=1779386

[APP] [PROFILES] Sixaxis Controller Profiles for Nexus 7
[Nexus 7 Original Development] DJLamontagneIII:
Mabe some help here guys

http://xdaforums.com/showthread.php?p=28190318
[Nexus 7 Original Development] Kidromulous:
Guys who are stuck what you likely can't get is adb. What you can do is fastboot commands. I downloaded a working kernel extracted the zip and placed the boot image in the folder with fastboot likely platform-tools. Then use the command "fastboot boot boot.img" . Then "fastboot reboot". You should be good to go.
[Nexus 7 Original Development] parcsalooc:
Still wont solve the issue i am having w/ oc
[Nexus 7 Original Development] Kidromulous:
Can't help you with that cause I can't get the kernel to boot. Might mess around with pushing it to my device the old fashioned way later.
[Nexus 7 Original Development] h3r3tic:
OK so yea a no go on the kernel I'm back manage to boot stock image got back into recovery and restored my system.
[Nexus 7 Original Development] bsw11:
So I installed Paul Obrien's ROM and then did a backup and installed this Kernel again and - IT WORKS PURRRFECTLY!!! Overclock and all.

It seems the combo did the trick.
[Nexus 7 Original Development] hanthesolo:
I can confirm that your kernel will *not* boot with the stock rom, although I did not check any logs, as I just got it, and am in the process of setting it up. I will try and stick with stock, as I see no need for a custom rom on this device (plus, I like the stock UI). If you need me to fastboot any images, I will be happy to help, although i'm sure it's a simple issue.
[Nexus 7 Original Development] bigxie:
Not sure if this has been mentioned yet, but JB has built in screen on/off profiles, so it will default back to 1.3GHz when you turn your screen off and on again.

This can be changed in the ramdisk.

The workaround is to set a screen on profile using SetCPU.
[Nexus 7 Original Development] _motley:
Thanks guys and all the rest of you for helping out with the alpha testing. I think I may have found the contamination from the Paul Obrien ramdisk. Just did a diff and found a line that I didn't realize I had. Looks like something that waits to do the init.d stuff until the rom signals that the filing system is ready to go, or something like that. Yeah....this looks like it could stop the stock rom from booting!

on property:mcr.filesystem.ready=1

I will upload a new zip here in a second that the is based on the stock ramdisk without this trigger. I happen to be on his ROM still, so that is why it works for me. Anybody able to test?

The new version will also have UV and the V(R) i/o scheduler. Need to get an Anykernel package together here soon!
[Nexus 7 Original Development] bigxie:
I'm on Paul's ROM too, but I can tell you from looking at the logcat when I tried on the stock ROM that it was waiting for init.d

I think removing the line from the RD will do the trick.
[Nexus 7 Original Development] _motley:
Awesome, I hope so too! OP has been updated with v1.0.3! New additons are UV and the V(R) i/o scheduler. My fingers are crossed!
[Nexus 7 Original Development] Clienterror:
You are awesome man!
[Nexus 7 Original Development] h3r3tic:
I'm gonna try again tomorrow. I got scared earlier but it was actually my PC. Drivers are all jacked up and wouldn't recognize bootloader Idk what to do to fix it. I tried my gfs laptop and it loaded up no problem installing naked driver. Its installed on my PC too but don't load up I'm stumped. If anyone knows a quick way to clean out all USB drivers so I can just reinstall my defaults n start over let me know.
[Nexus 7 Original Development] antiochasylum:
Wish I would have checked this before work. I would have flashed it, and it is hadn't booted given you the needed info. ::sad panda::

I'll try when I get home.
[Nexus 7 Original Development] dude2k5:
getting bootloops on benchmark tests. even on stock settings. might revert back.

edit: then again, this thing is flying now. wow. lol. antutu and cfbench give reboots. quadrant, smartbench, and velamo seem fine. not sure why those are, but this seems stable, not sure how battery will be affected but i'll test it out for a few days.

edit: had too many reboots, had to revert back. but for some reason it didnt restore the wifi right, maybe because i was using TWRP or something. If you flash CWM and restore a backup you had that way, you can get wifi working again, then use TWRP again. That is, if you get stuck.
[Nexus 7 Original Development] friedsonjm:
I'm assuming he meant 'system tuner' not 'simple tuner' - I'm trying to find where that setting is!

I'm also wondering if there is a setting there somewhere that will enable my N7 to keep wifi on when 'sleeping' the stock setting under wifi is not doing it...

thanks, jf
[Nexus 7 Original Development] pinoyto:
It's System Tuner..also you need to click on Boot Settings to be able to access the Screen-Off Behavior and change the governor from there.
[Nexus 7 Original Development] friedsonjm:
I'm trying to find what tile Boot Settings is under.. I know I'm going to feel dumb once I get it...

EDIT: System Tweaks, Boot Settings - yeah, I knew I'd feel dumb...
[Nexus 7 Original Development] clemsyn:
:) Just goes to show how long I've been out, can't take a chance on pulling out what's left of my hair coz they are just falling off faster than their growing now, LOL. Anyways, that fix on the ROM side will most likely fix it. Goodluck in your kernel :)

---------- Post added at 03:46 PM ---------- Previous post was at 03:43 PM ----------

Your welcome, its great that it works for you. Maybe it's bypassing the ROM control and giving it over to system tuner when you use the same governor on Screen-Off. Looks more like a ROM issue than the kernel as per _motley but glad that this simple fix helps.
[Nexus 7 Original Development] chosen14u:
With the latest kernel 1.0.7 I'm getting a delay in when the screen turns off from pushing the power button. The delay is not there in 1.0.6
[Nexus 7 Original Development] 123egg:
Same here. The animation is like in slow motion when screen turns off
[Nexus 7 Original Development] Character Zero:
That might be because of:
[Nexus 7 Original Development] meatlocker:
Clemsyn, you are a legend around these parts, my man. You did heroic, HEROIC! things with the GTab, and turned that hunk of crap into a downright useful device. Very nice to see you here, sir.
[Nexus 7 Original Development] CooLoserTech:
You should add SMartAssv2 governor
[Nexus 7 Original Development] leelaa:
Id say that your best bet try nogpu oc, i dont have any problems with oc gpu, even at 1600mhz cpu.
[Nexus 7 Original Development] demandarin:
you can use system tuner to force all cores online also. ALL cores online, 24/7, WILL DRAMATICALLY decrease battery life.
[Nexus 7 Original Development] mkiker2089:
So are most people still getting the 1300 on screen awake? I am not as one other poster mentioned. I also have the Trinity Toolbox. Something between the new kernel and the toolbox seem to have fixed the issue. Perhaps the toolbox is overriding the screen governor?

I also noticed that even when I did have the 1300 issue my games would still use the 1600. Others refered to it as "spikes" but it wasn't that for me. If I played 5 minutes of "Where's my Perry" I'd be at 1600 for 3 or 4 minutes of that.

Anyway, the new Kernel is working fine and my Antutu Benchmark scores have greatly improved with the last two builds and the installation of TKT (removing Antutu's CPU Control app). I'm over 10k now.

Anyone else using Antutu Benchmark? You have to get the Kindle Fire version from Amazon (I did anyway) as the new one doesn't work on the Nexus.

---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------

Regarding Antutu Benchmark - Amazon offer version 2.4.2 which works Google offers version 2.9 which will not allow me to install it.
[Nexus 7 Original Development] leelaa:
Well i have to say this kernel is great, i undervolted today, gave asphalt 7 a run for about 45 minutes straight and the heat from the device was great, about 50° wich in my books is exceptional.

Battery life is great too. Thanks OP
[Nexus 7 Original Development] lightninbug:
Can u post a link to the antutu you used?
[Nexus 7 Original Development] mkiker2089:
It's in the Amazon appstore. It's also here http://www.amazon.com/AnTuTu-Benchm...ie=UTF8&qid=1343345146&sr=8-1&keywords=antutu but I think you have to go through the appstore to actually download it.
[Nexus 7 Original Development] phonic:
Question about this part.

So does that mean that it will do an additional -50mV on top of any custom undervolting? IE: If I set everything -100mV, would it drop it to -150mV when it's "cold"?
[Nexus 7 Original Development] phonic:
Hrmmm. So that's not necessarily a good thing. Actually, it could be quite bad if you do actively UV. If you find that "safe" minimum, and your tablet drops it even more, it could crash it. Which means you have to add 50mV to the safe minimum to be sure you don't run into any issues, which means you would always be 50mV over that threshold when it's "hot".
[Nexus 7 Original Development] thracemerin:
I believe that's why motley posted that in the 2nd post, to warn people of this potential problem.
[Nexus 7 Original Development] chosen14u:
Can someone address this please. I would love to use the latest kernel but I get a delay/slow motion screen off action with this kernel, the previous kernel I did not, another user suggested it was to do with the crt animation tweak that was added.
[Nexus 7 Original Development] jarjar124:
idk for me...1.0.7 feels slower/laggier than 1.0.6...but thats just me
[Nexus 7 Original Development] demandarin:
1.07 running	Good for me. I'm running the overclocked gpu version on stock rom. UNdervolted by -50mv. Put cpu overclock on 1.4ghz(undervolt and CPU overclock done on system tuner). Plus I have mortification trinity kernel app I/O performance tweak running also(applied automatically when app is opened. Its built into hard settings. Just open the toolbox and it runs the script.)

I figure putting CPU overclock on 1.4ghz like prime should be good plus better battery life than if I ran @ 1.6ghz.

@motley is it possible to implement the power modes like our Prime has? Power saving, balanced, and performance. Like in Asus quick settings on prime.
[Nexus 7 Original Development] _motley:
v1.0.8 released

v1.0.8 released. Please see OP. We can now play around with the PegasusQ governor and see what we can do with it. I haven't played with any tunables yet, still learning it myself. Should be a good governor for multi-core once we get it tuned properly. It works pretty well as is.

P.S. A little trivia...3-to-1 choose the GPU OC version when downloading:D

Yeah, it's a bit awkward, but clever since this automatic under-volt is good for battery and longevity of the cpu. You can still try to knock down the voltages to see what you can get away with (YMMV), but we just need to keep this mind.

Fixed in v1.0.8. Caused more harm than good, sorry :o

Yes, I could do this, but I am not sure I want to do it exactly the same way, since we will then need a custom app/widget for control. This might be a nice little project for me that would be fun when I have some extra time.
[Nexus 7 Original Development] CooLoserTech:
The PegasusQ for those of you

http://xdaforums.com/showpost.php?p=24233103&postcount=3
[Nexus 7 Original Development] Metallice:
Is using a hotplugging governor really a good idea when tegra has its own hotplugging?
[Nexus 7 Original Development] CooLoserTech:
pegasusq governor is reallyreally smooth and jank free in games and apps and ui

ill run battery tests tomorrow
[Nexus 7 Original Development] _motley:
I guess we'll see.... Here is what I found about the native hot plugging on/off switch supposed to be built into the gov

http://xdaforums.com/showpost.php?p=24233103&postcount=3

If it doesnt work well, we can try to fix it or take it out.
[Nexus 7 Original Development] Annihlist:
Hi All,

Tested out the new governor. So far no problems at all. I played super Mario on emulator for an hour and also browsing forums for another hour. Everything is fluid at 1600mhz gpu oc version.
[Nexus 7 Original Development] demandarin:
Back on v. 1.07 and everything is good. Ran quadrant, overclocked to 1.6ghz & UV by -50mV across the board, and it scored very high in all categories. Ran sqlitebench and good score of 34secs. Overall. Top of the list. Then ran nenamark2 and got a best score so far of 61.1fps. Im not sure what was going on with THST new kernel on my device. But back on 1.07 and everything running great.

I did notice also that UV does keep CPU temps down. Even through all 3 of those benches, back to back and overclocked to 1.6ghz, my temps stayed low. Where before I UV, they would shoot up fast. So I think for me, -50mV across the board is good. Even if tegra decides to do another -50mV, like motley mentioned, it won't be drastic. MINES is holding the UV pretty well so far.
[Nexus 7 Original Development] _motley:
Haha, that was a long post! It's definitely a finicky beast right now, so yeah it's just experimental and I am not expecting rave reviews for PegasusQ just yet. I used it for a night and think that it is not scaling down like it should (at least for the 2nd cpu), so it is chewing more battery than it should when the screen is on. I was able to play some games and browse the web without any issues. Scored a 12000 in Antutu, so that wasn't bad.

About your instability issues. If you have several apps loaded trying to control your CPU, then things will be more difficult to tame. It shouldn't revert back the the PegasusQ governor like that after a reboot unless some app is resetting it. If things get wacky in System Tuner, clear your data in system settings for the app and make sure that any other CPU control apps aren't set to change to something different. Then, reboot and go back in and see how it goes. System Tuner Pro is working great for me for monitoring, but I did see the same types of instability at first with the app when I was switching back and forth between System Tuner and SetCPU. The transition between the governors is rough and I think that is what you are seeing. It has to disable native hot-plugging and then re-allow it when another governor is switched back to that uses native hotplugging. Not sure this is all working reliably right now.

I am curious how it goes for others that don't mess with the PegasusQ governor after the initial install. Theoretically, it shouldn't behave any different than 1.0.7 except for the reverted pause on screen off.
[Nexus 7 Original Development] _motley:
P.S. Changed v1.0.6 and 1.0.7 to "stable" releases. 1.0.8 is still beta for sure.
[Nexus 7 Original Development] demandarin:
I did like	you said. I went into app settings and cleared system tuner data. Then I booted into recovery. Flashed back the new 1.08 version. Then rebooted system. Went back into system tuner and everything looks fine. Leaving it on interactive governor. OC back to 1.6ghz. UV -50mV across the board. Lets see how she do throughout the day ;)

Thanks for the tip!
[Nexus 7 Original Development] bclark:
Hopefully you are able to get it running properly, I have an s3 and it runs incredibly.

Have you looked into gokhanmoral's got to see what he has done with it, obviously taking into account Sammy v asus?
[Nexus 7 Original Development] giveen:
Heh _motley, totally off topic question, but my tablet I dev for has a 2.6.36 kernel, is it an easy port to 3.1, or am I looking at a total rewrite of my stuff in mach-tegra?
[Nexus 7 Original Development] mkiker2089:
So far on 1.0.8 I'm getting an Antutu score of 10k+. I'm not seeing any adverse effects. I set the gov to interactive and have the max CPU as 1600.

If anything my wireless seems a bit weak, but I can't swear that the Nexus hasn't always had weak wireless. I'd think it's not related.

I've noticed on the Antutu test the FPS in the two 3d tests are now 60-65 where as before the last few builds they were 55-58 or so.

As before my max CPU seems to be sticking after screen off as well so either your kernel or trinity's toolbox have fixed that one as well.
[Nexus 7 Original Development] foxorroxors:
can we get a third kernel with 512mhz on the GPU plz? also anyone sorted the clocks changing after the screen times out?
[Nexus 7 Original Development] friedsonjm:
Did you sideload AnTuTu? I'm getting the 'Device not supported' on Play...
[Nexus 7 Original Development] DJLamontagneIII:
He got it from the amazon app store.. the kindle fire version works for n7... he posted a link a few posts ago
[Nexus 7 Original Development] foxorroxors:
get 10256 on antutu just downloaded the apk 2.9.0 from a random website
[Nexus 7 Original Development] friedsonjm:
OK, I'm trying to keep up with all this... where do I find that toolbox and the trinity tweak? thanks, jf