yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Dsmforlife92:
Where is download link for beta 39
[Nexus 7 Original Development] Shano56:
Page 19
[Nexus 7 Original Development] cburk01:
Great

Normally on Quadrant I get a score of 3,500 or so but NOW at 1.6GHz I am getting 4,600 to 4,800. Almost 5,000. If I could get 5,000 on this I'd be happy so I could rub it in my brother's face. XD This is great :)
[Nexus 7 Original Development] thracemerin:
Quadrant scores are affected too much by turning fsync on and off for them to be reliable for anything, turning fsync off can raise quadrant scores by 1000+ but it's not a good or safe idea to actually do.
[Nexus 7 Original Development] antiochasylum:
I can't come close to any of these benchmarks, my best quadrant is 4457, 53 seconds on the SQ benchmark. Only thing is nenamark2 58.9fps.

Not sure why mine is so slow. But I'm already sending it back and waiting for my new one since my screen isn't sticking in the bottom corner.

I've tried everything. And nothing helps.

Getting a FC on the camera app on kernel 39
[Nexus 7 Original Development] demandarin:
just because your scores arent higher than others mean your device is slow. 53 seconds on sq benchmark is still good along with your other score. those scores still higher than majority of more expensive high end devices.

best of luck on your new replacement coming defect free.
[Nexus 7 Original Development] ikn0wagh0st:
Will this work with the JR5 Rom?
[Nexus 7 Original Development] Rafase282:
Yes I use it with that rom and it works well.
[Nexus 7 Original Development] leelaa:
Where do i overclock the GPU?
[Nexus 7 Original Development] thracemerin:
It's not user settable, it's just overclocked.
[Nexus 7 Original Development] DaF1974:
You can use apps like SetCPU, ROM Toolbox, or System Tuner.
[Nexus 7 Original Development] _motley:
Build 39

v1.0.5 (build 39) now available in OP. Changed to beta status since everyone is reporting success. If anyone has any ideas to make it better, please let me know. While this kernel carries my name, I consider it the community's properly and hope that some of you savvy devs that have been posting here will consider helping out. Some other great kernel devs will soon be joining us and bringing their ideas into the fray, so it can only get better from here!

We'll be looking closer at the voltage control (it works, but is a confusing in some app UI's) as well as hoping to get an OS level fix for the return to 1.3GHz on return from sleep (power.default.so).

I also want to create an AnyKernel delivery method, but have barely gotten started. If anyone has time to pitch in and help provide this, I would greatly appreciate it!

Enjoy you weekend!
[Nexus 7 Original Development] phonic:
Thanks motley! I've been using b39 for a while and it seems very stable. In fact, all your kernels have always been stable. I assume that the b39 in the OP is the same as you posted yesterday, right?

Question: it seems like in this kernel the 51mhz step is being ignored. In prior versions, afaict, it was working even if "100" was the min_freq. But now it doesn't go below 102.

I've also used system tuner to UV it down -50mv across the board without issue. Running at 1.5, since i didn't see any need for going all the way to 1.6.

Can you explain how the zram thing works? I looked all over the file system for the init scripts but couldn't find any.

Thanks again for all the hard work!
[Nexus 7 Original Development] DRSdroid:
there is no deep sleep on this kernel... i only tested it for a bit, is the lowest cpu speed (51mhz) considered "deep sleep"? Because when i ran the kernel for a few hours (screen off and on) cpuspy says "deep sleep" is left unused. Other than that, awesome kernel, kicks ass at the benchmarks! i had a nenamark of 59.4fps!

The reason i switched back to stock was over concerns about battery life. The stock kernel really does have a remarkable way of throttling the cpu that both allows for great performance and great battery life.

Please keep developing this though! it's fantastic and i would likely switch to it again if "deep sleep" comes back and perhaps "smartass" is implemented as a cpu governor
[Nexus 7 Original Development] phonic:
Deep sleep works fine. I think your issue is that you have deep sleep being ignored by CPUSpy (the default iirc). Go into the settings menu for the app and make sure its being monitored. That should show you deep sleep time.
[Nexus 7 Original Development] DRSdroid:
No, it's definitely showing deep sleep in cpuspy because it shows it on the stock kernel, and it's listed as an "unused cpu state" with this kernel. Any reason why it would show this way for me and not others? I cleared cache before flashing, should i clear dalvik too next time?
[Nexus 7 Original Development] evonc:
Is there hotplug support automatically included in the governors? I know for all our moto kernels there is a specific hotplug governor that acts similar to on demand but has the ability to turn off an unused core.
[Nexus 7 Original Development] _motley:
Deep sleep works fine. Mine is currently showing 85% of time in that mode. Maybe try using the app "better battery stats" to determine where the wake-lock is coming from.

