Bluetooth (BT)
btr-core 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 — the RDK Bluetooth Manager (btmgr) middleware component — that initializes it to obtain a handle and drives event handling through registered callbacks.
btr-core 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.
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.
flowchart LR
classDef RDKMW stroke:#75D701,fill:#F1FFE6,stroke-width:2px;
classDef VL stroke:#808080,fill:#F2F2F2,stroke-width:2px;
subgraph RDKMW["RDK Core Middleware"]
BtMgr["Bluetooth Manager (btmgr)\n(host process)"]
BTRCore["btr-core library\n(BTRCore API)"]
BtIfce["Bt-Ifce\n(DBus / GDBus abstraction)"]
end
subgraph VL["Vendor Layer"]
BlueZ["BlueZ daemon\n(bluetoothd)"]
Kernel["Kernel BT modules"]
end
BtMgr -->|API Calls| BTRCore
BTRCore --> BtIfce
BtIfce -->|DBus / GDBus method calls| BlueZ
BlueZ --> Kernel
BlueZ -->|DBus signals / replies| BtIfce
BtIfce -->|callbacks| BTRCore
BTRCore -->|Callbacks| BtMgrKey Features & Responsibilities:
- Adapter management: Provides APIs to enumerate, select, power on/off, rename, enable discoverable state, reset, and query version information for Bluetooth adapters.
- Device discovery, pairing, and connection: Supports scanning for nearby devices, pairing and unpairing, and managing the full connection lifecycle for both classic and LE devices.
- A/V media session management: Handles A2DP sink/source and HFP media endpoint registration, codec negotiation (SBC, MPEG, AAC), AVRCP transport paths, and media player metadata and control commands.
- Bluetooth Low Energy (GATT): Manages GATT profile hierarchies, LE advertisement registration and release, GATT read/write/notify operations, and OTA firmware transfer.
- Battery level monitoring: Periodically polls battery levels for connected devices and delivers low-battery threshold notifications to the host process.
- Callback-based event dispatch: 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.
- Telemetry integration: Reports Bluetooth events to the platform telemetry service via T2 markers.
Design
The library is structured as a three-layer stack: the BTRCore API layer in btrCore.c, a sub-module layer (btrCore_avMedia, btrCore_le), and a transport-abstraction layer (Bt-Ifce). The top layer maintains all device and adapter state in the opaque stBTRCoreHdl structure allocated at BTRCore_Init(). Incoming DBus/GDBus events from BlueZ are received on the Bt-Ifce callback thread and enqueued onto a GLib asynchronous queue (pGAQueueRunTask) for processing in a dedicated btrCore_RunTask GThread. Processed events that need to be surfaced to the host process are similarly queued onto pGAQueueOutTask and dispatched by btrCore_OutTask, decoupling DBus dispatch latency from host-process callback execution. Device identity is represented by a tBTRCoreDevId derived from the device MAC address via btrCore_GenerateUniqueDeviceID. Known (paired) devices are stored in stKnownDevicesArr and scanned devices in stScannedDevicesArr, each tracked with a parallel stBTRCoreDevStateInfo array.
Northbound, the host process calls BTRCore_* functions and receives asynchronous events via function pointer callbacks. Southbound interaction is through DBus method calls and signal subscriptions to BlueZ’s org.bluez.* interfaces (Adapter1, Device1, AgentManager1, Media1, MediaTransport1, MediaPlayer1, GattManager1, LEAdvertisingManager1, Battery1, etc.) implemented in btrCore_dbus_bluez5.c or btrCore_gdbus_bluez5.c depending on the build configuration.
DBus (via libdbus-1) or GDBus (via gio-2.0 / gio-unix-2.0) is used to communicate with bluetoothd. The host process interacts with btr-core exclusively through direct C function calls and registered callbacks.
The known-device list is populated at init time by querying BlueZ’s paired-device list via DBus.
graph TD
subgraph Lib["btr-core library (C)"]
BTRCoreAPI["btrCore.c\nBTRCore_* public API\nstBTRCoreHdl state store"]
RunTask["btrCore_RunTask (GThread)\nProcesses incoming BT events\nfrom GAsyncQueue"]
OutTask["btrCore_OutTask (GThread)\nDispatches events to host\nvia fPtr callbacks"]
BattThread["btrCore_BatteryLevelThread (GThread)\nPeriodic battery level polling"]
HidThread["btrCore_HidNameWaitTimeoutThread (GThread)\nTimeout for HID name resolution"]
AVMedia["btrCore_avMedia\nA2DP / AVRCP / HFP\ncodec negotiation"]
LEMod["btrCore_le\nGATT profile tree\nLE advertisement"]
BtIfce["Bt-Ifce\nbtrCore_dbus_bluez5 /\nbtrCore_gdbus_bluez5"]
end
HostProc[("Bluetooth Manager (btmgr)\nhost process")]
BlueZD[("bluetoothd\n(BlueZ daemon)")]
HostProc -->|API Calls| BTRCoreAPI
BTRCoreAPI --> RunTask
BTRCoreAPI --> OutTask
BTRCoreAPI --> BattThread
BTRCoreAPI --> HidThread
BTRCoreAPI --> AVMedia
BTRCoreAPI --> LEMod
AVMedia --> BtIfce
LEMod --> BtIfce
BTRCoreAPI --> BtIfce
BtIfce -->|DBus/GDBus method calls| BlueZD
BlueZD -->|DBus signals / replies| BtIfce
BtIfce -->|internal callbacks| BTRCoreAPI
RunTask -->|enqueue outbound events| OutTask
OutTask -->|Callbacks| HostProcThreading Model
- Threading Architecture: Multi-threaded, event-driven architecture using GLib-based threads.
- Main Thread: Calls
BTRCore_Init()andBTRCore_*API functions. Registers callbacks and submits operations. - Worker Threads:
btrCore_RunTask(GThread): Dequeues tasks frompGAQueueRunTask. 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.btrCore_OutTask(GThread): Dequeues tasks frompGAQueueOutTask. It invokes the host-process-registered callback functions (fpcBBTRCoreDeviceDisc,fpcBBTRCoreStatus,fpcBBTRCoreMediaStatus,fpcBBTRCoreConnIntim,fpcBBTRCoreConnAuth).btrCore_BatteryLevelThread(GThread): Sleeps onbatteryLevelCond(GMutex/GCond), wakes periodically atbatteryLevelRefreshIntervalto query battery levels for connected devices via GATT, and exits onbatteryLevelThreadExit.btrCore_HidNameWaitTimeoutThread(GThread, per-device): WaitsBTRCORE_HID_NAME_WAIT_TIMEOUT_SEC = 7seconds for a HID controller name to be resolved after connection. It cancels or confirms pending name information instPendingHidNameInfo.- Synchronization:
GMutex+GCondfor battery thread coordination and HID name wait.GAsyncQueue(internally lock-free) is used for task hand-off between the Bt-Ifce callback thread and RunTask/OutTask threads. - Async / Event Dispatch: BlueZ events arrive as DBus signal callbacks in the Bt-Ifce layer. These callbacks post
stBTRCoreTaskGAqDataitems topGAQueueRunTask. RunTask processes and posts topGAQueueOutTask. OutTask invokes the host-registered callback. This two-queue chain keeps the DBus dispatch thread free.
RDK-V Platform and Integration Requirements
- Build Dependencies: C toolchain; autoconf >= 2.69, automake, libtool;
dbus-1(required);bluez5(required, resolved fromDISTRO_FEATURESvia theBLUEZvariable);rdk-logger(required);telemetry(required);glib-2.0 >= 2.58.0+gio-2.0+gio-unix-2.0+libffi >= 3.0.0+gdbus-codegen+glib-2.0-native(whengdbus_bluez5is inDISTRO_FEATURES);safec(whensafecis inDISTRO_FEATURES);bluetooth/audio/a2dp-codecs.hfrom BlueZ source. - Device Services / HAL: BlueZ daemon (
bluetoothd) must be running and reachable on the system DBus. - Systemd Services:
bluetoothdmust be running. - Startup Order:
bluetoothdmust be available beforeBTRCore_Init()is called. The library queries BlueZ for adapters and paired devices at init time. - Build flags (from
EXTRA_OECONF): --enable-btr-ifce=bluez5|gdbus_bluez5— selects Bt-Ifce backend.gdbus_bluez5is selected whengdbus_bluez5is inDISTRO_FEATURES, otherwisebluez5whenbluez5is inDISTRO_FEATURES.--enable-unsupportedgamepad=yes|no— enables/disables unsupported Bluetooth gamepad support. Defaults toyesunlessdisable_unsupported_gamepadis inDISTRO_FEATURES.--enable-rdk-logger=yes|no— linkslibrdkloggersand enablesRDK_LOGGER_ENABLEDwhenrdk-loggeris present in runtime dependencies (RDEPENDS).--enable-safec=yes|no— linkslibsafecwhensafecis inDISTRO_FEATURES, otherwise usesSAFEC_DUMMY_APIstubs.
Component State Flow
Initialization to Active State
sequenceDiagram
participant Host as Bluetooth Manager (btmgr)
participant BTRCore as btrCore.c
participant BtIfce as Bt-Ifce
participant BlueZ as bluetoothd (DBus)
Host->>BTRCore: BTRCore_Init(&hBTRCore)
BTRCore->>BtIfce: BtrCore_BTInitGetConnection()
BtIfce->>BlueZ: dbus_bus_get / g_bus_get (system bus)
BlueZ-->>BtIfce: DBusConnection / GDBusConnection
BTRCore->>BtIfce: BtrCore_BTGetAdapters()
BlueZ-->>BtIfce: adapter paths + addresses
BTRCore->>BTRCore: btrCore_InitDataSt(), populate adapterPath[]/adapterAddr[]
BTRCore->>BTRCore: g_thread_new(btrCore_RunTask)
BTRCore->>BTRCore: g_thread_new(btrCore_OutTask)
BTRCore-->>Host: enBTRCoreSuccess, hBTRCore handle
Host->>BTRCore: BTRCore_RegisterAgent(hBTRCore, capMode)
BTRCore->>BtIfce: BtrCore_BTRegisterAgent()
BtIfce->>BlueZ: AgentManager1.RegisterAgent
Host->>BTRCore: BTRCore_StartDiscovery(hBTRCore, adapterPath, devType, duration)
BTRCore->>BtIfce: BtrCore_BTStartDiscovery()
BtIfce->>BlueZ: Adapter1.StartDiscovery
BlueZ-->>BtIfce: DeviceFound signals
BtIfce->>BTRCore: btrCore_BTDeviceStatusUpdateCb()
BTRCore->>BTRCore: btrCore_RunTaskAddOp(enBTRCoreTaskPTcBDeviceDisc)
BTRCore->>BTRCore: btrCore_OutTaskAddOp → fpcBBTRCoreDeviceDisc
BTRCore-->>Host: fPtr_BTRCore_DeviceDiscCb(stBTRCoreDiscoveryCBInfo)Runtime State Changes
State Change Triggers:
BTRCore_PairDevice()transitions a scanned device toenBTRCoreDevStPaired. On failure, the device remains atenBTRCoreDevStFound.BTRCore_ConnectDevice()transitions a known device throughenBTRCoreDevStConnecting→enBTRCoreDevStConnected.BTRCore_DisconnectDevice()transitions it throughenBTRCoreDevStDisconnecting→enBTRCoreDevStDisconnected.enBTRCoreDevStPlayingis set when an A2DP/AVRCP transport path becomes active.enBTRCoreDevStLostis set when BlueZ reports a device has disappeared from scan results.enBTRCoreDevStUnpairedis set on unpairing.- Connection intimation (
fPtr_BTRCore_ConnIntimCb) and authentication (fPtr_BTRCore_ConnAuthCb) callbacks give the host process the opportunity to accept or reject incoming connection and pairing requests.
Context Switching Scenarios:
- Unstable LE HID connections are detected by monitoring disconnect timestamps. When instability is identified, reconnect attempts are suppressed to prevent connection thrashing.
- 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.
Call Flows
Initialization Call Flow
sequenceDiagram
participant Host as Bluetooth Manager (btmgr)
participant BTRCore as btrCore.c
participant BtIfce as Bt-Ifce
Host->>BTRCore: BTRCore_Init(&hBTRCore)
BTRCore->>BTRCore: g_malloc0(stBTRCoreHdl)
BTRCore->>BTRCore: btrCore_InitDataSt()
BTRCore->>BtIfce: BtrCore_BTInitGetConnection()
BtIfce-->>BTRCore: connHdl (DBusConnection / GDBusConnection)
BTRCore->>BtIfce: BtrCore_BTGetAdapters()
BtIfce-->>BTRCore: numOfAdapters, adapterPath[], adapterAddr[]
BTRCore->>BTRCore: g_thread_new("btrCore_RunTask")
BTRCore->>BTRCore: g_thread_new("btrCore_OutTask")
BTRCore-->>Host: enBTRCoreSuccessRequest Processing Call Flow
sequenceDiagram
participant Host as Bluetooth Manager (btmgr)
participant BTRCore as btrCore.c
participant BtIfce as Bt-Ifce
participant BlueZ as bluetoothd
Host->>BTRCore: BTRCore_ConnectDevice(hBTRCore, devId, devType)
BTRCore->>BTRCore: btrCore_GetDeviceInfoKnown() — resolve MAC from devId
BTRCore->>BtIfce: BtrCore_BTConnectDevice(devPath, devType)
BtIfce->>BlueZ: Device1.Connect (DBus method call)
BlueZ-->>BtIfce: PropertiesChanged signal (Connected = true)
BtIfce->>BTRCore: btrCore_BTDeviceStatusUpdateCb(enBTDevConnected)
BTRCore->>BTRCore: btrCore_RunTaskAddOp(enBTRCoreTaskPTcBDeviceStatus)
BTRCore->>BTRCore: RunTask: update stKnownDevStInfoArr → enBTRCoreDevStConnected
BTRCore->>BTRCore: btrCore_OutTaskAddOp(fpcBBTRCoreStatus)
BTRCore-->>Host: fPtr_BTRCore_StatusCb(stBTRCoreDevStatusCBInfo{eDeviceCurrState=Connected})Internal Modules
| Module / Class | Description | Key Files |
|---|---|---|
btrCore | Main BTRCore API implementation. Manages stBTRCoreHdl, adapter and device state arrays, task queue threads, battery thread, and routes Bt-Ifce callbacks into the two-stage task dispatch pipeline. | src/btrCore.c, include/btrCore.h |
btrCore_avMedia | 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. | src/btrCore_avMedia.c, include/btrCore_avMedia.h |
btrCore_le | Bluetooth Low Energy / GATT implementation. Maintains the GATT profile tree (up to BTR_MAX_GATT_PROFILE = 16 profiles, BTR_MAX_GATT_SERVICE = 6 services, BTR_MAX_GATT_CHAR = 28 characteristics, BTR_MAX_GATT_DESC = 6 descriptors). Provides LE advertisement registration/release, GATT read/write/notify operations, and OTA transfer helpers (BtrCore_LE_BatteryOTATransfer). | src/btrCore_le.c, include/btrCore_le.h |
Bt-Ifce (btrCore_dbus_bluez5) | DBus/BlueZ5 transport layer. Connects to the system DBus, proxies all org.bluez.* method calls, and registers DBus message filter handlers for org.freedesktop.DBus.ObjectManager signals and property change events. Selected with --enable-btr-ifce=bluez5. | src/bt-ifce/btrCore_dbus_bluez5.c, include/bt-ifce/btrCore_bt_ifce.h |
Bt-Ifce (btrCore_gdbus_bluez5) | GDBus/BlueZ5 transport layer. Uses GLib GDBus bindings generated by gdbus-codegen for type-safe BlueZ interface proxies. Selected with --enable-btr-ifce=gdbus_bluez5. | src/bt-ifce/btrCore_gdbus_bluez5.c |
bt-telemetry | Thin wrapper for T2 telemetry reporting. Provides telemetry_init(), telemetry_event_s(), telemetry_event_d(), telemetry_event_f(). telemetry is a required build dependency (always linked via DEPENDS). | src/bt-telemetry.c |
btrCore_service | 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. | include/btrCore_service.h |
Component Interactions
Interaction Matrix
| Target Component / Layer | Interaction Purpose | Key APIs / Topics |
|---|---|---|
| Device Services / HAL | ||
BlueZ daemon (bluetoothd) | All Bluetooth operations — adapter control, device discovery, pairing, connection, A2DP media, GATT — are performed via DBus or GDBus method calls and signal subscriptions to BlueZ interfaces. | org.bluez.Adapter1, org.bluez.Device1, org.bluez.AgentManager1, org.bluez.Media1, org.bluez.MediaTransport1, org.bluez.MediaPlayer1, org.bluez.GattManager1, org.bluez.LEAdvertisingManager1, org.bluez.Battery1 |
| External Systems | ||
T2 Telemetry (libtelemetry_msgsender) | Reports Bluetooth events as T2 markers (string, integer, float values). | t2_init, t2_event_s, t2_event_d, t2_event_f |
Events Published
Outbound notifications are delivered synchronously to the host process via registered C function pointer callbacks:
| Callback Type | Trigger Condition | Data Structure |
|---|---|---|
fPtr_BTRCore_DeviceDiscCb | A device is found or an adapter property changes during discovery. | stBTRCoreDiscoveryCBInfo |
fPtr_BTRCore_StatusCb | A known or scanned device changes state (connected, disconnected, paired, lost, LE property update, etc.). | stBTRCoreDevStatusCBInfo |
fPtr_BTRCore_MediaStatusCb | A media player state changes (track started/paused/stopped/changed, position update, player name, volume, AVRCP playback controls). | stBTRCoreMediaStatusCBInfo |
fPtr_BTRCore_ConnIntimCb | An incoming connection request requires the host’s decision (accept/reject). Passkey delivered in stBTRCoreConnCBInfo. | stBTRCoreConnCBInfo |
fPtr_BTRCore_ConnAuthCb | An incoming pairing/authentication request requires the host’s authorization response. | stBTRCoreConnCBInfo |
IPC Flow Patterns
Primary Request / Response Flow:
sequenceDiagram
participant Host as Bluetooth Manager (btmgr)
participant BTRCore as btrCore.c
participant BtIfce as Bt-Ifce
participant BlueZ as bluetoothd
Host->>BTRCore: BTRCore_* API call (e.g. BTRCore_PairDevice)
BTRCore->>BtIfce: BtrCore_BT* function (e.g. BtrCore_BTPairDevice)
BtIfce->>BlueZ: DBus method call (e.g. Device1.Pair)
BlueZ-->>BtIfce: DBus reply / PropertiesChanged signal
BtIfce->>BTRCore: internal status callback
BTRCore->>BTRCore: RunTask: update device state
BTRCore->>BTRCore: OutTask: queue outbound callback
BTRCore-->>Host: fPtr_BTRCore_StatusCb(stBTRCoreDevStatusCBInfo)Event Notification Flow:
sequenceDiagram
participant BlueZ as bluetoothd
participant BtIfce as Bt-Ifce
participant RunTask as btrCore_RunTask
participant OutTask as btrCore_OutTask
participant Host as Bluetooth Manager (btmgr)
BlueZ->>BtIfce: DBus signal (e.g. DeviceFound, PropertiesChanged)
BtIfce->>RunTask: g_async_queue_push(pGAQueueRunTask, task)
RunTask->>RunTask: process event, update stBTRCoreHdl state
RunTask->>OutTask: g_async_queue_push(pGAQueueOutTask, outTask)
OutTask->>Host: invoke fPtr_BTRCore_*Cb(cbInfo)Implementation Details
Major HAL APIs Integration
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.
| BlueZ Interface / Method | Purpose | Implementation File |
|---|---|---|
org.bluez.Adapter1.StartDiscovery / StopDiscovery | Start and stop BT device scanning. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.Device1.Pair / CancelPairing | Initiate and cancel pairing with a remote device. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.Device1.Connect / Disconnect | Connect and disconnect a paired device. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.AgentManager1.RegisterAgent / UnregisterAgent | Register/unregister the pairing agent for passkey handling. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.Media1.RegisterEndpoint / UnregisterEndpoint | Register A2DP/HFP media endpoints with codec capabilities. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.MediaTransport1.Acquire / Release | Acquire the file descriptor for A2DP PCM/SBC audio streaming. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.GattManager1.RegisterApplication / UnregisterApplication | Register GATT server application for LE GATT service hosting. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.LEAdvertisingManager1.RegisterAdvertisement / UnregisterAdvertisement | Register and unregister LE advertisement data. | src/bt-ifce/btrCore_dbus_bluez5.c |
org.bluez.Battery1 (property read) | Read battery level from connected devices that expose the Battery service. | src/bt-ifce/btrCore_dbus_bluez5.c |
Key Implementation Logic
- State / Lifecycle Management:
- Device state transitions are tracked in
stBTRCoreDevStateInfo.eDevicePrevState/eDeviceCurrStatearrays parallel tostKnownDevicesArrandstScannedDevicesArr. - Device IDs are generated deterministically from MAC address via
btrCore_GenerateUniqueDeviceID()so they are stable across discovery sessions. - Event Processing:
- All Bt-Ifce callbacks post a
stBTRCoreTaskGAqDataitem (containingenBTRCoreTaskOp,enBTRCoreTaskProcessType, and the event data pointer) topGAQueueRunTask. btrCore_RunTaskpops items and processes them by type (enBTRCoreTaskPTcBAdapterStatus,enBTRCoreTaskPTcBDeviceDisc,enBTRCoreTaskPTcBDeviceStatus,enBTRCoreTaskPTcBMediaStatus,enBTRCoreTaskPTcBDevOpInfoStatus,enBTRCoreTaskPTcBConnIntim,enBTRCoreTaskPTcBConnAuth,enBTRCoreTaskPTcBModaliasUpdate).- Events destined for the host are posted to
pGAQueueOutTaskand dispatched bybtrCore_OutTask. - Error Handling Strategy:
- All public API functions return
enBTRCoreRet. Failure codes includeenBTRCoreFailure,enBTRCoreInitFailure,enBTRCoreNotInitialized,enBTRCoreInvalidAdapter,enBTRCorePairingFailed,enBTRCoreDiscoveryFailure,enBTRCoreDeviceNotFound,enBTRCoreInvalidArg. - DBus errors in Bt-Ifce are handled by
btrCore_BTHandleDusError()which logs the error name and message. - Unexpected return codes are logged with diagnostic context and do not cause execution to abort.
- Logging & Diagnostics:
- When built with
--enable-rdk-logger=yesandRDK_LOGGER_ENABLEDdefined, logging usesrdk_debug.hmacros. - Without RDK logger, the built-in
BTRCORELOG_INFO,BTRCORELOG_WARN,BTRCORELOG_ERROR, andBTRCORELOG_DEBUGlog macros are used. - Telemetry events for key operational milestones are emitted via
bt-telemetry.cwrappers.
Configuration
Key Configuration Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
BTRCORE_MAX_NUM_BT_ADAPTERS | unsigned int macro | 4 | Maximum number of BT adapters tracked simultaneously. Defined in include/btrCore.h. |
BTRCORE_MAX_NUM_BT_DEVICES | unsigned int macro | 64 | Maximum number of paired (known) devices. Defined in include/btrCore.h. |
BTRCORE_MAX_NUM_BT_DISCOVERED_DEVICES | unsigned int macro | 128 | Maximum number of scanned devices held concurrently. Defined in include/btrCore.h. |
BTRCORE_LOW_BATTERY_THRESHOLD | int constant | 10 | Battery level percentage below which a low-battery condition is flagged. Defined in src/btrCore.c. |
BTRCORE_BATTERY_REFRESH_INTERVAL | int constant | 300 | Default battery level polling interval in seconds. Defined in src/btrCore.c. |
BTRCORE_LOW_BATTERY_REFRESH_INTERVAL | int constant | 60 | Battery polling interval in seconds when a low-battery device is found. Defined in src/btrCore.c. |
BTRCORE_HID_NAME_WAIT_TIMEOUT_SEC | int constant | 7 | Maximum seconds to wait for a HID controller name to be resolved after connection. Defined in src/btrCore.c. |
BT_MAX_NUM_GATT_SERVICE | int constant | 6 | Maximum GATT services per profile in the LE sub-module. Defined in include/bt-ifce/btrCore_bt_ifce.h. |
BT_MAX_NUM_GATT_CHAR | int constant | 28 | Maximum GATT characteristics per service. Defined in include/bt-ifce/btrCore_bt_ifce.h. |
Configuration Persistence
All configuration parameters are runtime values that apply for the lifetime of the process.

