yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] suckshardcore:
I was able to install the mod to the SD card no problem. Thanks!!! I do have a question I hope somebody can help with about side loading things to the SD card once the mod has been installed to the card.

I can't seem to get windows to acknowledge anything but the root directory on the SD card. I know it is because windows does not assign drive letters to multiple partitions on SD cards. Is there a way to force windows to assign a drive letter? Or, is it possible to re-size the root partition and just install everything to it? I'm trying to side load a few books from Caliber onto either the Nook or Kindle app. If anyone can provide directions on how to do this I will be very grateful.
[Nook Color Android Development] gordesky1:
Hmm just did a bit of reading a few pages back and saw about 1.21 with oc kernels.

Do i need too install 1.21 for the oc kernels too work? I did 1.3 and every time i try too install the darins oc kernal it will get stuck at a black screen after the cm7 spash screen.

I just finally got netflix working with out chickmunks now i just need too get the overclock kernel working so i can try 1.1 or 1.2ghzs.
[Nook Color Android Development] barbo:
I am still new at this myself so this may not be what you need but I think you need the "NookColorUMS" apk. It works for me. Unfortunately, I am in a rush and can't point you to exactly where to get it. Hope this helps.
[Nook Color Android Development] gordesky1:
Update i got everything working i was updating with the wrong oc kernal which was 033111 which i thought was good sense its linked in the nook links, So i went and updated with 052311 and it went right threw it and im now on 1.1ghzs:)

And makes a really nice difference from 925mhzs, Like in air attack it was a but slow and laggy but now its almost as good as my galaxy tab @ 1.4ghzs:)
[Nook Color Android Development] pchoi94:
How did you get Netflix working without chipmunk sound?
[Nook Color Android Development] :
Try searching the forums. There's an entire thread dedicated just to getting Netflix running.

http://xdaforums.com/showthread.php?t=1078123
[Nook Color Android Development] leapinlar:
You have to change the build.prop file even if you are using the version of the Netflix application that no longer checks for which device you have in order to run. It does still check for your device so it can set some parameters like playing speed. You need to change the model to Vision and manufacturer to HTC.
[Nook Color Android Development] gordesky1:
Yep like others say you have too change the build.prop i got mine set too HTC Vision for model and manufacturer on HTC works perfect after that:)
[Nook Color Android Development] topcaser:
verygreen,

the cm7 download link dont works any more. You have updated it today. Maybe you have a type error??
[Nook Color Android Development] topcaser:
Hallo verygreen,

is this still valid:

The key triggering thing hardly works for me and therefore i have not updated yet. Are you working on this issue - because i will wait until you finished - much more convinient for me :-)
[Nook Color Android Development] jared_c:
It depends on your version of u-boot if you need to hold down the keys or not, not on just on verygreen's script. fattire's menu makes it significantly easier to get into recovery.
[Nook Color Android Development] verygreen:
Ah, indeed. Should have checked it. Should be fine now. Thanks.
[Nook Color Android Development] verygreen:
That bolded section is only relevant when you are migrating from pre v1.2 to 1.2 or 1.3

starting from 1.2 I adjusted timings to make thing easier.

Also once Fattire's uboot with menu hits the nightlies it will become even easier.
[Nook Color Android Development] topcaser:
Ok, thanks to all. I will wait until it becomes even easier.

Just another question: do you recommend to remove cell standby service to boost battery life? I have done this and

I also patched this IMEI stuff for my nightly 85 which I currently running. Now Astrid and XDA app works good.

When I flash another nightly, are these things also gone and needs to be patched again?
[Nook Color Android Development] rhester72:
Removing cell standby does not actually improve battery life.

Yes, any changes to the framework, installed packages, etc. will be reset every time you flash a new build.

Rodney
[Nook Color Android Development] marketingmail:
Reboot into recovery worked

Thanks for posting 93 nightly...was using "update-cm-7.0.0-encore-signed.zip" and could not install gapps/market due to reboot into recovery not working. Now works - Market installed successfully. :)
[Nook Color Android Development] Khegobier:
It's probably already been said, but I'm not reading through 51 pages of posts...

