This constructor is never called and was implicitly deleted.
Build flag is throwing a error when building for host

Test: atest --host with OS_GENERIC defined
Change-Id: Ic807687181f7f732dff0dfce2e6643686f2134d0

* changes:
  pdl: Update getter names as per C-GETTER
  pdl: Use ‘bytes’ crate to read scalars
  pdl: Let UPDATE_SNAPSHOTS create new snapshots
  pdl: Simplify the generation of unit tests

Bug: 262654461
Test: gd/cert/run
Tag: #refactor

Change-Id: I4d94ce76a2cf36fb4d30638793c5e0ee3073dbd4

In addition to the memory contents, the info of being nullptr is used

Bug: 262654461
Test: gd/cert/run
Tag: #refactor

Change-Id: I1bc07daedcf270c56c86da6de503e6223464462e

Also add Myles to service

Test: no
Change-Id: Ia1bb5bc0e9e1caa693b0e1b3a86b2bb3570b9e43

The Rust API Guidelines say that getters should not be prefixed with
‘get_’ in most cases[1].

[1]: https://rust-lang.github.io/api-guidelines/naming.html#getter-names-follow-rust-convention-c-getter

Test: atest pdl_rust_generator_tests_{le,be} pdl_tests
Change-Id: If47c2f032b57075e17f803ae036ea5fb435afad3

Before we parsed the scalars by hand by tracking an offset and picking
out individual byte indices. Now we delegate this to the bytes crate.
This simplifies the generated code significantly (the bytes crate was
already a dependency of the generated code).

Test: atest pdl_tests pdl_rust_generator_tests_{le,be}
Change-Id: Ifa6f822df6aba06bcf13b8694ea182d7f1cfac1d

Bug: 257972065
Test: gd/cert/run
Tag: #refactor
BYPASS_LONG_LINES_REASON: Bluetooth likes 120 lines

Change-Id: Id35f66dbb3f852b95783ae0e05ea970c3e1749b4

* changes:
  Add test for BassClientStateMachine#Connecting
  Add test for BassClientStateMachine#Disconnected

Added opp.py file
Updated _android.proto and AndroidInternal.kt files
Added AcceptIncomingFile function in AndroidInternal.kt using uiautomator.

Test: atest pts-bot:OPP -v
Change-Id: If2ab94f8033035ddf7b40a1a5acdc58b8f272acc

Bug: 237467631
Test: atest MessageTest
Change-Id: If287e7eeaaaf870ebe87c0155c2f4dc3ed2687e2

Updated Host.kt file

bluetoothAdapter.clearBluetooth() performs bluetooth config clear and reset bluetooth. Hence no need to call rebootBluetooth().
Increased factoryReset timeout from 10 to 30.

Test: atest pts-bot:AVCTP -v
Change-Id: Id3dd6addd6f2e725d00401dd82406d7693149555

Bug: 237467631
Test: atest BluetoothInstrumentationTests
Change-Id: I3bca6240a43afed735cc84d99e9c5affd44f7880

Bug: 261213459
Test: gd/cert/run
Tag: #refactor
BYPASS_LONG_LINES_REASON: Bluetooth likes 120 lines

Change-Id: Ibdbb1dfa29c2e333e80d53ce99eff1f650984e36

This semaphore was the last one being used directly by the stack. It
cause some test failure when using mock and we do not wish to keep it.

Test: atest net_test_btif_stack
Change-Id: I71f4ee5a235e190fe1d988967b9989de9f3d0916

Disable and enable are async shell command.
This is creating flakyness in test that expect the bluetooth to be
already enabled / disabled.

Test: atest BluetoothInstrumentationTests
Test: atest BluetoothShellCommandTest
Test: atest 'BluetoothTest#AdapterEnableDisable' // net_test_bluetooth
Fix: 261772749
Tag: #refactor
Change-Id: I3ca29dde23a5182ede28eceaf1ac97e4668ab5d5

Initialize attribute value to zero properly. Executing on x86 is filling
it with garbage value causing the test to fail.

Test: atest GattCacheTest#stored_attribute_to_binary_descriptor_test --
--abi x86
Bug: 262348171
Tag: #refactor

Change-Id: I519c116e1d5eaeff778f68c9715e54292e46b1db