Bug: n/a
Test: n/a
Change-Id: Id0f1a76eb470e47d28bd40dc4c42c648272b4a27

The CONTEXTHUB_SERVICE may not be published if the
FEATURE_CONTEXT_HUB feature is not present. So getting the ContextHub
serivce with "context.getSystemService(ContextHubManager.class)"
will throw ServiceNotFoundException.

This commit fixes this issue by checking the CONTEXTHUB_SERVICE
before creating the ContextHubManager instance.

Test: verified with cuttlefish that it won't throw from NearbyService
Bug: 299388818
Change-Id: Icd51a0f88c10259f4a912f5dd82bad49b70562e3

FeatureFlagsFilter looks for `android:featureFlag` attributes in the XML
and removes elements according to the given flag values.

Bug: 297373084
Test: atest aapt2_tests
Change-Id: Icf97de2152c0c53b0b4518ae837e0d198873d1c5

* changes:
  Add PermissionAnnotationDetector
  Ignore superMethods from non-Stub parents

This reverts commit c83ec716.

Reason for revert: b/309999062 | testSmsShortCodeDestination failing

Change-Id: I98b18677f6330e6d1fb52bc3cdfec7c4a4418b57

Bug: 310547345
Change-Id: I64cc5ff6659dfa6875baa225227951d1d5f86eb4
Test: N/A

* changes:
  Remove the SDK level checks.
  Remove findIPv4DefaultRoute
  Remove LegacyVpnRunner

Test: N/A
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:e715b9927adc1b5de39e081b9a76cec0713130da)
Merged-In: Ieca72562b291839efe14a03e987da1b13fb6acdc
Change-Id: Ieca72562b291839efe14a03e987da1b13fb6acdc

There are several cases where inner classes of @SystemApi-annotated
classes should be kept, but aren't. Add a conditional rule to ensure
this. This is probably overly conservative, but for now should avoid
issues with optimization.

A follow-up change will refactor this to reuse the rules in
system-api.pro, but that requires a bit of build file surgery first.

Bug: 300514883
Change-Id: Ibd561a9098881db1c7e78346d60f4c91d9c75894
Test: m + check services.jar dex diff

Change-Id: I60a3bf312b1fff4abe6c72f9ae30482b894b543d

Test: owners change
Flag: EXEMPT
Change-Id: I6e2483650a543efdbc5b38b788d5d73619b80c4b

This detector ensures that all AIDL-generated interfaces are annotated
with one permission annotation (@EnforcePermission,
@NoPermissionRequired, or @PermissionManuallyEnforced). It is part of
the framework linters and disabled by default.

It will be enabled explicitly in a subsequent change (for
services/Android.bp). The baseline of the services will also be updated
to capture the current status of non-annotated interfaces.

Bug: 220214993
Test: atest --host AndroidFrameworkLintCheckerTest
Change-Id: I0fbd41b63465f119d90505153fa3a98c0fcdc798

Bug: 309993780
Flag: NA
Test: N/A, just OWNERS updates
Change-Id: I37c660a7cb53970b0bd5f8c73436b4ce4f79518a

Bug: 297373084
Test: atest aapt2_tests
Change-Id: I7567aa8f41e6fde7334430446a940eb6b04c1446

The CtsHostsideNetworkTests:com.android.cts.net.
HostsideNetworkCallbackTests needs to know whether trunk flag is enabled
or not. But there is no stable way to read the flag from CTS for module.
So adds this hidden API in platform.

Bug: 288340533
Test: atest
CtsHostsideNetworkTests: com.android.cts.net.HostsideNetworkCallbackTests

Change-Id: I02cea917a3f75f11d6ea5754a6ea0d460f1372c9

Currently, the signature file elides overrides of a default method,
as they are not essential for the compilation of the stubs.
However, in some scenarios, the overrides of a default method may be
essential for the compilation of the reverse dependency of the stubs.
In the scenario seen below:
```
// API
interface ApiInterface {
    public default void bar() {};
}
class ApiClass implements AnotherParentInterface{
    public void bar() {}
}

// App depending on the API
interface AppInterface {
    public void bar();
}
public class AppClass extends ApiClass implements AppInterface {
}
```
Removal of `ApiClass.bar()` will lead to not overriding an abstract method
`AppInterface.bar()` compilation error in `AppClass`.
Therefore, this change adds the overrides of a default method to the
signature files.

Test: checkapi
Bug: 299366704
Change-Id: I212bd9aa895088fa9de33c7e3521453dea30c350

These are used by nfc stack, so should be formal APIs

Bug: 301090456
Test: CtsVerifier
Change-Id: I60ce07e30bbec5458ca72b6e11b57b0f0058d589