Change-Id: I1ea48133f32324b6bf3cddde89952e1383e3e72c

Using the Q library causes parse errors for stats, as that library is
not forward-compatible with R. The R library is backwards-compatible
with Q and should be used on R builds.

Bug: 160656765
Test: statsd_testdrive on device with an updated NetworkStack
Change-Id: Idf3e654a679ab31d0d3c3d960f9745387edbbe4a

Change-Id: I44acb557f9b07f858f3e24f2b79c6ae15f2d4a36

Change-Id: I4c5b50031c36b95e79b2dbae7bee6a45deb05db3

Rename members for a clearer API, and add try/catch blocks to each
NetworkMonitor call to guarantee there will not be any crash.

Add a flag allowing to disable all the metrics collection code.

Bug: 151796056
Test: atest NetworkStackTests (see also test-only change)
Change-Id: I06d6dccc57146b955b15cf36a2109c68a5355494

1. Fill in each field of the NetworkValidationReported
2. Write the NetworkValidationReported into statsd

This patch also refactors tryCapportApiProbe to return null when the
capport data is incorrect, instead of doing the check after calling the
method. This makes it easier to compile capport API probe metrics.

Test: atest NetworkStackIntegrationTests NetworkStackTests
Test: atest FrameworksNetTests
Test: Manual test with statsd_testdrive
Bug: 151796056
Original-Change: https://android-review.googlesource.com/1295496
Merged-In: Icf34402d6a293cc76c32d00835cbf358c99a87fa
Change-Id: Icf34402d6a293cc76c32d00835cbf358c99a87fa

If capport API does not send any valid rely, the capportData
could be null in CapportApiProbeResult. Thus, take null
capportData for invalid case.

Bug: 154196512
Bug: 139034276
Bug: 151796056
Test: atest NetworkStackTests
Merged-In: I99cbff2eb1a9ab87a42011038d911fe15e7344a4
Change-Id: I99cbff2eb1a9ab87a42011038d911fe15e7344a4

Change-Id: Id89e24a0077bee4154a240734c04d193d1977cba

Each test target in NetworkStackCoverageTests needs to have appropriate
jarjar rules applied: this was not the case for NetworkStaticLibTests,
even though jarjar rules are already applied in NetworkStackTests and
NetworkStackIntegrationTests.

NetworkStaticLib is used by multiple modules that are each supposed to
jarjar it to their own package, so jarjar rules cannot be applied on the
test target itself.
Define an android library to apply the jarjar rules before including the
tests into NetworkStaticLibTests.

Bug: 152461494
Test: atest NetworkStackCoverageTests

Change-Id: I2afebd0e0fbfde2ed8c9daa396077761db23409f

FLAG_UPDATE_CURRENT was not helpful because:
 - For the venue info notification, the only extra is the Network, and
   the intent uses the network handle as identifier; meaning that two
   matching intents would already have the same extra.
 - The ACTION_WIFI_SETTINGS intent does not have any extra, so there is
   nothing to update.

Bug: 157475111
Test: atest NetworkStackTests; manual: connected to captive portals and
          used notifications
Change-Id: Ifd9e6ff04f2d574f3e28d612c8ea6215a209069e

LocalLog is in android.util, not android.net.
The previous code used to work because methods used by NetworkStack are
@UnsupportedAppUsage, but this should be avoided because the symbols are
not stable.

Bug: 160113128
Test: m; atest NetworkStackTests; manual: wifi working
(cherry-pick from AOSP with conflicts)
Merged-In: I3864ce089c02d53dfc6d0f9c58ac4a84daaaf787

Change-Id: I3864ce089c02d53dfc6d0f9c58ac4a84daaaf787

Change-Id: I695426e00381733e83324b9e88263b10894727e0

Auto-generated-cl: translation import
Change-Id: If8dc0134cbdd7c6380bee53c94c4731cf44704c9

Change-Id: I6b5068f6224208052954d9278cbcfaddc8ca0dc0

Change-Id: Ic23a19bf3ccd554b79dfa77b7330b0656ac23048

Problem:
1. When the errocode is not defined in DhcpErrorCode enum.
   Then the DhcpErrorCode.forNumber(errorCode) will return null.

2. Then use null as the parameter cause NullPointerException on
   addErrorCode.
   (Because the addErrorCode need nonNullable parameter)

Solution:
If the errorcode is not defined in the Dhcp ErrorCode enumeration,
please use ET_UNKNOWN instead as AddErrorCode parameter, not null.

Bug: 151796056
Test: atest
Original-Change: https://android-review.googlesource.com/1346103
Merged-In: I43b8415ab98b4cf6520c3240dc544a9f62730a4e
Change-Id: I43b8415ab98b4cf6520c3240dc544a9f62730a4e

The previous IpClientLinkObserver code could in theory call
mCallback.update with a linkState that came from another update; for
example:
 1. onInterfaceAddressUpdated
   - mLinkProperties.addLinkAddress
 2. onInterfaceLinkStateChanged
   - setInterfaceLinkState(false)
 1. mCallback.update(false) <- should be true ?
 2. mCallback.update(false)

In practice this would not happen because the onFoo methods are all
called in order (same binder token from netd), but IpClientLinkObserver
should not need to make such assumptions.

Bug: 151796056
Test: atest NetworkStackIntegrationTests (see also test-only change)
Change-Id: I60f5a319519069070eb5a07643686bf5ec937665

When turning wifi off, the interface gets torn down and empty
LinkProperties are received before wifi calls stop(). This causes a loss
of provisioning to be logged, instead of normal termination.

Watch interface link status up/down events, and when provisioning is
lost when the interface is down, consider it a normal termination.

Bug: 151796056
Test: manual: turn wifi off, observe events
Test: atest NetworkStackIntegrationTests (see also test-only change)
Original-Change: https://android-review.googlesource.com/1343236
Merged-In: I9d086a199de0017aa425219d20882211423925e0
Change-Id: I9d086a199de0017aa425219d20882211423925e0

This avoids potential conflicts if the library is also added to the
bootclasspath.

com.google.protobuf is pulled as a dependency when adding protobuffers,
like those used for data stall, IP provisioning and validation metrics.

Bug: 159587267
Test: m; manual: booted, wifi working

Change-Id: I3339e47c1ca1cd8b0186da0dbf880eff245b4c67

Change-Id: I9b5fafd799b9b3eeff170540e816d7c8ab9598b0

Auto-generated-cl: translation import
Change-Id: Id55f05d5114f9f76b53f9363c4578333dbbf26d4

Change-Id: I05b3263a6b956ddef153b2b90bdb31665c87e2ed

Bug: 151796056
Test: atest NetworkStackIntegrationTests NetworkStackTests
Test: atest FrameworksNetTests
Test: Manual test with statsd_testdrive
Original-Change: https://android-review.googlesource.com/1343438
Merged-In: Ib83ceb70af3491dacbb4a45f65ef38661ae75e32
Change-Id: Ib83ceb70af3491dacbb4a45f65ef38661ae75e32

1. Fill in each field of the NetworkIpProvisioningReported
2. Write the NetworkIpProvisioningReported into statsd

Bug: 151796056
Test: atest NetworkStackIntegrationTests NetworkStackTests
Test: atest FrameworksNetTests
Test: Manual test with statsd_testdrive

Original-Change: https://android-review.googlesource.com/1313574
Merged-In: If4bc6af1b794a8620a08858d6cfd85e661865bd7
Change-Id: If4bc6af1b794a8620a08858d6cfd85e661865bd7

Change-Id: Icfec0fd29533485c19e05fffdb3150dbf4eecdbb

If wifi and softAp shared with same interface and switching from wifi
to sotAp, there is race that tethering fail to set LCAL_NETID to softAp
interface because ConnectivityService do not release wifi netid from
that interface yet.

Bug: 158269544
Test: atest TetheringCoverageTests
      atest NetworkStackTests
Merged-In: I1dcf0a64190106820a93854b2eb53040341a97e6
Change-Id: I1dcf0a64190106820a93854b2eb53040341a97e6

Change-Id: I7a2261e19821d8793539db6c9d20510deec71a55