Use this page as the table of contents for the BlueZ profile validation guides. Each profile page contains the
bluetoothctl, obexctl, and D-Bus commands needed to check one implemented or prepared Bluetooth workflow on an AGL target.
Start with GAP because every profile depends on a working adapter, discovery, pairing, and trust flow. Then run the profile guides that match the feature being implemented or tested.
Implemented profile guides#
- Profile GAP: adapter power, discovery, pairing, trust, bonded-device listing, removal, and discoverable mode.
- Profile A2DP: Bluetooth media audio connection, BlueZ media transport state, and PipeWire routing checks.
- Profile HFP: hands-free call control through PipeWire telephony when the target image supports it.
-
Profile PBAP: phone book access through BlueZ OBEX and
obexctl. -
Profile MAP: message access through BlueZ OBEX and
obexctl.
Related setup guides#
-
Install OBEX on Yocto: add
obexctland the BlueZ OBEX daemon to an AGL/Yocto image for PBAP and MAP testing. -
Remote D-Bus Inspection: forward a target system bus socket to a PC for inspection with
busctlor D-Spy.
References#
- BlueZ Adapter API: Adapter API
- BlueZ Device API: Device API
- BlueZ Media API: Media API
- BlueZ OBEX API: OBEX API