yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
If you want to use it with your bootable CWM SD recovery card, do what you suggested, name them uImage and uRamdisk, and put them on the boot partition of the SD. These files only work for emmc installs. They are hard coded to read the partitions there. (Don't put them on your SD installed CM9).

If you want them on emmc, you rename them uRecImg and uRecRam if you want them to be your primary recovery. If you want them to be your alternate recovery name them uAltImg and uAltRam. I use NookColorUMS to mount the boot partition then you can see it on your PC and can copy these files to it. But that program only works on CM7 since CM9 does not support UMS. I'm not sure how to get these on your emmc boot partition if running CM9. Maybe with adb? Someone else will have to tell you how to do that.
[Nook Color Android Development] RETIEF:
Thanks

Thanks for your help. I would like them as my primary recovery and I am running CM9. I guess I'll wait for help. But you have given me some ideas. Thanks.

Figured it out

$ adb shell mkdir /data/mnt

$ adb shell mount -t vfat /dev/block/mmcblk0p1 /data/mnt

$ adb shell cp /data/mnt/uRecImg /data/mnt/uRecImg.old

$ adb shell cp /data/mnt/uRecRam /data/mnt/uRecRam.old

$ adb push uRecRam /data/mnt/

$ adb push uRecImg /data/mnt/

$ adb reboot

I used ADB Wireless to connect.
[Nook Color Android Development] racks11479:
you seem to be missing a dependency "/usr/bin/ld: cannot find -lstdc++" ?
[Nook Color Android Development] alunral:
How would I get this? I can't seem to find anything pertaining to it, nor do I know what it is.
[Nook Color Android Development] numus:
Try 6 instead of 7.. 7 was giving me lag and stability issues.. 6 seems better.
[Nook Color Android Development] bigbob23:
Probably libstdc++.
[Nook Color Android Development] alunral:
Ended up getting it to work. Had to install libcr-dev before it would finally decide to work. Thanks for the help everyone! Especially kxfdadev!
[Nook Color Android Development] KingJL:
Power Switch Menu (Airplane Mode)

I don't know if this has been addressed previously (I did a search of this thread, but found nothing directly related). If it has been previously addressed, I apologize!

I tried toggling airplane mode via the power switch menu. I can turn airplane mode "on", but cannot toggle it "off" via the power switch menu. Also if I then turn off airplane mode via the status bar settings and then try the power switch menu, airplane mode is said to be "on" (even though it isn't). Also, if airplane mode is set to on via the status bar settings and the unit is rebooted, the power switch menu indicates that airplane mode is "off" (but it is actually on in the status bar settings).

I was hoping to use the power switch menu to toggle airplane mode off/on as an easy way to quickly enable/disable wifi without having to try to switch wifi on/off in the status bar settings (which can be frustrating without a stylus).

EDIT: It might be helpful if I list my environment: evergreen SD CM9 (eyeballer's build 3/5) w gapps 20120304
[Nook Color Android Development] alunral:
I feel like I'm posting in here a lot. Is wallpaper scrolling supposed to be broken at the moment? And is there a way to change the portrait keyboard's size, that thing is just way too big. Otherwise, I'm liking it! Big thanks to fattire and everyone for it.
[Nook Color Android Development] Nburnes:
Wallpaper scrolling works if opengl is enabled.
[Nook Color Android Development] alunral:
How would I enable this?
[Nook Color Android Development] mrapollinax:
You would need to flash a ROM that has OpenGL code compiled.
[Nook Color Android Development] cybertimber2007:
This is a problem in CM7 as well and seems specific to the nook. Can you get a logcat of it? I'm not aware of it being solved in CM7 either, but it would be nice if it was... it was a pain to get out of airplane mode.
[Nook Color Android Development] KingJL:
No, that is another issue I have... cannot get adb to work with the NC (don't think it is a problem with CM9). adb worked with my Samsung Infuse, but not with my NC... cannot get the right drivers to load. DM shows it as a Nook Color with no drivers loaded. I have tried all of the NC adb hacks to no avail. I have a sneaking suspicion that it may be because I am running CM9 from SD.

I agree!

I noticed some other strange behavior concerning airplane mode ( If I have wifi set to sleep when not on charger power ):

If I put it in airplane mode from the power sw menu, then use the status bar to take it back out of airplane mode, turn off the display and let the unit go to sleep; when I later wake it up, the wifi shows no connection (as expected) but then wifi wakes up and connects ( a desired behavior, but completely unexpected because I thought that wifi sleep/wakeup would not work). I can get this behavior only by using the previously described sequence. Of cousre once I toggle into airplane mode with the pwr sw, the pwr sw menu always indicates "Airplane mode is on" regardless of the setting in the status bar menu.

The above behavior was noticed while running eyeballer's 3/5 build. I have now moved to eyeballer 3/7 and have yet to further test the above sequence.

Current envirionment:

SDCARD CM9 (eyeballer 3/7 w/OpenGPL) gapps 20120304
[Nook Color Android Development] leapinlar:
No, it's not because you are on SD. You have to change the device id in your Windows device driver setup. Search for a post I made about the subject a couple of months ago.

Edit - Look here:

http://xdaforums.com/showthread.php?p=21665649

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] KingJL:
I have not been able to re-create this behavior with the current ROM.

I believe that I have solved the issue that I was trying to address with the "Airplane Mode"... that being prolonging battery life when wifi is not needed by easily disabling wifi. I have set Keep Wi-Fi on during sleep to "Always" and installed "GreenPower" app which is supposed to manage wifi automatically. We will see!

Current envirionment:

SDCARD CM9 (eyeballer 3/7 w/OpenGPL) gapps 20120304
[Nook Color Android Development] mateorod:
I know that this is a little old, but I think I know what your problem is. I am building right now and read the bug report. There is an easy fix.

(This info care of fat_tire)

Open and edit external/mesa3d/src/glsl/linker.cpp and somewhere around line 67 (where you will see a bunch of other lines with #include), add:

#include <stddef.h>

That's it.

Include the #!

The write-up on the bug is here: http://code.google.com/p/android/is...3d&colspec=ID Type Status Owner Summary Stars

I don't know if that's your problem, but it looks likely from here.
[Nook Color Android Development] alunral:
No, that wasn't the bug at all, was one of the first things I tried. I fixed it, though, and gave an example on what I did. Thanks, though.
[Nook Color Android Development] Larteas:
I've the same problem, just edit /system/build.prop, look for "ro.wifi.channels" and set it to 14 (it should be empty).

Reboot, done!
[Nook Color Android Development] leapinlar:
You just gave me an idea and I tried it and it worked.

To put the new 5.x CWM Recovery files on your emmc installed CM9, just use root explorer and terminal emulator.

Make a new directory in data with root explorer. Like /data/mnt.

Go to terminal emulator, type the following:

su

mount -t vfat /dev/block/mmcblk0p1 /data/mnt

Then go back to root explorer and go to /data/mnt. Your emmc boot files should be there.

Just rename and copy the uRecImg and uRecRam files like you did in your post.

Reboot into recovery and you should be there.

The beauty of this method is you never have to hook up to PC or use adb.

Edit: even though I came up with this easy way to install the files, the recovery does not work right on my system. I have CM7 on emmc, but that should not make a difference. When I boot to recovery, I get a lot of error messages scrolling by, most of which deal with the recovery.fstab lines being wrong and NULL not being a valid option. Then when I try to backup, it only does /boot and quits. Anyone else having these problems?

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] seth.i.simmons:
Yep, getting the same problems here, I get a bunch of errors related to recovery.fstab and it doesn't have access to anything but boot. Would love to be able to use it, not really sure why it doesn't work correctly! I also have a flashable zip of it I can upload if someone wants it...
[Nook Color Android Development] Dj-Gutz:
Attention to devs , Defy seems one step closer to full hwa

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

Quarx git : https://github.com/Quarx2k/android_device_motorola_jordan/commits/ics

Interesting commits?

https://github.com/Quarx2k/android_...mmit/292b716f9727ca1dd8355bdc299650f052ea197f

https://github.com/Quarx2k/android_frameworks_base/commit/638abf5b347e0d11ae2d06be0e1f64c19d9f9213

https://github.com/Quarx2k/android_frameworks_base/commit/5d9ec4d70ea3207471cf0f24f73efb51b0c478d5

https://github.com/Quarx2k/android_frameworks_base/commit/135a9a7f21a0c4b5b97f08a762282aaf22e11600

https://github.com/Quarx2k/android_frameworks_base/commit/3a5514906d0c779a12e5e3ccb8bed880705b93af
[Nook Color Android Development] johnny15:
Pardon the ignorance.... how does this affect the NC?
[Nook Color Android Development] Harlley Sathler:
If I'm not wrong, Defy uses the same gpu as nook color.
[Nook Color Android Development] boomn:
Same PowerVR SGX530 graphics chip as the Nook Color, so they're dealing with the same driver issues and solutions from the Defy can possibly be applied to the NC as well. I believe it's the only other Android device with this GPU that has any significant community development going on. Other devices with the same GPU include the Droid X, Droid 2 and LG Optimus Black
[Nook Color Android Development] fattire:
Cool! Someone want to try applying these and let me know how it works? This is the nice thing about writing a tutorial on how to build-- I can be lazy :)

If no one takes it up, I'll give it a shot, but I'm out of town now so my time is a bit limited...
[Nook Color Android Development] leapinlar:
For those of you that use my 240 dpi soft key patches, the latest nightly finally broke my earlier patches. (It added some nice stuff though, profiles, swap storage, rotation settings, etc.) You need to download and flash my latest version. Get it here (rev7):

http://xdaforums.com/showthread.php?p=22444148

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] HacDan:
These look Tegra 2 related for the most part, no? (I don't have hardware to test on anymore, so =/)
[Nook Color Android Development] tonyp:
It's confirmed by LG that the Optimus Black will get ICS in the 3rd quarter 2012. If LG confirmes anything it usually means that you have to wait three month longer - but they will release it.

If they do - does that mean that we can get full hardware acceleration using their binaries? Would be great news. I don't mind waiting but it would be nice to know that at some future point we will have a full functional ICS to use the new gapps and tablet optimized apps.
[Nook Color Android Development] mateorod:
I obviously saw the same thing on the commits you did. But the defy doesn't have a Tegra 2. It has the exact PowerVR gpu and the CPU can't be that different (defy=OMAP 3610, nook=3621).

Very similar specs. I can't tell you what those commits are trying to do, though. Looks ported in from another device. There are mentions of nvidia in there as well.

Edit: which could be related to the fact nvidia makes the Tegra. Whoops.
[Nook Color Android Development] leapinlar:
Fattire, I just noticed something about the new Cyanoboot. After the screen starts showing the "Loading..." message, the message "Hold n for menu" still shows. I noticed this yesterday when I was showing a new user how to operate the Nook Color. She waited too long to press the n and could not get it to work even though it still said to press n. I don't remember if the old version did that. Can that be modified so that it does not show once loading is displayed? Maybe have it at the same location on the screen so it is overwritten by loading. It's confusing for new users.

Edit: One other thing, if you have your SD out and press n, the boot menu comes up, as expected, but if you select any of the SD options, it hangs when trying to boot rather than giving an error message.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] afzalarsalan:
I think that the Defy rom probably used some of the code Fatire may have created. :D According to the Github, there doesn't seem to be any recent merges related to graphics.
[Nook Color Android Development] ew2x4:
Is hwa the thing keeping us from being able to use netflix and hulu plus?
[Nook Color Android Development] johnny15:
Has anyone been able to test these? Curious if this will provide any benefit to us NC owners.
[Nook Color Android Development] Dj-Gutz:
I don't know of anyone who tried but we should probably wait

TI has released some updates for kernel 3.0 ( still wip ) that will probably have to be backported , Galaxy sl i9003 devs are working on that

I know keyodi is working on a 2.6.35 kernel , not sure of it's current status but you can get it from his github account and see for yourself

And we might also benefit from NT 3.0 kernel progress in the future

I'm sure the devs will update us when theyll have significant improvements
[Nook Color Android Development] HacDan:
I had no idea TI was even dropping anything for omap3 anymore, so if so, this is awesome news as the android 3.x branch is lacking in omap3 innards.

In regards to 2.6.35:

What isn't working:

*wifi

*sleep

*sound

*other things I'm sure... but those are the main ones
[Nook Color Android Development] keyodi:
@hacdan

How's the battery drain with fix?
[Nook Color Android Development] HacDan:
1% over 15 hours
[Nook Color Android Development] keyodi:
Thanks for testing

I made a change to the kernel in order get the sgx drivers to powerdown on suspend/resume which should reduce the amount of battery drain during sleep. Based on hacdan's and my testing battery drain has been reduced from ~1% an hour to ~1% every 8-15 hours w/ wifi off. But before I push the change i would like a little more testing to ensure that it doesn't break anything else.

SGX change: source + modified KERNEL_VERSION(2,6,35) to KERNEL_VERSION(2,6,32)
[Nook Color Android Development] seth.i.simmons:
Awesome, testing the new uImage right now! Thanks again for all yalls great contributions to the NC, you make it an amazing tablet!
[Nook Color Android Development] RETIEF:
test of kernel
[Nook Color Android Development] racks11479:
Huuuuuge difference here for me as well. Another thing was Deep Sleep was a hit or miss with the previous kernel for me. Now it's sleeping like a baby. And battery life already has improved tremendously. Had no battery drain leaving my nook uncharged overnight (that's 6 hours for me) :D

