yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
You have two choices. Flash your CM7 again and immediately flash the new nightly without wiping or booting between. Or flash a pre-3/10 CM9 and use it until eyeballers fix is pushed. Actually, you can keep using the newer nightlies as long as you don't wipe system.
[Nook Color Android Development] eyeballer:
Check your pm :)

I'm adding this to my builds tonight, it's been tested enough for me at least on encore/touchpad. So the 4/13 dated builds will have it.
[Nook Color Android Development] BPB21:
First off, let me give the obligatory and well deserved thanks to all the people working on this; it has made my NookColor an amazing device!

One question: has anyone successfully used a Verbatim folding Bluetooth keyboard with their Nook Color and this ROM? Sometimes I can get it to pair but not connect; when it connects it will frequently seem to "stick" on a particular key and end up looking like thiiiiiiiiiiiiiiiiiiiiiiiis. Has anyone experienced this? Any ideas? Not a big deal; just checking.
[Nook Color Android Development] DigitalMD:
You need to load a null keyboard application, There are some on the market. Otherwise the Nook is confused and unloads the Bluetooth and uses the touchscreen keyboard.
[Nook Color Android Development] tinpusher1:
Or to put it another way...

"Mad props yo." LOL:)
[Nook Color Android Development] BPB21:
Yep - crazy respect for this ROM!
[Nook Color Android Development] BPB21:
I tried the null keyboard but didn't really get anywhere with it. Ended up going with an app called Bluetooth Keyboard; free and does something like monitor for BT keyboard connections (and correctly connects them). But thanks for the tip; it got me thinking and I was able to get things going!
[Nook Color Android Development] SeaFractor:
I use this keyboard. I don't have problems getting it to pair and connect, but I did find that after connecting that if I pause for a moment or two that I don't run into stuck keys.

Likely due to paging from memory constraints. After I do the pause and wait, I no longer encounter stuck keys.

Interestingly this is the only ROM I can get the keyboard to work with. CM 7.x ROMS would say they'd paired but I could never type. CM9 has come a long way in terms of bluetooth keyboard support in my opinion.

However, the Verbatim keyboard does share blame as many other keyboards worked great under CM7 according to user reports. I just had made a mistake purchasing this keyboard. Fortunately a correctable mistake in terms of CM9 actually supporting it.

