[android-porting] Re: Frame buffer , Hardware overlay, rendering

2011-11-13 Thread Girish
But how the video renderer is able to write into same framebuffer memory area (Logically there is only 1 hardware display) as we can see on the device. Regards Girish -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting

[android-porting] Re: Frame buffer , Hardware overlay, rendering

2011-11-18 Thread zmyde2...@163.com
For gingerbread there is a screen capture tool in: frameworks\base\services\surfaceflinger\tests\screencap It's ok to capture osd layer, but for video layer, you cannot capture by framebuffer. On 11月10日, 下午8时55分, Girish H T wrote: > Hi, > > Sorry for cross posting. Stuck up with a problem , hope

Re: [android-porting] Re: Frame buffer , Hardware overlay, rendering

2011-11-14 Thread Matt Shao
I agree with what Eric said. Yes, there is only one "screen", the finally overlay is done by hardware, so whether you can get the overlay buffer is case by case or say device by device 2011/11/14 Girish > But how the video renderer is able to write into same framebuffer > memory area (Logica

Re: [android-porting] Re: Frame buffer , Hardware overlay, rendering

2011-11-15 Thread Devaraj Rangasamy
its doable on a platform, but difficult to give a generic user side solution applicable to all devices. as google showed in android4.0 launch, screen capture is inherently supported in icecream and android4.0 source is out today.. On Tue, Nov 15, 2011 at 10:02 AM, Matt Shao wrote: > I agree wit