You do NOT need to install CM7, reboot and THEN install gapps. You can copy both the cm7 nightly as well as the gapps installer, and as soon as the CM7 installer is done it will install the gapps package immediately.

You don't need to worry about wifi out of the box, when you get the "phone setup" screen with the "Touch the Android to begin" page, simply touch all four corners of the (black part) of the android screen - top left, top right, bottom right, bottom left - and it should drop you to the launcher screen where you can go in and setup wifi and accounts from there.

By the way, the OP's instructions need to state on the cm wiki page, to download the gapps package, you need to scroll ALL THE WAY TO THE BOTTOM of the page. I stupidly flashed the cm 7.0.3 build 3 times before realizing that that wasn't the gapps package.

hth
[Nook Color Android Development] verygreen:
While it has been said, this method does not work reliably in my testing. I get all sort of weirdness during first run and such.

So I cannot recommend it as the default easy way.

Please suggest the better wording if you think that "at the end there is a table with various google apps versions" is not clear enough. Thanks.
[Nook Color Android Development] danvee:
Thanks VG...

I've been a proponent of this method as it has worked perfectly for me-countless times. (also the fact that getting into recovery mode using the button-dance method still eludes me- and I've played keyboards for over 40 years:cool:)

HOWEVER, as you're the one who went through the time and trouble to create the SD card images that we're using, I'll humbly defer to your knowledge of your own creation.:)

Thanks again for all of your contributions! (still waiting for my adapter to try out the USB functions)

Dan
[Nook Color Android Development] pchoi94:
Degraded performance over time?

Hi all,

I'm running the 7.1 stable release from SD (16GB Class 4 Sandisk with 0.800MB/s 4k random write 32QOD) and noticed that my performance seems to get degraded over time. Is this normal? I'm trying to determine if this is a CM7 thing or if it's possibly something wrong with my SD card?

By degraded performance I mean that I start getting stuttering and lag, and once the nook even rebooted itself into the internal stock ROM even though the sd card was still installed (i just had it sitting there on the nightstand and watched it happen).

It seems like it happens more consistently when I try to watch any type of streaming video. The video almost always stutters and afterward I have to reboot...

btw, does anyone know if there is a utility i can use to test the SD card to see if it's bad?

thanks!
[Nook Color Android Development] rhester72:
I've had the reboot-into-stock happen three times now - I chalked it up to running max overclock (as I too only see it when streaming), but it happened once when paused, so maybe not...

Rodney
[Nook Color Android Development] verygreen:
Autoreboot into emmc is usually a sign of a kernel panic.

When that happens please connect to your nook with adb right away and capture the crash message from /proc/last_kmsg

It would not be specific to SD-card only so we need some place to collect those crashes I guess.
[Nook Color Android Development] shumash:
At the risk of sounding like a broken record, I updated to release 93, reflashed DAl's OC and it broke the wifi. Using the reasoning above, I assumed that I needed to reflash the 1.3 installer, and then reflash Dal's OC. Wifi stayed broken, but was fixed when I reflashed the 1.2.1 installer.
[Nook Color Android Development] verygreen:
Just installer does not touch the kernel so it cannot fix the wifi.

So I am a bit at loss at what exactly did you do
[Nook Color Android Development] topcaser:
Hi,

i have updated to nightly version 94 now which has this change:

http://review.cyanogenmod.com/#change,5911

Is it now easier to get into recovery?

Just another couple of questions:

Am i allowed to remove SD card out of the nook while OS is loaded (but screen off)?

Am i flash both simultaneously: nightly + OC Kernel?
[Nook Color Android Development] topcaser:
Just to inform you: After flashing nightly 94 no framework patch is needed any more to run XDA Free app.
[Nook Color Android Development] verygreen:
No, don't remove it.

this is untested.
[Nook Color Android Development] topcaser:
Double Post
[Nook Color Android Development] giedrys:
It works, boots from SD, except my PC doesn't recognize NC anymore. Also, when I remove SD card and use usb reader to PC, it only shows boot files and 120MB size(i does show everything on NC)

How to "recover" SD card so i can move stuff from PC and how to make PC to recognize NC?
[Nook Color Android Development] acme2ajax:
Updating from your initial update script

Hi verygreen,

Thanks for your sd card image.

I am facing problems in updating with your new installer.

