| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updates onScreenTurningOn/device state callbacks
in the unfold overlay class to be executed on
the background thread.
This allows to draw the first black frame even
if SystemUI's main thread is busy at the moment,
so it will be less likely to have flicker because
of that.
Also this CL adds a separate thread to render
the vignette to avoid conflicting with the other
operations made on the shared background thread.
Bug: 262381044
Bug: 262518402
Bug: 233045200
Test: manual fold/unfolds with/without AOD enabled
Test: add artifical delay to SystemUI configChanged
that exceeds WM keyguard drawn timeout
=> test that there is a flicker without changes
test that there is no flicker with the changes
Test: atest com.android.keyguard.mediator.ScreenOnCoordinatorTest
Change-Id: Ic5a61839500dbbf63e9c5422bfc0085827526d92
|
| |
|
|
|
|
|
|
|
|
| |
This is the first step in moving over to the new public
android.util.Dumpable api.
Bug: 217567642
Test: m SystemUI
Merged-In: Ibaebcfb2c6c5326d0c45b8c72d868c76655d89a0
Change-Id: Ibaebcfb2c6c5326d0c45b8c72d868c76655d89a0
|
| |
|
|
|
|
|
|
|
|
|
| |
Continue dividing KeyguardViewMediator into smaller, testable
units, first by removing screen on/off calls that go here.
Consolidate screen on/off logic into one file. Add support to
Lifecycle to dispatch methods with 1 argument.
Bug: 195430376
Test: KeyguardViewMediatorTest ScreenLifecycleTest
Change-Id: I2696629fc7e1a3934503e8c94ecdeed749762769
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Creates a controller in the Shell that manipulates
SurfaceControl leash of the current active full
screen task and animates it based on the current
unfold transition progress.
Bug: 193795714
Test: manual
Test: atest com.android.wm.shell.fullscreen.FullscreenTaskListenerTest
Change-Id: I8b9f4e0530042b333c3b6b793d39049932878bb8
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Dependency.get() automatically registers its managed objects to the
DumpManager if they implement Dumpable. However, if code is refactored
that removes all usages of Dependency.get() in favor of Dagger
injection, then there is no longer a guarantee that the class in
question will be registered to DumpManager (and so included in bug
reports).
Instead, remove the auto-registration feature of Dependency in favor of
manually registering all dumpables with the DumpManager.
Bug: 198713580
Test: atest
Change-Id: Ie02a44fb7da0b76bf53da874cc9eee030a1b9173
Merged-In: Ie02a44fb7da0b76bf53da874cc9eee030a1b9173
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is far easier to move _everything_ into SysUIComponent, and then
selectively promote things back to GlobalScope and/or WMScope than
it is to try to do it one at a time. With this change, though lots
of files are touched, very little actually changes structurally.
After this change goes in, folks should stop using @Singleton quite
so freely. Most things should live in @SysuiSingleton. @Singleton
is due to quickly be replaced by @GlobalScope.
Bug: 162923491
Test: atest SystemUITests && manual
Change-Id: Idc31d3d83b030581fb1fa869f7fafc4f2d3a8828
|
| |
|
|
|
|
|
|
|
| |
Create DependencyBinder which is abstract and can tell dagger how
to convert directly between interfaces and implementations without
requiring code for it.
Test: compile (which runs dagger)
Change-Id: I7013ee12d37172441e2c70cf2fe36f707975c821
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
No longer do the upwards animation from AOD1, because there is a fade in instead now.
Also, because the DozeService gets finished when waking up, we were disallowing
animations again. Instead, we now ignore disallowing animations while waking up.
Also don't cancel the NotificationPanelView wakeup animation when another identical
request comes in.
Also adds tracing for various SystemUI states.
Bug: 63531607
Test: Wake up from AOD1. Ensure there is no jank or flicker
Change-Id: I383ffa320f28ac4bf5432e4f4f5c06372717f66f
|
|
|
Test: runtest systemui
Bug: 62446740
Change-Id: Ife34c1f4299b152a6352445adc8c9fc3c757e87c
|
