yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] leelaa:
Can anyone get aokp to boot using this kernel? At first it bootloops so i hold the piwer button to restart againg and it works. And when ever i reboot the device when on, it bootloops again.
[Nexus 7 Original Development] brizey:
I had the same issue...but i kept trying and it works ok now. I downloaded the kernel again....not sure why that worked since the previous download had worked on paranoid.

I also booted into the ROM, then flashed trinity then flashed motley. Seems to be ok now.
[Nexus 7 Original Development] leelaa:
Will give it a go. Thanks matey :)
[Nexus 7 Original Development] Jay Aristide:
I run all stock frequencies with interactive/deadline, fsync off, /data remounted, and 100mV undervolt. No lag/stutter to speak of in any games, including DT and GOF2...

On the subject of fsync, I've been disabling it whenever possible for a couple of years on heavily used devices being used by many people - noons and guru's alike - and have only had a /data integrity issue once. I'd let my mother run a device with fsync disabled :P
[Nexus 7 Original Development] leelaa:
Gof2?
[Nexus 7 Original Development] Jay Aristide:
Galaxy on Fire 2, very intensive game during missions.
[Nexus 7 Original Development] _motley:
Hi, hope everyone is doing well. Just wanted to let you all know that I have been busy with work and family, so I haven't had much time to do much with Android here lately. Thanks to those helping out on the thread, you do a great job supporting each other. Hopefully I can back to working on Android soon!
[Nexus 7 Original Development] leelaa:
No rush mate. Its not like the kernel isn't good enough already ;)
[Nexus 7 Original Development] Jay Aristide:
What leelaa said. I really can't imagine this kernel getting much better, and IMO, Google should just incorporate it into their next JB update.

---------- Post added at 02:18 PM ---------- Previous post was at 02:10 PM ----------

Oh, hey leelaa.. I found a game that I'm pretty sure will tax your n7 to the max.. It's the only thing I've found that makes mine stutter in the slightest (and it definitely does stutter some (but not much)).

Dangerous HD with everything turned up to high makes my device stutter when exiting warp and dogfighting in systems with a lot of planets/stations/anomalies.
[Nexus 7 Original Development] leelaa:
Will have a go an see what its like, thanks. ;)
[Nexus 7 Original Development] noneabove:
Hey, so my tablet just rebooted for seemingly no reason, could be nothing, but if i provide you with last_kmsg, can you do anything with that to check if something weird went wrong ?
[Nexus 7 Original Development] CharliesTheMan:
Also if you could add your kernel build and version, the configuration such as CPU speed settings, governor, if voltage is stock or modified, what app you're controlling the kernel with, things like that; you will probably get some useful feedback.

Also if you can remember, what apps were in use when you got the reboots and what apps had you had open that were in the background.
[Nexus 7 Original Development] luke05dee:
Hi, the kernel is running great! Although it would be amazing to see the gpu overclocked to like 550mhz but without a pixel clock increase as I have read that that just wastes power and heat. :)
[Nexus 7 Original Development] Jay Aristide:
What game/app/scenario is the 484MHz OC not far more than adequate for? I'm just curious, as I've barely been able to force my tab to fire up the 4th core, let alone make the GPU stutter at 416MHz
[Nexus 7 Original Development] jazzboyrules:
The kernel's running great on my stock N7. Love how snappy and stable it is.

GPU484_build_219, max 1100MHz, ondemand, noop
[Nexus 7 Original Development] airmaxx23:
So what are acceptable CPU temps? What would be considered "getting warm"?
[Nexus 7 Original Development] will444:
What's the best 1.6hgz settings?
[Nexus 7 Original Development] demandarin:
Mid 60's and up. I believe motley raised the the temp that causes throttle down to kick in. So CPU can get hotter and still have Max performance. I think he raised to 70. Can't remember. But I know he raised it up from stock temp.

You can use system tuner to check CPU temp. I use trinity kernel CPU temp widget so I always see what my temps are. During normal use and during benchmarking.
[Nexus 7 Original Development] t_007_v2:
adjust your settings and play the same game and see which ones perform better for you. i personally seem to get the best scores & performance using interactive with cfq. nena2 performance/cfq 70.7fps and hit 71 once but avg around 69.4 to 69.8 using inter/cfq daily use. been enjoying the motley modded by clemsyn @ 1.8 / 650 with the glazed jelly bean rom and my n7 vibrates with raw gaming power.