No need to wipe anything before flashing.
[Nexus 7 Original Development] phonic:
When looking at activity through System Tuner (or whatever that app is called), I can see that most of the cores are kept offline, and only get brought online when needed. So assuming that the app is reporting the correct information, then yes it works properly.
[Nexus 7 Original Development] boynamedstacy:
So I tried the CM10 build and I'm loving it so far. Motley 39 seems to be running great except for the fact that it resets to 1.3 when the screen turns off and the 51mHz slot won't stick. I tried using both setCPU and System Tuner Pro to set the 51 slot. SetCPU says that its active but when I use system tuner it just pops back up to 102. No sticky. No problems with deep sleep or over clocking though. User experience is excellent. Your making great headway here Mo! Thanks dude!
[Nexus 7 Original Development] thracemerin:
I believe the 51mhz frequency is for the 5th low power core on the tegra chipset, it will only drop to this when it's in the modes that activate this chip not while it's on the main chipset.
[Nexus 7 Original Development] Land Master:
Nice work on this Kernel.

Working fine on MoDaCo's J4. Haven't cooked J5 yet but others have reported success.

Appreciate those of you that have reported their findings!!

---------- Post added at 02:35 PM ---------- Previous post was at 01:47 PM ----------

I do have a question ....

I assume the Kernel the "Boot.img" file contained within the various Rom's and flashing a new ROM that contains said file replaces the Kernel?

Assuming so ... can this file be replaced by simply renaming the downloaded Kernel file to boot.img and then re-zipping the contents?

OR ...

Is it a better procedure to flash the new ROM, make sure it boots properly, and then flash an updated kernel?

TIA
[Nexus 7 Original Development] thracemerin:
boot.img also contains the ramdisk which is all the files required to get the system going before loading the ROM, the reason there can be issues is that modifications done for different ROMs may not be compatible with the ramdisk that motley includes with his kernel, this is solved by putting together an any kernel package which basically pulls out the zImage (kernel) from the ramdisk already installed on the phone and injects the new one keeping the ramdisk intact, motley already expressed an interest in getting this working so he should no longer need to build different packages for different roms.
[Nexus 7 Original Development] Land Master:
So the long and short of it is ...... as long as the proper Motley Kernel was downloaded for the particular ROM you want to flash (CM10 or Stock, Etc), then the re-naming / re-zipping process should work?

In other words ... the Ramdisk for the various ROM's has already been plucked by Motley and included in the Kernel download and in the future this will be done on-the-fly?

Anyway .. I think I'm going to stick with simply flashing the ROM first and then updating the kernel but I appreciate you helping to clarify the information!!
[Nexus 7 Original Development] thracemerin:
Yeah, if you pull the boot.img that motley made for CM out of his package and put it in the CM ROM package it should work, you may run into problems if you pull the boot.img for one of motley's other packages and stick it in the CM ROM package though.
[Nexus 7 Original Development] Land Master:
Yeah, that was a duh on my part and I would have screwed it up. I was simply going to rename the download but now I realize that wouldn't have worked as it contains the update scripts.

I got it! Thanks a bunch!
[Nexus 7 Original Development] thracemerin:
@motley - looks like trinity is using any kernel for N7, so you could probably download the trinity zip and get the scripts, etc... out of there.
[Nexus 7 Original Development] antiochasylum:
I'll say again, with modacos camera starter, the camera FCs on build 39. Logcat doesn't show ****.
[Nexus 7 Original Development] DRSdroid:
I reflashed and wiped dalvik first.. works great this time around! Deep sleep and all. Using no frills CPU app, is there any good app for monitoring how much each core is being used? And any info on activating zram or getting the country speeds to stick?
[Nexus 7 Original Development] phonic:
I too would like some more info on the zram stuff. I don't see any details in the OP and haven't been able to find any script examples.
[Nexus 7 Original Development] DJLamontagneIII:
He has a script example in his transformer thread and it works for us... there's a link in motley's sig
[Nexus 7 Original Development] jarjar124:
lets say i dont like this kernel or any other kernel on the nexus 7...how do i revert back to stock kernel? nandroid?
[Nexus 7 Original Development] thracemerin:
That or you can push the boot.img from the stock factory images on Google's site.
[Nexus 7 Original Development] jarjar124:
im a noobie at pushing stuff..i usually just flash back lol..what would the command be to push the boot.img?
[Nexus 7 Original Development] thracemerin:
you need to have fastboot installed, then just boot to the bootloader on the tablet, connect it to usb, then 'fastboot flash boot boot.img'
[Nexus 7 Original Development] fr4nk1yn:
You could also test the kernel, as I plan too, with fastboot boot boot.img after extracting it from the zip.
[Nexus 7 Original Development] antiochasylum:
Or you could search the thread. Epic face palm.
[Nexus 7 Original Development] _motley:
I updated the OP installation instructions earlier today with an optional step 3 (revert back to stock). I couldn't remember who had posted the zip when I downloaded. Thanks go to antiochasylum.

