Creates new setting on SFPS to require screen on before unlocking a
device. Also sets up toggles for this setting at the end of fingerprint
enrollment and on the fingerprint settings page, and adds test to verify
expected behavior.
Test: atest KeyguardUpdateMonitorTest#testStartsListeningForSfps_whenKeyguardIsVisible_ifRequireScreenOnToAuthEnabled
Fixes: 249169615
Fixes: 245343077
Fixes: 248530806
Change-Id: Ibc55dfa6667ec281add11a2665fceb073974ccb0
DevicePolicyResourcesManager.getString() was added in T and called in
many places inside system server. However, it uses
DeviceConfig.getBoolean to determine if a feature is enabled or not. In
the places where it is called from inside system server,
`clearCallingIdentity` was not always called, which can result in
DeviceConfig.getBoolean throwing SecurityException due to mismatched
AttributionSource (calling uid is the caller from the binder client,
while the context is "android" which should have calling uid 0). Context
is "android" because it is inside the system server where the
DevicePolicyManager instance is created. This bug might lead to
unexpected behavior such as packages failing to be uninstalled by admin.
The easiest fix is to place a bypass in SettingsProvider and manually clear
the calling uid there. This fix also allows for the cleanest backporting as
it can be cherry-picked into T without touching all the places where
DevicePolicyResourcesManager.getString() is called in the system server.
BUG: 252663068
Test: manual
Change-Id: I37a6ceb29575593018b93093562c85d49770a43c
ENABLED_INPUT_METHODS and DISABLED_SYSTEM_INPUT_METHODS reveals
a list of input methods apps, which violates the rules of package
visibility. This cl restrict the setting key to be readable for
apps targeting in T and below.
Bug: 253164661
Test: atest AccessibilitySoftKeyboardTest
Test: atest CarRotaryImeTest
Change-Id: I48aa7b05cd0dbde70fc6d53eee455959264a6867
New AppOp to be used for near-field file-based audio transfer
(ie. TV Remote Service) to allow audio recording
regardless of sensor privacy state, because it is considered
an intentional user interaction: hold-to-talk
And new Global Settings and SensorPrivacyManager APIs for the
opt-out toggle - as agreed with PWG.
Bug: 235618473
Test: manual
Change-Id: I95cdf8fa362b937609bdf834a82b05ec8375ac26
This reverts commit fb43f54289.
Reason for revert: Software Cursor not launching in Android U
Test: manual
Change-Id: I3f27b7d8958f455a580758192794308d5f91d152
1. Used Android Studio to auto generate the equals
and hashCode method.
2. e-order the field to match the database column order.
3. Better readability for toString().
Bug: 239607619
Test: atest SubscriptionDatabaseManagerTest
Change-Id: Ibc80d41f3019a4ebb012358f3369d69222925214
This reverts commit 36e81f298f.
Reason for revert: Software Cursor will not be launching in Android U
Test: manual
Change-Id: Ibf70015d294e03aa74d839c0caa64bf3542b341f
Add new column enabled_mobile_data_policies and copy the legacy data_enabled_override_rules to the new column. Future
read/write will only apply to the new column, and the legacy column will not be synced.
Bug: 244064524
Test: atest TelephonyManagerTest + TelephonyDatabaseHelperTest + TelephonyProviderTest + manual upgrade and observe user setting is preserved
Change-Id: I460c24909fb1eae689d02cedc76e24e87674a891
This is for feature gating a feature expansion to App Info -> App Details to include MBAs on top of existing Playstore Apps.
Change-Id: I7b3e296c310f19a01bc83b129b95021e92df3abb
Bug: 244215932
Previously we only auto enable factory system trust agents when the
devices is booted for the first time. This change added logic to detect
newly installed/enabled trust agents, and enable them if appropriate.
Fixes: b/243705470
Test: atest FrameworksMockingServicesTests:TrustManagerServiceTest
Change-Id: I3c345a44cfcfccc6f7e2507ba37e378b6b16bd98
In case seeing the unexpected fallback keyboard layout when focusing to
the window without an editor from the app has shown the IME.
Note that this behaviour change affects when the IME focus switching to
the next window with following configurations from an IME shown window:
1) SOFT_INPUT_STATE_UNCHANGED state without an editor
2) SOFT_INPUT_STATE_VISIBLE state without an editor
3) SOFT_INPUT_STATE_ALWAYS_VISIBLE state without an editor
Also, we guarded this platform behavior with DeviceConfig platform flag
in input method manager namespace.
Fix: 240701729
Bug: 243897178
Test: manual as issue steps
1) In Launcher, swiping up to enter all apps page.
2) Tap the search bar to show IME
3) Type "Keep" to show Keeps app's shortcut
4) Tap Keeps app's shortcut
5) Verify IME won't be shown on top of Keeps app's activity
(As the app set SOFT_INPUT_STATE_UNCHANGED without focusing an
editor by default)
Test: atest KeyboardVisbilityControltest#\
ImeInvisible_softInputAdjustNothingFromImeShownApp
Change-Id: I0c502bec5c5e21dabde08d610a9a1969c1229b08
The settings and systemUI use the LocalBluetoothLeBroadcast and
they use different sharedPreferences since the context is different.
It causes the data are not consistent.
Solution: Add data into ContentProvider, and listen the data changed
by the ContentObserver.
Bug: 243107842
Test: build pass. manual test in local.
atest SettingsBackupTest
atest SettingsValidatorsTest
Change-Id: I5f8367f3eb8e2dafa2986004dd8540de41409192
Merged-In: I5f8367f3eb8e2dafa2986004dd8540de41409192
The settings and systemUI use the LocalBluetoothLeBroadcast and
they use different sharedPreferences since the context is different.
It causes the data are not consistent.
Solution: Add data into ContentProvider, and listen the data changed
by the ContentObserver.
Bug: 243107842
Test: build pass. manual test in local.
atest SettingsBackupTest
atest SettingsValidatorsTest
Change-Id: I5f8367f3eb8e2dafa2986004dd8540de41409192
The e2e BiometricController need to access this field to enabled
Fingerprint Virtual HAL.
Test: atest sysui-biometrics-jank
Test: atest BiometricMicrobenchmark:BiometricPromptMicroBenchmark
Bug: 236074209
Change-Id: Iab85a16777b16ac4710521a6ba4bb32737157b2d
Settings.
The original implementation was designed to allow users to individually
enable/disable certain complications. However, we have since decided to
simplify the complication controls around a single master toggle. This
fixes an issue where when new complications are added, we will no longer
switch the toggle to off in Settings.
Bug: 241469874
Test: atest ComplicationTypesUpdaterTest
Test: atest DreamBackendTest
Test: manually on device
Change-Id: I1bbfbbe2abd6398b74bcd0b9ba601583a1403bef
Add a new setting that controls whether media on lock screen is enabled,
disregarding the notifications status. The new setting is available
under media and privacy settings.
Bug: 229915240
Test: atest MediaHierarchyManagerTest
Test: atest KeyguardMediaControllerTest
Change-Id: I6adaa00ead1660488e4114d303c4394751ff87e8
