While this offers minimal savings, there's no real reason to opt out of
optimization (the default for app targets).

Test: m + check APK diff
Bug: 203241149
Change-Id: Ib1bba31a95afa87f37aedb0251796bdb31ab65c0

Make sure we display the Intent extras as string, not spannable
char sequences.

Change-Id: Ifd08941179ee809ee038e25be9d92a283e7ab2cc
Fix: 197874968
Test: Launch SoundPicker with CharSequence intent extra

For some low-end or bad performance devices, sometimes keyguard
flingToHeight animation still not complete, at this moment if received
the onStartedWakingUp while try turn screen on, it will cause the
remote SystemUI keyguard dismiss transition can't run.

Before execute a fling animation of Keyguard, set the animation execution time to 0 determines that it is Screen Off state.
This solution makes Screen On can not affect animation.

Bug: 301196699
Test: run cts KeyguardTests

Change-Id: Ic7be1b5e41814adb44ce79857b79283040b4e3a4
Merged-In: I4743c0ad53f89ee2fdc2f8e9eed864fe79f3bfc3

For new Thread network APIs or shell command for only testing, a new
signature permission is deversed to protect them (so to distinguish them
from existing system APIs which are designed for privileged apps such as
GMS Core).

Bug: 329368792
Change-Id: I291989eb0e024614568044945726edc07e20b8be

Revert submission 3085486-cherrypicker-L33500030003548614:N45100030056225643

Reason for revert: Droidmonitor triggered revert due to build breakage in b/341363560. 

Reverted changes: /q/submissionid:3085486-cherrypicker-L33500030003548614:N45100030056225643

Change-Id: I08e6857f1dc2afe6f25e8ed757b641d44a639c4e

Revert submission 3085486-cherrypicker-L33500030003548614:N45100030056225643

Reason for revert: Droidmonitor triggered revert due to build breakage in b/341363560. 

Reverted changes: /q/submissionid:3085486-cherrypicker-L33500030003548614:N45100030056225643

Change-Id: I04e20626d5c410e4dfd8d41a141af50a4df426f3

In aosp/3020232, the intermediateLayout was removed, while
isMeasurementApproachComplete has been changed to
isMeasurementApproachInProgress.

Test: No new test
Bug: 332591722
Flag: NA
Merged-In: I3b33480980331b20f2e6e0f66f03b2e5dcda253b
Change-Id: I3b33480980331b20f2e6e0f66f03b2e5dcda253b

Bug: 332591722
Change-Id: I631210dc4e07980c0e68c96f4bdba749e8ccdda4
Merged-In: Ib7d69f64cd955c9069c47293810178b5cebe2099
Test: Presubmits
Flag: N/A

The 'mOneShot' should default to 'true' to prevent accidental activation of the sticky mode in the system.

Bug: 339788967
Test: adb shell am start-activity \
    -n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
    -a android.os.image.action.START_INSTALL \
    -d file:///storage/emulated/0/Download/system.raw.gz \
    --el KEY_SYSTEM_SIZE $(du -b system.raw|cut -f1) \
    --el KEY_USERDATA_SIZE 4294967296

Change-Id: Iad40d9923fa0680f6e8f37690bed817af2a19f04

Bug: 327599769
Test: atest com.android.settingslib.bluetooth.BluetoothLeBroadcastMetadataExtTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:6428ed9fb9f9f1873dede7963d86c3913522ab8d)
Merged-In: I57a0ddeef04c879750c9a1dd51452cf196c8c9ed
Change-Id: I57a0ddeef04c879750c9a1dd51452cf196c8c9ed

NOTE FOR REVIEWERS - errors occurred while applying the patch.
PLEASE REVIEW CAREFULLY.
Errors:
Error applying patch in packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothLeBroadcastMetadataExt.kt, hunk HunkHeader[311,7->311,7]: Hunk cannot be applied

Original patch:
 From 6428ed9f Mon Sep 17 00:00:00 2001
From: Rongxuan Liu <rongxuan@google.com>
Date: Wed, 06 Mar 2024 03:14:00 +0000
Subject: [PATCH] [Audiosharing] Fix address type usage in  QR code format if address not present

Bug: 327599769
Test: atest com.android.settingslib.bluetooth.BluetoothLeBroadcastMetadataExtTest
Change-Id: I57a0ddeef04c879750c9a1dd51452cf196c8c9ed
---

