Android queries fb info via FBIOGET_VSCREENINFO ioctl call., and processes it.
it should be inherently taken care as per fb is set by kernel, but you can track if /hardware/libhardware/modules/gralloc/framebuffer.cpp Also, check in pdk display driver doc (at bottom), this exact problem is mentioned in troubleshoot section http://www.netmite.com/android/mydroid/development/pdk/docs/display_drivers.html => Both problems are caused by an incorrect implementation of the frame buffer's page flipping. Key events are captured, but the graphical interface appears to drop every other frame. -- Regards, Deva www.bittoggler.com On Sat, Sep 11, 2010 at 7:43 AM, James lichtenstiger <[email protected]> wrote: > I'm porting android 2.2 sense UI to the Motorola droid (OMAP3430 board- > sholes), The incredible has WVGA(480x800) panel and the Droid has a > FWVGA(480x854) panel. I tried hard coding the resolution into the > kernel, but it threw off the screen calibration and the capacitive > softkeys no longer worked. Is there a better way to set the screen > resolution, perhaps internally in android? > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
