yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] phonic:
Thanks, I'll give no-frills a try.

And btw, great kernel. I'm so happy you are working on the Nexus7!

---------- Post added at 02:40 PM ---------- Previous post was at 02:36 PM ----------

By the way, how low did you UV? Have you found a 'safe' threshold? I was going to try -50mv on each freq.
[Nexus 7 Original Development] danielsf:
Hi, may I ask if you have the problem of not being able to go to a lower clock speed than 1.6ghz, as I flashed the kernel and it was set to 1.3ghz yet it kept jumping up to 1.6 no matter what I tried to do to lower the max clock speed. As in every cpu controlling app would say the max clock speed was 1.3ghz yet it kept jumping to 1.6. :)
[Nexus 7 Original Development] phonic:
While I did see that issue with SetCPU, it looks like No-Frills doesn't have the problem. I turned off the former and turned on the latter. It's sat to 1500 max, and looking at stats, I don't see anything going up to 1600. It was earlier with SetCPU set to 1500 (not following that cap), but I think No-Frills is working properly. At least so far.
[Nexus 7 Original Development] danielsf:
I just tried that and cpu spy shows that I keep going to 1.6ghz even though I am set to a max to 1.3.

Edit: Turns out my device doesn't like 1.6ghz and it just froze on me and had to reboot. _motley what do you think please, is there a way to fix this as I really like the little extra kick this kernel give GPU wise, for example on dead trigger it would drop a frame or two every so often, with this it is a little bit better. Please could you fix it, my device unfortunately it can't handle 1.6ghz and I can't seem to lower it.
[Nexus 7 Original Development] antiochasylum:
If you guys want to go back to stock. Flash this in recovery. I tested it and it works.

Thanks to motley for the install zip.
[Nexus 7 Original Development] CooLoserTech:
When i installed this my settings were 51-1300 with interactive governor. It was so f in buttery smooth. I didnt mess with anything i was afraid of ruining the sexy
[Nexus 7 Original Development] kaizvn:
CPU rang 102MHZ - 1400MHZ

50% battery after 10 hours on battery, 2h30m screen on with wifi with game - chat - surf web - download stuff (full time).

that's mean I can use my device 5 hours/day.

cool kernel.
[Nexus 7 Original Development] drpfenderson:
Uh-oh. Yeah...magnetic cover. :-/ That's a weird and unfortunate bug. I'm going to do some research and see if other users are getting it without custom kernels. Guess it's not motley specific.
[Nexus 7 Original Development] bso44:
I just hope it's not doing cumulative damage to my speaker.
[Nexus 7 Original Development] seros:
Using a magnetic cover, unlocking after sleeping for a long time I usually get this continuous clicking/popping sound from the speaker that can last for around 10 seconds. Pretty sure it doesn't happen without the case.

But it didn't happen when I first got the case, I'm sure it started after a version upgrade of motley or cm10. Although that could just be coincidence..
[Nexus 7 Original Development] Robin2:
Great kernel. Still hoping for someone to incorporate a fix for the touchscree issues lots of people are experiencing. Not kernel related btw, just something Google needs to fix for the N7.
[Nexus 7 Original Development] Metallice:
Speaker popping with magnetic cover happens with both morfic/motley. It does not happen with the CM10 kernel so its an issue with something changed not with the source.
[Nexus 7 Original Development] demandarin:
Never had any touchscreen or speaker popping issues on motley latest stable.
[Nexus 7 Original Development] CekMTL:
Hahahahah xDDDD

Yeah, just got it a couple hours ago, in my hands, and it's a little cutie! (hope there are no hidden ASUSfluenza...:p)

Well... been adding a lot of stuff to my TF201 kernel from the N7 "deep wells of wisdom", some of them are on par with the latest N7 kernels here, but it is still private, for me, just in case my TF explodes in my face... but gosh... that asus kernel is a mountain of ...ummm..."manure".

I sure would love to help out the community once I'm up and running, and also will try to trickle all the knowledge to poor TF201 ;)

Good to see you here!! :)

---------- Post added at 01:53 PM ---------- Previous post was at 01:48 PM ----------

Hahahahaha xDDDDDDDDDDDDDDDDD

I don't claim anything and I don't even bother claiming that, but it has been running way way long time, before anyone even mentioned the word "fsync"... it was one of the first & easiest "fixes" I did, from the times where I was almost about to throw the TF out the windows with that botched EMMC access...

Anyways I never mentioned that I invented anything, I remember using the word "implemented"...

