From a10e2a774a41cbfbebb313dc648c9e4cdbbf4f8c Mon Sep 17 00:00:00 2001 From: Hector Palacios Date: Mon, 30 Nov 2015 11:57:34 +0100 Subject: [PATCH] bluetooth: bring interface up before launching bluetoothd If the bluetoothd daemon is launched before the interface is ready RFCOMM/L2CAP listening socket connections fail (apparently because the channel is not ready) with BlueZ 5. Signed-off-by: Hector Palacios https://jira.digi.com/browse/DEL-2042 --- meta-digi-dey/recipes-connectivity/bluez/bluez5/bluez-init | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta-digi-dey/recipes-connectivity/bluez/bluez5/bluez-init b/meta-digi-dey/recipes-connectivity/bluez/bluez5/bluez-init index dd3dd27cf..dbd5fc7e8 100755 --- a/meta-digi-dey/recipes-connectivity/bluez/bluez5/bluez-init +++ b/meta-digi-dey/recipes-connectivity/bluez/bluez5/bluez-init @@ -94,8 +94,8 @@ bt_init() { fi } -echo "Starting bluetooth services." -start-stop-daemon -S --background --exec /usr/lib/bluez5/bluetooth/bluetoothd - # Check if this hardware does support Bluetooth [ -d "/proc/device-tree/bluetooth" ] && bt_init + +echo "Starting bluetooth services." +start-stop-daemon -S --background --exec /usr/lib/bluez5/bluetooth/bluetoothd