The newest version of `beto-rust` includes some updated error
handling. This CL adds explicit `throws` of these new errors in
`SecureChannel`.

Test: build
Change-Id: I6fff07a3666431f43adefa9632e69f2698d74561

Set the container field of aconfig flags

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

The package name was changed. Change the use-sites to reflect that.

Test: TreeHugger
Change-Id: I039d02f599692efd51ca8a3316338914eb30a3b9

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

when creating virtual devices. This breaks all our CTS
because the CDM shell doesn't accept device profiles,
so fixing this as well.

Bug: 315481938
Test: atest VirtualDeviceManagerBasicTest
Change-Id: I431a2e170d5ef485daa6fe06b424e699adb1f597

Bug: 315533814
Test: atest CtsVirtualDevicesSensorTestCases
Change-Id: I40499c5f1d6d37c82028f7c1131d84e2cc3314aa

Bug: 287269288
Test: CTS
Change-Id: I53d5ebcfba026aef86e70a0db6ff931754f5741c

Useful for other system services that already use
VDMInternal so they won't have to create a VDM instance.

Bug: 287269288
Test: presubmit
Change-Id: I827b54d1301514bc37efea3567bd2a7c36a46802

New VirtualDeviceParams.Builder#setInputMethodComponent API that
for now only updates a map in IMMS.

The custom VD IME cannot be changed during the device lifetime.

Bug: 287269288
Test: CTS
Change-Id: Iad2401d19482030fca072bdec48935c9b574d465

Bug: 309528663

Test: CTS
Change-Id: Id50517977e5f5fcd9806e2bf5b65e4d5cf87d0a9

Test: atest VirtualCameraControllerTest, CtsVirtualCameraTestCases
Bug: 310857519
Change-Id: I03526bbf5f993068a2f0555b2e553d5bbf61906f

Bug: N/A
Test: mm
Change-Id: I080b729ece0158d51b540f00fae1c89ab65d69d3

Useful for other system services that already use
VDMInternal so they won't have to create a VDM instance.

Bug: 287269288
Test: presubmit
Change-Id: I5f430834b48635613071cc78cda8bf3e30496b7c

- Add hidden API to get virtual camera id
- Avoid binder call inside VirtualCamera constructor
- Also, add CtsVirtualDevicesCameraTestCases to VDM
postsubmit

Test: atest CtsVirtualDevicesCameraTestCases
Bug: 310857519
Change-Id: Id8fcc802ae1561f2ffd5c38f763ee665364accde

There's no need to keep the non-VDM-related CDM associations.

Bug: n/a
Test: presubmit
Change-Id: Iba5efbafbc7fc857e6ffac3af4e3b22330e762fb

Bug: 310547345
Change-Id: I3f702495ec9877a3c2bbac0b4470baf512da26ed
Test: n/a

Bug: 300905478
Test: presubmit
Change-Id: I53df260bad1b20c217f358e8c9e6f1ec6fd6af5a

Test: presubmit
Bug: 295258915
Change-Id: Ifac4ea4563623f3bd7f0edd23b51ecaa03c07cba

Bug: 301023410
Test: atest virtual_camera_tests
Change-Id: I91c4b9d0f60b378620e968de8f0262082b4fb05c

Bug: 193583135

Test: m and CTS
Change-Id: I00f7c63ebb5f3b11b8a5ad2b29b03365c932d05a

Test: atest VirtualCameraControllerTest
Bug: 311349980
Change-Id: I1da91b52710b4eed343d3e4b66352b56b44ff56a

Reintroduce these two commands to revert the regression.

Test: cts
Bug: 307685323
Change-Id: I6daf0783810fcb92ebb57dd8bfc299008a9eb877

 - Do not crash when closing a closed input device
 - Do crash when the input device failed to be created
 - Log the device name when an event failed to be sent
 - Log the device name when closing the device
 - Remove redundant checks already covered in the configs
 - Add missing checks in the configs
 - Add missing API documentation

Fix: 306679262
Fix: 268457357
Test: CTS

Change-Id: Icbe521a7ba46c460d3b98286b2c4c05ce6e8e2c6

 - Single callback class for VirtualCamera
 - Update the virtual camera AIDL interface and parcelable to
   align with the planned API
 - Add interoperability between the client-server aidl and
   server-service aidl and update the related test

Test: atest VirtualCameraControllerTest
Bug: 270352264
Fixes: 302255544
API-Coverage-Bug: 310857520

