yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
Coming soon :D

3.0.58-tinykernel-2.6.0-06285-g357f1d7 #33 SMP PREEMPT Wed Jan 16 20:53:11 EST 2013

ROW scheduler

OC options as mentioned above

One thing keeping me from wanting to release it is resolving the SOD issue reported by a few users in 2.5.1.

If you get an SOD, can you log in with adb and grab the kernel log?

adb shell
dmesg > /sdcard/dmesg.txt
exit
adb pull /sdcard/dmesg.txt

Also if you can use adb with the SOD, you should be able to get a logcat.
[Samsung Galaxy Nexus] andrewc513:
Eh.. what can I offer up if it happened a few days ago, and hasn't happened since?
[Samsung Galaxy Nexus] d00dr:
I can honestly say that I have yet to experience an SOD with any of the more-recent TinyKernel versions...

*knock on wood*
[Samsung Galaxy Nexus] tiny4579:
Wait for it to happen since you probably rebooted to get out of that state.
[Samsung Galaxy Nexus] zerocool79346:
If i can catch one will at home I'll get it. No promises though
[Samsung Galaxy Nexus] ATTACK:
I have had ZERO problems on all version's on TinyKernel.
[Samsung Galaxy Nexus] ArnieG:
Mmuzzy's Roms and Tiny's kernels =no SOD

from mmuzzyfied GNex w/tiny kernel
[Samsung Galaxy Nexus] cms5423:
Tiny, could you explain a little bit about the 'read ahead buffer' parameter and why you chose to set it so low? I'm just trying to learn a little more about kernels and I can't seem to find good info on it. Thanks so much
[Samsung Galaxy Nexus] tiny4579:
I left it stock. I used to have it at 1024 but I lowered it to set it back to the stock kernel's settings. It wasn't setting it low, it was reverting to what Google had, though I'm starting to be more experimental lately like integrating linux kernel patches and introducing new I/O schedulers.

