diff options
| author | 2025-02-05 20:19:32 +0000 | |
|---|---|---|
| committer | 2025-02-06 10:04:16 -0800 | |
| commit | 0a4d8d88166b77668b364efb84be6cca60804fdb (patch) | |
| tree | da8d716b90a46264b4029a0d81324dcb78cbb7a0 /libs/androidfw/AssetsProvider.cpp | |
| parent | c6ac4dc997e73915ae4c8590a55c20da9e725d45 (diff) | |
Make sure the current shade blur uses the old blur radius value when notificationShadeBlur flag is not enabled.
Ramping up the bouncer_ui_revamp flag led to jank in the NOTIFICATION_SHADE_EXPAND_COLLAPSE CUJ because it was using the 60dp radius by mistake.
This might help reduce the jank for now, but it might come up when we ramp up the notificationShadeBlur flag later on. Jank requires a bit more investigation, the intent of this CL to isolate the flag's impact to only the bouncer CUJs.
Bug: 394275414
Bug: 393199337
Flag: com.android.systemui.bouncer_ui_revamp
Test: NA
Test: verified manually that shade pull down still uses the old blur radius
Change-Id: I35d0f873a059f042d85903b24ca142215dd4f95e
Diffstat (limited to 'libs/androidfw/AssetsProvider.cpp')
0 files changed, 0 insertions, 0 deletions