*** This bug is a duplicate of bug 1845046 ***
https://bugs.launchpad.net/bugs/1845046
I have the same problem with Sennheiser MOMENTUM M2 AEBT in Ubuntu 20.04
Nice workaround:
https://forums.linuxmint.com/viewtopic.php?p=1691795&sid=3c219e459f6aac3d70695b278e3454f6#p1691795
--
You received
*** This bug is a duplicate of bug 1845046 ***
https://bugs.launchpad.net/bugs/1845046
Same for Sennheiser MOMENTUM M2 AEBT in Ubuntu 20.04
ii bluez 5.53-0ubuntu3
amd64Bluetooth tools and daemons
ii bluez-cups
*** This bug is a duplicate of bug 1845046 ***
https://bugs.launchpad.net/bugs/1845046
** This bug has been marked a duplicate of bug 1845046
Bluetooth headphones default to low quality headset mode and fail to switch
to A2DP when selected
--
You received this bug notification because yo
** This bug is no longer a duplicate of bug 1845046
Bluetooth headphones default to low quality headset mode and fail to switch
to A2DP when selected
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchp
*** This bug is a duplicate of bug 1845046 ***
https://bugs.launchpad.net/bugs/1845046
Thanks for the bug report and sorry I was on vacation when you emailed
me about bug 1724919.
Now that you mention Sony WH-1000XM3 I realize this is actually bug
1845046 which also was first reported against
** Attachment added: "headphones"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308568/+files/headphones
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/18543
The only other Bluetooth headphones I've had access to recently were a
pair of Bose QC35 (1st generation). They showed up in the list of
visible BT devices, but my laptop couldn't connect to them at all,
despite numerous attempts. As a result, I bought the Sonys and got rid
of the Bose.
If you tak
That's not /really/ helpful anyway. You'd have installed an extra
application, for a wholly unrelated issue, and still have to set the
profile to A2DP yourself.
Alistair, there are messages in your logs that seem to point to a firmware
issue:
Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to
How do I run blueman after installing it?
$ blueman
Command 'blueman' not found, did you mean:
command 'bluemon' from deb bluemon (1.4-7)
Try: sudo apt install
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https:/
Sounds similar to
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197
Can you install blueman, connect to the headset, right click on the headset in
blueman, go to audio profile, select off, disconnect headset then reconnect and
can you set the audio profile to A2DP then
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1854392
11 matches
Mail list logo
