yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] KDOG2020:
Hmm I'm definetly interested in the 1.2ghz OC kernel but I'd like to see if its stable or not. Don't want to fry my rig lol. Can I ask why its 1190 and not an even 1200?
[Nook Color Android Development] philburkhardt:
I agree, on both counts.

I have been running at 1100 for as long as the 1100 kernels have been available, and I have never had an issue.
[Nook Color Android Development] circuithero:
All i did was change the clock speed to 1.1 and to performance governer.
[Nook Color Android Development] ADude:
So, if you run the Nook for awhile, and put it on your lap, you feel no warmth at all (from the home key end of the bottom) ??
[Nook Color Android Development] philburkhardt:
I never turn my nook off, and I have never felt heat coming from it.
[Nook Color Android Development] rahlquist:
1100 is rock solid but cant get 1190 even with Setcpu. 1100 is fine by me.
[Nook Color Android Development] dalamchops:
same, mine locks up going to 1190 with either CM7 menu or setcpu
[Nook Color Android Development] Kendr1ck:
Same here.
[Nook Color Android Development] TJNooker:
To those of you that have tried this kernel and posted comments, go back and edit your posts to include what version of Android you're running so we can narrow down issues to CM7, Froyo, or both.
[Nook Color Android Development] Nburnes:
Glad to mention that the 1.2 works amazing fine on two nooks in my house. Both running CM7 nightly (#30).
[Nook Color Android Development] jewnersey:
Ditto

from my NookCOLOR, *****es
[Nook Color Android Development] KitF:
1.2 bootloops for me on CM7 n23.
[Nook Color Android Development] poofyhairguy:
Oh wow, 1.2GHz rocks! I am on 27. I have no force closes. The Nook Color is finally free!
[Nook Color Android Development] celebi23:
So, I'm a bit of a noob when it comes custom kernals. I think I set this up correctly: I've got CM7 n30 on an 8GB uSD (thanks to verygreen's topic) & it's been running great.

I decided to give overclocking a shot & chose OC kernels (up to 1100Mhz, Interactive gov, BT and DSP). I replaced the "uImage" file on the boot partition of my uSD with the "uImage" from the kernal zip file, put the uSD back in my Nook Color & booted it up.

I then went to cyanogen settings->performance->cpu settings-> & changed Max CPU to 1100 MHz & selected "Set on boot". Everything seems to be running a bit quicker/smoother. The only issue is that Bluetooth isn't working. Is there anything that I'm missing? Like I said, I'm a bit new at the whole custom kernal thing. Thanks!
[Nook Color Android Development] timekeeper:
Quardrant score of 1692 (1981 second time) using the non-net 1110 kernel on CM7 Nightly 29. Very nice! The LauncherPro homescreen loading animation is also actually smooth for the first time, no crashes so far.
[Nook Color Android Development] dukdukgoos:
Installed 1.1ghz non-net on Nookie Froyo. Installed okay, bit of weirdness getting booted up first time but eventually fine. Linpack scores went up noticeably. Quadrant errors out during video decoding test and has to be force closed. Opening pages in stock browser is very slow and hangs for minutes at a time, also requiring force close. Not sure what i should do. It's not totally broken but it's not right either.
[Nook Color Android Development] sebanoel:
I played many hours Dungeon defenders at 1.2.

After reboot, freeze at lock screen.

I will limit it to 1.1 at boot.

Maybe a widget "overboost" to activate the "more overclocked" :)
[Nook Color Android Development] Riley1524:
So, does this overclock just inflate quadrant scores or are there really improvements in speed? Everyone knows quadrant scores mean absolutely nothing as a performance benchmark
[Nook Color Android Development] spyderman33:
running the Regular kernel with 1100MHz OC with no problems on Phiremod 5.1

running faster than before...
[Nook Color Android Development] Divine_Madcat:
A couple of things in regards to this:

The previous version of this kernel was already overclocked; that is but what this kernel changed.

Ironically, the quadrant scores that you dismiss, actually demonstrated a real problem. There was a kernel update that was made, and it did not play nice with I/O functions. Even worse, quadrant was the only one that actually showed this fault.

The fix, as reported by many in this thread, gives a system wide improvement, in addition to quadrant properly working again. Users should see the app drawer open smoother, and programs opening faster.
[Nook Color Android Development] junkrobot:
Well, I tried the normal net version on Phiremod v5 and it was going great, I got iptables to work and everything. Then I enabled wireless, the device force closed and now it's in boot loops. This is a real bummer.

Edit:

I reverted to the latest Dalingrin kernel and it seems to be working fine now, but no more iptables and obviously, no more fixed I/O stuff. If anyone could tell me if iptables work in the non-net version of this kernel, that'd be great.
[Nook Color Android Development] smartmind:
I am using cm nightly build (the kang signed one) with your OC kernel (up to 1190Mhz, Interactive gov, BT and DSP), the speed is fascinating, but I can not turn on the BT, the wifi works good, I wonder if this problem could be solved?
[Nook Color Android Development] Divine_Madcat:
To fix the BT (same with the previous Dalingrin kernels) you need to hard turnoff the device - just hold the power until the system turns off (do not select the shutdown option). You may need to do this a few times, but BT will turn on after that. Though, it also can't hurt to do a fix permissions using ROM Manager..
[Nook Color Android Development] ficklecycler:
This kernel does not seem to be compatible with froyo emmc. I flashed it and the first time it booted all the way up then froze. Now subsequent boots don't make it all the way to the lockscreen.
[Nook Color Android Development] junkrobot:
I flashed the non-net kernel and the boot loops have stopped. So, judging by my experience and other people's as well, there seems to be an issue with the net features.

Anyway, I honestly haven't noticed any speed difference at all, but maybe it's just very subtle.
[Nook Color Android Development] krweby:
Ok tried the net version again. This time I removed my network and turned off wifi then flashed it. Everything looked good tell I turned wifi back on then it started boot looping again. Is there an app that has the net info in it that I can clear data/cache on without having to clear the whole thing and resetup?
[Nook Color Android Development] junkrobot:
This is exactly what happened to me when I tried the net version.
[Nook Color Android Development] ficklecycler:
I'm not having any luck getting through the boot completely. I've tried flashing an older kernel to replace this one but I still can't get all the way through the boot. Can anyone offer a suggestion of what I need to do?
[Nook Color Android Development] lwhitit:
Same here. It boots up until right b4 the lock screen. I just get a blank screen i tried both versions.
[Nook Color Android Development] Link3737:
I was having the same issue with the net kernel, but reflashing the nightly and then the normal kernel fixed the boot loop for me.
[Nook Color Android Development] ficklecycler:
I'm on nookie froyo though. Is there a way for me and others to recover from this bootlooping?
[Nook Color Android Development] jyams:
Flashed non-net kernal. Running Phiremod 5.1. Works for me. Quadrant scores went from 1100's to 1856!! I'm tickled!!

EDIT: Tested. Did a hard reboot. New quadrant score of 1955!! Everything is smooth and FAST!!

For Noobs like me, here is the process I followed to flash this new overclock kernal.

1. Downloaded the new kernal: OC kernels (up to 1100Mhz, Interactive gov, BT and DSP):Regular, http://www.mediafire.com/?k00ruvyulf01y64

2. Inserted my ClockworkMod 3.0.1.0 bootable SD in my laptop and copied over the above .zip to the root directory of my bootable SD card

3. Removed SD card from my laptop and inserted my ClockworkMod bootable SD into my Nook

4. Powered-up my Nook. It will now boot from the SD card into ClockworkMod

5. Wiped regular cache

6. Wiped Davlik Cache (in "Advanced" menu)

7. Choose "update .zip from SD card" - can't remember the exact menu wording

8. Choose the .zip you copied over to the SD card which is the "update-CM7-madcat-OC-emmc-032511" .zip file

9. Hold the power button and power off

10. Remove the SD card and replace with your normal SD storage card (non-bootable).

11. Hold Power button power up. Be patient. This boot takes longer. Give it some time to boot and settle down, like 3-5 minutes

12. Unlock slider

13. Go to Settings / CyanogenMod settings / Performance / CPU Settings. Set "available governors", "Min CPU Freq to 300mhz", "Max CPU Freq to 1100mhz", "Set on Boot".

14. Back out and go to Quadrant app and "Run Full Benchmark". Report results here. Be sure to tell everyone what ROM you are using. Do a hard reboot serveral times (hold power button for about 7 seconds until unit powers off. Then hold power button to power back up). This re-enables the Bluetooth to work again.

Hope this helps Noobs like me!!
[Nook Color Android Development] hrizzy:
Seems Froyo version doesn't benefit from this kernel. Mine booted OK,but Dolphin becomes pretty sluggish. Although Guerilla Bob is more or less OK :). Can't pass quadrant, it stops on h264 test. Wifi looping is as usual.
[Nook Color Android Development] Clienterror:
Using cm7 nightly 30 its stable at 1.2 for me. Getting 1900+ on almost every quad run. It doesn't really load any faster but it is way more responsive.
[Nook Color Android Development] timoskrempel:
same here with CM7 this is the last stuff in the logcat:

I/wpa_supplicant( 1101): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 1034): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
I//system/bin/tc( 935): RTNETLINK answers: Operation not supported on transport endpoint
I/logwrapper( 935): /system/bin/tc terminated by exit(2)
I/ActivityManager( 1034): Start proc com.android.launcher for activity com.android.launcher/.Launcher: pid=1148 uid=10001 gids={1015}
D/WifiService( 1034): ACTION_BATTERY_CHANGED pluggedType: 2
D/dalvikvm( 1034): GC_EXTERNAL_ALLOC freed 102K, 38% free 5402K/8711K, external 1591K/1734K, paused 79ms
I//system/bin/tc( 935): RTNETLINK answers: Operation not supported on transport endpoint
I/logwrapper( 935): /system/bin/tc terminated by exit(2)
I/ActivityManager( 1034): Start proc com.google.process.gapps for service com.google.android.location/.NetworkLocationService: pid=1159 uid=10008 gids={3003, 1015, 2001, 1007}
D/szipinf ( 1138): Initializing inflate state
I//system/bin/tc( 935): Cannot find device "ifb0"
[Nook Color Android Development] andrew2pack:
1.2 Ghz kernel for Honeycomb?

