Remove the now unused config value.

Bug: 62437848
Test: Manual tests
Change-Id: I24b2b9e57cec5052037a86dbd53fad7afed6f9d8

Test: runtest frameworks-net
Bug: 63250751
Change-Id: I63aa115e534123c46bd515bc099a601da45c5725

Fixes corner case when the same component name first shows up as a
non VR activity, then again as VR.

Bug: 63709047
Test: Device launched to VR Home
Change-Id: I6f590185635cde06b0fba9f0e05ff6d6d586cfbb

1. interrupt the sleeping testing thread onDestory to avoid
any thread keep running after onDestory.
2. add check of isFinishing() or isDestoryed() when the
testing thread wakeup.
3. detory the webview onDestory since there're chances that
some callbacks in WebChromeClient will try to open dialogs
while the container activity has been destroyed.

Bug: 63819703
Test: Manual test
Change-Id: Ida62d9d8e97e8c9f905ce2feab4ea265575baee8

Fixes: 63992836

Test: adb shell settings delete secure system_navigation_keys_enabled
&& make -j RunSettingsRoboTests

Change-Id: I6632c7244749b3b98227cb4392438ab861f3f815

Test: tests still pass
Bug: 62022517
Change-Id: Ifc01797c6ada51130586b5b42570c3357923ef85

Keystore stores key blobs in with filenames that include the symbolic
name and the uid of the owner. This behaviour should have been
completely opaque to the user keystore. However, the granting mechanism,
by which an app can allow another app to use one of its keys, leaked the
internal structure in that the grantee had to specify the key name with
the granter's uid prefix in order to use the granted key. This in turn
collided with prefix handling in other parts of the framework.

This patch refurbishes the granting mechanism such that keystore can
choose a name for the grant. It uses the original symbolic key name as
prefix and appends _KEYSTOREGRANT_<grant_no> where the grant_no is
chosen as first free slot starting from 0. Each uid has its own grant_no
space.

This changes the grant call such that it now returns a string, which is
the alias name of the newly created grant. The string is empty if the
grant operation failed.

As before apps can still mask granted keys by importing a key with the
exact same name including the added suffix. But everybody deserves the
right to shoot themselves in the foot if they really want to.

Bug: 37264540
Bug: 62237038
Test: run cts-dev --module CtsDevicePolicyManagerTestCases --test
          com.android.cts.devicepolicy.DeviceOwnerTest#testKeyManagement
	  because it grants a key
Merged-In: I047512ba345c25e6e691e78f7a37fc3f97b95d32
Change-Id: I047512ba345c25e6e691e78f7a37fc3f97b95d32

The new fonts do not have a dedicated fancy colon for the lockscreen clock
and fall back to Roboto which breaks the kerning.

Change-Id: I4621c6248de3f42f6c3c49ee4149bc1c0bb233e6
Fixes: 63891134
Test: visual; runtest -x packages/SystemUI/tests/src/com/android/keyguard/KeyguardClockAccessibilityDelegateTest.java

On AOD, we run the proximity sensor, so when a pulse comes in,
there is no need to wait for a new result. Instead, we can use
the existing value if available.

Change-Id: Ibded081e5011a3053e6990012f97f63865e20298
Fixes: 63538693
Test: receive notification, verify that pulsing starts immediately and does not wait for the proximity check.

This reverts commit e5d0b9dd.

Fixes crashloop with lock pattern

Change-Id: I3721444c91e2be625c59ec3e6ba14f1080badc07
Fixes: 63980375

Change-Id: I1670c714954e5835f6c79f446c463ee18d72d17b
Auto-generated-cl: translation import
Exempt-From-Owner-Approval: translation import

Change-Id: Ida215c44df2fd5572b046d426bca7304947398bc
Auto-generated-cl: translation import
Exempt-From-Owner-Approval: translation import

Change-Id: I8c164681df192fe74083e69adf301a0f312dc144
Auto-generated-cl: translation import
Exempt-From-Owner-Approval: translation import