When setAllowedProvider is specified, currently we are filtering out all
the system providers. With this change, we will always ping the system providers
+ the providers specified in the allow list.
Bug: 277773297
Test: built locally & deployed on devive
Change-Id: I8a82f68edbd75b9a879d7e32aa32413af3a35cd9
When an OnBackInvokedCallback is unregistered from a WindowOnBackInvokedDispatcher, it is important to check if the callback is the current top one and if the back animation is in progress. If it is, we should call onBackCancelled() on the callback as a final step.
Test: atest WindowOnBackInvokedDispatcherTest
Bug: 276816667
Change-Id: Icaf98899c474c4e8d89d4a9c77acc309d37e9582
1. add new route type and icons
2. update the way to get Media information to consist with UMO
Bug: 279641026
Bug: 278728942
Test: atest MediaOutputAdapterTest MediaOutputControllerTest MediaOutputBaseDialogTest MediaOutputDialogTest
Change-Id: I42f1bbc433d7471f54417332102ed7be345df5be
SASS device should also work in U, this change fixs color update for
SASS device layout, consistently use setBackgroundTintList.
Bug: 281521758
Test: atest MediaOutputAdapterTest
Change-Id: Ie9fe55b829d6326ac22322b6c4a1b38b15726119
FLAG_IGNORE_EPHEMERAL shared its value with FLAG_ACTIVITY_REQUIRE_DEFAULT
which was problematic since these flags were used or checked together
in a few cases. A short term solution was to replace the value of
FLAG_IGNORE_EPHEMERAL with another flag value - FLAG_RECEIVER_OFFLOAD -
which isnot used with the former flag.
This will be revisited in the future, with a concrete solution, since
there are no 32bit flags left in Intent.java.
Bug: b/269674648
Test: None
Change-Id: I9e3d282bb12a630d0a170871fe8e2da5d259ad57
This CL adds owners into the tests.
Bug: 281709596
Test: atest InsetsSourceTest#testGetIndex,testGetType
Change-Id: I1ededa130ecc6e579403ac4ddd53585369848fa8
Fix support of AudioManager.FLAG_ALLOW_RINGER_MODES which enables
the change of ringer mode in response to the unmuting of a stream
currently muted by the ringer mode.
When this flag is not present, the unmuting of a muted stream
is not allowed, and that call shouldn't change the ringer mode.
This prevents entering situations where NOTIFICATION is unmuted
but the ringer mode is VIBRATE or SILENT.
Bug: 278661956
Test: atest CtsMediaAudioTestCases:android.media.audio.cts.AudioManagerTest#testAdjustUnmuteNotificationInSilent
Test: atest CtsMediaAudioTestCases:android.media.audio.cts.AudioManagerTest#testAdjustUnmuteNotificationInVibrate
Change-Id: Ib1306be48ba61a0294e12e3bf7ac74fb54a0bd6c
Fixing the truncation in the text that exceeds the boundary of textview
with settings ellipsize=marquee and allow horizontally scrolling.
Bug: 280162065
Test: manually - attach videos in the bug
Change-Id: I7965ced2dfdccfa83c2add8fa7f81ba12e8fc720
Since Android R, background-started FGS can't access the mic/camera
even if the user has granted "while-in-use" permission, so does for
the foreground location permission. Now, if the app tries to start
a FGS from the background with the type mic/camera/location,
the start would be denied, since they can't access those sensors
from that FGS anyway, it makes no sense to start such a FGS.
If the app has the background location permission and tries to
start FGS from the background, this is still allowed.
Bug: 280936347
Test: atest CtsAppFgsTestCases
Change-Id: I56865b4f9e9c317c968a6cbfced5b3b4cdccda79
Since keyguard animations sync transactions to view rendering,
it's possible for them to apply changes after the finishtransaction,
so wrap containers in leashes so that we can just detach them.
Also, remove the single-task-opening restriction now that keyguard
animations support multiple tasks.
Bug: 278886491
Test: app in pip, turn screen off, turn screen on+unlock.
Change-Id: Iea2fc2d5ae16c59e7983b87fea2cd62d327f4ac9
This fixes any final issues in the metric collection and emission
system, including logs. The fixes primarily focus on ensuring the
timestamps are properly recorded, the aggregations are done properly for
the total canddiate, and that all types and values are recorded or
collected as they should be and emitted when they should be.
Statuses and TODOs are also fixed here, alongside any final logs.
Bug: 271135048
Bug: 270568738
Test: Build, won't submit without E2E Test (No Affect + Validate Metric Emits)
Change-Id: I3637bf4a84596ba72bdab9ef225e4e5c77ab0bb6
* changes:
Cleanup mRearDisplayPresentationController if SecurityException caught
Add foreground check for controlling or requesting device state
Do not show Keyguard Presentation when occluded
Check the underlying monitor value is not null before proxying the call
in the onEvent() method.
Bug: 282075312
Test: atest BackupManagerMonitorWrapperTest
Change-Id: Iece25d81bc9ec765244898589222491c16ca629a
This reverts commit 62f291ffd8.
Reason for revert: ComponentInfo can be retrieved using BiometricManager API with proper permissions and the info doesn't need to be exposed in dumpsys.
Bug: 281914035
Change-Id: If3575c5b9a66f65593ff377834d660561886b079
In Autoconfirmation, if we lockout, we want to have the backspace key
have the same behavior as the enter key. We also want to remove pin
hinting.
Fixes: 281661030
Test: autoconfirmation, long press backspace key
Test: autoconfirmation lockout and regular authenticate
Change-Id: Ia1128b9d2f98b1758b23e3a75909900810fd051a
There were a couple of issues with the accessibility of the wrong pin
scenario.
1. the user activity signal from the password view is trying to set the
error message to an empty string. Move setting the error message to
after resetting the password view.
2. No text is set yet while we are animating the view and this prevents
the text from being announced. I remedied this by relying on a
textwatcher to keep track of the textview.
3. The password view is constantly being selected, which shouldn't
really be the case. This is because we set the input to be disabled
as we check the password and re-enable it. While in this process, we
requestfocus if focus is not on the password view.
4. For some reason we set the textview to "wrong pin" and then
immediately an empty string. There is a 250ms delay to make the
accessibility announcement. After 250ms, we want to ensure that the
text is still displayed in the textview.
Consequently, once a wrong pin in inputted, the only talkback text is now
"Wrong Pin"
Fixes: 281635711
Fixes: 281787557
Test: wrong pin scenario in bouncer.
Test: password, simpin, and sim puk views.
Change-Id: I018e067e0a3b17fbd7921f40924ced401707297c
