yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] denzel09:
You are drunk?:confused:
[Nexus 7 Original Development] TheAtheistReverend:
In system tuner, do I need to press start to apply changes to clock and voltage values? I'm taking about the little button in the upper right hand corner that turns red in the middle when you click it.
[Nexus 7 Original Development] luckylui:
Using this kernel on my N7 and also N4. Thank you greatly sir!! Best stock steroid kernel in town. :)
[Nexus 7 Original Development] TDO:
This kernel is a beast.

Unbelievable performance in real world apps. (equaling the performance of other kernels with GPU clocked at 600!)

Thanks for this great work.

The only thing missing is a compiled version with higher GPU clock.
[Nexus 7 Original Development] Mountainjew:
I'd like to use this kernel, as i used it on 4.1 without problems.

Though whenever i use it, my N7 becomes possessed. It starts randomly clicking everything on the screen and i have to fight it to be able to reboot.

Dunno if anybody else had this problem, didn't read very far back. But the kernel is totally unusable to me.
[Nexus 7 Original Development] popdog123:
This happened to me too on 4.2 using build #233. Almost crapped my pants thinking it was a hardware problem...
[Nexus 7 Original Development] _motley:
Thanks, I am researching more into this. Couple Q's for you:

Which ROM?

Does this happen immediately after you boot up, or does it take some time for it to start happening?

Are you in one particular app for awhile when it starts happening, or doesn't it matter?

Do you change anything from the defaults after startup? (OC CPU, fsync off etc.)

Anything else interesting that might help me understand where the problem lies?

Anybody seeing this issue with the 4.1 kernel, or is it just the 4.2 kernel?
[Nexus 7 Original Development] popdog123:
Stock 4.2.1

At first it took some time before I noticed it. Then, even after a few reboots, it would happen right after booting

Apps don't matter

I increased the lower limit of OC to 300 I think. I thought that could be it so I switched everything back to stock and removed the set on boot option. After reboot the problem was still there

I noticed the touchscreen would have trouble when touching near the edges of the screen. Most notably if you want to input 1 on the keyboard for example or trying to pull the notification drawer from the top.

I hope this helps...
[Nexus 7 Original Development] PhantomApollyon:
motley-

Any comment on the thing about custom kernels at the bottom of this post from CM 10.1 official?

"4. Third party kernels are not supported by CM, I have had no luck with any of the current kernels on these nightly builds, your mileage may vary."
[Nexus 7 Original Development] Mountainjew:
Paranoid Android, beta 7 & 8.

Immediately after i boot up.

No overclocking, though i have applied a few tweaks through Pimp My Rom. And, doh! I forgot i even had that on there. Downloaded the rescue package to undo the changes made and the kernel is fine now. No strange behaviour so far.

I'll keep testing to make sure.

Edit: Ok, still acting possessed. Only it took a few minutes for it to start. Seems like maybe the touch sensitivity is sky high, since it reacts to waving my hand over the device. So that lead me to think that maybe the screen was dirty or something, but i gave it a good clean and it's still acting the same. Dunno if it's relevant, but most of the random screen touches seem to happen around the middle of the screen (portrait mode).
[Nexus 7 Original Development] _motley:
Thanks for the feedback guys. Please see the OP for the notes on build 244 that I just posted. It would be awesome if you can test and see if it helps alleviate the problems you reported. Also, have you recently run other kernels that OC the GPU? If so, let me know which one and what speed you were stable at. IMO, this is not really necessary, but I know folks like to push their devices and some claim it helps with gaming etc. Unfortunately, it does so at the price of an overheated GPU and it repeated use may be catching up with some of us :(

Hi, this kernel uses the AnyKernel install method. I would think that it would work fine on CM 10.1. I looked at their 10.1 kernel source and it looks like the stock kernel to me. Kernels that have you flash the full boot.img (look inside the zip), won't likely work on CM 10.1 unless specifically specified.
[Nexus 7 Original Development] Mountainjew:
Yeah i've been switching back and forth from Franco & Bricked 0.55, both with 484Mhz OC on the GPU.

Edit: Just flashed 244 and the issue is completely gone now. Strange that i don't have any issues on other kernels with a gpu overclock. Then again, i don't know much about the workings of kernels :)

Oh and 244 is buttery smooth too, no noticeable lag on animations or scrolling issues :)
[Nexus 7 Original Development] PhantomApollyon:
Gotcha, I'll give it a try later today and post up results

