* Most of the genrules doesn't affect the JNI/jajar. Only genrules that uses
the following scripts must be jarjared
  * //base/android/jni_generator/jni_generator.py
  * //base/android/jni_generator/jni_registration_generator.py

Test: None
Change-Id: I2f750e151002b8b21fa2bfd557ad1bbaf5110dff

* The current testing situation for Cronet is dire due to the presence of Cronet on the platform,
As cronet is on the platform, we can't run any unit-tests as they'll link against the platform version
and not the statically-linked cronet. We could avoid this by jarjaring the code however this is impossible.

* It's impossible to jar-jar the code as the C++ code which does JNI expects jar-jared java classes. So the
only possible solution here would be to duplicate the C++ modules, one for testing(with no jarjar) and another
for platform(with jarjar)

* Java sources/actions are not collected for testing modules until a proper solution has been figured out.

Test: None
Change-Id: I20bbad13d83e9e3c7956f028f3f0493b24d0f8bc

Test: none
Change-Id: I72a2a23021b01bbf7a78fd458405340349503ea5

* This is a test suite containing 90 unit tests which passes currently on AOSP. using a custom test runner that will be pushed
in upcoming commits

Test: m
Change-Id: Ifa2aa82c5a36ab5b5f9f91dc52dfe803a429a074

* changes:
  gn2bp: Add linker script to modules
  gn2bp: Add missing linker flags
  gn2bp: Fix C++ warning showing up as errors when compiling cronet tests

Test: m
Change-Id: I549d78baf94b1abec07782df006269ba00e2776c

* Tests usually shim memory allocations for metrics purposes through linker flags.

Test: m
Change-Id: I2a3bbe648f155469721cf1df25439ca60afee6b5

Test: m
Change-Id: Id48dabf893fb7dc7698973f8d52a802134d77e82

* The cmd of the `cc_genrule` is now arch-dependent. So we no longer generate a genrule for each arch.
  The propagation of the arch-dependent genrule was broken due to an old if-statement.

Test: m
Change-Id: I4b9b522c429f32fe74d141b00bd856f6c39498d7

* This is a python script that runs a binary on files to generate output files for testing.
* The python script is not really needed as we can run the binary right away.

Test: m
Change-Id: I3be64e7f51380f2c028dec3168c924451076db95

* Aidl `local_include_dirs` was hardcoded. This change should handle extracting the srcs and local include dirs for any
aidl action.

Test: m
Change-Id: I7893dd3897f292f96c1934b192d20b97c26c54cb

Test: TH
Change-Id: I66bbbb17446ea1f87e07b3d63d2c4e1ffa9d1a51

Test: new test in this patch
Bug: 269719647
Change-Id: I32e8d35f1751e2fd81a0007ae6cb308b6bcbb463

Bug: 269714344
Test: atest FrameworksNetTests
Change-Id: Ia9c47967a1b96204a6a739d133f2b8455229af52

Bug: 251012627
Test: atest CtsNetHttpTestCases
Change-Id: I5bd980e6b289b8ef86f1c0d8b0f5fe473bd3aab8

A template with type MATCH_MOBILE could have empty subscriber
IDs but it should not contain one of subscriber IDs is null.

An app might still build a template through the constructor
which is annotated with @UnsupportedAppUsage. NetworkTemplate
will throw an exception when the app trying to construct a
template with type *_WILDCARD. The constructor should be
backward compatible with old version so this change is to add
the backward compatibility to have NetworkTemplate not throw
an exception.

Bug: 267701889
Test: FrameworksNetTests
Change-Id: I23a607dae508e0c53520e2edf187cb611ed36b68

Test: VpnTest
Bug: 269714344
Change-Id: I0d8a2818ea0b67ebb5da7dbac9cd6aea9bede386

Move the CtsHostsideNetworkTestsAppNext to the top of file to to prevent
any future automerger merge conflict between aosp and downstream
branches. The CtsHostsideNetworkTestsAppNext target will not exist in
some downstream branches, but it should exist in aosp and some
downstream branches.

Test: atest -c CtsHostsideNetworkTests
Bug: 270006466
Merged-In: I8cb64d8bb86b781cd57d1a1a466c56185573fcc2
Change-Id: Icc475586d6f26d913b328647b94af1b53a3bb32d

The untrusted apps should not directly access /dev/socket/mdnsd since
Android U(SDK 34). For untrusted apps built with target SDK 33 or less,
it should still be able to access the mdnsd socket. Fix the mts test
suits from mts-networking to mts-tethering. If the test suits is marked
as mts-networking, it would run in NetworkStack MTS, which isn't really
what is tested in the tests.

Test: atest CtsNetTestCases CtsNetTestCasesMaxTargetSdk33
Bug: 267102290
Change-Id: Icfbce8bb387df4481eef7fae94ffc38539975ce5

ActivityManager checks if there is any non-protected broadcast
sent from the system to prevent malwares sending the fake intent.
This could be fixed with declaring it as a protected broadcast
which is the current implementation. However, the uid in the
AndroidManifest for tethering is networkstack uid. Though system
only check whether the intent is defined as protected broadcast
or not regardless of where the protected intent is defined, it
is confusing to define the protected intent in tethering
AndroidManifest. Thus, update to alternative way to fulfill
the protection in ActivityManager to declare the required
permission in the broadcast filter and specify the expected
package name of the intent.

Bug: 269383522
Bug: 259000745
Test: atest FrameworksNetTests
Test: manually check no am_wtf log complains sending non-protected
      broadcast from system
Change-Id: I04986aed4fb92f85adcbac8a61665f3f465e2eab

Reduce duplicated code and remove unused variable.

Test: atest VpnTest
Change-Id: I9f38bf7e16d821b51ee966607f873c5d39714e3c

File a VPN request to prevent the VPN network being lingered.

The VPN network will be lingered and onCapabilitiesChanged()
will be fired when the linger timer is expired, which will
cause the test receiving an unexpected onCapabilitiesChnaged()
and make the test failed eventually.

Bug: 265396507
Bug: 265510523
Test: atest FrameworksNetTests
Change-Id: Id9ad810d46cb2bbb13fa5c602520635ae8e73e31