battery drain gaming is like 5hrs at the most lol but i always have that n7 plugged in. i own two n7s one for gaming and one for reading, tunes and movies just perfect for when i'm flying all over the place.
[Nexus 7 Original Development] Jay Aristide:
I ran SPB 3D on my SGS4G.. Really loved it, except for the fact that it liked to reload a lot...

Definitely looks slick on your tablet, man.. I might have to reinstall it, I paid fifteen bucks for it, after all...
[Nexus 7 Original Development] t_007_v2:
thx. you should reinstall the SPB people are always like what tablet is that. your right it's expensive but it does give jelly bean pizzazz lol.

on gpu overclocking i agree on most games it's overkill except open world games like TDKR, spiderman and the like. it seems that gameloft utilizes just a single or at most dual core with their games?
[Nexus 7 Original Development] mix1234:
What are some safe values for under voting? I searched and couldn't find much...
[Nexus 7 Original Development] demandarin:
There are no standards as everyone device will handle different UV values. Just take baby steps. If you using system tuner, just do it in increments of -25mV at most. Before you do THST, save the default values. Press that tab. So you can always go back to default in case you went too low. For ex. UV -25 across the board. Run THST for a couple days or so and see how it holds up. You can Finch some benchmarks or stress tests to also see how it holds up. If your device handles it well,hen decrease by another -25mV. Repeat same process. Don't get too crazy with it though as too much UV can actually cause your battery to drain faster. Whatever you do, don't save new values until you absolutely sure your device handles it well. If not, you could end up with booting issues if values set to low.
[Nexus 7 Original Development] M3drvr:
Love this kernel. Run at 1.6 and 520 problem free for days now. With - 75mv across the board. Everything so smooth and perfect. Keep this kernel developing this way! No needto run or even look elsewhere. AAlthough with all the developers moving in here I think there will be some nice competition moving in. Especially Franco, his stuff is pretty awesome!
[Nexus 7 Original Development] espionage724:
Hmm, I believe this can happen, but is there an explanation as to why?
[Nexus 7 Original Development] leelaa:
I think its because if you UV to much the cpu has to do more work to run at that voltage. Even though it is stable.
[Nexus 7 Original Development] luke05dee:
Hi _motley I have a fairly big problem. I have two nexus 7's both running your kernel and a stock rom. Both recently started to show strange battery behavior as in both tablets will just shut off at about 40% battery life and would make a strange buzzing sound when putting them on to charge, after about a 30 seconds of holding the power button down the tablet will go to the charging screen. Also after it has been fully charged it will hang on 100% battery life for a fairly long time. I thought both may have a hardware defect so I flashed a stock recovery image using the tool kit on one nexus 7 and flashed codename rom on the other but keeping your kernel on the nexus 7 with codename's rom on. The battery behavior of dieing at about 40% on the codename rom with your kernel remained the same. But the other nexus 7, which was showing the exact same behavior is now on stock everything and the battery dies normally. In addition I just flashed stock on the other nexus 7 and the problem has stopped. Both tabs were using your 520mhz GPU kernel and both tablet stopped showing this strange battery behavior when your kernel wasn't being used. I don't know what to do, I love the gpu overclock as the tegra 3's gpu is really weak, but I need to be able to trust my battery. Please could you look in to this? If it was happening to just one tab, I would think it was a hardware problem, but as it is happening to two and when your kernel is taken off the problem stops, I thought I should tell you.
[Nexus 7 Original Development] Jay Aristide:
Try the 416MHz or 484MHz GPU version, and see if there's a difference. Also, were you under/over volting? Did you happen to notice if the tablet was getting hot at the time of cutoff?

To each their own, and I understand the desire to push this baby to it's limits, but I honestly haven't been able to find anything I can throw at it that makes it stutter, save for one game, and even that behaves when I turn a single, unimportant setting down one notch.

I'm running 1.1.1, stock frequencies, -100mV UV, interactive/deadline
[Nexus 7 Original Development] luke05dee:
I'm going to try 484mhz, I suppose I can leave all the serious gaming to my galaxy s3 with the exynos 4412 SoC. My normal setup would be fsync off, -100mV on all frequency steps, 520mhz GPU, 1.4ghz cpu and that would be it. I am now currently trying, on both, -75mv, fsync off, 484gpu, 1.3ghz cpu. I hope it stops happening. I really like this kernel. :)
[Nexus 7 Original Development] Jay Aristide:
What serious game(s) does the n7 not handle perfectly at stock speeds with the rest of those options enabled?
[Nexus 7 Original Development] DJLamontagneIII:
Your at two extremes with your settings you really should slowly work your way up rather than jumping straight to 520 GPU and 100mv uv as not all chips are created equal