Thanks,

Racks
[Nook Color Android Development] greiland:
Quick question: Is it supposed to deep sleep while it's charging? Installed CPUSpy to monitor deep sleep. Had it plugged in overnight and it didn't go into deep sleep. Looks like it sat at 300MHz. Does it only go into deep sleep when it's

not

plugged in? Thanks!
[Nook Color Android Development] leapinlar:
It's not supposed to sleep while plugged in.
[Nook Color Android Development] KingJL:
I noticed this as well. Previously, it did go into deep sleep while plugged in. I don't think that that is an issue, as I can see no benefit to deep sleep when plugged in. But it is a difference and a data point!

It is getting more deep sleep when not plugged in (which IS beneficial). It is too early for me to give quantifiable numbers for comparison, but I do see an increase in the ratio of deep sleep vs non-deep sleep. With the older kernel, deep sleep was always <= non-deep sleep, now it is running > 50% (if I leave it alone enough).

evergreen SD, CM9 (eyeballer 3/15), gapps 20120304, keyodi's modified 2.6.32.9 kernel.
[Nook Color Android Development] leapinlar:
I know in CM7 when it was plugged in, the cpu was set to 600 and deep sleep was disabled. It may be different in CM9. I just got some deep sleep while plugged in, not much, but a little. And the cpu seemed to be at 300.
[Nook Color Android Development] mateorod:
Deep sleep working well. Had the kernel in since late last night, and sleep has become more reliable. Used to have no deep sleep when I manually turned the screen off, but that is no longer a problem.

