I don't know exactly where to post my question, so I'll just ask it here and move it to a more appropriate location if needed.
On Android 6.0, is hardware composer enabled on virtual displays?
I am trying to modify surface flinger to do some post processing of the primary display content. Blending all the layers on GPU is a tad costly and I wanted to alleviate this by using the hardware composer instead. To that end, I create a virtual display and send all the layers to this new display. Result is then read back through a layer on the primary display. But composition is always GLES.
Has anyone tried this before? A few pointers, or documentation, would be greatly appreciated.
Drilling down AOSP/hardware composer's code showed I had a problem with surface sizes. That beeing said, I still have other issues. Is there any documentation available on MDSS? The most relevant document I found is https://developer.qualcomm.com/download/db410c/android-display-overview.pdf but is a bit light on actual mdss actual usage and parsing code is very time consuming since I am not too familiar with this hardware. Help would be greatly appreciated.
Is it possible to open a direct ticket?
it is not well working on zebronics hardware components check details recruitment portal