Bug: 289414897
Test: it builds
Change-Id: Iaaa94da72df680406138364e06865c768b79edef

Define Thread hardware feature FEATURE_THREADNETWORK = "android.hardware.threadnetwork"
so that apps/users can know whether the device has Thread support.

This flags is defined as public API but not system API because we
defined TRANSPORT_THREAD as public API and general apps can access
Thread network by adding callback for the Thread network. Adding
the FEATURE_THREADNETWORK as public API allows apps to be more
clear/confident of whether they can retrieve the Thread network
with TRANSPORT_THREAD.

FR: b/235016403

Bug: 284296494
Bug: 292948264
Change-Id: I3bce3458fa721a20d8937a0c70eec2dbc7c54bc6

Merge "Fix the concurrency issue when 'linkToDeath' in AccountManagerService that leads to JE" into main

This is only used for legacy transition, so change it to an error log to
fix the flakiness.

Bug: 242718321
Test: pass existing tests.
Merged-In: Ib2a68f7488724370e44da28bdc30c8db19085889
Change-Id: Ib2a68f7488724370e44da28bdc30c8db19085889

The @JvmDefault annotation and -Xjvm-default=enable argument are both
removed from kotlinc 1.9.0 in favor of -Xjvm-default=all.

Bug: 291335478
Test: builds
Change-Id: I473e578b92482fbd6c8812c4d32acc1a4c27a84a
Merged-In: I473e578b92482fbd6c8812c4d32acc1a4c27a84a

The documentation had a typo (missing "@") and would not render some
links correctly. See: https://developer.android.com/reference/android/os/Handler?hl=en#Handler()

Change-Id: I55333133f130736271c6550b0e8fba7e485ef933

Bug: 290757184
Change-Id: Ie897f0d6a8f121d512f2d04aeb213bde6622e73c
Test: N/A

Move the ref of 'mResponse' after the completion of 'linkToDeath' to avoid concurrency issues caused by 'unlinkToDeath' being triggered in different thread

Test: MTBF
Bug: 291856266

Change-Id: Ifc5af9f85aac83be56afec9a1fb32501a6f32ebc
Signed-off-by: zhuning3 <zhuning3@xiaomi.corp-partner.google.com>

This reverts commit dde5ebaa.

Reason for revert: Will re-introduce http://b/278157584

Even though KeyMint v2 supports the MGF_DIGEST tag, it does not include it in the key characteristics. This would not be a problem for keys generated on an Android U device with KeyMint v2 but it will be a problem on a device that was upgraded to Android U where keys were generated before the upgrade (so the MGF_DIGEST tag was not added).
Because we have no way of knowing if the MGF_DIGEST tag was specified when the key was created on KeyMint implementations older than v3, we should not add the tag on begin().

Change-Id: I7b34799b95eb2ff054ec4d090ccbd93e6442dcfe

Change-Id: I0a12812e0f0171bf8ef65dac728ae78b9323d701

There is a possibility that a certain DC does not perform
ensureActivitiesVisible since exception occurs on the binder thread.

If an exception occurs during its execution, the execution of the
finally statement is not conducted. From this point on, the DC doesn't
execute ensureActivitiesVisible forever.

Bug: 291175616
Change-Id: I042c15d3836f62a6c31e22d05023f4e61fb046d2
Signed-off-by: Hyeongseop Shim <hyeongseop.shim@samsung.corp-partner.google.com>

Since fsverity builtin signatures are no longer being used, the comment
in FileIntegrityService#loadAllCertificates() no longer applies.

Bug: 290064770
Test: comment-only change
Change-Id: I78ca3868dabe3133c7e521a5dc8fcc8cd598ac3c

To save CPU cycles during boot for low resource device a new
configuration is added to delay registration of psi monitoring until
boot is complete. ActivityManagerService will send an lmkd message to
start psi monitoring after boot.

Bug: 288566858
Test: Build, boot and verified boot logs to confirm the behavior.
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:9c63a06ddc00747d0f5901e4fb29025c9b1acdee)
Merged-In: Iee5cecdae54304b092c6a1801f3814e13a919be2

Change-Id: Iee5cecdae54304b092c6a1801f3814e13a919be2

Merge "Provided a solution to sort partitions from order in /product/overlay/partition_order.xml, added a debugging command to dump the partition order and how it get established." into main

HdmiVideoExtconUEventObserver handles only "HDMI=1" external
connection state while kernel generates uevent with "DP=1" state
when external hdmi display is connected via USB-C-to-HDMI converter.
This results in wrong DisplayPolicy.mHdmiPlugged value when
hdmi display is connected, so we need to handle "DP=1" state as well.

Bug: 288003290
Test: take bugreport while external hdmi display is connected
and grep for "mHdmiPlugged=true"
Signed-off-by: Aleksej Makarov <aleksej.makarov@sony.com>
Change-Id: I410122aad09a5414a736cac51647e75fcfa61055

Test: adb shell dumpsys window policy
Change-Id: I802de6a6b280bbcfa9dda0b12efa165b577aef34

/product/overlay/partition_order.xml, added a debugging command
to dump the partition order and how it get established.

Bug: b/278850109
Test: Added and verified affected tests pass.
Change-Id: I707ace74dc55ed5e37b672f191636e8d0ff78e95
Merged-In: I707ace74dc55ed5e37b672f191636e8d0ff78e95

incident_helper contains some "interesting" code that automagically
fills in a SystemPropertiesProto by finding the protobuf fields by name
using system property name components.  One of these fields is
'update_verifier_nonencrypted' which is nested inside 'init_svc'.  This
gets filled in with the value of init.svc.update_verifier_nonencrypted.

The "update_verifier_nonencrypted" service is being renamed to simply
"update_verifier", and as a result the name of the corresponding
"init.svc.${service_name}" system property will change too.  Therefore,
rename the corresponding protobuf field too.

Bug: 208476087
Test: presubmit
Change-Id: I782ab726870df64c5b9cb354b223634d85a0f63b