Not sure what is going on....I am on the latest Modaco ROM and I can run the camera app fine on build 39. I just tested again to be sure and I can take pics and capture video. I haven't tried his add-on app with stock or other ROMs though...
[Nexus 7 Original Development] antiochasylum:
Hmm. Yea this is stock with camera add on app.

Trying to prevent from flashing a rom, because I'm sending this tablet back. Screen separation issues. I'm waiting for my new one.

If it works on modaco then not a clue why its not working on stock. I'll use modaco once I get my new one.
[Nexus 7 Original Development] Land Master:
Yeah I'm on MoDaCo J4 with no issues.

Out of curiosity. Did you try to fix the screen separation with the tighten screws thingy? Mine has it too and it seems to be getting worse.
[Nexus 7 Original Development] kieso:
I have the screen issue also. I'm not going to mess with it. I suppose I'll get a new one but the lady just said she was forwarding my information to someone else. I used to open my gtablet when needed but I didn't want to bother when I could get a new one.
[Nexus 7 Original Development] phonic:
Not sure what good the standalone camera is. I don't see any use in even having it - which is probably why Google left out the app. Don't get me wrong, the physical device is a necessity (ie: skype, etc.), but I don't see myself taking any pictures or video with the thing.
[Nexus 7 Original Development] antiochasylum:
I did, but it didn't do anything. This is the glue no sticking to the glass.

Pretty annoyed. Called google Thursday. They better get back in touch with me tomorrow or I'm gonna be pissed. Lol
[Nexus 7 Original Development] Land Master:
Agreed but it would be more the principal of it for me. FC's drive me crazy cause it indicates that "something" is wrong but yeah the camera app is pretty worthless on a low megapixel front facing cam.

Thanks for the replies regarding the screen everyone.
[Nexus 7 Original Development] _motley:
1.0.6 build 47

1.0.6 build 47 released:good:

See OP for details...working good so far.
[Nexus 7 Original Development] aaronpoweruser:
Glad any kernel worked out for you
[Nexus 7 Original Development] _motley:
Thx, I use it with my prime kernel too, but there it gives problems with the 64GB models and we can't use it for everyone. I've been lazy about getting it working here lol. Thanks for the push. Hope the ROM is coming along well.
[Nexus 7 Original Development] aaronpoweruser:
Lots more modules so lots of cherry picking I should have it out tomorrow night
[Nexus 7 Original Development] Rafase282:
How do I enable zram?
[Nexus 7 Original Development] _motley:
Save this to a file and run from terminal, script manager or system tuner. Or create a file in init.d and automate it if your ROM supports it.

#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984

echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";

if [ ! -e /sys/block/zram0/disksize ] ; then
echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
echo "[90ZRAM]: Is this a ZRAM kernel?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
#find busybox in /system
bblocation=$(find /system/ -name 'busybox')
if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
echo "[90ZRAM]: busybox found in:" $bblocation;
echo "[90ZRAM]: Setting ZRAM disksize.";
echo $((100*1024*1024)) > /sys/block/zram0/disksize