I may increase the default to 256 but not higher as there's probably a reason it was left at 128. I honestly haven't done much research on readahead myself.
[Samsung Galaxy Nexus] tiny4579:
Maybe a 2.6.0 release soon :)
[Samsung Galaxy Nexus] Jose Viegas:
Re: [KERNEL]Tinykernel 2.5.1(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/10/13

Yeaaahh
[Samsung Galaxy Nexus] tiny4579:
Just an opinion question, I'm working on a lower min CPU option (maybe not a great idea for those that have already seen SODs), but I wanted to add a single lower frequency option. Imoseyon has 180mhz min and 230mhz kernels (both will not be used unless the min is explicitly set to either). Right now I have both but the small gap between 180 and 230 isn't really logical or even great on battery in my opinion. I was wondering what of the two would be preferred. I have a tentative plan to make a single 200mhz min.
[Samsung Galaxy Nexus] andrewc513:
No SOD since the one a while back. Was probably a fluke like I originally thought, seeing as how I am on CM10.1 *nightlies*, and not a fault of tinykernel.
[Samsung Galaxy Nexus] tiny4579:
As promised:

2.6.0

Linux 3.0.58

WiFi driver updates

ROW I/O scheduler enabled and default

disabled CFQ scheduler (necessary to build ROW for now)

OC frequencies change from 1400/1600/1800/2000 to 1350/1520

supports 230Mhz min frequency and lower voltages are set on the lower frequencies

default readahead increased to 256KB
[Samsung Galaxy Nexus] Jose Viegas:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Great! Gona try it now
[Samsung Galaxy Nexus] JohnKuczek:
[KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

2.6.0 downloaded, flashed, and running... Very smooth, just as expected!
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

No issues so far......you are the man!
[Samsung Galaxy Nexus] zerocool79346:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

2.6.0 is running incredibly well at the 230 screen off for me. Gonna try out the interactivex governor for the rest of the day and see what happens.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Screen off not screen min? The reason I added 230 was for screen min.
[Samsung Galaxy Nexus] zerocool79346:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Yeah i used to have it reversed from what it is now. Never gave me any trouble that way, but wasn't running IX either.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

350mhz screen off should be more than enough especially on interactive. On interactiveX you might need to raise it.
[Samsung Galaxy Nexus] zerocool79346:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

No problems yet but I'll definitely let you know! IX seems more responsive than interactive oddly enough.
[Samsung Galaxy Nexus] zerocool79346:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

First SOD with settings chosen above. I think it's likely the IX governor on my device.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Possibly. I remember people reported those on the hotplug and ix governors before even in the ICS days on lean kernel.
[Samsung Galaxy Nexus] laureanop:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Battery savings are negligible on ix and are not worth the risks of the SOD imo. Interactive has been the way to go since 4.0 (1.5 through 2.3 was on demand)

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] zerocool79346:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Yep so do I.

This in my case.
[Samsung Galaxy Nexus] aperseghin:
ok so whats different in 2.6.0-1 ? My phone just downloaded it all by it self.
[Samsung Galaxy Nexus] Txwolf1980:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Nothing. When you opened up your

browser, the goo download page was still up in one of your tabs. It initiated the download. It's happened to me,a few times. Now,I just get it

straight from goomanager. The 1, at the end, indicates that is a copy
[Samsung Galaxy Nexus] aperseghin:
Ahhh, ok, got it.. i was all kinds of confused.. thanks I would normally recognize the -1 being a copy, but i was thinking point release since it was 2.6.0-1

:facepalm:
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Awful quiet on here...everything must be good. Mine sure is.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Finally installed 2.6.0 on Mmuzzy's CM ROM and it's running great. Will be paying attention tomorrow to see how she does under normal usage.
[Samsung Galaxy Nexus] IthsSunnyB:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Just installed 2.6.0. Having an issue not sure if it's kernel related but never happened on other versions... So here is my issue after install, every time I play music and go to lock the screen after maybe 30sec the player would stop playing I would have to turn the screen on and press play but can't turn the screen off or the player will stop... Tried reboot didn't help... I'm running muzzys CM with 2.6.0... Thanks in advance
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Never heard of that issue before. Sounds like something funny on your end.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Update soon. Hopefully for 4.1 as well as 4.2.
[Samsung Galaxy Nexus] tiny4579:
A short changelog regarding the beta I just uploaded:

1. Pegasusq governor included

2. Wheatley included - preferred to use stock min/max for ideal results - it is normal for it not to spend as much time at the minimum frequency as the method behind this governor is to maximize time in C4 state, so even though it's based on ondemand, it's not quite the same

3. interactive and interactiveX have an experiemental patch to prevent race conditions - I reverted imoseyon's tweak for best results - also, it replaces the powerHAL with a CM-based one so that boostpulse will be reopened when switching back to interactive from another governor.

4. updated to Linux 3.0.60
[Samsung Galaxy Nexus] tiny4579:
If you download it prior to 9:00 PM you will need to re-download it. I pushed up an earlier kernel that I thought was going to release. Not a bad kernel but not the one I wanted to test.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Tiny, just read up on Wheatley and Pegasusq... Can you elaborate on pros/cons? Running wheatley now, so far so good.
[Samsung Galaxy Nexus] tiny4579:
I'd rather let people determine what is better for them through usage.

I summarized wheatley on the last page and it's design. Pegasusq is a modified ondemand governor released with the S3 stock kernel from Samsung. The one on here has been tweaked for 2 cores by various devs.

To top it off, there's a sticky page in Galaxy Nexus general that describes the various governors, though I think the wheatley one is missing the point because it's not optimized for performance but for maximizing the C4 CPU state so it can use less power even at a higher frequency. As a result it feels like a performance type governor. You shouldn't really have worse battery.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Thanks tiny, the sticky is helpful but so is the devs perspective :)
[Samsung Galaxy Nexus] ArnieG:
Installed beta. Running interactivex today. Looking good so far.
[Samsung Galaxy Nexus] ATTACK:
I have been using v2.7 beta-1 since the release and its working nice and smooth like always.
[Samsung Galaxy Nexus] sajty:
I have read some good references to this kernel,but i have one stupid question.Is this version working with maguro?
[Samsung Galaxy Nexus] tiny4579:
All Galaxy Nexus kernels since 4.0.3 are compatible with both maguro and toro and I imagine toro plus.
[Samsung Galaxy Nexus] Mystique:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

Trying out this kernel for the first time..

Using the 2.6.0

I see ondemand, interactive and interactivex. Is that correct?

Defaults to row, which is great thank you.
[Samsung Galaxy Nexus] tiny4579:
I pulled out most governors from my kernel so that sounds about right. I can't remember if I removed conservative but I might have. The 2.7.0 betas have wheatley and pegagusq.
[Samsung Galaxy Nexus] dereaper:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

any chance for nightmare? and fiops ?
[Samsung Galaxy Nexus] tiny4579:
Not for now. I already added more user governors and schedulers than stock. I/O schedulers don't seem to affect performance that much on an SSD/flash memory. In fact the more complex ones can actually impede sometimes. I have been curious about FIOPS. Also, as to nightmare, what are you hoping to get out of it that isn't satisfied by pegasusq or interactive?
[Samsung Galaxy Nexus] dereaper:
Re: [KERNEL]Tinykernel 2.6.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 01/18/13

everything seemed more responsive on my phone with nightmare and fiops but hell could be placebo lol
[Samsung Galaxy Nexus] tiny4579:
I didn't include the above requests but maybe in a future release. I was wanting to push out a stable.

2.7.0 is stable. The changelog is pretty big:

Linux 3.0.61

WiFi patches and update to version 5.90.195.114

Revert patch that doesn't remove sysfs nodes - reason below

powerHAL patched to allow interactive boostpulse node to reopen when switching back to interactive from another governor - this powerHAL also prevents CPU max from being reset to 1200.

Wheatley (Ezekeel) and PegasusQ (Zenkernel) governors

interactive/interactiveX: fix race condition on governor start/stop - this is why I reverted above patch and thus had to add my own powerHAL

netfilter qtaguid patches

increased MPU voltages for stability

added improved glibc memcpy and memmove functions (Ezekeel)

built with 01/2013 Linaro toolchain
[Samsung Galaxy Nexus] dereaper:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

still can't wait to try it out !thanks for your hard work as and dedication XD
[Samsung Galaxy Nexus] cmoG530:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

Heard about this kernel through the grapevine. Will give it a go Lord willing.
[Samsung Galaxy Nexus] kmcrane:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

I left tiny's to air kernel to try the nightmare... It's nice.. 3 days and I'd have to say that I like it better than Wheatley. Which I use to think was my favorite. I am downloading 2.7 now to try tiny's kernel. Same settings always work better here than any other kernel.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

2.7.0 is working just fine. Using Wheatley and no adjustments have been made. All I can say is fast but smooth. Thanks so much.
[Samsung Galaxy Nexus] tiny4579:
For those who care about frandom, I reuploaded 2.7.0 with a working frandom module. This is only useful if you care about tweaks regarding the whole seeder/entropy thing. I liked this one as frandom promises to be way faster than random; however a little less secure when using crytographic functions than random or urandom.

For more information on how to apply that tweak, read the thread on crossbreeder thread and look for my post as to how to replace random with frandom.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

Has anyone tested the frandom module? Performance/smoothness bump? Battery life?
[Samsung Galaxy Nexus] baggar11:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

Is there something special we need to do to test it? Been running 2.7.0 since it came out otherwise. Great kernel.
[Samsung Galaxy Nexus] tiny4579:
On it's own it does nothing. If you want a basic init.d script that enables frandom and erandom and replaces urandom and random with them, here's one:

#!/system/bin/sh
insmod /system/lib/modules/frandom.ko
chmod 666 /dev/frandom /dev/erandom
mv /dev/urandom /dev/urandom.ORIG && ln /dev/erandom /dev/urandom
mv /dev/random /dev/random.ORIG && ln /dev/frandom /dev/random
killall system_server

The last line restarts system_server to make the system use the new frandom and erandom devices. In the next version frandom.ko will be built into the kernel so we won't have to load it at boot but the other steps are still necessary.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

Tiny, have you tested it yourself? I jumped on the original seeder apk and the improvements were overshadowed by the hit to battery life.

Now there is so much noise surrounding these I've tuned it out. I trust your opinion and experience. Thanks!

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

...and noobish question, what do I do with the code above? Making a new file (name?) Or editing an existing script?
[Samsung Galaxy Nexus] savantist:
sorry for noob question... :)

