* changes:
Integrate new touch architecture with UdfpsController
Change computed properties to regular in UdfpsOverlayParams
Introduce testable UDFPS touch architecture
Add rotatePointF to RotationUtils
Add tryDismissingKeyguard() to UdfpsController
After ag/20514286, the DeviceStateProvider no longer reports state if
the sensor values do not match the declared states. For the invalid
sensor config test, the onStateChanged() will not be called because the
sensor config is invalid.
(I thought presubmit would run all the tests, so I didn't run them
locally when submitting ag/20514286.)
Fix: 260572046
Test: atest FrameworksServicesTests:com.android.server.policy.DeviceStateProviderImplTest
Change-Id: Ic7aa004747fa940aa3445ed537dd76ee00c72553
We want to share this code between System UI and ThemePicker.
Fix: 259728815
Test: System UI and WPPG both build and work end-to-end with
customizable lock screen quick affordances.
Change-Id: If2fe99c5d679da57e00c6fcece10a1d2fc9ca807
This was needed because of a Dagger-related crash when querying the
content provider while a secondary user is selected. I don't understand
why it was happening, but this fixes it and is a safe fix.
Also formats the file using `ktfmt`.
Bug: 254333599
Test: when signed in with a secondary user and querying the quick
affordance content provider from the wallpaper picker experience, we no
longer see a crash.
Change-Id: Ie195b21934179576051371181560c2263284b98c
Adds support for backup & restore of the currently-selected quick
affordances on the lock screen.
Only supports user 0 for now. A future CL will add support for additional users since the feature is broken for multi-user anyway (see b/260251307).
Fix: 258278136
Test: added test case. Manually verified, using the instructions from
go/localtransport that selecting some affordances, then triggering a
backup, then changing the selections and triggering a restore properly
restores the initial set of selections.
Change-Id: I9f2a51287a7467af95e7824f2b1804baba962099
Before, when there is no ActivityEmbedding, the transition is requested
later when the previous top Activity is paused to resume the Task top,
which works ok. But when there is ActivityEmbedding, the organizer may
request WCT that trigger visibility update before a transition is
requested, which cause a flicker.
When startActivity with FLAG_ACTIVITY_REORDER_TO_FRONT to bring an
existing activity to the front, we should call prepareAppTransition
early to make sure the following activity visibility change is tracked.
Fix: 255701223
Test: verify with FLAG_ACTIVITY_REORDER_TO_FRONT app
Change-Id: I65d4ffd1c17d6817c073122447e620a2fbb514a1
The clock complication comes with internal paddings that make the
spacing with the complications below too large, even without any layout
engine margin. Without a better solution, add a y translation to the
clock so reduce the spacing, and also change its text size to dp unit
so it doesn't respond to system text size change, which would mess up
the translation.
Test: https://screenshot.googleplex.com/BLfQEhA6i2t4qyu
Test: https://screenshot.googleplex.com/BbuvDvfmahtNy5U
Bug: 257553229
Change-Id: I7350981a28af590f6e70fb4fab004d5180cda502
This change adds a new attribute in the complication layout params to
allow constraint on width or height, depending on its direction.
Smartspace is added a constraint width so not to overflow.
Bug: 258455314
Fix: 258455314
Test: atest ComplicationEngineTest
Test: atest ComplicationLayoutParamsTest
Test: on device create a meeting with a long title and see that
smartspace does not overflow
Change-Id: Ie5a1278810ac77a8aa3f0046970642919c46f7ed
- update complication weights so home controls, media entry chip, and
smartspace are always shown below the clock
- instead of applying the bottom padding to home controls at the layout
engine level in order to center align with smartspace, apply to the
home controls chip view, which prevents the layout engine from giving
an exception to adding padding to a root node
Bug: 259264239
Bug: 259719867
Test: https://screenshot.googleplex.com/BZNatvxHFHxqxaS
Test: https://screenshot.googleplex.com/9gxsLUZWTFy7sGX
Change-Id: Icfcc3653ad7eb52e707c8289803188388484666e
The methods ShadeController was calling in CentralSurfaces are now
in ShadeController. A small amount of interaction between the two
classes had to remain, but it's now a small interface instead of a
direct dependency on CentralSurfaces. This work is far from done,
but the dependency was removed and atest passed, so it seemed like
a good place to stop and review.
Bug: 249277686
Test: manual and atest
Change-Id: Ide5c6f1964a83073f39323c083ea1ccc281bc8fe
Fixes the problem about launching a letterboxed app
from home having the "App isn't installed" message.
Fixes: 260188035
Test: Launch apps from Home and check they all start without the
"App isn't installed" message
Change-Id: I2cd2059933b33b13a0958ed410757373ca77611d
