Bluetooth Connection Issues

Questions about WIFI networks and devices
Forum rules
Before you post please read how to get help
Post Reply
stephenc
Level 1
Level 1
Posts: 2
Joined: Tue Oct 16, 2018 1:23 am

Bluetooth Connection Issues

Post by stephenc » Tue Oct 16, 2018 1:41 am

After many frustrating hours on the internet, I seek help. I would like to connect my MintBox Pro to my Garmin Glo over Bluetooth. Not having much luck. I can see the device on the GUI, but will not connect. My main attempts have been through CLI.

Using hcitools scan gives a null result

Code: Select all

stephen@molly-fitlet2:~$ hcitool scan
Scanning ...
stephen@molly-fitlet2:~$ 
I have more luck with bluetoothctl

Code: Select all

stephen@molly-fitlet2:~$ bluetoothctl
[NEW] Controller B8:08:CF:A0:8E:25 molly-fitlet2 [default]
[NEW] Device 88:53:95:29:DE:D6 88-53-95-29-DE-D6
[NEW] Device 6E:C2:40:B0:A7:A3 6E-C2-40-B0-A7-A3
[NEW] Device 10:C6:FC:EF:8A:94 Garmin GLO #f8a94
[NEW] Device 6C:94:F8:D6:42:CF 6C-94-F8-D6-42-CF
[NEW] Device 3F:D1:BD:FA:D5:0B 3F-D1-BD-FA-D5-0B
[NEW] Device 40:CB:C0:C1:4B:4F 40-CB-C0-C1-4B-4F
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[bluetooth]# pair 10:C6:FC:EF:8A:94
Attempting to pair with 10:C6:FC:EF:8A:94
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[bluetooth]# info 10:C6:FC:EF:8A:94
Device 10:C6:FC:EF:8A:94 (public)
	Name: Garmin GLO #f8a94
	Alias: Garmin GLO #f8a94
	Class: 0x00240418
	Icon: audio-card
	Paired: no
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: yes
	RSSI: -100
	TxPower: 8
If i try to connect directly I get

Code: Select all

[bluetooth]# connect 10:C6:FC:EF:8A:94
Attempting to connect to 10:C6:FC:EF:8A:94
Failed to connect: org.bluez.Error.Failed
Some more information in case it help

Code: Select all

[bluetooth]# show
Controller B8:08:CF:A0:8E:25 (public)
	Name: molly-fitlet2
	Alias: molly-fitlet2
	Class: 0x001c0104
	Powered: yes
	Discoverable: yes
	Pairable: yes
	UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0530
	Discovering: yes
and from systemctl status bluetooth :

Code: Select all

stephen@molly-fitlet2:~$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2018-10-15 22:13:02 PDT; 21min ago
     Docs: man:bluetoothd(8)
 Main PID: 722 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─722 /usr/lib/bluetooth/bluetoothd

Oct 15 22:13:02 molly-fitlet2 systemd[1]: Starting Bluetooth service...
Oct 15 22:13:02 molly-fitlet2 bluetoothd[722]: Bluetooth daemon 5.48
Oct 15 22:13:02 molly-fitlet2 bluetoothd[722]: Starting SDP server
Oct 15 22:13:02 molly-fitlet2 bluetoothd[722]: Bluetooth management interface 1.14 initialized
Oct 15 22:13:02 molly-fitlet2 systemd[1]: Started Bluetooth service.
Oct 15 22:13:22 molly-fitlet2 bluetoothd[722]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource
Oct 15 22:13:22 molly-fitlet2 bluetoothd[722]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink
Oct 15 22:16:05 molly-fitlet2 bluetoothd[722]: 10:C6:FC:EF:8A:94: error updating services: Host is down (112)
Oct 15 22:32:01 molly-fitlet2 bluetoothd[722]: 10:C6:FC:EF:8A:94: error updating services: Host is down (112)
Clearly "Host is down" is not a great sign. But the host is not down, and other devices can see it. A full listing of logs can be found at https://ptpb.pw/Svm0

I thing the rfkill is wrong as I have unlocked all and confirmed this with

Code: Select all

stephen@molly-fitlet2:~$ rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked
stephen@molly-fitlet2:~$ 
Lastly I have tried everything i know to make sure the garmin device is discoverable. And I rebooted a few times. Help!

stephenc
Level 1
Level 1
Posts: 2
Joined: Tue Oct 16, 2018 1:23 am

Re: Bluetooth Connection Issues [solved]

Post by stephenc » Wed Oct 17, 2018 12:03 am

After trying this again, seems like it is now working.

Code: Select all

[Garmin GLO #f8a94]# info 10:C6:FC:EF:8A:94
Device 10:C6:FC:EF:8A:94 (public)
	Name: Garmin GLO #f8a94
	Alias: Garmin GLO #f8a94
	Class: 0x00240418
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: yes
	UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (58e1f790-aa26-11e3-a5e2-0800200c9a66)
	Modalias: bluetooth:v0087p0005d0001
	RSSI: -89
	TxPower: 8
Not entirely sure how I convinced it to pair. I used the Blueberry GUI to pair, and then it all worked from the command line.The most important thing is I am now getting NEMA sentences. Very happy.

Post Reply

Return to “Wireless”