We have moved to a new Sailfish OS Forum. Please start new discussions there.

[HowTo] XA2 Bluetooth connection to car [released]

Tracked by Jolla

asked 2019-02-07 12:48:28 +0300

SagaciousT gravatar image

updated 2019-10-30 15:25:03 +0300

I've paired my Xperia XA2 with my 2013 Volvo Sensus successfully. It works pretty fine, even better than the Xperia X. Phone book, recent calls, etc. work.

The known problems when pairing the usual way still exist. It works if you make your car's Bluetooth interface visible and search for it in the phone. When you try to connect, the car will request a PIN, but the phone doesn't show one. Just enter 0000 to pair them.

Update for Sailfish Now, my car does not find my phone anymore. Even if I make it visible. Workaround is to connect to the car manually using the phone by clicking the car under Paired devices in the Bluetooth menu. Unfortunately, I need to do this every time anew.

Update: Manual pairing needs the correct order. It's necessary to try to initiate pairing from the car first before manual pairing triggered on the phone works.

Update for Sailfish 3.2.0: I can confirm that auto-pairing works now! Thanks for fixing this!

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by addydon
close date 2019-11-24 13:37:38.756982


Hi. Is it only me that can't get the bluetooth working as a key on my Tesla Model 3 through the Tesla android app? I can pair the phone with the media stuff so i can play music, have the phone book, recent calls and sync my calendar. XA2 Hossa

Breeze ( 2019-05-06 00:07:32 +0300 )edit

@Breeze :

in a nutshell: it's a common type of problems with some type of Bluetooth peripherals with Android apps (that want direct access to the Bluetooth) on Sailfish. Try Wifi if possible.

The long version: for Bluetooth, Sailfish uses bluez like any other GNU/Linux system (same as Ubuntu running on your Laptop). Android uses it's own thing - BlueDroid.

For a few devices, Sailfish handles the Bluetooth device, and it shows up as a standard device.

Bluetooth Speaker work, because Bluez5 and Pulseaudio handle them in Sailfish, and they simply show as "audio output" to Android app, (so Spotify works). Same with keyboards.

But currently the Jolla devs have not made something yet to forward between bluez and AlienDalvik.

So apps that want to directly control the Bluetooth connection don't work. To take again the example of Bluetooth speaker: although Spotify works, the special dedicated app by the manufacturer to upgrade the Firmware or upload equalizer settings will not work (because that one does't just play music over an audio output, but want direct access).

It seems very likely that Tesla isn't simply using the standard Bluetooth protocols that Sailfish already hands ("Car Handsfree" audio out, contacts sharing, etc) but is using some proprietary protocols that would require direct access to the Bluetooth stack, which won't work.

I don't own a Tesla (the joys of working in academic research) but check if it is possible to unlock over Wifi: Sailfish gives some (relative) access to the Wifi connection to Android Apps, and depending on how the apps checks if it is connected to the car's Wifi, it might correctly detect it and proceed.

DrYak ( 2019-07-21 14:39:36 +0300 )edit

@DrYak: Ok, thanks for the information. Do you think we gonna get something so bluez can give AlienDalvik access? Wifi is not possible to use as a key. The car detects your bluetooth and allows you to open the doors.

Breeze ( 2019-07-21 21:14:04 +0300 )edit

I can also confirm Bluetooth auto connections from car fail for 3.1.0 11

GD ( 2019-07-23 13:09:55 +0300 )edit

