This reverts commit 1cf56be6.

Reason for revert: the test that fails is bad, needs to be fixed

Change-Id: Ifa225ea5d8a7cf3df1132fb0e3c411ed18c5ea57

This reverts commit 1d71aa6f.

Reason for revert: Likely culprit for b/342000526  - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.

Change-Id: Iff38c55a7ec68786107c305129ab091b2384b36b

This CL adds a flag cache class to PackageParser that is
available during the startup package Parsing, as opposed to
the one in SettingsProvider.

Manifest parsing now calls into this cache to skip the flagged-
out entries

Bug: 297373084
Test: atest PackageParserTest
Test: Manually on a device. Verified that permissions behind a disabled
feature flag were absent. Override the setting for the flag in device
config to enable it, rebooted, then the permission was present.

Change-Id: I8d8ea0a264dfbfd30adf79c6051410cda7bdebbe

Bug: 326227403
Test: adb shell device_config put biometrics_framework com.android.server.biometrics.use_vhal_for_testing true
Change-Id: I4dc95def492ef606e93259d68519261c6faef84e

This is the same as Iefdd457e99fc61c1ce2f5a05ae59f5e12256a764 where we
moved the dependency on protolog.conf.json.gz to services.

core.protolog.pb has is causing a dependency cycle reported as below:

error: frameworks/base/services/core/Android.bp:111:1: encountered dependency cycle:
error: frameworks/base/services/core/Android.bp:311:1:     module "core.protolog.pb" variant "android_x86_64" depends on module "checked-core.protolog.pb"
error: frameworks/base/services/core/Android.bp:111:1:     module "checked-core.protolog.pb" depends on module "gen-core.protolog.pb"
error: frameworks/base/services/core/Android.bp:78:1:     module "gen-core.protolog.pb" depends on module "protolog-groups" variant "android_common"
error: frameworks/base/core/java/Android.bp:589:1:     module "protolog-groups" variant "android_common" depends on module "framework" variant "android_common"
error: frameworks/base/Android.bp:542:1:     module "framework" variant "android_common" depends on module "framework-minus-apex" variant "android_common"
error: frameworks/base/Android.bp:486:1:     module "framework-minus-apex" variant "android_common" depends on module "core.protolog.pb" variant "android_x86_64"

Bug: 321626681
Test: check the existence of /system/etc/core.protolog.pb in installed-files.txt
Change-Id: I502eee9e184bcf5fa3e5443cc3c124828ed565ad

framework-jarjar-rules.txt contains a rule that renames
the package "perfetto.protos" to "android.internal.perfetto.protos".

However, the rule was not affecting the entire framework's code.
The confusing result was part of the framework importing "perfetto.protos"
and other parts importing "android.internal.perfetto.protos".

This commit adds a new library "perfetto_trace_javastream_protos_jarjar"
that provides to the entire framework the perfetto javastream protos
under a single unified package "android.internal.perfetto.protos".

Test: m framework-minus-apex
Bug: 276433199
Change-Id: Ie653c7b7b763fd97f021f89d413a7ed360946e7b

The dependency is a "required" dependency, so it's not used for building
framework-minus-apex. We just want that protolog.conf.json.gz is
installed along with framework-minus-apex.

This CL moves the source of the dependency from framework-minus-apex to
services for two reasons:

1. There's a dependency cycle:
  checked-protolog.json
  -> generate-protolog.json
  -> protolog-groups
  -> framework
  -> framework-minus-apex
  -> protolog.conf.json.gz
  -> services.core.json.gz
  -> checked-protolog.json

Currently, this cycle is harmless because the installation of required
modules is done by Make and Make is not checking cycles there. However,
this is preventing Soong from implementing the installation of required
modules by itself.

2. services don't have such a dependency cycle, while
   framework-minus-apex and services are installed together.

Bug: 321626681
Test: check the existence of /system/etc/protolog.conf.json.gz in
installed-files.txt

Change-Id: Iefdd457e99fc61c1ce2f5a05ae59f5e12256a764

The dependency is a "required" dependency, so it's not used for building
framework-minus-apex. We just want that protolog.conf.json.gz is
installed along with framework-minus-apex.

This CL moves the source of the dependency from framework-minus-apex to
services for two reasons:

1. There's a dependency cycle:
  checked-protolog.json
  -> generate-protolog.json
  -> protolog-groups
  -> framework
  -> framework-minus-apex
  -> protolog.conf.json.gz
  -> services.core.json.gz
  -> checked-protolog.json

Currently, this cycle is harmless because the installation of required
modules is done by Make and Make is not checking cycles there. However,
this is preventing Soong from implementing the installation of required
modules by itself.

2. services don't have such a dependency cycle, while
   framework-minus-apex and services are installed together.

Bug: 321626681
Test: check the existence of /system/etc/protolog.conf.json.gz in
installed-files.txt

