[KERNEL] [WIP] Quickie "Screamer" 0.2 **STABLE** for Froyo!

---

First off - I must acknowledge that that code this came from, is not mine. All credit goes to Geniusdog254, fat-tire, mbm (irc advice), and those who have committed to their branches; i would like to eventually make my own branch, but for now, this is a great start. Hopefully this is ok with them - if not, i will happily take it down.

UPDATE AT YOUR OWN RISK.

So, for all those lucky 2.1 users, you have have a nice overclocked kernel. Well, today lucky 2.2 users get the same enjoyment! Just as a teaser - Quadrant gives a score of 1618

0.2:
950Mhz: http://www.mediafire.com/?mbfnt3i39cz8q9o
900Mhz: http://www.mediafire.com/?opmajiyx1puf11t or http://www.megaupload.com/?d=AQKPIPHR

Changes:
***ROTATION IS FIXED***
Original Kernel base proved unstable for the Froyo build. So, went back to basics, and modified the original Nookie Froyo Kernel, as found here: https://github.com/fat-tire/nook_kernel
Future code will be branched from this for the time being.
Built two different kernel speeds, for those whose systems dont like 950.

0.1:
http://www.mediafire.com/?aoadpgt2foxhby9
Compiled from https://github.com/fat-tire/Quickie, as of 1/18/11.
Kernel defaults to 950Mhz
Kernel made compatible to 2.2 standards, with other minor fixes (as noted in Github


To Install:
[Pre Install]
Wipe Dalvik Cache
As suggested here: http://forum.xda-developers.com/show...7&postcount=12, it is best to wipe the dalvik cache (if this is not the first boot of the system,). To do so (after connecting your nook to a PC):

adb shell
cd /data/dalvik-cache
rm *
reboot

This can also be done in root explorer.

[Install]
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.

[Tested on]
I have tested this Kernel on both a fresh copy of .5.8, as well as the custom .5.9 as posted here: http://forum.xda-developers.com/showthread.php?t=922324

[Recomendations]
Get SetCPU (from this friendly forum!), and change the governor to on-demand. It is currently defaulted to conservative for battery, but OD should give better performance.

Future & Reserved:
Ideally, i would like to build on this kernel, and add features other kernels have, such as different governors, BFS, and HAVS. I don't know much I can actually do, but as time goes I am sure i will learn more. Please be patient with me, and remember this is a WIP. While i am not new to coding, I am new this kind of kernel work, so I am still picking up things here and there..

Issues -
Quadrant is stupidly picky. I am not sure what i did to get it to run when I did, but the best i can say s to keep trying. Right now, it seems to really hang at 2/4 on the I/O.
I believe the default governor is set to conservative; i recommend downloading SetCPU and setting it to ondemand.

Woot :P Saw the IRC work and couldnt wait.


And i was going to say the wait at 2/4 on I/O was like that before :P


1607 Quadrant score (:

Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.

Originally Posted by kassemja

Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.

Just boot a copy of nookie froyo from a mircosd and mount the /data partition from the emmc to delete the davlik cache. That's how I was making changes to nookie froyo when I was running it off the emmc. Once hardware decoding for media is supported I will put NF back on the emmc. Can't wait till clockwork supports froyo. I will be all over this!


Nook Color+Rooted+OC@950+Nookie=Awesome

Not working on my Froyo'ed Nook

---

Originally Posted by Divine_Madcat

To Install:
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.

Hi! It sounds really promising.

I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.

Any idea? TIA

Originally Posted by xyzolog

Hi! It sounds really promising.

I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.

Any idea? TIA

Same thing happening here.

Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.

However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.

I have used the 950 kernel on 2.1 for about a week no issues. I'm happy to test again with a davlik cache wipe. On the way to work now. So hopefully you can post new build by then.

Originally Posted by Divine_Madcat

Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.

However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.

Sent from my Nexus S using Tapatalk

Originally Posted by Divine_Madcat

Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.

However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.

Yes. 950 Mhz ran fine for me. The 1Ghz though did not.

I didn't do a Dalvik cache wipe first. When i get a chance I'll try that and give it another go.