EDIT: kernel installed fine and I'm not having any issues with the newest version + CM 10.1 Official.
[Nexus 7 Original Development] comfuzio:
Hello guys, since today i own a Nexus 7 too :) I have rooted it etc but i am thinking of changing the kernel and use this kernel.

Since i am new to the Nexus corner i would like to know if this kernel can work with stock rom 4.2.1 JOP40D (for the moment i don't see any reason to change it). I am very very sorry if this has been answered before and thanks for any kind replies.
[Nexus 7 Original Development] TDO:
Running build #233 for days without problems.

Unfortunately you decreased the already extrem low overclocking of the GPU in the new build. :(

In other kernels the GPU run's stable at 700 but you don't get much performance increase as the memory bandwith limits it.

It would be great if you could provide again a 484 GPU (better 520) build.
[Nexus 7 Original Development] _motley:
Great to hear, thanks for the quick feedback!

Good deal, glad it is working well on CM 10.1.

Yes, it will work great with the 4.2.1 stock ROM. This is what I am currently running as well.

No prob, I will soon provide other GPU builds as I did before for 484 and 520. I just wanted to see if this fixed the problem before over-complicating things. Personally, I think 700MHz is ridiculous...that is 284MHz over stock (68%). 484MHz (16%) and 520MHz (25%) are reasonable increases if you are OK with the risks and extra heat generated. What is weird is that I used to run 484MHz all the time without issues, but now I have also seen the reported touchscreen issue. I'll be running the 446MHz GPU (7% over) from now on since it doesn't generate the extra heat and it makes it generally better for my daily use. I would think this would apply to most folks as well unless you are playing games that don't work with stock or the 446MHz build.
[Nexus 7 Original Development] O2Blevel:
I've been running build 244 for a while now and no problems to report. I have noticed that with the video portion of the quadrant benchmark, the fps is quite a bit lower than the 233 build I tried last week. Also, the video appears slow and choppy, particularly the portion in the hallway leading to the chamber. One other observation is the AnTuTu GPU score is about 15% lower than the stock kernel. I'm running the stock ROM.

Feels good to be back on the _motley kernel. Thanks for all your hard work.
[Nexus 7 Original Development] killa12222:
Updated to #244 from #233 and the touch problems were gone! Benchmarks a little lower than before but so far it works great! Thanks
[Nexus 7 Original Development] TDO:
AnTuTu GPU is not really reliable.

But for me the values are as to be expected.

stock 233 244
3D Rating (AnTutu) onscreen 3042, 10.5 afps 3200, 11.3 afps 3109, 10.7 afps
3D Rating (AnTutu) offscreen 1298, 3.4 afps 1325, 3.4 afps 1378, 3.6 afps
[Nexus 7 Original Development] _motley:
Thanks for the feedback. TDO's last scores seem right to me as well. They should fair better than stock. Here is my last Antutu run on build 244 (1.6 CPU/446 GPU).
[Nexus 7 Original Development] comfuzio:
Great! Thanks for the reply I just flashed it! It seems to run very good! Later i will test it further!
[Nexus 7 Original Development] Roll3r:
Haven't been on XDA in a bit. Good to see you back _motley! Doing a fresh install of 4.2.1 stock to wipe out any leftovers from the 10 kernels I've tried since you went on hiatus.
[Nexus 7 Original Development] Jay Aristide:
Haven't found a single game that doesn't perform perfectly @446, and 416 is *more*than*adequate* for everything but the most intensive Gameloft games. Overclockong the gpu is more of a placebo than anything. The same people put cold air intakes on their cars then never take them over 60mph but swear they can tell a difference.
[Nexus 7 Original Development] xfrancis14:
Idkk if this is the right place to post this but has anyone compared this kernel to mkernel a24? If so which one is better and battery and performance?
[Nexus 7 Original Development] denzel09:
Better this for me then a24 atm

Sent from my Asus Nexus 7 3g 32GB
[Nexus 7 Original Development] xfrancis14:
Does it let you mount a usb without stickmount?
[Nexus 7 Original Development] Jay Aristide:
That's rom dependant, not kernel dependant. The kernel enables OTG, then either your rom or stickmount actually does the mounting/unmounting.
[Nexus 7 Original Development] xfrancis14:
Well I have pa so ik I can do it with that Rom but like before a23 or before wouldn't auto mount otg
[Nexus 7 Original Development] Rafase282:
Motley, could this be implemented? http://xdaforums.com/showpost.php?p=34897653&postcount=244
[Nexus 7 Original Development] Jay Aristide:
Aye. It was accidentally left off in a23, but was enabled again in a24.

Both of these kernels are magnificent, and M-Kernel was built off _motley's kernel to begin with. _motley was gone for quite an extended period of time, so M-Kernel developed into it's own creature. Personally, I'm running this kernel for now, because it doesn't have the odd adobe flash issues M-Kernel does, but Metallice does amazing work, and his kernel is top-notch, as well
[Nexus 7 Original Development] xfrancis14:
Mkernel is amazing and I love it but I'm curious about this kernel, do you think it has better battery life? And how's the performance?
[Nexus 7 Original Development] Jay Aristide:
I find them to be nearly identical in both battery life and performance.
[Nexus 7 Original Development] opz187:
244 is super solid for me on cm10.1
[Nexus 7 Original Development] Moscow Desire:
NOTICE

Ok, here's a notice to you people who seem to think they can demand things.

Repeatedly posting about wanting more CPU and GPU OC, especially in all kernel threads, is considered Spamming. Also, you must understand, kernel development can sometimes be a slow process as developers look for stability first, then performance. So demanding such things all the time is only going to stifle the development process. If you're not satisfied, then I suggest you install Linux and start developing your own kernels.

Also, comparing one dev's kernel to another dev's kernel (in the kernel thread) is considered a "cold slap in the face" to both devs, and can eventually result in no more further development. If you have to compare, then take it to the General Forum!

Thread is cleaned of all the recent arguing/spamming/flaming and other off-topic banter.

MD
[Nexus 7 Original Development] senel:
+1,pleeeease :)
[Nexus 7 Original Development] weedy2887:
I'm running build #232 on my WiFi 4.1.2, I can't find any mention of init.d or run-parts in any of the /init.* files.

Are you sure you included it?
[Nexus 7 Original Development] _motley:
Sure, I have no problem adding this into the next release if it has no ill effects. I doubt there will be.

The install zip employs the "Anykernel" method, so it doesn't' alter your ramdisk in any way. It simply tucks in the kernel binary and leaves the rest intact. So, init.d support will be dependent upon your ROM. The kernel wont' have any issues as long as the ROM supports it.
[Nexus 7 Original Development] _motley:
Hey, just wanted you, Tasssadar and the others know that I posted a test kernel (build 246) for you in the MultiROM thread. Let me know how it goes! This project looks very interesting. I really want Linux on my Transformer Prime with the dock+keyboard. Not sure if the guy working on that has anything yet, but he has been busy. N7 is also cool though!:good:
[Nexus 7 Original Development] temasek:
Hi motley,

Awesome kernel! Works great on my self compiled cm10.1.

Kudos to u. :)
[Nexus 7 Original Development] porkovich:
Hey all, i have one question. I have the feeling that changing voltage of the CPU does not apply somehow. I have tired SystemTuner, Faux123 and TricksterMod. Now i am on TricksterMod and i have lowered the voltage agressivelly low , 1300@ 975 ...... 520@ 750. And somehow it's stable. I cannot find a software that shows actual voltage (realtime) .... and i cannot find a real increase in battery time, considering that default voltage for 1300mhz is 1175 , lowering it with 200mv must boost the battery alot.

