• A2DP packet priority used in AudioDirectionExt. NORMAL should be used whenever audio is not streaming, and SOURCE/SINK should match the direction audio is being streamed.
  • Audio Priority Direction extension. Used to put the channel in a mode where A2DP packets are prioritized over other packets in the source or sink direction.
  • Protocol representing the controller actively encoding offloaded audio to or from this channel. Closing the protocol will stop the encoding, which can also be done using the Stop() if synchronization is required. If the controller fails to start audio offloading, an epitaph will be sent when this is closed.
  • Audio Offload Extension. Used to retrieve offloading capability and supported features.
  • Audio offload features used in AudioOffloadExt.
  • Used to specify preferred and accepted L2CAP channel modes. If the peer rejects a non-BASIC mode, the Bluetooth system will attempt to open the channel in BASIC mode instead. For a description of each mode, see Bluetooth Spec v5.2, Vol 3, Part A, Sec 2.4.
  • The channel and relevant parameters for a connection.
  • Represents a service which is registered by this profile. Closing this protocol will remove the service registration.
  • A DataElement is one element in a SDP record. SDP attributes and other parameters are expresssed in DataElements.
  • Indicates the audio transport that should be used for the data on a synchronous connection.
  • Codec parameter sets defined in the Hands-Free Profile specification (v1.8, section 5.7).
  • L2CAP Parameters Extension. Used to configure L2CAP channel parameters on an open channel.
  • MockPeer provides an interface for managing the lifetime of a mock peer in the piconet. Dropping MockPeer will unregister the peer from the Profile Test Server database.
  • PeerObserver provides the integration test client with a way to validate the behavior of a peer in the piconet. Dropping PeerObserver will stop any subsequent updates for the peer.
  • Service provides Bluetooth BR/EDR profiles a way to register a service definition, making a profile discoverable by peers. Registered services can receive L2CAP connections made to the advertised records, and can open new connections on peers.
  • The ProfileTest interface should be used to validate behavior of Bluetooth Profiles that use the [fuchsia.bluetooth.bredr.Profile] service.
  • Defined Protocol Identifiers for the Protocol Descriptor We intentionally omit deprecated profile identifiers. From Bluetooth Assigned Numbers:
  • Inbound SCO data has a RxPacketStatus that indicates possible data loss or corruption.
  • Represents an active synchronous connection request by a profile. Either Connected() or Error() will be called and then server will close the protocol.
  • Represents an active search which can produce results when peers are connected. Closing this protocol will result in the associated search not being performed on new connected peers.
  • Identifiers that are valid for Bluetooth Classes / Profiles. We intentionally omit classes and profile IDs that are unsupported, deprecated, or reserved for use by Fuchsia Bluetooth. These numbers are sourced from the Bluetooth Assigned Numbers for SDP.



Type Aliases§