Troubleshooting Bluetooth Connectivity in Arch Linux

Bluetooth allows short-range wireless communication between phones, headsets, speakers, keyboards and other peripherals. When working properly, Bluetooth devices can connect with simplicity and ease. However, sometimes tricky connectivity problems can arise that require in-depth troubleshooting.

In this comprehensive guide, I dive deep into Bluetooth internals, architecture, tools and techniques for diagnosing and fixing connection issues in Arch Linux from a developer perspective. Whether you are trying to use a new Bluetooth headset, synchronize files between your phone and laptop or build Bluetooth-enabled applications, this guide will equip you with the knowledge to overcome problems.

Anatomy of Common Bluetooth Issues

Bluetooth relies on several layers of specification and software components working in harmony. A fault in any piece can cause connectivity failures. Here are some frequent areas worth inspecting first:

Hardware and Drivers

• Bluetooth adapter disabled in BIOS or blocked via hardware switch
• Kernel driver not functioning correctly for adapter
• rfkill identifying adapter as blocked despite unblock attempts
• Adapter placement in USB 3.0 port causing interference

System Configuration

• Bluetooth daemon or services not fully started
• Firewall preventing connectivity on ports
• Outdated daemon or utilities version installed

Protocol and Connections

• Discovery failing due to maximum devices reached
• Pairing problems from incorrect PIN codes or timeouts
• Profile configuration issues preventing service authorization
• Bulk data transfer failure on faulty transport link

Methodically verifying correct functionality at each layer is key to narrowing down Bluetooth problems.

Bluetooth Architecture on Linux

Understanding the Bluetooth software stack architecture provides context on where issues can manifest:

• Controller Layer: Bluetooth device hardware and firmware
• Host Layer: Kernel drivers and system daemons/services
• Application Layer: Userspace programs and utilities

The Linux kernel contains drivers for Bluetooth controllers. Data gets passed to bluetoothd, which manages adapter connections. Client programs like Blueman then leverage the daemon for pairing devices and transferring data.

Key components include:

• BlueZ: Linux Bluetooth stack
• bluetoothd: Background daemon, controller/discovery
• D-Bus: IPC mechanism for Bluetooth tasks
• rfcomm: Serial device emulation protocol
• utilities: hcitool, hciconfig, bluetoothctl

Interactions between the layers is complex, so issues can be tricky to isolate.

Advanced Troubleshooting with Bluetooth Tools

Arch Linux and BlueZ contain various utilities that aid in pinpointing Bluetooth operation issues. Here is an overview of some handy ones:

bluetoothctl: Interactive shell with discovery, pairing and config control.

Commands allow direct management of the Bluetooth controller:

