OSDN Git Service

Don't send config change when display is removed
authorAndrii Kulian <akulian@google.com>
Thu, 1 Mar 2018 02:51:36 +0000 (18:51 -0800)
committerAndrii Kulian <akulian@google.com>
Thu, 1 Mar 2018 02:51:36 +0000 (18:51 -0800)
commitdce1da45cadda2c9278b7fa57731e8a854e44cc6
tree6391e5b1453e661326d1b44efeb3e6da24fb13c6
parent58b0948b1ffb92217eb984aa41be545d61259e33
Don't send config change when display is removed

When a private display is removed, we're finishing all activities
that were on that display. But because the display will not be
available during activity finish process, we're fist moving all
stacks to the back of the default display, so that the removed
display won't be referenced accidentally.
This, however, can cause an additional resize message to the client
from the WindowManager if the size of the default display is
different, which will cause a configuration change. To avoid that
this CL freezes the config of the stacks being finished by overriding
to their current configs.

Bug: 73379938
Test: ActivityManagerMultiDisplayTests#testContentDestroyOnDisplayRemoved
Change-Id: I20e0becab097075ccb84e471e366a2ace37ab7cc
services/core/java/com/android/server/am/ActivityDisplay.java