Mathias Agopian abe815dd69 rework how we take screenshots for a CPU consumer ... We're not using IMemoryHeap as a transport anymore, instead we're providing a CpuConsumer and use the IGraphicBufferProducer version of the screenshot API. However, some GPU drivers don't support properly a GPU to CPU path, to work around this, we use a temporary BufferQueue on the server side for the GL rendering, and we use glReadPixels into the CpuConsumer (we're now using a CPU to CPU path which is always supported). Currently this "wrapping" is always performed, but it can be bypassed on devices that support the GPU to CPU path. This also addresses a DoS attack vector on SurfaceFlinger, where an application could consume all of SF's filedescriptors by creating a lot of screenshots in a row. Bug: 8390553 Change-Id: I9e81514c2a7711b9bb393f74305be7d2abe08f1c		2013-03-19 22:22:21 -07:00
..
powermanager	Use new PowerManager API.	2012-08-15 01:16:39 -07:00
sensorservice	Revert "improve sensor fusion" -- DO NOT MERGE	2012-10-01 20:31:05 -07:00
surfaceflinger	rework how we take screenshots for a CPU consumer	2013-03-19 22:22:21 -07:00