This reverts commit c996b909.

Reason for revert: Fixed CTS tests

Change-Id: I4ebb7d1a05eec41e8c5f603c42972c2e16d60b3d

3bebb903

Change-Id: I605177fabae80ea68399aa42a66419119cf02cd3
Bug: 343583446
Bug: 343690533

it's used in v2/android-platinum/suite/test-mapping-staged-platinum

Change-Id: I87d9aff0dea6344908e44ed693730143f504dbf8
Test: presubmit
Bug: 341947105

This reverts commit ec7f7207.

Reason for revert: Fixed tests

Change-Id: Iadd0ea6f09f7f3159f94489c03f28c326bbbb664

This will allow to build them more effectively.
This has no impact on the test execution itself.

Change-Id: I76bbb06b6b5f0e21f096b80da9062863294d2ff4
Test: presubmit
Bug: 341947105

This will allow to build them more effectively.
This has no impact on the test execution itself.

Change-Id: I22183f1f2176e929eb0ab82f9f7eaa20ccb770c8
Test: presubmit
Bug: 341947105

These tests are build with -Werror, so we need to migrate them.

Bug: 341129262
Change-Id: I0bd8d03f16f0fef1772826a24f663a7babe2bfcd
Flag: test_only
Test: presubmit
Merged-In: I7661dd73c3f9d0e44cabd928b96cf2affc9cae22

.. so that they are included in the test_suites package

Bug: N/A
Test: check general-tests_list.zip
Change-Id: I79fbb7d66e506cded5c09ae871ef185124f2ce61

Require VCN to be used by a "main user" instead of a "system user"
since "system user" will no longer be a full user on HSUM devices

Bug: 310310661
Test: FrameworksVcnTests, CtsVcnTestCases on non-hsum and hsum devices
Flag: android.net.vcn.enforce_main_user
Change-Id: I5abfa7ba82055cd953083b1ab3f83e61bafd8a55

Allow disabling detector for better configurability

Bug: 336638836
Test: atest FrameworksVcnTests(new tests) && atest CtsVcnTestCases
Flag: android.net.vcn.allow_disable_ipsec_loss_detector
Change-Id: Icd7183d12fb287399a500ea9c0ee4125c749275c

Flag: NONE
Test: n/a
Bug: 338178020
Change-Id: I6494166c24d37d398d72b05a9d7b3f966f3b9ffa

IpSecTransformState is a new API that exposed from a mainline module.
Ideally before SDK finalization, platform should check the API flag
com.android.net.flags.ipsec_transform_state before calling the API.
However the flag is defined in mainline module is not accessible from
the platform. Thus previously a placeholder flag was used.

This patch removes the usage of the placeholder flag. Instead the
code will check the availability of the API with a try catch block

Bug: 328844044
Test: atest FrameworksVcnTests && atest CtsVcnTestCases
Flag: NONE mainline API flag not accessible; using try catch
      block to gate the behavior
Change-Id: Ibbcb14817a6d714cdc99cf0894f1fc935a602a2c

Bug: 331528424
Test: m OneMedia
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:a401cbeeabfaece70150e7fc9ab41a2b9f02dd81)
Merged-In: I13725bc7dccb1c4cb22f1cb2ea5a875ee927bf13
Change-Id: I13725bc7dccb1c4cb22f1cb2ea5a875ee927bf13

When the expected received packet number is smaller than 10, the
packet loss detection result will be ignored because the sample
size is too small to ensure a reliable result.

This patch also fixes the bug where the detector does not update
ths packet loss threshold when carrier config updates

Bug: 332598276
Test: atest FrameworksVcnTests && atest CtsVcnTestCases
Change-Id: Iccc47e83c48699d139029420572e2a2616c357cd

This pacth enables IPsec packet loss detector to handle the case when
there is an intentional sequence number leap on the server's downlink.

Previously the detector assumes that sequence number will always
increase consecutively, which is not true. During load balancing the
server might add a big leap on the sequence number intentionally. In
such case a high packet loss rate does not always indicate a lossy
network. At the same time, a low loss rate does mean the network is
not lossy

Bug: 332598276
Test: atest FrameworksVcnTests (new tests) && atest CtsVcnTestCases
Change-Id: I163cb274d293a305499fd60f7ad6eed394af5a4d

