OSDN Git Service

Compute merged configuration changes
authorAndrii Kulian <akulian@google.com>
Wed, 1 Mar 2017 04:28:25 +0000 (20:28 -0800)
committerAndrii Kulian <akulian@google.com>
Wed, 1 Mar 2017 19:13:46 +0000 (11:13 -0800)
commit0d8ff25fabae95d5ffc826adbb68b4036d41af41
treed203ffe744b8dd890c71a0dc704cd331dffb3b86
parentfbe8553860fd99b0a1ac98af453acb7f08c506fd
Compute merged configuration changes

When we compute configuration changes to decide whether to relaunch
an activity or just report a coniguration change, we were calculating
task override changes and global changes separately. This results in
incorrect set of detected changes if we're moving between the
displays. E.g. when moving from secondary display to the primary
a lot of override config values change from empty to non-empty.

This CL switches to calculating configuration changes for merged
task configuration (global + overrides).

Bug: 34164473
Test: android.server.cts.ActivityManagerDisplayTests
Test: #testOnMovedToDisplayCallback
Change-Id: Icd6d10a49ab3ef80e00caf92cfd46e491b079d50
services/core/java/com/android/server/am/ActivityRecord.java