The header was keeping a map of roaming states which could have
stray old subids in it when it shouldn't. It just needs to be
cleared when the sims change.
Test: runtest systemui
Change-Id: I62c5acab5739b9c4acf69a8c7e00b2f75de903dc
Experimentally, it makes more sense to more people to have the parent
setting as an overlay not a concrete thing.
Test: make cts -j30 && cts-tradefed run cts --module CtsDevicePolicyManagerTestCases --test 'com.android.cts.devicepolicy.ManagedProfileTest#testRingtoneSyncAutoDisableRingtone' </dev/null 2>&1
Bug: 34730524
Change-Id: I5f804713def9e54921b90e4f5cea742ba8aaa685
This CL is a follow up CL to my previous CL [1] that aimed to reduce
false positives in InputMethodManagerService.MyPackageMonitor when
deciding if InputMethodManagerService (IMMS) needs to rebuild the list
of enabled IMEs or not.
Currently IMMS.MyPackageMonitor#onSomePackagesChanged() gets called
back to trigger IMMS#buildInputMethodListLocked() when either the
following rule A or B is fulfiled.
A. Intent with one of the following actions for any package name:
- ACTION_PACKAGE_ADDED
- ACTION_PACKAGE_REMOVED
- ACTION_EXTERNAL_APPLICATIONS_AVAILABLE
- ACTION_EXTERNAL_APPLICATIONS_UNAVAILABLE
- ACTION_PACKAGES_SUSPENDED
- ACTION_PACKAGES_UNSUSPENDED
B. ACTION_PACKAGE_CHANGED with a package that is included in the
known IME package list, which can be obtained from PackageManager.
The previous CL [1] addressed Bug 28181208 by introducing the rule B,
but we can actually apply the same optimization for A, except for one
false negative case where an appearing package that is not in the
known IME package list actually contains one or more
InputMethodService.
In short, we can reduce false positives by replacing the above two
rules with the following two rules.
A. Intent with one of the following actions for any package name that
is in the known IME package list:
- ACTION_PACKAGE_ADDED
- ACTION_PACKAGE_CHANGED
- ACTION_PACKAGE_REMOVED
- ACTION_EXTERNAL_APPLICATIONS_AVAILABLE
- ACTION_EXTERNAL_APPLICATIONS_UNAVAILABLE
- ACTION_PACKAGES_SUSPENDED
- ACTION_PACKAGES_UNSUSPENDED
B. Intent with one of the following actions for any package that
implements at least one InputMethodServivce.
- ACTION_PACKAGE_ADDED
- ACTION_EXTERNAL_APPLICATIONS_AVAILABLE
Basically in the rule A PackageManager gives us the list of relevant
package names that might contain IMEs regardless enabled/disabled
state, and such a list works well to filter out irrelevant
notifications except for one case where a new package is adding one
or new IMEs that we did not know. This is why we also need the rule B.
Even though the rule B requires a secondary query to PackageManager,
it can be done outside of the state lock of IMMS.
[1]: I7b69c349318ce06a48d03a4468cf2c45bfb73dc2
c4e4491735
Test: Manually verified as follows.
1. tapas ShortcutDemo && make -j
2. Copy ShortcutDemo.apk to the current directory.
3. adb shell dumpsys input_method | grep mMethodMapUpdateCount=
to check the "mMethodMapUpdateCount".
4. adb install -r ShortcutDemo.apk
5. adb shell dumpsys input_method | grep mMethodMapUpdateCount=
to make sure "mMethodMapUpdateCount" remains unchanged.
6. adb install -r ShortcutDemo.apk
7. adb shell dumpsys input_method | grep mMethodMapUpdateCount=
to make sure "mMethodMapUpdateCount" remains unchanged.
8. adb uninstall com.example.android.pm.shortcutdemo
9. adb shell dumpsys input_method | grep mMethodMapUpdateCount=
to make sure "mMethodMapUpdateCount" remains unchanged.
Test: Manually verified as follows.
1. tapas SoftKeyboard && make -j
2. Copy SoftKeyboard.apk to the current directory.
3. adb root
4. adb install -r SoftKeyboard.apk
5. adb shell dumpsys input_method
Make sure that
com.example.android.softkeyboard/.SoftKeyboard
is recognized by IMMS.
6. adb shell pm disable com.example.android.softkeyboard/.SoftKeyboard
7. adb shell dumpsys input_method
Make sure that
com.example.android.softkeyboard/.SoftKeyboard
is no longer recognized by IMMS.
8. adb shell pm enable com.example.android.softkeyboard/.SoftKeyboard
9. adb shell dumpsys input_method
Make sure that
com.example.android.softkeyboard/.SoftKeyboard
is recognized by IMMS again.
Fixes: 35361128
Change-Id: I063688297156188f68fe0b55a46d72f2e811dc88
Change-Id: Idfd094f3c9ea59356440d6851ccd5abda36ca6ba
Fixes: 35640585
Test: manual; after boot, opened the power menu to force
system_server to spin up a ThreadedRenderer instance
(and thus register itself as a callback on GraphicsStatsService).
Then manually set the date forward by a day to trigger onAlarm
and verified the system didn't reboot/crash. A systrace capture
verified that the alarm fired and package:android (system_server)
had a log rotation event.
Set AM/PM mode before setting hour in TextInputTimePickerView. This is
needed so we know exactly which it is when we are using 12 hour clock.
Not setting it early was causing TextInputTimePickerView to update TimePicker
with the hour that was not offset correctly based on AM/PM state.
Test: existing tests caught this - TimePickerTest#testKeyboardInputModeClockAmPm
verified locally that this test now passes.
Bug: 35262830
Change-Id: I7e912320cb5a72c5d9d4e80dc0b42deb651f2636
Spinner is a special kind of list-value field because its auto-fillable
values are not currently present in the assist structure: this change
adds a getAutoFillOptions() to fill that void, and implements the
auto-fill APIs on Spinner.
It also fixes RadioGroup.getAutoFillValue() - it should return the index
of the child, not its resource id.
Bug: 33550221
Test: CtsAutoFillServiceTestCases (with new tests) pass
Change-Id: I625e7dd705fade56fda490fcd3c4446c0c245ee1
It was never a public API, and we now have a support and CTS tested
public API over at StorageStatsManager that apps should be using.
Test: builds, boots
Bug: 34643504
Change-Id: Iad3f2c000dd9d7c1b1e70d0bf2d281826737322e