But, if it's you who "invented" it, my sincere congratulations m8! ;)
[Nexus 7 Original Development] GeekMcLeod:
Not sure what the hell went wrong, but I haven't been able to get this kernel to work. It will always get me stuck in a boot loop. I've tried several times, each time failing. I've been trying to get the "buttery goodness" to work. I've never had any issues when installing kernels.

Here is the last_kmsg (I think I did it right) from after being stuck in a bootloop.
[Nexus 7 Original Development] CharliesTheMan:
What's your current setup, what rom are you running it with?
[Nexus 7 Original Development] GeekMcLeod:
I'm using ParanoidAndroid 2.1.1
[Nexus 7 Original Development] CharliesTheMan:
So you wipe cache and dalvic cache, install the kernel, and reboot, and when it tries to boot it goes into a bootloop?
[Nexus 7 Original Development] GeekMcLeod:
That is exactly it. This is the only kernel I've had the problem with.
[Nexus 7 Original Development] CharliesTheMan:
Give me a second I'm going to flash it and verify some stuff.
[Nexus 7 Original Development] DJLamontagneIII:
Most likely a corrupted download... I flashed it with the same pa and no boot loop
[Nexus 7 Original Development] CharliesTheMan:
I just got done flashing on the previous version of Paranoid Android and then rebooted and downloaded the latest Paranoid, dirty flashed, and flashed Motley 1.1.1 484 OC on GPU and it flashed and booted fine also.

I think it's either something in your scripting or modifying with the buttery smooth thread or a bad download.
[Nexus 7 Original Development] jamminjon82:
Does this interact well with codename 3.5?
[Nexus 7 Original Development] Jay Aristide:
More than likely a bad download, there's nothing in my tweaks that would cause a boot loop...
[Nexus 7 Original Development] CharliesTheMan:
Sorry Jay now that I read back I see that I wasn't clear. I was thinking it might be an error from the user's end when playing around with scripts, I'm familiar with and believe in what you've contributed in your thread.

But you're right, at worst he would have a non change from what I can see and not an exciting fiery crash or bootloops.

I say delete all signs of the file, check the MD5 and download again.
[Nexus 7 Original Development] Pete7ate:
Great work as always motley.
[Nexus 7 Original Development] Bierfreund:
Is it possible, that the kernel does not work with AOKP?

I'm have aokp_grouper_jb-Sept-10.zip flashed as ROM.

I tried to flash motley_nexus7_with_stock_ramdisk_v1.0.5_build_39.zip and directly afterwards motley_anykernel_nexus7_1.1.1_NoGPUOC_build_220.zip. Whe i do this I stuck at the bootlogo.

If i onky flash 1.1.1 I stuck the the Google Logo, if i only install 1.0.5 I stuck at the bootlogo, too.

Is there anythins special to note on AOKP ROMs, or does it simply not work (yet)?
[Nexus 7 Original Development] CharliesTheMan:
Flash 1.1.1 only and it will work.
[Nexus 7 Original Development] Bierfreund:
Tried again and it stucks straight at the beginning at the Google Logo...
[Nexus 7 Original Development] Metallice:
You have to reflash AOKP first. You over wrote AOKPs custom boot.img when you flashed 1.0.5 and you have to reflash aokp to get their boot image back.
[Nexus 7 Original Development] Bierfreund:
I reflashed AOKP (and the GApps), before flashing 1.1.1 again. I always had a booting device before flashing the Kernel.
[Nexus 7 Original Development] Metallice:
Are you trying to flash a GPU oc version? If so, try the NoGPUoc version.

Otherwise I'm out of ideas. Only answer is there's some change to this kernel that your device doesn't like.
[Nexus 7 Original Development] CharliesTheMan:
Ok give me just a second, are you using Steve's build?

Update: I just flashed the kernel. It seemed to take a long time at first boot, I thought it wasn't going to work. But I manually rebooted while it was at that google screen and it booted to the rom and the kernel works great.

I'm running the newest build that has the quad core cherry picks and it's working good it seems like.
[Nexus 7 Original Development] nm8:
Hi

I'm running 1.1.1 at the moment and my battery goes flat quicker. Is there any way of going back to stock speeds (no overclocking) but also I would want to undervolt.

cheers
[Nexus 7 Original Development] CharliesTheMan:
You need to be using the no overclock GPU or 484 GPU build, and use system tuner to set your max CPU speed to 1.3 or 1.4 and min CPU speed to 100.

Make sure you aren't using performance governor which is next to the CPU speed controls. You want to use something like interactive or ondemand or conservative, you'll have to find what feels the best and gives you the battery life you're hoping for.

