yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Milamber33:
Again, an indication your device can't handle the higher speeds, at least not at those voltages. Not all devices are created equally.
[Nexus 7 Original Development] khan1989:
Hi, thanks a lot for this kernal. Using stock rom here. Only features in interest to me were the GPU over clock and the ntfs write on USBOTG. GPU I have notices a slight improvement on n6goid, my mario64 does not lag as much now.

Regarding the ntfs rw, I have ntfs ro working with chainfires stickmount, it wasn't mouting properly earlier without your kernal. It now mounts fine, root explorer says it has rw, but I still cannot write, create a new folder or anything. Am i missing something?
[Nexus 7 Original Development] smt8544:
Has development for this kernel halted?
[Nexus 7 Original Development] Jay Aristide:
_motley said a few pages back he'd been pretty busy with real-life stuff. As far as I can see, this kernel is pretty much perfect as it sits. I try new kernels as they come out, and come back to good old _motley's 1.1.1 every time :)
[Nexus 7 Original Development] Metallice:
Yeah. His job has some big software launch he's working on or something. Lol he's actually Steve Ballmer and is busy with windows 8 :).

Its rock solid as it is anyway. Definitely the most stable of the custom kernels. Just works with good performance, GPU choices, and decent battery.
[Nexus 7 Original Development] mrbeardy:
There has been some sort of vsync change in recent cm10 builds which breaks compatibility with aosp. On my nexus S this issue means kernels from last week arent compatible with nightlies from this week. Cant say i know the details, just the side effects!
[Nexus 7 Original Development] hospital349:
Hey folks,

I'm new to this thread, though I've been using 1.1.1 GPU520 for about a week now. I've tried a couple of other kernels just to compare, but nothing else really compares to Motley's Kernel! :good:

Thanks so much for all of your hard work, I can really feel a difference in performance and battery alike.

I've had a slight issue and I was actually wondering if somebody could enlighten me. I'm not sure if it's a bug or just a general flaw that cannot be fixed permanently:

I've tested a few kernel control/voltage control apps over the past few days and they all have the same reoccurring problem, that is; when I apply the settings and commit to 'set on boot', sometimes (even without a restart), the settings will become somewhat 'wiped'/don't stick. I have used the recommended 'System Tuner', along with 'Trickster MOD Kernel Settings' & 'SetCPU'. However, If I force close whichever app I have installed & then select it again, the settings reappear...

For a while, I thought it might have been permissions issues regarding Superuser/SuperSU - but then if it is reoccurring on every app I've tried, then it must be at least partially kernel related, right?

I don't know if there is a permanent solution to this and I'm sure I'm not the only person with this problem. I made a brief search on the thread to find my answer, with no such luck.

I am currently using Paranoid 2.16, if that makes any difference at all. :)

Thanks in advance to anybody willing to assist!
[Nexus 7 Original Development] crg31953:
Just my two cents,

I have been using motley 's 1.1.1 on BAMF Paradigm since it's release with zero issues.

I use System Tuner Pro and am oc at 1.6 max, and 204 min and ondemand with the 520gpu oc version.

I never use set on boot due to issues it can cause.

Maybe try not using set at boot?

Sent from my Rezound using Xparent SkyBlue Tapatalk 2
[Nexus 7 Original Development] Milamber33:
1. Make sure you're only using one of these apps at a time, otherwise they WILL interfere with each other. Uninstall all you're not using for safety.

2. Isn't PA based on CM? Doesn't it have CPU control stuff built in? This could easily also be interfering. Check settings.
[Nexus 7 Original Development] Jay Aristide:
CM's CPU settings don't interfere if you haven't set them to anything. I'm on PA, use system tuner, run this kernel and have no issues
[Nexus 7 Original Development] Milamber33:
And I have Trinity Kernel Toolbox, System Tuner Pro, SetCPU, and CPU Master Free all installed at once, despite my own advice. I know different CPU control apps can be made to not interfere with each other, but when something like this comes up it's always safest to uninstall all but the one thing, and maybe bring the others back later once you have it working right.
[Nexus 7 Original Development] Jay Aristide:
Why on earth do you have all those installed?
[Nexus 7 Original Development] hospital349:
I only have one installed at a time, I've just tried them all out over the past week to see if at least one would treat me well :p

It looks as if the guy above me who mentioned

not

to 'set on boot' actually had a point. I haven't had a problem for a while now, (touch wood). Fingers crossed that's solved it. :thumbup:
[Nexus 7 Original Development] Milamber33:
Trying out different things and not bothering to remove them. :p
[Nexus 7 Original Development] dazbutler1:
Hi,

Hope someone can help. I'm currently running stock ROM with motley kernel. Love this setup but cannot for the life of me write to NTFS USB HDD. I can read no problems but write does not work. Anybody had any luck getting this working. Would greatly appreciate any assistance.
[Nexus 7 Original Development] hospital349:
Hey motley,

Just writing to say thanks for creating such a fantastic kernel.

I have tried every kernel available for the N7 and yours appears to be 'The One'. I always return to it, even after flashing alternatives. :D

My current set-up is (for those who're interested) -

motley GPU520 build 1.1.1

PARANOIDANDROID 2.179

Apex Launcher

Trickster MOD

102mhz - 1600mhz

on demand + deadline

-100mV per frequency step; undervolted

powersave_bias: 8

sampling_down_factor: 4

sampling_rate: 20000

up_threshold: 98

FSYNC: off

Smart Dimmer: off

WIFI High Performance: off

GPU 3D Scaling: on

zRam: 18%

Allow purging of assets: on

Kernel samepage merging: on

Surface improvement: Fix colour banding and blur effect

My N7 is BUTTERY SMOOTH, with no lag, no reboots/SOD's. I get around 8 hours of on_screen_time and 2 days on_battery_time with moderate-high usage. I cannot fault the kernel at all.

For anybody considering flashing, don't consider, just do! You definitely won't be disappointed. :good:
[Nexus 7 Original Development] clusterchuck:
I tried to install this over the new 4.1.2 update and it wont go past the load screen now :(
[Nexus 7 Original Development] Draje0:
Also fails when flashing over the CM10 nightly from 2012-10-09.
[Nexus 7 Original Development] IRX120:
Use grouper_defconfig

Or goto the kernel directory, and run make mrproper

Sent from my 1.8GHz Linaro optimized Nexus 7
[Nexus 7 Original Development] Facegarden:
Hmm, okay, i updated my build script to run make mrproper by changing the last lines to this:

sudo make clean
make mrproper
make grouper_defconfig
make

make mrproper did seem to do something but I'm getting the same build error.

Also I'm on Ubuntu 10.4 32 bit, if any of that matters.
[Nexus 7 Original Development] IRX120:
Check you have all the correct build tools and delete and redownload the kernel source.
[Nexus 7 Original Development] Facegarden:
so I see several folders in the toolchain that are called "arm-linux-androideabi" and they seem to contain duplicates of the stuff in the folders called "arm-eabi"

so far I've been using the second one in my PATH and variables. should I use the first one? what is the difference?

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

Okay, thanks for the reply!

I am using this toolchain:

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

Which was linked to in a previous post (but that was two months ago, not sure if that's changed). (EDIT: I see the source hasn't been modified in two months, so I'm guessing the toolchain is fine?)

I'll re-download the source also, and try my build script with arm-linux-androideabi instead of the arm-eabi too. (EDIT: this produced the same error)
[Nexus 7 Original Development] Facegarden:
Okay! Re-downloaded the source, then made a copy so I'll always have an untouched version to go back to.

Dropped in my build script, ran it, aaaaaand same error!

So either my build script is wrong, my toolchain is hosed (I'll try downloading that again but I am beginning to think that isn't the issue), or... I don't know.

All I need on the machine is the toolchain and the kernel code from the git repository, right? I do also have the grouper code from:

https://android.googlesource.com/device/asus/grouper/

but it looks like I don't need to do anything with that in this case?

Are there any build instructions for this that I'm missing? It seems like its a relatively simple procedure but clearly I'm doing something wrong...

Thanks guys.
[Nexus 7 Original Development] IRX120:
Try a fresh copy of the AOSP sources, that'll get everything fresh,

Sent from my 1.8GHz Linaro optimized Nexus 7
[Nexus 7 Original Development] Facegarden:
Well I originally built it using Google's instructions and I was able to get it to build, but I had no idea how to package the resulting zImage so that it would load onto the phone.

I spent all day yesterday trying to figure that out. I used several different "kitchen" scripts to unpackage a working boot.img, replace the zImage, and then repackage it, but none of those would boot. I tried unzipping one of the zips from this thread, replacing the zImage, and loading that with clockworkmod, but it said bad zip. I tried that with and without signing the zip, and it still said bad zip. I tried the sample AnyKernel from the original github page with my zImage and it said bad zip. I tried decompiling several different boot.img files to replace with my zImage and that still wouldn't work.

So then I decided it would be better to just find a kernel that someone has already hacked and put on gitgub, so if I have a problem, there will be people who have done the exact same thing to provide help.

So I guess the real question is, am I missing something?

my understanding is that the complete instructions for this are as such:

Set up a new Ubuntu 10.04 32 bit virtual machine.

Install git.

set up a folder in the home directory called "android" or whatever you want.

cd to that directory and git clone the github repository for this kernel.

download and extract the toolchain and put that folder in that directory.

make a build script (optional) like the one I posted on the previous page and run it from the android folder.

take the resulting zImage file, unzip one of the zips provided at the beginning of this thread, replace the zImage file, re-zip everything, and then load it onto the device and install via CWM (does it need to be signed?)

But that's it, right?

if those are the only steps that are required, then the most probable thing is that my build script is wrong. Which wouldn't be surprising since I kind of guessed on the paths for that, and I still haven't been able to figure out if I'm supposed to use the "arm-eabi" folders or the "arm-linux-androideabi" folders.

Does someone have a working build script? And could that perhaps just be added to the repository?
[Nexus 7 Original Development] Juzman:
Hey guys,

Was wondering how much people have undervolted the CPU by? I currently have each CPU step -50mv with system tuner and no SOD yet. Just trying to squeeze as much battery as possible. :)

Also set WiFi scan interval to 360 instead of 15.
[Nexus 7 Original Development] Facegarden:
So it seems I had an error in my build script. I found some other posts about using the linaro toolchain and was able to make some changes to my script to get everything building. Now, however, I get an error close to the end. Here is my build script:

#!/bin/bash
# Build Grouper Kernel
export TOOLCHAIN_DIR=/home/taylor/android/android-toolchain-eabi/
export PATH=$TOOLCHAIN_DIR/bin:$PATH
export CCOMPILER="$TOOLCHAIN_DIR/bin/arm-eabi-"
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
cd /home/taylor/android/Kernel-Nexus7/
#echo $PATH; read -n1
sudo make clean
make mrproper
make grouper_defconfig
make

and here is the last portion of the ouput from make:

arch/arm/boot/compressed/head.S:956: Warning: (null)
arch/arm/boot/compressed/head.S:988: Warning: (null)
arch/arm/boot/compressed/head.S:990: Warning: (null)
arch/arm/boot/compressed/head.S:991: Warning: (null)
arch/arm/boot/compressed/head.S:998: Warning: (null)
arch/arm/boot/compressed/head.S:1030: Warning: (null)
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/piggy.gzip.o
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
arm-eabi-ld: error: arch/arm/boot/compressed/piggy.gzip.o: unknown CPU architecture
arm-eabi-ld: error: arch/arm/boot/compressed/lib1funcs.o: unknown CPU architecture
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2

I'm googling around now, but nothing has really jumped out at met yet. Anybody know whats going on?

I'd love to see someone's working build script here...

Thanks.
[Nexus 7 Original Development] Metallice:
First of all, how and why did this thread turn into a help thread for kernel compiling haha?

And I can't tell you what's up with your build script. It looks fine to me. But then again... I'm lazy and just modify the root directory Makefile itself with "arm" and my toolchain path manually entered in. I save the relevant defconfig to .config in the root directory and then type "make". And that's it. To make changes to config just type "make menuconfig".

By the way if anyone is interested in Motley's kernels for 4.1.2 and beyond a new thread will be popping up in Android (non-original) Development in a day or two that you'll like :D... since it appears motley is indisposed for the time being :(
[Nexus 7 Original Development] Juzman:
I'm currently using this kernel on 4.1.2. o_O Why a new thread?
[Nexus 7 Original Development] DJLamontagneIII:
Sounds good :D
[Nexus 7 Original Development] Jay Aristide:
Running the pre-release of this right now with PA2.2 and my Buttery Tweaks and it's dead sexy.. Which reminds me, pm incoming Metallice.. Something I noticed while setting up my tweaks.

:good:
[Nexus 7 Original Development] iamelton:
this would be excellent!

was checking this thread on daily basis and also was wondering why there was no mentioning of this kernel for 4.1.2 (yet)..

and then was afraid to ask as this thread seemed to be switching direction to a compiling and debugging one.. :p
[Nexus 7 Original Development] Metallice:
You're running a 4.1.1 kernel and ramdisk on a 4.1.2 ROM. I don't think I should have to explain why that's bad.
[Nexus 7 Original Development] Juzman:
Ah, this is true. Guess I will swap back to stock CM10 for now then. :)
[Nexus 7 Original Development] BillGoss:
I think you do need to explain, especially since it works.

Sent from my Nexus 7
[Nexus 7 Original Development] smt8544:
Where did you obtain the pre-release?
[Nexus 7 Original Development] Jay Aristide:
I'm testing the early builds before they go public :) Don't fret, won't be long...
[Nexus 7 Original Development] Juzman:
That's what I was thinking too, I thought if didn't match, it wouldn't boot.

Sent from my GT-I9100T running Resurrection Remix
[Nexus 7 Original Development] tobitronics:
So I cant use the current motley for PA 2.2?

Beamed from my Google Galaxy Nexus
[Nexus 7 Original Development] MetalPainis:
Correct, wait for the update ;)

sent from a Nexus 7 via Tapatalk
[Nexus 7 Original Development] BillGoss:
Try it. I'm running motley kernel with CM10 (4.1.2) and everything works ok so far.

Sent from my Nexus 7
[Nexus 7 Original Development] godelsproof:
I'm using motley kernel with PA2.2,works well ;)
[Nexus 7 Original Development] Metallice:
A simple "would you mind elaborating?" would have worked, but fine, if you're going to be obnoxious I can return the favor.

Oh wow you're completely right. How could I have not noticed? I won't bother keeping this kernel current then.

I urge you to keep using this kernel on a ROM with an incomplete 4.1.2 like PA or CM that's missing key parts of 4.1.2 like the ramdisk that fixes many storage bugs or use it on a complete 4.1.2 build by forcibly downgrading the boot.img to 4.1.1 by one dev, ripping it apart, replacing it with the 4.1.1 kernel of another dev, and running it on a 4.1.2 ROM.

...Or, as you said, it works perfectly with 4.1.2.
[Nexus 7 Original Development] tobitronics:
So are you saying that PA 2.2 is basically android 4.1.1 because it misses the key fixes?

Beamed from my Google Galaxy Nexus
[Nexus 7 Original Development] Jay Aristide:
No, what he's saying is cm borked the ramdisk and it doesn't incorporate a lot of important changes new to 4.1.2
[Nexus 7 Original Development] tobitronics:
You mean the powerchip changes? Will it influence the user experience compared to stock 4.1.2 (not looking at PA features)?

Beamed from my Paranoid Google Nexus 7
[Nexus 7 Original Development] Jay Aristide:
No, I mean there are features utilized by the 4.1.2 kernel and corresponding ramdisk that aren't present in the 4.1.1 kernel and ramdisk, like the specification of when to and not to use the discard option when mounting /data and /cache

There's more, but that's a pretty important one. Discovered it last night. CM needs to address it

Edit: The power chip changes would be another big one potentially rendering your device useless
[Nexus 7 Original Development] sizanx:
I have PA 2.2 now with it's kernel (cms?), so because CM fragged up the kernel and system doesn't match? Or the main point is to wait for CM to update, then PA to update and then use motley's not yet released kernel for 4.1.2?

Btw your Buttery Goodness, will there be a new method for 4.1.2? (haven't tried yet because of yeah, no motley 4.1.2)
[Nexus 7 Original Development] smt8544:
The buttery goodness tweaks are not motley specific, they can be used with other kernels. Maybe try bricked v.55 which is supposed to be 4.1.2 based.
[Nexus 7 Original Development] Jay Aristide:
Fair enough. I honestly don't know what the differences are other than I know the cm10 ramdisk (not kernel) for 4.1.2 doesn't mount /data and /cache with discard as it should, I had to add it into my init script as a temporary fix

Yes, there will be a set of all new tutorials and a couple of weeks later I'll stop officially supporting my 4.1.1 threads (as there's no reason not to update). That's not to say, though, that I won't still answer questions and help people on them

And, it'll be worth the wait, man. The guy maintaining this fork is all pro :)
[Nexus 7 Original Development] tobitronics:
How is the testing of the pre-release going jay?

Beamed from my Paranoid Google Nexus 7
[Nexus 7 Original Development] rootbrain:
Everyone needs to calm down a bit, LOL. While this "works" those of us "vultures" that live off of the hard work of devs who ask little more than thanks and possible donation (that rarely comes) should defer to their expertise and advice.

I also use the Motley 4.1.1 kernal after the update to 4.1.2 on stock ROM, rooted. Post from Jay on his "buttery goodness" said not to flash it, but it was too late, I already had. And yes, it "works" and when I mentioned to Jay, his comment was simply that just because I didn't see any issues and the thing booted, didn't mean it "works". And I believe him, I'm not getting the benefits from motley that I was getting, because things need to be changed. I defer to him, and wait for this update so I can get the benefits of 4.1.2 in a new and improved motley kernel.

Bill, as you can tell from the response, it's best not to prod a dev, anymore than you would poke a pit bull.. :laugh:
[Nexus 7 Original Development] Metallice:
I'm having issues with crashing during games... trying to figure out if it is just my device.
[Nexus 7 Original Development] Jay Aristide:
Like which games? My brother says horn is giving him all kinds of trouble. People on the PA thread are saying Horn sucks for them, too

I'll load a few games up and see what's what
[Nexus 7 Original Development] demandarin:
Did I miss some news? Where's Motley at?
[Nexus 7 Original Development] Metallice:
Death dome keeps locking up and hard resetting for me.
[Nexus 7 Original Development] Jay Aristide:
Don't have that..

So far, I've played a couple levels of Horn, a level of TDKR, a round of Hot Pursuit, some OaC, inning of madden, loaded a mine craft world and walked around, galaxy on fire 2 did a cleanup mission, dead space ran around for a few

Everything is running great. TDKR is actually improved considerably.

I'll see how much Death Dome is
[Nexus 7 Original Development] Metallice:
Alright downloads are available in the Nexus 7 Developement section or from the link below.

http://xdaforums.com/showthread.php?t=1937146
[Nexus 7 Original Development] BillGoss:
Well, I've found one problem using motley (4.1.1) on CM10 (4.1.2): using Swype, traces get broken up, as though the touch screen was stuttering. Running pure CM10, Swype works flawlessly.

However, without motley, Apex has lags on screen rotations, so...

@metallice: looking forward to your 4.1.2 kernel.

Sent from my Nexus 7
[Nexus 7 Original Development] Jay Aristide:
It's out!
[Nexus 7 Original Development] tobitronics:
Where can I find it? Good job!

Beamed from my Paranoid Google Nexus 7
[Nexus 7 Original Development] Metallice:
Look back exactly 3 posts from yours.

---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------

Ehh. whatever. I'll just quote myself.

4.1.2 version available above.
[Nexus 7 Original Development] notko:
This is the first flashed kernel on my Nexus 7 and it's awesome.

Better scores in benchmark...will test it for few days on 1.4Ghz and 1.5Ghz and then finally to 1.6Ghz.
[Nexus 7 Original Development] kzakhar:
This information is very important, same as benchmark scores!

Oh wait...
[Nexus 7 Original Development] notko:
Running Android version 4.1.1 Cookies&Cream 1.2.1 ROM on 1.6Ghz kernel version 3.1.10 motley

NenaMark

AnTuTu

Quadrant
[Nexus 7 Original Development] jhondidfool:
Whenever I flash this Kernel using the latest SmoothROM I get locked in a permanent boot screen. :(
[Nexus 7 Original Development] N@th_OC:
Because the last SmoothROM is 4.1.2.

Besides this kernel that is still in 4.1.1. You can't use this kernel with this rom
[Nexus 7 Original Development] jhondidfool:
Dang! When will I learn to read!?
[Nexus 7 Original Development] CharliesTheMan:
In the android development section, there's a new version based in _Motley's kernel but ported to work on the new firmware.
[Nexus 7 Original Development] _motley:
New kernel for 4.2 build 233 posted! (finally)

Hi guys, I hope everyone is doing well. Had some other life stuff to get done and now I finally have some time away from work and family to catch up the kernel. Thanks to metallice, clemsyn and the rest of you that provided support and being around when I couldn't be.

I have posted a 484 MHz GPU build for with 4.2 support on the first post. It has been rock solid for me thus far. It should also support 3G models, but I have no way to test that myslef. If this goes well and folks are still interested in this kernel I will post a 446 and 520 GPU builds tomorrow. I also just posted a Nexus 4 kernel over in that forum as well in case anyone is interested. It feels good to get back to fooling around with Android, my mistress! Looks like some of the other kernel devs have been making good progress on the platform.

Cheers,

motley
[Nexus 7 Original Development] DJLamontagneIII:
Welcome back:D
[Nexus 7 Original Development] _motley:
Thanks man! Glad to see most of the familiar faces, um I mean avatars and screen names around here.