This rule was introduced in 2017 as a way to run unit tests in a continuous build target. We have better ways to achieve the same today.

Bug: 337281646
Bug: 332609042
Test: presubmit
Change-Id: Iba9934f39df2ebb883ded941d438b3528b3f29c2

Adds a flag behind which we add the new storage area API.

Bug: 325129836
Test: atest StorageAreaTest
Change-Id: I974477213015b215e60d2e23392638d674cc14c0

Change-Id: If2297ae7402a2eefee6ab0b5051dbf18e51af91f

Test: presubmit
Change-Id: Ie32c7af67c17e4ffee8d5ce1fc74aa184925b755

Adds a finalizer to the `LockscreenCredential` class, which calls
the `zeroize` method to zeroize the LSKF `byte[]`. This ensures that
`LockscreenCredential` objects that were not closed still have their
data wiped when they are garbage collected.

This is part of an effort to remove instances of the LSKF available
in a RAMdump.

Bug: 320392352
Test: atest com.android.server.locksettings
Change-Id: Id7f1f102cdaa182659e2632bdaf81bd2c46d0f86

Test: manual
Change-Id: Idd27c2b79455e0895aa73f268113a8aa873fd022

This CL clears a local variable `byte[]` storing a copy of the
LSKF, to avoid it being present in a RAMdump.

Bug: 320392352
Test: build
Change-Id: I3781ad8c0a15b7761820a21413cb870e01794c37

* Broaden jarjar Flags rules for NFC.  Note that this brings the NFC rules in line with other packages
* Opt classes named CustomFeatureFlags into Ravenwood

Flag: none
Bug: 336768870
Test: presubmit
Change-Id: Ib1e76ebd04915554f464ec9a3d101b07925e18be

1. Enabling "flag resets" behind aconfig flag
2. Mocking the above flag in Tests

Bug: 333720513
Test: atest RescuePartyTest
Change-Id: I87e82def65b01367dbb36c7324b91c36203f2409

lock.

Bug: 335096825
Change-Id: I86b36197d3220fcf7db0c01645497a11d38e7285

This is using the new pipeline in R8 for optimized shrinking.

This reduces apk size by 3.96% on phone and -12.47% on watch!

Bug: 296870300
Test: Existing
Flag: NONE
Change-Id: I3a509c6d6f22af1713827c0a59911b937dcfda64

Bug: 336058761
Bug: 333622829
Bug: 336058293
Test: android.mediav2.cts.CodecEncoderBlockModelMultiAccessUnitTest#testSimpleEncode
Test: android.mediav2.cts.CodecUnitTest$TestApi#testQueueInputBuffersInUnInitState

Change-Id: I4ce7fd2872ce3b4734050b68e5bf2c9b0519c898

Bug: 287618292
Test: TH
Change-Id: I15be72b31e1d26c2f38574c2f6b0af80a8b2c3f4
Merged-In: Id06f6a076db8fbe9dc5d4d17170f819f8f472bd5

Upgrading to clang-r522817's new libc++ requires that <mutex> be
included here.

Bug: 333165689
Test: treehugger
Flag: EXEMPT, fix build error
Change-Id: I14ff396b21feb4b569a3c8d967c8295a04005beb

This fixes a build failure that arise due to the fact that ART (profman) does not correctly handle profiles that contains a method descriptor where the method's class in the dex does not have any class data (neither fields nor methods).

This issue was fixed by aosp/3047152, but there is a checked in profman binary on some build targets (e.g., barbet-ap2a-userdebug), which does not have the fix.

The underlying issue is that the baseline profile of CredentialManager does not match the optimized dex created by R8. As a result of R8 optimizations, it is possible that there is a line "Lfoo/bar/Baz;->m()V" in the baseline profile and that the class foo.bar.Baz does not have any fields or methods after running R8, which triggers this build failure.

This is an issue in the build system and is tracked by b/335418838.

Bug: 335809645
Bug: 335777227
Bug: 335418838
Bug: 335209102
Test: manual

Change-Id: I8a44b1ec99bad8e9461c1a2a371f19de14f402aa

Merge "Remove mateuszc@google.com from libs/WindowManager/Shell/src/com/android/wm/shell/pip/OWNERS" into main

Merge "Remove mateuszc@google.com from libs/WindowManager/Shell/src/com/android/wm/shell/pip2/OWNERS" into main