| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
A call to Dependency#get had to be added to RadioListPreference,
and will have to be refactored later.
Fixes: 218350940
Test: manually built.
Change-Id: Ia30ed1ede10e03a44640561329ad7679a7f3218a
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CollapsedStatusBarFragment.
Because NotificationPanelViewController is not @Singleton but
@StatusBarScope, we need to update the fragment creation classes to
know how to get references to @StatusBarScope classes and that's the
bulk of this CL.
Bug: 205609837
Bug: 204792508
Test: atest FragmentServiceTest
Test: atest SystemUITests
Test: manual
Change-Id: I84ef8c7621944d6924775c1fe54178af296a3485
|
| |
|
|
|
|
|
|
|
| |
each time CollapsedStatusBarFragment is re-created.
Bug: 205609837
Test: manual
Test: atest SystemUITests
Change-Id: I3a6f9cfeae644e41836fbaa53495fe31a71b0a7e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Bug: 183229367
Test: atest ran and manual
Change-Id: I8f754f4d894999a4bd5c13db81324e9abe204747
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Move off fragments, now we have direct ownership of
NavBarController -> NavBar (per display) -> NavBarView
- Move the nav bar components to its own package
- Removed some unused files
- Can finally dump NavigationBarController instead of FragmentService :)
- Clean up some of the dumps to be more consistent
Bug: 163690441
Bug: 158605244
Test: atest SystemUITests
Test: Test bar in various nav modes
Change-Id: I21130899df560f6cf8b7f38d4d86edca6d8f920e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure that only the code that actually needs the root component asks
for it.
This also fixes ContentProvider injection (a bit). They no longer have
to manually run injection on themselves, as long as they implement
SystemUIAppComponentFactory.ContextInitializer properly and define
an inject(MyClass) method in the root component.
Bug: 162923491
Test: manual && atest SystemUITests
Change-Id: I507859f5f8d89bdde5b10e78b54c5cfbf28737bc
|
| |
|
|
|
|
|
|
|
| |
This is the first step in establishing separate subcomponents for
WindowManager and SysUI within the SysUI process.
Bug: 162923491
Test: manual
Change-Id: I54269e853de92b622d63186e43042780d8ef1d4b
|
| |
|
|
|
|
|
|
|
|
|
| |
ConfigurationChangedReceiver is removed. Classes that want to be
notified of configuration changes should implement
ConfigurationController.ConfigurationListener instead and register
themselves with the ConfigurationController.
Bug: 144782965
Test: atest SystemUITests
Change-Id: Id2c3fe5ae2729b181769fb31b8050da264299d72
|
| |
|
|
|
|
|
|
|
| |
This adds new Dagger qualifiers for BgHandler, BgLooper, MainHandler,
MainLooper, and MainResources, replacing the use of @Named for them.
Bug: 142954072
Test: atest SystemUITests
Change-Id: Ibbda8998e587474c26740ba8d49a8b3f90d89efa
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is a significant change that allows Services to have their
constructed injected into.
This change includes DozeService as an example, injecting the
FalsingManager into its constructor.
Bug: 136279712
Test: atest SystemUITests
Change-Id: Ib58f8763c996fbc2aea07ead56493d2d9e936f5b
|
| |
|
|
|
| |
Test: Update ignored test, somewhat
Change-Id: Iec69c52ee1d0826bbbde6aa414fb5f81d7f33303
|
| |
|
|
|
|
|
|
| |
Convert NavigationBarFragment as a proof of concept and remove all
references to Dependency from NavigationBarFragment.
Test: atest SystemUITests
Change-Id: I0cdb5bc6ac455fce91e67b9e449cb7b78b1da9a4
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Disable rotation suggestion button if the navbar is on
non-default display because there is no accelerometer sensor.
- Avoid leakage by removing navbar fragment from fragment
host when display is removed.
Bug: 117746225
Bug: 117744614
Test: atest SystemUITests
Test: manual - create a virtual display with system decoration.
The navbar on the virtual display should not change when
rotating or changing density of default display.
And after releasing the display, use command "dumpsys
activity service com.android.systemui/.SystemUIService |
grep NavigationBarFragment" to check the number of instances.
Change-Id: Icdc8634628ace21395b7eb9d77c6b1067850d1b2
|
| |
|
|
|
|
|
|
| |
Test: adb shell dumpsys activity service com.android.systemui, ensure
the nav bar state shows up.
Fixes: 79881849
Change-Id: I13e6fb4c61c02cbd142e64b7201667e47fe31232
|
| |
|
|
|
|
|
|
| |
Some UX updates to the tuner to feel better and align with settings
UX patterns.
Test: visual
Change-Id: I9c57194b9649c61e0d6d3f9e21a51d9c4a5c1286
|
|
|
Add system to add fragments to sysui windows for better code
modularity and testability.
Bug: 32609190
Test: Manual
Change-Id: I2ae7ed6133aff3fc5cdbdb3ec89d55183b7ac797
|