yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
*Sneak sneak* New build on goo. CPU overclocking up to 1.6Ghz. Also reverted default I/O scheduler to cfq and default congestion scheduler to cubic. Honestly cfq feels a bit smoother to me and these settings are default in stock.

I go out of town Thursday for a while so this build will sit for a while but I like it so far.
[Samsung Galaxy Nexus] icon123:
Are you going to build one for 4.1.2? I wanted to try it out.
[Samsung Galaxy Nexus] tiny4579:
Yeah, I'm actually getting ready to update the OP in a short while.
[Samsung Galaxy Nexus] tiny4579:
I didn't forget you Android 4.1.2 users (and I still like it myself and am using it right now). Update for both 4.1.2 and 4.2 builds.
[Samsung Galaxy Nexus] d00dr:
So, just out of curiosity, what ROM are you going to be running while on vacation?
[Samsung Galaxy Nexus] tiny4579:
CM10 stable. I know, not bleeding edge. Let me know how 1.8 is if you're staying on 4.1.2.
[Samsung Galaxy Nexus] kmcrane:
2.1.0 or 2.1.0 exp1 newer?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

Ok, so this is how it goes. You have Nexus Evolution which runs LK. When you flash the ROM, the zip wipes system and flashes the ROM to system. It then flashes the boot.img containing the ramdisk and LK. When you flash a boot.img it overwrites everything. Nothing gets stuck as it's a complete overwrite. Then when you flash TK it will pull the existing ramdisk and replace the kernel and repack it into a boot.img and flash it. Then your new boot.img becomes the boot.img from the ROM with LK replaced with TK as the zImage.

One easy way to tell if the kernel uses boot.img is as said above. There will be a file called boot.img when you open the zip. An anykernel zip (one that takes the existing ramdisk already on the phone and replaces the kernel - zImage) will have a kernel folder with a zImage file in it and no boot.img file.

I don't believe your issue is a bug with either LK or TK or a combination. It could be a script the dev had loaded or an app in the ROM that is interfering. See if you can check with the ROM dev about the I/O scheduler not sticking and if anyone else had this issue. I don't know if wiping will solve it but you should never need to wipe data to deal with swapping kernels. Reinstalling the ROM will reset the kernel and ramdisk back to what came with the ROM. A dirty flash is more than sufficient and it always wipes system so any custom init.d scripts will be removed and you'll only have the ones with the ROM. It's also possible the ROM dev tweaked the boot.img. What does the I/O scheduler get set to at boot? Trickster should be able to change it. LK defaults to deadline I believe.
[Samsung Galaxy Nexus] phaze one:
Hell yes! I used your kernels on my Incredible. Stoked to see you're on the GNex. Flashing now.
[Samsung Galaxy Nexus] tiny4579:
You just flash it like any other kernel. Make sure it's a good download. Redownload maybe?

Either way, all the versions you listed worked for me. If they didn't they wouldn't be released and have many users successfully using them. For best results, make sure you're using the Android 4.2 with the kernel versions you mentioned. This kernel is compatible with all Galaxy Nexus models so I don't know why it wouldn't work for you.
[Samsung Galaxy Nexus] nitsua98:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

Imma lol if it turns out he's on ics
[Samsung Galaxy Nexus] klubhead:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

Just want to make sure, 3.0.0 will work on 4.2.2?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

Yes for sure.
[Samsung Galaxy Nexus] BaMaDuDe87:
You sir just blew my mind and am still trying to digest this, but I am sure you know what you are talking about and thank you for taking the time to write that response out. Now I have to take the time to try to understand. Time to research
[Samsung Galaxy Nexus] gt5oh:
any issues with Shiny Rom 2/22/13 build and this kernel?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

I don't see any reason why there would be. Version 3 is compatible with JB 4.2.x meaning 4.2.1 and 4.2.2, even if the binaries are out of date on 4.2.2 it will work fine.
[Samsung Galaxy Nexus] tacosrdelicioso:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

GPS no want to lock
[Samsung Galaxy Nexus] tiny4579:
That's not a kernel issue. Mine locks fine. Check your ROM thread for reported GPS issues.
[Samsung Galaxy Nexus] jesta192:
Tiny,

Your link to the frandom description should be .html rather than .htm

http://billauer.co.il/frandom.html
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

Thanks. Ill be sure to update it.
[Samsung Galaxy Nexus] justen7723:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

First time trying this kernel out. Been running very nice with sorcery 5.0. Thanks!

http://xdaforums.com/showthread.php?t=2131538

Ui sound mods 2/25/13 [IRONMAN, Transformers, HALO, star wars, Star Trek]
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.0.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/17/13

I've been using these kernels since the droid days... They are the best...
[Samsung Galaxy Nexus] tiny4579:
Today's release is just a quick update. I reverted a change I did earlier that could have had a negative impact on the wheatley governor. Nothing else should be affected.
[Samsung Galaxy Nexus] Gorilla*:
im gonna pass then, Im happy with CFQ.

This kernel provides good battery and speed.
[Samsung Galaxy Nexus] chazzdjr:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Holy crap! I was wondering what was going on. This update has my GNEX screaming fast again! Thanks!
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

The latest update has nothing to do with cfq or anything io scheduler. What do you mean your happy with cfq? All the same this update will make no difference unless you use the Wheatley CPU governor.
[Samsung Galaxy Nexus] JJones1210:
If I want to use this on a 4.2.2 ROM, will I need to flash the binaries first? Thanks in advance.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

No
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Tiny, want to report that 3.0.1 on IX governor was not entering deep sleep and battery life was suffering.

I've been experimenting with cross breeder over the last few weeks and removed it, tested, reinstalled 3.0 and tested, reinstalled CB and tested. The result was the same with or without CB... No deep sleep.
[Samsung Galaxy Nexus] tiny4579:
What ROM? CM has an issue where GPS prevents deep sleep until it gets a lock. Before assuming it's the kernel, please check betterbatterystats or another app that reports more detailed usage.

To go further, check for a gps kernel wakelock. If that's active at boot or shows up soon after boot in BBS, then your ROM has the gps issue where you have to get a GPS lock prior to getting deep sleep. iX has not changed one bit since 2.7 and it's extremely unlikely a kernel governor would have any impact on deep sleep.

Just tested and I'm getting deep sleep on interactiveX on 3.0.1.

If your issue is the gps wakelock and are using CM10.1 that is 4.2.2 based, then check the CM10.1 thread for a flashable zip that reverts the GPS files to ones that work on Verizon just fine.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Tiny, I'm on mmuzzy and have been since it's release. I didn't run a deep battery stat log but the os was dominating the battery usage. This lead me to suspect CB but it continued after uninstall.

I always open nav and maps after I flash a ROM or kernel after the wakelock issues a few months back.

So far I've never had any issues with your kernels and though I've strayed I always come back :). I'll wait for the next release and cross my fingers.
[Samsung Galaxy Nexus] chazzdjr:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

I'm on mmuzzy... Deep sleeping like a baby on 3.0.1. You got something else going on.
[Samsung Galaxy Nexus] chazzdjr:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Some proof.
[Samsung Galaxy Nexus] tiny4579:
I don't care what kernel you use though I am happy when people use mine. But deep sleep is one of those topics that is almost always not kernel related. It's generally app related. It's not your device preventing sleep either or an issue between a kernel release and device not going well together. Simply, an app wants to keep the phone awake. Please provide BBS screenshots or something as anything in the OS could be keeping the phone awake. Either way, if 3.0.0 worked for you then 3.0.1 will work fine as they are nearly identical.
[Samsung Galaxy Nexus] klobkelosh:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Are you, by chance, using trickster mod to measure deep sleep? I ask because I was having issues with deep sleep, at least I thought I was, but I realized that if I toggled the warp counter setting on and off a few times that it changed the amount of deep sleep, and showed that the device had in fact been deep sleeping. This was only happening with a fresh kernel flash, and I've found it hard to reproduce so I never reported a bug to the dev. I dunno, see if it helps or if I am just crazy.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

