Introduce stylus handwriting settings and check if its enabled before
calling IMM#startStylusHandwriting()
Bug: 219777744
Test: atest StylusHandwritingTest
Change-Id: Id58b2eb66a0a1178743d08921918f3d9d717546c
- Add a listener for the new setting Settings.Secure.STATUS_BAR_SHOW_VIBRATE_ICON
- Rebuild any IconManager that receives an updated blocklist
- Assert that any blocklist changes come in on the main thread
Test: atest CollapsedStatusBarFragmentTest
Bug: 220144337
Change-Id: I667b5c57ef646c57a2f6912df7d233b1b5c0f89d
Merged-In: I667b5c57ef646c57a2f6912df7d233b1b5c0f89d
- Add a listener for the new setting Settings.Secure.STATUS_BAR_SHOW_VIBRATE_ICON
- Rebuild any IconManager that receives an updated blocklist
- Assert that any blocklist changes come in on the main thread
Test: atest CollapsedStatusBarFragmentTest
Bug: 220144337
Change-Id: I667b5c57ef646c57a2f6912df7d233b1b5c0f89d
Use device config to control whether autofill dialog feature is enabled.
To support this, the autofill namespace of DeviceConfig needs to be exposed
for AutofillManager to read in the app thread.
There are augmented_autofill_mode, smart_suggestion_supported_modes and
compat_mode_allowed_packages existed in autofill space. These can be made
app readable.
Bug: 210926084
Test: atest android.autofillservice.cts.dialog.LoginActivityTest
Change-Id: Idfb846656a0c26eba1db4f8ef6ec427ae4ca666d
This is more correct. Android devices, even under ideal conditions,
don't track UTC (which contains leap seconds and uses the SI definition
of a second) but use a clock based on Unix epoch time (no leap seconds,
but clocks may skip/stop or smear around leap seconds to ensure a fixed
number of second increments per calendar day when leap seconds are
applied to UTC).
Bug: 218802673
Test: Compile only
Change-Id: I0c557e2231f87ea1b99e3935f79af15bccf91da4
Introduce a LAUNCHER_TASKBAR_EDUCATION_SHOWING setting for taskbar to
indicate that the education is about to be shown or is currently
showing.
After the taskbar education is dismissed, the letterbox education will
only be shown for a different task or for the same task once its compat
state changes and the letterbox education is eligible to be shown.
Bug: 214590804
Test: N/A
Change-Id: Ia8512e5f188fe421adf1de2fc8a0422b9cc79c76
This new timeout will only apply when the device is docked, while still honoring any maximum timeouts set by DevicePolicyManager or WM.
Test: atest PowerManagerServiceTest
Test: locally on device, modifying the setting manually via adb
Bug: 213908097
Change-Id: I3d992154723fa8871f7c1c24607b16a35c42fb87
BufferStateLayer is the now the default interface to SurfaceFlinger
and BufferQueueLayer code path is obsolete and non-functional.
Test: presubmit
Bug: 217973491
Change-Id: I0d083230f3a27d4b0380a1d958fdc5c1b6c3aa51
This reverts commit c51683b7e7.
Reason for revert: API should not be expose, errorprone is being updated
Change-Id: I633ac76aa03982aa9cb03b1cc9f3d92ced94db4d
configurable.
The content of the half watchdog is now more consistent with watchdogs
to make it more actionable (watchdog subject, memory psi, cpu data).
The half watchdog is also published to dropbox in a similar way to the
watchdog. We also use a thread to publish to dropbox to make sure that
we do not block the watchdog handler code.
For the half watchdog, we know wait for 5s to get the cpu data (similar to
the watchdog) which delays the next run. That's only 10% of the default
timeout though so that's not a big difference.
For the configurable watchdog timeout, we delay fetching the value to
be able to start the watchdog as early as possible when system server
starts to detect blocked threads that might happen early. As well, even
if fetching settings is broken, the watchdog will still be running with
the default timeout values.
Test: tested that the half watchdog is added to dropbox
~/master$ adb shell dumpsys dropbox | grep watchdog
2022-01-25 23:22:19 system_server_pre_watchdog (compressed text, 21612 bytes)
2022-01-25 23:22:56 system_server_watchdog (compressed text, 21386 bytes)
2022-01-25 23:29:09 system_server_pre_watchdog (compressed text, 21621 bytes)
The watchdogs and half wathdogs were generated by adding a message with
a long sleep on the ui thread
Runnable runnable = new Runnable() {
@Override
public void run() {
SystemClock.sleep(40_000); // 40s
}
};
Message msg = Message.obtain(UiThread.getHandler(), runnable);
msg.setAsynchronous(true);
UiThread.getHandler().sendMessage(msg);
Bug: 209932320
Change-Id: I1bca723d1d7bee98dc7e1aade73a2e4384d6f035
Bluetooth is going mainline and can no longer use hidden api. We tried
to use the public alternative as our user is the same returned by
contentResolver.getUserId() but errorprone is not happy with it
Bug: 216769091
Test: Build bluetooth as apex mainline module
Change-Id: I195d545cc359d765e261c169032dfad46c916d75
CTS-Coverage-Bug: 217352944
This is a follow up of ag/16406749
Bug: 195782998
Test: unit tests, manual test on device
Change-Id: Icb977d9a7591ffe48ae44bbe2ad521945b7b0139
Merged-In: Icb977d9a7591ffe48ae44bbe2ad521945b7b0139
(cherry picked from commit 5ab8466005)
