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

The soft keyboard keeps crashing!

The Play Store is acting up!

Did you flash the correct Google Apps?

How do I install this to an external SD card?

See this excellent guide by leapinlar for instructions.

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 CM10.2.1 stable, "cm_encore-userdebug 4.3.1 JLS36I bf3d49df9c test-keys") seven times.

How do I get the Honeycomb/ICS tablet UI?

You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)

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'm having a problem with my Nook Color running CM10.2.

That's not a question :p

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

Glad you asked! Please check the following:

Does the problem occur with a clean install of CM10.2? 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.