yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] DizzyDen:
I've ran it for a long time off Wintec 16 GB cl10 card... only issue I had with them is the initial partitioning and formatting... once I got around that... have had no problems.... however... sandisk class 4 16 GB had no issues partitioning/formatting and runs just as well.
[Nook Color Android Development] topcaser:
Hi

First of all: thanx verygreen for this wonderful description.

I have two issue:

1. My nook is a little bit laggy. Is this because of the sdcard? I am using class4. I havent installed overclocked kernel yet but activated 900MHz in cm settings

2. I have messed around with statusbar settings and cant drag it qnymore.
[Nook Color Android Development] waktasz:
Swapping out my ****ty pny SD card and using a sandisk fixed all my problems. Both are class 4
[Nook Color Android Development] GTT1:
I have encountered a problem which hopefully someone can help with.

I had updated my SD to CM7.1 with OC and updated to the 1.2.1 zip but ran into problems with wifi not activating itself so decided to go back to my stable version of 7.0.3 and before booting up I applied the new 1.2.1 zip from OP and booted by the power (n) method to load it.

It flashed the file but then my screen went into a faint backlight condition and no skateboarder came on. Waited a bit then thought well I will just power down and power up again. Same backlight no skateboarder. Pressed power once and screen went black, pressed N and screen came up with everything now seeming okay and programs run.

If I press the power button and get tablet boot options and go to reboot I now load into NC system not CM7.

The problem seems to have occurred from the 1.2.1 zip file, I had previously used this on my CM7.1 SD and wonder if this file gets into NC OS and by running it again it has caused a problem. This doesn't seem the case because I tried a backup SD I made with 7.1 on it and it works fine.

For now will just format and reload my previous setting without the 1.2.1 update until I get some advice.
[Nook Color Android Development] angomy:
You're the second person to assume it's my SD card. I'm running on a Sandisk class 4 that I've Crystalbenchmarked at decent r/w speeds and has been stellar on stable and nightlies, so I'm betting it's a beta issue.
[Nook Color Android Development] jrid32:
Anybody else able to download the installer image? Bad link?
[Nook Color Android Development] danbutter:
This one?

http://nook.handhelds.ru/sdimage/generic-sdcard-v1.2.1.img.gz

Worked for me just now.
[Nook Color Android Development] stargaterules:
Hmmm, I was able to run CM7 just fine and then I tried to update to the newest nightly #76. It seemed to have installed the file, but then when I rebooted and it passed the loading screen it just sat there on the dark screen with a faint blue line in the corner. I can boot into 1.2 firmware just fine. I don't know what the problem is. Help?
[Nook Color Android Development] stargaterules:
NVM, I went back to #75 and it worked. I think there may be something wrong with nightly#76 as I tried it 2x. I also noticed the file is bigger, not sure that has anything to do with anything....
[Nook Color Android Development] topcaser:
My nook is so slow. Iam on the nightly build 76 andere using a pny class 4 card. Anyone with the same Problems?
[Nook Color Android Development] bonzer2u:
get a sandisk class2/4, u will b shocked......
[Nook Color Android Development] topcaser:
OK, is it possible just to do a copy of the SD Card in windows, or what is your suggestion??
[Nook Color Android Development] neoshi:
1.2.1/7.0.3 stable is being odd for me too. I loaded 7.0.3 stable because .32 was too laggy and now I can't get into recovery by selecting it in the reboot menu. It just boots straight back into the GUI. But luckily you make it easy enough to just toss both 7.0.3 and gapps on at the same time so I don't have to boot into recovery to load gapps. ;)
[Nook Color Android Development] waktasz:
You can use Windiskimager to copy the card, then use it again to write it back to your new card
[Nook Color Android Development] Taosaur:
I noticed with the new image that sometimes the boot to recovery is so fast, especially flashing kernels only, that I literally miss it, and apparently vg got it sorted to reboot itself when it's done, so for instance when I flashed back to 7.0.3 + 4/24, I didn't know whether I'd booted into recovery previously or gone straight into CM7 until I went into settings and checked my version and CPU settings to see yes, everything had installed.

Now, though, I'm getting force closes, particularly a process called something like android.media, and parts of the market--I'll try to do a search or go to My Apps and get a force close message, but rather than close entirely, the market just shunts me back to the last screen I was looking at.