Change-Id: I3ab768db277b5574d6fdb74b674d0500ffd6452e

 - return a non-null persistent id for the default device
 - Add overloads to CDM hidden APIs to get association info for all
   users
 - Maintain a list of all associations in VDMS
 - Add a VDMInternal listener for when a association that may create
   virtual devices is gone, so the persistent id is gone as well

Fix: 295258915
Fix: 282629983
Test: atest VirtualDeviceManagerServiceTest
Test: atest VirtualDeviceManagerBasicTest
Change-Id: I0d33c7242652ca49aa68e8d912bcc263a7e4a08b

Bug: 310547345
Change-Id: I64cc5ff6659dfa6875baa225227951d1d5f86eb4
Test: N/A

Test: manual
Bug: 292212199
Change-Id: I5f8c71660d4c979af468a7ee4bfd72da1d74aeb6

Context#getDeviceId is the correct way of identifying virtual devices
instead of relying on an associated display id.

Do not blanket ignore all vibration requests from UIDs that run on
virtual devices as these apps have no way of vibrating the default
device; they can now request default device context and trigger the
default device vibration.

Not handling ExternalVibration here. ExternalVibration passes invalid
deviceId, which tells VibrationSettings to apply the existing fallback
UID-based logic.

Bug: 249785241
Fix: 250568048
Test: presubmit
Test: manual with streamed app that triggers vibration
Change-Id: Ie0f6d96faa8480bfd8427680ff05bc60faad02e8

Fix: 306622082
Test: see CTS
Change-Id: I2d9f49cd6cb006a1733d064a3edbaba88cdf0970

For mutil user case, make sure the calling userid
matching the passing userid

Test: test it on sample app
Bug: 298635078
Change-Id: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a
Merged-In: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a

For mutil user case, make sure the calling userid
matching the passing userid

Test: test it on sample app
Bug: 298635078
Change-Id: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a
Merged-In: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a

For mutil user case, make sure the calling userid
matching the passing userid

Test: test it on sample app
Bug: 298635078
Change-Id: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a
Merged-In: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a

For mutil user case, make sure the calling userid
matching the passing userid

Test: test it on sample app
Bug: 298635078
Change-Id: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a
Merged-In: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a

Fix: 291740640
Test: manual
Change-Id: I19e28e30d97a7b1ffb99236c619068fde87583ee

This change also triggers connected display animation
every time a virtual device owned mirror display is added.

Flag: ACONFIG android.companion.virtual.flags.interactive_screen_mirror DEVELOPMENT
Test: atest SystemUITests
Bug: 292212199
Change-Id: I9bfd7f5e2923f18b963d0e71ed5ad03c687f0d42

- Allow VDM to create auto mirror virtual displays:
It would be up to the caller to pass the appropriate
flags to VirtualDevice#createVirtualDisplay to create
an auto-mirror virtual display, following the exact
semantics as DisplayManager#createVirtualDisplay, i.e.,
either pass VIRTUAL_DISPLAY_FLAG_AUTO_MIRROR explicitly
or pass VIRTUAL_DISPLAY_FLAG_PUBLIC, without
VIRTUAL_DISPLAY_FLAG_OWN_CONTENT_ONLY in either case.

- VDM supports mirroring only the default display, and
any mirror display is put into the default display group.

- Launching presentations or activities are not allowed
on any mirror display created by a virtual device.

- VIRTUAL_DISPLAY_ALWAYS_UNLOCKED flag is not set for
any mirror display.

Test: atest DisplayManagerServiceTest, VirtualDeviceManagerServiceTest
Bug: 292212199
Change-Id: I3f65f1f19bd44aba278531308822c05da956f700

Bug: 307297730
Test: manual
Change-Id: I8112f6c2e615f512d1894f08125253414ea010f7

Flag has been rolled out to next. Testing has concluded. The flag + the
flagged code can be removed.

Test: N/A
Bug: 297220822
Change-Id: I0cb0782cccd18d6d858b5971115ac53f4094ebed

For mutil user case, make sure the calling userid
matching the passing userid

Test: test it on sample app
Bug: 298635078
Change-Id: I6c478ebcc1d981faf2d125a4b41909c3b6a30a2a

Currently, we seem to update the virtual mouse pointer display id in
InputManager only during mouse creation/destruction. This doesn't work
if we have multiple mice, each associated with a different display.
Hence, we update the virtual mouse pointer display id in InputManager
based on which virtual mouse is currently being used.

Test: atest VirtualMouseTest
Bug: 302121028
Change-Id: I36dbb7b0eacfbef1a30ef7e088f28e4e3e1cdaa1