Comment 14 for bug 1500242

Revision history for this message
Uranicus (matthias.ritter) wrote :

One add-on to the Jabra device:

I realized that I have missed to put the "bluetoothctl", "info" data in the report above (1). So I did the same procedure as above again today and acquired the info data. But I also managed to get the info data the second time after I have turned the Jabra off and back on again before it looses connection (2). The difference is that the "ConnectedProfiles:" section is empty:

Information about the Jabra device directly after pairing before I have turned it off and on again:

[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)

Information about the Jabra device after I have turned it off and on again (before it looses connection to the phone):

[JABRA 250]# info
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)

Hope this also helps in finding the issue.