I have installed a lot of widgets, particularly Pure Messenger and several Pulse feeds, so that may be a factor. I'm thinking about migrating to eMMC in the near future, maybe flashing Phiremod. I already have CWM on eMMC, so it should be pretty simple.
[Nook Color Android Development] angomy:
I was having some weird issues with Market only (slow downloads, then intermittently dropping wifi connection only during market downloads) so at first I flashed back to beta1 (was using OC .32 kernel). That didn't fix it, so I next tried to flash gapps back onto my install, and now it's not going into recovery using power + n. Just does the first loading screen, flashes, second loading screen, to a blank black (backlit) screen. After ~30 sec or so it turns itself off. It boots into CM7 fine, just won't go into recovery.

Edit: (Tried again because of Taosaur's post above this one) So I popped the uSD and took a look. Gapps zip is gone, so I re-added it and did it again. Gone again when I peeked @ boot partition after the same blank screen/shut off after power + n. Is it just flashing successfully without the Penguin + text appearing ?
[Nook Color Android Development] khaytsus:
Yes, flash the 1.2.1 update in the first post if you haven't yet. Otherwise you see nothing.
[Nook Color Android Development] topcaser:
I use the latest nightly 78. Which ocerclock kernel works with this version?
[Nook Color Android Development] Eustacia:
I have this with 77 also.
[Nook Color Android Development] japzone:
Ok, since I was pretty much ignored in the CM7 General thread I'll repost here since this is what I'm using.

I have 2 problems.

1) My Status Bar keeps Crashing. It will come back the 1st or 2nd time but 3+ and it will remain gone. The only way I have found to fix this is to reboot, which is obviousely very inconvenient. Is there any way to Manually Restart it? I don't care if I have to use terminal. For now I installed Softkeys which I can use for buttons when my Bar disappears, that way I can at least finish what I 2as doing before rebooting, but that still is inconvenient.

2) My Bluetooth refuses to come on even after hardboots, softboots, soft-reboots, ect... Any way to fix this? It worked when I fresh installed CM7.

CM7 Stable 7.0.3

Recovery v1.1

No Mods

No OC

No CWR

Unrooted Stock

____________________________________________________

Sent from NookColor CM7 uSD using Tapatalk
[Nook Color Android Development] Taosaur:
What often works for bluetooth is to turn off wifi, reboot, turn on bluetooth, then turn on wifi. I've also sometimes had luck just turning wifi off and trying bluetooth, then on/off on/off until it takes. Yeah, it's a pain.
[Nook Color Android Development] HarleyChick:
Too Easy

Verygreen - this is so very easy, for a while I kept thinking I must have done something wrong! In fact, I must say, it is even easier than I thought. I read through all 69 pages of this thread, and at one point was ready to just give up - so much talk of unzipping this, and renaming that, and moving it to this partition, yada yada yada - it was giving me heartburn. Once I got to the part that said to just load everything onto the Boot partition, I was stoked! Everything worked like a charm (well, almost). But I do have a couple of quick questions -

1. Can I use this card - with the CM7 installer - for loading a completely different ROM? In other words, if I wanted to try NookieComb or even HoneyComb, can I just load them on my card (after taking the Beta that I have on now off)?

2. Is there any way to get my apps from the Phiremod ROM I'm using now onto my card to use with the Beta 3.1 ROM, or do I have to reload everything?

Thanks so much for all your hard work!
[Nook Color Android Development] SCWells72:
Titanium Backup is your friend. There are free and paid versions in the Market. The free version will do what you want, but when restoring your apps to the new image you'll be prompted for each app. If you have 100+ apps like I do, that's annoying. Do that once or twice and the few $ that the paid version costs seems like chump change! Anyway, just go into the menu and choose Batch, then Backup User Apps (+ System Data if you want). They'll get written to /sdcard/TitaniumBackup. Install TB to the new system and choose Batch, then Restore User Apps. You may have to reauthenticate with certain apps, but for the most part it migrates your stuff quite well.
[Nook Color Android Development] HarleyChick:
I always backup my apps with TB, but they always get backed up to my sd card - an empty one that I use when I'm on my regular, emmc ROM Phiremod. How do I get those to the ROM that I'm running off of my sd card?
[Nook Color Android Development] joe2262:
You could copy the TB backup folder to a computer then boot CM7 and copy the TB folder back over.
[Nook Color Android Development] SCWells72:
Several ways. Use NookColorUMS to mount your /sdcard partition from your SD card-installed image and drag-and-drop from your other SD card. Or you can use adb to push it to the sdcard partition from a locally-inserted SD card.
[Nook Color Android Development] shumash:
Version 1.2.1 Thanks

