Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

New Pipeline: isNewPipelineEnabled() is always true.

Browse Source 
This just deletes Flags.NEW_NOTIFICATION_PIPELINE_RENDERING and returns true where it was used.

Change-Id: If2e36064a7b8dfc1f27ec046818ee68696a7e387
Test: attempt to disable flag; new pipeline stays on.
Bug: 200269355
This commit is contained in:
Jeff DeCew
2022-06-03 14:45:16 +00:00
parent ecae4748db
commit 1f72161a15
2 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
packages/SystemUI/src/com/android/systemui/flags/Flags.java
View File

@@ -43,9 +43,6 @@ public class Flags {
/***************************************/
// 100 - notification
public static final BooleanFlag NEW_NOTIFICATION_PIPELINE_RENDERING =
new BooleanFlag(101, true);
public static final BooleanFlag NOTIFICATION_PIPELINE_DEVELOPER_LOGGING =
new BooleanFlag(103, false);

3
packages/SystemUI/src/com/android/systemui/statusbar/notification/NotifPipelineFlags.kt
View File

@@ -48,8 +48,7 @@ class NotifPipelineFlags @Inject constructor(
fun assertLegacyPipelineEnabled(): Unit =
check(!isNewPipelineEnabled()) { "Old pipeline code running w/ new pipeline enabled" }
fun isNewPipelineEnabled(): Boolean =
featureFlags.isEnabled(Flags.NEW_NOTIFICATION_PIPELINE_RENDERING)
fun isNewPipelineEnabled(): Boolean = true
fun isDevLoggingEnabled(): Boolean =
featureFlags.isEnabled(Flags.NOTIFICATION_PIPELINE_DEVELOPER_LOGGING)