Commit 2b8d8100 authored Sep 07, 2025 by Shai Barack

Re-introduce explicit allowance of systemui to new concurrent MessageQueue...

Re-introduce explicit allowance of systemui to new concurrent MessageQueue implementation (DeliQueue)

We previously disabled sysui in concurrent MQ due to an issue with sync barriers that we could not reproduce in tests and did not fully understand.
Since DeliQueue has a completely novel approach to sync barriers, it stands to reason that it's not vulnerable to the same issue that was affecting the previous concurrent implementation.
Seeing as such, we get a do-over.
The team will monitor the situation as the flag ramp progresses.

Bug: 438822893
Flag: build.RELEASE_PACKAGE_MESSAGEQUEUE_IMPLEMENTATION
Change-Id: Ia01132d2694df56595e6d3a66ce48cb97a844979

parent 81c6443f

core/java/android/os/CombinedDeliMessageQueue/MessageQueue.java

+10 −0

Original line number	Diff line number	Diff line
		@@ -191,6 +191,16 @@ public final class MessageQueue {
		}
		}

		// Also explicitly allow SystemUI processes.
		// SystemUI doesn't run in a core UID, but we want to give it the performance boost,
		// and we know that it's safe to use the concurrent implementation in SystemUI.
		if (processName.equals("com.android.systemui")
		\|\| processName.startsWith("com.android.systemui:")) {
		return true;
		}
		// On Android distributions where SystemUI has a different process name,
		// the above condition may need to be adjusted accordingly.

		// We can lift these restrictions in the future after we've made it possible for test
		// authors to test Looper and MessageQueue without resorting to reflection.
		return false;