Time is deprecated and there are better alternatives.

Bug: 16550209
Test: atest FrameworksSaxTests
Change-Id: I301d1075b4b64c4586c2e4d7d9b0a12e609fe064

Properly encode an P-256 EC Public Key in uncompressed form, in
particular ensure that the resulting blob is always 65 bytes long as
is expected.

Was able to reproduce this with about 4% failures running a
test. After the fix didn't get a failure in 1,000 runs.

Also remove unused Util.integerCollectionToArray() function.

Bug: 239857653
Test: atest --rerun-until-failure 1000  android.security.identity.cts.ProvisioningTest#testProvisionAndRetrieveMultipleTime
Change-Id: I9a8a5570fde5a80f74632606126cdfcc1f6c7c99

FGS starts are allowed by default to apps targeting pre-S sdks. However,
on update their alarms may start getting denied if the app could not
reset its alarms.
Explicitly adding them to the allowlist to avoid this problem.

Test: atest FrameworksMockingServicesTests:AlarmManagerServiceTest
Test: Manual, using steps listed in b/238407723

Bug: 239098759
Bug: 238407723
Change-Id: I895901f0c870b161a8a4df92ebe93c873a55abc9
Merged-In: I895901f0c870b161a8a4df92ebe93c873a55abc9

Also move the resource owners to the new OWNERS file from the OWNERS
file one level of folder above.

Bug: None
Test: None
Change-Id: I81b3eeff0cf565482772023243652a949cfbcd1f

Bug: 210134615
Test: Unit + manual
Change-Id: Ic350e4e45c0d1597c6f61e3e3e717b3a2c1bb099
Merged-In: Ic350e4e45c0d1597c6f61e3e3e717b3a2c1bb099

Bug: 239607619
Test: Build
Change-Id: I84b3f813e798707d5564b54b6b2cc329f570908d

fdff6e62

Change-Id: I6b29eca9f21b36db0dbf9357625c36c230550987

This change early-exits from the sendEventToVpnManagerApp()
method if the profile was not a VPN app.

Otherwise the sendEventToVpnManagerApp() will call
getRedactedNetworkCapabilities() which will call
AppOpsManager#checkPackage() eventually.
And AppOpsManager#checkPackage() will check if the given package
is the same as the given uid. In this case, VPN sends
"[Legacy VPN]" as the package and sends 1000 as the uid, but
there is no package named "[Legacy VPN], so the SecurityException
is thrown.

Bug: 236315805
Test: atest FrameworksNetTests:VpnTest
Change-Id: I228f62a5e09017dbf985a614f2e42434238a220c

This makes the VpnManager APIs consistent with VpnService, ensuring that apps relying on CONTROL_VPN and a separate consent dialog (per CDD) can work properly using the VpnManager. Without this patch, there is an inverted incentive to use the VpnService.

As a workaround, apps using this with CONTROL_VPN already can/do work around this by calling VpnService.prepareAndAuthorize().

Bug: 232051081
Test: atest FrameworksNetTests:VpnTest
Change-Id: I0e0566bb8fed2f9330889e031175c33d499fa855

Add a note about the return values from logging function since it was
asked in b/228523679.

Bug: 228523679
Fix: 228841312
Test: m
Change-Id: I39a3cad4ba10c4602e58ec9e88c7864ead4b9d85

Check whether the package is allowlisted to always have full location
data.

Test: atest LocationAccessPolicyTest
Bug: 231445403
Change-Id: I33c5088b639595c8e0f89f3f2a926dfc5d830fcf
Merged-In: I33c5088b639595c8e0f89f3f2a926dfc5d830fcf

Ranges were the same as LTE values, which is incorrect.

Test: atest CellSignalStrengthNrTest
Bug: 234304714
Change-Id: I030c6aeec22556454955bb4f9671afe830bb9e2f
Merged-In: I030c6aeec22556454955bb4f9671afe830bb9e2f

Test: n/a
Change-Id: If647d9f16ab26aab2a6cb7d699031a5db8cd6015

Merge "Add explanation about the purpose of accessibility heading and use case apps should consider."

Revert submission 2152437-remove-net-module-utils-srcs

Reason for revert: broke build.
Bug: 239599703
Reverted Changes:
I058e1aa37:Remove unused net-module-utils-srcs filegroup.
I7c8a12372:Remove unused net-module-utils-srcs filegroup.

Change-Id: Ib9f9319fd6dfade634eda65cafc8c9f7b643f3bb

* changes:
  Offer explicit 3-byte vs 4-byte modified UTF-8.
  Cache least recently used output buffer.

This reverts commit 61a0a35d.

Reason for revert: debugging b/237904436

Change-Id: I557e7b69cd5917188c33cbd42293307efa9d6f8f

As documented in art/runtime/jni/jni_internal.cc, ART has deviated
from the RI by using a 4-byte encoding instead of the 3-byte encoding
required by the JNI specification.

Some users are okay with this 4-byte encoding (where they control
both the reading and writing logic) but other users require
compatibility with the DataOutput/DataInput API contract, so this
change lets users request either behavior.

This change now exercises all tests in both 4-byte and 3-byte modes,
and exhaustively confirms that all valid code-points match the
DataOutput/DataInput contract when in 3-byte mode.

Benchmark results still show significant performance benefits when
using this 3-byte encoding over the upstream RI:

    timeRead_Upstream_mean (ns):                  5090068
    timeRead_LocalUsing3ByteSequences_mean (ns):  1996032
    timeRead_LocalUsing4ByteSequences_mean (ns):  1813250

    timeWrite_Upstream_mean (ns):                 3856276
    timeWrite_LocalUsing3ByteSequences_mean (ns): 1632697
    timeWrite_LocalUsing4ByteSequences_mean (ns):  886503

Bug: 236923096
Test: atest FrameworksCoreTests:CharsetUtilsTest
Test: atest FrameworksCoreTests:FastDataTest
Test: atest FrameworksCoreTests:XmlTest
Test: atest FrameworksCoreTests:BinaryXmlTest
Test: ./frameworks/base/libs/hwui/tests/scripts/prep_generic.sh little && atest CorePerfTests:FastDataPerfTest
Change-Id: Ibddd36410a0d4a909522de011f23a337b53d6889