I do use trickster and I was refreshing regularly. I'll get a BBS log of 3.0.1 tomorrow if I have time to catch my breath.
[Samsung Galaxy Nexus] claytonjn:
I posted this in the RootzWiki thread, but maybe someone here will know the answer.

I'm learning how to build a ROM from source. This is going to be a ROM that solely I use, with personal cherry picks. I'd like to include TinyKernel by default. I added the following to local_manifest.xml:

But when I try to sync, I get the following errors:

I'm sure this is a complete n00b mistake...anyone have any ideas how to get this working?
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Tiny, the plot thickens. Looks like you're probably right that it's not the kernel. I'm getting a wlan_Rx_wake wake lock which has me thinking a hardware change at the office might be to blame. Will continue to troubleshoot.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13
[Samsung Galaxy Nexus] tiny4579:
Hey, this might help you with your wlan_rx_wake wakelocks:

http://rootzwiki.com/topic/16134-kernel-wakelock-wlan-rx-wake/
[Samsung Galaxy Nexus] ATTACK:
I don't know, but after using v3.0.1 my battery life is a lot better then v3.0 and lower.

It's the best battery life I have ever seen to date

on my phone

.

Awesome kernel
[Samsung Galaxy Nexus] gerodive:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Hey all. Potential new Tiny user here. Could anyone give me a brief rundown of this kernel vs. Lean? Which has better battery life? Also, the reason it's between those two is because someone on the Eclipse forum told me only tiny and lean allow for raising the throttle temp without disabling it entirely - that sounds wonderful. But if there are any others that offer this, feel free to mention them as well. Again, huge concern for me is battery, because it's been awful lately om whatever kernel came with eclipse. I'm pretty much a kernel n00b, as this is the first time I'm venturing away from my ROM's stock kernel. Thanks guys.
[Samsung Galaxy Nexus] aggrophobik:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

Depends on so many variables, you may as well test both and see which is better for your use. That being said, I find tiny to yield better battery life for my setup.

Sent from my Nexus 7
[Samsung Galaxy Nexus] ashclepdia:
Re: [KERNEL]Tinykernel 3.0.1(4.2.x)/1.10.0(4.1.2) [JB] Updated 02/25/13

That was me that mentioned that

Try one of the new lean kernel exp builds and use 230mhz min

Or just use tiny

I love both

Tiny 3.01 is what I'm gonna install right now Cuz I like that it has the frandom modules and already comes with a 230min CPU setting If u choose

Try tiny first
[Samsung Galaxy Nexus] gerodive:
Thank you for the tips! I've been Googling around and downloaded Trickster to edit the ROM settings to my liking, and performance and battery life are already many times better (wow that Luna kernel thing included with Eclipse must have really sucked). But I still have a couple questions. I read a few article on CPU governors, i/o schedulers, and TCP algorithms, and I'm feeling like the Tiny defaults are pretty darn good, but do you guys have any input/opinions that are more kernel specific than the general community can provide? I ran a Quadrant test on it and you can see the results below. Not sure why it's performing lower than stock, specifically that abysmal i/o value (not that benchmarks mean the end of the world, but I do find it interesting). My settings are all their defaults: CPU governor = interactive, i/o = cfq, tcp = cubic, and I'm OCed to 1350 and my temperature limit was raised from 64 to 70. Thoughts? Last of all, has anyone checked out the play store app called seeder? Lots of people, specifically g-nexus people seem to be seeing significant performance boosts with it, but I'd like to run it by the development community before I put down the 0.99 only to learn whatever it does is already baked into our roms/kernels or something. Sorry for the tons of questions everyone!
[Samsung Galaxy Nexus] thesuzukimethod:
just a quick thanks for a great kernel and a +1 to doublecheck apps when you are getting funky battery life

