OSDN Git Service

don't automatically unblank external displays
authorMathias Agopian <mathias@google.com>
Mon, 8 Oct 2012 22:12:36 +0000 (15:12 -0700)
committerAndroid (Google) Code Review <android-gerrit@google.com>
Tue, 9 Oct 2012 21:49:01 +0000 (14:49 -0700)
this should be handled by the display-manager. we were doing
that in SF because until recently we didn't have enough support
in the HAL. however, this is now causing other problems when
plugging hdmi while the screen is off for instance.

Bug: 7150885
Change-Id: I739b209056a765d38d05295cf202f67ee0f506ae

services/surfaceflinger/SurfaceFlinger.cpp

index 8367417..17c67f9 100644 (file)
@@ -1212,12 +1212,6 @@ void SurfaceFlinger::handleTransactionLocked(uint32_t transactionFlags)
                                 state.viewport, state.frame);
                         hw->setDisplayName(state.displayName);
                         mDisplays.add(display, hw);
-                        if (hw->getDisplayType() < DisplayDevice::NUM_DISPLAY_TYPES) {
-                            // notify the system that this display is now up
-                            // (note onScreenAcquired() is safe to call from
-                            // here because we're in the main thread)
-                            onScreenAcquired(hw);
-                        }
                     }
                 }
             }