this kernel is secured kernel, yes?

coz when I'm trying to push file via ADB, it says "permission denied" and when I'm trying to "adb remount" it says "operation not permitted"

change u change it to insecured kernel?

or adding ro.secure=0 to /system/build.prop is enough?

thanks, it's been a good kernel dude... :)

but you know, MTP's kinda sucks, and I'm using ADB to overcome that suckness... LOL
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

I use the ROM's ramdisk so the answer is it depends. Have you tried adb root to get root access from adb? Insecure means adb will run in root mode.

ro.secure needs to be modified in default.prop in the ramdisk and not build.prop.
[Samsung Galaxy Nexus] tiny4579:
Frandom is not really part of the seeder using a background process to generate entropy. All I'm doing in the kernel is adding two new random devices that can be used for generating random data instead of the built in random and urandom. frandom is faster than urandom but uses up entropy. erandom is slower than frandom but does not use entropy. Both should be quicker than urandom.

I can't claim whether or not this will help battery life but having the devices in there will do no harm. Above I linked a script to get the OS to use the new random devices. Either creating a new script or using an existing one is fine.

One thing to keep in mind is that the killall command soft reboots the ROM once to force the OS to use the new links. This isn't required and you probably won't notice anything if you remove it, but I recommend if you are going to run this script any way other than in init.d or something else that runs right away that you remove the killall line as you will definitely see a soft reboot then.
[Samsung Galaxy Nexus] savantist:
Yes I have tried that (adb root) from my PC, and it shows:

adbd cannot run as root in production builds

and still I can't do adb push/pull thing... :(

it shows:

failed to copy 'blablabla.zip' to '/data/media/0': Permission denied

and when i do 'adb remount':

remount failed: Operation not permitted

One thing I noted, is, when I do "adb shell" command from my PC, that remote shell Android logins with normal user, not root/superuser... and I must do 'su' to enter root privilege...

Maybe those two problems related? Or I just change ro.secure=1 to ro.secure=0 in default.prop to solve this?
[Samsung Galaxy Nexus] tiny4579:
You can push or pull to /sdcard without root. But you need root to push to /data/media/0.

Yes, you can change ro.secure=1 to ro.secure=0 to give you root all the time with adb. However, you need to edit the ramdisk as if you edit it any other way it's only editing on boot and once you reboot the file is repopulated from the ramdisk. Check for an insecure boot.img for the Galaxy Nexus. I don't see why there wouldn't be one for 4.2.
[Samsung Galaxy Nexus] savantist:
wow! that was very quick reply... :)

yes, I've tried that, and success... thanks... :)

mmm... yes, with insecured boot.img, just realized that you'd said that your kernel's using ROM's ramdisk... sorry for my stupidity... :)
[Samsung Galaxy Nexus] tiny4579:
Who's interested in trying out a beta?

Quick changelog:

frandom built in

CFQ back instead of ROW (sorry ROW scheduler users)

nightmare governor

For some reason intellidemand doesn't like my kernel and won't compile yet.

It's available at the usual spot.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

Tiny, beta running great
[Samsung Galaxy Nexus] ashclepdia:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

I've been following your work lately with the frandom tweaks and such tiny, seems promising.

I plan to load your kernel later and then install this mod on top

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

just wanted to mention it in case you hadn't seen it and wanted to look thru it.

and for anyone else interested in it :D

I'll report back after installing everything
[Samsung Galaxy Nexus] ArnieG:
running beta with PA3......so far everything is copacetic.
[Samsung Galaxy Nexus] tiny4579:
The goal of that CrossBreeder Mod already seems to be fulfilled by moving /dev/urandom and linking /dev/erandom to /dev/urandom.

Below I have a sample script. You can uncomment insmod if you're using 2.7.0 but you don't need that line if you're using 2.8.0 beta1.

#!/system/bin/sh
#insmod /system/lib/modules/frandom.ko
chmod 666 /dev/frandom /dev/erandom
#sleep 2
mv /dev/urandom /dev/urandom.ORIG && ln /dev/erandom /dev/urandom
#sleep 2
mv /dev/random /dev/random.ORIG && ln /dev/frandom /dev/random
pkill system_server

To verify, do lsof | grep -i random and you should see a lot of /dev/urandom entries and a few /dev/uradom.ORIG entries if it worked fine.

The pkill system_server will restart the Android processes so I recommend the above script in init.d or something that runs early in the boot.

My opinion on that mod is that while it seems significantly better than Seeder as it doesn't run when the phone is asleep, saving battery power, it still runs in the background and does use a tiny bit more juice. Plus,

cat /proc/sys/kernel/random/entropy_avail reports a decent number like over 1000 so there seems no danger of depletion. I still have some doubts on lack of entropy being the main cause of lagging. I still have not solved my good old lag issue on my phone. It seems that given enough time, I can have bad lag fits where the phone pauses to think for several seconds before updating the UI or switching to the next screen.
[Samsung Galaxy Nexus] laureanop:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

Terrible idle drain on the latest beta even on WiFi. The kernel kept the phone awake for 3 hours in a 12 hour period with minimal usage. However, phone has never been this fast or smooth

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

Not having this issue. Do you have the same drain on 3g? Likely its an issue with your WiFi router. 9 out of 10 times wakelocks are os related.
[Samsung Galaxy Nexus] laureanop:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

I'll leave it on 4g tonight to see what kind of drain I get. At my house it would normally be 3-4 % /hour

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 2.7.0(4.2.x)/1.10.0.(4.1.2) [JB] Updated 02/02/13

I lose less than 1% an hour on WiFi. Did you double check your router? Looking at your screenshot I see dhd_cfg80212_ev near the top. I also only see 9 mins of kernel awake time over an 8 hour period for myself.