Bug: NA
Test: NA

Change-Id: Id40751c8eaaae76a8391de6b3eef60ac38b48d86

Use the size of limitSurfaceSize to set the window

Bug: 339763174
Test: 1. set the property:
	    [ro.surface_flinger.max_graphics_height]: [1080]
    	[ro.surface_flinger.max_graphics_width]: [1920]
    2. Repeatedly Turn on/off while connecting to 4K TV and check the boot animation
Change-Id: I378aab715d75b8ddb47068cb0e81503d83339021

Test: presubmit
Change-Id: I4472fcf8140a8a9bceaff6b3c5a7abf6bc8df69e

Noticed that Rollback reason during boot loop was getting logged and
unknown because of a missing reason to string map. Updated that.

Test: manual
Bug: 291137901
Change-Id: I2ea6206d07099a413aeeca464e0d1ebd97c04840

Package name is more commonly used than appid, so we hope to support obtaining permission and appop status based on package name.

Change-Id: I4f0e9bcb979132d99222cadaf306034bf58e092a

Change-Id: I77f267228b8e9d83a6726aa25351a59cd06634b0
Bug: 335068579

Add notes to indicate that developer is responsible for validating data files picked through a file picker on WebView.

Bug: 309408775
Change-Id: Iefae7f325f5457461dd91c87c3dd2a7eee22ad36

Disable flags in old test, these could be removed during flag cleanup

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

Bug: 29055299
Test: manual
Change-Id: I4f821acb298f8d74d17afd0db7ba4eb7729620d2

Merge "Add pdwilliams to WM owners (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0ddb53602dee5c5b1d3408e7bda7c09743bda23a) Merged-In: I44ff4c3f3a68cfbfe85cbb7017a6291f0c5ff9d8 Change-Id: I44ff4c3f3a68cfbfe85cbb7017a6291f0c5ff9d8" into main

(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0ddb53602dee5c5b1d3408e7bda7c09743bda23a)
Merged-In: I44ff4c3f3a68cfbfe85cbb7017a6291f0c5ff9d8
Change-Id: I44ff4c3f3a68cfbfe85cbb7017a6291f0c5ff9d8

Bug: 232711049
Change-Id: I3888fdbc45d283d6444e302bb44b098e3c4f5c59
Test: Compiles

Require VCN to be used by a "main user" instead of a "system user"
since "system user" will no longer be a full user on HSUM devices

Bug: 310310661
Test: FrameworksVcnTests, CtsVcnTestCases on non-hsum and hsum devices
Flag: android.net.vcn.enforce_main_user
Change-Id: I5abfa7ba82055cd953083b1ab3f83e61bafd8a55

Audioservice register content observer for MASTER_BALANCE/MONO at the time of initialization/boot up. Registration by default is only applicable for current user which in this case is primary user.
So even when audio balance/mono changes for secondary user, the callback
won't be received in audioservice and hence the settings update won't
have any effect on the audio output.

Bug: 339131898
Test: manual
- Validated that audio output balance and mono varies based on the settings in the secondary user
- atest AudioManagerTest
- atest AudioServiceTest

Change-Id: Ifce17d23e0dd0af61d6e27de7c7da629e9480e77

So far, we have used `instalable: false` to avoid collision with the
other modules that are installed to the same path. A typical example was
<foo> and <foo>.microdroid. The latter is a modified version of the
former for the inclusion of the microdroid image. They however both have
the same instalation path (ex: system/bin) and stem (ex: foo) so that we
can reference them using the same path regardless of whether we are in
Android or microdroid.

However, the use of `installable: false` for the purpose is actually
incorrect, because `installable: false` also means, obviously, "this
module shouldn't be installed". The only reason this incorrect way has
worked is simply because packaging modules (ex: android_filesystem)
didn't respect the property when gathering the modules.

As packaging modules are now fixed to respect `installable: false`, we
need a correct way of avoiding the collision. `no_full_install: true` is
it.

If a module has this property set to true, it is never installed to the
full instal path like out/target/product/<partition>/... It can be
installed only via packaging modules.

Bug: 335369205
Bug: 337993945
Test: m droid aosp_cf_system_x86_64
Change-Id: If9c053968bde39c3eb3b852f1df1d475161bd846

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