
{"id":9864,"date":"2022-06-21T09:10:25","date_gmt":"2022-06-21T09:10:25","guid":{"rendered":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/documentation\/rdk_video_documentation\/components\/open-sourced_components\/bluetooth_bt\/"},"modified":"2026-11-19T10:29:49","modified_gmt":"2026-11-19T10:29:49","slug":"bluetooth_bt","status":"publish","type":"page","link":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/","title":{"rendered":"Bluetooth (BT)"},"content":{"rendered":"\n<p><code>btr-core<\/code> is a C library that implements the Bluetooth HAL for RDK middleware. It provides a software abstraction layer that interfaces with the BlueZ Bluetooth stack through DBus, isolating callers from BlueZ version differences and DBus protocol details. The library is not a standalone daemon; it is linked into a host process \u2014 the RDK Bluetooth Manager (<code>btmgr<\/code>) middleware component \u2014 that initializes it to obtain a handle and drives event handling through registered callbacks.<\/p>\n\n\n\n<p><code>btr-core<\/code> exposes APIs for adapter lifecycle, device discovery, pairing, connection, audio\/video media session management (A2DP\/AVRCP), and Bluetooth Low Energy (GATT) operations. It supports multiple adapters, a pool of paired devices, and a larger set of concurrently scanned devices.<\/p>\n\n\n\n<p>Internally, the library coordinates adapter and device state through a central module, using decoupled event queues to separate BlueZ signal dispatch from host-process callback delivery. Dedicated sub-modules handle AV media (A2DP\/AVRCP\/HFP) and Low Energy\/GATT operations. A transport-abstraction layer isolates the rest of the library from the specific DBus binding in use.<\/p>\n\n\n\n<div class=\"wp-block-merpress-mermaidjs diagram-source-mermaid\"><pre class=\"mermaid\">flowchart LR\n\nclassDef RDKMW stroke:#75D701,fill:#F1FFE6,stroke-width:2px;\nclassDef VL stroke:#808080,fill:#F2F2F2,stroke-width:2px;\n\nsubgraph RDKMW[\"RDK Core Middleware\"]\n    BtMgr[\"Bluetooth Manager (btmgr)\\n(host process)\"]\n    BTRCore[\"btr-core library\\n(BTRCore API)\"]\n    BtIfce[\"Bt-Ifce\\n(DBus \/ GDBus abstraction)\"]\nend\n\nsubgraph VL[\"Vendor Layer\"]\n    BlueZ[\"BlueZ daemon\\n(bluetoothd)\"]\n    Kernel[\"Kernel BT modules\"]\nend\n\nBtMgr -->|API Calls| BTRCore\nBTRCore --> BtIfce\nBtIfce -->|DBus \/ GDBus method calls| BlueZ\nBlueZ --> Kernel\nBlueZ -->|DBus signals \/ replies| BtIfce\nBtIfce -->|callbacks| BTRCore\nBTRCore -->|Callbacks| BtMgr<\/pre><\/div>\n\n\n\n<p><strong>Key Features &amp; Responsibilities:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Adapter management<\/strong>: Provides APIs to enumerate, select, power on\/off, rename, enable discoverable state, reset, and query version information for Bluetooth adapters.<\/li>\n\n\n\n<li><strong>Device discovery, pairing, and connection<\/strong>: Supports scanning for nearby devices, pairing and unpairing, and managing the full connection lifecycle for both classic and LE devices.<\/li>\n\n\n\n<li><strong>A\/V media session management<\/strong>: Handles A2DP sink\/source and HFP media endpoint registration, codec negotiation (SBC, MPEG, AAC), AVRCP transport paths, and media player metadata and control commands.<\/li>\n\n\n\n<li><strong>Bluetooth Low Energy (GATT)<\/strong>: Manages GATT profile hierarchies, LE advertisement registration and release, GATT read\/write\/notify operations, and OTA firmware transfer.<\/li>\n\n\n\n<li><strong>Battery level monitoring<\/strong>: Periodically polls battery levels for connected devices and delivers low-battery threshold notifications to the host process.<\/li>\n\n\n\n<li><strong>Callback-based event dispatch<\/strong>: Delivers device discovery, status, media, connection intimation, and connection authorization events to the host process through registered callbacks, without blocking the BlueZ DBus dispatch path.<\/li>\n\n\n\n<li><strong>Telemetry integration<\/strong>: Reports Bluetooth events to the platform telemetry service via T2 markers.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Design<\/h2>\n\n\n\n<p>The library is structured as a three-layer stack: the <code>BTRCore<\/code> API layer in <code>btrCore.c<\/code>, a sub-module layer (<code>btrCore_avMedia<\/code>, <code>btrCore_le<\/code>), and a transport-abstraction layer (<code>Bt-Ifce<\/code>). The top layer maintains all device and adapter state in the opaque <code>stBTRCoreHdl<\/code> structure allocated at <code>BTRCore_Init()<\/code>. Incoming DBus\/GDBus events from BlueZ are received on the Bt-Ifce callback thread and enqueued onto a GLib asynchronous queue (<code>pGAQueueRunTask<\/code>) for processing in a dedicated <code>btrCore_RunTask<\/code> GThread. Processed events that need to be surfaced to the host process are similarly queued onto <code>pGAQueueOutTask<\/code> and dispatched by <code>btrCore_OutTask<\/code>, decoupling DBus dispatch latency from host-process callback execution. Device identity is represented by a <code>tBTRCoreDevId<\/code> derived from the device MAC address via <code>btrCore_GenerateUniqueDeviceID<\/code>. Known (paired) devices are stored in <code>stKnownDevicesArr<\/code> and scanned devices in <code>stScannedDevicesArr<\/code>, each tracked with a parallel <code>stBTRCoreDevStateInfo<\/code> array.<\/p>\n\n\n\n<p>Northbound, the host process calls <code>BTRCore_*<\/code> functions and receives asynchronous events via function pointer callbacks. Southbound interaction is through DBus method calls and signal subscriptions to BlueZ&#8217;s <code>org.bluez.*<\/code> interfaces (<code>Adapter1<\/code>, <code>Device1<\/code>, <code>AgentManager1<\/code>, <code>Media1<\/code>, <code>MediaTransport1<\/code>, <code>MediaPlayer1<\/code>, <code>GattManager1<\/code>, <code>LEAdvertisingManager1<\/code>, <code>Battery1<\/code>, etc.) implemented in <code>btrCore_dbus_bluez5.c<\/code> or <code>btrCore_gdbus_bluez5.c<\/code> depending on the build configuration.<\/p>\n\n\n\n<p>DBus (via <code>libdbus-1<\/code>) or GDBus (via <code>gio-2.0<\/code> \/ <code>gio-unix-2.0<\/code>) is used to communicate with <code>bluetoothd<\/code>. The host process interacts with <code>btr-core<\/code> exclusively through direct C function calls and registered callbacks.<\/p>\n\n\n\n<p>The known-device list is populated at init time by querying BlueZ&#8217;s paired-device list via DBus.<\/p>\n\n\n\n<div class=\"wp-block-merpress-mermaidjs diagram-source-mermaid\"><pre class=\"mermaid\">graph TD\n\nsubgraph Lib[\"btr-core library (C)\"]\n    BTRCoreAPI[\"btrCore.c\\nBTRCore_* public API\\nstBTRCoreHdl state store\"]\n    RunTask[\"btrCore_RunTask (GThread)\\nProcesses incoming BT events\\nfrom GAsyncQueue\"]\n    OutTask[\"btrCore_OutTask (GThread)\\nDispatches events to host\\nvia fPtr callbacks\"]\n    BattThread[\"btrCore_BatteryLevelThread (GThread)\\nPeriodic battery level polling\"]\n    HidThread[\"btrCore_HidNameWaitTimeoutThread (GThread)\\nTimeout for HID name resolution\"]\n    AVMedia[\"btrCore_avMedia\\nA2DP \/ AVRCP \/ HFP\\ncodec negotiation\"]\n    LEMod[\"btrCore_le\\nGATT profile tree\\nLE advertisement\"]\n    BtIfce[\"Bt-Ifce\\nbtrCore_dbus_bluez5 \/\\nbtrCore_gdbus_bluez5\"]\nend\n\nHostProc[(\"Bluetooth Manager (btmgr)\\nhost process\")]\nBlueZD[(\"bluetoothd\\n(BlueZ daemon)\")]\n\nHostProc -->|API Calls| BTRCoreAPI\nBTRCoreAPI --> RunTask\nBTRCoreAPI --> OutTask\nBTRCoreAPI --> BattThread\nBTRCoreAPI --> HidThread\nBTRCoreAPI --> AVMedia\nBTRCoreAPI --> LEMod\nAVMedia --> BtIfce\nLEMod --> BtIfce\nBTRCoreAPI --> BtIfce\nBtIfce -->|DBus\/GDBus method calls| BlueZD\nBlueZD -->|DBus signals \/ replies| BtIfce\nBtIfce -->|internal callbacks| BTRCoreAPI\nRunTask -->|enqueue outbound events| OutTask\nOutTask -->|Callbacks| HostProc<\/pre><\/div>\n\n\n\n<h3 class=\"wp-block-heading\">Threading Model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Threading Architecture<\/strong>: Multi-threaded, event-driven architecture using GLib-based threads.<\/li>\n\n\n\n<li><strong>Main Thread<\/strong>: Calls <code>BTRCore_Init()<\/code> and <code>BTRCore_*<\/code> API functions. Registers callbacks and submits operations.<\/li>\n\n\n\n<li><strong>Worker Threads<\/strong>:<\/li>\n\n\n\n<li><em><code>btrCore_RunTask<\/code><\/em> (<code>GThread<\/code>): Dequeues tasks from <code>pGAQueueRunTask<\/code>. It processes incoming adapter status, device discovery\/removal\/loss, device status, media status, connection intimation, authentication, and modalias update events from the Bt-Ifce callbacks.<\/li>\n\n\n\n<li><em><code>btrCore_OutTask<\/code><\/em> (<code>GThread<\/code>): Dequeues tasks from <code>pGAQueueOutTask<\/code>. It invokes the host-process-registered callback functions (<code>fpcBBTRCoreDeviceDisc<\/code>, <code>fpcBBTRCoreStatus<\/code>, <code>fpcBBTRCoreMediaStatus<\/code>, <code>fpcBBTRCoreConnIntim<\/code>, <code>fpcBBTRCoreConnAuth<\/code>).<\/li>\n\n\n\n<li><em><code>btrCore_BatteryLevelThread<\/code><\/em> (<code>GThread<\/code>): Sleeps on <code>batteryLevelCond<\/code> (GMutex\/GCond), wakes periodically at <code>batteryLevelRefreshInterval<\/code> to query battery levels for connected devices via GATT, and exits on <code>batteryLevelThreadExit<\/code>.<\/li>\n\n\n\n<li><em><code>btrCore_HidNameWaitTimeoutThread<\/code><\/em> (<code>GThread<\/code>, per-device): Waits <code>BTRCORE_HID_NAME_WAIT_TIMEOUT_SEC = 7<\/code> seconds for a HID controller name to be resolved after connection. It cancels or confirms pending name information in <code>stPendingHidNameInfo<\/code>.<\/li>\n\n\n\n<li><strong>Synchronization<\/strong>: <code>GMutex<\/code> + <code>GCond<\/code> for battery thread coordination and HID name wait. <code>GAsyncQueue<\/code> (internally lock-free) is used for task hand-off between the Bt-Ifce callback thread and RunTask\/OutTask threads.<\/li>\n\n\n\n<li><strong>Async \/ Event Dispatch<\/strong>: BlueZ events arrive as DBus signal callbacks in the Bt-Ifce layer. These callbacks post <code>stBTRCoreTaskGAqData<\/code> items to <code>pGAQueueRunTask<\/code>. RunTask processes and posts to <code>pGAQueueOutTask<\/code>. OutTask invokes the host-registered callback. This two-queue chain keeps the DBus dispatch thread free.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">RDK-V Platform and Integration Requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Build Dependencies<\/strong>: C toolchain; autoconf >= 2.69, automake, libtool; <code>dbus-1<\/code> (required); <code>bluez5<\/code> (required, resolved from <code>DISTRO_FEATURES<\/code> via the <code>BLUEZ<\/code> variable); <code>rdk-logger<\/code> (required); <code>telemetry<\/code> (required); <code>glib-2.0 >= 2.58.0<\/code> + <code>gio-2.0<\/code> + <code>gio-unix-2.0<\/code> + <code>libffi >= 3.0.0<\/code> + <code>gdbus-codegen<\/code> + <code>glib-2.0-native<\/code> (when <code>gdbus_bluez5<\/code> is in <code>DISTRO_FEATURES<\/code>); <code>safec<\/code> (when <code>safec<\/code> is in <code>DISTRO_FEATURES<\/code>); <code>bluetooth\/audio\/a2dp-codecs.h<\/code> from BlueZ source.<\/li>\n\n\n\n<li><strong>Device Services \/ HAL<\/strong>: BlueZ daemon (<code>bluetoothd<\/code>) must be running and reachable on the system DBus.<\/li>\n\n\n\n<li><strong>Systemd Services<\/strong>: <code>bluetoothd<\/code> must be running.<\/li>\n\n\n\n<li><strong>Startup Order<\/strong>: <code>bluetoothd<\/code> must be available before <code>BTRCore_Init()<\/code> is called. The library queries BlueZ for adapters and paired devices at init time.<\/li>\n\n\n\n<li><strong>Build flags<\/strong> (from <code>EXTRA_OECONF<\/code>):<\/li>\n\n\n\n<li><code>--enable-btr-ifce=bluez5|gdbus_bluez5<\/code> \u2014 selects Bt-Ifce backend. <code>gdbus_bluez5<\/code> is selected when <code>gdbus_bluez5<\/code> is in <code>DISTRO_FEATURES<\/code>, otherwise <code>bluez5<\/code> when <code>bluez5<\/code> is in <code>DISTRO_FEATURES<\/code>.<\/li>\n\n\n\n<li><code>--enable-unsupportedgamepad=yes|no<\/code> \u2014 enables\/disables unsupported Bluetooth gamepad support. Defaults to <code>yes<\/code> unless <code>disable_unsupported_gamepad<\/code> is in <code>DISTRO_FEATURES<\/code>.<\/li>\n\n\n\n<li><code>--enable-rdk-logger=yes|no<\/code> \u2014 links <code>librdkloggers<\/code> and enables <code>RDK_LOGGER_ENABLED<\/code> when <code>rdk-logger<\/code> is present in runtime dependencies (<code>RDEPENDS<\/code>).<\/li>\n\n\n\n<li><code>--enable-safec=yes|no<\/code> \u2014 links <code>libsafec<\/code> when <code>safec<\/code> is in <code>DISTRO_FEATURES<\/code>, otherwise uses <code>SAFEC_DUMMY_API<\/code> stubs.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Component State Flow<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Initialization to Active State<\/h4>\n\n\n\n<div class=\"wp-block-merpress-mermaidjs diagram-source-mermaid\"><pre class=\"mermaid\">sequenceDiagram\n    participant Host as Bluetooth Manager (btmgr)\n    participant BTRCore as btrCore.c\n    participant BtIfce as Bt-Ifce\n    participant BlueZ as bluetoothd (DBus)\n\n    Host->>BTRCore: BTRCore_Init(&amp;hBTRCore)\n    BTRCore->>BtIfce: BtrCore_BTInitGetConnection()\n    BtIfce->>BlueZ: dbus_bus_get \/ g_bus_get (system bus)\n    BlueZ-->>BtIfce: DBusConnection \/ GDBusConnection\n    BTRCore->>BtIfce: BtrCore_BTGetAdapters()\n    BlueZ-->>BtIfce: adapter paths + addresses\n    BTRCore->>BTRCore: btrCore_InitDataSt(), populate adapterPath[]\/adapterAddr[]\n    BTRCore->>BTRCore: g_thread_new(btrCore_RunTask)\n    BTRCore->>BTRCore: g_thread_new(btrCore_OutTask)\n    BTRCore-->>Host: enBTRCoreSuccess, hBTRCore handle\n\n    Host->>BTRCore: BTRCore_RegisterAgent(hBTRCore, capMode)\n    BTRCore->>BtIfce: BtrCore_BTRegisterAgent()\n    BtIfce->>BlueZ: AgentManager1.RegisterAgent\n\n    Host->>BTRCore: BTRCore_StartDiscovery(hBTRCore, adapterPath, devType, duration)\n    BTRCore->>BtIfce: BtrCore_BTStartDiscovery()\n    BtIfce->>BlueZ: Adapter1.StartDiscovery\n    BlueZ-->>BtIfce: DeviceFound signals\n    BtIfce->>BTRCore: btrCore_BTDeviceStatusUpdateCb()\n    BTRCore->>BTRCore: btrCore_RunTaskAddOp(enBTRCoreTaskPTcBDeviceDisc)\n    BTRCore->>BTRCore: btrCore_OutTaskAddOp \u2192 fpcBBTRCoreDeviceDisc\n    BTRCore-->>Host: fPtr_BTRCore_DeviceDiscCb(stBTRCoreDiscoveryCBInfo)<\/pre><\/div>\n\n\n\n<h4 class=\"wp-block-heading\">Runtime State Changes<\/h4>\n\n\n\n<p><strong>State Change Triggers:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>BTRCore_PairDevice()<\/code> transitions a scanned device to <code>enBTRCoreDevStPaired<\/code>. On failure, the device remains at <code>enBTRCoreDevStFound<\/code>.<\/li>\n\n\n\n<li><code>BTRCore_ConnectDevice()<\/code> transitions a known device through <code>enBTRCoreDevStConnecting<\/code> \u2192 <code>enBTRCoreDevStConnected<\/code>. <code>BTRCore_DisconnectDevice()<\/code> transitions it through <code>enBTRCoreDevStDisconnecting<\/code> \u2192 <code>enBTRCoreDevStDisconnected<\/code>.<\/li>\n\n\n\n<li><code>enBTRCoreDevStPlaying<\/code> is set when an A2DP\/AVRCP transport path becomes active.<\/li>\n\n\n\n<li><code>enBTRCoreDevStLost<\/code> is set when BlueZ reports a device has disappeared from scan results. <code>enBTRCoreDevStUnpaired<\/code> is set on unpairing.<\/li>\n\n\n\n<li>Connection intimation (<code>fPtr_BTRCore_ConnIntimCb<\/code>) and authentication (<code>fPtr_BTRCore_ConnAuthCb<\/code>) callbacks give the host process the opportunity to accept or reject incoming connection and pairing requests.<\/li>\n<\/ul>\n\n\n\n<p><strong>Context Switching Scenarios:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unstable LE HID connections are detected by monitoring disconnect timestamps. When instability is identified, reconnect attempts are suppressed to prevent connection thrashing.<\/li>\n\n\n\n<li>HID controller name resolution is handled asynchronously using a per-device timeout of 7 seconds, as BlueZ may deliver the device name after the connection event.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Call Flows<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Initialization Call Flow<\/h4>\n\n\n\n<div class=\"wp-block-merpress-mermaidjs diagram-source-mermaid\"><pre class=\"mermaid\">sequenceDiagram\n    participant Host as Bluetooth Manager (btmgr)\n    participant BTRCore as btrCore.c\n    participant BtIfce as Bt-Ifce\n\n    Host->>BTRCore: BTRCore_Init(&amp;hBTRCore)\n    BTRCore->>BTRCore: g_malloc0(stBTRCoreHdl)\n    BTRCore->>BTRCore: btrCore_InitDataSt()\n    BTRCore->>BtIfce: BtrCore_BTInitGetConnection()\n    BtIfce-->>BTRCore: connHdl (DBusConnection \/ GDBusConnection)\n    BTRCore->>BtIfce: BtrCore_BTGetAdapters()\n    BtIfce-->>BTRCore: numOfAdapters, adapterPath[], adapterAddr[]\n    BTRCore->>BTRCore: g_thread_new(\"btrCore_RunTask\")\n    BTRCore->>BTRCore: g_thread_new(\"btrCore_OutTask\")\n    BTRCore-->>Host: enBTRCoreSuccess<\/pre><\/div>\n\n\n\n<h4 class=\"wp-block-heading\">Request Processing Call Flow<\/h4>\n\n\n\n<div class=\"wp-block-merpress-mermaidjs diagram-source-mermaid\"><pre class=\"mermaid\">sequenceDiagram\n    participant Host as Bluetooth Manager (btmgr)\n    participant BTRCore as btrCore.c\n    participant BtIfce as Bt-Ifce\n    participant BlueZ as bluetoothd\n\n    Host->>BTRCore: BTRCore_ConnectDevice(hBTRCore, devId, devType)\n    BTRCore->>BTRCore: btrCore_GetDeviceInfoKnown() \u2014 resolve MAC from devId\n    BTRCore->>BtIfce: BtrCore_BTConnectDevice(devPath, devType)\n    BtIfce->>BlueZ: Device1.Connect (DBus method call)\n    BlueZ-->>BtIfce: PropertiesChanged signal (Connected = true)\n    BtIfce->>BTRCore: btrCore_BTDeviceStatusUpdateCb(enBTDevConnected)\n    BTRCore->>BTRCore: btrCore_RunTaskAddOp(enBTRCoreTaskPTcBDeviceStatus)\n    BTRCore->>BTRCore: RunTask: update stKnownDevStInfoArr \u2192 enBTRCoreDevStConnected\n    BTRCore->>BTRCore: btrCore_OutTaskAddOp(fpcBBTRCoreStatus)\n    BTRCore-->>Host: fPtr_BTRCore_StatusCb(stBTRCoreDevStatusCBInfo{eDeviceCurrState=Connected})<\/pre><\/div>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Internal Modules<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Module \/ Class<\/th><th>Description<\/th><th>Key Files<\/th><\/tr><\/thead><tbody><tr><td><code>btrCore<\/code><\/td><td>Main BTRCore API implementation. Manages <code>stBTRCoreHdl<\/code>, adapter and device state arrays, task queue threads, battery thread, and routes Bt-Ifce callbacks into the two-stage task dispatch pipeline.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/btrCore.c\">src\/btrCore.c<\/a>, <a href=\"https:\/\/wiki.rdkcentral.com\/include\/btrCore.h\">include\/btrCore.h<\/a><\/td><\/tr><tr><td><code>btrCore_avMedia<\/code><\/td><td>Audio\/Video media session management. Handles A2DP media endpoint registration with BlueZ, SBC\/MPEG\/AAC codec capability negotiation, A2DP transport path acquisition, and AVRCP player\/browser path callbacks.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/btrCore_avMedia.c\">src\/btrCore_avMedia.c<\/a>, <a href=\"https:\/\/wiki.rdkcentral.com\/include\/btrCore_avMedia.h\">include\/btrCore_avMedia.h<\/a><\/td><\/tr><tr><td><code>btrCore_le<\/code><\/td><td>Bluetooth Low Energy \/ GATT implementation. Maintains the GATT profile tree (up to <code>BTR_MAX_GATT_PROFILE = 16<\/code> profiles, <code>BTR_MAX_GATT_SERVICE = 6<\/code> services, <code>BTR_MAX_GATT_CHAR = 28<\/code> characteristics, <code>BTR_MAX_GATT_DESC = 6<\/code> descriptors). Provides LE advertisement registration\/release, GATT read\/write\/notify operations, and OTA transfer helpers (<code>BtrCore_LE_BatteryOTATransfer<\/code>).<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/btrCore_le.c\">src\/btrCore_le.c<\/a>, <a href=\"https:\/\/wiki.rdkcentral.com\/include\/btrCore_le.h\">include\/btrCore_le.h<\/a><\/td><\/tr><tr><td><code>Bt-Ifce (btrCore_dbus_bluez5)<\/code><\/td><td>DBus\/BlueZ5 transport layer. Connects to the system DBus, proxies all <code>org.bluez.*<\/code> method calls, and registers DBus message filter handlers for <code>org.freedesktop.DBus.ObjectManager<\/code> signals and property change events. Selected with <code>--enable-btr-ifce=bluez5<\/code>.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a>, <a href=\"https:\/\/wiki.rdkcentral.com\/include\/bt-ifce\/btrCore_bt_ifce.h\">include\/bt-ifce\/btrCore_bt_ifce.h<\/a><\/td><\/tr><tr><td><code>Bt-Ifce (btrCore_gdbus_bluez5)<\/code><\/td><td>GDBus\/BlueZ5 transport layer. Uses GLib GDBus bindings generated by <code>gdbus-codegen<\/code> for type-safe BlueZ interface proxies. Selected with <code>--enable-btr-ifce=gdbus_bluez5<\/code>.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_gdbus_bluez5.c\">src\/bt-ifce\/btrCore_gdbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>bt-telemetry<\/code><\/td><td>Thin wrapper for T2 telemetry reporting. Provides <code>telemetry_init()<\/code>, <code>telemetry_event_s()<\/code>, <code>telemetry_event_d()<\/code>, <code>telemetry_event_f()<\/code>. <code>telemetry<\/code> is a required build dependency (always linked via <code>DEPENDS<\/code>).<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-telemetry.c\">src\/bt-telemetry.c<\/a><\/td><\/tr><tr><td><code>btrCore_service<\/code><\/td><td>Header-only UUID\/service string definitions. Maps Bluetooth SDP UUIDs (A2DP source\/sink, AVRCP, HFP, Headset, GATT, Tile, Battery, etc.) to shorthand name constants used in UUID-to-service classification logic.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/include\/btrCore_service.h\">include\/btrCore_service.h<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Component Interactions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Interaction Matrix<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Target Component \/ Layer<\/th><th>Interaction Purpose<\/th><th>Key APIs \/ Topics<\/th><\/tr><\/thead><tbody><tr><td><strong>Device Services \/ HAL<\/strong><\/td><td><\/td><td><\/td><\/tr><tr><td>BlueZ daemon (<code>bluetoothd<\/code>)<\/td><td>All Bluetooth operations \u2014 adapter control, device discovery, pairing, connection, A2DP media, GATT \u2014 are performed via DBus or GDBus method calls and signal subscriptions to BlueZ interfaces.<\/td><td><code>org.bluez.Adapter1<\/code>, <code>org.bluez.Device1<\/code>, <code>org.bluez.AgentManager1<\/code>, <code>org.bluez.Media1<\/code>, <code>org.bluez.MediaTransport1<\/code>, <code>org.bluez.MediaPlayer1<\/code>, <code>org.bluez.GattManager1<\/code>, <code>org.bluez.LEAdvertisingManager1<\/code>, <code>org.bluez.Battery1<\/code><\/td><\/tr><tr><td><strong>External Systems<\/strong><\/td><td><\/td><td><\/td><\/tr><tr><td>T2 Telemetry (<code>libtelemetry_msgsender<\/code>)<\/td><td>Reports Bluetooth events as T2 markers (string, integer, float values).<\/td><td><code>t2_init<\/code>, <code>t2_event_s<\/code>, <code>t2_event_d<\/code>, <code>t2_event_f<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Events Published<\/h3>\n\n\n\n<p>Outbound notifications are delivered synchronously to the host process via registered C function pointer callbacks:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Callback Type<\/th><th>Trigger Condition<\/th><th>Data Structure<\/th><\/tr><\/thead><tbody><tr><td><code>fPtr_BTRCore_DeviceDiscCb<\/code><\/td><td>A device is found or an adapter property changes during discovery.<\/td><td><code>stBTRCoreDiscoveryCBInfo<\/code><\/td><\/tr><tr><td><code>fPtr_BTRCore_StatusCb<\/code><\/td><td>A known or scanned device changes state (connected, disconnected, paired, lost, LE property update, etc.).<\/td><td><code>stBTRCoreDevStatusCBInfo<\/code><\/td><\/tr><tr><td><code>fPtr_BTRCore_MediaStatusCb<\/code><\/td><td>A media player state changes (track started\/paused\/stopped\/changed, position update, player name, volume, AVRCP playback controls).<\/td><td><code>stBTRCoreMediaStatusCBInfo<\/code><\/td><\/tr><tr><td><code>fPtr_BTRCore_ConnIntimCb<\/code><\/td><td>An incoming connection request requires the host&#8217;s decision (accept\/reject). Passkey delivered in <code>stBTRCoreConnCBInfo<\/code>.<\/td><td><code>stBTRCoreConnCBInfo<\/code><\/td><\/tr><tr><td><code>fPtr_BTRCore_ConnAuthCb<\/code><\/td><td>An incoming pairing\/authentication request requires the host&#8217;s authorization response.<\/td><td><code>stBTRCoreConnCBInfo<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">IPC Flow Patterns<\/h3>\n\n\n\n<p><strong>Primary Request \/ Response Flow:<\/strong><\/p>\n\n\n\n<div class=\"wp-block-merpress-mermaidjs diagram-source-mermaid\"><pre class=\"mermaid\">sequenceDiagram\n    participant Host as Bluetooth Manager (btmgr)\n    participant BTRCore as btrCore.c\n    participant BtIfce as Bt-Ifce\n    participant BlueZ as bluetoothd\n\n    Host->>BTRCore: BTRCore_* API call (e.g. BTRCore_PairDevice)\n    BTRCore->>BtIfce: BtrCore_BT* function (e.g. BtrCore_BTPairDevice)\n    BtIfce->>BlueZ: DBus method call (e.g. Device1.Pair)\n    BlueZ-->>BtIfce: DBus reply \/ PropertiesChanged signal\n    BtIfce->>BTRCore: internal status callback\n    BTRCore->>BTRCore: RunTask: update device state\n    BTRCore->>BTRCore: OutTask: queue outbound callback\n    BTRCore-->>Host: fPtr_BTRCore_StatusCb(stBTRCoreDevStatusCBInfo)<\/pre><\/div>\n\n\n\n<p><strong>Event Notification Flow:<\/strong><\/p>\n\n\n\n<div class=\"wp-block-merpress-mermaidjs diagram-source-mermaid\"><pre class=\"mermaid\">sequenceDiagram\n    participant BlueZ as bluetoothd\n    participant BtIfce as Bt-Ifce\n    participant RunTask as btrCore_RunTask\n    participant OutTask as btrCore_OutTask\n    participant Host as Bluetooth Manager (btmgr)\n\n    BlueZ->>BtIfce: DBus signal (e.g. DeviceFound, PropertiesChanged)\n    BtIfce->>RunTask: g_async_queue_push(pGAQueueRunTask, task)\n    RunTask->>RunTask: process event, update stBTRCoreHdl state\n    RunTask->>OutTask: g_async_queue_push(pGAQueueOutTask, outTask)\n    OutTask->>Host: invoke fPtr_BTRCore_*Cb(cbInfo)<\/pre><\/div>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation Details<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Major HAL APIs Integration<\/h3>\n\n\n\n<p>All southbound calls go directly to BlueZ over DBus\/GDBus. The key BlueZ interfaces invoked are listed below. All calls are made from within the Bt-Ifce layer.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>BlueZ Interface \/ Method<\/th><th>Purpose<\/th><th>Implementation File<\/th><\/tr><\/thead><tbody><tr><td><code>org.bluez.Adapter1.StartDiscovery<\/code> \/ <code>StopDiscovery<\/code><\/td><td>Start and stop BT device scanning.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.Device1.Pair<\/code> \/ <code>CancelPairing<\/code><\/td><td>Initiate and cancel pairing with a remote device.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.Device1.Connect<\/code> \/ <code>Disconnect<\/code><\/td><td>Connect and disconnect a paired device.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.AgentManager1.RegisterAgent<\/code> \/ <code>UnregisterAgent<\/code><\/td><td>Register\/unregister the pairing agent for passkey handling.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.Media1.RegisterEndpoint<\/code> \/ <code>UnregisterEndpoint<\/code><\/td><td>Register A2DP\/HFP media endpoints with codec capabilities.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.MediaTransport1.Acquire<\/code> \/ <code>Release<\/code><\/td><td>Acquire the file descriptor for A2DP PCM\/SBC audio streaming.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.GattManager1.RegisterApplication<\/code> \/ <code>UnregisterApplication<\/code><\/td><td>Register GATT server application for LE GATT service hosting.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.LEAdvertisingManager1.RegisterAdvertisement<\/code> \/ <code>UnregisterAdvertisement<\/code><\/td><td>Register and unregister LE advertisement data.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><tr><td><code>org.bluez.Battery1<\/code> (property read)<\/td><td>Read battery level from connected devices that expose the Battery service.<\/td><td><a href=\"https:\/\/wiki.rdkcentral.com\/src\/bt-ifce\/btrCore_dbus_bluez5.c\">src\/bt-ifce\/btrCore_dbus_bluez5.c<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Key Implementation Logic<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>State \/ Lifecycle Management<\/strong>:<\/li>\n\n\n\n<li>Device state transitions are tracked in <code>stBTRCoreDevStateInfo.eDevicePrevState<\/code> \/ <code>eDeviceCurrState<\/code> arrays parallel to <code>stKnownDevicesArr<\/code> and <code>stScannedDevicesArr<\/code>.<\/li>\n\n\n\n<li>Device IDs are generated deterministically from MAC address via <code>btrCore_GenerateUniqueDeviceID()<\/code> so they are stable across discovery sessions.<\/li>\n\n\n\n<li><strong>Event Processing<\/strong>:<\/li>\n\n\n\n<li>All Bt-Ifce callbacks post a <code>stBTRCoreTaskGAqData<\/code> item (containing <code>enBTRCoreTaskOp<\/code>, <code>enBTRCoreTaskProcessType<\/code>, and the event data pointer) to <code>pGAQueueRunTask<\/code>.<\/li>\n\n\n\n<li><code>btrCore_RunTask<\/code> pops items and processes them by type (<code>enBTRCoreTaskPTcBAdapterStatus<\/code>, <code>enBTRCoreTaskPTcBDeviceDisc<\/code>, <code>enBTRCoreTaskPTcBDeviceStatus<\/code>, <code>enBTRCoreTaskPTcBMediaStatus<\/code>, <code>enBTRCoreTaskPTcBDevOpInfoStatus<\/code>, <code>enBTRCoreTaskPTcBConnIntim<\/code>, <code>enBTRCoreTaskPTcBConnAuth<\/code>, <code>enBTRCoreTaskPTcBModaliasUpdate<\/code>).<\/li>\n\n\n\n<li>Events destined for the host are posted to <code>pGAQueueOutTask<\/code> and dispatched by <code>btrCore_OutTask<\/code>.<\/li>\n\n\n\n<li><strong>Error Handling Strategy<\/strong>:<\/li>\n\n\n\n<li>All public API functions return <code>enBTRCoreRet<\/code>. Failure codes include <code>enBTRCoreFailure<\/code>, <code>enBTRCoreInitFailure<\/code>, <code>enBTRCoreNotInitialized<\/code>, <code>enBTRCoreInvalidAdapter<\/code>, <code>enBTRCorePairingFailed<\/code>, <code>enBTRCoreDiscoveryFailure<\/code>, <code>enBTRCoreDeviceNotFound<\/code>, <code>enBTRCoreInvalidArg<\/code>.<\/li>\n\n\n\n<li>DBus errors in Bt-Ifce are handled by <code>btrCore_BTHandleDusError()<\/code> which logs the error name and message.<\/li>\n\n\n\n<li>Unexpected return codes are logged with diagnostic context and do not cause execution to abort.<\/li>\n\n\n\n<li><strong>Logging &amp; Diagnostics<\/strong>:<\/li>\n\n\n\n<li>When built with <code>--enable-rdk-logger=yes<\/code> and <code>RDK_LOGGER_ENABLED<\/code> defined, logging uses <code>rdk_debug.h<\/code> macros.<\/li>\n\n\n\n<li>Without RDK logger, the built-in <code>BTRCORELOG_INFO<\/code>, <code>BTRCORELOG_WARN<\/code>, <code>BTRCORELOG_ERROR<\/code>, and <code>BTRCORELOG_DEBUG<\/code> log macros are used.<\/li>\n\n\n\n<li>Telemetry events for key operational milestones are emitted via <code>bt-telemetry.c<\/code> wrappers.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Configuration<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Key Configuration Parameters<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Parameter<\/th><th>Type<\/th><th>Default<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr><td><code>BTRCORE_MAX_NUM_BT_ADAPTERS<\/code><\/td><td><code>unsigned int<\/code> macro<\/td><td><code>4<\/code><\/td><td>Maximum number of BT adapters tracked simultaneously. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/include\/btrCore.h\">include\/btrCore.h<\/a>.<\/td><\/tr><tr><td><code>BTRCORE_MAX_NUM_BT_DEVICES<\/code><\/td><td><code>unsigned int<\/code> macro<\/td><td><code>64<\/code><\/td><td>Maximum number of paired (known) devices. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/include\/btrCore.h\">include\/btrCore.h<\/a>.<\/td><\/tr><tr><td><code>BTRCORE_MAX_NUM_BT_DISCOVERED_DEVICES<\/code><\/td><td><code>unsigned int<\/code> macro<\/td><td><code>128<\/code><\/td><td>Maximum number of scanned devices held concurrently. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/include\/btrCore.h\">include\/btrCore.h<\/a>.<\/td><\/tr><tr><td><code>BTRCORE_LOW_BATTERY_THRESHOLD<\/code><\/td><td><code>int<\/code> constant<\/td><td><code>10<\/code><\/td><td>Battery level percentage below which a low-battery condition is flagged. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/src\/btrCore.c\">src\/btrCore.c<\/a>.<\/td><\/tr><tr><td><code>BTRCORE_BATTERY_REFRESH_INTERVAL<\/code><\/td><td><code>int<\/code> constant<\/td><td><code>300<\/code><\/td><td>Default battery level polling interval in seconds. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/src\/btrCore.c\">src\/btrCore.c<\/a>.<\/td><\/tr><tr><td><code>BTRCORE_LOW_BATTERY_REFRESH_INTERVAL<\/code><\/td><td><code>int<\/code> constant<\/td><td><code>60<\/code><\/td><td>Battery polling interval in seconds when a low-battery device is found. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/src\/btrCore.c\">src\/btrCore.c<\/a>.<\/td><\/tr><tr><td><code>BTRCORE_HID_NAME_WAIT_TIMEOUT_SEC<\/code><\/td><td><code>int<\/code> constant<\/td><td><code>7<\/code><\/td><td>Maximum seconds to wait for a HID controller name to be resolved after connection. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/src\/btrCore.c\">src\/btrCore.c<\/a>.<\/td><\/tr><tr><td><code>BT_MAX_NUM_GATT_SERVICE<\/code><\/td><td><code>int<\/code> constant<\/td><td><code>6<\/code><\/td><td>Maximum GATT services per profile in the LE sub-module. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/include\/bt-ifce\/btrCore_bt_ifce.h\">include\/bt-ifce\/btrCore_bt_ifce.h<\/a>.<\/td><\/tr><tr><td><code>BT_MAX_NUM_GATT_CHAR<\/code><\/td><td><code>int<\/code> constant<\/td><td><code>28<\/code><\/td><td>Maximum GATT characteristics per service. Defined in <a href=\"https:\/\/wiki.rdkcentral.com\/include\/bt-ifce\/btrCore_bt_ifce.h\">include\/bt-ifce\/btrCore_bt_ifce.h<\/a>.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Configuration Persistence<\/h3>\n\n\n\n<p>All configuration parameters are runtime values that apply for the lifetime of the process.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>btr-core is a C library that implements the Bluetooth HAL for RDK middleware. It provides [&hellip;]<\/p>\n","protected":false},"author":28,"featured_media":0,"parent":9844,"menu_order":4,"comment_status":"open","ping_status":"closed","template":"","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"class_list":["post-9864","page","type-page","status-publish","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Bluetooth (BT) - RDK Documentation Portal | Documentation<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Bluetooth (BT) - RDK Documentation Portal | Documentation\" \/>\n<meta property=\"og:description\" content=\"btr-core is a C library that implements the Bluetooth HAL for RDK middleware. It provides [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/\" \/>\n<meta property=\"og:site_name\" content=\"RDK Documentation Portal | Documentation\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-19T10:29:49+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/\",\"url\":\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/\",\"name\":\"Bluetooth (BT) - RDK Documentation Portal | Documentation\",\"isPartOf\":{\"@id\":\"https:\/\/developer.rdkcentral.com\/documentation\/#website\"},\"datePublished\":\"2022-06-21T09:10:25+00:00\",\"dateModified\":\"2026-11-19T10:29:49+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/developer.rdkcentral.com\/documentation\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentation\",\"item\":\"https:\/\/developer.rdkcentral.com\/documentation\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"RDK Video\",\"item\":\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Components\",\"item\":\"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"Bluetooth (BT)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/developer.rdkcentral.com\/documentation\/#website\",\"url\":\"https:\/\/developer.rdkcentral.com\/documentation\/\",\"name\":\"RDK Documentation Portal | Documentation\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/developer.rdkcentral.com\/documentation\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Bluetooth (BT) - RDK Documentation Portal | Documentation","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/","og_locale":"en_US","og_type":"article","og_title":"Bluetooth (BT) - RDK Documentation Portal | Documentation","og_description":"btr-core is a C library that implements the Bluetooth HAL for RDK middleware. It provides [&hellip;]","og_url":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/","og_site_name":"RDK Documentation Portal | Documentation","article_modified_time":"2026-11-19T10:29:49+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/","url":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/","name":"Bluetooth (BT) - RDK Documentation Portal | Documentation","isPartOf":{"@id":"https:\/\/developer.rdkcentral.com\/documentation\/#website"},"datePublished":"2022-06-21T09:10:25+00:00","dateModified":"2026-11-19T10:29:49+00:00","breadcrumb":{"@id":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/bluetooth_bt\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/developer.rdkcentral.com\/documentation\/"},{"@type":"ListItem","position":2,"name":"Documentation","item":"https:\/\/developer.rdkcentral.com\/documentation\/"},{"@type":"ListItem","position":3,"name":"RDK Video","item":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/"},{"@type":"ListItem","position":4,"name":"Components","item":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/rdk_video_documentation\/components\/"},{"@type":"ListItem","position":5,"name":"Bluetooth (BT)"}]},{"@type":"WebSite","@id":"https:\/\/developer.rdkcentral.com\/documentation\/#website","url":"https:\/\/developer.rdkcentral.com\/documentation\/","name":"RDK Documentation Portal | Documentation","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/developer.rdkcentral.com\/documentation\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}},"_links":{"self":[{"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/pages\/9864","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/comments?post=9864"}],"version-history":[{"count":5,"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/pages\/9864\/revisions"}],"predecessor-version":[{"id":13053,"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/pages\/9864\/revisions\/13053"}],"up":[{"embeddable":true,"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/pages\/9844"}],"wp:attachment":[{"href":"https:\/\/developer.rdkcentral.com\/documentation\/wp-json\/wp\/v2\/media?parent=9864"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}