Merged-In: Iefdd457e99fc61c1ce2f5a05ae59f5e12256a764
Change-Id: Iefdd457e99fc61c1ce2f5a05ae59f5e12256a764

- Update HintManager and its aidl types to use NDK backend
- Switch HintManager to using PowerHAL's WorkDuration
- Update SDK WorkDuration.java to no longer be parcelable,
    since it isn't being sent over binders anymore.
- Remove duplicate WorkDuration in powermanager in favor of PowerHAL's

Bug: 315894228
Test: atest HintManagerServiceTest
Test: atest PerformanceHintNativeTestCases
Test: atest PerformanceHintManagerTest
Change-Id: Ibc5a3aa96e73a225fce980811694ee02bdabb963

Causing the file to be missing on the system and so decoding of the proto messages is failing because we need to read this file to decode the messages to write the message to logcat when requested

Test: adb shell wm logging enable-text WM_DEBUG_WINDOW_TRANSITIONS
Bug: 327491675
Change-Id: Ic98187a0b5fe785eec8cec275c394fb2c68d4242

This reverts commit f9bdb797.

Reason for revert: cherry picker placed the change in incorrect place

Merged-In: Ie2ee7578352463aa42942c0b42b78557c414fb52
Change-Id: Ifda8252249402d4452a9629c79950f177ba5d9f2

Test: CI
Bug: 310504781
Merged-In: Ie2ee7578352463aa42942c0b42b78557c414fb52
Change-Id: Ibc0434bfa88108426c85a61fd9ddc7e7d3ac8868

ProtoLogTool now has additional parameters to support Perfetto tracing. We also need to generate and include a proto version of the viewer configuration.

Flag: ACONFIG android.tracing.Flags.perfettoProtolog DEVELOPMENT
Test: mp droid && atest FrameworksServicesTests
Bug: 276432490
Change-Id: I26929eed96faae04bec65ae5eaf86afda75cb83c

This reverts commit 2f858356.

Reason for revert: The original issue is fixed ag/26320339

Change-Id: I74bb8123fe90d82e3569a60fea44af13bcbd0f5f

This reverts commit 7aa2a3af.

Reason for revert: b/326075332

Change-Id: I0da1ac971619b22f34cb69432df1ef21d1c84c4a

This change create exported mode library for package
android.service.notification. This library should be used in not "system" container.

Bug: 322678979
Test: presubmit
Change-Id: If143142cbf005c29d318f2227807806556283145

Test: CI

Bug: 310504781
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:14459bf7e2f4b8a33655181b5f9092e745402809)
Merged-In: Ie2ee7578352463aa42942c0b42b78557c414fb52
Change-Id: Ie2ee7578352463aa42942c0b42b78557c414fb52

Test: CI

Bug: 310504781

Change-Id: Ie2ee7578352463aa42942c0b42b78557c414fb52

Adds to AltitudeConverter a method that returns a geoid height at the location (go/msat:geoid-heights-altitude-hal-design).

Note that the implementation uses *fake* assets for calculating expiration distances, specifically, a copy of the geoid height assets. Real assets will be added in followup CLs.

Test: FrameworksMockingServicesTests:AltitudeConverterTest
Bug: 304375846
Change-Id: I78bc3c9f9d814f750c38c627ee9af8dc27183e2a

This reverts commit 225bfb76.

Reason for revert: We are possibly losing tombstones

Change-Id: I8372ae3b7b5db63bc48155eca63eb3cae41239c8

Now that all the @hide usage of NFC API's from rest of platform is
cleaned out, we can now switch to the module defaults and continue the
separation of NFC API classes.

Bug: 303286040
Test: Compiles
Merged-In: I8bd5e38b1482600594c41660d14537cf15b48318

Change-Id: I8bd5e38b1482600594c41660d14537cf15b48318

Bug: 309630341
Test: atest CoreTracingTests
Change-Id: I9e9486ba406aa67fbc73922910ea97429ee4683c

NewApi is a lint check that you don't call framework methods that were
introduced in versions later than your min_sdk_version. We want to
make this an error, so we're baselineing all existing issues.

This cl was generated automatically, by taking all the NewApi issues
from the reference baselines, and all the non-NewApi issues from the
existing checked in baselines.

Flag: None
Bug: 268261262
Test: Presubmits
Change-Id: I26ca494d6089ac145eb5e3d267a9546eceea7c77

Now that all the @hide usage of NFC API's from rest of platform is
cleaned out, we can now switch to the module defaults and continue the
separation of NFC API classes.

Bug: 303286040
Test: Compiles
Change-Id: I8bd5e38b1482600594c41660d14537cf15b48318

The availability to wifi apex was done implicitly using a baseline map in
build/soong/apex/apex.go. Make this explicit in Android.bp

Bug: 281077552
Test: m nothing
Change-Id: I5c3fb582f290da2d5cedc65417ca126013941da5

Test: m framework-all
Test: Compiled and applied OTA using settings app using stable interface
m Settings && adb install -r $ANDROID_PRODUCT_OUT/system_ext/priv-app/Settings/Settings.apk
Bug: 317914533

