Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.8.0 Beta
-
None
-
B2QT images, Linux Ubuntu Development Environment
Description
Relates to QTBUG-57017
When cross compiling from the development environment to the pi the Bluetooth works as expected. However, if I set the app as the default app for boot2qt, restart the pi, the blue tooth errors in exactly the same way saying that
Cannot find running Bluez, please check the Bluez installation.
if I ssh into the pi and check the following it says that Bluetooth is on and
running. None of my services or characteristics are discoverable, as they are when cross compiling.
Below are some commands I ran on the device to check the bluetooth. Please note that the first 2 commands I run from a system('') command when the app starts up. Thats where I get the error for
Cannot find running Bluez, please check the Bluez installation.
root@b2qt-raspberrypi3:/# connmanctl enable bluetooth Error bluetooth: Already enabled
root@b2qt-raspberrypi3:/# systemctl start bluetooth
[[0;1;32m●[[0m bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor prese
t: enabled)
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor prese
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor prese
t: enabled)
Active: inactive (dead) since Tue 2016-11-15 07:44:52 UTC; 22s ago
Docs: man:bluetoothd(8)
Process: 221 ExecStart=/usr/libexec/bluetooth/bluetoothd (code=exited, status=
0/SUCCESS)
Main PID: 221 (code=exited, status=0/SUCCESS)
Status: "Quitting"
Nov 15 07:44:52 b2qt-raspberrypi3 systemd[1]: Stopping Bluetooth service...
Nov 15 07:44:52 b2qt-raspberrypi3 systemd[1]: bluetooth.service: Got notificatio
n message from PID 221 (STATUS=Powering down)
Nov 15 07:44:52 b2qt-raspberrypi3 systemd[1]: bluetooth.service: Got notificatio
n message from PID 221 (STATUS=Quitting)
Nov 15 07:44:52 b2qt-raspberrypi3 systemd[1]: bluetooth.service: Child 221 belon
gs to bluetooth.service
Nov 15 07:44:52 b2qt-raspberrypi3 systemd[1]: bluetooth.service: Main process ex
ited, code=exited, status=0/SUCCESS
Nov 15 07:44:52 b2qt-raspberrypi3 systemd[1]: bluetooth.service: Changed stop-si
gterm -> dead
Nov 15 07:44:52 b2qt-raspberrypi3 systemd[1]: bluetooth.service: Job bluetooth.s
ervice/stop finished, result=done
root@b2qt-raspberrypi3:/# bluetoothctl -a [NEW] Controller B8:27:EB:45:5D:8E b2qt-raspberrypi3 [default] Agent registered [bluetooth]# show Controller B8:27:EB:45:5D:8E Name: b2qt-raspberrypi3 Alias: b2qt-raspberrypi3 Class: 0x000000 Powered: yes Discoverable: no Pairable: yes UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0525 Discovering: no [bluetooth]#
Do I need to be deploying the disk image in some other way to ensure that these services are on, even though they say they're on?