Just installed the latest updates and kernel, and it screams on the 4gb SD. This is the first time that the bootanimation runs at full speed. Battery life is great, too.

Thanks to all you who worked on this. You make our lives and geek stuff better.
[Nook Color Android Development] angomy:
I'm not sure if this is only for Titanium Backup Pro, but you can also sync it to a Dropbox account if you have one using TB. Whenever I do my routine backup, I sync it to Dropbox, then open Dropbox on my PC and copy the backup folder into a folder with archived backups. Can't be too safe with data :)
[Nook Color Android Development] angomy:
It actually already is. It's fresh install of the 1.2.1 image that I initially flashed beta1 to, gapps, then the OC kernel. After my wifi woes I flashed back to non-OC kernel, then tried to reflash gapps, and that's where I'm experiencing the blank screen issue in recovery. However since my zips are disappearing on boot, I'm wondering if they're actually installing.

After fiddling with my router settings (now on WPA/WPA2 PSK TKIP instead of TKIP/AES, also changed channels) and setting wifi sleep policy to never that seems to have cleared up the slow market downloads issue. I just have to remember to turn off wifi if I'm setting the nook to sleep for an extended period of time.

Do you recommend running the 1.2.1 updater over my current install in case something happened along the way to bork recovery?
[Nook Color Android Development] verygreen:
If the other ROMs follow the conventions of the CM7 image, they would work. That is, retain the full directory structure in a zip except for ramdisk and kernel.

The HoneyComb image I looked at about a month ago was totally incompatible, with a few tar files inside that were unpacked by a script.
[Nook Color Android Development] verygreen:
They are disappearing because installer found them, unpacked and then deleted.

The black-screen recovery is strange, though. If you did not replace uRecRam and uRecImg with the old ones that do tend to have "black screen" for me, the new ones should have screen output.
[Nook Color Android Development] LBN1:
Same here. I don't think the 1.2.1 boot works with the nightlies or stable, only the beta kernel (as OP said - works with .32 kernel, not tested wit .29 kernel). I tried the 1.2.1 with Nightly 77, and with Stable 7.0.3 and neither worked, though it seemed it may have worked for others.

End result, I went back to the 1.1 boot and back to the Stable 7.0.3 with 1.3 overclock. I found the .32 beta kernel even with Overclock was a little too buggy and slow for my daily use, though the battery use was superior.
[Nook Color Android Development] Taosaur:
Solved! Turns out if you roll back from beta to 7.0.3 and don't clear your dalvik cache, it causes problems. This worked for me:

ETA: makes me wonder if doing this in my beta install would have cleared up the issues I was having. At any rate, I flashed the beta to eMMC and will be graduating from my SD install whenever my card reader shows up from Amazon. I'll probably flash racks' HC/Phiremod dual-boot to the SD and see if I can get the eMMC install pointed to the storage partition, and cruise with that triple-boot for a while.
[Nook Color Android Development] angomy:
I tried again today to update the 1.2.1 updater zip file. Got the blank recovery screen again (after the 2nd loading ... screen). Shut down, removed card, put in my card reader. Found u-boot.prev file there, which seems to indicate that it did install the update. Deleted the u-boot.prev file, put the updater zip again in boot directory, inserted card in Nook and started it up normal (not recovery).

Ran ROM Manager, booted into recovery through that, and presto - got the penguin and installer went through the motions, including creating a u-boot.prev file along with some text explaining why.

So I'm not sure why I'm not getting recovery screen when doing power + n. Now that the 1.2.1 updater zip was installed successfully, I'm going to try flashing gapps again to see if the recovery screen will come up this time.

