FBX-3566/3566W » FBX-3566/3566W-FW

# Bluetooth

Copy rtl_bt to /lib/firmware/rtl_bt

-------------------------------

Copy new files to /etc/pulse

-------------------------------

Useful commands if connect Bluetooth headphones:

pulseaudio --start

pulseaudio --system

pulseaudio --daemonize --system

add user root to audio group

usermod -aG audio root

Search and connect with hciconfig:

hciconfig hci0 up

hciconfig -a

hcitool dev

hcitool scan

hcitool cc F4:4E:FC:C3:DF:07

hcitool con

hcitool auth F4:4E:FC:C3:DF:07

test:

l2ping F4:4E:FC:C3:DF:07

Search and connect with bluetoothctl:

```

# bluetoothctl

```

to be greeted by its internal command prompt. Then enter:

```

# power on

# agent on

# default-agent

# scan on

```

Now make sure that your headset is in pairing mode. It should be discovered shortly. For example,

[NEW] Device 00:1D:43:6D:03:26 Lasmex LBT10

shows a device that calls itself "Lasmex LBT10" and has MAC address 00:1D:43:6D:03:26. We will now use that MAC address to initiate the pairing:

```

# pair F4:4E:FC:C3:DF:07

```

After pairing, you also need to explicitly connect the device (every time?):

```

# connect F4:4E:FC:C3:DF:07

```

If everything works correctly, you now have a separate output device in PulseAudio. Note: The device may be off by default. Select its audio profile (OFF, A2DP, HFP) in the "Configuration" tab of pavucontrol.

You can now redirect any audio through that device using the "Playback" and "Recording" tabs of pavucontrol.

You can now disable scanning again and exit the program:

```

# scan off

# exit

```

so, kudos to archlinux for that (after the 'connect' command, the sound over my bt speakers worked with pulseaudio pavucontrol)