yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] newellj79:
Exactly. I would not do it thru Rom Manager myself. It's just as easy to do it thru clockwork and good to know how. But either way. If you do it thru Rom Manager make sure "wipe dalvik" is the ONLY box checked, NOT DATA! And as a final step to your post make sure you enter the advanced menu from the main menu in CWM and wipe dalvik. E-Z-P-Z...
[Nook Color Android Development] leapinlar:
Why do you recommend not using RM? I know a lot of users do not and I don't understand why. It's so easy and I have never had a problem and I have flashed almost every nightly since 100. It does everything that you are recommending doing manually.

I agree it's good to know how to use CWM, but once you have done it once, why continue?
[Nook Color Android Development] leapinlar:
OK, another 24 hours of no SODs with the wifi file patch. And I am now connected to another wifi source with no trouble connecting.

I hope the devs pick up on this and issue some nightlies with this mod, followed with a permanent upgrade to CM7.1 stable.
[Nook Color Android Development] mrapollinax:
I use the CWM Method on my Nook Color because it essentially encourages me to have a uSD card that is ready to flash and recover my Nook should anything wonky happens to it. Flashing through ROM Manager does not. I always have a bootable CWM uSD card with 1.3 recovery image, dual boot images (install and remove), latest CM7 nightly (hopefully CM8 in the future) and latest GApps handy.
[Nook Color Android Development] leapinlar:
I also have a bootable uSD card with CWM on it ready in case something goes wrong. But I still flash my nightlies with RM since it is so easy. Aren't you afraid you will wear out your uSD slot changing it so many times? I have found on other devices that the mechanical mechanisms of those slots have a finite life. But then again maybe you don't flash that many ROMs.
[Nook Color Android Development] mrapollinax:
On the contrary I was flashing between ROMs quite frequently using bootable uSD cards, I have quite a few of them. I'm not worried about the mechanical portions of the card slot breaking down so it isn't an issue for me. If you like using ROM Manager, hey that's cool, it works for you. I just prefer using CMW and uSD cards.
[Nook Color Android Development] j21blackjack:
So, I was on 7.1 stable for the last week, and slowly started getting more and more FC's, mainly status bar, then boat browser started closing for no reason, then random apps, and now my live Clock wallpaper. I decided to update to the current nightly, and now have the same force closes more often. Is there something I should know about that is causing them, I'm still pretty new with the Nook, but I've been using MIUI for my MyTouch 4g forever, and never have these kinds of issues. I even switched to dolphin browser, and started getting FC's after a few hours. It also seems that minimalistic text is causing my status bar to FC every time I open the menu for it. More often than not it doesn't restart either. I am running CM7 from the Nook, not an SD card, OC to 1.2Ghz.
[Nook Color Android Development] bigbob23:
Not all Nooks can handle overclocking to 1.2 GHz. Mine is much more stable at 1.1 GHz and some people have reported best results at even lower clock frequencies. It's easy enough to test and see if there is a difference.
[Nook Color Android Development] Sincitybronze:
Did you fix permissions?
[Nook Color Android Development] j21blackjack:
No, I just switched to MIUI 1.11.4 to try it out for a little while.
[Nook Color Android Development] androidmonkey:
Confused. I cant seem to get into CWR to do a Nandroid backup. I hold the N button while booting up, it goes to the green/black screen and gives me the boot options. I then tried using ROM Manager to boot into recovery, it goes the the penguin screen, then goes through some commands, says something like partition is already done and correct, then it says restarting.

Where do I do a Nandroid backup?
[Nook Color Android Development] leapinlar:
It sounds from your description of the ROM Manager response that it was trying to flash a new recovery or something rather than rebooting.

You are trying the right things to do a Nandroid backup. CWM Recovery is where you do it.

You are letting go of the power button too soon. Keep holding both buttons until it says "booting into recovery".
[Nook Color Android Development] stolenmoment:
Lookout guys, two different people are asking about upgrades: androidmonkey has a uSD install (and should use the instructions in the OP of the size-agnostic thread), but timmyjoe hasn't said whether he's on emmc (use ROM Manager) or uSD (see above).