Change-Id: I393df5218c60303dbea60386c680b75b553ddac2

8d8898c9

Test: atest BootReceiverTest
Bug: 296207744

Change-Id: Ib6e1a1d66a8cf402b26287b8960ad4a0acc11281

Test: launch_cvd
Bug: 218588089

Change-Id: Ifeb615dccbac68eb050c340bc8809cd07a89dc6f

lintable modules currently pick up files named "lint-baseline.xml" to use as the
lint baseline implicitly. This is confusing because you could end up using the
baseline files in more modules than intended. Lint also has a feature where it
requests you remove unnecessary findings from the baseline file, so something
could be necessary for one module, but unnecessary for another that accidentally
picked up the baseline.

We're removing the implicit detection of the baseline file, which requires
all modules using it to list the baseline file explicitly.

Bug: 272769514
Test: Presubmits
Change-Id: I4e74094eed3f5a0b7395bcb5e16cbee9f0f28b7e
Merged-In: I4e74094eed3f5a0b7395bcb5e16cbee9f0f28b7e

lintable modules currently pick up files named "lint-baseline.xml" to use as the
lint baseline implicitly. This is confusing because you could end up using the
baseline files in more modules than intended. Lint also has a feature where it
requests you remove unnecessary findings from the baseline file, so something
could be necessary for one module, but unnecessary for another that accidentally
picked up the baseline.

We're removing the implicit detection of the baseline file, which requires
all modules using it to list the baseline file explicitly.

Flag: None
Bug: 272769514
Test: Presubmits
Change-Id: I4e74094eed3f5a0b7395bcb5e16cbee9f0f28b7e

The `--api-lint-ignore-prefix` option adds a package prefix within
which API lint checks will be ignored. However, the options are
not actually necessary. That is because they are only used in the
`android-non-updatable-stubs-defaults` and the non updatable code does
not include any source classes from those packages.

While modules that do use `android-non-updatable-stubs-defaults` do
include classes from those packages on the classpath they are already
excluded from having API lint checks performed on them as they do not
contribute to the API surface being generated by those modules.

Bug: 311690008
Test: m checkapi
(cherry picked from https://android-review.git.corp.google.com/c/platform/frameworks/base/+/2880166)
Merged-In: Ife750c586edc2b5af92c0b5e9211b23345083f69
Change-Id: I202e4da20f6d77fd99d4f17f917327bea759e409

Bug: b/316620445
Test: atest CtsStrictJavaPackagesTestCases android.compat.sjp.cts.StrictJavaPackagesTest#testBootClasspathAndSystemServerClasspath_nonDuplicateClasses
Change-Id: Ia7aa29637799c380b4a8d6185b25ba107f016d97

Revert submission 2843682-tombstone-proto

Reason for revert: Android Go build break, b/316637921

Reverted changes: /q/submissionid:2843682-tombstone-proto

Change-Id: Ic9d7b73e97c070fc378becb59799268323d9cead

1. Map HIDL to AIDL fingerprint sensor configuration
2. Propagate that through FingerprintService and FingerprintProvider
3. Similar implementation for face sensors
4. Use only one provider

Test: atest FingerprintSensorConfigurationsTest
FaceSensorConfigurationsTest AuthServiceTest FaceServiceTest
FingerprintServiceTest FaceProviderTest FingerprintProviderTest
HidlToAidlSensorAdapterTest HidlToAidlSessionAdapterTest SensorTest
Bug: 303480396
bug: 303480830

Change-Id: I7a945e596c6331077e90cbe1500de0bcb212895c

Use the proto tombstone as source of truth and ignore the text
tombstone. Instead create the text tombstone by omitting the memory data
from the proto tombstone to save space on data that would get removed
anyway. This allows us to save bandwidth and avoid truncating useful
data from the tombstones.

Test: atest BootReceiverTest
Bug: 296207744

Change-Id: I809122d3206ce326cbbbceadb45c3b98b9762a3e

Bug: 312540064
Test: make framework
Change-Id: Ia27a2608ae05c1a9d033e52f8d0244c886163112

Test: atest BiometricContextproviderTest
Bug: 305284901
Change-Id: I3d00157b2b00048466d1e893a96ffa1c51a7a591

We would be moving these files to a new module.
Separating them to a new filegroup, which would be later moved to the
new module behind guarded by build flag when ready.

Bug: b/289203818
Test: m
Change-Id: I5275cf6d416fb74384eb2f0a66d3bcba50dd3fc4

Bug: 303286040
Test: Device boots up after flashing
Merged-In: Iad08614f0aa3b7bea12a1ad52debd0ee13302a8e

Change-Id: Iad08614f0aa3b7bea12a1ad52debd0ee13302a8e

Bug: 303286040
Test: Device boots up after flashing
Change-Id: Iad08614f0aa3b7bea12a1ad52debd0ee13302a8e