I have installed the nightlies on the sd card and update them by using the following method

1. Replacing the uboot.bin, urecimg & urecram by the one u had posted in earlier forums

2. I place the update nightly file in the sdcard root

3. Reboot into recovery using the keys

4. The penguin logo comes and the card is updated to the latest build.

My query is what is this 1.3 version? Does it contain the updated 0.32 kernel?

To update to a new build, do i need to use the uboot, recimg, recram files i am already using, from your earlier builds?

I am confused...Kindly help me and tell me the process to update the sd card with your new 1.3 installer image.

Thanks
[Nook Color Android Development] zombieflanders:
The installer is just that, an installer. It's not a kernel, those come from either CM7 or the add-ons like dalingrin's overclock. The installer just simplifies the process for putting CM7 on an SD card and booting/updating the software. The version of the installer is only related to the version of the kernel if you're running stable (7.0.3) or nightlies up to 86, in which case you should be on the 1.21 installer. If you are using the nightlies N87 or beyond, you're running the .32 kernel and should be using 1.31.

BTW, you're making the install process waaaaaay too complicated for yourself. There's a specific section in the first post that says "How to update if you already installed using older version of the installer and don't want to reinstall" that makes it very easy. There's no more need for all of the file replacing you do. After you follow those steps, all you need to do is put the nightly ZIP in the "boot" (not "root") part of your SD card and boot into recovery.
[Nook Color Android Development] Homer_S_xda:
I think there are two question you are asking:

1) How to remove the four partitions and reformat the card in Windows? Easeus Partition Manager Home Edition

2) How to mount the data partition so it can be seen in Windows via USB? Search for NookColorUMS.

Homer
[Nook Color Android Development] GTT1:
I am using CM 7.0.3 on a 4gb card and it has been working wonderfully for about 3 weeks. Lately I see a bit of lag when page turning in my reader and getting emails.

I haven't added or changed anything and wonder if this is a cache buildup or something?

Any suggestions on what to possibly clear out to get back to full speed?

I had tried 7.1 but experienced some wifi problems so dropped back to CM 7.0.3 can anyone recommend any stable versions that are newer to try?
[Nook Color Android Development] verygreen:
Instead of updatind u-boot and other stuff by hand, just use the provided update file (see in the upgrade section).

The non-recovery kernel is provided by the update you are installing.

Please see the upgrade section. You just download the update zip for the installer, install that via recovery, then drop in the nightly you want to update to and install that.
[Nook Color Android Development] shumash:
Except that the update has a different u-boot.bin and, if you want to keep the current installer, you need to remove that u-boot.bin file from the update zip, otherwise you have to replace the CM7 u-boot with fattire's again.
[Nook Color Android Development] zombieflanders:
:confused:

There's nothing in the post that I responded to about fattire's u-boot.
[Nook Color Android Development] shumash:
Yah, I probably shot off my fingers without thinking first. I use fattire's u-boot and I've gotten used to removing the u-boot in the update so that it doesn't get overwritten. Sorry, no offense.
[Nook Color Android Development] acme2ajax:
Hi zombieflanders, verygreen, shumash..(did i miss anyone?)..

Thanks for your help. Yes...i was using wayyyy to complicated method for updating....didnt know i could reboot into recovery by just pressing the power off + n button...

I was able to update to latest nightly with verygrens 1.3 version and installed dalingrin's 5/23 OC kernel. Running smooth till now...

However...(there will always be a 'however'), I seem to have lost adb....when i connect the nook and give the command adb devices...no device is listed under the 'List of Devices attached'. It used to work before I updated. Is this a nightly problem? (Nightly 93 btw)

Any method to enable adb again?

Again.....Thanks for all your help......
[Nook Color Android Development] shumash:
Did you check in Settings/Applications/Development to make sure you've got USB debugging enabled?
[Nook Color Android Development] acme2ajax:
Hi shumash,

The USB debugging was already enabled. I tried disabling it, rebooting, enabling it and then reboot again....The Usb connected dialog shows...to mount the sd card...but the usb debugging is not shown....

Helllppppp!!!!!! :confused:
[Nook Color Android Development] stolenmoment:
Why fstab.vold for /mnt/emmc?