Edit: Gapps flashed successfully (penguin recovery screen) this time. No idea why it hadn't done it the 15+ times I tried the last couple of nights, and I had had no trouble previously getting the timing down. (Made sure it wasn't actually turning off each attempt from bad timing too).
[Nook Color Android Development] khaytsus:
I just wanted to post some of my experiences with CM7 on two different SD cards, and comparing it to eMMC which I finally did today.

I've used a Kingston Class 6 and a Sandisk Class 2. Both felt pretty similar, boot times, load times, no severe issues like Force Closes, nothing really unexpected. But a lot of things just had a little bit of lag to them, particularly the Browser and downloads from the Market were extremely slow. Often for things like Pulse I would have to launch it and just sit it down and let it load up data, it'd take 2-3 minutes. But in general it ran well!

I finally installed to eMMC today.. No lags. Market is super fast, downloads come down as fast as they do on my Nexus One and install almost instantly. Pulse loaded articles in about 10s and no lag reading them. Browser doesn't stall for 4-5s anymore, pages load MUCH faster.

Of course some folks might have faster SD cards than I do or have simply gotten used to how things are working. I was booting CM7 off SD for about 6 weeks and was blissfully unaware of how it ran previously until I had my wifes Nook Color beside mine. Her's is still on 1.0.1, but her market launch and downloads were super fast, and no browser lags. That's when I realized it was time to try installing internally. Glad I finally did.

So I thank verygreen very much for this and I feel like everyone who's just "curious" about CM7 should do it, but if you have no need to use the stock ROM, install to eMMC. You'll be glad you did. :)
[Nook Color Android Development] HarleyChick:
I kinda figured that, but thanks for the confirmation.
[Nook Color Android Development] shumash:
I've got the same problem. Can you provide a link to the tiwlan_drv.ko file?

Thanks
[Nook Color Android Development] verygreen:
tiwlan_drv.ko is in the zip file with the kernel.

v1.2.1 of the installer will now install everything correctly so no need to install it by hand, though.
[Nook Color Android Development] comets8518:
I've had a strange thing happen which didn't come up in my brief searches. I tried to update from stable to nightly. My nook got stuck on the "Loading" screen..I tried reformatting my SD card twice, to try and redo the img etc etc. Couldn't get it to work. I just restarted the nook without the SD Card in and it went back to the "Read Forever" nc 1.2 load screen, then loaded CWM and said something about waiting for SD card...I let it countdown and then when it finished, I restarted and now all bright and shiny, I'm back in my stock config NC v1.2

I'm currently redoing the install to CM7, but I got back to stock that easy it seems.

Don't know if anyone else had this happen to them
[Nook Color Android Development] Taosaur:
Well, if it added up to 8 failed boots, that's what stock recovery is supposed to do.
[Nook Color Android Development] lschroeder:
@verygreen With beta3.1 should we after an installation replace mlo with the one from update-nc-stock-1.2-signed.zip to improve battery monitoring at low levels?

Is the replacing mlo and u-boot.bin discussion over at the [DEV] CM7 Developers Thread **2.6.32 Beta 3.1** [5/13/11] something we should be following?