Refactor getPacketLossRatePercentage to return an object instead of
an integer. This is for extending the Packet Loss Detector's ability
to handle inbound sequence number leap

This patch does not include any behavior changes

Bug: 332598276
Test: atest FrameworksVcnTests && atest CtsVcnTestCases
Change-Id: Ied42e581fb331ab0603225865236779f50cc4881

This reverts commit 15ba5a90.

Reason for revert: Fixing the revert.

Change-Id: I962eb1c25f88d93a659d86d6fa138f324dbe5eb0

94058265

Change-Id: I847a3f5bd85879f02ddaa1d6043762121651ca31
Bug: 333155088

This reverts commit 0f91c2b9.

Reason for revert: Need to move back files to original place.

Change-Id: Icb7ab9956f2b662dd918a6be3941e830f1e05002

For detailed guidelines and further information on the migration please refer to the link below,
go/new-android-ownership-model

Bug: 304529413
Change-Id: I435534a2953e4d937b78a9a374e32f3d01773211

Since the bootloop is not for complete boot rather for  system-server
restarts, we dont have to be as conscious about performing higher
impact mitigations and we can perform them earlier. (Reboots
initiated by user doesnt trigger a bootloop scenario.)

Removed the increment boot count threshold needed between 2 mitigations.
Also removed BOOT_LOOP_THRESHOLD(default value: 15) which was needed to
perform any high impact mitigations.

PackageWatchdog would wait for DEFAULT_BOOT_LOOP_TRIGGER_COUNT (default
value: 5) after a reboot (ex: WARM_REBOOT step in rescue party, mainline
rollback). Changed the behaviour to wait for DEFAULT_BOOT_LOOP_TRIGGER_COUNT
only for first mitigation.

MitigationCount was not getting reset properly after de-escalation
window. Updated the logic to save mitigationCount to the file after reset.

Did manual tests by killing system_server process using the following
command:
`adb shell kill -9 $(adb shell pidof system_server)`
Verified that the first mitigation was performed at 5 restarts.
Every restart after that resulted in next mitigation being executed.

Ran `atest PackageEatcdogTest` to verify PackageWatchdogTest and
CrashRecoveryTest changes.

Test: Unit test, manual test
Bug: 291137901
Change-Id: Ia0174e0e5dca09c5d4e9d3a12909c5e5087b4dbf

For TestableContext, TestableResources, etc.

Test: N/A
Change-Id: I4ac0471388e88d1fa176992280250928a1c2e79d

Bug: 313005703
Test: atest UpdatableFontDirTest UpdatableSystemFontTest
Test: atest GtsFontHostTestCases FontManagerTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:d5e936166beea5a5a2b37ce0d9b1795c0438a2d3)
Merged-In: Ib4a32a9bbb27ebd2e9a32dc308f79ec1c91332ce
Change-Id: Ib4a32a9bbb27ebd2e9a32dc308f79ec1c91332ce

Bug: 323238888
Test: atest FrameworksVcnTests(new tests)
Change-Id: I83f2da42fe0ffed5d4403429e968510c7eeabec1

Bug: 329139898
Test: atest IpSecPacketLossDetectorTest (new tests)
Change-Id: Icc31fe7f1b76e7849c910b3cd1c300bcf4c1f3a3

This CL calls CarrierConfigManager.getCarrierConfigSubset instead of
getConfigForSubId to guard against crashing when phone process has gone.

The former method is designed for system components to retrieve carrier
configs with consideration of phone process may be gone (e.g. during
rebooting from previous crash).

Bug: 319791612
Test: atest TelephonySubscriptionTrackerTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:d7ebd7c10712a8a319ae6117949d4ece92be4de8)
Merged-In: I784610b243db2a666c1fe89b1438950a2f6a1478
Change-Id: I784610b243db2a666c1fe89b1438950a2f6a1478

PackageWatchdog will apply high user impact actions only in case of
network failure.

RescueParty updated the list of rescue levels and their corresponding
impact.

Test: unit and manual tests
Bug: 310236690
Change-Id: Iff34f6051b801a0d45149c317a7c9f344a2bd984

Utils that are not currently exposed as API but are required for the
module.

Bug: 289203818
Test: TH
Change-Id: I7dbb8f673b54ad9487e642bb339c5a30f561bf3c

