蓝牙耳机可以播放音频,但内置耳机麦克风却不能

蓝牙耳机可以播放音频,但内置耳机麦克风却不能

我正在使用 Pop_OS! 20.04。我有一副索尼蓝牙耳机(WH-1000XM3)。我正在使用一个USB加密狗对于蓝牙接收器。

耳机中的音频可以工作,耳机上的控件可以工作,但内置麦克风不能。麦克风和音频适用于我的 Android 手机、Windows 和 Mac。

我进入设置,一切看起来都正确,但操作系统没有检测到它。在Slack和Google Hangouts中,有消息说找不到这个在线测试https://www.onlinemictest.com/

有什么工具可以用来调试这个吗?我如何确定是蓝牙接收器的问题,还是操作系统或耳机中的某些问题?

我尝试过blueman,但没有看到任何异常情况。

我试过这个https://askubuntu.com/a/1233446/566235但我不知道将哪一个添加到我的 alsa-base.conf 中。我的编解码器是 Realtek ALC888

我的音频设置的屏幕截图,我无法取消耳机输入的静音。 我的音频设置的屏幕截图。

pavucontrol 的输入。最后一张是我的耳机。 pavucontrol 输入的屏幕截图

所有请求的输出:

$ bluetoothctl devices
Device 70:26:05:8C:CE:40 LE_WH-1000XM3
Device DC:2C:26:D0:90:6A RK-Bluetooth keyboard
Device CA:1C:83:E2:08:59 BT4.0+2.4G Mouse
Device E0:9F:2A:08:10:43 Intuos BT S
Device E0:EA:E1:C3:44:22 Inspire 2

$ bluetooth show
Controller 00:1A:7D:DA:71:11 (public)
    Name: pop-os
    Alias: pop-os
    Class: 0x001c0104
    Powered: yes
    Discoverable: yes
    DiscoverableTimeout: 0x00000000
    Pairable: no
    UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
    UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
    UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
    UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
    UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
    UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0535
    Discovering: no
Advertising Features:
    ActiveInstances: 0x00
    SupportedInstances: 0x05
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name

