Hi all, This might be a viewed as a fire torch, but there is, IMO, a major regression in BlueZ 5 which is shipped in Fedora 20. It doesn't support HSP/HFP headset profiles, which enables the microphone on many bluetooth headsets. It's already tracked in this BZ: <https://bugzilla.redhat.com/show_bug.cgi?id=1045548> It seems a solution for BlueZ 5 isn't close, especially not for F20. Upstream is looking at this issue, but not much news have been told yet: <https://bugs.freedesktop.org/show_bug.cgi?id=73325> Anyhow, not supporting HSP/HSP profiles is at least hitting my work ability, and I doubt I'm alone in this situation. Now, if I had known this before I started upgrading to F20, I wouldn't have upgraded yet but stayed on F19 a bit longer. However, that's too late now. This was first listed as a "common bug" about three weeks after the release. So, I wonder if it can be considered to enable a "downgrade path" for bluez and depending packages, as described in the "Contingency Plan": <https://fedoraproject.org/wiki/Changes/Bluez5> The other alternative is to tell users to re-install Fedora 19, which I doubt is such a good alternative in the long run. But I need to consider that if BlueZ isn't downgraded somehow. As a side note, it also needs to be discussed how such a key feature of the bluetooth stack could go unnoticed through QA, and how to avoid this from happening again. -- kind regards, David Sommerseth -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