Thanks for the new kernel, keyodi. I had been hearing about it, nice to try it out.
[Nook Color Android Development] KingJL:
After 5 1/2 hrs, deep sleep is a 72%. That is the best I have ever observed!

Is it possible that the wifi driver in keyodi's modded kernel is differnent than the one in the fattire kernel distrubuted with the eyeballer 3/15 build. My wifi had been waking up automatically when the screen woke up. Now it does not!

evergreen SD, CM9 (eyeballer 3/15), gapps 20120304, keyodi's modified 2.6.32.9 kernel.
[Nook Color Android Development] bass0324:
How do I go about including this with my Rom? Does it just get installed like any other zip or placed in a Rom file before flashing?
[Nook Color Android Development] KingJL:
I don't know about anyone else, but since I am running from SD, I just replaced the uimage on the root of my SD with the uimage contained in the zip!

evergreen SD, CM9 (eyeballer 3/15), gapps 20120304, keyodi's modified 2.6.32.9 kernel.
[Nook Color Android Development] bigbob23:
When running from eMMC, there does not appear to be a uImage file.
[Nook Color Android Development] DizzyDen:
The EASIEST method to customize any ROM... of course... this is just my personal opinion ;)
[Nook Color Android Development] leapinlar:
The wifi driver is not in the kernel. It is in the kernel module (twlan_drv.ko in /system/lib/modules), which is like a supplement to the kernel. Keyodi did not change that, just the kernel itself. The kernel module is the thing "Embedded" modded months ago to prevent SODs and is included in the patch zip that I and several others flash after every nightly to prevent SODs.
[Nook Color Android Development] bobtidey:
That's effectively what I did to use this. I took the latest nightly zip opened it in 7-zip. Deleted the kernel file from the top folder. Dragged the new uImage file from the supplied zip onto desktop. Renamed it to kernel (all lower case). Dragged it into the top folder of the nightly ROM. Then flashed as normal. The kernel file gets named to uImage by the ROM install script.

