am: 60cc2ab6e7 -s ours
am skip reason: change_id I1b26dc64eaab2151e6885fd01cc5e8d4e18c4e60 with SHA1 da48f0f6d3 is in history
Change-Id: I23657309145be45306d2df70dcc517e4c36a82a1
am: 55a06bb5d1 -s ours
am skip reason: change_id I5eb72772a0a35897611dd6db95c68a2d2e971e9a with SHA1 a31ed1bbdd is in history
Change-Id: I1bf9f453e7a9d254d09286d054948ef4fbe3557c
ConnectivityManager and its usages are removed from
NetworkStatsService. After that, forceUpdateIfaces requires
information that only ConnectivityService has, hence
restricting the calling permission to NETWORK_STACK or
MAINLINE_NETWORK_STACK permission. The required permission
will be changed from READ_NETWORK_USAGE_HISTORY to
NETWORK_STACK or MAINLINE_NETWORK_STACK. This change would make
it impossible to call outside the system.
Bug: 126830974
Test: atest FrameworksNetTests
Merged-In: I1b26dc64eaab2151e6885fd01cc5e8d4e18c4e60
Change-Id: I4ea421e4126a45f65d25fe0bec74243a3b20aeab
(cherry picked from commit 6b895dea25)
This is a preparation to introduce CTS for per-profile IME.
Currently
adb shell ime enable <ime id>
and
adb shell ime disable <ime id>
can throw IllegalArgumentException when <ime id> is not recognized by
the system. This makes some sense, but if we start supporting
'-u all' option it'd make more sense if it just shows an error message
rather than letting the command crash with throing an exception.
This behavior change also removes a limitation that developers cannot
use
adb shell ime disable <ime id>
command to remove an IME ID from Settings.Secure.ENABLED_INPUT_METHODS
if that IME is not currently installed.
Bug: 120784635
Test: Manually verified as follows.
1. Build aosp_blueline-userdebug and flash it
2. adb shell ime enable com.example.android.softkeyboard/.SoftKeyboard
-> "Unknown input method <IME ID here> cannot be enabled"
3. adb shell ime disable com.example.android.softkeyboard/.SoftKeyboard
-> "Input method <IME ID here>: already disabled"
Change-Id: Ib9be7700557f2f606c90d62f79ec3afca2f82c40
Keep the current auth session until ConfirmDeviceCredential succeeds
or fails. ConfirmDeviceCredential's BP and LSKF screens can be canceled
now.
Bug: 123378871
Bug: 128747871
Test: With modified BiometricPromptDemo, ConfirmDeviceCredential's
BiometricPrompt and LSKF screens can be canceled
Change-Id: Icaf3f0c55b07fd138a2ee9d214941ea83408f0ee
am: 3b4698c39c -s ours
am skip reason: change_id I8e1fb5b47fff3bf624131ba1f5732daabd991e6d with SHA1 0b98441205 is in history
Change-Id: I66537498ead2d600efa38c5e7207f13d07943d8d
am: c2615ed218 -s ours
am skip reason: change_id I3599377406b88751ee11139e9a1aa5afab734f7c with SHA1 5f78486ac1 is in history
Change-Id: Ib1f2ed83860c90bac56fed91f1277556f3146678
am: 2a5098f888 -s ours
am skip reason: change_id I3599377406b88751ee11139e9a1aa5afab734f7c with SHA1 5f78486ac1 is in history
Change-Id: Ie2b30f7677476eb5b03d065b5535044da2157288
