summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorRiddle Hsu <riddlehsu@google.com>2020-07-04 02:05:36 +0800
committerRiddle Hsu <riddlehsu@google.com>2020-07-06 19:04:28 +0000
commit1e431500734794d526299f0fc682e1e83ac6049a (patch)
tree26d2b1b92950d0c4d8d6af62043ba4080d66db24 /tools/aapt2/java/JavaClassGenerator.cpp
parent11d0c95fd08b2c125496658eace4a8f8fa3c3857 (diff)
Fix boot timeout and reduce boot time
Since the notification shade has been separated from status bar to another window where the keyguard resides. It won't be visible until KeyguardViewMediator receives system ready. By making the visibility of notification shade consistent with the initial state of keyguard when attaching the window, window manager won't miss to wait for it. That avoids dismissing boot animation too early. The windows of notification shade and wallpaper can also be drawn earlier, that reduces the total waiting time of drawn windows by about 50~100ms on a mid-end device. The logic of wait-for-visible-not-drawn-window is restored to be the same as Q. The isVisible considers the independent visibility of wallpaper and visibility of the insets client. The isDrawnLw accepts READY_TO_SHOW so even keyguard decides not to use wallpaper, the procedure won't wait until timeout. Bug: 160271169 Bug: 158144185 Bug: 157746100 Bug: 157281833 Test: atest DisplayContentTests# \ testShouldWaitForSystemDecorWindowsOnBoot_OnDefaultDisplay NotificationShadeWindowControllerTest#attach_visibleWithWallpaper Test: Boot with enable/disable keyguard/wallpaper, there is no timeout and black screen or flickering. Change-Id: I2f979055e89ae5e40af05e469741bb89e2e24ce6
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions