true, its surfaceflinger that owns fb0 by default in android., instead of tweaking existing framework, why cant you create a surfaceflinger client, and post your surface? (like all app does it by default today, using their isurface handle). Probably you need to port /dev/fb calls to SurfaceComposerClient calls.,
-- Regards, Deva www.bittoggler.com On Thu, Sep 9, 2010 at 8:49 PM, wrobelekelemelek < [email protected]> wrote: > Hi, > > I'm newbie in android. I'm trying to port application that uses /dev/ > graphics/fb0. From my first test it looks like that some other > application write to frame buffer (I guess surface flinger). > > And here are my questions: > > 1. can I somehow configure Surface Flinger to stop writing into frame > buffer? > 2. perhaps it is better to create second frame buffer? In this case > how to force surface flinger to display it? Do I have to use > SurfaceView::onDraw and copy data from second frame buffer into > Picture (and then draw it on canvas)? > > Thanks, > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