Bug: 324655158
Test: atest com.android.settingslib.bluetooth.BluetoothLeBroadcastMetadataExtTest
Test: manually tested with broadcast source and assistant by QR code
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4abfa5bed1a35a9a9b5ac54951296b3edde4ee9a)
Merged-In: I798666b89c4e3558c7528bace0346caf8218dc53
Change-Id: I798666b89c4e3558c7528bace0346caf8218dc53

Set the container field of aconfig flags

Test: printflags --format='{package}:{container}:' | grep "::"
Bug: 312769710
Flag: NONE
Change-Id: I84fda0d5e9813940609436d825738ff786908ff0

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: 287618292
Test: TH
Change-Id: I15be72b31e1d26c2f38574c2f6b0af80a8b2c3f4
Merged-In: Id06f6a076db8fbe9dc5d4d17170f819f8f472bd5

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

Bug: 309426522
Test: manual
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:9d5f70c8d3ca45447c3019bd934e338c05cef193)
Merged-In: I8905841cc46ba62099f44dbecf01c06869677bf5
Change-Id: I8905841cc46ba62099f44dbecf01c06869677bf5

Bug: 205124386
Change-Id: I4a96d41cee9b41ea9eaaa295e7a9bbef5b78cd12
Test: N/A

Fence of ParcelImage is ParcelFileDescriptor, when call getFd() to
get file descriptor of it, the file descriptor still be owned by
ParcelFileDescriptor, which cause fatal occurs when close the
file descriptor in Gralloc4Mapper.

Therefore, use detachFd() to get file descriptor of ParcelImage Fence.
When call detachFd() to get file descriptor of ParcelFileDescriptor,
the file descriptor will not be owned by ParcelFileDescriptor,
so the file descriptor can be closed normally in Gralloc4Mapper.

Bug: 334802005
Change-Id: I8388c913f967565d90eca80e6b1b8ccb09ab018e

This suggested change is automatically generated based on group
memberships and affiliations.
If this change is unnecessary or in error, vote CR -1 and the bot
will abandon it. Vote CR +1/2 to approve this change.

See the owner's recent activity for context:
https://android-review.googlesource.com/q/mateuszc@google.com

To report an issue, file a bug in the Infra>Codereview component.

Change-Id: Ib8c4b5ea538b70118bae049ae4ff6079052c0543

Fixed a system UI crash when clicking a notification to launch a PendingIntent with a user-created IIntentSender.

Change-Id: I4f55a12e8cc85f2d8b79e7076bc3f543280b5678

Unable to raise the SystemAPIs from the new place so moving it back.

Bug: 289203818
Test: atest CtsPackageWatchdogTestCases
Change-Id: Ia79f349c1e6addb083b0b5c7cac0276922d7c5db

This reverts commit d47fc309.

Reason for revert: Fixing the revert.
Change-Id: I73ab752c9469cd19778d822d59e7675656bb8854

This reverts commit 15ba5a90.

Reason for revert: Fixing the revert.

Change-Id: I962eb1c25f88d93a659d86d6fa138f324dbe5eb0

94058265

Change-Id: I847a3f5bd85879f02ddaa1d6043762121651ca31
Bug: 333155088

1df0ae18

Change-Id: I64489e569ab77585ab02b01872f64673e574b3ff
Bug: 333092549

This reverts commit 160cb21a.

Reason for revert: Need to move back files to original place.

Change-Id: I0e61db91e99b4a4bc76a34de76d0107195d80cab

This reverts commit 0f91c2b9.

Reason for revert: Need to move back files to original place.

Change-Id: Icb7ab9956f2b662dd918a6be3941e830f1e05002

Increasing the throttle duration to 24 hours from 10 min

Change-Id: Ibc8477394bd3a41f5f5614552e24d723bc2ee811
Test: TH
Bug: 296455962

Remove a greenpath log statement which prints 3x every 10s, filling logs

04-03 19:35:15.980  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:15.980  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:15.980  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:25.985  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:25.985  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:25.986  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:35.978  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:35.978  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled
04-03 19:35:35.978  2065  2065 D ShadeCarrierGroup: ignoring old pipeline callback because new mobile icon is enabled

Flag: None
Bug: 36785118
Test: manual
Change-Id: I465bde520d4e79e6e4e18ffb7dc109d36eacaa10
Signed-off-by: Neill Kapron <nkapron@google.com>

Since the bootloop is not for complete boot rather for  system-server
restarts, we dont have to be as conscious about performing higher
impact mitigations and we can perform them earlier. (Reboots
initiated by user doesnt trigger a bootloop scenario.)