I searched the thread for anything thing honeycomb related and came up with nothing. Has a version of the 1.2 Ghz tes kernel been posted that runs with deeper blue's honeycomb preview?
[Nook Color Android Development] Divine_Madcat:
Sorry, no, i have not done any work on the Honeycomb version of the kernel.
[Nook Color Android Development] andrew2pack:
Thanks for getting back to me! I understand, if at any point you decide you want to play around with the HC kernel I would be more they happy to test it. :)
[Nook Color Android Development] funcrusher:
Froyo needs some kernel love. Someone please. ;p
[Nook Color Android Development] newellj79:
I'm noticing a much needed volume increase with the madcat version kernel.
[Nook Color Android Development] poofyhairguy:
Ok, nevermind on the 1.2Ghz overclock. Today my Nook Color mysteriously turned off by itself, when I tried to reboot it completely locked up on the first lock screen.

I then re-tried to reboot it after that. When CM7 booted the screen got completely corrupted and froze. I then used a SD card to reflash the normal 1.1GHz kernel, and I use the CM7 settings to put it back at 1.1GHz and everything is fine.

1.2Ghz is too far for my Nook Color.

Honestly though, the real improvement I noticed was with games playing smoother. At this point it would seem that some real benefit could come from trying to max out our GPU speeds..
[Nook Color Android Development] Shawn_230:
I managed to make CM7 nightly #30 boot stable enough to run Quadrant a few times just one time, the best score I got was over 2100 which was amazing.