What do you think ? is there a way to see actuall readings ? or it's just me waiting for a miracle :D
[Nexus 7 Original Development] _motley:
Hi, the only app I test with is System Tuner. Some others won't work properly, but I can't say for sure which ones will and which ones won't. On System Tuner, make sure you aren't setting on boot and then gradually lower your voltage for your highest freq. When you get too low, the tab should freeze and you will need to reboot. This will prove to you whether or not it is working properly. As far as the real readings, I check the voltage table is sysfs to make sure it is being written to. Root will be required of course, so make sure you are using the latest version of SuperSU and the su binary.
[Nexus 7 Original Development] bonzer2u:
Works like a champ although GPU freq doesnt seem to be exposed in trickster, is this normal? or just use system tuner instead??

Thx again.....
[Nexus 7 Original Development] denzel09:
It s normal atm

Sent from my Asus Nexus 7 3g 32GB
[Nexus 7 Original Development] Notarzt23:
I really like the fluidity of this kernel but get some sound glitches here and there. Is that a common issue? If you want a logcat, i could try to reproduce the glitches.

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Nexus 7 Original Development] bonzer2u:
Hmmmmm observations:

runs on my stock 4.2.1 without issue, however random freezes running ubuntu 13.04, switch to Tass's modified stock 4.2 kernel and no lock ups. FYI ran Antutu on both modified kernels at default settings and got 12,990 with stock and 13,509 with motley.

