Red Hat Bugzilla – Bug 1019509
Bluetooth headset does not offer HSP/HFP modus
Last modified: 2015-06-29 08:38:58 EDT
Description of problem:
My Samsung HM1700 headset currently only offers A2DP as bluetooth profile, no HFP/HSP profile. That means of course that i'm only able to hear but not record any sound. This makes phone application useless.
Version-Release number of selected component (if applicable):
Version : 5.9
Release : 4.fc20
Steps to Reproduce:
1. Pair headset
2. Show supported profiles in GNOME control center or using pacmd in command line.
Lists only A2DP profile.
Lists A2DP profile *and* HFP/HSP.
owner module: 25
device.description = "HM1700"
device.string = "50:A4:C8:AA:81:92"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_50_A4_C8_AA_81_92"
bluez.class = "0x240404"
bluez.alias = "HM1700"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
a2dp: High Fidelity Playback (A2DP Sink) (priority 10, available: unknown)
off: Aus (priority 0, available: yes)
active profile: <a2dp>
bluez_sink.50_A4_C8_AA_81_92.monitor/#3: Monitor of HM1700
headset-output: Headset (priority 0, latency offset 0 usec, available: unknown)
headset-input: Headset (priority 0, latency offset 0 usec, available: no)
Also for Logitech Bluetooth headphone on F20 -- I can use it in A2DP mode to listen, but no option to use in headset mode (i.e. no mic).
This is a regression from previous Fedora versions, where this headset worked fine.
Reproduced on F20 with bluez-5.18-1.fc20.x86_64 using a Jawbone Era and a Rocketfish RF-MAB2. Both worked in F19.
Same here. It use to work in a previous Fedora release. Just tried it now after maybe a year. A2DP works fine, but no option for HSP/HFP. Also tried pavucontrol.
Plantronics Pulsar 590A
Unfortunately... this is expected.
Bluez 5.0 removed support for HSP/HFP and expects a 3rd party plugin to support it.
Pulseaudio finally has support for HSP, works fine with F21 and backported with F20. See #1045548
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.