Obviously you need to repeat if using a later nightly, but I suspect this one is going to be a base feature pretty soon based on the feedback.

Thanks for this update which is running fine for me.
[Nook Color Android Development] KingJL:
I am just exploring what might be different to cause the above noted behavior. I have been testing eyeballer's builds without any patches for a baseline on progress of the Nook Color CM9/ICS effort.
[Nook Color Android Development] HacDan:
Was wifi turned on? If you read keyodi's post, you'll notice he said with wifi off.
[Nook Color Android Development] KingJL:
I understood that for the purpose of comparing battery drain. But, he also wanted to see if anything else was broken! The battery drain effect of the kernel change was significant and noteworthy, but if the wifi operation is affected, it should be noted and at least discussed. Maybe keyodi would like to know (maybe not).
[Nook Color Android Development] keyodi:
What do you have Keep Wi-fi on during sleep set at?
[Nook Color Android Development] HacDan:
I'm almost positive this issue existed before this change. At least I've experienced it and keyodi has as well.

There were no changes to anything that has to do with wifi, so =/

---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------

Judging by the battery % drained, I would guess it is set to 'always on'.
[Nook Color Android Development] leapinlar:
What % drained? He did not say anything about that.

He has it set to be off when screen off. That is when it experiences the wifi not coming on when the screen is turned back on. It has been doing this for a long time, but what he has said is the last few nightlies it has not been doing that. And now, apparently, with this new kernel and the same nightly, it has started again.

