Comment 20 for bug 1574324

Revision history for this message
Joakim Koed (vooze) wrote :

Sure. It works now (for me) using the method I mentioned.

 name: <bluez_card.44_5E_F3_B5_64_94>
 driver: <module-bluez5-device.c>
 owner module: 26
 properties:
  device.description = "Jaybird X2"
  device.string = "44:5E:F3:B5:64:94"
  device.api = "bluez"
  device.class = "sound"
  device.bus = "bluetooth"
  device.form_factor = "headset"
  bluez.path = "/org/bluez/hci0/dev_44_5E_F3_B5_64_94"
  bluez.class = "0x240404"
  bluez.alias = "Jaybird X2"
  device.icon_name = "audio-headset-bluetooth"
  device.intended_roles = "phone"
 profiles:
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 20, available: unknown)
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 10, available: unknown)
  off: Off (priority 0, available: yes)
 active profile: <headset_head_unit>
 sinks:
  bluez_sink.44_5E_F3_B5_64_94/#2: Jaybird X2
 sources:
  bluez_sink.44_5E_F3_B5_64_94.monitor/#3: Monitor of Jaybird X2
  bluez_source.44_5E_F3_B5_64_94/#4: Jaybird X2
 ports:
  headset-output: Headset (priority 0, latency offset 0 usec, available: unknown)
   properties:

  headset-input: Headset (priority 0, latency offset 0 usec, available: unknown)
   properties:

Hope this helps :)