Love the performance but had to restore back to stock 4.2 for stability in ubuntu
[Nexus 7 Original Development] _motley:
Not that I am aware of. Please list the environment and how it can be duplicated.

ROM

kernel version (assuming you used the newest build from OP)

Apps or activities that cause said glitches, or better yet a website, video link, mp3 etc.

After it happens, grab the output of dmesg (kernel log, not logcat)

Thanks for the feedback, but I am not yet able to interpret what it means quite yet. I need to read up in that thread to better understand how everything is working. Correct me if I am wrong...after my Android kernel boots, it then starts the other kernel via kexec and then goes away (its memory is overtaken etc.). At this point, it is the kexec Linux ARM kernel that is running Ubuntu. Rafase282 reported that it was working great for him in the MultiROM thread. That was an early reported after I posted the kernel in the thread. It would be good if you guys can compare notes to see if you are having the same issues or whether it could be something else.
[Nexus 7 Original Development] Tasssadar:
I believe that this has nothing to do with your kernel, because, as you say, it just runs the Ubuntu kernel, it is no longer active when Ubuntu is booted.

Please note that Ubuntu is like halfway through the developement cycle now - it is not stable yet, it is "beta" at best. But they are working on it, one of the goals of 13.04 is to bring better user experience to portable devices like Nexus 7.
[Nexus 7 Original Development] _motley:
Thanks for your input Tasssadar. This is such a cool project, maybe I'll have some extra time to play around with it sometime soon:fingers-crossed:
[Nexus 7 Original Development] bonzer2u:
Sorry for the confusion, I recently applied 13.04 updates via the 'ppa:ubuntu-nexus7/ppa', restored your 246 and haven't noticed the issue since.
[Nexus 7 Original Development] _motley:
Good deal, I like it when there is a happy ending for all:victory: Thanks for sharing the solution.
[Nexus 7 Original Development] tobitronics:
Motley you are back! Are you as stable as it used to be on 4.1?
[Nexus 7 Original Development] _motley:
Hi, it's good to be back! Yes, I think things are now nice and stable on 4.2. I have been running the latest build on 4.2.1 and haven't had any issues.

Battery life has been great. Others have reported they have been running well on CM 10.1 and some other 4.2 ROMs. Let me know how it goes if you give the new version a spin. More feedback is always appreciated.
[Nexus 7 Original Development] dbrickg:
I'd been running your kernel 232 on cm10 ever since I saw your post and it worked without a glitch. Just a couple of days ago I switched to cm10.1 with kernel 233, and it's working excellently. In both cases I was getting quadrant standard scores around 6000 after setting cpu to max 1500, undervolting to 700mV at 520MHz and 1100mV at 1.5GHz (and likewise undervolted by 100mV for each Hz level), remounting data noauto_da_alloc, and turning off fsync. I also set up 500MB of swap, though I imagine that doesn't affect the quadrant score.
[Nexus 7 Original Development] currydude:
works perfectly on cm10.1 build 20121023
[Nexus 7 Original Development] ArcticFish:
Hey everything is running good with pa beta 9 and xLoud/beats. The battery life is also really long so +1

Sent from my 4.2.1 xLoud Paranoid Grouper with Motley Kernel
[Nexus 7 Original Development] PhantomApollyon:
Everything is running awesome on CM10.1 with 244 installed, I frequently do the nightly update and reflash your kernel right after that goes through to get back to the improved battery life/performance :good: Looking forward to any future improvements you may make but runs awesome as is!
[Nexus 7 Original Development] tobitronics:
This is the kernel I loved and had to miss for quite some time... Tried out all the other options, but motley kicks all their asses at once! My nexus loves it, I love it, who doesn't? A pity that you don't develop for GNex :P Anyway, is it still useful to apply Jay's recipe for smoothness?
[Nexus 7 Original Development] demandarin:
This kernel running very well for me. I'm using latest motley 4.2 build 246 with Team eOS4 latest nightly 247. Battery life has greatly improved. Battery drains alot slower now. Didn't change anything. Just flashed kernel as is.

Great work Motley ;)
[Nexus 7 Original Development] Jay Aristide:
My script disables fsync, [optionally] enables zRAM, and remounts /data and /cache with noauto_da_alloc, so yeah: it's still useful to use my script (with or without zRAM) :)

---------- Post added at 09:05 PM ---------- Previous post was at 08:47 PM ----------

