3bebb903

Change-Id: I605177fabae80ea68399aa42a66419119cf02cd3
Bug: 343583446
Bug: 343690533

This reverts commit ec7f7207.

Reason for revert: Fixed tests

Change-Id: Iadd0ea6f09f7f3159f94489c03f28c326bbbb664

This reverts commit 831334bd.

Reason for revert: Droidmonitor triggered revert due to b/341375758.

Change-Id: I9aaf3e0bca1d173ea7f449339185db5ace780626

In case of crash loops with a short time mainline rollbacks don't finish before the next mitigation which is warm reboot.

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

The lambdas that ManifestFixer::BuildRules attach to XmlActionExecutor
outlive ManifestFixer::BuildRules, so they need to capture diag
by-value instead of by-reference.

Bug: 339119172
Test: aapt2_tests
Change-Id: I6b9b6a8733875247a5be12111413b45b99727e1f

This change makes sure that the consecutive delimiters at the
beginning of the just refilled buffer are consumed.

Previously, if there were consecutive delimiters at the beginning
of the just refilled buffer, they were not being consumed and were
causing parsing errors. This was also causing fatal exceptions.

```
04-22 12:37:53.077   607   707 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: CachedAppOptimizerThread
04-22 12:37:53.077   607   707 E AndroidRuntime: java.lang.NumberFormatException: invalid long: READ
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.invalidLong(ProcFileReader.java:238)
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.parseAndConsumeLong(ProcFileReader.java:220)
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.nextLong(ProcFileReader.java:183)
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.nextLong(ProcFileReader.java:172)
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.util.ProcFileReader.nextInt(ProcFileReader.java:246)
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.internal.os.ProcLocksReader.handleBlockingFileLocks(ProcLocksReader.java:111)
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at com.android.server.am.CachedAppOptimizer$FreezeHandler.handleMessage(CachedAppOptimizer.java:2267)
04-22 12:37:53.077   607   707 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:107)
04-22 12
```

Bug: 336208153
Bug: 338416108
Bug: 331988929
Test: atest --host-unit-test-only -c  ProcFileReaderTest
Change-Id: I12813fa204d53d53687ffe6e8e3c0a85595b7e25

Allow disabling detector for better configurability

Bug: 336638836
Test: atest FrameworksVcnTests(new tests) && atest CtsVcnTestCases
Flag: android.net.vcn.allow_disable_ipsec_loss_detector
Change-Id: Icd7183d12fb287399a500ea9c0ee4125c749275c

This is imported from material icon at https://fonts.corp.google.com/icons?selected=Google%20Symbols%3Athread_logo%3AFILL%400%3Bwght%40400%3BGRAD%400%3Bopsz%4024

But system notifications and settings also need to use this icon. For
example, it will be used in Settings > Connected devices > Connection preferences.

Bug: 327583301
Change-Id: I08ef9c90b7d4085f9b901b3d9c41b57258aa9680

Fixed end point correctional animation for cell to cell animations
during lock pattern drawing.

In the lock pattern view, cells have an area of slop around them to
allow for drawing the pattern without hitting the exact center of cells.

When a cell is hit, the end point of the line drawn between that cell
and the previous is adjusted with an animation from the hit coordinate
and the exact center of the cell.

With LockPatternView_keepDotActivated set to true, cell animations for
the previous cell are recreated when a new cell is hit to allow changing
how a cells color is updated as the pattern is drawn.

This caused a glitch where the starting position of the end point
correcting animation for said previous cell would be recreated with the
current finger position coordinate, making it jump ahead to be closer to
the current latest cell, and animating back towards the target.

This fix makes the animation instead continue from where it was last, in
the case where the animation is recreated.

Test: manual, set a short, tight lock pattern, and try it in rapid
motion.
Bug: 328088937

Change-Id: Id445266cbc834fec7a514dbb227557f2ceae9dba

* changes:
  [Audiosharing] Fix address type usage in  QR code format if address not present
  [Audiosharing] Update QR code format to follow BT SIG standard

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

Bug: 338661733
Change-Id: I04ce021ef7838f0574875359daeb8c765d5f6a09

Summary:Add a call to `jobFinished` after processing completes to ensure that the system is notified
that the work has been completed.

Test: Run `adb shell cmd jobscheduler run -f android 260817` multiple times in succession. Verify that processing is now triggered each time.

Tags:
Change-Id: Ifa6fcd8b2fdcea4904677bcae4a1cb36cac33154
Signed-off-by: Abhishek Gadewar <abhishekgadewar@meta.com>

Flag: NONE
Test: n/a
Bug: 338178020
Change-Id: I6494166c24d37d398d72b05a9d7b3f966f3b9ffa

Set the container field of aconfig flags

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

This CL still keep PRODUCT_COPY_FILE for the original system image
packaging for Make, but create 3 soong's modules which could be used for
soong generated system images.

Bug: 337993945
Test: lunch aosp_cf_x86_64_only_phone-trunk_staging-userdebug ;\
      m aosp_cf_system_x86_64 ; m
Test: lunch yukawa-trunk_staging-userdebug ; m
Change-Id: Ie749de99273f85623861a001e69a9c4187cc8067

Previously, APIs from updatable modules and information about the SDK
extensions was only included in `api_versions_public` and
`api_versions_system`. This change adds the following two modules:
* `api_versions_module_lib_complete`
* `api_versions_system_server_complete`

It did not change `api_versions_module_lib` or
`api_versions_system_server` because Android Lint requires that they do
not include information about APIs from updatable modules because
otherwise it will report calls within a module as it has no way to
determine whether a call crosses an API boundary or not.

Bug: 336993217
Test: TARGETS=$(for i in public system module-lib module-lib-complete system-server-complete; do U=$(echo $i | sed "s|-|_|g"); echo "out/target/common/obj/PACKAGING/api_versions_${U}_generated-api-versions.xml"; done)
      m $TARGETS; mkdir -p before; cp $TARGETS before
      m $TARGETS; mkdir -p after; cp $TARGETS after
      meld before after
      # Review differences.
Change-Id: Ia542fbdc517fb223a0488f0e3f81b8727cb204e4

This reverts commit fd803f55.

Reason for revert: This change break most of the tv targets. Please test building cf_x86_tv_gtv

Bug: 338497361
Change-Id: I5e9063f3099315de4ec6bde966bf8563f5faac56

Bug: 337174893
Test: manual, connect to paired but just factory reseted headset
Flag: EXEMPT, xml file change
Change-Id: I3ff5698f896b7b8caee02bf2d5f7b398c6fad418