echo "[90ZRAM]: Starting ZRAM...";
bblocation=${bblocation%/*}
cd $bblocation
./busybox mkswap /dev/block/zram0
./busybox swapon /dev/block/zram0

echo "[90ZRAM]: ZRAM activated.";
else
echo "[90ZRAM]: ERROR! busybox not found!";
echo "[90ZRAM]: Is busybox installed? Symlinks set?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
fi
fi
[Nexus 7 Original Development] digweed4me:
Latest 1.06 updAte
[Nexus 7 Original Development] digweed4me:
Quadrant score latest 1.06
[Nexus 7 Original Development] David Horn:
How warm are your tablets getting with this kernel? I flashed it last night but it felt uncomfortably warm during general use to went back to stock. Presumably battery life is taking a bit of a hit as a consequence of the increased speed?
[Nexus 7 Original Development] demandarin:
It does get hotter, faster, with this latest kernel, it seems. Nenmark2 gave me 60.6fps best. That was without overclock. When I raised clock to 1.6ghz, my score went down..lol. quadrant gave me around 4768 score overall, on normal speeds. Overclocked, score dropped. All these benchmarks vary in scoring though if you run them back to back. New kernel seems to work good. I will leave it on latest kernel for now. If battery life takes too much of a hit, I will just flash back to good ol 1.05 build 39 kernel. That kernel was working very well for me.

Just a f.y.I. I'm using stock rom with these motley kernels ;) still waiting for roms to mature more before I go flashing one of them.
[Nexus 7 Original Development] leelaa:
Love the new build thanks mat.

Sent from my Nexus 7
[Nexus 7 Original Development] jarjar124:
how is ur io that high?
[Nexus 7 Original Development] leelaa:
Beats me.

Sent from my Nexus 7
[Nexus 7 Original Development] jarjar124:
did u do anything else besides flashing the kernel?
[Nexus 7 Original Development] CooLoserTech:
Lets see if we can get this GPU over 500
[Nexus 7 Original Development] asgard:
N/A
[Nexus 7 Original Development] armyboy11b:
I don't think its from this
[Nexus 7 Original Development] _motley:
Very sorry to hear this mate. Appreciate your posting either way. I am now also providing a stock GPU download for v1.0.6 (see OP). I kind of wanted to do this anyway and already had the compile switch in place. This made me pull the trigger as I want people to have this choice.
[Nexus 7 Original Development] _motley:
Damn dude, I'm not much of a fan of Quadrant for serious benchmarking, but that's one hell of a score! Which ROM are you running?
[Nexus 7 Original Development] asgard:
Appreciate your efforts Motley, one of the best kernels I've used across numerous devices, I'll be back as soon as I get a replacement, likely just some flaky Asus QA if there isn't any other mention in the coming hours in which case I'll /dev/null the post to avoid potential noob scaring :)
[Nexus 7 Original Development] danielsf:
I am not sure this is from the GPU OC, when doing research on this tablet there were a few people on you tube and here on xda who have had the same problem as you. I think it is just a random fault as I have seen quite a few people say that they have had it. http://www.youtube.com/watch?v=Vow4liV43tM From what I have seen on the internet or seems to just be an unlucky fault that pops up. I hope everything goes well for getting it replaced :)
[Nexus 7 Original Development] giveen:
Odd i getting worse quadrant scores now. Was doing an average 4700 now only 4000 after latest build
[Nexus 7 Original Development] _motley:
Some things to consider why your scores may drop:

1) When the device sleeps and you wake it, it is going back to 1.3GHz. I am working on this and hope to have a fix before long. This is an OS limitation/feature, not a kernel issue.

2) Dynamic EDP (a temp throttle layer on top of Nvidia's EDP) will allow OC but will throttle the tab back when you hit 60C. So, if your tab gets warmer, it is falling back to 1.3GHz and your scores won't be as high. If I open this up and allow the tablet to overheat to say 80C or so, scores will increase dramatically. I think most want performance, but not at the cost of a super-overheated cpu. So, when I need to bench over and over to test stability, I set it the AC vent to keep it cool. In normal conditions, this is exactly what you want to happen. When it throttle back to 1.3, it cools fairly quickly and will again allow you to clock back to whatever your OC limit is.

3) You never step in the same river twice....Quadrant tests are of very short duration (and are prone to misreport from what I have heard). If you have background processes working (like an account sync or a system event that requires disk i/o, cpu etc.), they will easily lower your quadrant score since the tests are of short duration. Antutu is a bit better because the tests are of a longer duration and it balances out, but is still prone to this as well.

4) ROMs will have an effect due to tweaks that they make (sqllite libs, memory tweaks, disk mount parameters etc.)
[Nexus 7 Original Development] leelaa:
Nope just ran the test @ 1600/1600

Sent from my Nexus 7
[Nexus 7 Original Development] rockaholic112:
Great work!

Sent from my Nexus 7
[Nexus 7 Original Development] okantomi:
This is odd...this morning I had a similar experience on xda 2013 beta version...very milky, totally unlike the way it had been last night, so I scrolled down and chose an older version (xda 2010), and the milkiness completely disappeared and hasn't come back.

Not saying that this is related to your issue, but could it be app related and not related to the kernel?
[Nexus 7 Original Development] giveen:
This kernel + euroskank rom = no camera
[Nexus 7 Original Development] katestar:
I don't OC the cpu, but the GPU OC in the latest bulid is working great, I mean I can now have rapid tide gp and shine runner at max graphics with out the occasional drop in fps like at stock. Also gamelofts amazing spider man is now playable :D and with no cpu OC but with the GPU OC the temperature is relativity low on heavy load :) Roll on 500mhz :D Thank you :)
[Nexus 7 Original Development] _motley:
Not sure if you are talking about the camera launcher by Paul O'Brien or not, but it was reported back a few pages that the Modaco Camera Launcher didn't work with the stock rom for someone (FC's) and it was thought to be the kernel. However, Paul Obrien's camera launcher works fine with this kernel and the Modaco Jr5 ROM. I'll double check this again when I get home as I am not sure if I tested on v1.0.6 yet, but build v1.0.5 was definitely working fine with the camera launcher on the Jr5 ROM.

Awsome, thanks for the feedback. I played a little Dead Trigger last night and it was working great (Dead Trigger is free now BTW:good:). Yeah, I agree, if you are playing vids, watching Netflix or playing games, 1.3GHz is fine, no need to OC the cpu on this kernel. I sometimes like to turn up the CPU OC when I am web browsing...that really helps with JavaScript/Flash/page rendering etc. on heavy pages.
[Nexus 7 Original Development] jarjar124:
im not sure is it the gpu oc doing this but my n7 gets a bit warm when playing cs portable online after 30 minutes lol. but great kernel..got 5116 on quadrant no oc running with trinity kernel toolbox :D
[Nexus 7 Original Development] giveen:
Thanks, motley, I am actually switching back to JR5 because of that issue, I like the camera.
[Nexus 7 Original Development] rockaholic112:
This is happiness.

Sent from my oc'd cm10 nexus 7
[Nexus 7 Original Development] _motley:
Here is where I am at with trying to fix the CPU falling back to 1.3GHz on screen off. I found the culprit module/code, changed it, and complied a full JB build. But, the output file I set out to change still doesn't fix the issue. It might be deeper in the Android build and require more files to be updated, not sure. If this fixes it in his ROM build, then most ROM's can follow suit with this patch soon I hope.

http://xdaforums.com/showthread.php?p=29218456#post29218456
[Nexus 7 Original Development] hanthesolo:
_motely, awesome, AWESOME work! I honestly don't know why most people don't use linaro...it provides such a large speed increase with such a small amount of effort. Your latest update has fixed some microlags I was having on stock and JR5. I will try it with CM10+eos as soon as I get enough nerve to perform a full reset, as I don't want to lose anything at the moment, and stock is plenty fast, although linaro rom's may push me over the edge. I have no heat issues (except for heavy, heay gaming in a hot car), and it runs imbelievably smooth @1.6 GHZ. Keep up the good work, and as other people have said, pushing the GPU is 500 and beyond would be nice (just as proof-of-concept).

EDIT: It seems that flashing a CM10 rom without wiping has caused some issues with stock roms (great...), so it seems that I will be testing your kernel on linaro CM10 far sooner than I thought. I have a older CWM backup with stock so I can sorta get back with that, so I will tell you how it goes if my issues persist.
[Nexus 7 Original Development] Land Master:
Now that the newer versions are using "any Kernel" is it a good procedure to flash back to the stock Kernel first before flashing the latest build so that it has the stock RamDisk to work with?

OR

Can we simply flash the latest build over a previous build (I'm on 39)?

I would assume the 2nd option should work fine as it is my understanding that the prior versions were compiled by simply including the original Stock RamDisk anyway but I figured I would ask. Thanks in advance.
[Nexus 7 Original Development] demandarin:
I flashed over previous build & everything is fine. no wipes or reverting back to stock kernel needed.
[Nexus 7 Original Development] ericsch333:
USB

has anyone tried usb storage with this getting my cable today..
[Nexus 7 Original Development] demandarin:
if it doesnt work initially, try getting the app called stickmount. it will mount unmount your usb otg cable/device.