[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on
[bluetooth]# pair XX:XX:XX:XX 
[bluetooth]# connect XX:XX:XX:XX

hciconfig: Provides low-level parser for controller configuration:

See adapter index, address, supported features:

$ hciconfig -a  

Check connection state, statistics:

$ hciconfig hci0

Manually reset controller:

# hciconfig hci0 reset

hcitool: Sends HCI commands for debugging connections:

Scan nearby visible devices:

$ hcitool scan

List bondings and stored remote device data:

$ hcitool dev

Initiate high-level connections to test links:

$ hcitool cc XX:XX:XX:XX

sdptool: Manipulates Bluetooth service discovery data stored on devices. Useful for inspecting and clearing pairings:

$ sdptool browse XX:XX:XX
$ sdptool clear XX:XX

Wireshark: Captures live packet data from controller for analysis:

$ sudo wireshark -k -i bluetooth0

Lets you inspect protocol traffic like discovery, pairing and connections.

These tools provide extensive control over the Bluetooth stack for advanced diagnosis. Running them while replicating issues helps capture where problems occur.

Bluetooth Audio Troubleshooting

Bluetooth headphones and speakers rely on the Advanced Audio Distribution Profile (A2DP). Streaming A2DP audio can have quirks worth addressing:

Choppy/Skipping Audio: Often from interference or range issues. Can try:

• Adjusting device distance/location
• Using 5 GHz WiFi band instead 2.4 GHz
• Updating Bluetooth adapter and audio driver

Profile Authorization Issues: A2DP connection succeeds but no audio. Verify profiles active:

$ pactl list cards

If missing A2DP profile, remove and re-pair device.

Connecting Multiple Sinks: By default pulseaudio auto-switches sinks, causing unwanted disruptions. Create static sinks for each hardware device instead in /etc/pulse/default.pa.

No Microphone: Separate profile for audio input rarely connected automatically. Explicitly connect HSP/HFP after pairing:

$ pacmd set-card-profile 0 hfp_ofono

Testing with the CLI utilities while replicates issues will surface the culprit.

Advanced Usage: Bluetooth Tethering & PAN

Bluetooth tethering allows sharing Internet connections with other devices. Bluetooth PAN (Personal Area Network) sets up ad-hoc device networking. Both useful capabilities.

Internet Tethering

First, install dnsmasq and iptables packages, required for IP routing.

Enable tethering on host transport device (e.g. WiFi):

# ip link set wlp2s0 up  
# dhcpcd wlp2s0
# iptables -t nat -A POSTROUTING -s 10.42.0.0/16 ! -d 10.42.0.0/16 -j MASQUERADE  

Next, configure the Bluetooth adapter interface:

# hciconfig hci0 up
# hciconfig hci0 piscan  
# rfcomm bind hci0 <channel>

Authorize RFCOMM and NAP profiles after client device pairing to enable BT tethering connection. Clients get assigned IP from dnsmasq DHCP server.

Bluetooth PAN

Similar setup, but use Bluetooth Network Encapsulation Protocol (BNEP) instead of RFCOMM. This creates an ad-hoc peer-to-peer network over Bluetooth.

Host configuration:

# hciconfig hci0 up
# hciconfig hci0 piscan
# bnep0

Pair BNEP profile on client. Useful for file transfers without Internet.

Automating Bluetooth Actions

Bluetooth connections can be automated for simplifying pairing and data syncing between devices. Especially helpful for headless servers and IoT systems.

Connect on Boot

To auto-connect a headset on boot, append a new systemd unit:

[Unit]
Description=Auto-connect Bluetooth headset
After=bluetooth.service

[Service]
ExecStart=/usr/bin/bluetoothctl connect XX:XX:XX:XX
Type=simple
User=username

[Install]  
WantedBy=bluetooth.target

Replace XX:XX with headset MAC address.

Automate Data Sync

Script a two-way file sync over Bluetooth when attaching a phone:

#!/bin/bash

ADDR="XX:XX:XX:XX"

bluetoothctl << EOF
pair $ADDR
trust $ADDR  
EOF

obexftp -b$ADDR -B9 -l > /home/user/phone-backup.img
obexftp -b $ADDR -p/path/to/music/*.mp3

Customizations like this tailor Bluetooth functionality to your specific work.

Additional Bluetooth Tools Overview

Beyond what ships default in Arch, other handy Bluetooth utilities exist:

Blueberry: Featureful Bluetooth tray applet for MATE/XFCE. Fixes intermittent GNOME tray dropping.

Blueman: Packed with advanced options like audio profile selection, debug logs. Alternative to GNOME Bluetooth.

Bluez-Utils: Former standard Linux Bluetooth CLI programs. Being deprecated but still useful.

Evaluating different projects allows mixing and matching ideal tools for you particular Bluetooth use cases and workflow.

Key Takeaways

While intermittent glitches can plague Bluetooth connections, having an insight into common culprits along with an arsenal of troubleshooting tools places you well to diagnose issues. Remember these key points:

• Check adapter hardware, driver and software configuration issues first
• Utilize tools like hcitool and hciconfig for low-level debugging
• Break down problems based on Bluetooth architecture layers
• Capture traffic with Wireshark for protocol analysis
• Automate connections and syncing with scripts when necessary

Bluetooth serves an increasingly central role in how devices interconnect. I hope by offering this developer-focused guide to solving Bluetooth problems in Arch Linux, you feel empowered tackle any connectivity challenges you encounter!

Let me know in the comments if you found this deep dive helpful or have additional Bluetooth troubleshooting tips to share with readers.