Bluetooth headset profile HSP/HFP doesn't work

Bug #1734960 reported by pl7ofit
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Invalid
Undecided
Unassigned
pulseaudio (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP profile, but when i try change sound profile in blueman-manager to HSP/HFP - then i get error "Failed to change profile to headset_head_unit".
With profile a2dp headphones work good(clementine, chromium etc..), but I could not get work output headphones in steam games, i listen only silence(i think it's problem of pulseaudio)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pl7ofit 3040 F.... pulseaudio
 /dev/snd/controlC1: pl7ofit 3040 F.... pulseaudio
CurrentDesktop: MATE
Date: Tue Nov 28 19:51:59 2017
InstallationDate: Installed on 2016-06-22 (524 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: Bluedio
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pl7ofit 3040 F.... pulseaudio
 /dev/snd/controlC1: pl7ofit 3040 F.... pulseaudio
Symptom_Type: No sound at all
Title: [Bluedio, recording] No sound at all
UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
dmi.bios.date: 07/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: L2.38
dmi.board.name: AM2NF6G-VSTA
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810

Revision history for this message
pl7ofit (pl7ofit) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I agree it sounds like a pulseaudio problem (or a general Bluetooth problem). But that error it seems is specific to blueman so we should keep both options open.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

P.S. I believe in Gnome settings, when profile changes fail (and they do - I agree), Gnome just ignores it and displays the old profile. No error message there, but it feels like the same issue.

Revision history for this message
varacanero (varacanero) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueman (Ubuntu):
status: New → Confirmed
Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can't see any log messages here the same as bug 1576559. But I agree it does sound similar. Most users however don't use blueman, so the error message for the same bug could appear different.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in pulseaudio (Ubuntu):
status: Confirmed → Incomplete
Changed in blueman (Ubuntu):
status: Confirmed → Incomplete
Changed in blueman (Ubuntu):
status: Incomplete → Invalid
Changed in pulseaudio (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
nasatome (nasatome) wrote :

I have a Bluedio F2 headset, I have exactly the same problem in two devices (A2DP works but HSP no), a Lenovo IdeaPad 320-15IKB Laptop with Ubuntu Mate 18.04 and a Desktop Computer with a 6 dollar USB Dongle bought in Gearbest with Ubuntu 18.10. the bug is still active.

I'm not a Linux expert, but both BlueZ (Gnome) and BlueMan have the same problem of not supporting HSP mode

In ubuntu 18.04 I made tests with the application "Ukku" to downgrade the kernel 4.14 and upgrade to version 4.19 thinking that the problem could be out there. (default kernel 4.15)

the headphones Bluedio F2 works correctly on Windows computer and Android phones (Xiaomi RedMi Note 4)

On the same Lenovo computer with Ubuntu Mate 18.04 I have tried a Panasonic SHB4000 headset and if they work properly with the HSP mode and A2DP

I have noticed that the PavuControl application detects the audio input as if it were a "Monitor" or something like that (attach screenshot)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is closed. If you have any problem at all then please open a new bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.