From 5b3cfe42f05ff4996d8d7098160d68c5235be658 Mon Sep 17 00:00:00 2001
From: Sudheer Shanka <sudheersai@google.com>
Date: Fri, 7 Apr 2023 09:04:58 +0000
Subject: [PATCH] Always propagate the reported proc_state to
 WindowProcessController.

When forceProcessStateUpTo() is used, we update the mRepProcState
but we don't propagate this to WindowProcessController which means
it won't always know when an app came out of the Cached state and
won't send any delayed configuration-changd event.

Bug: 274240050
Test: manual
Change-Id: Ie7f90d7fca381bc552683a69e5278dc5992a94e3
---
 .../core/java/com/android/server/am/ProcessStateRecord.java     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/services/core/java/com/android/server/am/ProcessStateRecord.java b/services/core/java/com/android/server/am/ProcessStateRecord.java
index eb1fd3aa49be9..5a0e8e3e65499 100644
--- a/services/core/java/com/android/server/am/ProcessStateRecord.java
+++ b/services/core/java/com/android/server/am/ProcessStateRecord.java
@@ -618,7 +618,7 @@ final class ProcessStateRecord {
     void forceProcessStateUpTo(int newState) {
         if (mRepProcState > newState) {
             synchronized (mProcLock) {
-                mRepProcState = newState;
+                setReportedProcState(newState);
                 setCurProcState(newState);
                 setCurRawProcState(newState);
                 mApp.getPkgList().forEachPackage((pkgName, holder) ->