bluetoothd
Manages Bluetooth devices and connections
TLDR
Start the daemon
Start the daemon, logging to stdout
Start the daemon with a specific configuration file (defaults to /etc/bluetooth/main.conf)
Start the daemon with verbose output to stderr
Start the daemon with verbose output coming from specific files in the bluetoothd or plugins source
SYNOPSIS
bluetoothd [options]
PARAMETERS
-n, --nodetach
Do not detach from the controlling terminal (run in the foreground).
-d, --debug
Enable debugging output. More -d's increase the verbosity.
-v, --version
Show the version of bluetoothd.
-h, --help
Show help options.
-E, --experimental
Enable experimental interfaces.
DESCRIPTION
bluetoothd is the Bluetooth daemon, the core process providing Bluetooth support on Linux systems.
It handles various aspects of Bluetooth functionality, including device discovery, pairing, service management, and connection management.
It acts as a central point of control, interacting with Bluetooth hardware through the BlueZ stack and exposing Bluetooth functionality to user-space applications via D-Bus.
Many desktop environments and other applications rely on bluetoothd to interact with Bluetooth devices like headphones, speakers, keyboards, mice, and more.
Without bluetoothd running, Bluetooth functionality will be unavailable. Its configuration is managed via the /etc/bluetooth/main.conf file, allowing customization of various parameters like device class, name, and security settings. Understanding how to configure and manage bluetoothd is essential for system administrators and developers working with Bluetooth on Linux.
CAVEATS
Proper system setup and kernel modules are required for bluetoothd to function correctly. User intervention or configuration may be needed to connect to and manage certain Bluetooth devices.
CONFIGURATION
The main configuration file for bluetoothd is located at /etc/bluetooth/main.conf. This file allows you to customize various settings, such as the Bluetooth device class, local name, and security options.
Changes to this file typically require a restart of the bluetoothd service.
D-BUS INTERFACE
bluetoothd exposes its functionality through the D-Bus inter-process communication system. Applications can use the D-Bus API to interact with bluetoothd, discover Bluetooth devices, establish connections, and manage services.
TROUBLESHOOTING
If you encounter issues with Bluetooth connectivity, check the bluetoothd logs for errors or warnings. Ensure that the Bluetooth hardware is enabled and that the required kernel modules are loaded. Use commands like hciconfig and bluetoothctl to diagnose and troubleshoot common problems.
HISTORY
bluetoothd is part of the BlueZ Bluetooth stack, which has been developed and maintained for many years. It has evolved significantly over time to support new Bluetooth standards and features. Its initial development focused on providing basic Bluetooth connectivity on Linux, but its role has grown to encompass a wide range of functionalities and integrations with desktop environments and applications.
SEE ALSO
hciconfig(8), rfkill(1), bluetoothctl(1)