Not directed anyone in particular, other than myself...in short...I flashed the3.01 version after stupendous battery life on 3.0, but was getting very bad results (battery wise)...i thought, maybe needed to flash back to 3.0 or figure out what happened..and was even about to post a query here, but turns out beautiful widgets were going nuts with a wakelock.should have looked there first, but the correlation/coincidence (not causation) re: the kernel update sent me down the wrong path.

again, thanks tiny and the rest of you who spend free time developing, bug/beta-testing and whatever else goes into making stable daily drivers for the rest of us...
[Samsung Galaxy Nexus] tiny4579:
Good news, 4.1.x folk are not forgotten! I'm testing a new build 1.11.0 tonight. I'm reverting to 4.1.2 just so I can properly test it and see if I end up preferring 4.1.2 but I'll probably be back on 4.2.2 soon just since it's the newest.
[Samsung Galaxy Nexus] tiny4579:
3.1.0 released. 1.11 should arrive in the next couple days which should have the major changes from 3.1.0

Changelog:

compiled using 2013.02 Linaro toolchain

powerHAL updates to support ondemand governor

Linux 3.0.67

net: bluetooth: Remove the AID_NET_BT* gid numbers

sync: fix timeout = 0 wait behavior

cpufreq: ondemand: add boostpulse interface and set default boostfreq to 700 MHz

ext4: prevent kernel panic in case of uninitialized jinode
[Samsung Galaxy Nexus] bunnahabhain:
Maguro user here - wasn't aware of this - tried and it works flawlessly! Rated 5 stars - thanks a lot. I will visit this thread every no and then to check for updates :good:
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Tiny, latest version has solved my battery woes. See my post in mmuzzys thread for specifics. Thanks for bearing with me.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13
[Samsung Galaxy Nexus] ogpowell:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Awesome work...best I've found for all around performance and battery
[Samsung Galaxy Nexus] markculton:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Thanks Tiny!
[Samsung Galaxy Nexus] tshelby73:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Can I use this with stock ota 4.2.2
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Yes. Op says all 4.2.x meaning 4.2.1 and 4.2.2 ROMs.
[Samsung Galaxy Nexus] CondemnedSoul:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Very happy to come over here and see tiny making kernels :D:thumbup:
[Samsung Galaxy Nexus] tiny4579:
Welcome to the Galaxy Nexus!

Does anyone want 1.11? It's an updated 4.1.x kernel. I built it about a week ago but didn't post it as I was hoping to be able to figure out a way to use a 4.2.2 kernel branch and make bluetooth work on that source for 4.1.x ROMs.
[Samsung Galaxy Nexus] kevdliu:
Is everyone from vivow mass migrating to galaxy nexus? well im not surprised after that cm10 hell :P
[Samsung Galaxy Nexus] nitsua98:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Yes :p lol
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

I went from inc to Galaxy Nexus. Vivow wasn't enough of an upgrade.
[Samsung Galaxy Nexus] klobkelosh:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Some of us remember condemnedsoul from his (gulp) droid eris days...
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

I do. Still have the old eris laying around too!
[Samsung Galaxy Nexus] baggar11:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

I actually came over from vivow. The constant disappointment from the ICS upgrade drove me over here. I'll probably never buy another phone besides a nexus now.
[Samsung Galaxy Nexus] kevdliu:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Tiny I've discovered this multi core power saving feature in kernels like ak and fancy where it groups tasks into the least number of cores possible to save battery. You think that works?

Damn straight :D so pissed Verizon doesn't carry n4. Let's hope my galaxy nexus doesn't break before the "x-phone"
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Not sure if it will help or not. It seems to go against what multiprocessing is about though.

I don't think the n4 is worth the upgrade otherwise I'd have it already on T-Mobile or at&t. I thought I'd want another nexus but due to their history of hardware lagging I might just get the s4 next. It'll end up running my ROM of choice anyway.
[Samsung Galaxy Nexus] stewyfallingup:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

