Originally Posted by jhanford
Interesting. I have the same GPU (OpenGL) information on my DroidX and yet the NC has "Frame buffers: unsupported" whereas its "supported" on DroidX.
Also noted that the Sensors section is fairly sparse (again in comparison to my DroidX)
It IS very interesting. If not to say scandalous. Unsupported Frame buffers may mean mediocre video playback and so-so UI snappiness (compared to what OpenMAX/Open GL ES 2.0 can offer when engaged in full.)
Obviously, the NC should be Cyanogened with the inclusion of all 2D/3D hardware accelerated drivers of Droid X/Droid 2, overclocked to 1....1.2 GHz ASAP.
Quadrant shows free ~100 MB out of ~500 MB, what is it? Must be B&N watchdogs protecting an NC user from using Amazon, Borders shops. Obviously, they don't work, so find and get rid of them, what are you guys waiting for? Do your local dump and clean your NC.
Framebuffer 'not supported' must be because exactly this reason: there's no memory allotment for FB big enough to keep several (4....16) fields/hires screens in cache for smooth hires video and UI transitions