ParanoidAndroid 2.99beta9

This kernel (#244)

1.6GHz OC, performance/deadline, -75mV undervolt

Jay's Recipe for Buttery Goodness (no zRAM)
[Nexus 7 Original Development] CharliesTheMan:
Just wanted to stop and say hello guys, I've been quite busy and not stalking the 7 sections like usual.

I usually use the items in Jay's script with Motley's kernel, in fact most of that stuff, like disabling fsync and some init d stuff I use, Motley taught me back in the day and now I use it and end up passing the info on to kernel devs that are on different devices because I know the things that Jay uses are so useful and full of benefits.

ZRam is the only thing I don't know well enough to give advice on, but since Jay said it can go either way, I agree with his response fully :)

*waves to motley and Jay*
[Nexus 7 Original Development] Jay Aristide:
Sure does, runnin' it right now :)

Yeah, it works just fine with 4.2, just make sure you've got a working busybox (pa comes with a working busybox)

Edit: Updated the OP of my Buttery Goodness thread to clarify compatibility :)
[Nexus 7 Original Development] JohnCorleone:
Where does one find your script? or is it in your sig and I just can't see it from the app. I would like to give that a shot
[Nexus 7 Original Development] Milamber33:
In his sig. Here's the link: http://xdaforums.com/showthread.php?t=1946347
[Nexus 7 Original Development] jeff.murillo:
how can I overclock the gpu in this kernel?
[Nexus 7 Original Development] TDO:
That's not possible.

Hopefully motley will provide again different overclocked versions of his kernel (I am looking forward to see again a 520 one)
[Nexus 7 Original Development] FReaKRaNT:
Why can't you use trickster mod to OC this kernel?

Cheers, FReaKRaNT
[Nexus 7 Original Development] Jay Aristide:
Because it isn't built with a user-adjustable GPU.
[Nexus 7 Original Development] sNoxious:
What version of this works on PA Beta 9? 244 or 246?
[Nexus 7 Original Development] mulletcutter:
I'm using 246 and running great.
[Nexus 7 Original Development] DeFcOn:
If you will read carefully then you will see that there is no much difference, only the MultiROM support added in 246 :p
[Nexus 7 Original Development] yukkio:
This kernel has the same problem with Adobe flash in the stock browser, Firefox not

Br
[Nexus 7 Original Development] snarlytaz:
Stock browser meaning Chrome or the old Google browser? I assume Google because Chrome doesn't support flash? But again some kernels do cause flash to render images as corrupt, such as M-Kernel but I hadn't found that true for this one. I will go back and try it later.
[Nexus 7 Original Development] TDO:
In the m_kernel flash is not working correctly.

Regardless which browser.

So there is some unknown serious bug in the kernel which can effect all kinds of apps (not only flash).

In motleys kernel everything is working as it should.
[Nexus 7 Original Development] yukkio:
I mean stock aosp browser, chrome doesn't support flash.
[Nexus 7 Original Development] NicoGa:
why would they be "unknown serious bug" in M Kernel, just because flash is not working ... it is the same in several kernel and beside flash M Kernel works perfectly!

Envoyé depuis mon Nexus 7
[Nexus 7 Original Development] TDO:
If some change in the kernel leads to an error I call it a bug (or how would you call it?)

And as this bug regards a widely spread standard app it is to regard it as seriously.

And there is no way of knowing which apps will also be effected by this bug.

Or can you name them and the source of this bug?
[Nexus 7 Original Development] abzza:
Hi

have been running CM10.1 with motley's kernel for couple of days and it is running great.

The touchscreen has improved but the issue is still there but not that noticeable as on stock.

thanks for that and keep up the great work :good:
[Nexus 7 Original Development] icytrey:
+1
[Nexus 7 Original Development] NicoGa:
from what I know, flash is not anymore a widely standard app on android! In addition, coming from Linux I have to underline that new nvidia graphic driver often break flash ... so flash problems might be related to some patch from nvidia that have been included by some of the kernel devs but fortunately not y motley ... anyway I will not argue more as it is off topic

Envoyé depuis mon Nexus 7
[Nexus 7 Original Development] jamesst20:
I'm surprise to see that newest build #244 isn't sluggish anymore. I don't know what you have done but good job
[Nexus 7 Original Development] temasek:
Good job cannot well describe motley work here. This kernel is a beast. Been using this kernel since I use it on my cm10.1.

I like motley using anykernel packaging.

Great job. :)