He was just adding a data point for Keyodi.
[Nook Color Android Development] KingJL:
Where did I say anything about battery drained? I said deep sleep was up to 70% of total cpu time!

You must be reading what you want to hear/see.

---------- Post added at 07:11 PM ---------- Previous post was at 06:55 PM ----------

I believe it was never (would have answered sooner, but just got back from dinner... had SOD had to reboot).

My wifi had been operating (going to sleep and then waking up) fine since eyeballers 3/10 (3/10 - 3/15) build. Battery drain was ~2 - 2.5%/hr overall).

@keyodi, I appreciate your efforts in trying to improve the CM9 for the Nook Color. My observations are only meant as information and a data point for your endeavors. I think that I have not stated a complaint (if I did, I surely did not mean to).
[Nook Color Android Development] leapinlar:
If you have it set to 'never', then you have wifi on all the time. If so, there is nothing to turn back on, it has been on all the time you were sleeping. I only experienced the issue of not turning back on/reconnecting when I have it set to 'when screen off'. Screen goes off, wifi turns off, screen turns on, wifi supposed to turn back on and reconnect. Mine would turn back on but not reconnect.

Edit: forget that! I was wrong! Never means never keeping it on during sleep. Sorry.
[Nook Color Android Development] KingJL:
@leapinlar, I do not have those options (those are options in CM7). My menu reads:

Keep Wi-Fi on during sleep

-> Always

-> Only when plugged in

-> Never

I have reverted back to the original kernel and am doing some re-checking! Thanks for the input.
[Nook Color Android Development] leapinlar:
you are right. I caught the error and edited, but you beat me. LOL
[Nook Color Android Development] KingJL:
@keyodi

I have reverted back to my original kernel and settings. I was wrong about my keep wi-fi on settings. It was set to always.

But the funny thing is wi-fi was powering down when unit was in a sleep. When I would wake the system up the wifi icon would not be showing, i go into my browser, it would immediately go to 'page not found'. After hitting the refresh a couple times the wifi icon would appear and the browser would go to the page (Google in this instance).

I will now collect sleep and battery usage for a few (maybe 24) hrs, then put in your modded kernel, and measure the improvements (I know there are improvements, because I did see more deep sleep time) and the effect, if any on wifi.

Thanks again for your efforts and sorry for the confusion!