If there is no DisplayState, and it gets initialised because of any
other field, for instance refresh-rate, the brightness gets initialised
by 0. Since 0 is a permissible value for brightness, is causes issues by
changing the brightness to 0.
Bug: 259517441
Test: atest PersistentDataStoreTest
Change-Id: I532afc9e9d437199922f83f3c4440127a86a88f5
Refactor BrightnessTracker so that it receives an array of lux readings rather than listening to the light sensor
Bug: 215100807
Test: atest BrightnessTrackerTest
Test: atest AutomaticBrightnessControllerTest
Change-Id: I9807ecb39ac8962d2dae9e53c68e6eadbba5c50f
Merged-In: I9807ecb39ac8962d2dae9e53c68e6eadbba5c50f
This CL allows disassociating the leaf task if relaunched and
reparented it to TDA as root task for split-screen.
Bug: 236317871
Test: atest WindowOrganizerTests
Change-Id: I6704fab733ed7d239d7004c93d3d2f471ac94822
Merged-In: I6704fab733ed7d239d7004c93d3d2f471ac94822
Ensure that DesktopModeController and DesktopModeTaskRepository are only
created when they are needed, when the desktop mode flag is on.
With the previous dagger configuration WMShellBaseModule relied on
submodules to provide an implementation if one exists.
If the submodule does have the implementation defined, it is always created and
supplied to WMShellBaseModule provider method.
Provider method in WMShellBaseModule then decides, based on flags,
whether to return that implementation or not. But the instance is always
created, regardless of that flag check.
This change ensures that DesktopModeController and
DesktopModeTaskRepository are only instantiated if WMShellBaseModule
provider methods will provide a corresponding instance. This is achieved
by relying on lazy instance creation by dagger.
If the instances won't be provided due to flags being off, the instances won't be
created.
Bug: 260908558
Test: build and run sysui with desktop mode flag off, observe
DesktopModeController object is not instatiated
Change-Id: Ia155b8e079072e543c98463a58ab1907729db7b0
As the height is fixed, the bottom constraint is not needed. With the new ConstraintLayout version they were causing a conflict that ended up making the media player with a smaller height.
Bug: 261475673
Test: QSMediaPlayerContent
Change-Id: Ia5373a624e1c597af8d4899f9743672df23c9c88
QS was not visible because we were not updating QS expansion when heads up notification motion was in progress. Now we will do it when swiping down, so after going below starting movement position.
Fixes: 259447896
Test: show heads up notification -> swipe down on it -> QS should be visible throughout the whole down motion
Change-Id: Id54d7ac289fdd5bb527d9aa985e2bff90c4a4307
Activity info is not used by the InternetTile, so we can remove them to
avoid unnecessary tile updates.
Bug: 260714553
Test: Unit tests
Change-Id: I24575d87909db3d1824a37503458f1b7bdbced2e
