yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] stolenmoment:
I've been having similar problems in recent nightlies; installed n136 yesterday. The WiFi indicator goes white, my Google account (and sometimes LinkedIn or Facebook) vanishes from Settings/Accounts, and the Google account can't be added back; it's not one of the options offered. Flashing gapps and registering again appears to clear it for a while.

I don't remember whether I ever flashed gapps via Rom Manager; it's a possibility. The last several flashes have all been from CWM. md5 checks out.

It also hasn't happened to me since I backed off the new Market, but that's a weak correlation so far; it's been less than 24 hours.
[Nook Color Android Development] hetzbh:
PPTP fix soon?

Sorry if I'm "barging" in the middle of the reports (btw, N136 works great on my Nook).

With the latest news about Netflix and the ability to watch videos even with Nook as well as any other "modern" Android phone/tablet, we (the people who live outside USA) are stuck with one problem: PPTP/VPN connection.

At the moment, Nook, as well as Nexus one has this severe issue (including Nightly 136): trying to connect to a PPTP connection will automatically crash your phone/nook (it does kernel panic). It's being issue 3353 as you can see here, and there was a rumor that there is a fix which needs to be merged.

So, could someone please help us with this issue?

Sorry for the interruption.
[Nook Color Android Development] bobster0001:
Did anyone lose their root after installing n139?
[Nook Color Android Development] keyodi:
It happened to me one time on an earlier nightly. I had to re-install the superuser app to fix the issue.

http://xdaforums.com/showpost.php?p=14853751&postcount=2907
[Nook Color Android Development] Razor1973:
If I have 7.0.3 (I don't even remember where I found the instructions I found at this point) and want to upgrade the the latest nightly, can I simply drop the file in my first partition and flash (no wipe) with CWM?
[Nook Color Android Development] tsukaza:
Absolutely, I am on nightly 143, runs sweet.
[Nook Color Android Development] SeaFractor:
Works very well for me as well. I suspect we are closing in on a stable release, or at least another RC.
[Nook Color Android Development] Razor1973:
Is this an answer to my question right above your post?
[Nook Color Android Development] boxcar8028:
Yes. you can flash from 7.0.3 to the newest nighty. but do wipe cache and wipe dalvik but no need to wipe data.

you may also want to check this out. no need for the OC kernel it has been merged with cm7.

Nook Color Tweaks:

http://xdaforums.com/showthread.php?t=1104039
[Nook Color Android Development] Razor1973:
Thank you so much. I am about to try this. Question, though... Are my SD card partitions alright? Please see attached (nookpart.jpg). I'm concerned, because it seems the space left in my primary partition is barely enough to fit the CM7 file. See files in this partition also attached (nookfiles.jpg).
[Nook Color Android Development] Ronin3178:
Take the dive, go to eMMC, its so much easier. <-- from a guy who jumped straight into eMMC tho.
[Nook Color Android Development] bigbob23:
I have done both and highly agree that eMMC is the way to go.
[Nook Color Android Development] Razor1973:
Sure, I'm willing to loose all my data. Where do I start? Here? Do they even have to worry about the nooter or simply flash 1gb_clockwork-3.2.0.1-eyeballer.img and gapps and reboot?
[Nook Color Android Development] bdcrim:
I lost my apps in the market with nightly 8.
[Nook Color Android Development] tominabox1:
I did not.
[Nook Color Android Development] woolmonkey:
I can't press and hold on the home screen I can do it in the app launcher but once a app or widget is on the home screen it can't be moved or deleted.
[Nook Color Android Development] ericman77:
Adobe flash,my apps,maps,and YouTube, don't work. Also when I click on a app that is installed in the market it says app not found. Key boards lagging. But other than that its pretty cool.
[Nook Color Android Development] dalingrin:
Nightly #8 fixes:

For "My Apps," go to manage apps, market, uninstall updates, clear market cache. Then delete data for Google Framework Services.

For Maps, set the lcddensity to 169.

Reboot your nook.

You should find nightly 8 to be pretty snappy even without my overclock kernel.
[Nook Color Android Development] tominabox1:
ldc density of 169 breaks google reader again by the way
[Nook Color Android Development] openallnight:
Looks good so far. default Kernel (or whichever one is included) is not causing wifi disconnects for me. Can see video (avi) for the first time. You tube does not work. XDA app still crashes when logged in.
[Nook Color Android Development] bonobomidwest:
Oh man I don't know how you guys do it... I've been holding off with v5 as the kinks got worked out, and this is just gorgeous. Everything is working great. Thank you so much!
[Nook Color Android Development] bonobomidwest:
Try 169.3333333 not sure how many decimal places you need but I believe this is the stock value and Google reader works for me with this setting.

***EDIT*** after a little more digging, the correct stock value is "169.33333" - i.e. 5 decimal places. In fact it makes no difference on my system which is used, but my apologies nonetheless.
[Nook Color Android Development] chli:
Thanks dalingrin.

I updated from 5 to 8 because it looked like it was worth it... and it IS :)