ROM Manager doesn't play well with SD installs.
[Nook Color Android Development] timmyjoe42:
I'm using emmc. I used ROM manager to update and it was super easy, but the nightly 246 was not as nice as the nightly 177 that I was on. The signal bars were annoying and apps were Force Closing left and right (even after wiping Dalvik and cache), that I just gave up and went back to 177. I'm not sure how the nightly seems to have regressed. Why were the signal bars included in these later nightlies? Why are we getting all these FC's?
[Nook Color Android Development] zequav:
I've been upgrading every week or so and don't have any FC. Ever. Stable as a rock.

The bars ARE annoying, though. Wish some dev took a look at it. The bug must be fairly easy to fix.
[Nook Color Android Development] mrapollinax:
Running 241 right now (dual boot), no FCs to report either.
[Nook Color Android Development] androidmonkey:
Ah, I am using uSD for my install. So is it possible to do a Nandroid backup using that method?
[Nook Color Android Development] leapinlar:
If you want a newer nightly than 177 without the signal bars, go back to 233 or before. The devs changed the system to help other devices show signal strength better. But for us Nook users without a radio, it backfired. You could also search back on this thread where a user created a modified SystemUI.apk that prevents the bars from showing. That is what I use. I added it to my custom gapp zip and flash it with each new nightly. And I will till the devs fix it.

As far as your FCs, try going to recovery and fixing permissions. Also try reducing the maximum on the cpu overclock. Some Nooks do not play well with high settings. You might also try the conservative setting on your cpu governor. As of October 24 Dal modified the kernel and, I think but I'm not sure, added interactivex as a governor setting. Anyway, somehow mine got set to that and I had to manually change it back.

BTW, another night without an SOD using the modified wifi module. And yes, it was unplugged overnight.
[Nook Color Android Development] leapinlar:
Thank you Stolen, finally a rational reason for not using ROM Manager. I will be more careful about giving advice until I understand the user's situation.
[Nook Color Android Development] andyrubin1:
is there any plan for a point release or a flashable zip to include the new wireless driver? thx
[Nook Color Android Development] mrapollinax:
Check the thread link I posed earlier. Someone on the CM Forums has done that already.
[Nook Color Android Development] mis3:
I retract my comment. WiFi sites work now. After copying to system/ lib/modules need to change permissions to match the original file. rw-r--r--

I know for some, this was probably obvious, but for someone like me, this was a key missing direction.
[Nook Color Android Development] andyrubin1:
ooop sorry i meant a flashable zip with just the new driver and installable on existing cm7.1 release.

thx.
[Nook Color Android Development] stolenmoment:
My only gripe with Root Explorer is that it doesn't show enough detail to get this sort of thing right on the first try.
[Nook Color Android Development] khaytsus:
Just copy the card.... dd if=/dev/carddevice of=backup.img bs=8m

Or use whatever method on other OSes.
[Nook Color Android Development] ganovim:
what is you custom gapps? and where do I get the fixed wifi file?
[Nook Color Android Development] leapinlar:
I created flashable zips that just installs the files needed to fix the signal bar issue and wifi driver to prevent SODs. I have shown the links below. Just install with CWM Recovery or ROM Manager. To install with RM, go to "install ROM from SD" and follow prompts. Be sure to choose "wipe Dalvik". These work with emmc installed CM7. I don't know if they work with SD installs.

This zip is for CM 7.1 stable and recent nightlies that have the 2.6.32.9 kernel. (Look in settings/about tablet)

Install zip (SOD fix only):

http://d01.megashares.com/index.php?d01=8VPCE7N

I am also including a zip for recent nightlies (234 and above) that have signal bar issues.

Install zip (SOD fix and signal bar fix)

http://d01.megashares.com/index.php?d01=KFyOSYg

I am also providing the links for just the files if you want to install them manually.

Wifi driver/module:

http://www.mediafire.com/?61b1nzzt8kq62hx

Signal bar fix:

http://d01.megashares.com/?d01=ed8d5d9

Thanks to Embedded and Keyodi for the original files.
[Nook Color Android Development] ianPhillips1:
Thx for the patch.

Ian

sent from my ereader
[Nook Color Android Development] timmyjoe42:
It's not letting me download the "Install zip (SOD fix and signal bar fix)" file.

:(
[Nook Color Android Development] leapinlar:
Try again. Others seem to be getting it.
[Nook Color Android Development] timmyjoe42:
I installed nightly 247 last night and everything seems to be working fine. I didn't do anything different. Oh well, I'm not complaining. Now I will try adding the SOD and bars patch. :)
[Nook Color Android Development] zequav:
Got a SOD today. The fixed lib seems to work for me. Here's hoping that Embedded guy submits the fix to git (or even better, joins CM. There doesn't seem to be many devs dedicated to encore right now :( )