Pass Device Bus from the native side to the Java side. This is done so
we can log Device Bus ID in atoms.
Since the same vendor ID could mean different vendors depending on
whether the device is connected over bluetooth or USB, we require to know
the device bus to disambiguate the vendor IDs.

Bug: 308918242
Test: atest InputDeviceTest
Test: atest inputflinger_tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:b4015294e1c3452a00d4a326ca3871e6e56b5f78)
Merged-In: I0ff2e31d7a8b610b0e1208cc5c444d1f785e162c
Change-Id: I0ff2e31d7a8b610b0e1208cc5c444d1f785e162c

The NDK APIs are supposed to be C-compatible. This one accidentally
included a default argument, which is a C++ feature. That's being
fixed, so this needs to pass the argument explicitly.

Bug: https://github.com/android/ndk/issues/1920
Test: treehugger
Change-Id: Ia79da4b4593dfd46302cb44298e906bb8e6c4d86

Test: n/a
Change-Id: Id2586f04933b97e1d8562fd86dc7e65ee419c10e

CL created based on go/new-android-ownership-model

Bug: 304529413
Test: make
Change-Id: I7db3a93e8f4752591822062e043ee7126248b2cc

Before, the test gets root implicitly via DeviceSetup which
wasn't intented.

Change-Id: I4b86fd5ee31f746942a2bf073a29cb2180a39f27
Test: presubmit
Bug: 325094408

Before, the test gets root implicitly via DeviceSetup which
wasn't intented.

Change-Id: I9b34a85025a6aa4f138483202fd11db0cbb8b04b
Test: presubmit
Bug: 325094408

Rollbacks are currently stored only for some mainline packages, but
rollbacks will be added for phonesky and GMS core in V. These new
rollbacks should not be treated similar to mainline. We would want to
perform GMS core rollback only when all other rescue party mitigations
are already tried. And Phonesky should not be automatically rolled back.

We introduce a new field rollbackImpactLevel to RollbackInfo, which is
used to determine the order in which these rollbacks should be performed
relative to other mitigations in PackageWatchdog.

rollbackImpactLevel is exposed through PackageInstaller.SessionParams.

Bug: 291135724
Test: CTS test. Unit tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:a3ae2464aac43d8bbc2129bdea7733d09b90e2da)
Merged-In: I723405eb62577202893ff208af2ab01b212b112a
Change-Id: I723405eb62577202893ff208af2ab01b212b112a

Split flags.aconfig to platform flags and module flags.
Platform flags are used from platform code.
Module flags are used for FlaggedAPI annotations in modules.

This CL cherry-pick ag/25977118 to aosp-main-future.
After this CL, aosp/2919289 can be merged.

Bug: 321624552
Test: TH
Change-Id: Ie8e0f911d0f7d7e81d108b8e8ab539b29a255ad0
Merged-In: Ie8e0f911d0f7d7e81d108b8e8ab539b29a255ad0

This test started failing as it was not able to access
CrashRecoveryProperties. Mocking them in the test fixed it.

Bug: b/323272250
Test: atest PackageWatchdogTest:com.android.server.PackageWatchdogTest

Change-Id: I6ec10adfc17cb85e1c370ff76d08c0aa7e14c11f

This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.

For more details please refer to the link below,
<add g3 doc link>

Bug: 304529413
Test: N/A
Change-Id: Iee8a9d8357c174532902d88d5d59e41c6c518c2f

While the main fix is on the other change in the topic, this change:
 * Adjust to the installd API change by dropping userId in the call
 * Mark the test as suitable for secondary users

Bug: 319280249
Test: atest FsVerityTest
Test: atest FsVerityTest --user-type secondary_user
Merged-In: I1abc779ddc4fd79644d64b704698d0e7d67a9d75
Change-Id: I1abc779ddc4fd79644d64b704698d0e7d67a9d75

Split flags.aconfig to platform flags and module flags.
Platform flags are used from platform code.
Module flags are used for FlaggedAPI annotations in modules.

Bug: 321624552
Test: TH
Merged-In: Ie8e0f911d0f7d7e81d108b8e8ab539b29a255ad0
Change-Id: Ic868b70b3be10d4e394f005cd55a858acc7ba14d