WM team starts to remove functionalities that were made for unmanaged
tasks so take this step 1 to avoid regressions from this type of
changes.
Also remove UNSUPPORTED_WINDOWING_MODES because ShellTaskOrganizer can
handle all windowing modes now.
Bug: 192310211
Bug: 165794880
Bug: 165794636
Test: Maximize, drag and resize freeform windows.
Change-Id: If130b449fe6cf37c39f0e1424e4f23cdb2d33dd5
When the devices goes into doze mode to display AOD contents, the screen
turns off before displaying AOD contents on some devices (i.e.
config_displayBlanksAfterDoze=true).
On such devices, SysUI calls IActivityTaskManager#setLockScreenShown
first before start dozing, otherwise ATMS/WM wakes up the activities
when dozing starts.
Bug: 193479273
Test: manual
1. adb root && adb shell setprop debug.force_blanking 1 && adb reboot
2. atest KeyguardTests
Change-Id: I64cecd8e866f1debdcd7429ca4987cd70eceb45c
This reverts commit 7d9eb2b6f9.
Reason for revert: Regression happens in "com.instagram.android" that IME will cover the comment fields
Bug: 195385541
Bug: 192337037
Bug: 194746204
Change-Id: Id33459ab4f53f8bec2027759302dafc1a4f02fae
(cherry picked from commit 9eca14b72b)
A prior change to the permissions flow for Trusted Hotword
(I80dabaf6ae0e781028dde16ead3321fbff319542) made the system enforce
the required permissions on the APIs the conventional way - by throwing
a SecurityException. But the existing behavior was to silence these
exceptions and instead return error results. This change brings back
the old behavior which exists in the SoundTrigger layer.
Also removes permissions checks for a couple of APIs to again be
consistent with the old behavior (and the current behavior in the
SoundTrigger layer).
Fix: 193116894
Test: manual - remove permission and reboot / remove permission after
boot, stop/start reco
Test: atest HotwordDetectionServiceBasicTest
Change-Id: I56391260fd4375a04233eb3261bacec8696bda99
Root cause:
1. Design change "tap app to exit" -> always being true, and settings
remove this option.
2. Tuning performance, due to 1, no longer listens to the key change,
so we remove the listener.
Solution:
Change getSettingsTapsAppToExit() API to return default TRUE.
Bug: 195629000
Test: Build ROM and factory-reset to test
Test: atest WMShellUnitTests
Change-Id: Id3c265258ed28f7e0aa54505c339671885d28fa7
This is split into two high-level issues which together cause
strange auth behavior on keyguard:
============= Issue 1 =============
For fingerprint, auth ends when:
1) Success
2) Error
For face, auth ends when:
1) Success
2) Reject
3) Error
This change ensures that cancellation signal is set to null upon
any of these conditions, so that there is never an opportunity of
using a stale CancellationSignal.
Furthermore, do not invoke stale cancellation signal when
starting authentication. In the off chance the bug is re-introduced,
or if some other situation can cause a cancellation signal to be
non-null when keyguard requests auth again (e.g. bad state management
in keyguard), do NOT invoke the stale cancellation signal's cancel
method. The framework already handles this case gracefully and will
automatically cancel the previous operation.
============= Issue 2 =============
We have a runnable that's scheduled to run after X ms if
ERROR_CANCELED is not received after cancel() is requested. However,
there are various bugs around that logic:
1) shared runnable for both fp and face, leading to unexpected
and incorrect state changes (e.g. face does not respond to cancel
within X ms, both fp and face will go to STATE_STOPPED, even though
cancel() was never requested of fp
2) Always remove and re-add runnable when requesting cancel() though
it should never occur that cancel() is requested in close temporal
proximity, it never hurts to have the correct timeout before
resetting the state.
Bug: 195365422
Bug: 193477749
Test: manual
Change-Id: I3702f41c8af7e870798f19c43012a26281a6632a
Bug: 195411307
Test: atest CtsSharesheetTestCases:android.sharesheet.cts.CtsSharesheetDeviceTest
Test: manually test on the device
Change-Id: If7d3f7acadcbed3340616b0ab239c776dedf7af7
(cherry picked from commit 13b9f947e0)
By default, use 48px. This value can be
overridden by overlays.
Update stroke width of lock and udfps icons from 2.5 => 2
Update stroke width of aod udfps icon from 1 => 1.3
Test: manual
Change-Id: I7c3883c9acac68acc02684a3115e9e6512fe9a1f
Bug: 195564809
Allows code to subscribe to changes in specific flag values.
Bug: 194781951
Test: atest SystemUITests
Change-Id: Icae5c80cb32f0dd425e53297aa28e555f34a07a5