Removed the increment boot count threshold needed between 2 mitigations.
Also removed BOOT_LOOP_THRESHOLD(default value: 15) which was needed to
perform any high impact mitigations.

PackageWatchdog would wait for DEFAULT_BOOT_LOOP_TRIGGER_COUNT (default
value: 5) after a reboot (ex: WARM_REBOOT step in rescue party, mainline
rollback). Changed the behaviour to wait for DEFAULT_BOOT_LOOP_TRIGGER_COUNT
only for first mitigation.

MitigationCount was not getting reset properly after de-escalation
window. Updated the logic to save mitigationCount to the file after reset.

Did manual tests by killing system_server process using the following
command:
`adb shell kill -9 $(adb shell pidof system_server)`
Verified that the first mitigation was performed at 5 restarts.
Every restart after that resulted in next mitigation being executed.

Ran `atest PackageEatcdogTest` to verify PackageWatchdogTest and
CrashRecoveryTest changes.

Test: Unit test, manual test
Bug: 291137901
Change-Id: Ia0174e0e5dca09c5d4e9d3a12909c5e5087b4dbf

This CL introduces a new "warning" callback on excessive binder
proxies, where if the total count of binder proxies from certain UID
goes above the threshold, the callback will be triggered. This is
very similar to the existing binder proxy high watermark callback.

We're logging this warning event into statsd, where it may trigger
perfetto dump, before it reaches to the high watermark and gets killed
because of that.

This callback signal could also be used as a hint to the GC in
the future, which could effectively release the references to
remote binder stubs.

(cherry-picked from ag/25078745)

Flag: ACONFIG log_excessive_binder_proxies DEVELOPMENT
Bug: 298263955
Test: atest FrameworksCoreTests:android.os.BinderProxyCountingTest
Merged-In: I3c959a7dd62ee57415c22a8034d774fe49a8f64f
Change-Id: I2eac629a1a63877adc432b23aae36d83a93c538e

skip_jarjar_repackage was used as a temporary solution
to system ui build time increase. Now the problem should
be resolved by moving jarjar actions before combine action
in java compile.

Test: CI
Bug: 328067025
Flag: NONE
Merged-In: I01136f7d00e13f258212885a52b11c1de34fd87a
Change-Id: I8c6c5b5834f842eaa29aafed431146967f1aa167

When you turn on the "Accessibility Menu shortcut" switch in settings,
it starts a service and creates a new A11yMenuOverlayLayout.

However, the layout is not set to null at the right time, causing the
A11yMenuOverlayLayout to be repeatedly created and leading to a memory
leak.

Change-Id: I2368a1bbbbe0159755859651ecf53831ac70db37
Signed-off-by: Jia Jia <jia.jia@zte.com.cn>

The androidx nodeps modules were an internal implementation detail,
they are being removed.  Replace the nodeps dependencies with the
non-nodeps versions.

Bug: 326265727
Test: builds
Flag: None
Change-Id: Ief6c23460c27c64eaf9220563316bdbcc5b8d86b

Bug: 298486662
Test: N/A - Build issue only
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4e6b43c890f3d91016a8159602f357f9be7c8e6e)
Merged-In: I809b0abef1a33d39082448f8d504ef54e0793da6
Change-Id: I809b0abef1a33d39082448f8d504ef54e0793da6

PackageWatchdog will apply high user impact actions only in case of
network failure.

RescueParty updated the list of rescue levels and their corresponding
impact.

Test: unit and manual tests
Bug: 310236690
Change-Id: Iff34f6051b801a0d45149c317a7c9f344a2bd984

Bug: 328275985
Test: ComplicationViewModelTransformerTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:472a4f234016895b2368355466cfe1e5ce16fcc9)
Merged-In: If12ce8b219143e6642a988bc3f1611412d420e5a
Change-Id: If12ce8b219143e6642a988bc3f1611412d420e5a

Bug: 328120273
Flag: NA
Test: m
Merged-In: Ia845ccffa84a11eeb13680fc7b19642e7f7444ad
Change-Id: Ia845ccffa84a11eeb13680fc7b19642e7f7444ad

Scope of isAttemptingFactoryReset method was updated to include both the
reboots that were triggered by RescueParty.
As it would be made an API, refactoring it to isRecoveryTriggeredReboot
which seems a better name with expanded scope.

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

Same three owners were being repeated at multiple places, having them at
central owner place and including that everywhere.

Bug: 289203818
Test: NA
Change-Id: Ic63f939e196fe5974eb5e4c31d7b2991eafac6cd