kernel-packages team mailing list archive

Thread
Date
[Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: Uranicus <sliding.paul@xxxxxx>
Date: Wed, 09 Dec 2015 09:20:24 -0000
Reply-to: Bug 1500242 <1500242@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Reporting on Bluetooth bug 1500242

I have send such a report on December, 6th 2015 where I have tested the
rc-proposed with my Jabra device. At that time the syslog-file was
missing which I have added later. I found out later, that syslog is a
rolling log, therefore maybe not all test logs are part of that syslog.

I have taken the time today to retest all that with the following
devices. I attach the log files:

Audi A3 car kit (2012 model)
Seat Alhambra car kit (2012 model)
Jabra BT250 head set
Logitech bluetooth mouse LogiLink ID0078 (Compatible to BT1.1/2.0/3.0+EDR)

Before testing I deleted all existing pairings with the devices and started from scratch.
System Information of the device
Detailed image information of the system used for testing
system-image-cli -i:

current build number: 196
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-12-05 18:28:01
version version: 196
version ubuntu: 20151204.1
version device: 20151028-869191d
version custom: 20151111–36-46-vivid


hciconfig -a

hci0:	Type: BR/EDR  Bus: UART
	BD Address: 4C:74:03:64:75:ED  ACL MTU: 1021:4  SCO MTU: 184:1
	UP RUNNING 
	RX bytes:8537 acl:181 sco:0 events:502 errors:0
	TX bytes:221664 acl:460 sco:0 commands:72 errors:0
	Features: 0xbf 0x3e 0x8d 0xfe 0xdb 0xff 0x5b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH SNIFF 
	Link mode: SLAVE ACCEPT 
	Name: 'Aquaris E4.5 Ubuntu Edition'
	Class: 0x7e0110
	Service Classes: Networking, Rendering, Capturing, Object Transfer, Audio, Telephony
	Device Class: Computer, Handheld
	HCI Version: 4.0 (0x6)  Revision: 0x0
	LMP Version: 4.0 (0x6)  Subversion: 0x0
	Manufacturer: MediaTek, Inc. (70)


bluetoothctl

[NEW] Controller 4C:74:03:64:75:ED Aquaris E4.5 Ubuntu Edition [default]


[bluetooth]# show
Controller 4C:74:03:64:75:ED
	Name: Aquaris E4.5 Ubuntu Edition
	Alias: Aquaris E4.5 Ubuntu Edition
	Class: 0x7e0110
	Powered: yes
	Discoverable: no
	Pairable: yes
	UUIDs:
	  Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	  Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	  A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	  SIM Access                (0000112d-0000-1000-8000-00805f9b34fb)
	  Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	  PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	  A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	  Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	  Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	  Dialup Networking         (00001103-0000-1000-8000-00805f9b34fb)
	  Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	  Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	  Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	  Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0523
	Discovering: no
Modifications on the device (debugging information)
sudo mount -o remount,rw /
Since no bluetooth-override file was available I used:

sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf
sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf
I was not 100% sure about the ofono modifications: “Add '-d' to the exec line in /etc/init/ofono.override”. I have modified the line in ofono.override to:

exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

Audi A3
[bluetooth]# devices

At this time devices shows no results (nothing paired yet).

Audi A3 in search mode and the two found each other:

[bluetooth]# devices
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[NEW] Device 00:0E:9F:E8:3A:24 Audi UHV 4272           
[CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -49
[CHG] Controller 4C:74:03:64:75:ED Discoverable: no

Connect Audi A3 with the phone (manually press the connect button in the
bluetooth menue):

[bluetooth]# 
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -67
[bluetooth]# 
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -52
[CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes

8:58 h: Enter the pairing code 1234 (nothing happens)

9:00 h: Enter pairing code a second time

[CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -62
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -54
[CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -54

Get more info of the Audi device with info-command

[bluetooth]# info 00:0E:9F:E8:3A:24
Device 00:0E:9F:E8:3A:24
	Name: Audi UHV 4272           
	Alias: Audi UHV 4272           
	Class: 0x200408
	Icon: audio-card
	Paired: no
	Trusted: no
	Blocked: no
	Connected: no
	ConnectedProfiles:
	  None
	LegacyPairing: yes
	UUIDs:
	  None
	RSSI: -61

I got no connection, I stopped there. 
Seat Alhambra
9:14 h start pairing process

Seat proposes a pin to confirm both on the phone and in the car.

[NEW] Controller 4C:74:03:64:75:ED Aquaris E4.5 Ubuntu Edition [default]
[NEW] Device 00:0E:9F:E8:3A:24 Audi UHV 4272           
[NEW] Device 90:03:B7:46:8E:E9 SEAT_BT
[CHG] Device 90:03:B7:46:8E:E9 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Device 90:03:B7:46:8E:E9 Connected: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 90:03:B7:46:8E:E9 Modalias: bluetooth:v0043pE001d0144
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001107-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 Paired: yes
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001107-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110d-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001107-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110d-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 90:03:B7:46:8E:E9 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes

Works like it should more or less automatically.

[SEAT_BT]# info
Device 90:03:B7:46:8E:E9
	Name: SEAT_BT
	Alias: SEAT_BT
	Class: 0x340408
	Icon: audio-card
	Paired: yes
	Trusted: no
	Blocked: no
	Connected: yes
	ConnectedProfiles:
	  None
	LegacyPairing: no
	UUIDs:
	  Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
	  OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	  OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	  IrMC Sync Command         (00001107-0000-1000-8000-00805f9b34fb)
	  Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	  Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	  Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	  A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	  Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
	  A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	  PANU                      (00001115-0000-1000-8000-00805f9b34fb)
	  Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	  Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	  PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	Modalias: bluetooth:v0043pE001d0144

Jabra headset

9:19 h start to pair Jabra headset, put headset in discovery mode

bluetoothctl 
[NEW] Controller 4C:74:03:64:75:ED Aquaris E4.5 Ubuntu Edition [default]
[NEW] Device 90:03:B7:46:8E:E9 SEAT_BT
[NEW] Device 00:0E:9F:E8:3A:24 Audi UHV 4272           
[NEW] Device 00:07:A4:00:A7:05 JABRA 250
[CHG] Device 00:07:A4:00:A7:05 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:07:A4:00:A7:05 RSSI: -52

9:20 h pairing, no pin required

[CHG] Device 00:07:A4:00:A7:05 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Device 00:07:A4:00:A7:05 Connected: yes
[CHG] Device 00:07:A4:00:A7:05 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 Paired: yes
[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 Trusted: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes

[JABRA 250]# info
Device 00:07:A4:00:A7:05
	Name: JABRA 250
	Alias: JABRA 250
	Class: 0x200404
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	ConnectedProfiles:
	  Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	  Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	LegacyPairing: yes
	UUIDs:
	  Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	  Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)

After this the Jabra changed from search mode into operational mode.
This is how the bluetooth window looked like after the pairing process
(correct symbol of the head set):


I can place calls and receive calls. I can end the calls with the button on the bluetooth device.

9:21 h turn off Jabra

[CHG] Controller 4C:74:03:64:75:ED Discoverable: no
[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 Connected: no

9:22 h turn Jabra back on. I expect that the device automatically
reconnects to the phone. So first I did nothing just waiting.

[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 Connected: no
[CHG] Device 00:07:A4:00:A7:05 Class: 0x20040c
[CHG] Device 00:07:A4:00:A7:05 Icon: audio-card
[CHG] Device 00:07:A4:00:A7:05 Connected: yes

[JABRA 250]# info 00:07:A4:00:A7:05
Device 00:07:A4:00:A7:05
	Name: JABRA 250
	Alias: JABRA 250
	Class: 0x20040c
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	ConnectedProfiles:
	  None
	LegacyPairing: yes
	UUIDs:
	  Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	  Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)

There is a short period where the device is connected where I was able
to place the info command on it but shortly thereafter it was
disconnected.

[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes
[CHG] Device 00:07:A4:00:A7:05 Connected: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes

[JABRA 250]# info 00:07:A4:00:A7:05
Device 00:07:A4:00:A7:05
	Name: JABRA 250
	Alias: JABRA 250
	Class: 0x20040c
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	ConnectedProfiles:
	  None
	LegacyPairing: yes
	UUIDs:
	  Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	  Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)


I was also not able to manually reconnect it.
The bluetooth window looked like the following (see the changed symbol!):

The window of the Jabra device looked like:




Logitec Bluetooth Mouse
This device worked once with the following rc version:

I did the test with the following rc-proposed version:
current build number: 191
device name: krillin
channel: ubuntu-
last update: 2015-11-30 17:03:26
version version: 191
version ubuntu: 20151130
version device: 20151028-869191d
version custom: 20151111-

Today I tried it again to complete the test and I got a different
behaviour:

9:27 h turn mouse on

[NEW] Device 00:80:00:00:15:76 Bluetooth Mouse
[CHG] Device 00:80:00:00:15:76 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:80:00:00:15:76 RSSI: -42

Mouse not yet connected but shown in bluetooth overview of the phone

9:29 h press connect on the phone:

[CHG] Device 00:80:00:00:15:76 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discoverable: no

not connected

allow trusted on phone and press connect on phone again:

[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Trusted: yes
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no

again press (manually) connect on the phone

[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no
[CHG] Device 00:80:00:00:15:76 Connected: yes
[CHG] Device 00:80:00:00:15:76 Connected: no

no result – but it did work before with r191

try to remove Jabra & Audi profile from phone via the bluetooth phone
menue to see if this has an effect, but I am not able to remove the Audi
profile from the phone (the “delete profile” button is grayed out)

[DEL] Device 00:07:A4:00:A7:05 JABRA 250
[CHG] Device 00:0E:9F:E8:3A:24 Trusted: yes

now forced by console:

[bluetooth]# remove 00:0E:9F:E8:3A:24
[DEL] Device 00:0E:9F:E8:3A:24 Audi UHV 4272           
Device has been removed
[CHG] Controller 4C:74:03:64:75:ED Discovering: no

This caused a crash of the bluetooth application on the phone. I had to
completely stop the bluetooth device (via the bluetooth menue in the
phone (system settings) and restart bluetooth on the phone.

[CHG] Controller 4C:74:03:64:75:ED Class: 0x000000
[CHG] Controller 4C:74:03:64:75:ED Powered: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Powered: yes
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no

9:42 h, again try to reactivate mouse

[bluetooth]# info 00:80:00:00:15:76
Device 00:80:00:00:15:76
	Name: Bluetooth Mouse
	Alias: Bluetooth Mouse
	Class: 0x002580
	Icon: input-mouse
	Paired: no
	Trusted: yes
	Blocked: no
	Connected: no
	ConnectedProfiles:
	  None
	LegacyPairing: yes
	UUIDs:
	  None

In the short moments when mouse is connected info says:

[Bluetooth Mouse]# info 00:80:00:00:15:76
Device 00:80:00:00:15:76
	Name: Bluetooth Mouse
	Alias: Bluetooth Mouse
	Class: 0x002580
	Icon: input-mouse
	Paired: no
	Trusted: yes
	Blocked: no
	Connected: yes
	ConnectedProfiles:
	  None
	LegacyPairing: yes
	UUIDs:
	  None

9:44 h, Pull log files for reporting

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1500242

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions
References

[Bug 1500242] [NEW] Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
From: Uranicus, 2015-09-27