Device 00:6A:8E:17:08:00 Name: BH-M20C Alias: BH-M20C Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no 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: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) need "autodetect_mtu=no" to module-bluetooth-discover in /etc/pulse/default.pa
Can you report this to the BlueZ developers? They can be contacted on the linux-bluetooth mailing list: http://vger.kernel.org/vger-lists.html#linux-bluetooth I believe the bluetooth adapter has more to do with this problem than the headset, so you should also include your computer's bluetooth adapter model in the report. The BlueZ developers haven't been very responsive regarding these issues, which is why the default value of autodetect_mtu was changed to "no" as of PulseAudio 11.1.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/149.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.