Acquire transport file descriptor and the MTU for read and write respectively.

Possible Errors:

Acquire transport file descriptor only if the transport is in "pending" state at the time the message is received by BlueZ. Otherwise no request will be sent to the remote device and the function will just fail with org.bluez.Error.NotAvailable.

Possible Errors:

Releases file descriptor.

Applicable only for transports created by a broadcast sink. This moves the transport from 'idle' to 'broadcasting'. This allows the user to select which BISes he wishes to sync to via a 2 step process: 1) the user calls the method, changing the transport's state to broadcasting 2) the audio server detects that the transport is in the 'broadcasting' state and automatically acquires it

Possible Errors:

Applicable only for transports created by a broadcast sink. This moves the transport from 'broadcasting' or 'active' to 'idle'. This allows the user to terminate the sync to a BIS to via a 2 step process: 1) the user calls this method, changing the transport's state to idle 2) the audio server detects this event and releases the transport

Possible Errors:

Device object which the transport is connected to.

UUID of the profile which the transport is for.

Assigned number of codec that the transport support. The values should match the profile specification which is indicated by the UUID.

Configuration blob, it is used as it is so the size and byte order must match.

Indicates the state of the transport. Possible values are:

Transport delay in 1/10 of millisecond, this property is only writeable when the transport corresponds to a sink endpoint and it was acquired by the sender.

Indicates volume level of the transport, this property is only writeable when the transport was acquired by the sender.

Possible Values: 0-127

Endpoint object which the transport is associated with.

Indicates transport Audio Location.

Indicates transport Metadata.

Linked transport objects which the transport is associated with.

For a Broadcast Sink, the BIG sync procedure requires all desired streams to be enumerated from the start and it cannot be later reconfigured by adding or removing BISes. To avoid terminating and recreating the BIG sync everytime a new transport is selected for acquire, all transports selected via Transport.Select need to be linked together. When the first transport is acquired via Transport.Acquire, all links are included in the BIG sync command. An acquired transport will create and set fds for all its links. Then, each link needs to be acquired separately, to get the fd and start receiving audio.

Only present when QoS is configured.

Possible values for Unicast:

Possible values for Broadcast:

Possible values for both Unicast and Broadcast: