* changes:
[Media TTT] Remove the tap-to-dismiss option for the phone chip.
[Media TTT] Increase the default timeout to 10s, and the timeout for the "transfer started but not finished" state to 30s.
[Media TTT] Don't wake the screen if the screen is already in dream state.
This is a guide for developers for how to add new quick affordance
buttons to the lockscreen.
Bug: 235403546
Test: N/A
Change-Id: Id8417c48732e25331027f11442c16d0220e690c4
The implementation of shared-element transitions takes the
ActivityOptions from the calling activity and sends them to
another activity. This means that any sensitive information
passed into ActivityManager via ActivityOptions can make its
way to an unrelated app. Recently a RemoteTransition object
was added which includes some sensitive information.
This CL strips the sensitive information from the activity
options after it is extracted so that it can't be sent
to the target.
Bug: 237290578
Test: atest ActivityManagerTest#testActivityManager_stripTransitionFromActivityOptions
Change-Id: Ic9f8062e67ab895292af75e97a9ce2f4aa45d467
Aspect ratio changes could be deferred, and thus only the aspect ratio
itself needs to be updated, but the bounds itself is already correct.
Bug: 234615306
Bug: 241096069
Test: Enter PiP and move it around right after animation finishes
Change-Id: Ia1078a6492358e694d4eadf97fa0f242a4033c6f
- We were previously initializing components manually because some startup
is order-dependent, which led to an increasing number of dependencies
from ShellTaskOrganizer on things that it really doesn't need to know
about. The initialization order actually matches the dependency order
pretty closely, so instead we can have these components add callbacks
in the order they are created and initalize in sequence.
- Also move some logic out of constructors to the init callback
- The other subtle issue is that the provider for ShellInitImpl was
implicitly also ensuring that certain shell components were created at
startup (since they aren't otherwise referenced by any SysUI component
directly or indirectly). Instead, separate that out into another
more explicit provider, with the @ShellCreateTrigger annotation, and
allow subclasses to provide a @ShellCreateTriggerOverride annotated
provider for product-specific initialization
Test: atest WMShellUnitTests
Test: atest SystemUITests
Bug: 238217847
Change-Id: I4a2583ceeaf469130ac07fc8c4e267c28843b7b8
Signed-off-by: Winson Chung <winsonc@google.com>
This flag is used by the SysUI to dismiss an insecure keyguard
when an app is launched from an insecure lock screen. The flag
should only affect the app launch once, so needs to be cleared
once the flag is processed.
Bug: 234583880
Test: atest KeyguardTests#testDismissKeyguard_fromActivityOption_onlyOnce
Change-Id: Ia4179b40de7d45b2199b175a6dcc24016dfba091
(cherry picked from commit 41cbf49af7)
and have the processor connect to it.
Test: Compiles
Test: ConnectivityInfoProcessorTest
Bug: 238425913
Change-Id: I1a363caaddd8e731be617a0030e81c2411dec0b8
Title says it all.
Bug: 235403546
Test: Made sure that the feature is enabled while the teamfood flag is
enabled and the feature flag itself is disabled using the flag flipping
app
Change-Id: I1bef5c65fc17bff7c80c8997d823d048cb8c4f19
This flag is used by the SysUI to dismiss an insecure keyguard
when an app is launched from an insecure lock screen. The flag
should only affect the app launch once, so needs to be cleared
once app launch animation finishes.
Bug: 234583880
Test: atest KeyguardTests
Change-Id: I74e9e00caad0d9af80127b2fc930c4ff0d52af76
CollapsedStatusBarFragment uses disable flags to show and hide the
system info in two cases: when showing the keyguard and when showing
quick settings. This animation causes the alpha to animate to zero AND
the visibility to be View.INVISIBLE.
This means that the system event animation only has the context to set
the alpha of the system status area -- _not_ the visibility.
In the case where the disable flags change while a system status event
animation is in progress, CollapsedStatusBarFragment would bail on the
_entire_ animation, including the change from View.INVISIBLE to
View.VISIBLE, which is crucial for unhiding the view eventually.
This change simply allows CollapsedStatusBarFragment to set the system
info area back to View.VISIBLE even if it doens't control the overall
animation.
Test: atest CollapsedStatusBarFragmentTest
Fixes: 238968127
Fixes: 239508705
Change-Id: I7ad8c4a4df8ff335ea9b3de428521b24e59002ee
Merged-In: I7ad8c4a4df8ff335ea9b3de428521b24e59002ee
The code was moved to another package but the tests weren't.
Bug: 235403546
Test: N/A - just a file move of test files.
Change-Id: I74e2f5b792d58cf02510ab62ab1bafa084e972b9
In the new implementation of the KeyguardBottomAreaView, when the user
locks their device, moving directly from the unlocked state into
AOD/doze, we erroneously show the home controls quick affordance button
for a moment/frame before hiding it.
This was caused by our reliance on isDozing and dozeAmount where, what
we should really look at is isDozing and isKeyguardShowing - like the CL
is doing.
The approach taken here is actually refactored out of the wallet quick
affordance config implementation and applied generically to all quick
affordance config implementation at the use-case layer. The reason I
thought this could work is because I was only seeing the home controls
button exhibit this bug while the wallet one was not. I didn't test the
QR Code scanner one, but I bet it would have worked just like the home
controls one.
Bug: 240969525
Fix: 240969525
Test: locking from the unlocked home-screen proves that the fix works
because it no longer flickers the quick affordance view over the AOD
screen. Also, unit tests were added/modified to capture this.
Change-Id: Id2917989991802825d1024d5a0d9161d4452265f
Fix SpatializerHelper.setSpatializerEnabledInt() to
avoid overriding the enable state computed by onRoutingUpdated()
when spatial audio is enabled.
Bug: 238378679
Test: repro steps in the bug
Change-Id: I2e77945c889c1db093832f780c632a626e979e7c
Merging 8ce3c53fcf into qt-qpr1-dev resulted in a merge conflict due to a method being moved between qt-qpr1-dev and rvc-dev, such that the patch backported from rvc-dev didn't match at all. Removing the old method makes this branch match qt-dev and rvc-dev.
Test: will use abtd to validate the build and the resulting logic.
Original changes: Id82d20c9f1f2001400871b5381f52b40fbdf81c5
Original
Bug: 231322873
Breakage
Bug: 241087006
Change-Id: Ic4f8d701d97aa9b6c72875df8c7eab5fd51934e0