Long term, I suspect that as the ROM matures (it's still considered an alpha stage, not even yet beta) this will get much better.
[Nook Color Android Development] ryuz4ki:
Downloaded the latest nightly(20120416) and couldn't boot up my Nook, got stuck on a black screen and the Nook then proceeded to reboot, and continue for infinity, so decided to go back to the march nightly I've been using.

Any thoughts as to why that happened?

And I know this won't probably happen until HWA comes along, but any chance to run Chrome beta with these nightlies? Finally able to download it from my country directly from the Play Store and can access the settings and all, but nothing loads.
[Nook Color Android Development] leapinlar:
You probably wiped system first. The newest nightlies get stuck and do not install properly when you do that. Eyeballer has a fix in the pipeline to fix that but I don't think it was pushed yet for that build. If you flash again over the March nightly without wiping first, it should install properly.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] eyeballer:
No, the fix was merged already. Shouldn't be an issue since 4/13ish.
[Nook Color Android Development] ryuz4ki:
Just tried your solution with no such luck, once again have a black screen when booting and the Nook endlessly rebooting itself.

Going from 20120330 to 20120416. Was hoping to try the new kernel, but will hope for the next nightly to see if this issue resolves itself.

EDIT: Just flashed the new 20120417 build and had no issues whatsoever with wipe or stuck on boot, don't know what may be different from this build from the 04/16 one, but it fixed my problem.
[Nook Color Android Development] Etaduck:
No issues here, downloaded fine, but I did notice that the first time I downloaded the rom it was only 76 megs. I think I started the download before the upload was complete.

Looking foward to trying out the new wifi kernel, been having issues with the wifi at work. (it uses web authenitcation by loading a website after you connect, but the connection would never stay on long enough to pull up a website)

Thanks Fat-tire, eyeballer, keyodi, samiam303 and many others I know I left out.

This really has brought new life to my Nook.
[Nook Color Android Development] bornagainpenguin:
Running update-encore-20120417.zip and performance-wise it's been the best I've seen...it just "feels" right when moving around in the system, if that makes any sense.

Only, for some reason about a quarter of my apps (including Opera and a few others I can't think of since I'm back on CM7 again) are convinced they're on 240 dpi and changing the dpi does nothing to improve things at all.

Any ideas?

--bornagainpenguin
[Nook Color Android Development] leapinlar:
What do you mean 'convinced they're on 240 dpi'? You mean they are in their phone gui? The phone gui will show for all apps if you are above 160 dpi. If you are at 160 or lower, the device goes into tablet gui, but some apps stay in phone gui either because they have no tablet gui built in or they are getting bad information from the system. That was true for Evernote. It displayed the phone gui even though the nook was in tablet gui.
[Nook Color Android Development] bdcrim:
Opera Mobile scales correctly for me for the first time with the new kernel addition. It is not blown up and does not think the nook is a phone. I did a build yesterday and the kernel had been merged. Does Sams 4-17 build have the new .59 kernel? If so, you may try uninstalling and reinstalling those apps. Don't know otherwise.
[Nook Color Android Development] bornagainpenguin:
I mean when I change DPI it has no effect whatsoever and that I think DPI is being misreported somehow.

Here's two screenshots that might help explain things.

This is what is being reported as 160 dpi:

This is what 160 dpi actually looks like:

When I reboot to complete the changes it goes back to the faux 160dpi (which is clearly higher than being reported.)

--bornagainpenguin
[Nook Color Android Development] leapinlar:
You are talking about the lettering size? That's the only difference I can see in your screenshots.

Go to the Dev Tools app and look at configuration. It tells you the real screen density.

That screen density changing app may not be accurate.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] bornagainpenguin:
None of the them seem to be accurate at this time. Usually I use nook odds and ends, but since it didn't work earlier I tried this one. I can do some more screenshots tomorrow, I'm tired now, sorry.
[Nook Color Android Development] mateorod:
That slider for the new dpi may just be set there with an app database, waiting for you to click apply. Have you been clicking the set at boot option? It's not on in your screenshots, and I can't see why you'd unset it just to take the picture.

That would explain the return upon reboot, if that is the only problem you're having.
[Nook Color Android Development] bornagainpenguin:
I don't know what to think now, I reflashed this morning and have been unable to make the issue happen again. I did notice that Opera was using the phone GUI, but my icons were fine.
[Nook Color Android Development] notriddle:
On a friend's Nook, DoggCatcher, Kaiten mail, Amazon Kindle, IMDB, all phone UIs. But all the Google and Android apps are tablet modes, and Nova Launcher, Super user are. The system is in tablet mode. Default dpi.

Seems to depend on how they decide if something's a tablet or a phone.
[Nook Color Android Development] boomn:
Yes, there is certainly that too. If a developer doesn't think their "tablet" layout will display well enough on a 7" screen they can choose to stick to their "phone" layout.

Also, when the first real Android tablets came out with Honeycomb they were all 10" devices so many apps are probably still coded to only think of that size as qualifying as a tablet

I don't think it has to be between just two choices either. My Nook with these latest CM9 builds displays IMDB, for example, in a tablet layout of some form but it doesn't appear to be the same layout I've seen on larger 10" tablets. I need to double-check that at some point though
[Nook Color Android Development] bigbob23:
I must have missed something. How do you tell if it a phone or tablet UI?
[Nook Color Android Development] leapinlar:
Phone GUIs are generally just single panes that get larger as the screen gets larger. Usually the tablet gui's have multiple panes. Like a window on the left and a scrollable pane on the right. They take advantage of the capabilities of ics that gingerbread does not have.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] leapinlar:
I did some experimenting with imdb. My Galaxy Tab 7", which is running gingerbread at 240 dpi, shows imdb in tablet gui. It has multiple panes in landscape. One pane is stationary and the other is scrollable.

