[Nook Color Android Development] rhester72:
My own experiences with VG's 1.2.0 u-boot on a SanDisk 8GB Class 4, clean-installed beta 3.1, gapps 0503, 160dpi and the HTC vision hack, and the OC kernel (@1.2GHz w/smartass scheduler):

On the plus side, wifi is rock-solid for me on the beta, unlike CM stable for time out of mind. Ironically, the behavior I saw with stable (had to periodically delete connections to get connectivity back, network cutouts after about 2 minutes, etc., etc.) that people are attributing to the beta are _precisely_ what I saw with stable...but have yet to see on the beta.

Deep sleep appears to be working mostly fine. I've had an incident or two where the n key didn't bring the screen back, but no SODs, either when/after charging or idle.

I have had the mysterious battery issue, which manifested itself by odd and sudden shifts in battery percentage, particularly after reboots (as much as 12% swings!). I never saw this on stable.

ADW Launcher EX will always return to "small" icons after a reboot. Simply toggling the large-icon hack off and back on solves the problem, but must be done after each reboot. Never seen on stable.

Disney Princess Puzzle from the Market (hey, I have a young daughter, alright? ;) does not run fullscreen, even with compatibility mode off. This worked fine on stable.

I have had exactly one mysterious FC of the status bar, which immediately reloaded itself.

Most troubling, I've encountered an issue where returning to the home screen after watching Netflix *ALWAYS* results in an instant switch from smooth, reliable performance to _horrible_ lag. Force-killing Netflix doesn't improve things, and my CPU activity is less than 17% at that point but the device still crawls like molasses. The only thing I've found to 'fix' it is to reboot, at which point everything is perfectly normal again until I start watching Netflix and exit out. This was not seen under stable, and happens whether I'm using smartass or ondemand schedulers - I haven't had a problem yet that I could directly attribute to smartass, and I wonder if people are unfairly blaming it when the real problem may lie elsewhere. I have not yet tested with the stock kernel, but I expect similar results.

It's the last issue that may force a return to stable for me. I don't have ADB, but if anyone thinks it would be helpful, I can push it back to the 'slow' state and check /proc/kmsg while still running to see if there's anything of interest. (This is 100% repeatable, so anyone can give it a try.)

One other thing I'd like to point out is that, as much of a pain in the ass it might be, the ability to switch between 16-bit and 24-bit is sorely needed. I don't deny that 16-bit significantly accelerates 3D, but certain MP4 videos and Netflix (see the skies in most any early episode of Airwolf for a great example) show massive and distracting color banding in 16-bit that is just awful. It's a pity to have such capable hardware marred by such ugliness, particularly when showing it off to friends! *laughs*

On a more serious note, _please_ consider making this capable of being user-toggled (ideally separately between 2D and 3D). That, plus the much-rumored volume "fix", would make this the tablet to beat.

Many, MANY thanks to all the hardworking devs that have made all this possible and the Nook such a compelling device!

Rodney