Created attachment 1650957 [details] journalctl -xe --no-pager > bluetooth_^Cadset_failure.log Description of problem: Headset microphone never recognizes sound. Version-Release number of selected component (if applicable): rpm -qa | grep bluetooth NetworkManager-bluetooth-1.20.8-1.fc31.x86_64 gnome-shell-extension-remove-bluetooth-icon-0.5.1-11.fc31.noarch gnome-bluetooth-3.34.0-1.fc31.x86_64 gnome-bluetooth-libs-3.34.0-1.fc31.x86_64 pulseaudio-module-bluetooth-13.0-1.fc31.x86_64 rpm -qa | grep bluez bluez-5.52-1.fc31.x86_64 bluez-hid2hci-5.52-1.fc31.x86_64 bluez-libs-5.52-1.fc31.x86_64 bluez-tools-0.2.0-0.11.git20170912.7cb788c.fc31.x86_64 bluez-obexd-5.52-1.fc31.x86_64 bluez-cups-5.52-1.fc31.x86_64 bluez-hcidump-2.5-14.fc31.x86_64 rpm -qa | grep pulseaudio alsa-plugins-pulseaudio-1.2.1-1.fc31.x86_64 pulseaudio-13.0-1.fc31.x86_64 pulseaudio-libs-13.0-1.fc31.x86_64 pulseaudio-module-bluetooth-13.0-1.fc31.x86_64 pulseaudio-module-x11-13.0-1.fc31.x86_64 pulseaudio-libs-glib2-13.0-1.fc31.x86_64 pulseaudio-utils-13.0-1.fc31.x86_64 How reproducible: 100% Steps to Reproduce: 1. Headset connects. Output is A2DP and it works fine 2. Select headset as Input and Output goes to Mono but the Input never recognizes sound. 3. Actual results: Microphone does not recognize soune Expected results: Microphone accept sound Additional info: The headset is a Sennheiser MB 660 MS The headset worked fine on Fedora 29 before "upgrade" to Fedora 31 The headset wtill works fine with Android mobile phone.
With some further analysis, I've determined a reliable, albeit inconvenient, method to make this work. 1. Connect the headset via bluetooth 2. In gnome sound settings, select the headset as the output device 3. Select the Output Configuration "Headset Head Unit (HSP/HFP)" 4. Select the Headset as the Input Device I've tested 3 times, even disabling and re-enabling Bluetooth once, and it works 100% of the time. On Fedora 29, when I received a softphone call and did not have the headset on, I could turn it on and accept the call. Now I'm unable to do that because it requires the steps above or requires me to have the headset on all the time. Is there any way to configure bluetooth and sound settings to default to the desired operation? This would be: When headset connects, select it as the output device in the "HSP" configuration and select the headset mic as the input.
These issues are resolved in the current git of pulseaudio. I've built RPMs from F31 srpm with mods for building from current git clone. All works as expected with restore_bluetooth_profile=1. I haven't noticed any new issues or side effects.
This problem is still present in F32, pulseaudio-module-bluetooth-13.99.1-3.fc32.x86_64. From pacmd list-cards, for this headset I get: index: 3 name: <bluez_card.E8_07_BF_82_79_37> driver: <module-bluez5-device.c> owner module: 27 properties: device.description = "SoundBuds Slim" device.string = "E8:07:BF:82:79:37" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_E8_07_BF_82_79_37" bluez.class = "0x240404" bluez.alias = "SoundBuds Slim" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" profiles: a2dp_sink_sbc: High Fidelity Playback (A2DP Sink: SBC) (priority 40, available: unknown) a2dp_sink_aac: High Fidelity Playback (A2DP Sink: AAC) (priority 40, available: yes) a2dp_sink_aptx: High Fidelity Playback (A2DP Sink: aptX) (priority 40, available: no) a2dp_sink_aptx_hd: High Fidelity Playback (A2DP Sink: aptX HD) (priority 40, available: no) a2dp_sink_ldac: High Fidelity Playback (A2DP Sink: LDAC) (priority 40, available: no) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: <a2dp_sink_aac> sinks: bluez_sink.E8_07_BF_82_79_37.a2dp_sink/#4: SoundBuds Slim sources: bluez_sink.E8_07_BF_82_79_37.a2dp_sink.monitor/#5: Monitor of SoundBuds Slim ports: headset-output: Headset (priority 0, latency offset 0 usec, available: yes) properties: headset-input: Headset (priority 0, latency offset 0 usec, available: no) properties: From "Headset Head Unit (HSP/HFP) (priority 30, available: no)", is there some codec missing? In Gnome Settings/Sound, I can select the HSP/HFP profile, but it never 'takes' -- in fact it's ignored. Only A2DP works. The headset is never available as an input.
James - I've been running successfully with 13.99 for several weeks. The issue you are having is definitely not the same one I originally reported. Perhaps check the settings specified in https://unix.stackexchange.com/questions/407447/how-to-force-a2dp-sink-when-wireless-bluetooth-headset-is-connected and google for additional hints if that is not helpful Once you have both profiles enabled, make sure you set load-module module-card-restore restore_bluetooth_profile=1 in /etc/pulse/default.pa
James I have the same issue, I wonder if https://bugzilla.redhat.com/show_bug.cgi?id=1311238#c49 is more relevant
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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' of '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still valid, see also: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227#note_705053
today I tested pipewire-pulseaudio 3.20 and looks like everything is resolved for bluetooth support. Attached screenshot. So if everything goes well and Fedora replaces pulseaudio with pipewire: we can consider this as resolved. https://pagure.io/fedora-docs/release-notes/issue/611 https://bugzilla.redhat.com/show_bug.cgi?id=1906086 https://fedoraproject.org/wiki/Changes/DefaultPipeWire https://gitlab.freedesktop.org/pipewire/pipewire/-/tags/0.3.20
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
FEDORA-2021-2c994d0609 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2c994d0609
FEDORA-2021-2c994d0609 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2c994d0609` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2c994d0609 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-2c994d0609 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.