Verygreen, I have a real technical question for you: why did you use fstab.vold to manage /mnt/emmc instead of mounting it directly like you do /cache?

Does using vold/179:20 for /sdcard allow for exporting it via USB? Can somebody point me to doc for this facility? I'm an old Unix/FreeBSD kernel hacker but new to Android, so I understand a weird mix of stuff.

My mmcblk0p8 filesystem got corrupted (my own damn fault), and CM7 wouldn't mount it or export it, so I've been inspecting your scripting...

My busybox doesn't have mkfs.vfat, so I dd'd blk0p1 onto blk0p8 to give it a filesystem. It got mounted properly when I rebooted, so I'm back up.
[Nook Color Android Development] verygreen:
Well, the line was already in vold config, so it was easier to change it than to delete it and to add another line to the init file to mount sdcard storage.

After all the emmc "free" area is also mounted via vold and it's not like you can eject internal storage ;)

I am not very verse in Android myself ;)

I know you can echo stuff to /sys to change what is exported. (you can find it by searching in this thread I think)

By default /sdcard and /sd-ext are exported. You need to enable "usb storage mode".

You could just took a "nooter" image floating around and booted off that, that one is debian-based and has mkdosfs and such. (which is what you are looking for, not mkfs.vfat anyway).
[Nook Color Android Development] pchoi94:
Super Noob Question about Nightlies vs Stable/Beta

Hi, I just installed the latest nightly (97) and I'm wondering: does it incorporate the deep sleep improvement that was introduced in 7.1 Beta, thus improving battery life?

I didn't see anything in the change logs about it specifically and I don't know where the stables/betas end and the nightlies begin... are the current nightlies built on the 7.1 beta, or are they branched off from a totally different line?

Thanks!
[Nook Color Android Development] lanyao1920:
cool, a must have for nook color owners :)
[Nook Color Android Development] Thirtybird:
Had your EXACT same problem for the longest time! Using installer 1.1 and I had ADB, using 1.2.1 or 1.3 and no ADB. Other devices woulad work under ADB just fine as well, so it seemed like it was the installer....

It turned out to be an old ADB driver for windows. I went and ran EasyADB 0.2 setup and it updated the drivers I had, and then I was able to see the Nook using the 1.2.1 or 1.3 installer.
[Nook Color Android Development] GTT1:
Have installed Nightly 98 to SD card and it seems to be running okay so far.

Would like to add an overclock kernel. What is recommended for the latest nightlies. Is the best approach to use the May 23rd one?
[Nook Color Android Development] zombieflanders:
There's an updated OC kernel dated June 9, check the dedicated OC thread for both the kernel and the Nook Tweaks app that works with it.
[Nook Color Android Development] shumash:
Here's what worked for me:

http://xdaforums.com/showpost.php?p=12092206&postcount=86

To find out which USB Storage Device has the proper hardware ID, you'll need to connect the NC to your PC. Be sure to disconnect it before you update the driver, though.
[Nook Color Android Development] rhester72:
Stupid question, but how does one go about clearing things like Dalvik when everything is on SD and there is no CWM?

Rodney
[Nook Color Android Development] verygreen:
go into adb shell and do

rm -rf /cache/davlik*
[Nook Color Android Development] fastoy:
Backup CM7 MicroSD

Thanks to all who have contributed to CyanogenMod7. These instructions were easy to follow and the results incredible.

I do have a follow-up question and the moderators are welcome to move this to the appropriate forum.

How do I backup the microSD card I created? I am a Windows 7 user and tried using win32diskimager to create a .img file from the microSD but when I wrote that .img file back to another microSD the Nook Color wouldn't boot from it.
[Nook Color Android Development] rhester72:
I use WinImage without issue.

Rodney
[Nook Color Android Development] rokkywoof:
Step-by-step Details/Linux?

How about updating the 1st post (looking as though it is "sticky-ed") with more specifics of the SD creation/usage process (including for Linux-based)?

For example, reading:

"Write the image on your SD card...

After done with writing, eject and then insert the uSD card into your computer."

This has me wondering exactly how "write" is to be done (seeing mentions in posts of a Win utility and/or "dd"), and in what context (looks like on a Wintel PC with that Win utility, or Linux with dd). The eject/insert bit seems as though it should be written as eject/RE-insert (i.e. same PC as it was burned in), etc.