exactly I've had no trouble playing any game at stock or 484... personally 520 gets to hot after a wile and not really all that much real world difference to justify it for me
[Nexus 7 Original Development] luke05dee:
All these examples are at stock gpu for the s3 and n7. Yet it is note mentioning the s3's mali-400mp4 gpu can be overclocked safely to 700mhz thanks to the 32nm manufacturing process the heat isn't bad and at the same clock speed the s3 is considerably faster than the geforce ulp in the tegra 3. Asphalt 7, the nexus 7 has no where near as many affects enabled as my s3, so the game consequently looks a lot nicer on my s3. Not only that, my s3 plays the game smoother with the extra effects. Dead Trigger isn't exactly what I would call smooth in the n7, I have edit the xml in the shared prefs folder in /system/data/data on my s3 to enable all the tegra 3 effects on the international s3, and is is so much smoother on the s3. The amazing Spider man is a lot smoother on my s3. Nova 3 has a huge amount of extra effects on my s3 and yet is still smoother than my n7. Don't get me wrong, I like the n7 a lot. It's just not the best for gaming. Although at 484/520mhz it isn't bad at all and the nexus 7 was possibly the best thing I have bought in a long time.

---------- Post added at 02:32 AM ---------- Previous post was at 02:29 AM ----------

I have worked my way up, I have had the devices for over a month and I have slowly worked my way up.
[Nexus 7 Original Development] Metallice:
You pretty much only listed Gameloft games. Gameloft doesn't optimize their games for tegra 3 and that's why you end up with crappy framerates and effects set to medium instead of high. The gpu in the tegra 3 is top notch. It's gameloft that sucks.
[Nexus 7 Original Development] bso44:
Can someone tell me what I'm doing wrong here. I followed these instructions to disable fsync and setup a zRAM but I can't seem to make it work. When I type "busybox free" in a terminal emulator, I'm still getting all 0s next to "Swap" for my last line. And my settings aren't sticking in System Tuner after a reboot.

Only difference is that I did it using ES File Explorer and there was no .bak file in the folder to delete.
[Nexus 7 Original Development] farmerbb:
Check your script and make sure this line is correct as shown:

echo $((100*1024*512)) > /sys/block/zram0/disksize

Also, ES File Explorer doesn't always like to refresh when it's supposed to. After you're done editing the file hit menu and choose Refresh, then you'll see the .bak file. Delete that and then redo the permissions on the original file.
[Nexus 7 Original Development] bso44:
Yea, the line is exactly how it's shown. And even after I hit refresh, I don't see the .bak file.

---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------

I see 4 files in the init.d folder. S90zRAMandSpeedTweaks, 99pmwcpu, 99pmwioscheduler and 99pmwsdcache.

---------- Post added at 11:39 PM ---------- Previous post was at 11:35 PM ----------

Also, does it matter if I'm using the free version of System Tuner?
[Nexus 7 Original Development] demandarin:
same here. I can actually run 484mhz gpu& 1.1ghz cpu and games play fine. and IM playing nova3 online multiplayer. hardly any game more graphically intense than that and my n7 plays it fine. along w/tegra3 optimized ones also. n7 is a beast when it comes to gaming.

---------- Post added at 12:26 PM ---------- Previous post was at 12:17 PM ----------

Why are you typing "busybox free" in terminal? all you need to do to check zram swap is type "free".

Use script manager to run zram script if init.d not working or other apps. but u can use faux reset kernel w/init.d support to give u that. I have that but use S manager anyways to make sure my scripts running. find script file. select it. Then script. Then press Su & boot icon. then press run. you will see it run command and say zram successful. then press back. then save it. now on boot it'll run automatically everytime.

Also make sure your busy box and Su is updated to latest versions/binaries.
[Nexus 7 Original Development] bso44:
OK, I ran it in Script Manager and this is what I get:

exec sh */system/etc/init.d/S90zRAMandSpeedTweaks*

root@android:/ # exec sh */system/etc/init.d/S90zRAMandSpeedTweaks*

/system/etc/init.d/S90zRAMandSpeedTweaks[7]: can't create /sys/class/fsynccontrol/fsync_enabled: No such file or directory

