am: b03099d9dd -s ours
am skip reason: change_id I389617491f640afd9ca28ec3f247912365e6cc53 with SHA1 1965bb1cc2 is in history
Change-Id: I17a02da5df726f4844efd2650696d2c6bc9e4687
1. Use suggestConversationActions for both replies and actions
2. Make existing flags configurable via DeviceConfig
Test: atest SmartActionHelperTest.java
Test: atest AssistantSettingsTest.java
BUG: 123745079
Change-Id: I9b84edf9818d5839202c337ac3c3d48378adbf55
1. Pull out the common intent genereation logic to TemplateIntentFactory,
so that it could be used by actions.
2. Fix a bug that we are freeing the annotator immediately when
we are switching annotator model file. It is incorrect as
it could be used by another thread / model.
Test: atest frameworks/base/core/tests/coretests/src/android/view/textclassifier/
BUG: 123745079
Change-Id: I6c5364595470b900be2dd976dda6e9fc90464de9
am: a98a76e53a -s ours
am skip reason: change_id I61cf05a8095f9d121fafb862def8239b325a7f43 with SHA1 c7b16ca0ab is in history
Change-Id: I698f97f7ed9a1b468c38ca52f76135c06b355967
Also migrating UiModeManagerService to register a LowPowerModeListener
so it uses the more standard interface for Battery Saver.
Bug: 119261320
Bug: 122968431
Test: atest com.android.server.power.batterysaver.BatterySaverPolicyTest
Change-Id: I669737d5985d0b2835740a53695526a2119cdf49
am: 98afe69ae9 -s ours
am skip reason: change_id Ia9917d12987e91e87e34ffb3f126e7bc7c9c187e with SHA1 e413528700 is in history
Change-Id: I6aea18280ee55740725a73d969a6485b69cb0521
It turns out that AppRestrictionsHelper#addSystemImes() has always
queried for the owner user's system IMEs despite the fact that it's
trying to query system IMEs for a restricted profile user. This
behavior has not changed since its beginning [1].
Most likely people would not have noticed this though, because:
* Settings app does not show a menu item to create a restricted user
on phone devices.
* Even if it's available, most people do not use restricted users.
* Even if someone created a restrected user, most likely the owner
user and the restrected user share the same set of system IMEs,
which are defined as "pre-installed" IMEs.
Anyway, AppRestrictionsHelper#addSystemImes() will start using a newly
introduced @hide API IMM#getEnabledInputMethodListAsUser() so that it
can query for the right user's system IMEs, instead of querying owner
user's ones.
[1]: Ifced841ad3bfbde33d2403356216dd1749b7fa9a
a7a93784d1f9798d37cb618def1a558f8d626f0f
Bug: 122164939
Test: atest SettingsLibTests:AppRestrictionsHelperTest
Test: manually done as follows.
1. Build aosp_taimen-userdebug and flash it.
2. adb shell pm create-user --restricted test_profile
3. adb shell am start -a android.settings.USER_SETTINGS
4. Click the gear icon next to the "test_profile" user.
5. By adding a log, make sure that IMMS#getInputMethodList()
gets called with userId = 10.
Change-Id: I5b50b5fe143c74c87b331bda3e5bcc4d6248436e