At 1.3 max CPU which is stock clock speed, this kernel will be quite a bit faster than stock because it's so much more efficient.
[Nexus 7 Original Development] Bierfreund:
No, I used the NoGPUoc version

I first flashed the AOKP nightly from today, afterwards the 1.1.1 kernel (No GPUOC). At first boot, the same problem, stuck at the google Logo for 10 minutes. Then i switched my Nexus 7 off and on again and then i booted. Seems fine now!
[Nexus 7 Original Development] nm8:
Thanks for the help. Do I really need to use the other kernel then, because when I checked the max speed of the cpu, it was set to 1.3Ghz, and minimum was 100Mhz.

Do I just need to change the Governor to r On demand etc.. ? Or do I really need to flash the no Overclock GPU or 484 build?

Thank you for your patience.
[Nexus 7 Original Development] Milamber33:
No, you don't 'need' to be using any particular kernel. Just pick the one that works best for you. That being said, the ones with no GPU OC are more likely to have better battery life, and the ones with GPU OC are likely to have better performance, so long as your device can handle it. Same with CPU speed. 1.3GHz is the standard max speed, but you can put it down to 1.2 or 1.1 for example to give yourself better battery life, or you can push it up to 1.4, 1.5, or 1.6 for better performance, again, so long as your device can handle it. It's the same with any other kernel, too.
[Nexus 7 Original Development] CharliesTheMan:
I'd flash the no over clock version of 1.1.1. In system tuner, click the CPU tab and make sure your CPU settings are 1.3 max and 100 minimum, and there will be a voltage tab on the menu bar across the top. Click that to open the voltage menu and subtract -25 mv (down at the bottom). Screenshot the voltages before adjusting and you'll always know what default was, and then after -25 run the ROM a lil while and see how it does. Then if its stable and works good after running some of your normal activities you can go down 25 again for a total of -50 so far. I'd test it at leat a day or so there and see how it does before going down anymore.
[Nexus 7 Original Development] thebobp:
Is anyone getting automatic shutdowns at 10% battery? (Using 1.11, 520 gpu, 1400 cpu with glazed rom.) I like this setup very much except for that.
[Nexus 7 Original Development] bigeyes0x0:
We have released a new tweaking app. For now it does not do much on the Nexus 7 but it will get there.

Discussion for it here

And you can get it in my signature.
[Nexus 7 Original Development] boynamedstacy:
Dude, really? STOP SPAMMING

Sent from my SCH-I535
[Nexus 7 Original Development] Jay Aristide:
:smh:
[Nexus 7 Original Development] rredef:
Lol..he's trying..
[Nexus 7 Original Development] morell2:
best kernel !

thank you very much!

is very smoother on nexus 7 and fast!

1.4ghz very good !

best kernel
[Nexus 7 Original Development] yukkio:
Hi, I've proved all xda kernels in my n7 but for me, this the best kernel. Motley, Have you planned another updated?

Thank you.

