From 4ab77d12358dbeb7f06cd64cf3f32a6bdc75c4a4 Mon Sep 17 00:00:00 2001 From: Sean Stout Date: Tue, 9 Mar 2021 18:12:34 -0800 Subject: [PATCH] Fix DisplayGroup event reporting behavior. The check for whether a group had been previously updated was incorrect. Bug: 182322424 Test: Add a DisplayGroup and see the correct event is fired. Change-Id: I085b6b1e7cdf73a4dd8311c50e26a4f2d4a9e769 --- .../java/com/android/server/display/LogicalDisplayMapper.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/core/java/com/android/server/display/LogicalDisplayMapper.java b/services/core/java/com/android/server/display/LogicalDisplayMapper.java index d6826be248df3..fcfa674dcc4e3 100644 --- a/services/core/java/com/android/server/display/LogicalDisplayMapper.java +++ b/services/core/java/com/android/server/display/LogicalDisplayMapper.java @@ -357,7 +357,7 @@ class LogicalDisplayMapper implements DisplayDeviceRepository.Listener { for (int i = mDisplayGroups.size() - 1; i >= 0; i--) { final int groupId = mDisplayGroups.keyAt(i); final DisplayGroup group = mDisplayGroups.valueAt(i); - final boolean wasPreviouslyUpdated = mUpdatedDisplayGroups.indexOfKey(groupId) < 0; + final boolean wasPreviouslyUpdated = mUpdatedDisplayGroups.indexOfKey(groupId) > -1; final int changeCount = group.getChangeCountLocked(); if (group.isEmptyLocked()) {