Same issue here: After updating to (Seitseminen) my phone no longer automatically connects to my car (Volvo C30 2012). I have to manually establish the connection from the phone each time I enter the car. Re-Pairing did not fix the problem :(

mlohse ( 2019-09-10 12:08:36 +0300 )edit

6 Answers

Sort by ยป oldest newest most voted

answered 2019-07-24 10:54:51 +0300

jovirkku gravatar image

Thanks for the problem reports. To be investigated.

edit flag offensive delete publish link more


Will this be resolved before final release of 3.1?

GD ( 2019-07-27 12:03:49 +0300 )edit

It would be great, if this will be fixed quickly. Shouldn't be a big issue since it already worked before.

SagaciousT ( 2019-08-06 12:34:27 +0300 )edit

answered 2019-07-21 14:18:36 +0300

DrYak gravatar image

(That's because on recent versions, Sailfish tries to use '0000' automatically as a default password. This works on Headphones, but not on more complex devices with a keyboard+screen that don't use default passwords like cars)

Alternatively, it's also possible to pair manually using the command line. It works 100% of the time, but is a bit more geeky/less noon-friendly.

edit flag offensive delete publish link more


Thanks for the password tip, I need to test if I set the connection authentication from "Generate random number" to "Fixed number" in my car's BT setting. I'll check back with the results.

raketti ( 2019-08-06 14:34:52 +0300 )edit

If you initiate pairing from the phone, you don't need to change the settings in your car, since the password will be defined by the phone, i.e. always set to 0000. However, it is not displayed and you need to know that you have to enter 0000 in the car.

SagaciousT ( 2019-08-06 14:50:27 +0300 )edit

The pairing works with the random generated number, the same sequence is shown both on the phone and car UI when initially connecting the phone to the car BT.

I merely want to test if it has an effect to the automatic pairing, just out of curiosity. If the issue is that the phone defaults to (for example) '0000' and that's why it doesn't re-connect automatically. To be honest, I have no idea how this works. :D

raketti ( 2019-08-06 15:01:02 +0300 )edit

Interesting! I never had the chance to enter the car's number in the phone. That's why I tried it the other way round and paired from the phone. In this case, the car lets you enter a number, but the phone doesn't display one. However, it's always 0000.

SagaciousT ( 2019-08-06 15:05:28 +0300 )edit

The phone does connect "automatically" with my car BT, however it takes a (random) long time to establish the connection, between 4 to even 10 minutes.

raketti ( 2019-08-25 12:24:48 +0300 )edit

answered 2019-07-24 08:55:16 +0300

muppis gravatar image

I tested with Volkswagen's RNS 315 (radionavigationsystem with build-in BT) and separate 9W7 -bluetoothmodule. Same behavior in both, after pairing connecting from car to phone fails, but from phone to car works when done manually thru menus. From car to phone, phone shows that connection is made, but drops it in few seconds and RNS 315 shows Telephone connection failed -message.

edit flag offensive delete publish link more

answered 2019-08-07 10:13:31 +0300

DiBasse gravatar image

Asked by me in another thread: Have you tried to connect with Android auto or Mirror link with cable?

edit flag offensive delete publish link more


Android Auto and Mirror Link are not available in my car.

If I'd have Android Auto, I would try to look for Sailfish Auto ;-)

SagaciousT ( 2019-08-07 10:38:29 +0300 )edit

In fact, it wouldn't be bad at all if Sailfish had Mirror Link compatibility! ๐Ÿ‘๐Ÿ‘๐Ÿ‘

mercurio ( 2020-03-12 10:24:45 +0300 )edit

answered 2019-11-24 12:03:55 +0300

SST_73 gravatar image

I had they same problem in my BMW E93. The problem is solved within the latest version :-) Thanks a lot.

edit flag offensive delete publish link more

answered 2019-11-07 21:49:29 +0300

Will-Do gravatar image

Thanks! with your guidance I finally gor my phone connected to my Volvo V60! (connected by making the car visible for bluetooth and searching for it from the phone)

edit flag offensive delete publish link more


chicago limo services administrations is the best limousine administration I have gone over. They work worldwide on the off chance that you were pondering.

LimoservicesinChicagoIllinois ( 2020-01-30 13:26:44 +0300 )edit

Question tools



Asked: 2019-02-07 12:48:28 +0300

Seen: 1,542 times

Last updated: Nov 24 '19