yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] mkiker2089:
Friedsonjm- I have the Amazon appstore on my Nexus. It allows Antutu to install. It's an older version but apparently the new one works as well if you can find and sideload it.

As for the Trinity tweaks, there's an app called "trinity kernel toolbox" in the play store. It isn't free, costs 4 bucks if I recall. It's supposed to run a few optimizations on it's first run. I don't know what exactly. It did improve my Antutu score however. I was using Antutu CPU control before.

---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------

Yes, with Trinity's toolbox and the any of the Kernels above 1.0.6 on my Nexus I seem to be staying (and according to CPUspy using) 1600. I don't know which fixed it.
[Nexus 7 Original Development] evonc:
Was noticing similar issues but i reflashed, wiped cache/dalvik and now it seems fine. Here's my time in state after two runs of antutu in a timeframe of about 40 mins.

Sent from my Nexus 7
[Nexus 7 Original Development] friedsonjm:
9836 on 1300, 12158 on 1600
[Nexus 7 Original Development] luke05dee:
Hiya, now that we've been running at 484mhz and I am yet to hear of any person having a problem, do you think we would be able to pump it up a notch? I just hope some day we might be able to get to 520, but I am thinking there must be a reason why this isn't the full speed tegra 3, maybe it never met the stability requirements at those higher clocks that nivida required. I just hope we can :fingers-crossed:
[Nexus 7 Original Development] friedsonjm:
This is interesting... on Quadrant at 1300 got 4575 total, best ever at that speed. What is interesting is that the area that has really improved is I/O, now at 5503 ! Result of the GPU speed increase?
[Nexus 7 Original Development] foxorroxors:
quadrant is a rubbish bench mark for testing, one line of code increased my I/o by 4k points yet antutu still gave the same 350 points I can't see how in anyway except to maybe trick quadrant into giving up some extra points?
[Nexus 7 Original Development] thracemerin:
Most if not all android benchmarks (antutu & quadrant included) can be easily manipulated by certain kernel settings that make little to no actual difference in performance.
[Nexus 7 Original Development] mkiker2089:
Quadrant runs too quickly. Any field will tell you that the more data you have the better the result. Antutu gives inconsistent data as well however based partly on random chance and partly on how close my Nexus is to the air conditioner.
[Nexus 7 Original Development] Roll3r:
Had nearly the same exact issues you experienced w/ PegasusQ. Wifi wouldn't reconnect after waking the device, Settings froze when trying to toggle Wifi, System Tuner would just freeze upon opening, etc. Luckily I hadn't set System Tuner to apply the CPU changes on boot, so a reboot had me back on Interactive.
[Nexus 7 Original Development] phonic:
True, but I do think that the modifications to fstab actually help real world performance. By disabling file and directory atimes and turning off some of the constant writes, you will probably see a noticeable boost in disk access. I wouldn't really call it a 'trick', as it is a valid optimization. Though obviously not as significant as quadrant makes it seem.
[Nexus 7 Original Development] foxorroxors:
do we actaly have a benchmark that we can use that's consistent and non bias?
[Nexus 7 Original Development] thracemerin:
I don't disagree that there are some benefits to some of the tweaks, but there is a large amount of benchmark score placebo involved too.

Some are better than others, but the answer is there isn't one.
[Nexus 7 Original Development] phonic:
The best benchmark is your own subjective opinion.

In the end, it doesn't matter what "score" you get on Quadrant, Antutu, etc. It all comes down to what YOU do on YOUR device, and how well it works for those tasks. While the benchmarks are certainly useful (in some ways) to help guage the difference in changes/tweaks you make, they don't mean anything if you aren't happy. So play around, find what's best for you, and enjoy the tablet :).
[Nexus 7 Original Development] thracemerin:
True, a smooth, robust user experience is far better than any benchmark score.
[Nexus 7 Original Development] friedsonjm:
Which I have found includes turning off all animations, of any kind, wherever I find them, eliminating wallpaper, and spending a lot of time making sure that all of the icons to apps I frequently use are on the home page, and logically organized... that leaves me plenty of time to spend changing ROMs and kernels!
[Nexus 7 Original Development] jarjar124:
1.0.8 is running fine for me atm...cpu sticks when screen turns off(using combo that consist of tkt and system tuner) i believe its just the governor that isnt stable. im really looking forward to that governor. heard many good things of it :)
[Nexus 7 Original Development] foxorroxors:
I'm glad I'm not the only one, all the fancy crap turned off an the nexus is on steroids everything is instant =) ripped up 179k on broswermark, so Ui is instant and webpages are pretty much instant swell. love it.
[Nexus 7 Original Development] demandarin:
I got mines from there also. It works on nexus 7. Only thing is, when you open it up, it tells you a newer version is available. But when you click the link tl the play store, it'll tell you app not compatitble. So you can run your tests from Amazon version. But you can't update to latest version and Antutu won't allow you to upload your scores unless you update. Hopefully Antutu update soon for JB/nexus 7 support.
[Nexus 7 Original Development] mkiker2089:
Someone, sorry can't find the post, in this thread loaded the new one manually and said it works. If so hopefully Antutu just needs to fill in the paperwork to get it approved for JB.
[Nexus 7 Original Development] demandarin:
I got 10453 with Antutu on latest 1.08 version with gpu overclock. This version has been running well since following motley tip he gave me earlier and leaving governor on default interactive. I also decided to UV another -25. So right now I set my OC to 1.4ghz and have UV by -75mV so far. So far so good.