Everything worked so smoothly... app drawer loaded completley differently, and overall the Nook seemed like a different device.

But alas, I can't make this kernel work at all again. Either it gets stuck in the reboot loop or it locks after loading the lockscreen.

It was so amazing the one time it worked though, like the Nook had actually recieved a newer better processor.
[Nook Color Android Development] chisleu:
I also have no success with 1.2ghz.

1.1ghz has been solid for me.
[Nook Color Android Development] Divine_Madcat:
Are you trying the 1.2 Ghz kernel, or the "net" kernel? If it is either, try the "nonnet" kernel. The name is a bad misomer, since the system does have working BT and wifi...
[Nook Color Android Development] MedLine:
You and me both ... ended back using dalingrin OC kernel 031611 after flashing to n31. Still tried 1.2Ghz a few times with no real success before that, though.

Here's a reminder for anybody trying the 1.2GHz overclock: uncheck "Set at Boot" before clicking 1190 MHz, that way if system locks up right away or any time after, you can just do a hard reset to successfully reboot (as opposed pulling out the recovery SD to revert to a prior kernel).
[Nook Color Android Development] chisleu:
I have no troubles what-so-ever with the 1.1ghz madcat modified kernel. Runs fantastic at 1100
[Nook Color Android Development] dalamchops:
is it posssible to raise voltage slightly to stabilize 1.2?? Don't seem to be a heat isssue.
[Nook Color Android Development] camwinnn:
What nightly? Been using your 1.2ghz kernel for about a day only using the cm performance settings an haven't had a problem yet.

Thank you btw ;P
[Nook Color Android Development] Shawn_230:
I'm using the 1.2GHz kernel, the third and last linked in the original post.