The modified SystemUI for the annoying bars also works fine.
[Nook Color Android Development] dexx0008:
for the SOD, signal bar zip, can I just rename the zip file to contain "update" in it, and reboot into recovery and flash it that way? (I use verigreens generic 1.3 installer for sd cards)
[Nook Color Android Development] leapinlar:
I don't know. Someone familiar with SD installs will have to answer that for you.
[Nook Color Android Development] dexx0008:
i just went ahead and tried in recovery, it worked fine, you just need to put update- at the beginning of the zip. It did get rid of the signal bars. i'm moving from n150 to n247, we'll see if I experience any SOD, none after a few hours.

thanks for the zip!!!

Coming from n150, i was impressed the new market worked. I can really tell the difference with dpi now set to 160 though, everything doesn't seem as crisp on screen as it was before(icons, etc). I wish this wasn't the only fix for the new market since 161 looks so much better imho. (i'm ignoring the fact that i could in theory switch to old market) I might just live with it and hope we get ICS.
[Nook Color Android Development] stolenmoment:
I use the "LCD Resolution" app to switch densities, since some of my apps don't work right at 160 (ShortyZ in particular), but are fine at 161.
[Nook Color Android Development] stolenmoment:
Got it, installed it, signal bars gone, no SODs yet.

Thanks!
[Nook Color Android Development] guv.:
I had my first SOD with the fixed wifi module today. I fell asleep watching a YouTube video on the nook and woke up 3 three hours later to an unresponsive nook. Battery was at 44% after the reboot, s it didn't run dry..
[Nook Color Android Development] BitingChaos:
Do the devs know this?

Are after-flash packages going to be needed & installed every time we upgrade now? Or are these changes going to make it into the buildbot? Whom do we contact to let them know?
[Nook Color Android Development] leapinlar:
I think the CM7 Devs know. But since fattire and dalingren have moved on to the touchpad, I don't think there is any Dev putting priority on it. So it may be a while before anything is done.

Also part of the delay is the way the CM project works. It is not possible to just take some compiled code and stick it into a nightly. They have to have the source code to do a peer review and approval before anything is put in a nightly. This is done for our protection so some weird or malicious code is not injected into CM.

Just keep flashing.
[Nook Color Android Development] dexx0008:
with ICS source being released on the 17th, are there any devs for the nook color left to get this running on our device?

for those in the know, how challenging is it expected to be to get this up and running and is there any sort of rough timeline? I'm not expecting it'll be ready in 3 days but I imagine at some point focus will be on this vs. cm7.
[Nook Color Android Development] zequav:
Well, IIRC dal said we probably need 2.6.35 (minimum) for ICS and asked for volunteers without (apparently) much success, so... things don't look good.

Oh well. Maybe it's time to buy a Transformer Prime :P
[Nook Color Android Development] dexx0008:
hmmmm. was hoping nook tablet release would be enough to gather enough interest.(although I realize it isn't out yet) I like the 7" form factor for tablets so will have to start looking i guess.
[Nook Color Android Development] koopakid08:
In case anyone hasn't heard yet the ICS source is out. If there are any devs left....

---------------------------------
[Nook Color Android Development] :
LOL...all this passive aggressive guilt-tripping going on.
[Nook Color Android Development] zequav:
We looking at dal:

:D
[Nook Color Android Development] tsddave:
Nook ICS would be a dream come true!
[Nook Color Android Development] Awats:
I am running B251 and while I have the gray airplane icon, I don't have signal bars. Why is that?
[Nook Color Android Development] Snyperx:
Hoping someone can help me. I am running CM7 build 12. Everything has been running great up until today. I can not download from the market again. I did the clear cache/force stop trick, but that has not resolved the issue. I even reinstalled gApps. Not sure what is going on. Any ideas? Thanks.
[Nook Color Android Development] Foetus:
The only real fix I've found so far is to click "uninstall updates" and then wipe the market cache, force stop, clear the data from the framework, and reboot. Uninstall updates is in the same place you clear the market cache.
[Nook Color Android Development] timekeeper:
Setting LCD density to 169.33333 solved Market my apps for me. Your mileage may vary.
[Nook Color Android Development] donballz:
Thanks maps never worked before and now it does in addition to the scaling issue. Off to check if YouTube is fixed also.
[Nook Color Android Development] donballz:
I was having that issue on 8 and 11 but seems to be fixed for 12. It has continued working normally through three reboots so far.
[Nook Color Android Development] jkurl:
I set mine to setting above and no market download apps for me. I changed it to 161 and they were back. Changed it to 160 and they are gone. Changed back to 161 and still gone going to do a reboot now.

Edit I had to end up clearing cache in market force stoping market and clear data on framework and then rebooted and my apps came back well some of them.
[Nook Color Android Development] Paul22000:
Perfect. Thank you!
[Nook Color Android Development] jd95:
is there anyway to improve my streaming frame rates I am not sure if this is the right section to ask it?
[Nook Color Android Development] tehpeach:
is anyone having an issue with connecting USB, even with charging? I'm running v12 and my PC and power brick do not detect the NC or charge it, UNLESS it is powered off. anyone got a fix?

EDIT: i happened to try another nook cable i had hanging around (we own 2 in the house) and it worked fine on my nook. now to wonder how im going to get it replaced without showing the B&N guy the CM7'ed nooks :(
[Nook Color Android Development] RoboRay:
I'm still having this issue in 12
[Nook Color Android Development] Paul22000:
Ah, damn it.

I wonder what would cause this to be fixed for some people but not others?

Did you wipe before flashing v12?

And donballz, if you're still reading, did you wipe before flashing v12 as well?

Just wondering what else could be the cause of it being fixed only for some people.
[Nook Color Android Development] MisterEdF:
Do you have to start with a rooted Nook to install the CM7 or does installing the ZIP using the bootable SD w/recovery do the rooting for you?
[Nook Color Android Development] diomark:
Amazon kindle should work just fine offline though, but it seems to think its on a new device and want to rwregister when it fails- that's the part that confuses me...

-mark
[Nook Color Android Development] racks11479:
If you're flashing to the emmc, no need. It will just replace your stock completely.
[Nook Color Android Development] RoboRay:
Yep, I formatted every partition except /boot, wiped dalvik and cache (again!), flashed #12+Gapps, and reloaded apps from Titanium without data (except for my Angry Birds progress).

Hmmm... Do you use the WiFi Manager widget to control your wi-fi?
[Nook Color Android Development] faceman66:
That's easy...just take the cable in. Tell them you have two nooks at home and tested it yourself. They can test it with a nook there in the store and see it's bad. You shouldn't have to return the whole nook to warranty just the charging cord.
[Nook Color Android Development] JeremyNT:
I tried this and maps still fcs on me. Anything else I can try to fix maps?
[Nook Color Android Development] bonobomidwest:
I may be wrong, but I don't think density changes take effect without a reboot
[Nook Color Android Development] bonobomidwest:
Ok guys I've been watching this very carefully on my machine. This is the pattern I have observed.

1. The NC has remembered at least two networks (in my case work, home, and adhoc) (also at work there are multiple routers with different MACs but the same ssid)

2. The NC. Sleeps on one network but wakes on another. It has to be a special kind of sleep because this seems not to happen if you move between sites quickly....

3. It recognizes the new network but never completes the connection

I'm pretty sure that even a reboot won't fix the problem every time....

But here is what does... for me at least...

1. Disconnect from your troublesome network. I forget the network for good measure, but actually I have got this to work only with a simple disconnect

2. join another visible network (e.g. your adhoc) with a different SSID.

3. Disconnect from the new network

4. Reconnect to your original network.

I know there's a lot of unknowns left in this post, but give it a shot, with enough experimenting perhaps we can nail the behavior down enough to help the devs :)

If anyone else can replicate this then I think it points to some obvious places to look for the problem... also I wonder if leaving wifi on during sleep might be a workaround... anyone tried that?
[Nook Color Android Development] eyecrispy:
I am not seeing this wifi issue on 12. I did in 8. When I flashed I wiped system, data and cache.

Sent from my NookColor
[Nook Color Android Development] timmyjoe42:
Doesn't the airplane symbol mean airplane mode which kills the signal bars? Can you connect to wifi in airplane mode?
[Nook Color Android Development] Awats:
If I turn on airplane mode, wi-fi goes off and doesn't work and I never get signal bars.

Not that it's that important... Just curious, that's all.
[Nook Color Android Development] bigbob23:
I have the same thing. A while back I had enabled a display of WiFi signal strength and wonder if that had anything to do with the airplane display (the signal strength always said -1 dBm but I couldn't find the screen to turn it off again). It has no effect on whether I can turn WiFi on or off.
[Nook Color Android Development] jimvsmij:
Hi,

I'm running CM 7.1.0 and everything has been fine. Yesterday I was having trouble connecting to WiFi and today it won't at all. It detects and list my WiFi router but says that it is not in range even when I am right next to it.

Has anyone experienced this? Does anyone know how I can get WiFi back?

Thanks
[Nook Color Android Development] DizzyDen:
forget all remembered networks and let it rescan
[Nook Color Android Development] jimvsmij:
You are the Man! Thank you!!! This community rocks and is a real life saver to wanna be geeks like me!
[Nook Color Android Development] leapinlar:
Great news. Dalingrin has come up with a patch to the kernel instead of the wifi module to fix the SOD issue. Brian Faris took the patch and created a new kernel that incorporates it. You can read about it in the same thread on the cyanogenmod forum that I referenced earlier (http://forum.cyanogenmod.com/topic/32316-sleep-of-death-debugging/page__st__20.)

Brian created a flashable zip that replaces the kernel on your system with his modified kernel and also takes the wifi module back to stock CM7.1. This zip is intended for CM7.1 stable and recent nightlies. You can download it here:

http://www.multiupload.com/2RY15NAYDB

Edit: Brian modified his zip to fix an issue with Nook Tweaks. Here is new link:

http://www.multiupload.com/D2Z5R1J9N6

He also provided a link for just the kernel here:

http://www.multiupload.com/PGC510T2F5

I modified his zip to include the signal bar fix if people are interested in that. This should be used on nightlies above 233.

http://d01.megashares.com/index.php?d01=LBKwElp

Dalingrin is looking for feedback on how this works in preventing SODs. You can give feedback on the cyanogenmod forum or here.
[Nook Color Android Development] dalingrin:
Signal bars

Signal icon should be fixed in next nightly: http://review.cyanogenmod.com./#change,10233

SOD

Also, please test the kernel. This silly SOD problem is the bane of my existence because I cannot reproduce. Really need someone to give feedback on that kernel so I know how to move forward.

ICS

Work is underway to get legacy device(thats us) to work with ICS. These legacy hal changes will make it easier to support the Nook Color but we still need to either backport DSS and SGX drivers for update to a new kernel. Both of these options are a good bit of work and won't happen overnight so please be patient. =)
[Nook Color Android Development] ianPhillips1:
Dal thanks for looking out, glad you could do your thing once again. And a big thanks for giving us some real ICS hope

Ian

Sent from space
[Nook Color Android Development] tsddave:
Thanks alot Dal....you bring great news :)
[Nook Color Android Development] ponyboy82:
Thanks for the update, Dal. Glad to see you're still taking care of us NC folks :)
[Nook Color Android Development] frankusb:
FYI - at the moment, if you use this kernel patch, do not use Nook Tweaks to adjust the display bit depth. The kernel patch only replaces the booting kernel, not the kernels that Nook Tweaks uses.

UPDATE - fixed.

Frank
[Nook Color Android Development] leapinlar:
So far, so good. I left it unplugged overnight and I usually would have an SOD in the morning and have had none with the new kernel.
[Nook Color Android Development] mrg666:
I am using the test kernel although I did not have the SOD problems. It still works completely fine with 7.2.0-RC0 build on 11/16/2011. No problems to report here. Thank you Dalingrin and Brian.
[Nook Color Android Development] slider2828:
Thanks Dal for the update. We should really start a Dal ICS donation thread. Its going to be so awesome if he gets it.

But he is working with the CM team, so probably CM9 is what he is concentrating on? Slated for January?
[Nook Color Android Development] GTT1:
Okay I am getting confused I downloaded and installed the zip in your post of Nov 11th

http://xdaforums.com/showthread.php?p=19261533#post19261533

Is the above zip that replaces the kernel different and will it conflict if used with the original fix?
[Nook Color Android Development] MechaGen:
^

Same, but different!

Doesn't seem to interfere.

Sent from Tapatalk, NOOK Color CM7 Nightly's!
[Nook Color Android Development] bigbob23:
What happened to CM8?
[Nook Color Android Development] slider2828:
CM8 was slated for Honeycomb, but I think since HC's source wasn't released, CM is dumping that project.
[Nook Color Android Development] danvee:
+1

Dan