However, my Nook Color, running either CM7 or CM9, displays imdb in phone gui. It has single panes. It has a scrolling section at the top, but when you scroll the whole window, that scrolling section moves up off the screen. And it makes no difference what dpi I set in CM9, it still is in phone gui. (Edit: I ordinarily run CM7 at 240dpi, so I temporarily changed it to 160 and imdb displayed in tablet gui.)

And both devices are running the same version (2.6). So that tells me the software itself decides how to display based on what it thinks the device will support.

As an aside to this, I could not get imdb to show up in market in CM9 (running non-openGL 4/21 eyeballer), but it showed up in CM7. I downloaded with CM7, then used the apk to install on CM9.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] boomn:
I was just starting to type when I saw your edit. I had double-checked my Nook because you made me doubt my memory for a second! With standard 160dpi mine shows a tablet layout like you said and it appears in the market too. Screenshot in case anyone's curious
[Nook Color Android Development] leapinlar:
That screenshot is of CM9, and imdb is showing in tablet gui. Mine still shows phone gui at 160. Are you running opengl? Mine is non. And at 160 still no market.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] boomn:
Sorry, I should have clarified further: it's a recent non-opengl build from eyeballer (4/17 think) with no changes or mods. I'm really just assuming the dpi is 160 because I haven't changed anything over stock
[Nook Color Android Development] leapinlar:
Ok, I found out why my system is not showing IMDb in tablet GUI in CM9. I am using my patched framework-res.apk which sets the 'showNavigationBar' value to true. And even though I can set the dpi to 160 and CM9 displays in tablet GUI, IMDb sees the framework-res setting and displays in phone GUI at all dpi settings.

But it still does not show in Market. Of course I have frozen my system to always run an old version of Market, so that might be making a difference too.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] mateorod:
In the recent versions of the Play Store you can set it to no filters in the settings. I am pretty sure that all the apps show up: IMDB, call blockers, camera effects and stuff like that are there for me..

If that even helps.
[Nook Color Android Development] skwalas:
I'd been meaning to reply to your assertion here: its wrong. The filters setting has to do with maturity content only. It won't do a thing for any other kind of filter in place, device-specific or otherwise.
[Nook Color Android Development] mateorod:
My mistake. Since I don't flash the telephony fix, yet still have phone apps in market, I thought that was it.
[Nook Color Android Development] grayfoxmg1:
I haven't flashed telephony in a long time, I'm pretty sure it's integrated now.
[Nook Color Android Development] jdebay:
The latest nightly?

The latest nightly update-encore-20120421.zip is bad. It is only 5.2mb big and will not even open to see what is going on. Sorry to say this.

Keep up the good work. Image works fine for me.

:confused::confused:
[Nook Color Android Development] deshwasi:
I did this install a while ago. pardon me but i forget how to update it. can someone put a quick 1-2step process on how to update to current nightly? i have a sd card based setup using the verygreen method. dont remember if i need to pop out the sd card and copy the "update" file to the root directory or can i use rommanager app to do this?
[Nook Color Android Development] leapinlar:
Pop out the card and put the file on the root directory. Put back in and using the boot menu boot to SD recovery. Do not use rommanager, that is for emmc installs.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] deshwasi:
thanks a lot. do we need to re-flash gapps upon every install of nightly?
[Nook Color Android Development] leapinlar:
No. If it was already installed, no need to do it again.
[Nook Color Android Development] deshwasi:
anyone have a recommendation for the best (most stable) nightly build so far? i have to set one up to give to someone who just needs to use it for email/web. dont want any surprises. if someone has a favorite nightly pls let me know asap. thanks. (i have the 4/26 one running for a day or so. seems ok but dont have enough time to test it as the guest is leaving tomorrow)
[Nook Color Android Development] leapinlar:
Use eyeballers 4/28 non-opengl version (on techerrata.com). It has the new, non-rotated kernel and is very stable.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] deshwasi:
thanks for this. is there a way to use TWRP instead with an sd-card install?
[Nook Color Android Development] leapinlar:
No. That CWM has been modified to work with the partitions on the SD. TWRP is still set up for emmc.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] deshwasi:
can i still flash TWRP to emmc and have the same setup i have (nook color on emmc and CM9 on sd card). no biggie if not. i can still use the script (you posted) for the direct install of nightlies? thanks a lot for your help leapinlar.
[Nook Color Android Development] leapinlar:
Yes. TWRP works on emmc. As long as you use it for emmc only. But I don't know if TWRP has the option of putting the nandroid backup files on the emmc media partition or not. If not, you must swap out your CM SD for an ordinary SD before doing a nandroid backup of emmc. And you still need to use the special script on the SD boot partition to install new nightlies to SD.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] eyeballer:
Yes, TWRP can switch between internal and external memory for storing backups. Default is actually internal memory and you can change it in the mounts menu.
[Nook Color Android Development] Samiam303:
For what it's worth -- as far as I know this fix hasn't been integrated into the rom. The reason for this is that it isn't strictly supposed to be -- the nook doesn't support phone functionality so the file allowing for phone permissions isn't present on the nook. From what I understand, it used to be included in CM7 because there was no real official "tablet" configuration before ICS, so everything was just assumed to be a phone. However, since ICS now takes into account that some devices may not be phones, the nook color is configured as a tablet instead of a phone.

What this means is that we've ended up with a number of apps who request phone permissions even though they have plenty of other features that aren't phone specific, and thus don't show up on tablets. This, ideally, should be fixed by the developers either releasing a tablet version of their app or just finding a way to do the same thing without using the phone permission. However, in the mean time it's useful for us to "hack" in the phone permission even though it isn't going to be included in the main build configuration. Sure, I could just include it in my builds -- but I made the decision to keep these as stock source builds so as to avoid introducing any outside bugs or issues.

tl;dr version: as far as I know you still should flash the .zip if you're interested in seeing all the apps.
[Nook Color Android Development] tnpapadakos:
and that is definitely the way to go when compiling as you are doing
[Nook Color Android Development] skylar.sutton:
+1, running this on three NC's and have found it to be the best yet.
[Nook Color Android Development] bhalbower:
replacement wpa_supplicant file for ICS

Anyone find a good replacement wpa_supplicant file for ICS that would enable Ad-Hoc WiFi mod? Can't tether my Nook to my phone now that I have upgraded from CM7 to CM9. (I don't have a phone that can allow infrastructure WiFi connections. I have tried several that used to work for CM7 with no luck. Not worth downgrading to CM7 just for Ad-hoc tethering so I am living without it for now.
[Nook Color Android Development] Samiam303:
I don't know the answer to this question, but you may have more luck posting it in the general ICS dev thread than in the thread specific to my builds.
[Nook Color Android Development] gnuts:
Hello all, firstly I must say thank you. I have been using the nightlies for quite a while. For the last few rounds I noticed posts that stated that flashing the gapps file from the misc folder was no longer necessary. My experience had been different in that when I flash a new nightly the gmail icon is still present but when clicked the screen flashes and goes straight back to the app menu screen. I have worked around this by reinstalling the gapps file. Today I flashed the newest nightly and went to the misc folder and it is gone where can I get a gapps file and or what do I need to do to fix my wonderful ics nook so that I no longer need to reinstall? thanks for reading my question.
[Nook Color Android Development] leapinlar:
The gapps that were in the misc folder were old and outdated. You should get them at goo.im/gapps. Look for the latest ics version.
[Nook Color Android Development] gnuts:
Thank You, I have the latest gapps installed now. All is well.
[Nook Color Android Development] fattire:
99% of changes appear here: review.cyanogenmod.com