---------- Post added at 04:08 PM ---------- Previous post was at 03:59 PM ----------

Lol. I thought I was the only one. I go into developers settings and cut off windows animations, transition animations, & animation duration. Makes everything, UI wise, happen nearly instantly. That's how I speeded up My prime also when it was stock. Cut all that stuff off. Less CPU/GPU dedicated to that. Rather it use that extra elsewhere.
[Nexus 7 Original Development] mkiker2089:
I do that in Windows as well. Windows 7 can be pretty effective when you turn the prettyness down a bit.
[Nexus 7 Original Development] phonic:
I like pretty...
[Nexus 7 Original Development] mkiker2089:
I like my tablets fast and my girls pretty. Pretty tablets are cumbersome and fast girls....
[Nexus 7 Original Development] pinoyto:
Tried 1.0.8 and I am having issues with Pegasusq...Seem to hang my system tuner every time I change governor to pegasusq. I just stay on interactive and everything is good. Do you think we can push the GPU a bit higher?
[Nexus 7 Original Development] leelaa:
Wouldnt mind a 500 gpu or a 512. Suppose we will have to wait and see.
[Nexus 7 Original Development] CharliesTheMan:
I'm up for pushing mine till it starts smoking or making sparks. Totally worth the cost of a tablet to post a pic of my GPU combusting in my Sig.
[Nexus 7 Original Development] thracemerin:
If you guys want to, you can fork motley's tree and look at his commits for the GPU and increase them and build the kernel itself, it's really really easy and motley has done most of the heavy lifting for you. You need a linux box or a virtualbox setup, but even that's not difficult.
[Nexus 7 Original Development] phonic:
I cloned the git repo, but can you provide some direction on where to go from here? I've built generic Linux kernels for servers, but not cross compiling for Android.
[Nexus 7 Original Development] thracemerin:
Look here: http://source.android.com/source/building-kernels.html

Mainly the building section since the kernel is already downloaded, etc... when you get it from motley's git.

You're going to want the linaro GCC 4.7 toolchain instead of the one in that guide, but it's pretty much the same deal as in that guide. To make it easier you might want the same one that motley is using but you'd have to ask him about that.

Edit: (i added a little more info above)
[Nexus 7 Original Development] phonic:
Thanks!

Ok, so I think I got it working.

I pulled the zImage out of motley's 1.0.8 release, and used that extract config script to make the .config file. I then downloaded the linaro gcc toolchain from here:

https://android-build.linaro.org/je...id-toolchain-eabi-4.7-daily-linux-x86.tar.bz2

and adjusted my path to use include the bin directory in there first, and set the proper variables.

It's "make"'ing now, and all looks good so far. I'll compare the compiled zImage to the one I downloaded when it's done to see if there is a difference. If not (cross fingers), I'll take a look at the kernel source and maybe play around with it.
[Nexus 7 Original Development] thracemerin:
If you want to flash it, just stick the zImage from /arch/arm/boot where the zImage in motley's zip is and you should be good to go flashing it. Worst case you boot loop and have to go in recovery and reflash motley official.
[Nexus 7 Original Development] phonic:
Well, it built the kernel without errors!

But, mine seems to be a little different....

-rwxr-xr-x 1 jbabiak jbabiak 3781496 2012-07-27 22:57 arch/arm/boot/zImage (mine)

