Bluetooth Headphones switches from (A2DP sink) to (HSP/HFP) when starting VoIP application
since a few weeks I have some (more) trouble with my bluetooth headphones Sony WH-H900-N in Ubuntu 18.04 (but also in Linux Mint). It is a headphone with noice cancellation feature. So it does have a microphone for this purpose, but I doubt that it is good enough to use as input for VoIP applications. Instead I would like to use a webcam as microphone input.
So here are my problems:
-I am able to connect the headphones more or less properly, but I have to manually pair it in every session and manually set it to A2DP profile. Using this annoying workaround it works as an high quality audio sink.
-Whenever I connect to any VoIP application (Telegram call, connect to TeamSpeak Server, Skype) for some reason it automatically switches from A2DP audio sink profile to Headset Head Unit (HSP/HFP) Profile. The result is, that I can not hear anything anymore. Neither system sounds, nor the audio from the voice call. People hear me talking though and it seems like the correct microphone is used as input (the webcam, NOT the microphone from the headphones).
Strangely I had no problems with calls until some weeks ago. And this is true for two different systems (Ubuntu, Linux Mint). So I guess there was some recent common update that causes the problems.
Does anybody know how I can fix this issue? To me it seems like permanently setting the headphones as A2DP audio sink and permanently setting the webcam as default microphone input could solve this. But I am not sure how this noice cancellation thing interacts with all this. Plus I don't know how to set things up permanently and I read terrible stories of people trying to manually mess with pulseaudio :)
Any help is appreciated!
bluetooth voip a2dp
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
add a comment |
since a few weeks I have some (more) trouble with my bluetooth headphones Sony WH-H900-N in Ubuntu 18.04 (but also in Linux Mint). It is a headphone with noice cancellation feature. So it does have a microphone for this purpose, but I doubt that it is good enough to use as input for VoIP applications. Instead I would like to use a webcam as microphone input.
So here are my problems:
-I am able to connect the headphones more or less properly, but I have to manually pair it in every session and manually set it to A2DP profile. Using this annoying workaround it works as an high quality audio sink.
-Whenever I connect to any VoIP application (Telegram call, connect to TeamSpeak Server, Skype) for some reason it automatically switches from A2DP audio sink profile to Headset Head Unit (HSP/HFP) Profile. The result is, that I can not hear anything anymore. Neither system sounds, nor the audio from the voice call. People hear me talking though and it seems like the correct microphone is used as input (the webcam, NOT the microphone from the headphones).
Strangely I had no problems with calls until some weeks ago. And this is true for two different systems (Ubuntu, Linux Mint). So I guess there was some recent common update that causes the problems.
Does anybody know how I can fix this issue? To me it seems like permanently setting the headphones as A2DP audio sink and permanently setting the webcam as default microphone input could solve this. But I am not sure how this noice cancellation thing interacts with all this. Plus I don't know how to set things up permanently and I read terrible stories of people trying to manually mess with pulseaudio :)
Any help is appreciated!
bluetooth voip a2dp
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
I have a similar problem under Kubuntu 18.04 with the difference that I always get HSP/HFP even if there is no VoIP application active. I have to manually switch to A2DP. Have you found a solution?
– sola
Dec 18 '18 at 9:00
add a comment |
since a few weeks I have some (more) trouble with my bluetooth headphones Sony WH-H900-N in Ubuntu 18.04 (but also in Linux Mint). It is a headphone with noice cancellation feature. So it does have a microphone for this purpose, but I doubt that it is good enough to use as input for VoIP applications. Instead I would like to use a webcam as microphone input.
So here are my problems:
-I am able to connect the headphones more or less properly, but I have to manually pair it in every session and manually set it to A2DP profile. Using this annoying workaround it works as an high quality audio sink.
-Whenever I connect to any VoIP application (Telegram call, connect to TeamSpeak Server, Skype) for some reason it automatically switches from A2DP audio sink profile to Headset Head Unit (HSP/HFP) Profile. The result is, that I can not hear anything anymore. Neither system sounds, nor the audio from the voice call. People hear me talking though and it seems like the correct microphone is used as input (the webcam, NOT the microphone from the headphones).
Strangely I had no problems with calls until some weeks ago. And this is true for two different systems (Ubuntu, Linux Mint). So I guess there was some recent common update that causes the problems.
Does anybody know how I can fix this issue? To me it seems like permanently setting the headphones as A2DP audio sink and permanently setting the webcam as default microphone input could solve this. But I am not sure how this noice cancellation thing interacts with all this. Plus I don't know how to set things up permanently and I read terrible stories of people trying to manually mess with pulseaudio :)
Any help is appreciated!
bluetooth voip a2dp
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
since a few weeks I have some (more) trouble with my bluetooth headphones Sony WH-H900-N in Ubuntu 18.04 (but also in Linux Mint). It is a headphone with noice cancellation feature. So it does have a microphone for this purpose, but I doubt that it is good enough to use as input for VoIP applications. Instead I would like to use a webcam as microphone input.
So here are my problems:
-I am able to connect the headphones more or less properly, but I have to manually pair it in every session and manually set it to A2DP profile. Using this annoying workaround it works as an high quality audio sink.
-Whenever I connect to any VoIP application (Telegram call, connect to TeamSpeak Server, Skype) for some reason it automatically switches from A2DP audio sink profile to Headset Head Unit (HSP/HFP) Profile. The result is, that I can not hear anything anymore. Neither system sounds, nor the audio from the voice call. People hear me talking though and it seems like the correct microphone is used as input (the webcam, NOT the microphone from the headphones).
Strangely I had no problems with calls until some weeks ago. And this is true for two different systems (Ubuntu, Linux Mint). So I guess there was some recent common update that causes the problems.
Does anybody know how I can fix this issue? To me it seems like permanently setting the headphones as A2DP audio sink and permanently setting the webcam as default microphone input could solve this. But I am not sure how this noice cancellation thing interacts with all this. Plus I don't know how to set things up permanently and I read terrible stories of people trying to manually mess with pulseaudio :)
Any help is appreciated!
bluetooth voip a2dp
bluetooth voip a2dp
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
asked Oct 20 '18 at 9:15
UbuntuNoobUbuntuNoob
265
265
I have a similar problem under Kubuntu 18.04 with the difference that I always get HSP/HFP even if there is no VoIP application active. I have to manually switch to A2DP. Have you found a solution?
– sola
Dec 18 '18 at 9:00
add a comment |
I have a similar problem under Kubuntu 18.04 with the difference that I always get HSP/HFP even if there is no VoIP application active. I have to manually switch to A2DP. Have you found a solution?
– sola
Dec 18 '18 at 9:00
I have a similar problem under Kubuntu 18.04 with the difference that I always get HSP/HFP even if there is no VoIP application active. I have to manually switch to A2DP. Have you found a solution?
– sola
Dec 18 '18 at 9:00
I have a similar problem under Kubuntu 18.04 with the difference that I always get HSP/HFP even if there is no VoIP application active. I have to manually switch to A2DP. Have you found a solution?
– sola
Dec 18 '18 at 9:00
add a comment |
1 Answer
1
active
oldest
votes
Been having this problem for months. Finally got around to googling for a solution and I found this answer on the arch linux forums (from user v1del):
From pulseaudio 10.0 release notes:
Pulse release notes wrote: Bluetooth headsets typically support both
the A2DP profile, which is suitable for music, and the HSP profile,
which is suitable for telephony use cases. module-bluetooth-policy
will now automatically switch the profile of a Bluetooth headset from
A2DP to HSP/HFP when an application creates a recording stream with
property media.role=phone (telephony applications should set that
property for their streams). When the stream goes away, the profile
gets restored back to A2DP. This way the user doesn't have to manually
switch the profiles when starting and stopping a call. This behaviour
can be disabled by giving argument auto_switch=false to
module-bluetooth-policy.
answered 9 hours ago
user1412135user1412135
111
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1085480%2fbluetooth-headphones-switches-from-a2dp-sink-to-hsp-hfp-when-starting-voip-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Been having this problem for months. Finally got around to googling for a solution and I found this answer on the arch linux forums (from user v1del):
From pulseaudio 10.0 release notes:
Pulse release notes wrote: Bluetooth headsets typically support both
the A2DP profile, which is suitable for music, and the HSP profile,
which is suitable for telephony use cases. module-bluetooth-policy
will now automatically switch the profile of a Bluetooth headset from
A2DP to HSP/HFP when an application creates a recording stream with
property media.role=phone (telephony applications should set that
property for their streams). When the stream goes away, the profile
gets restored back to A2DP. This way the user doesn't have to manually
switch the profiles when starting and stopping a call. This behaviour
can be disabled by giving argument auto_switch=false to
module-bluetooth-policy.
answered 9 hours ago
user1412135user1412135
111
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Been having this problem for months. Finally got around to googling for a solution and I found this answer on the arch linux forums (from user v1del):
From pulseaudio 10.0 release notes:
Pulse release notes wrote: Bluetooth headsets typically support both
the A2DP profile, which is suitable for music, and the HSP profile,
which is suitable for telephony use cases. module-bluetooth-policy
will now automatically switch the profile of a Bluetooth headset from
A2DP to HSP/HFP when an application creates a recording stream with
property media.role=phone (telephony applications should set that
property for their streams). When the stream goes away, the profile
gets restored back to A2DP. This way the user doesn't have to manually
switch the profiles when starting and stopping a call. This behaviour
can be disabled by giving argument auto_switch=false to
module-bluetooth-policy.
answered 9 hours ago
user1412135user1412135
111
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Been having this problem for months. Finally got around to googling for a solution and I found this answer on the arch linux forums (from user v1del):
From pulseaudio 10.0 release notes:
Pulse release notes wrote: Bluetooth headsets typically support both
the A2DP profile, which is suitable for music, and the HSP profile,
which is suitable for telephony use cases. module-bluetooth-policy
will now automatically switch the profile of a Bluetooth headset from
A2DP to HSP/HFP when an application creates a recording stream with
property media.role=phone (telephony applications should set that
property for their streams). When the stream goes away, the profile
gets restored back to A2DP. This way the user doesn't have to manually
switch the profiles when starting and stopping a call. This behaviour
can be disabled by giving argument auto_switch=false to
module-bluetooth-policy.
answered 9 hours ago
user1412135user1412135
111
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Been having this problem for months. Finally got around to googling for a solution and I found this answer on the arch linux forums (from user v1del):
From pulseaudio 10.0 release notes:
Pulse release notes wrote: Bluetooth headsets typically support both
the A2DP profile, which is suitable for music, and the HSP profile,
which is suitable for telephony use cases. module-bluetooth-policy
will now automatically switch the profile of a Bluetooth headset from
A2DP to HSP/HFP when an application creates a recording stream with
property media.role=phone (telephony applications should set that
property for their streams). When the stream goes away, the profile
gets restored back to A2DP. This way the user doesn't have to manually
switch the profiles when starting and stopping a call. This behaviour
can be disabled by giving argument auto_switch=false to
module-bluetooth-policy.
answered 9 hours ago
user1412135user1412135
111
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 9 hours ago
user1412135user1412135
111
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 9 hours ago
user1412135user1412135
111
answered 9 hours ago
user1412135user1412135
111
111
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user1412135 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1085480%2fbluetooth-headphones-switches-from-a2dp-sink-to-hsp-hfp-when-starting-voip-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have a similar problem under Kubuntu 18.04 with the difference that I always get HSP/HFP even if there is no VoIP application active. I have to manually switch to A2DP. Have you found a solution?
– sola
Dec 18 '18 at 9:00