| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
In multi-user multi-display systems where there could be multiple
SystemUI instances running, the concept of what displays are relevant
for a particular SystemUI may change. By adding a DisplayTracker class
to abstract away display retrieval and callbacks, these instances can
return the information that is most accurate for them.
Bug: 256236871
Test: atest SystemUITests
Change-Id: I51c1a380a344fb45d5e0de2c5c6ba5610733a3a2
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Bug: 146964271
Test: Just disabling logging
Change-Id: I9b6518cbc3cccab62084c9c8a0afda6ba2c2e731
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- There is a rare chance where SysUI state can change prior to
the overview service being connected in which the sysui state
would not be passed to launcher, and when the service connects,
the updating of the sysui state could trigger no changes (due
to what it thinks is no changes in the flags).
ie:
sysui or launcher crashes
> OPS registers callbacks but service is not yet connected
so initial callback does nothing (only for sysui crash)
> sysui notification state changes, updates sysui state,
notifies OPS via callback, but still not yet connected
> OPS service connects, triggers update of all relevant
states, but notifications is already in that state, so
sysui state skips callbacks to OPS
Change-Id: I7635ed19bfc2767d380703a52b8fb623f8a43e21
Bug: 146964271
Test: Force delay OPS service connection, change sysui state
and ensure launcher is still notified
|
| |
|
|
|
|
| |
Bug: 148422894
Bug: 146964271
Change-Id: I3951544789d1c936d6ff6084da69b5907d77d8ab
|
|
|
Move all sysUi state flag handling into a
separate class.
fixes: 138601608
Test: atest SysUiStateFlagsContainerTest
Checked that callbacks were being sent in
OPS, EdgeHandler and in Launcher codebase via
debugger.
Change-Id: Ie8f7ef2e647db88d244af1062eb95dbb69a46919
|