Maybe I'm being stupid but I didn't see any other choices for dialing up to 1190MHz.
[Nook Color Android Development] l0m31n:
using nightly 31.

1190mhz doesnt run for me in either setcpu or cyanogensettings.

locks up and reboots with cyanogensettings. hangs with setcpu.

1100mhz is stable.
[Nook Color Android Development] newellj79:
1190 not working for me with setcpu or cyanogenmod settings either. 1100 froze up twice on me last night. Never had this problem with the 3/16 kernel. Went back to 3/16 for awhile. Flashing 3/25 again now to test. As I stated a few posts back, for sure there is a volume increase with 3/25 so I really want it to work!
[Nook Color Android Development] ax0r:
I love my nook been on 1.2 and its perfectly stable for me
[Nook Color Android Development] JeremyNT:
Same here. I guess 1.1 ghz is the max for most devices, only a lucky few can hang at 1.2.
[Nook Color Android Development] clayginn:
This is what I am thinking as I also get lock ups at 1.2 with Nightly 30 and now 31. Setting back to 1.1 and no issue so far.
[Nook Color Android Development] FL5:
Just wanted to pop in and say that 1190mhz works incredibly well with mine. Even if it doesn't work for some, it is greatly appreciated by those of us that it does work for.

BTW, 2146 in quadrant. =P
[Nook Color Android Development] ADude:
To clarify for those not familiar with wafer fab:

The chip company is delivering CPUs to B&N to run at 800.

So, the wafers are only tested for that speed, but often the exact same wafers are used for higher speed CPUs, with the only difference being how well the fabrication came out.

There can also be variations from chip to chip on a wafer, and certainly there are variations amongst the various chips provided to B&N.

So, some CPUs may run fine at 1.2ghz, and others struggle to run at 1000.

This is obviously clear to most posters, but might not be to a few reading this.
[Nook Color Android Development] poofyhairguy:
Seems like though everyone can run 1.1GHz fine. That means there is still room to move for most. Honestly from most issues it just seems like at 1.2GHz we need a little more juice...
[Nook Color Android Development] DeadlyDa:
Nightly 31:

Using 1190mhz via cyanogen performance settings. Works perfectly, three Quadrant tests:

1) 1891

2) 2143

3) 2008
[Nook Color Android Development] Divine_Madcat:
I agree, more juice might help, but i am very learn of doing that; i really dont know how much is too much for these devices.....
[Nook Color Android Development] dalamchops:
i'm willing to test out a higher voltage if needed.
[Nook Color Android Development] camwinnn:
Damn can't say that now, froze up on me last night a couple times, gonna use setcpu to see if that will help.
[Nook Color Android Development] dalingrin:
There is a reason I've only released a 1.19ghz kernel. 1200mhz+ isn't stable no matter what voltage you push it to. 1.19ghz is really about the max you can get out of our CPU right now. Even 1.19ghz has sketchy stability. I think ~1.19ghz is the ceiling unless we increase the base dpll clock.
[Nook Color Android Development] ax0r:
This kernel isn't 1200 it is 1190.
[Nook Color Android Development] Nburnes:
Thank you for pointing out the obvious.
[Nook Color Android Development] chisleu:
well played.
[Nook Color Android Development] paleh0rse:
CM7 on Class10 SD, n31, 1190mhz "ondemand".

Best score: 2018

Average: mid-1800's

Nice work!!! and THANK YOU!

Now, if only one of the Gods would figure out the audio-processing issue that's causing the video problems, we'd be all set! :)
[Nook Color Android Development] chisleu:
Yes I am very excited for this as well. Mr Dalingrin said he will be on that when he gets back from his spring break. I've been looking at it, but to say I'm ill prepared is an understatement.
[Nook Color Android Development] Shawn_230:
How much testing have the people who are saying 1190MHz works perfectly fine for them done?

I've got this feeling that you just haven't messed around with it enough? I've gotten it to run stable at 1190MHz but a simple reboot or a tweak in the settings can completely ruin things.

My Nook was fine on n31 and 1190MHz with interactive governor last night, but when I woke up today it had shut itself off and the only way it would turn on was holding the power button for 7 seconds. And when it loaded all the widgets I had set up said "problem loading widget" and the system was overall too sluggish to be usable.

Try and do a bunch of reboots or change the settings a bit in SetCPU (raise the minimum speed or change the governor type) and you just might see things mess up on you. I hope some people really did get better quality 'wafers' in their Nook but personally my Nook has at times seemed fine and others not on this kernel.
[Nook Color Android Development] poofyhairguy:
Instead of dialing it up maybe tweak it down some? I don't even know, but is it possible to maybe run at 1180 instead of 1190? 1170? 1160, 50, etc?

It seems logical that at some level there is a point where most Nooks stop working. All we know for sure is that most peoples Nooks run fine at 1100, but not most at 1190. So maybe if possible all together we can test different ranges to find the optimal spot between those two points (if it is possible to change/add overclock values).
[Nook Color Android Development] Shawn_230:
For the record here's what Quadrant gives me when 1190MHz does run stable.

Sorry for the crap screenshot, actually had to photograph my Nook since screenshot apps don't seem to work on CM7 yet...
[Nook Color Android Development] SCWells72:
I just installed the 1100 no-net kernel and got ~1800 in Quadrant, so this is definitely a nice improvement. Overall interactivity seems smoother, too. I might try the 1190 kernel in a bit, but just the fact that it makes the CM7 settings lock up makes me a little nervous. GREAT work, guys! Between this and the Honeycomb-like usability features, CM7 is becoming one heck of an amazing experience for the NC!!!
[Nook Color Android Development] altimax98:
im doing some tests and the 1190 kernal runs impressive numbers on both 1100 and 800. but sadly it seems that my nook doesnt care for the 1190 speed :( its weird too because the 20 nightly ran it fine, im on 31 now
[Nook Color Android Development] Shawn_230:
So I gave up on 1190MHz and went to the 1100MHz no-net kernel.

At first it didn't seem too much worse than 1190MHz, Quadrant was a few hundred less, say about ~1800 or so... this one doesn't crash like the max kernel but I've noticed it slows down alot.

If I use it for say 20 minutes and then run Quadrant it's only about ~800 or so and the system is very sluggish. This is max CPU set to 1100MHz with interactive.
[Nook Color Android Development] glenairlie:
It seem that the Quadrant benchmark is very flaky.

A benchmark should not return significantly higher scores between the first and (say) third run. That implies it's relying on cached data or some carry-over from a previous run.

If you look at say, -3DMark- on Windows, if you run it multiple times it generally returns the same benchmark result. In other words, it's a true test of your systems baseline capabilities.

Quadrant has some reliability issues imo. Not a great benchmark program...
[Nook Color Android Development] chisleu:
Or that the computing power of our device isn't that high, and background/system processes can greatly affect the results.

Plus there is illusion in numbers. The difference between 1950 and 2050 is really big where the difference between 1.95 and 2.05 doesn't see like as much. :D
[Nook Color Android Development] Divine_Madcat:
No worries.. the "1.2Ghz" is set to 1190 (i figured you had done that for a reason ;) ).

Anyway, thanks for all the continued feedback guys; i am happy to hear that people are having a noticable improvement. As for bugs some people are reporting - i can't say i have an answer for them; this really isn't a new kernel - the only changes were the bug fix, so nothing new should have been introduced (but who am i kidding; as a CS guy, i know the smallest change can have huge results..)

That said, i will note that Dalingrin uses a different toolchain than i do for compiling, which could produce slightly different results. Perhaps i will have to investigate that further.....
[Nook Color Android Development] jtbnet:
Right... There are specific benchmarks for specific subsystems that I would expect to be more consistent... Quadrant tends to be a more 'General Useability' benchmark providing a weighted average of multiple subsytems on each run thus background processing has a sizable affect on the outcome... but all in all I have found that the best of 3 runs to be a good barometer for 'General Useability' overall of the release/version I'm testing...
[Nook Color Android Development] colbur87:
Any advice here. Switched to this kernal from the stock cm7 which i had clocked max at 925.

After trying this out my whole system is lagging.....quad scores from 1500 to 900.

Everything is lagging. Anyone have anything?
[Nook Color Android Development] chisleu:
redownload the kernel and start over.
[Nook Color Android Development] Shawn_230:
So what? Anyone who has used Quadrant knows the first test you do is slightly lower.

I'm only reporting the results as a relative comparison... as long as my system is running smoothly I couldn't care less is Quadrant throws me negative results.

But unfortunately neither the 1.1 or the 1.2GHz version of this kernel seem to work for me beyond just for testing.
[Nook Color Android Development] lschroeder:
1. What Class 10 SD card manufacture and what size?

I have the original verygreen SD card image on SanDisk Class4 4 GB and switched to phiremod nook v5.1 on emmc.

2. Are you running this, his new Size agnostic SD Card image and CM7 installer with updater, or something else?

3. What kernel did you use for the SD card version?

I also need the wizards to figure out the video problems.