-rwxrwxr-x 1 jbabiak jbabiak 3777116 2012-07-26 23:58 kernel/zImage (motley's)

:(

Maybe due to a different toolchain? I don't see any commits since yesterday, so I imagine everything else is the same.
[Nexus 7 Original Development] thracemerin:
I wouldn't worry about that little bit of size, just flash it and give it a try, i've built the same kernel with the same setup a bunch of times and had small variations in size.

Just make sure you have a motley official kernel on sd too in case it loops.
[Nexus 7 Original Development] phonic:
Yeah, I just rebuilt it again (wanted to double check something unrelated), and it was a different file size compared to my first identical build.

Ok, flashing now. Crossing fingers!

---------- Post added 28th July 2012 at 12:02 AM ---------- Previous post was 27th July 2012 at 11:26 PM ----------

Flashed, booted and good to go!
[Nexus 7 Original Development] thracemerin:
Nice! Now you can make all the mods you want and test them out, I do recommend baby steps though if you are planning to pump up the GPU, you never know where the breaking point might be. Don't want your tablet bursting into flames or anything :D
[Nexus 7 Original Development] phonic:
Where's the fun in that??? :eek:
[Nexus 7 Original Development] thracemerin:
Well, I don't think the warranty covers immolation :p
[Nexus 7 Original Development] foxorroxors:
dude don't be mean sort us out! I have no access to a Linux or windows machine ATM!
[Nexus 7 Original Development] Character Zero:
If you could post a small tutorial that would be cool. Wouldn't mind messing around and building my own kernel just to try it.
[Nexus 7 Original Development] hanthesolo:
Hmm, I think your guide+helping phonic has pushed me int he right direction on how the heck to compile kernels (I believe I was getting rom compilation messed up with kernels, which seem to be FAR simpler). I already have the Linaro toolchain (4.7 I think) sorta installed (the gcc compiler states 4.7, but when I compiled the linaro toolchain, it errored out 3/4 of the way through).

Anyway, back on topic for _motleys thread, I have had no issues so far with build #77. I have not attempted to use the pegasusq governor yet (my N7 is basically my only non test-bed device at the moment :D), but the latest version seems to be faster than the previous version/s. Combine this with a linaro-compiled version of CM10, and my N7 hahs not experienced lag in days!
[Nexus 7 Original Development] superleeds27:
Backed up ROM. Flashed 1.0.8 #78 Build. Seems okay so far. Time to tweak!
[Nexus 7 Original Development] mrRobinson:
I flashed this on BAMF rom and everything is running great. Only thing weird is on boot initial cpu min value was 1600 and max was set to 1300. Are these swapped? I changed the min down to 102 but every boot it goes back. I'm still using interactive and sio and flashed the 1.08 without the GPU OC. anyone know how i can get these to stick on boot?
[Nexus 7 Original Development] superleeds27:
tried using an app to do it?
[Nexus 7 Original Development] mrRobinson:
no just bamf settings. let me load setcpu....

Yea my stupidity... setcpu is keeping it. I just wasn't thinking and using bamf settings as if it can't be wrong.

what are stock cpu max/min? 1300/102?
[Nexus 7 Original Development] superleeds27:
Yeah i think so
[Nexus 7 Original Development] mkiker2089:
Well there is the 51 setting but people are a little mixed on if that should show up or not. I've been told that the 51 cpu is actually a fifth core optimized for audio. Like an independent sound card?

Anyway, some apps have 100 as the low others have 50.
[Nexus 7 Original Development] leelaa:
Dont know if this has been posted before but....... in systm tuner i changed my max freq to 1.5 then went to boit settings, and changed screen off max freq to 1.5. Now my freq does not reset after sleep.
[Nexus 7 Original Development] mateorod:
Ha. You want to see what I just put it through after installing this kernel? The temp on this thing rose almost 20 degrees centigrade in five minutes. It ended up at 64 degrees. OC to 1500, no other tweaks...

]

That's a load, there.

I could feel the back getting hot, but I think something must be off with either System tuner's temp conversion it my understanding of it's display. I doubt the thing got to 147 degrees or whatever.
[Nexus 7 Original Development] superleeds27:
Probably because you overclocked!
[Nexus 7 Original Development] mateorod:
No, it's a miscalibration or reading in tuner. It has me at 112 F at boot. Battery monitor widget will register the exact same minute as 24 degrees F cooler.

System Tuner just isn't reading my temp right.

But the load it was taking was real big, and the temp increase I have no doubt is accurate. I was running a jar binary in the terminal that just crushes resources.
[Nexus 7 Original Development] RegnierD:
I believe the 51mhz frequency is for the +1 core in the 4+1 core setup in our SOC. It's a weaker processing core for menial background tasks and simple processes to keep the more power hungry cores from draining the battery quickly.
[Nexus 7 Original Development] thracemerin:
Yup, for things like just playing music with screen off.
[Nexus 7 Original Development] jarjar124:
great kernel! major improvement from 1.0.6 in my opinion. my n7 doesn't get hot while browsing 2 hours straight now and isn't as hot when playing counter strike portable :D
[Nexus 7 Original Development] Rafase282:
Can someone tell me a bit more about the two new governors and if they can be used nad how they work?
[Nexus 7 Original Development] jarjar124:
so far they're not good to use. i heard it basically messes up ur tablet..freezing while multitasking etc. u can test it out. it needs further tweaking to be usable
[Nexus 7 Original Development] thracemerin:
PegasusQ is a governor for chips that don't hotplug themselves, since Tegras do this is likely the cause of some of the problems with that governor.

Try reading this http://xdaforums.com/showthread.php?t=1369817 it's for a different device, but the information is more or less the same, it will at least give you a decent overview.
[Nexus 7 Original Development] Kagedin:
These may be stupid questions, but what benefits would I gain from flashing this kernel besides the obvious additions of being able to undervolt and overclock? Are there any built in enhancements enabled by default? Also is there a link for the stock kernel somewhere so I can have a back up available? And are there any recommended settings to have this run as smooth as possible, Im more concerned with stability and day to day performance than any benchmark results.
[Nexus 7 Original Development] ice0901:
Anyone else has there tablet powering off during deep sleep?
[Nexus 7 Original Development] evonc:
Mine does it and other people have reported it as well. I think it's a software issue that Google has to address inan upcoming ota. However it will not power off if you're not plugged into the charger. Mine only does it when i plug it into the wall adapter at night and i see it turn itself off about 5 mins into deep sleep.

Sent from my Nexus 7
[Nexus 7 Original Development] demandarin:
Mine doesn't. Every since I reflashed motley latest, 1.08 w/gpu overclock and default interactiveggovernor, device has been running very well. No powering off during sleep. Plus I only draised the clocked speed to 1.4ghz. I'm also UV across the board by -75mV. Battery life is great. Very stable playing graphic intensive games even while undervolted. Device deep sleep goes well. I have no issues at all. Really liking this latest version. Surprised how well mine has been running with -75mV UV. mY CPU Temps definitely stay on the cooler side now. I'm on stock Rom using motley kernel
[Nexus 7 Original Development] ice0901:
IC I did notice it after it was plugged in the charger but it hasn't happened since its been off. I'll prevent t from deep sleep overnight and see what happens when I wake up
[Nexus 7 Original Development] phonic:
It's very weird, because there does not seem to be a rhyme or reason as to what causes the device to actually shut down.

I reported this issue a few weeks ago in a different thread (I think I was actually the first to notice it). The first two times I left my N7 plugged in overnight, it was off the next morning. A simple power button press turned it back online. The third time it didn't happen. The fourth time it did. Since then, it's never shut itself off automatically.

I've even left it plugged in for 12 hours or so in the middle of the day. Came back home, and it was plugged in and on.

Obviously I've been using a non-stock kernel, which might have something to do with the change in behavior (though I doubt this). And I did upgrade to the 'D' release too, but others also running this firmware are reporting the problem.

While I can certainly understand this happening due to design, to protect overcharging or something like that. But if so, it should happen all the time, not randomly. Or stop for no apparent reason.

In any case, very weird...
[Nexus 7 Original Development] _motley:
If you don't need any of the tweaks/additions listed in the OP, then going to a custom kernel won't likely benefit you.

These are experimental right now and only PegasusQ is enabled in v1.0.8. LulzActive is only available in the source code and not activated. I wouldn't recommend toying with these right now unless you want to help troubleshoot the technical aspects of their issues when enabled. They are tagged as experimental only, so I don't recommend using for normal users. I will turn PegasusQ off in the next version because people will keep reporting issues.

Yes, this happens on the stock ROM/kernel as well when it is plugged-in to the charger. I think there may be a thread in general about it. Never happens when I connect via USB to the PC, but only when plugged into the wall. And for the latter, it doesn't happen very often, maybe only once or twice since I have had the tablet. Maybe it happens only when we hit full charge? I have seen this on the GT8.9 tab as well. Hopefully we (or Google) can get it figured out.
[Nexus 7 Original Development] daveleebond:
The NTFS functionality is it ro or rw?
[Nexus 7 Original Development] _motley:
Funny you should ask. I have it changed to rw in the next release coming out soon. Just testing it 5 minutes ago! Stock was ro.
[Nexus 7 Original Development] foxorroxors:
hey motely, anychance of a experimental kernel with 512mhz gpu plz? id do it myself but i have no access to a linux box, or pc for that matter =(
[Nexus 7 Original Development] phonic:
Since a few people have requested it, and I was bored, enjoy:

http://core.routed.com/motley-512gpu.zip

Disclaimer:

1) I am NOT a kernel developer. In fact, I'm not a developer.

2) I simply took the latest motley github commits and modified the "arch/arm/mach-tegra/tegra3_dvfs.c" file, changing the values motley previously put at 484000 to 512000 in the OC section. Based off of the prior GPU OC commits, I *assume* this is all that's required. Obviously all credit for the kernel itself goes to motley.