Can we do this by mounting the SDcard in our computer, backing up the current mlo and u-boot.bin files and replacing them with the one from update-nc-stock-1.2-signed.zip? Is the u-boot.bin installed here sufficient and do we only need to install the mlo?
[Nook Color Android Development] TheTodFather:
I disagree with you. First off that kingston is trash! What kinda of qb32 speeds where you getting? I"m guessing you have no clue. I've been running cm7 off emmc for months but actually now with running on sd it's as fast or faster. Faster in certain tasks honestly. I"m using a sandisk 16gb class 2 from radioshack $29.99. my qb32 read and write is 1.8 and 1.2 MBs so that's fast; However if you didn't have the proper Sd card then you could be looking at .024 speeds. There is a thread that i'm too lazy to look up that will explain this all to you. I"m guessing my Sd card is running 50 times faster in qb32 speeds then yours , oh and pulse loads in 3 sec. So make sure you read up on this stuff "you'll be glad you did!!!!"
[Nook Color Android Development] SCWells72:
I don't see any reason to bash the previous poster, but I do agree that with a good SD card, things work very, very well. I've tried three or four different cards now ranging from class 2 to class 10, and I've settled on an 8GB Sandisk class 4 and a 4GB Kodak class 2, both of which run any of the ROMs from SD very smoothly. The class 6 and class 10 stuttered TERRIBLY, threw random FCs, barely worked with the Market, if at all, etc. It's all about getting the right card, and the claimed class is not necessarily the actual class of the card, both in terms of overstating and understating.
[Nook Color Android Development] shumash:
OK, I've got it working by recopying the ulmage that came with the v1.2.1 installer back to the SD, but that ulmage only allows clock speeds up to 925. What caused the problem was that I went to the kernel site and downloaded the update-cm7-dalingrin-2.6.32-sdcard-051311 file, replaced the OC uImage on the SD with that uImage. That's when the wifi went south and nothing fixed it. Can this RC beta be overclocked up to 1200 or is that still coming?
[Nook Color Android Development] TheTodFather:
Wasn't trying to start a flame war but the reason i might of been harsh is that this thread is for people using sd cards and when a guy comes in and disrespects what we are doing by saying that we should go to emmc and be glad we did. I think is misleading as well. Obviously that's not true. There is a thread in general that explains a lot about sd performance and how the most important is qb32 speeds for random read and writes and generally speaking the higher the class you go the worst the qb32 writes and reads are. IF you really want to know how good your sd card is download crystal disk mark and test it. It's not sequential read and writes that matter for having an OS on a sd card it's the random read and writes. Anything less then 1MB on either of those scores is substandard and even though Sandisk for example has different batches with same card their performance is really consistent. This has been documented. Stick with sandisk they are great for random read and writes. I'll try to dig that thread up for you.
[Nook Color Android Development] TheTodFather:
This takes 95% of the guess work out from picking the right SD card and also for easy comparison and testing for the SD cards you do have.

For all of you that want to know more about Sd card performance click this link!

http://xdaforums.com/showthread.php?t=1005633
[Nook Color Android Development] khaytsus:
First off, read my post again. Kingston Class 6 and Sandisc Class 2. Same card you have. Same REAL LIFE IN USE performance for both.

As for benchmarks, don't know, don't care. I've been using CM7 on SD card for 6 weeks and it's faster and consistently faster than it ever has been since running off of the eMMC. So in my experience, it's much faster this way.

And you don't need to explain anything to me... Get a grip.

Yes, I'm clearly very disrespectful. And clueless. You have me figured out.
[Nook Color Android Development] TheTodFather:
" I've been using CM7 on SD card for 6 weeks and it's faster and consistently faster than it ever has been on eMMC", is what you said...

Ok so why did you go to emmc if sd was faster for ya???? Your original post says that you where suggesting that everyone should just go to emmc cause you said it was faster and if they didn't "They would of wish they did" and NOW you say sd is faster? Dude you confuse me.

Let me make it clear that I simply just wanted people to know that before they give up on using Green's Sd installer to inform them of the hows the whys. Just cause you don't care about benchmarks, other people may want to know cause it does matter and if their card blows I want them to know why or to help them even choose the right one and that Sd installer works superbly with the right SD card.

Sorry i had bashed you...I should of been more tactful in retrospect. I'm not going to engage this any further, again my deepest apologies.
[Nook Color Android Development] khaytsus:
I guess my wording was bad, it's faster since going to eMMC. I tweaked the statement.

eh? Again, my original post said that it's great to use to try out CM7, but if you're going to use it full time and don't need the stock ROM, install to eMMC. Nobody said anything about giving up, this installer has any issues, or that nobody should use it.. And in fact..... again, my original post..... Stated that everything was running quite well except some specific activities were slow and there was a general lag here and there.

And again...... Same card as you. Remember? Radio Shack? Last post on this... geez.
[Nook Color Android Development] comets8518:
Well it acted like it was only an SD install not an internal memory install.

If it added up to 8 failed boots then it did 7 of 8 of them all on its own in about 30 seconds. I've never tried the 8 failed boots before but I assumed it was a lot more tedious than that.

But yeah not really a huge revelation, just not something I expected
[Nook Color Android Development] shumash:
Wifi Failure

Everything is fixed. I had replaced the uImage that came with the v1.2.1 update with the one in update-cm7-dalingrin-2.6.32-sdcard-051311. That uImage tanked the wifi, but allowed overclocking to 1200. The uImage with the v1.2.1 update only goes to 925. Is the overclocking a work in progress?