/system/etc/S90zRAMandSpeedTweaks[13]: /system/xbin/busybox: not found

/system/etc/S90zRAMandSpeedTweaks[14]: /system/xbin/busybox: not found

---------- Post added at 09:36 AM ---------- Previous post was at 09:35 AM ----------

And both busybox and SuperSU are updated to the latest versions.
[Nexus 7 Original Development] Jay Aristide:
Your busybox doesn't appear to be in /system/xbin

Type

busybox which busybox

And modify S90zRAMandSpeedTweaks accordingly.
[Nexus 7 Original Development] bso44:
When I type "busybox which busybox", I get:

/system/bin/busybox

So that means I should modify the script like this right?

#/system/bin/sh

#remount /data for faster i/o
mount -o remount,noauto_da_alloc /data /data

#disable fsync (controversial, I've been doing it for years with no real issues)
echo 0 > /sys/class/fsynccontrol/fsync_enabled

#set zRAM size (change the 512 to 1024 for a full 1GB of swap, I use 512 because I'm on an 8gb and space is precious)
echo $((100*1024*512)) > /sys/block/zram0/disksize

[B]#use busybox to create and activate zram0, if busybox is not in /system/xbin, modify accordingly
/system/bin/busybox mkswap /dev/block/zram0
/system/bin/busybox swapon /dev/block/zram0[/B]
[Nexus 7 Original Development] Jay Aristide:
Yep :)

Also, change the fsync line to this:

echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
[Nexus 7 Original Development] bso44:
Gotcha. I'll give that a shot and report back. Thanks.

---------- Post added at 11:02 AM ---------- Previous post was at 10:51 AM ----------

OK, looks like that worked. Now when I type "free" in the terminal emulator, I get:

Now my only problem is that the System Tuner settings still aren't sticking. Does it matter that I'm using the free version and not Pro? I tried uninstalling System Tuner and reinstalling but still no dice.
[Nexus 7 Original Development] Jay Aristide:
Nah, but make sure in boot settings, you're choosing the init.d method for applying each tweak :)

I use the free version, too
[Nexus 7 Original Development] bso44:
As per your directions, I've got "init.d script" for"Re-apply SD tweak" and "Re-apply CPU settings" under Boot Settings. Everything else is "Disabled".
[Nexus 7 Original Development] Jay Aristide:
Feel free to enable/disable whatever you like in system tuner, it's a magnificent app. In fact, this conversation reminded me, and I just bought the full version :)
[Nexus 7 Original Development] bso44:
Any ideas why my settings still aren't sticking though? Cache Size is still 2048, IO Scheduler is still on sio and my voltage numbers are still on stock after a reboot.
[Nexus 7 Original Development] Jay Aristide:
No idea, whatsoever... The only thing I can think of is System Tuner isn't being granted SuperUser permissions..
[Nexus 7 Original Development] bso44:
Weird. I granted SuperUser permissions in the beginning and even get a prompt that says System Tuner is being granted SuperUser permissions when it's being booted up.
[Nexus 7 Original Development] Jay Aristide:
Yeah, man, I really don't know, then

That's odd
[Nexus 7 Original Development] demandarin:
Try deleting the cache and data from system tuner. From N7 settings then apps. Then reboot. Start up system tuner again. This time it should be a fresh start and it'll ask you for SU permissions. Make sure to allow it. Then try your set up or whatever and see if things stick. Bit with system tuner, you need to set them with boot in order for them to stick after a reboot. If not, it usually always goes back to default.
[Nexus 7 Original Development] bso44:
Yup, I've tried clearing cache & data and setting up System Tuner again. I've also tried uninstalling reinstalling it. How would I go about setting them with boot?

---------- Post added at 01:04 PM ---------- Previous post was at 01:00 PM ----------

Btw, when I run the script in Script Manager now, I'm getting:

exec sh */system/etc/init.d/S90zRAMandSpeedTweaks*

root@android:/ # exec sh */system/etc/init.d/S90zRAMandSpeedTweaks*

Setting up swapspace version 1, size = 52424704 bytes

UUID=092c011f-4c26-4703-841d-6b027053eea3

