[Nook Color Android Development] steven676:
Frequently Asked Questions and Troubleshooting

The install fails with errors from "set_metadata_recursive"!

The installation appears to succeed, but nothing's changed when I reboot!

You'll need an updated recovery to install CM11. For CM11 nightly builds from May 16 and later, any recovery that reports itself as ClockworkMod 6.0.4.8 or later should work; other non-CWM recoveries should work if they incorporate the necessary changes to suppor these builds (you'll have to ask their maintainers for details).

For older CM11 nightlies, any recovery that reports itself as ClockworkMod 6.0.3.6 or later should work; other non-CWM recoveries such as TWRP 2.6.3.0 or later should be fine provided the kernel is sufficiently new (you'll have to ask their maintainers for details). NOTE:

Do not use

ClockworkMod 6.0.3.x builds older than 6.0.3.6, as they contain a bug which may brick your device!

I installed CM11, wiped /data, and now my tablet's been booting for an awfully long time. Is something wrong?

First boot will take at least five minutes, and the boot animation currently stops many times during this process. If you've been waiting more than 10 minutes and it's still not booted up, you probably have a problem.

The soft keyboard keeps crashing!

The Play Store is acting up!

Did you flash the correct Google Apps? If on an eMMC install, are you sure your Google Apps fit on /system?

How do I install this to an external SD card?

See this excellent guide by leapinlar for instructions. It's reported that Google apps installation is broken in the SD card installer at the moment, so you may need to wait for that to be fixed.

What happened to the "Developer options" and "Performance" screens in Settings?

They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM11 nightlies, it'll be something starting with "cm_encore-userdebug 4.4.2 KOT49H" or "cm_encore-userdebug 4.4.3 KTU84M") seven times.

How do I get the Honeycomb/ICS tablet UI?

You can't -- Google killed it off in Android 4.4.

The lock screen doesn't rotate!

The screen doesn't rotate to the sides I want!

Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.

For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:

Android likes to think of the "natural" orientation (0 degrees rotation) as landscape with the N key on the right side of the screen. (This is a change from CM10 and earlier, when we were carrying a hack to change this.) The degrees of rotation are counted in the counterclockwise direction, so in essence, each of the rotation settings allows the following:

0 degrees: landscape orientation with the N key on the right side of the screen

90 degrees: portrait orientation with the N key on top ("upside down")

180 degrees: landscape orientation with the N key on the left side of the screen

270 degrees: portrait orientation with the N key on the bottom ("right side up")

I enabled ART, and now my Nook Color won't boot!

ART isn't supported on Nook Color at the moment due to known issues:

The initial compiling pass that happens the first time you enable ART may cause your tablet to run out of both RAM and disk space.

Many of the Google apps packages for CM11 are incompatible with ART.

If you're currently stuck in a bootloop after enabling ART, boot into recovery and then see this post by fattire for advice on how to restore your system to a working state.

I can't get any of the ROMs or recoveries for Nook Color to boot!

Before you go any further -- are you sure you have a Nook Color and not a Nook Tablet? The two devices look almost identical, but Nook Color (model number BNRV200 -- check the fine print near the speaker grille on the back) has a dark gray bezel, while Nook Tablet (BNTV250) has a light gray or silver bezel. The two devices are not interchangeable -- Nook Color software will not boot on Nook Tablet and vice versa.

If you've got a Nook Tablet, you want to be in the Nook Tablet forums instead.

I'm having a problem with my Nook Color running CM11.

That's not a question :p

Okay, I'm having a problem with my Nook Color running CM11 -- is there something I can do to troubleshoot?

Glad you asked! Please check the following:

Does the problem occur with a clean install of CM11? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).

Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).

Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)

I'm having no luck with the suggestions above. What information should I include with my bug report?

When reporting a problem, please include the following information if at all possible:

Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?

For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.

For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).

For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.