Yes this new version feels quite snappier than the one I had before.
[Nook Color Android Development] spikey911:
I am not noticing it being any more snappy than before running 7. Not that it was bad before, just don't seem to feel a difference.

Great progress with everything else as well though. If anyone is on lower versions I think its safe to make the jump to 8...
[Nook Color Android Development] Narfx:
Same here. Maybe it's because I'm expecting too much... like the snappiness of CM7 in my HTC Desire, and since we are not quite there any progress goes unnoticed to me.

BTW, will we ever get that snappiness? I think the Nook's OMAP3621 with the SGX 530 GPU is more powerful than the Desire's QSD 8250 with z430 GPU (at the same frequency)... but the NC also has to move almost twice the pixels, and right now it feels sluggish compared to the Desire. Yeah, I know the Desire has had CM since many months ago and we've had CM for barely (edit) one week, but I think HW acceleration was already working in the kernel, right?
[Nook Color Android Development] newellj79:
Although "myapps" r back. I am randomly getting fc's on the super user application after performing this procedure. Any ideas?
[Nook Color Android Development] Mikey:
settings unlock desktop
[Nook Color Android Development] bonobomidwest:
Definitely feels faster and smoother than v5 at 800Mhz. Awesome...
[Nook Color Android Development] ericman77:
How do you change the screen density?
[Nook Color Android Development] newellj79:
Download "LCD density for root". Its a free app.
[Nook Color Android Development] ericman77:
Cool thanks. I don't know if LCD density fixed flash too but its working now also.
[Nook Color Android Development] KitF:
I tried this and it doesn't work for me. I've just gone back to 160 and a working reader and a broken maps.

Can you post the line from your build.prop?
[Nook Color Android Development] newellj79:
Hmm, flash had always worked for me. Your welcome.
[Nook Color Android Development] Ronin3178:
At quick glance that looked good, do you have one of the newer partitioned Nooks that needs a whole reworking to go eMMC? I luckily had one of the older one from back in march of this year.

And one more thought, to possibly not lose your data, try not formatting data partition and if it boots up properly, run TB to get all your app data. Then reboot into recovery and format data and restore. It may work.
[Nook Color Android Development] bigbob23:
I suspect there are several ways to get there, but Iused these instructions to install to eMMC: http://xdaforums.com/showthread.php?t=1030227. No need to use nooter.
[Nook Color Android Development] newellj79:
The newer ones have a blue dot on the box. I had to have b and n send me a replacement and that's what I ended up with. The routine for switching the partitions back to the original variety is very ez. A quick search should produce all that is needed.
[Nook Color Android Development] Razor1973:
I'm up and running. Thanks everyone who helped! :)
[Nook Color Android Development] Nburnes:
Has anyone compiled there own build recently? I did it before work this morning, including up to "GanOptimizer: Dutch translation added! (android_packages_apps_GanOptimizer)" and the system is running ridiculously slow. I want to find out if it is simply a problem with my build environment or what.

Edit: Also, the final .zip I end up with is only 88.3 mb?

Edit 2: Upon first boot, colors are off as well. Changes on reboot after Nook Tweaks 16 bit 32 bit color choice.
[Nook Color Android Development] newellj79:
Building right now. Will update this post shortly.

Edit.. have not flashed yet but i have a file size of 101.5mb.

Edit 2... finished building just before 12pm eastern time, rom is flying as usual. Everything seems ok.
[Nook Color Android Development] Nburnes:
Hmmm something definitely messed up on my machine. Thank you man.
[Nook Color Android Development] dalingrin:
Flash a nightly then run extract-files.sh from the device directory. You are missing proprietary files(SGX userspace libs) otherwise.
[Nook Color Android Development] Nburnes:
I was actually about to post this. :p

I ran the extract-files.sh on my build and boom, remote object 'blah blah blah' does not exist.
[Nook Color Android Development] boxcar8028:
congrats! enjoy! :)
[Nook Color Android Development] chisleu:
Where is the link to the guide on compiling CM7? I want to dive into the statusbar a bit on my 2 week break between summer and fall classes..
[Nook Color Android Development] bigbob23:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Encore
[Nook Color Android Development] blahbl4hblah:
I'd like to know why whenever I compile cm7 for nook I'm getting a force close on statusbarui, I can't give a logcat because I don't have adb setup for nook, nor are the steps on how to do so for ubuntu working.
[Nook Color Android Development] bigbob23:
See this to install the sdk and adb:

http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
[Nook Color Android Development] blahbl4hblah:
Let me restate what I said earlier, I have sdk and adb working properly for other phones, but not the nook
[Nook Color Android Development] knaries2000:
Use wireless adb for ubuntu. It works fine without any setup other than installing the sdk and it is more convenient.
[Nook Color Android Development] blahbl4hblah:
Well this is strange, nightlies will work perfectly while compiled cm7 roms don't work.

Maybe it's my proprietary files since there old I think

The reason why I'd rather compile it rather than download is simply because it's my preference

If anyone could help me, pull the latest proprietary files from your nook using the latest nightly. I'm aware of wireless adb, but since my desktop doesn't have wifi capabilities, it's a no go
[Nook Color Android Development] Nburnes:
Does this help?

http://wiki.cyanogenmod.com/wiki/ADB
[Nook Color Android Development] blahbl4hblah:
Sadly no, Thanks anyway

I tried the steps on there for nook adb for ubuntu, but it won't give me it

it'll give me the no permissions '???????????' then I'll do the next thing then no devices again when I do adb devices
[Nook Color Android Development] Nburnes:
Did you manually update your udev rules with info from lsusb?

http://wiki.cyanogenmod.com/wiki/Udev
[Nook Color Android Development] blahbl4hblah:
There's no nook color on that, it's fine

I'll do it manually
[Nook Color Android Development] Nburnes:
Haha I know mate. You will have to do it manually. If I was booted into Ubuntu, I would give you my udev rules. >.> gah

Edit: This should hopefully fix your ?????????? no permissions issue. http://nookdevs.com/NookColor_USB_ADB
[Nook Color Android Development] blahbl4hblah:
Tried that before didn't work, it's all good thanks for the help though
[Nook Color Android Development] newellj79:
I built cm7 3 times yesterday. They all resulted in bootloops. I haven't had a problem in the past. Any thoughts?

edit... i get the same thing with n146, bootloop...
[Nook Color Android Development] painter_:
I did not see this posted. Build 146 bumped CM7 to 2.3.5
[Nook Color Android Development] newellj79:
Can someone confirm bootloop with n146?
[Nook Color Android Development] elwood1229:
No bootloop for me on n146. Running super.
[Nook Color Android Development] khaytsus:
Create the ini file, create udev rules so you don't have to use it as root, restart udev (udevadm control --reload-rules) or reboot, adb kill-server. Done.

The instructions on the Nook Devs site just work.

You did it wrong.
[Nook Color Android Development] 12paq:
Confirmed.

I am going to try to set all votage and CPU clock speeds to stock and try again. The Nook was not stable to pull a log, and I am not near a PC.

Edit: restored via a nandroid, I will download 146 again and check md5. I am on the road traveling and I would rather vet all possibilities that I and my system are not the problem before reporting back.
[Nook Color Android Development] Nburnes:
No boot loops for myself, on neither the nightly or my own build.
[Nook Color Android Development] newellj79:
Hmmm. I'm running stock voltage. Cleared both caches and fixed permissions. Bootloop at animation. I flashed n138 becuz it was handy and it is fine.
[Nook Color Android Development] bigbob23:
I had a problem with 146 after installing with ROM Manager. I tried again downloading it to my Mac, copying to the SD card and using CWM and it worked fine that way.
[Nook Color Android Development] newellj79:
Anything after 138 creates a bootloop for me. N e ideas. I have used dizzydens imei generator n the past. Both modified and unmodified versions end with bootloops. Please help.
[Nook Color Android Development] woot1524:
Do you have the latest ClockworkMod installed? 3.2.0.1 if I remember right.
[Nook Color Android Development] newellj79:
Yes.

Tenblahblah
[Nook Color Android Development] fattire:
So-- a bootloop is a pretty generic symptom of what can be a zillion problems booting. Luckily there is a way to peek behind the scenes and see where exactly your boot is getting stuck:

adb logcat

