Hello, I have got the same problem. SurfaceFlinger uses the DisplayHardware (which uses the FrameBufferNativeWindow class) to get the frame buffer resolution once when it starts up. The frame buffer driver (which I am using) already has an interface to switch the resolution dynamically (using ioctl from user space) but the SurfaceFlinger doesnt notice the change. Is there any chance to adapt the Surface Flinger to recognize the resolution switch? Maybe there are only some small changes i.e. by ioctl'ing FBIOGET_VSCREENINFO to the frame buffer driver in the surface flinger's main loop to notice a resolution change and when happened set some variables according to the new resolution? Would be very easy this way ;-) Any useful ideas?
Best regards inok On Dec 3 2010, 4:02 am, Nitin Mahajan <[email protected]> wrote: > Hello, > > I am running Android 2.2 on a non mobile phone device, which supports > different display devices like TV and VGA.. > > What would be the right way to tell Surface flinger that the underlying > framebuffer device resolution has changed, and now the graphics should be > painted with new resolution... > > I had been trying to do some , experiments with Surface flinger regarding > this, not successful though. > > Can i get some pointers towards this... > > regards > > -Nitin -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