If I update any encore/NC-specific stuff, you'll see it here.
[Nook Color Android Development] Samiam303:
Most of the issues related to the gapps were apps crashing upon opening, which was from people flashing a version that includes OneTimeInitializer.apk. If you experience that problem you just need to remove that particular APK through ADB or Root Explorer, then wipe the dalvik cache. That said, you're welcome to keep using the google apps you already have installed if you're just as happy with them. Nobody wants you to be unhappy!
[Nook Color Android Development] disynthetic:
In regard to observations about the ICS updates, I have a pertinent finding in regard to the DPI settings some members of XDA have expressed curiosity over.

I've tried several variations to install scenarios and have discovered that if you install an ICS update.zip on top of a fully customized install of GB, most functionality carries over, and that includes your DPI settings and minfrees and such from any build.prop edits. You do lose a little speed though. Unless you wipe cache, data, and Dalvik before installing the ICS update.zip.

Further, more general observations: My personal tastes for how I setup my tablet are to circumvent the Google apps entirely and further, I like to remove several additional APKs from /system such as Calendar, Contacts, Phone, Camera, Sound Recorder-- around 10 or so altogether. I have noticed quicker movement throughout the user interface and with programs (system boot times, too) due to the decreased demand for system resources and CPU time. I have a core set of cherry-picked apps I use. Don't need the market because APK files can be downloaded and installed as needed--I keep mine archived on the SD card since I reinstall a LOT due to tweaking.

[By the way, those who use the V6 script(s): It's unnecessary. Just use Auto Memory Killer. It changes the same settings and allows you to set your own minfrees. Look up what they are, they are a useful setting that your requirements for may change depending on what you are currently doing. But I'm a tweaker by nature, so that may not be for everyone. /end rant]

System stability is almost never an issue (About Tablet in Settings crashes since it links to a Phone.apk reference and I remove that file, gaining a LOT of battery time) and the remaining apps form a nice barebones Android interface. This is far more workable in ICS than in GB, in my opinion, because GB was a ot more disparate/fragmented in the "proximity" of things you wanted to accomplish in a session of using the NookColor--consolidation of similar settings in the same place has increased with ICS, fewer required menus and submenus, the number of apps required to wrestle more control out from behind the curtain and giving it to the user... things of that nature.

I must admit though, having player with Google Currents, it IS a rather nice experience for consuming information. Maybe I'll see if I can't get it to work without requiring the whole Google Apps framework to be present.

Just some observations. One last one: As sad as I am to have to say it, I want for User Interface 2D acceleration above all else. Unfortunately, I may have to abandon my NookColor for a NookTablet soon (now that the signed bootloader is circumvented) as it has the appropriate kernel required to allow for UI acceleration. With some insight from the Kindle Fire developers UI accel seems very attainable, and that work would help very much unravel Nook Tablet's UI acceleration. I'll be sad to see it go, but at least the Tablet will be an improved experience: I do enjoy the no-slip physical treatment to the NT exterior, the faster graphics and more-than-double memory.
[Nook Color Android Development] jewnersey:
so, i downloaded the newest and flashed following the instructions, after doing a full wipe, and it never makes it to the boot animation. just black screen following the initial cyanogen bootscreen.

edit :: now its saying that the zip is bad.. gonna redownload

worked after redownloading.

cant mount SD
[Nook Color Android Development] asting:
Wow I have to say this rocks. Thank you very much. It's pretty speedy for me and works well. The only issue I have is the aforementionedkeyboard alt problem. Also, what are you guys using for over clocking? I used CPU tuner. Is there any built in setting like on cm7?

Thanks for the work!
[Nook Color Android Development] electrikjesus:
ROM Toolbox allowed me to OC just fine.
[Nook Color Android Development] asting:
Okay great.

The only thing missing IMO is the video driver to allow netflix support. That should hopefully make the transitions and everything a little snappier too. I can't wait!

I may return to cm7 for netflix :/, but then again, what else is my phone for?
[Nook Color Android Development] electrikjesus:
The video for many apps works fine, check out TV.com for instance, so I think it may just be something with the hardware accelerated video for the Netflix app.
[Nook Color Android Development] asting:
Yeah that's what I meant to specify. The transitions aren't quite as smooth as other tablets but I'm sure they will improve, and even know they're still pretty damn good.