If you've installed adb and run logcat, you can see what's going on-- and that will be invaluable in diagnosing and solving the problem.

[YOUTUBE]v3rhQc666Sg[/YOUTUBE]
[Nook Color Android Development] newellj79:
Thank u for the tip. When my company leaves I will flash n146. Let it bootloop then grab the log and paste it hear. I appreciate n e help.

edit... im running logcat but u cant copy and paste it out of terminal in windows. does it dump the file somewhere?
[Nook Color Android Development] :
I appreciate spelling :)
[Nook Color Android Development] fattire:
Not sure why you're having problems copy/pasting. I dont have Windows, but in Linux or OS X you could redirect the output to a file like this:

$ adb logcat > log.txt

I'm not familiar enough with the windows shell to know how to do the equivalent, but a quick googling suggests the same may work in windows too.

And that's one to grow on!

[YOUTUBE]B8rDti-rpZU[/YOUTUBE]
[Nook Color Android Development] newellj79:
Gotcha. Trying to get my daughter down for a nap now but will for sure post it in a few hours. Googling confirms you can paste into windows terminal but not copy from. Should have booted into Ubuntu. Trying to rush. :)
[Nook Color Android Development] pmilford:
Hi,

I had problems installing 146 (and an earlier CM7 version too). Not sure if it

is same problem as you have. I was hanging at "Loading..." after trying

to access CWM via ROMManager. See my (too long) post about it:

http://xdaforums.com/showpost.php?p=16153610&postcount=535

Summary: I worked around using a bootable uSD with CWM to boot and install CM&/GAPPS from.

Peter
[Nook Color Android Development] patruns:
I assume everyone is talking about the command prompt window in Windows. You can copy. Just right click in the window and choose "mark". You should see a flashing cursor at the beginning of all the text. With your mouse click where you want to start copying and drag it across all of the text until everything is highlighted. Then hit Ctrl+C and you can then paste it into another document, or right in your message.
[Nook Color Android Development] 12paq:
Exactly.

And thanks for links and tips, so we can identify our Nook's issues. Almost always it's somthing on my device that I can identify with a log. Rarely is it the build. I tweek it until it fails, then have fun seeing why. Yes, I am strange. :)

Edit: mine was a bad file download.
[Nook Color Android Development] newellj79:
Please find my logcat at the dropbox link attached. The logcat starts a couple seconds after the boot animation starts, and stops a couple seconds after the animation re-starts. This is n146, wiped dalvik and cache. Same things happens with anything after n138. Thanks guys.

http://dl.dropbox.com/u/27515414/log1.txt.txt

(note... it was to big to attach here)

Edit... I don't know anything about reading these logs but looking a the end of it I see alot of "package manager failed", and interrupts.
[Nook Color Android Development] blahbl4hblah:
I didn't do anything wrong. and those instructions don't work. Till the maintainer is able to fix this issue I don't see a reason to compile cm7.
[Nook Color Android Development] fattire:
Here's where things go bad:

I//system/bin/fsck_msdos( 1045): ** /dev/block/vold/179:17

I/ActivityThread( 1613): Pub contacts;com.android.contacts: com.android.providers.contacts.ContactsProvider2

I//system/bin/fsck_msdos( 1045): ** Phase 1 - Read FAT (compare skipped)

I//system/bin/fsck_msdos( 1045): Attempting to allocate 7675 KB for FAT

D/szipinf ( 1143): Initializing inflate state

D/szipinf ( 1143): Initializing inflate state

I/ActivityManager( 1143): Start proc android.process.media for broadcast com.android.providers.downloads/.DownloadReceiver: pid=1644 uid=10016 gids={1015, 2001, 3003}

D/szipinf ( 1143): Initializing inflate state

D/dalvikvm( 1143): GC_EXTERNAL_ALLOC freed 365K, 32% free 7699K/11207K, external 17965K/19378K, paused 127ms

E/dalvikvm-heap( 1143): 5038080-byte external allocation too large for this process.

E/GraphicsJNI( 1143): VM won't let us allocate 5038080 bytes

D/dalvikvm( 1143): GC_FOR_MALLOC freed <1K, 32% free 7698K/11207K, external 17965K/19378K, paused 101ms

D/skia ( 1143): --- decoder->decode returned false

W/dalvikvm( 1143): threadid=21: thread exiting with uncaught exception (group=0x40015560)

E/AndroidRuntime( 1143): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy

E/AndroidRuntime( 1143): java.lang.OutOfMemoryError: bitmap size exceeds VM budget