swapon: /dev/block/zram0: Device or resource busy
[Nexus 7 Original Development] demandarin:
One thing is remembered, when I had similar issues, is to go back to busy box. Alot of times you may think you have latest version but its more to busy box than just that. When I first rooted I had similar issues trying to dget these scripts to rum right. Sonic checked busy box. I ha latest version but the files said they needed updating. The applets WERE NOT symlinked. I couldn't get terminal to tell me zram from typing free and I could get script manager to run the file correctly. So in busy box, I did the smart/recommended install. Where I updated/symlinked all the applets thatwas checked by default. You shouldn't have to check anything. Then install and they all updated and were all symlinked. It will tell you where each Applet is symlinked to. After I did that, everything worked right. Terminal worked from typing free. Then my script manager properly ran the zram script and said successful or whatever. Try that. It made everything work for me. Sometimes when rooted, the busybox we get isn't updated/symlinked all the way. So we have to do this to get those type of things working right.
[Nexus 7 Original Development] Jay Aristide:
What I do is adb shell into /system/xbin and run a rather lengthy sh command that does 'busybox --help', separates the commands by commas, and sy links them all :) Never could get the 'create symlinks' option to work properly and ended up with things commands like 'free' and 'lsmod' not working properly.

For anyone who wants to familiarize themselves with the commands busybox provides, the following would be a good exercise for you:

Your Computer's Shell:>adb shell

you@droid~$: su

you@droid~#: mount -o rw,remount /system /system

you@droid~#: cd /system/xbin

you@droid/system/xbin#: busybox --help

Here, busybox will output all of it's commands

you@droid/system/xbin#: ln -s busybox <command>

For example, if you were creating a link for the 'free' command, you would

you@droid/system/xbin#: ln -s busybox free

This will create a symlink in /system/xbin called 'free' that when executed will pass every argument (including free itself) to 'busybox'

Repeat this process for all the commands you see under 'busybox --help', and by the time you're done, you'll have a pretty good working knowledge of the functionality busybox provides, as well as an arsenal of linked applets that will make your terminal feel a lot more like a standard *nix shell

Then finish up with

you@droid/system/xbin#: cd /

you@droid/#: mount -o to,remount /system /system

you@droid/#: exit

you@droid~$: exit

Your Computer's Shell:>

The 'create symlinks' option in the busybox installer does a lot of this for you, but how much do you really learn that way?

Hope this helps
[Nexus 7 Original Development] morfic:
Stericson's busybox installer is more reliable.

If you insist to do it on your own:

busybox --install -s /system/xbin/

It does it all correct and complete.
[Nexus 7 Original Development] bso44:
Thanks fellas. I'll look into Busybox and report back.
[Nexus 7 Original Development] noneabove:
You mention setcpu shouldn't be used for voltage control.. is it okay to use bit for profile control ??
[Nexus 7 Original Development] bso44:
So I went to Busybox (Stericson's) and did the Smart Install even though it looked like all the applets were already symlinked. System Tuner settings still didn't stick after a reboot. I guess I'll just have to manually change the settings every time I reboot.

Not really a big deal but kind of annoying. Thanks for the help, guys.
[Nexus 7 Original Development] t_007_v2:
Just use setcpu profiles... Set a profile for "screen unlocked" that way you always boot up at 1.3ghz. When you unlock the profile kicks in and sets your cores wherever you want. What I do using the motley modded by clemsyn 1.6 with the 650 gpu (:

No reason to leave it at 1.8ghz unless you want to wipe out your battery in 4hrs.

---------- Post added at 12:50 AM ---------- Previous post was at 12:29 AM ----------

setcpu is perfect for setting and executing profiles. all my games are played at 1.6ghz except for THD games imo there is no need to over clock them. 1.3ghz is plenty of push since THD utilizes all four cores and produce a bunch of heat.

see my setcpu icon in the lower left corner? perfect for a quick cpu adjust using SPB shell 3D.

2nd tab in setcpu is where you set your profiles and your screen unlock should look like this.
[Nexus 7 Original Development] noneabove:
Yeah I've actually got it set up to under clock when battery gets low or hot :)
[Nexus 7 Original Development] NoTnERb:
To anyone who's used both motley's kernel and trinity, can you confirm that motley's has better battery without any UVs? That seems to be the case for me running 100-1600 on both
[Nexus 7 Original Development] CerB:
Wanna try this one out :)

but coming from trinity should i wipe anything ? or just flash away ?

Flash the zip using custom recovery (no need to wipe anything)

thanks to myself, better learn to read topic posts ....
[Nexus 7 Original Development] CharliesTheMan:
Wipe cache and dalvic cache, it won't hurt anything to wipe those two when flashing mods, themes, kernels, etc.