Test: manual with pre-upload.py
Change-Id: I42876cc232115d07d6b9f2131df5b43f8698738a
Bug: 262605980

Bug: 279502784
Test: TreeHugger
Change-Id: I80939a57d48a00f542bb468555c75a1d7b740f02

* changes:
  Kotlinify the BluetoothService use of getter
  Migrate BluetoothService to kotlin
  Move "java" to "src" for incoming kotlin file
  Extract Change-ids from BMS
  Add apex rules to default
  Typo in clang-format

Use cached values rather than fresh values from controller to output dumpsys to manage lifecycle issues during shutdown

Bug: 273912385
Test: net_test_main_shim64

Change-Id: I43272e6f9f1bf5955767407893caf75a7da327d3

Player settings commands and notification will only be available if the user
initializes AVRCP service with implementation of Player Settings
Interface as it is currently done in JNI layer.

Test: atest AvrcpDeviceTest
Test: manual running floss tests
Bug: 279194432
Change-Id: Idec5b73cf58b367d3c8084f7ffd34c0dc6d51eea

These file were push by mistak in the same CL as the whole project.
Any editing with IDE is updating them and they appear in the updated
change to be add to git, even when ignored (since they are already
present in the tree).

Test: No-op change
Bug: 262605980
Change-Id: I671d4538c6df55d1856aa9e9c89d8fe758e3a1db

Test: avatar run --mobly-std-log --include-filter 'ASHATest'
Bug: 254077091

Change-Id: I4d9402270057d9402386117af5f8f756b4665460

1. add more context support that are supported  in bt stack
2. support update metadata to re-write the metadata setting during
   stream, and contain the information in the file title

Bug: 279356092
Test: verified with sw path audio dump
Change-Id: I93d1c2e71fbe9d3c54483c547b946ca2a3981480

Bug: 277769899
Change-Id: If80901880d3d4051204be1f039ac02bd239d185b
Test: None

Bug: 262605980
Test: No-op on code. Build
Change-Id: Ie70cdfe83cea4fe5998f41541aa2ef406a2f89b2

Bug: 262605980
Test: No-op on code. Build + boot
Change-Id: I08b1e381a14db36d33e9115660fda75c5a6d0aea

Test: Build service-bluetooth + bt apex
Bug: 262605980
Change-Id: Id2d1f2d2a8b1c48b938108ea915529f253f47176

This allow the platform_compat_config to no longer parse the whole
library.
This follow the pattern used in the Bluetooth app.

Test: No-op change
Bug: 262605980
Change-Id: Ib057df8e0ebdfa50ffeff4896d11920ea2a9f36e

Bug: 262605980
Test: Build
Change-Id: I606c3343483d5bd92583380cb332452811405890

Test: git clang-format
Bug: 262605980
Change-Id: I1c0e5dd9c1b8b25e8a38e269eca3cf50754d754d

Test: TreeHugger
Bug: 279502784
Change-Id: I1a726a4a0b7e7fd7786580337a3845701bdf3317

1. The previous version only support ATT packet parsing. Add the mechanism to get the cid for EATT, and filter the EATT packet to get the codec information
2. Modify the lint error together

Bug: 279356092
Test: verified with EATT supported headset via SW path audio dump
Change-Id: I46d18fbc3236857fe1710980c76e4dda47af3462

Problem: It was found that several AVRCP Controller functions would
allocate transaction labels without setting transaction timeouts. This
would cause labels to leak if something went wrong, either in lower
levels of code, or on the remote device. Once our device leaked enough
labels, we could no longer allocate labels for operations, which would
render the connection effectively useless

Solution: We previously added debugging to check which transaction types
were leaking labels. We've used those results with careful code review
to refactor the transaction label code so its much harder to leak
labels. First, context was added to get_transaction, which enables us to
better track which transactions have which labels. Second, the various
build_and_send_* commands now *all* start transaction timers for their
outgoing commands. This means Vendor, Passthrough, and Browsing all have
command timeouts, instead of just Vendor commands. Third, the
transaction timer/timeout code path has been unified into one timer.
Callbacks for browse timeout events have been added as well, so that
upper layers know when something has gone wrong.

Bug: 272585347
Test: Connect a recent device and browse, look at transaction labels in
logs and dumpsys

Change-Id: Ieb73aee5532c06f79265e204e739d8e15c153ae2

Bug: 269973219
Test: manual testing
Change-Id: I744da162270838f3d5329170c0006ed67854b4f0

Factorise code to have only one place to delay critical callback

Bug: 269973219
Test: manual testing
Change-Id: Ic4f89b6444a1f6c245e2b3f8f4d5de5e33327ad2

* changes:
  RootCanal: Remove the legacy authentication code
  RootCanal: Cleanup build declarations in CMakeLists.txt