From a quick gander, its trying to fsck a removable volume, probably the sdcard, and running out of memory shortly thereafter while loading a ~5MB image (related to the lockscreen). At that point there's a cascade of killed processes.

I don't know if the fsck is related to the memory error, but you might try fscking/repairing the sdcard to start. And do a repair permissions too...
[Nook Color Android Development] Colchiro:
I had trouble updating from Phiremod test2 (based on nightly #136) to nightly #146 or even nightly #136. The fix was to format data.

First clue: Google wanted login credentials, but wouldn't take them, meanwhile apps in the background were FC'ing.

EDIT:

I restored my backup (PM test2), installed gApps (not Phiremod version), and rebooted. When that still worked I booted into recovery, upgraded to #146 and fixed permissions.
[Nook Color Android Development] newellj79:
I will try repairing sdcard and fix permissions (which I've done). I do have a very big image set as my lockscreen wallpaper. Would it help to change that?
[Nook Color Android Development] newellj79:
Thanks Fattire

Sure enough, I changed the lockscreen image and it works no problem. Thank you.
[Nook Color Android Development] fattire:
logcat is your friend :)
[Nook Color Android Development] khaytsus:
Of course they work. You're doing something wrong. I bet you didn't create the ini file, that's almost always why people claim adb doesn't work in Linux on the Nook Color.
[Nook Color Android Development] blahbl4hblah:
I did create the ini file. So that's not the reason why
[Nook Color Android Development] sisterchick:
SOD is back??

Any thoughts on why SOD was re-introduced with build 146? Happened first time when I did an in-place upgrade from 140 (wipe cache, dalvik, install and fix permissions). First time it went to sleep, it was SOD. I hadn't done a clean install in awhile, so I wiped completely and installed 146. Again, first time it went to sleep, it was SOD

and

it ate 60% of my battery in the process. I'm sorry, but I didn't think to get a logcat before I recharged, rewiped and reinstalled 140. No problems with that build.

Please know I appreciate the time, attention and sacrifice that goes into making this a great ROM.
[Nook Color Android Development] Colchiro:
#146 introduced this change: http://review.cyanogenmod.com/6728
[Nook Color Android Development] hetzbh:
Few issues with #146

I installed #146 and previous versions (and erasing the Dalvik cache), and I found A major issues:

Few keyboards are missing (I was looking for Hebrew keyboard, it's gone, and the list seems to be smaller). I re-installed 7.0.3 and all the keyboards layout are there, but on the latest nightly, almost half are gone..

Should I fill a bug in cyanogenmod bug system?
[Nook Color Android Development] bhrich902:
wifi battery drain...

hey all, quick observation here. Just got my nook color last week and i'm running nightly 144 of a 2GB SD card. Everything works great and is surprisingly speedy for me. I then decided to flash nightly 147 (didn't wipe anything, just dropped it in boot and booted to recovery) and noticed a nasty battery drain i'm narrowing down to the wifi.

With 144 under spare parts battery history i notice 'wifi on' at 100% and 'wifi running' at around 7 or 8% when using the tablet. fully charged overnight, i wake up to 96 or 94% battery life, all is good here.

With 147 under spare parts battery history i noticed 'wifi on' at 100% and 'wifi running' also at 100% when using the tablet. fully charged overnight, it went from 92% to around 60% the next morning.

Luckily i 144 was my first install which ill keep as my go to 'stable' one. Hope this info helps someone, and if it's been posted already, i guess we it's considered a confirmation.

thanks to the CM team and those involved in this rom, it's the one and only reason i bought the nook color 8)...
[Nook Color Android Development] harpo1:
What's your wifi sleep policy set to?
[Nook Color Android Development] bhrich902:
the default, when screen is off.
[Nook Color Android Development] harpo1:
Have you gone into recovery and wiped cache and dalvik? That would be my next step.
[Nook Color Android Development] bhrich902:
normally i would of, but running off an sd card i don't have the option (that i know off). I think making a bootable cw recovery would wipe the contents of the stock nook software. I guess that's why nightlies are meant to be running off the internal storage. ah well, maybe it'll help others running off sd card to stick with 144 (my opinion of course). Thanks anyways...
[Nook Color Android Development] TDO:
You just need the modified cw with the right mounts.

If you use this layout: http://xdaforums.com/showthread.php?t=1022786

you can use my modified cwm. (just look on the last 2 pages of the thread)
[Nook Color Android Development] bhrich902:
i'll look into that, thanks.