I have just skimmed through 900+ postings over 95 "pages"/several months, and picked up helpful details, but they are a bit confusing in the context of the full process over so many posts. That is a lot of "evolution" to digest.

Clarifying these points in the main how-to at the beginning of this thread so we know more of the details of the results that

should

be happening (partitions/directories/files), and where (PC, card, tablet, etc) would be a hugely helpful sanity check.

TIA,

R
[Nook Color Android Development] verygreen:
Ok, I incorporated some changes. I don't have Windows and have not used it in quite a while so I cannot help with any WinImage questions. I know there is some special mode need to be usedthere and not the other, but that's about it.

Thanks.

If anybody have any proposed enhancement to the text, share them with me. I know my doc-writing skills are somewhat lacking.
[Nook Color Android Development] TabletConnect:
I believe "burn" is the correct terminology instead of "write" at least that is what I hear more common. One burns an image not write.

On a different note, which nightly is the most stable (87 or higher) that people have not have had issues with especially with the WiFi. I had WiFi issues with 85.
[Nook Color Android Development] topcaser:
Every nightly is very stable. I have no problems at all with wifi. Just use the latest 99.

just another question:

I have one app (oi file manager) which market tells me is out of date. As soon as I update it, nookie tells me, that update is failed. I cannot uninstall it since nookie tells me it's a system app. So what can I do?
[Nook Color Android Development] verygreen:
That;s a known problem, ignore it for now.
[Nook Color Android Development] topcaser:
OK, thanks verygreen.

Another question regarding the nighlies:

I have installed an alternative keyboard (swiftkey). When nookie is rebooted it forgets that swiftkey is selected - so i have to select swiftkey again in keyboard settings and switch input method again.

Is there something i can do?

BTW: This forum knows answers to almost all questions. Big big thanks to the entire Forum
[Nook Color Android Development] loveubuntu:
some questions

Excuse my ignorance on the Nook, have only had it for a day:

I used this method in conjunction with this website to accomplish what is intended here and was successful. Thank you very much. I do have some questions though:

1- I flashed CWR through rom manager when I was booted in through my sd card. But I can't get to the familiar CWR recovery menu. I did see it once when I was installing-uninstalling the sd card though. I may have accidentally pressed a combination of buttons. Is there a way to get there? I am assuming that since my nook really isn't rooted and the hardware is really running the sd card, my OEM boot is untouched. So it must be somewhere on the sd card. It's been driving me crazy. Any help is appreciated,

2- The Nook app from the market is very laggy. I am running the CyanogenMod nightly 100 (today's update) and the buttons at the upper right corner of the nook app (search,settings, go to shop and help) do not always work and have to be pressed a few times. Is this everyone's experience? Can this be improved by running a different kernel? it does look like it maybe the app's problem though.
[Nook Color Android Development] fastoy:
I hadn't noticed this before but I see the sluggishness from those buttons as well. I wondered if it was related to the Nook Color's decreased sensitivity around the edges of the screen so I tried Pulse. The Pulse.me button is in the topmost right corner and it is responsive.

Interesting the Nook app presentation on my Samsung Captivate is completely different.
[Nook Color Android Development] tjohnso1:
Hello, and thank for making this change for the Nook so easy to follow. Works pretty good. I've got CM97

Just a few questions/issues:

Webbrowser: seems that some pages seem to "hang" after a while, and swiping the page up or down no longer works. Facebook is a page where this happens often

The other day i put the nook down for a few hours, and when i came back it had rebooted into the Nook operating system. The SD card is still in the nook?

This prompts another question: is there some way of booting back and forth the nook from CM97 to Nook OS, and back? With the SD still in the nook?

thanks again!
[Nook Color Android Development] loveubuntu:
Hmmm, I don'tthink that's the reason. The soft keys in cm7 are at the very bottom left. They work fine when the Nook app is off but sluggish when the Nook app is up. Can the Nook app have less sensitivity to touch at the extreme edges? If yes how dumb for them to place buttons up there?

Any takers for the first question? Is there a way to get to cwrecovery menu in this method?