$ bluetoothctl info 70:26:05:8C:CE:40                                             
Device 70:26:05:8C:CE:40 (public)
    Name: LE_WH-1000XM3
    Alias: LE_WH-1000XM3
    Class: 0x00240404
    Icon: audio-card
    Paired: yes
    Trusted: yes
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
    UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: Vendor specific           (7b265b0e-2232-4d45-bef4-bb8ae62f813d)
    UUID: Vendor specific           (81c2e72a-0591-443e-a1ff-05f988593351)
    UUID: Vendor specific           (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
    UUID: Vendor specific           (96cc203e-5068-46ad-b32d-e316f5e069ba)
    UUID: Vendor specific           (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
    UUID: Vendor specific           (f8d1fbe4-7966-4334-8024-ff96c9330e15)
    Modalias: usb:v054Cp0CD3d0452
    ManufacturerData Key: 0x012d
    ManufacturerData Value:
  04 00 01 31 00 01 ba 5c 10 b9 00 60 d0 00 00 00  ...1...\...`....
  00 00 00                                         ...             
    ServiceData Key: 0000fe26-0000-1000-8000-00805f9b34fb
    ServiceData Value:
  0a c9 5c                                         ..\             
    ServiceData Key: 0000fe2c-0000-1000-8000-00805f9b34fb
    ServiceData Value:
  0a c9 5c                                         ..\             

$ lsusb -v | grep -E '\<(Bus|iProduct|bDeviceClass|bDeviceProtocol)' 2>/dev/null
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 
Bus 002 Device 013: ID 1224:2a25  
  bDeviceClass          239 Miscellaneous Device
  bDeviceProtocol         1 Interface Association
  iProduct                2 
      (Bus Powered)
Couldn't open device, some information will be missing
Bus 002 Device 012: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
  bDeviceClass          224 Wireless
  bDeviceProtocol         1 Bluetooth
  iProduct                2 
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Bus 002 Device 011: ID 05e3:0608 Genesys Logic, Inc. Hub
  bDeviceClass            9 Hub
Couldn't open device, some information will be missing
  bDeviceProtocol         1 Single TT
  iProduct                1 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 
Bus 006 Device 003: ID 045e:0291 Microsoft Corp. Xbox 360 Wireless Receiver for Windows
  bDeviceClass          255 Vendor Specific Class
  bDeviceProtocol       255 Vendor Specific Protocol
  iProduct                0 
      (Bus Powered)
Couldn't open device, some information will be missing
Bus 006 Device 002: ID 25a7:fa11 Nordic 2.4G Wireless Receiver
  bDeviceClass            0 
  bDeviceProtocol         0 
  iProduct                2 
      (Bus Powered)
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Couldn't open device, some information will be missing
  bDeviceClass            9 Hub
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 
Bus 005 Device 002: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
  bDeviceClass            0 
  bDeviceProtocol         0 
  iProduct                2 
      (Bus Powered)
Couldn't open device, some information will be missing
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Couldn't open device, some information will be missing
  bDeviceClass            9 Hub
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  bDeviceClass            9 Hub
Couldn't open device, some information will be missing
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         3 
  iProduct                2 
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         1 Single TT
  iProduct                2 

答案1

编辑:您的加密狗 ID 为 0a12:0001 Cambridge Silicon Radio。众所周知,这些都是低质量的,例如。如果可能的话,您可以尝试以下操作


如果您发布一些信息将会有很大帮助:

  1. 输出

    $ bluetoothctl devices
    $ bluetoothctl show
    $ bluetoothctl info <address of headphones>
    $ lsusb -v | grep -E '\<(Bus|iProduct|bDeviceClass|bDeviceProtocol)' 2>/dev/null
    
  2. 单击所显示图像的输出设备和输入设备中的向下箭头时所看到的内容的捕获(以便我们看到所有可用选项)。

  3. 单击pavucontrol->中的向下箭头时所看到的内容的捕获输出设备输入设备

同时,您可以尝试(全部来自 SE,无需复制粘贴,至少在获得更多信息之前):

  1. 这个序列
  2. pulseaudio -k && sudo alsa force-reload
  3. 这个序列
  4. 这个序列

可能相关

  1. https://gist.github.com/nevack/6b36b82d715dc025163d9e9124840a07
  2. https://github.com/mechaHarry/realtek-alc888-patched
  3. https://askubuntu.com/questions/287235/realtek-alc888-sound-card-doesnt-work-after-ubuntu-13-04
  4. https://www.linuxquestions.org/questions/linux-hardware-18/no-sound-or-bad-sound-card-with-codec-realtek-alc888-861049/
  5. https://askubuntu.com/questions/1230016/headset-microphone-not-working-on-ubuntu-20-04
  6. 强制耳机麦克风作为默认麦克风
  7. https://superuser.com/questions/1588750/mono-mic-instead-of-stereo-sound-for-bluetooth-headphones-on-ubuntu
  8. https://askubuntu.com/questions/816879/why-do-my-bluetooth-sony-stero-headphones-only-play-in-mono
  9. Debian 系统似乎可以识别联想笔记本电脑的扬声器,但无法识别耳机
  10. https://ubuntu-mate.community/t/mate-20-04-headphone-mic-combo-jack-not-detecting-headset/21731

答案2

PulseAudio 仅支持 2 个配置文件:

  • A2DP 质量好,但没有音频输入
  • HSP/HFP 具有音频输入和输出,质量较差

您似乎已启用 A2DP 配置文件。您可以在 pavucontrol 选项卡“配置”中更改它,您应该在其中看到带有“配置文件”下拉列表的 BT 耳机。

pavucontrol 窗口,带有可见的配置文件下拉菜单,其中包含树选项:“高保真播放 (A2DP Sink)”、“头戴式主机 (HSP/HFP)”和“关闭”

相关 StackExchange 问题:

  1. 与蓝牙耳机同时使用高品质编解码器和麦克风
  2. 使用蓝牙耳机麦克风时如何将音频配置文件保持在 A2DP? (一键通)

答案3

这看起来像是蓝牙问题,您最好的选择是进行更多调整,blueman因为过去有些人也必须这样做才能使蓝牙耳机正常工作。

有时,您需要将蓝牙设备直接与blueman桌面环境的 GUI 配对,而不是与桌面环境的 GUI 配对。

这是您应该摆弄的地方(连接、配对、信任、设置...):在此输入图像描述

我也看到这个:在此输入图像描述

难道不应该将“WH-1000XM3的监视器”设置为后备吗?

您还可以将任何其他输入设备静音,看看它们是否不会产生任何冲突。

尝试在 pavucontrol 上将 Slack 和 Hangouts 设置为正确的设备:在此输入图像描述

相关内容