3) While I am running my self-compiled kernel based off of the github commits without any changes right now, I have NOT tested the GPU OC kernel above. I simply made the change above and recompiled it since a bunch of people were asking for it. I imagine it should work, but I can not guarantee this.

4) I am not responsible if your GPU blows up, melts through your tablet, causes cancer, etc.
[Nexus 7 Original Development] jarjar124:
ima wait til this is tested and working fine :)
[Nexus 7 Original Development] foxorroxors:
erg guess ill be the first then, fastboot at the ready lol
[Nexus 7 Original Development] foxorroxors:
harsh ran nenamark2 scored 62.1 second rn it reset my tab =(
[Nexus 7 Original Development] foxorroxors:
stable now i think solid 62.1 five runs of nenamark, had to up my volts from 1125 to 1175, (stock 1200) guess that last jump to t33 speeds need a bit more power.
[Nexus 7 Original Development] hanthesolo:
Phonic, did you boost the GPU voltages any? Do you even need to?
[Nexus 7 Original Development] foxorroxors:
pretty sure its stable hit 62.4fps on nenamark , in performance mode.

asphalt 7 is smoother now too much more playable.

batman is a dream to play =)
[Nexus 7 Original Development] phonic:
No I did not touch the voltages. Only modified the freqs. I'll let a more knowledgeable person than I deal with that. :)
[Nexus 7 Original Development] phonic:
Awesome. Glad its working for you. I imagine motley will be integrating it into the official kernel eventually.

