Hi Claudiu, On 19 July 2015 at 20:50, Claudiu Olteanu < olteanu.vasilica.clau...@gmail.com> wrote:
> Hi Rick, > > I can select my usb bluetooth dongle (using the one that came with my >> petrel), and power it up or down, but I was not able to pair or unpair >> (when previously paired using the onboard bluetooth). Downloading fails >> with the usb dongle, even when it had already been paired. It didn't make >> any difference whether onboard bluetooth was powered or not when I tried. >> > > Can you give me more details about the downloading step? > It fails on the connection step or it gets stuck during the download > mode? You should find some logs on the console. > > Here's the console output. First section is using hci0 (onboard) successfully, second section is failing to pair with hci1 (usb). I have also attached hcidump logs from the same time. It appears it is failing at the authentication stage. Using bluetoothctl (see further below), pairing with hci1 requires entering a password, 0000. $ ./subsurface Map theme file does not exist: "" QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory qt.bluetooth.bluez: Bluez 5 detected. qt.bluetooth.bluez: Creating QtBluezDiscoveryManager qt.bluetooth.bluez: Discovered: "90:00:DB:C6:98:B0" "Galaxy S6" Num UUIDs 13 total device 0 cached RSSI 0 Class 5898764 qt.bluetooth.bluez: Discovered: "00:13:43:0E:6B:D0" "Petrel" Num UUIDs 0 total device 1 cached RSSI -35 Class 526084 qt.bluetooth.bluez: Initiating direct pair to "00:13:43:0E:6B:D0" qt.bluetooth.bluez: Sending pairing request to "00:13:43:0E:6B:D0" qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 24 error: -1 "Resource temporarily unavailable" [15.711507] ERROR: Failed to download the dive. [in shearwater_petrel.c:296 (shearwater_petrel_device_foreach)] (download worked fine until I clicked cancel after 10 dives) console output using hci1: qt.bluetooth.bluez: Discovered: "00:13:43:0E:6B:D0" "Petrel" Num UUIDs 0 total device 0 cached RSSI -63 Class 526084 qt.bluetooth.bluez: Updating RSSI for "00:13:43:0E:6B:D0" QVariant(short, -78) qt.bluetooth.bluez: Updating RSSI for "00:13:43:0E:6B:D0" QVariant(short, -66) qt.bluetooth.bluez: Updating RSSI for "00:13:43:0E:6B:D0" QVariant(short, -76) qt.bluetooth.bluez: Initiating direct pair to "00:13:43:0E:6B:D0" qt.bluetooth.bluez: Sending pairing request to "00:13:43:0E:6B:D0" qt.bluetooth.bluez: Failed to create pairing "org.bluez.Error.AuthenticationFailed" qt.bluetooth.bluez: Initiating direct pair to "00:13:43:0E:6B:D0" qt.bluetooth.bluez: Sending pairing request to "00:13:43:0E:6B:D0" qt.bluetooth.bluez: Failed to create pairing "org.bluez.Error.AuthenticationFailed" > Does the onboard bluetooth device work after applying the patches? > No problems with the onboard bluetooth device. > > I tested my patches on my OpenSuse env with a Gembird Mini3 > Tiny Bluetooth v.2.1 dongle and I didn't encounter problems during > the download. The pair/unpair commands work too. > > Unfortunately the device is not recognized on my Fedora virtual > machine. Probably it is a problem with my driver because on their site > the latest driver has support for Windows 7 and I have Windows 8.1. > > Also, please check if the pairing status from the Bt selection widget > is the same as the one from bluetoothctl/bluedevil tools. > Just to be sure I hadn't messed something up on my system, I checked I could use bluetoothctl to pair the usb dongle to the petrel. I can, but unlike when using the onboard bluetooth, it requires I enter a password (0000). bluetooth]# select 00:15:83:3D:0A:57 [bluetooth]# agent on Agent registered [bluetooth]# scan on Discovery started [CHG] Controller 00:15:83:3D:0A:57 Discovering: yes [CHG] Device 00:13:43:0E:6B:D0 RSSI: -69 (subsequent RSSI lines deleted) [bluetooth]# trust 00:13:43:0E:6B:D0 [CHG] Device 00:13:43:0E:6B:D0 Trusted: yes Changing 00:13:43:0E:6B:D0 trust succeeded [bluetooth]# pair 00:13:43:0E:6B:D0 Attempting to pair with 00:13:43:0E:6B:D0 [CHG] Device 00:13:43:0E:6B:D0 Connected: yes Request PIN code [agent] Enter PIN code: 0000 [CHG] Device 00:13:43:0E:6B:D0 UUIDs: 00001101-0000-1000-8000-00805f9b34fb [CHG] Device 00:13:43:0E:6B:D0 Paired: yes Pairing successful > Regards, > Claudiu >
btsnoop ê áøë�w;Æ áøë�w?® ÿÿ�þ›ÿyƒ áøë�wC• ëP B áøë�wG| 0ëÃC"