Go to file
Jesse Hall a8026d21f3 Stop using transparent region for computing visible regions
The transparent region hint is computed only from view layout
locations, ignoring post-layout translation. If a SurfaceView is layed
out with no other views above it, but a view is moved above it
post-layout, that view's layout bounds would be subtracted from the
window's transparent region instead of its drawing bounds. Prior to
this change, the view would not be visible (except where its layout
bounds and drawing bounds overlap).

With this change, composition uses visible regions computed without
regard to the transparent regions. However, if all of a layer's
visible region is transparent, it will be removed from the list of
layers to composite. This doesn't fix the root problem of incorrect
transparent regions, and doesn't prevent bad composition in all cases.
But it does avoid it for some existing apps, whiel still allowing the
transparent region hint to save power in the important
fullscreen-video-in-a-SurfaceView case.

Bug: 7179570
Change-Id: I47cf939e12129b167afa344b8b036e8827103ac8
2012-09-26 14:41:51 -07:00
build Configure GC free to be 8MB for devices with >512MB RAM. 2012-09-23 16:41:57 -07:00
cmds Merge "Use a named constant rather than a magic number." into jb-mr1-dev 2012-09-17 12:11:25 -07:00
data/etc Add android.hardware.camera.any feature to camera permissions. 2012-09-23 09:53:51 -07:00
include fix a crasher when running out of memory 2012-09-25 15:30:38 -07:00
libs Show build config in dumpsys SurfaceFlinger 2012-09-25 11:31:46 -07:00
opengl Merge "EGL: add the EGL_ANDROID_framebuffer_target enum" into jb-mr1-dev 2012-09-24 18:21:14 -07:00
services Stop using transparent region for computing visible regions 2012-09-26 14:41:51 -07:00
MODULE_LICENSE_APACHE2
NOTICE