REPRODUCIBILITY: 100%
OS VERSION: 4.4.0.68
HARDWARE: X10 III
UI LANGUAGE: Polish, English
REGRESSION:
DESCRIPTION:
OS 4.4.0.68 has broken pairing with older Bluetooth car kits from the UI (request to enter the pairing code does not appear, so pairing fails). Those car kits have a hardcoded “1234” pairing code which has to be entered on the phone, or else pairing fails. I had to pair it manually via the terminal using bluetoothctl
(which worked fine as it did request me to input the pairing code) and only this way I was able to pair it. But even when paired (the phone appears in the car kit’s list of paired devices), the phone is then unable to connect to the car kit. All attempts to establish the connection (initiated from either the phone’s and the car kit’s side) fail. They connect for a fraction of second and disconnect. See bluetoothctl
output below.
There shouldn’t be such problems with such a simple car kit (only HFP, HSP, SYNC and PBAP profiles). This is the ONLY case of a device that’s unable to connect, all other smartphones of mine (ranging from as old as the Nokia N900, Blackberry Z10, Blackberry Passport, to recent iPhones) pair and connect just fine with it.
I have two Citroen cars with two identical car kits, tried with both, same result. In one of them I have XA2 Ultra with SFOS paired and actively used, but pairing was done when the phone was on 4.3 OS. Now with 4.4.0.68 OS, I cannot pair the XA2 with the other identical car kit, either. So it’s not a X10 III problem but rather 4.4 OS problem.
As I also have 3 more spare car kit units (as spare parts, each of them having different HW and SW version, and even different manufacturers: Siemens and Continental), I tested it with all three of them, too. Same results, on five units in total.
PRECONDITIONS:
STEPS TO REPRODUCE:
-
Have a Bluetooth car kit, like the one that I have (Citroen/Peugeot KML, which is Parrot based)
-
Have a SFOS 4.4.0.68 phone like the XA2U or the X10 III
-
Try to pair them
-
You can’t because the Bluetooth Settings UI isn’t asking you to enter the required pairing code (i.e. 1234 which is hardcoded in those car kit units).
-
Use
bluetoothctl
in the Terminal instead, which does allow entering the pairing code, so pairing succeeds and your phone is now listed on your car kit’s list of paired devices -
Try to connect. Failure each single time. Bluetoothctl output shows that it does connect for a fraction of second, but connection is instantly dropped tike this:
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
EXPECTED RESULT:
It should be asking for the pairing code via the UI or else it is not possible to pair it without using bluetoothctl
via the terminal. And then it should normally connect.
ACTUAL RESULT:
It doesn’t ask for the pairing code, so pairing via Bluetooth Settings UI always fails and one has to use bluetoothctl
via the terminal to pair it. But even when successfully paired this way, it is then unable to connect.
MODIFICATIONS:
None. Fresh X10 III.
ADDITIONAL INFORMATION:
I attach output from bluetoothctl
showing pairing progress and then failed connection attempts.
[root@Xperia10III defaultuser]# bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 3C:38:F4:13:86:7C Discovering: yes
[NEW] Device 00:03:19:01:DE:2D CITROEN
[bluetooth]# pair 00:03:19:01:DE:2D
Attempting to pair with 00:03:19:01:DE:2D
Request PIN code
[agent] Enter PIN code: 1234
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D UUIDs: 00001107-0000-1000-8000-00805f9b34fb
[CHG] Device 00:03:19:01:DE:2D UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:03:19:01:DE:2D UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
[CHG] Device 00:03:19:01:DE:2D Paired: yes
Pairing successful
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Trusted: yes
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[bluetooth]# trust 00:03:19:01:DE:2D
Changing 00:03:19:01:DE:2D trust succeeded
[CHG] Device 00:03:19:01:DE:2D RSSI: -39
[bluetooth]# pair 00:03:19:01:DE:2D
Attempting to pair with 00:03:19:01:DE:2D
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# connect 00:03:19:01:DE:2D
Attempting to connect to 00:03:19:01:DE:2D
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[bluetooth]# connect 00:03:19:01:DE:2D
Attempting to connect to 00:03:19:01:DE:2D
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[bluetooth]# connect 00:03:19:01:DE:2D
Attempting to connect to 00:03:19:01:DE:2D
[CHG] Device 00:03:19:01:DE:2D RSSI: -47
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D RSSI is nil
[CHG] Controller 3C:38:F4:13:86:7C Class: 0x00000000
[CHG] Controller 3C:38:F4:13:86:7C Powered: no
[CHG] Controller 3C:38:F4:13:86:7C Discovering: no
[CHG] Controller 3C:38:F4:13:86:7C Class: 0x001c020c
[CHG] Controller 3C:38:F4:13:86:7C Powered: yes
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CITROEN]# trust 00:03:19:01:DE:2D
Changing 00:03:19:01:DE:2D trust succeeded
[CITROEN]# connect 00:03:19:01:DE:2D
Attempting to connect to 00:03:19:01:DE:2D
[CHG] Device 00:03:19:01:DE:2D Connected: no
Failed to connect: org.bluez.Error.Failed
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CITROEN]# scan on
Discovery started
[CHG] Controller 3C:38:F4:13:86:7C Discovering: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D RSSI: -44
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D Trusted: no
[CHG] Device 00:03:19:01:DE:2D Trusted: yes
[CHG] Controller 3C:38:F4:13:86:7C Alias: Xperia 10 III
[CITROEN]# connect 00:03:19:01:DE:2D
Attempting to connect to 00:03:19:01:DE:2D
[CHG] Controller 3C:38:F4:13:86:7C Class: 0x00000000
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Controller 3C:38:F4:13:86:7C Powered: no
[CHG] Controller 3C:38:F4:13:86:7C Discovering: no
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Device 00:03:19:01:DE:2D RSSI is nil
[CHG] Controller 3C:38:F4:13:86:7C Class: 0x001c020c
[CHG] Controller 3C:38:F4:13:86:7C Powered: yes
[CHG] Device 00:03:19:01:DE:2D Connected: yes
[CHG] Controller 3C:38:F4:13:86:7C Class: 0x00000000
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: yes
[CHG] Device 00:03:19:01:DE:2D ServicesResolved: no
[CHG] Device 00:03:19:01:DE:2D Connected: no
[CHG] Controller 3C:38:F4:13:86:7C Powered: no
[CHG] Controller 3C:38:F4:13:86:7C Discovering: no
[bluetooth]#
Controller 3C:38:F4:13:86:7C (public)
Name:
Alias: Xperia 10 III
Class: 0x001c020c
Powered: yes
Discoverable: yes
DiscoverableTimeout: 0x00000000
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d053A
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
Device 00:03:19:01:DE:2D (public)
Name: CITROEN
Alias: CITROEN
Class: 0x00300408
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: yes
UUID: IrMC Sync Command (00001107-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Device 00:80:37:1F:4C:F6 (public)
Name: C2
Alias: C2
Class: 0x00200408
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: yes
UUID: IrMC Sync Command (00001107-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)