I'm interested in what Motorola will bring to the table. That Motorola X phone I've been hearing about looks promising.
[Samsung Galaxy Nexus] gerodive:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Not if it's got one of those gargantuan screens. Our g-nexus phones are already at the absolute max for comfy one-handed operation. I loved my dinc size, and 4.3-4.6 isn't too terrible, but anything past that is absolutely out of the question. Bigger != better, and I hope they get that right with the X phone. And also have a removable battery. That's a must-have given our current battery life. Otherwise I might as well just buy a *cringe* Apple product.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Sgs3 itself is about the same phone size but has a slightly larger screen. The bezel is just a bit smaller. A lot if unused space in the galaxy nexus. Sgs4 will hopefully not be too much larger.
[Samsung Galaxy Nexus] TheGman125:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Can someone point me in the right direction of understanding Voltage of the kernel?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Its stock pretty much. What is it you want to know?
[Samsung Galaxy Nexus] TheGman125:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

I would like to know this best way of setting the voltage on my devices and that will give me great battery life?
[Samsung Galaxy Nexus] nitsua98:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Lower one voltage setting by five until the phone freezes/reboots, set it back to what it was before it froze; repeat with all other voltages.
[Samsung Galaxy Nexus] Txwolf1980:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Interesting. This was going to be the next thing I looked up. Clarification, if you would. The voltage figure references how much draw is being put on the battery to maintain that particular frequency. Correct? Does it have any bearing on governor? As in, if I'm running a lower voltage on 700mhz, under an interactive governor, will it take longer for the governor to be able to spool the processor to 700 on screen on? Understanding that the difference would be infinitesimal, I'm just curious
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Make sure you freeze the CPU at the given frequency before testing.

Also you won't gain very much. Smart reflex doors a pretty good job of auto-adjusting the voltages. In any case you have to get under whatever smart reflex is setting the voltage at to have any effect at all.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

This kernel has no user undervolting as I believe smart reflex is sufficient enough and undervolting can lead to instability issues. If you need to undervolt use a different kernel.
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

Delete
[Samsung Galaxy Nexus] tiny4579:
Just wanted to give everyone a heads up on an upcoming build, or two builds (4.1.x and 4.2.x versions):

So, I made some changes over the last couple days to the kernel. FIFO I/O scheduler for one and a fix to a possible memory leak in the SLUB allocator. Either way, it seems like this upcoming build may be smoother or it's the new CM nightly. I don't know which. What you can expect:

FIFO I/O scheduler

zcache/cleancache/ksm to help with memory management

fix to a possible memory leak in the SLUB allocator

intellidemand (if I can get it to build)

I kind of like the idea of the FIFO (first in first out) scheduler. It's supposed to be a true no-op scheduler so we'll see how this one goes. FIOPS is a bit complicated on my kernel code base as it needs some backporting/patches to build on 3.0 as it was designed for 3.4 so I'm not sure if FIOPS will happen.

Also soon to come is 1.11 which should be the Jellybean 4.1 version with all the new changes from 2.6 or 2.7 to 3.1 and these changes.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.1.0(4.2.x)/1.10.0(4.1.2) [JB] Updated 03/03/13

I sure appreciate all your hard work...
[Samsung Galaxy Nexus] tiny4579:
Enjoy! Please check OP for changelog. Both 4.1.x and 4.2.x kernels have been updated this time around.
[Samsung Galaxy Nexus] ATTACK:
v3.2.0

is making my phone run

HOT

(temperature wise). I've changed nothing on my phone, added no new app's, same AOSP Rom and running the same setup [Nightmare ~ Sio, 920 ~ 350] and my screen gets very hot after a few minutes of use. I flashed back to

v3.1.0

and now my phone is fine and doesn't get hot anymore.
[Samsung Galaxy Nexus] sonicdeth:
Interesting. I've been on 3.2 all day and everything seems normal here. Deep sleeping fine and scaling up when it needs too (at least according to CPU Spy)
[Samsung Galaxy Nexus] klobkelosh:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Same here. Some rootzwiki fora having deep sleep and clock issues too. I'm seeing lag on fifo scheduler, but otherwise smooth