BR.
[Nexus 7 Original Development] dkflint723:
Have to say that after trying pretty much all the kernel's listed in this forum I keep coming back to Motley's. It is extremely stable and smooth. Thank you for all your hard work.
[Nexus 7 Original Development] nimrodity:
8h ?,i get barely 4h :(
[Nexus 7 Original Development] thcaddict:
Sorry for the noon question but how do I use System Tuner to undervolt? I don't see the option anywhere. What would be a sage, stable number to set it at for decent battery running the motley kernel?
[Nexus 7 Original Development] CharliesTheMan:
On system tuner open the CPU tab and there's a menu bar across the top with a "voltage" button.

Start out by undervolting -25 ( there's a button on the bottom that you click to do - 25 for every frequency with one click.)

Run it a little while and then do -25 again if it's stable.

You're 50 under now. You can try -25 again and see if its stable. If not bump it back up to -50 total.

There's an app called CPU spy, and if you set up your governor and CPU min and max frequencies and then install and start CPU spy or reset it, then run your tablet through its paces a while, it will show you what CPU speeds it spends a lot of time using, and then you can try undervolting just those speeds if you want to.

Personally I Undervolt mine by using the shortcut to bring them all down together, and that's plenty good enough for me.
[Nexus 7 Original Development] Shano56:
This kernel is simply the best
[Nexus 7 Original Development] willis936:
I'm still waiting for the feature that makes me a cup of coffee. Perhaps VPN integration that finds your internet coffee maker and allows you to set the next brew time.
[Nexus 7 Original Development] nm8:
Screen refresh rate.

Hi all

I don't know if the Kernel is what defines refresh rate, but I am using 1.1.1 NO OC and just found out the screen refresh rate is 66.1719hz while on my other Nexus 7 running stock, the refresh rate is 59.99795Hz. I don't know and I can't tell which one is better, but does it have anything to do with quicker battery drain on my Nexus running motley kernel?

Sorry for such a noob question.
[Nexus 7 Original Development] a Mandroid:
Motley incompatible with Paranoid ROM 2.12

Although I had success with the stock rom and motley, I am unable to boot after flashing motley with Paranoid ROM 2.12 latest.

My steps are: Flash Paranoid Rom from recovery, and it boots ok. Then goto recovery again and flash motley 1.1.1 - after which I get boot loop.

Has anyone had success with the latest version? If so, what could I be doing wrong? Your help will be much appreciated.

Paranoid Rom downloaded from here : [http://xdaforums.com/showthread.php?t=1800268]

:confused:
[Nexus 7 Original Development] Milamber33:
Have you checked MD5 sums for everything?
[Nexus 7 Original Development] joedoe:
Have you cleaned up cache and dalvic cache after flashing the kernel?
[Nexus 7 Original Development] nemesis93:
Thank you very much motley for this amazing kernel! Running the 520mhz GPU of kernel and look at the results o got on nenamark 2 :D
[Nexus 7 Original Development] jshashwat93:
Hey guys I have just installed this kernel and the app SystemTuner as suggested in the original post.. Now I don't know the liots to which I can under volt over volt my device. Can someone help me out... Thanks a lot..
[Nexus 7 Original Development] Milamber33:
I'm going to presume 'liots' is meant to be 'limits'. ;)

Noone can help you there. Each device is unique, so you just have to do your own testing. Just take it slow (25mv at a time is good), and test each step for stability, performance, and battery usage. If performance drops, the device heats up more, or battery usage increases, then even if it doesn't actually crash, it means that it's not stable at that voltage. All of those things are signs that the CPU is failing to execute some commands and has to rerun them.
[Nexus 7 Original Development] nm8:
You need to download System Tuner from the Market
[Nexus 7 Original Development] jshashwat93:
Thanks a lot... I undervolted my device by 100mv and while using after a bit it feels very slightly warm on the bottom left part... I havent used the device on stock really so i cant say if it always happens or if its the undervolting. However its not over heating by any angle just very slight warm (like really little).. What do you think about it?

I already have that app. Was just looking for help and tips on using it.

And guys I am currently using Paranoid Android Rom with this kernel and it works perfect. Only thing is while playing this game Agent Dash the game goes completely black for 1 second in like every 30-40 seconds and comes back. I dont think its the voltage or clock speed tweeks as I made everything default and even tried restarting the device with no luck. So is it the rom or the kernel? I have played this game on unrooted stock and it worked perfectly fine.. Thanks a lot..
[Nexus 7 Original Development] Milamber33:
If it's still benchmarking at about the same or better than it did at the higher voltage, you're probably fine. That's the quick test that I do, run a few benchmarks and make sure the figures don't massively drop. For example, in AnTuTu, mine gets over 12,000 at 1.54GHz, but if I push it to 1.6GHz, I can still use the tablet, but the AnTuTu score drops to below 7,000. That's a very clear indication that my device isn't stable at 1.6GHz with this kernel, at least not with the standard voltages. It's normal for it to get a bit warm, just watch out for really really hot or noticeable drops in benchmark scores. Also, do a few runs at each setting, to get an idea of what it averages, sometimes you get an exceptionally good or bad run.

As for the Agent Dash thing, if you're using the 512MHz GPU version of this kernel, try dropping back to the 484MHz version and see if that fixes it. If it does, then that means your device can't take 512MHz on the GPU at the voltages this kernel uses there. If you still have problems, drop back to the stock GPU version. If you're still having problems with that, I would start looking at the ROM.
[Nexus 7 Original Development] jshashwat93:
I am on 484MHz. Should i drop to stock or flash 512?
[Nexus 7 Original Development] Milamber33:
Try stock GPU version. If it works fine there, you know it was the GPU not liking the OC. If it's the same, you know to look elsewhere.
[Nexus 7 Original Development] jshashwat93:
Same issue :( Gonna try putting stock Nexus 7 kernel before changing ROM.... CAN you please send me a link or tell me where to get the stock kernel from? I am new to this rooting and flashing business so have no clue where to get stock kernel from. Thanks a lot.
[Nexus 7 Original Development] Milamber33:
It's linked in the OP of the CleanROM thread.
[Nexus 7 Original Development] jshashwat93:
Thanks a lot for the help. However it was an issue of the ROM. Apparently there is some issue in all CM10 and CM10 based ROMS and the solutioin is to flash this file: http://xdaforums.com/showthread.php?t=1875712

And now its perfect..

However i was on 484MHz first and now back to stock. Not sure if I should flash back or save on battery and stay on stock. Can you give me an example of an app or a video which shows clear different performance between the different GPU clock speeds so I can see for myself. Thanks a lot.
[Nexus 7 Original Development] t_007_v2:
Gpu oc is for gaming and you will see major improvement from just about all of the gameloft titles. Play asphalt 7 with the high rez maps enabled on stock n7 settings then play it on the clymsen 650 gpu (;
[Nexus 7 Original Development] nm8:
I played Asphalt 7 on both stock and the overclocked versions and did not asee any difference. Maybe other gameloft games. I had a bit of fast battery drain so I switch back to No OC kernel.
[Nexus 7 Original Development] t_007_v2:
sorry i forgot to mention it's a setting you have to adjust in the A7 .obb file. see gameloft has the game by default on the lowest graphic setting. that small G logo when the game launches well that logo comes in three sizes represents which setting the game is using on your device.

http://xdaforums.com/showthread.php?t=1878598 here is the thread on the mod.

any other questions PM me.

cheers
[Nexus 7 Original Development] jshashwat93:
So other than asphalt 7 can you give me some examples of gmes or apps? And also what mode do you guys keep your system tuner cpu on? Like there is conservative, interactive or on demand. Which one is the ideal one?

And is that your theme on your sig? Looks kickass
[Nexus 7 Original Development] t_007_v2:
I will pm you shortly since we are off topic.
[Nexus 7 Original Development] jshashwat93:
Ok
[Nexus 7 Original Development] nemesis93:
Motley I think it would be great if you put out a kernel with a GPU 650mhz. I love your kernel the most out of all the options we have because I find that it is the smoothest by far. I only switch to clemsyns kernel for the 650 GPU over clock. Pleaseeee id really appreciate it I love your kernel :D
[Nexus 7 Original Development] t_007_v2:
The clymsen 1.8 / 650 gpu is the motley kernel (;
[Nexus 7 Original Development] Rafase282:
Could you also tell me about that?
[Nexus 7 Original Development] simms22:
truth.

but tweaked by clemsyn :)
[Nexus 7 Original Development] nemesis93:
Really?? Because I get a very noticeable amount of lag when just swiping through home screens on clemsyns kernel. With Motleys I get super buttersmooth performance throughout the os
[Nexus 7 Original Development] Milamber33:
That's a clear indicator that your device can't handle the CPU or GPU clock speed or voltages which are in use. Throw a few benchmarks at it and I bet you'll see worse values in some areas than on Motley's.

Remember, Clemsyn's kernel is ultra-high performance, pushing the device to its limits. Not every device can handle it.
[Nexus 7 Original Development] dislplin01:
As I'm sure it's been said doesn't work with CM10 based Roms
[Nexus 7 Original Development] nemesis93:
Aww that's true. I did get a higher score on clemsyns in nenamark 2. I got an average of about 70-72 fps while on motleys I got an average of 63-65. If the benchmark scores clemsyns higher how come I get some lag while swiping home screens is my question
[Nexus 7 Original Development] Jay Aristide:
Been running it with PA 2.12 since it was released, and ran it with CM10 nightlies before that. Zero issues.
[Nexus 7 Original Development] IRX120:
My I\O scores seem low. Its like this on every kernel if tried.
[Nexus 7 Original Development] DJLamontagneIII:
You can turn off fsync and use a ext4 mount script any your io scores will be much higher... there's many ways to do this check out the op or use jays tweaks in the other dev section
[Nexus 7 Original Development] nemesis93:
When I set my cpu clock on let's say 1.4ghz for example on the CPU frequency reading in the performance setting in cookies and cream ROM it never goes above 1.3?

I tryed using the trinity kernel toolbox and got the same results
[Nexus 7 Original Development] Milamber33:
Nenamark is only a GPU benchmark. Try running AnTuTu, CF-Bench, and Quadrant as well. And look at the score breakdowns, some things will be higher on Clemsyn's, but I bet some things will score much worse.
[Nexus 7 Original Development] B-Man2005:
I also noticed hat there is lag when opening APP drawer with other kernels . With this kernel its perfect ...

Thats strange
[Nexus 7 Original Development] friedsonjm:
I have run a bunch of tests using Vellamo, and strangely, the 'faster' kernals are NOT getting the 'best' overall scores.. Motley 484 is giving me the 'best' results using the Glazed ROM, compared to the 'faster' kernel, and all of the latest Trinity kernels.. I'm also getting fantastic battery life from it.