Headphones microphone is not working
I'm trying to use my headphones with my Ubuntu 13.10. My headphones are Nokia BH-905i, which can be connected via Bluetooth or green+pink wires.
If I use bluetooth, voice quality is terrible or microphone doesn't work. If I try to choose "Headset" option from In and Out tabs in Sound Settings, they're disabling each together.
In Out tab, I'm using "High sound quality A2DP", because it betters voice quality.
How could I get my microphone working? Sound out works fine.
sound bluetooth microphone headphones 13.10
add a comment |
I'm trying to use my headphones with my Ubuntu 13.10. My headphones are Nokia BH-905i, which can be connected via Bluetooth or green+pink wires.
If I use bluetooth, voice quality is terrible or microphone doesn't work. If I try to choose "Headset" option from In and Out tabs in Sound Settings, they're disabling each together.
In Out tab, I'm using "High sound quality A2DP", because it betters voice quality.
How could I get my microphone working? Sound out works fine.
sound bluetooth microphone headphones 13.10
add a comment |
I'm trying to use my headphones with my Ubuntu 13.10. My headphones are Nokia BH-905i, which can be connected via Bluetooth or green+pink wires.
If I use bluetooth, voice quality is terrible or microphone doesn't work. If I try to choose "Headset" option from In and Out tabs in Sound Settings, they're disabling each together.
In Out tab, I'm using "High sound quality A2DP", because it betters voice quality.
How could I get my microphone working? Sound out works fine.
sound bluetooth microphone headphones 13.10
I'm trying to use my headphones with my Ubuntu 13.10. My headphones are Nokia BH-905i, which can be connected via Bluetooth or green+pink wires.
If I use bluetooth, voice quality is terrible or microphone doesn't work. If I try to choose "Headset" option from In and Out tabs in Sound Settings, they're disabling each together.
In Out tab, I'm using "High sound quality A2DP", because it betters voice quality.
How could I get my microphone working? Sound out works fine.
sound bluetooth microphone headphones 13.10
sound bluetooth microphone headphones 13.10
asked Oct 6 '13 at 13:12
Aleksi KinnunenAleksi Kinnunen
2813
2813
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
By design, the Bluetooth A2DP profile is unidirectional. We can not use a microphone unless our headset and adapter were capable to be paired simultaneously on both HSP, and A2DP protocol, or the application switches from A2DP to HSP on demand.
See also this enlightning discussion on bug #508522.
add a comment |
I've just installed a solution for Bluetooth not selecting the mic on my Bose QC35 II on Ubuntu 16.04 LTS.
Since the internal mic on my Samsung laptop is too close to the fan audio sounds like inside an airplane for all participants in a videocall.
The solution is Blueman that adds functionality for Bluetooth.
Install it: sudo apt-get install blueman
I had to restart network-manager (sudo service network-manager restart
) after WiFi stopped working (could be unrelated, but hey better have it just in case).
I can now switch to Headeset Head Unit (HSP/HFP) and choose the headset mic in Sound settings
Still a bit of a hassle when it does not switch automatically (like Android does) but it's still better than being in a Jumbojet storage!
1
The question was on getting the microphone to work in A2DP mode, which AFAIK still is not possible. Using a mic in HFP mode is rather trivial and should work OOB without any additional applications needed. If you needed blueman in addition to get it working there may be an issue with your audio setup in the fist place.
– Takkat
Jan 31 '18 at 12:48
Well Takkat, it's a known problem with using BT mic in headphones on Ubuntu so it's not an audio setup for the mic problem... And sorry I accidentially downvoted your answer yesterday, could not reverse it. =(
– Valross.nu
Feb 1 '18 at 13:44
en.wikipedia.org/wiki/… - it is inherent to the Bluetooth profile definition. Nothing we or any other OS could do to overcome this - but you are quite correct in that issues with HFP-mode sadly still exist.
– Takkat
Feb 1 '18 at 14:23
I disagree here because most OS do make the switch between the two protocols without user interaction. As pointed out Android or Windows or ios switches automatically, where Ubuntu does not... So there is a solution in place for automation between the two...
– Valross.nu
Feb 2 '18 at 23:59
add a comment |
Already commented above that HFP is two-way and A2DP is one way.
But they also use different links:
https://stackoverflow.com/questions/40033827/what-is-the-difference-between-acl-and-sco-link-in-bluetooth
(or updated versions of those)
add a comment |
As it was already pointed out that A2DP is unidirectional, you have to switch to HSP profile every time you need to use the microphone. But doing so manually is not ideal, and unless application sets media.role=phone
for the stream (most non-voip apps don't), pulseaudio won't switch it automatically by default.
But starting from Pulseaudio v. 11.0, it's possible to automatically switch the profile whenever microphone access is requested by the application, but it's disabled by default.
- Find
load-module module-bluetooth-policy
line in/etc/pulse/default.pa
- Change it to
load-module module-bluetooth-policy auto_switch=2
Now pulseaudio will switch the device profile to HSP whenever microphone access is requested and change it back to A2DP after stream is closed.
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%2f354383%2fheadphones-microphone-is-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
By design, the Bluetooth A2DP profile is unidirectional. We can not use a microphone unless our headset and adapter were capable to be paired simultaneously on both HSP, and A2DP protocol, or the application switches from A2DP to HSP on demand.
See also this enlightning discussion on bug #508522.
add a comment |
By design, the Bluetooth A2DP profile is unidirectional. We can not use a microphone unless our headset and adapter were capable to be paired simultaneously on both HSP, and A2DP protocol, or the application switches from A2DP to HSP on demand.
See also this enlightning discussion on bug #508522.
add a comment |
By design, the Bluetooth A2DP profile is unidirectional. We can not use a microphone unless our headset and adapter were capable to be paired simultaneously on both HSP, and A2DP protocol, or the application switches from A2DP to HSP on demand.
See also this enlightning discussion on bug #508522.
By design, the Bluetooth A2DP profile is unidirectional. We can not use a microphone unless our headset and adapter were capable to be paired simultaneously on both HSP, and A2DP protocol, or the application switches from A2DP to HSP on demand.
See also this enlightning discussion on bug #508522.
answered Oct 6 '13 at 15:59
TakkatTakkat
108k37250377
108k37250377
add a comment |
add a comment |
I've just installed a solution for Bluetooth not selecting the mic on my Bose QC35 II on Ubuntu 16.04 LTS.
Since the internal mic on my Samsung laptop is too close to the fan audio sounds like inside an airplane for all participants in a videocall.
The solution is Blueman that adds functionality for Bluetooth.
Install it: sudo apt-get install blueman
I had to restart network-manager (sudo service network-manager restart
) after WiFi stopped working (could be unrelated, but hey better have it just in case).
I can now switch to Headeset Head Unit (HSP/HFP) and choose the headset mic in Sound settings
Still a bit of a hassle when it does not switch automatically (like Android does) but it's still better than being in a Jumbojet storage!
1
The question was on getting the microphone to work in A2DP mode, which AFAIK still is not possible. Using a mic in HFP mode is rather trivial and should work OOB without any additional applications needed. If you needed blueman in addition to get it working there may be an issue with your audio setup in the fist place.
– Takkat
Jan 31 '18 at 12:48
Well Takkat, it's a known problem with using BT mic in headphones on Ubuntu so it's not an audio setup for the mic problem... And sorry I accidentially downvoted your answer yesterday, could not reverse it. =(
– Valross.nu
Feb 1 '18 at 13:44
en.wikipedia.org/wiki/… - it is inherent to the Bluetooth profile definition. Nothing we or any other OS could do to overcome this - but you are quite correct in that issues with HFP-mode sadly still exist.
– Takkat
Feb 1 '18 at 14:23
I disagree here because most OS do make the switch between the two protocols without user interaction. As pointed out Android or Windows or ios switches automatically, where Ubuntu does not... So there is a solution in place for automation between the two...
– Valross.nu
Feb 2 '18 at 23:59
add a comment |
I've just installed a solution for Bluetooth not selecting the mic on my Bose QC35 II on Ubuntu 16.04 LTS.
Since the internal mic on my Samsung laptop is too close to the fan audio sounds like inside an airplane for all participants in a videocall.
The solution is Blueman that adds functionality for Bluetooth.
Install it: sudo apt-get install blueman
I had to restart network-manager (sudo service network-manager restart
) after WiFi stopped working (could be unrelated, but hey better have it just in case).
I can now switch to Headeset Head Unit (HSP/HFP) and choose the headset mic in Sound settings
Still a bit of a hassle when it does not switch automatically (like Android does) but it's still better than being in a Jumbojet storage!
1
The question was on getting the microphone to work in A2DP mode, which AFAIK still is not possible. Using a mic in HFP mode is rather trivial and should work OOB without any additional applications needed. If you needed blueman in addition to get it working there may be an issue with your audio setup in the fist place.
– Takkat
Jan 31 '18 at 12:48
Well Takkat, it's a known problem with using BT mic in headphones on Ubuntu so it's not an audio setup for the mic problem... And sorry I accidentially downvoted your answer yesterday, could not reverse it. =(
– Valross.nu
Feb 1 '18 at 13:44
en.wikipedia.org/wiki/… - it is inherent to the Bluetooth profile definition. Nothing we or any other OS could do to overcome this - but you are quite correct in that issues with HFP-mode sadly still exist.
– Takkat
Feb 1 '18 at 14:23
I disagree here because most OS do make the switch between the two protocols without user interaction. As pointed out Android or Windows or ios switches automatically, where Ubuntu does not... So there is a solution in place for automation between the two...
– Valross.nu
Feb 2 '18 at 23:59
add a comment |
I've just installed a solution for Bluetooth not selecting the mic on my Bose QC35 II on Ubuntu 16.04 LTS.
Since the internal mic on my Samsung laptop is too close to the fan audio sounds like inside an airplane for all participants in a videocall.
The solution is Blueman that adds functionality for Bluetooth.
Install it: sudo apt-get install blueman
I had to restart network-manager (sudo service network-manager restart
) after WiFi stopped working (could be unrelated, but hey better have it just in case).
I can now switch to Headeset Head Unit (HSP/HFP) and choose the headset mic in Sound settings
Still a bit of a hassle when it does not switch automatically (like Android does) but it's still better than being in a Jumbojet storage!
I've just installed a solution for Bluetooth not selecting the mic on my Bose QC35 II on Ubuntu 16.04 LTS.
Since the internal mic on my Samsung laptop is too close to the fan audio sounds like inside an airplane for all participants in a videocall.
The solution is Blueman that adds functionality for Bluetooth.
Install it: sudo apt-get install blueman
I had to restart network-manager (sudo service network-manager restart
) after WiFi stopped working (could be unrelated, but hey better have it just in case).
I can now switch to Headeset Head Unit (HSP/HFP) and choose the headset mic in Sound settings
Still a bit of a hassle when it does not switch automatically (like Android does) but it's still better than being in a Jumbojet storage!
answered Jan 31 '18 at 10:14
Valross.nuValross.nu
28014
28014
1
The question was on getting the microphone to work in A2DP mode, which AFAIK still is not possible. Using a mic in HFP mode is rather trivial and should work OOB without any additional applications needed. If you needed blueman in addition to get it working there may be an issue with your audio setup in the fist place.
– Takkat
Jan 31 '18 at 12:48
Well Takkat, it's a known problem with using BT mic in headphones on Ubuntu so it's not an audio setup for the mic problem... And sorry I accidentially downvoted your answer yesterday, could not reverse it. =(
– Valross.nu
Feb 1 '18 at 13:44
en.wikipedia.org/wiki/… - it is inherent to the Bluetooth profile definition. Nothing we or any other OS could do to overcome this - but you are quite correct in that issues with HFP-mode sadly still exist.
– Takkat
Feb 1 '18 at 14:23
I disagree here because most OS do make the switch between the two protocols without user interaction. As pointed out Android or Windows or ios switches automatically, where Ubuntu does not... So there is a solution in place for automation between the two...
– Valross.nu
Feb 2 '18 at 23:59
add a comment |
1
The question was on getting the microphone to work in A2DP mode, which AFAIK still is not possible. Using a mic in HFP mode is rather trivial and should work OOB without any additional applications needed. If you needed blueman in addition to get it working there may be an issue with your audio setup in the fist place.
– Takkat
Jan 31 '18 at 12:48
Well Takkat, it's a known problem with using BT mic in headphones on Ubuntu so it's not an audio setup for the mic problem... And sorry I accidentially downvoted your answer yesterday, could not reverse it. =(
– Valross.nu
Feb 1 '18 at 13:44
en.wikipedia.org/wiki/… - it is inherent to the Bluetooth profile definition. Nothing we or any other OS could do to overcome this - but you are quite correct in that issues with HFP-mode sadly still exist.
– Takkat
Feb 1 '18 at 14:23
I disagree here because most OS do make the switch between the two protocols without user interaction. As pointed out Android or Windows or ios switches automatically, where Ubuntu does not... So there is a solution in place for automation between the two...
– Valross.nu
Feb 2 '18 at 23:59
1
1
The question was on getting the microphone to work in A2DP mode, which AFAIK still is not possible. Using a mic in HFP mode is rather trivial and should work OOB without any additional applications needed. If you needed blueman in addition to get it working there may be an issue with your audio setup in the fist place.
– Takkat
Jan 31 '18 at 12:48
The question was on getting the microphone to work in A2DP mode, which AFAIK still is not possible. Using a mic in HFP mode is rather trivial and should work OOB without any additional applications needed. If you needed blueman in addition to get it working there may be an issue with your audio setup in the fist place.
– Takkat
Jan 31 '18 at 12:48
Well Takkat, it's a known problem with using BT mic in headphones on Ubuntu so it's not an audio setup for the mic problem... And sorry I accidentially downvoted your answer yesterday, could not reverse it. =(
– Valross.nu
Feb 1 '18 at 13:44
Well Takkat, it's a known problem with using BT mic in headphones on Ubuntu so it's not an audio setup for the mic problem... And sorry I accidentially downvoted your answer yesterday, could not reverse it. =(
– Valross.nu
Feb 1 '18 at 13:44
en.wikipedia.org/wiki/… - it is inherent to the Bluetooth profile definition. Nothing we or any other OS could do to overcome this - but you are quite correct in that issues with HFP-mode sadly still exist.
– Takkat
Feb 1 '18 at 14:23
en.wikipedia.org/wiki/… - it is inherent to the Bluetooth profile definition. Nothing we or any other OS could do to overcome this - but you are quite correct in that issues with HFP-mode sadly still exist.
– Takkat
Feb 1 '18 at 14:23
I disagree here because most OS do make the switch between the two protocols without user interaction. As pointed out Android or Windows or ios switches automatically, where Ubuntu does not... So there is a solution in place for automation between the two...
– Valross.nu
Feb 2 '18 at 23:59
I disagree here because most OS do make the switch between the two protocols without user interaction. As pointed out Android or Windows or ios switches automatically, where Ubuntu does not... So there is a solution in place for automation between the two...
– Valross.nu
Feb 2 '18 at 23:59
add a comment |
Already commented above that HFP is two-way and A2DP is one way.
But they also use different links:
https://stackoverflow.com/questions/40033827/what-is-the-difference-between-acl-and-sco-link-in-bluetooth
(or updated versions of those)
add a comment |
Already commented above that HFP is two-way and A2DP is one way.
But they also use different links:
https://stackoverflow.com/questions/40033827/what-is-the-difference-between-acl-and-sco-link-in-bluetooth
(or updated versions of those)
add a comment |
Already commented above that HFP is two-way and A2DP is one way.
But they also use different links:
https://stackoverflow.com/questions/40033827/what-is-the-difference-between-acl-and-sco-link-in-bluetooth
(or updated versions of those)
Already commented above that HFP is two-way and A2DP is one way.
But they also use different links:
https://stackoverflow.com/questions/40033827/what-is-the-difference-between-acl-and-sco-link-in-bluetooth
(or updated versions of those)
answered Jul 25 '18 at 11:02
user728938user728938
114
114
add a comment |
add a comment |
As it was already pointed out that A2DP is unidirectional, you have to switch to HSP profile every time you need to use the microphone. But doing so manually is not ideal, and unless application sets media.role=phone
for the stream (most non-voip apps don't), pulseaudio won't switch it automatically by default.
But starting from Pulseaudio v. 11.0, it's possible to automatically switch the profile whenever microphone access is requested by the application, but it's disabled by default.
- Find
load-module module-bluetooth-policy
line in/etc/pulse/default.pa
- Change it to
load-module module-bluetooth-policy auto_switch=2
Now pulseaudio will switch the device profile to HSP whenever microphone access is requested and change it back to A2DP after stream is closed.
add a comment |
As it was already pointed out that A2DP is unidirectional, you have to switch to HSP profile every time you need to use the microphone. But doing so manually is not ideal, and unless application sets media.role=phone
for the stream (most non-voip apps don't), pulseaudio won't switch it automatically by default.
But starting from Pulseaudio v. 11.0, it's possible to automatically switch the profile whenever microphone access is requested by the application, but it's disabled by default.
- Find
load-module module-bluetooth-policy
line in/etc/pulse/default.pa
- Change it to
load-module module-bluetooth-policy auto_switch=2
Now pulseaudio will switch the device profile to HSP whenever microphone access is requested and change it back to A2DP after stream is closed.
add a comment |
As it was already pointed out that A2DP is unidirectional, you have to switch to HSP profile every time you need to use the microphone. But doing so manually is not ideal, and unless application sets media.role=phone
for the stream (most non-voip apps don't), pulseaudio won't switch it automatically by default.
But starting from Pulseaudio v. 11.0, it's possible to automatically switch the profile whenever microphone access is requested by the application, but it's disabled by default.
- Find
load-module module-bluetooth-policy
line in/etc/pulse/default.pa
- Change it to
load-module module-bluetooth-policy auto_switch=2
Now pulseaudio will switch the device profile to HSP whenever microphone access is requested and change it back to A2DP after stream is closed.
As it was already pointed out that A2DP is unidirectional, you have to switch to HSP profile every time you need to use the microphone. But doing so manually is not ideal, and unless application sets media.role=phone
for the stream (most non-voip apps don't), pulseaudio won't switch it automatically by default.
But starting from Pulseaudio v. 11.0, it's possible to automatically switch the profile whenever microphone access is requested by the application, but it's disabled by default.
- Find
load-module module-bluetooth-policy
line in/etc/pulse/default.pa
- Change it to
load-module module-bluetooth-policy auto_switch=2
Now pulseaudio will switch the device profile to HSP whenever microphone access is requested and change it back to A2DP after stream is closed.
answered Feb 21 at 12:10
GlubGlub
1
1
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%2f354383%2fheadphones-microphone-is-not-working%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