---------- Post added at 06:10 PM ---------- Previous post was at 05:53 PM ----------

So far 9 people have already downloaded it. But the interesting thing (to me), is that one person was running the following UA:

"AndroidDownloadManager/4.1.1 (Linux; U; Android 4.1.1; Nexus 7 Build/JRO03

H

)"

I was under the impression that JRO03D was the latest build. Where is this "H" version coming from? Is there a new release somewhere? They were coming from Dallas TX, so it's not an International version (I assume). I read about how the Xoom was getting H, but I didn't think it was released yet for the Nexus 7. Or is this some custom ROM that is using an unreleased version?
[Nexus 7 Original Development] leelaa:
I think the H is from AOSP.
[Nexus 7 Original Development] brizey:
That was me from Dallas...I am running paranoid. It shows the H version.

Edit: running fine, by the way.

Another edit: Getting 61.9 in nenamark with -100 mV across the board. Ran ten back to back nenas, score was 61.7 to 61.9 the whole time. Played a little dead trigger, too. No issues to report.
[Nexus 7 Original Development] mkiker2089:
Motley's kernel gave me a 65 on nenamark1 and 59 on 2. Doesn't seem to be a major improvement.
[Nexus 7 Original Development] _motley:
Hi guys, glad to see you having fun experimenting and learning to build etc. For me, at least with my testing, I honestly don't see much benefit at all in pushing it up to 520MHz in its current state. I have also tried 500 and 520, but if you look at the kernel log while running Nenamark2 or Antutu you will likely see a warning "bandwidth maxed out", so there are other limiting factors (emc/bus rate etc.) that are holding us back. Also, I am already getting 62.2 - 62.4 on Nenamark2 on my latest build (unreleased) with the GPU still at 484MHz. I think this was about the same in the previous build as well, but I can't recall for certain. I will still be playing around with the limiters to see what we can do.