answered
2017-12-09 21:38:32 +0200
Update: 2019-03-29 version 3.0.2 - as mentionned in other posts, the hcitool and bluetoothctl CLI utils are now in a package which is not installed by default.
You need to first:
devel-su
pkcon install bluez5-tools
(Or use zypper install bluez5-tools if you prefer)
Update: 2019-02-15: version 3.0.1.11 - some parings (Logitech UE 9000 noise-cancelling headset) that used to require fall-back to command line in the past now work as-is in the GUI. Also hcitool command is still available as part of bluez55 package installed by default.
Had a similar problem (car is Volvo S60 2011, phone is Sony Xperia X with Sailfish X 2.1.3.7).
Looks like a problem on the Volvo's Infotainment OS. (According to our garage, it is known to have bluetooth problem. The first couple of year, if music was playing over bluetooth, the rest of bt functionnality would go south. Or vice-versa: very to get bluetooth audio working reliably when a smartphone is paired to the car's phone functionnality. A later firmware update from Volvo did at least fix these bluetooth conflicts)
Combine it with the "still beta, not yet officially stable" status of Bluetooth with Sailfish X on Xperia X, and you're in for a tough ride.
In this case, for some reason the Volvo is unable to trigger Sailfish OS's input for a BlueTooth PIN.
Partial solution :
When using the command line interface on the smartphone (e.g.: using FingerTerm, or using SSH over USB cable from a laptop), coupling seems to work a bit better. (Will use code check, instead of PIN input).
Put the car's bluetooth in discoverable mode (it's in the "phone" pane, settings menu).
On the smartphone's command line:
# get root:
devel-su
# scan for devices
hcitool scan
# you'll see the name of nearby devices in discoverable mode and corresponding MAC addresses. Note the address of your car.
# open a connection to your car.
hcitool cc 00:06:F7:B2:A0:2E
# authentify the connection with a password
hcitool auth 00:06:F7:B2:A0:2E
The last one will trigger the car and your phone to check each-others security. (Some message Is the other device also displaying 26785 ? will display both on a pop up on the car's interface, and as a full-screen alert on the smartphone screen).
The device are now correctly paired.
(Though due to bug on the Sailfish X side, at that point I need to reboot the Xperia X for the auto-connect to work reliably)
It's not optimal (require manual typing of commands), but it works reliably (device then correctly appears in the list of paired device in Sailfish X, and correctly connects)
Alternative commands :
If using the more modern bluetoothctl interface trying to do the same work-around as above :
# enter the tool
bluetoothctl
# find the device:
scan on
# a list with all the visible devices will start to scroll
# look at a device (to check if that really the one you're looking for) :
info 00:0D:44:D0:AE:B4
# par it
pair 00:0D:44:D0:AE:B4
# optionnally mark it trusted (i.e.: allow automatic connections) :
trust 00:0D:44:D0:AE:B4
# test: try connecting to
connect 00:0D:44:D0:AE:B4
quit
Hi, has this issue started after updating to 2.1.1.26? Did pairing work ok with the previous OS version? Which version was that?
Do you start the pairing process at the car console? You wrote that the car console is requesting you to enter a 4-digit code on the phone - is Jolla displaying the dialog for entering the code? I mean, usually each device should prompt for a code on the device itself. In the modern BT implementations there is no need to enter any code but simply compare that each device is showing the same code and then accept the codes.
Have you tried starting it on Jolla, seeking for the car?
jovirkku ( 2017-10-03 22:36:09 +0200 )editProblem did exist with previous version 2.1.0 as well. I bought car recently, so I haven't been able to test with older Sailfish versions than 2.1.0.
I did start pairing from car console as instructed in user manual in step when connecting phone for the first time. Please see following; http://new.volvocars.com/ownersdocs/2007/2007_S80/07S80_04b.htm#pg162
Jolla did not show any dialog for entering code, when car console was asking it.
Heikki ( 2017-10-04 16:54:50 +0200 )editIve also reported this ... it worked in 2.0, stopped working in 2.1 for me on Jolla C. There are also other problems, like when it does get paired, no phonebook is transferred (tho, i havnt tested this in so long as I cant actually get it to pair!) (this is with a parrot CK3100...requiring a pin to be entered, there is no prompt for the pin on the jolla)
pigg ( 2017-10-21 18:15:51 +0200 )editHello,
did you try to pair via command line as described here: Pairing the Bluetooth?
This was written for Sailfish OS on a Raspberry Pi but did work on my Jolla 1, too (where the standard pairing dialog was auto-closed within less than a second making it impossible for me to enter the pin).
Greetings
nop ( 2017-10-22 16:26:01 +0200 )edit@jovirkku : In my experience, some device doesn't seem to agree which style to trigger, either old style (type a 4 digit PIN) or new style (compare two 5-digit random numbers).
The firmware on Volvo, the UE Boom speakers, some buggy implementation of Android Lollipop and the Sailfish X on Xperia X seem to be among implementations suffering with this problem.
If you have such devices on both ends of a pairing, it's gonna be difficult.
Usually falling back to manual commands on the command line seem to circumvent the problem.
(If command line is possible. On Sailfish, it's trivial. On non-unlocked/non-rooted Android smartphones, it's a bit more hairy)
DrYak ( 2017-12-10 00:54:49 +0200 )edit