Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sony WH-1000XM3 connection on Debian 10 Buster #1209

Closed
Phil995511 opened this issue Apr 6, 2020 · 10 comments
Closed

Sony WH-1000XM3 connection on Debian 10 Buster #1209

Phil995511 opened this issue Apr 6, 2020 · 10 comments

Comments

@Phil995511
Copy link

Phil995511 commented Apr 6, 2020

blueman: 2.0.8-1
BlueZ: 5.50-1.2~deb10u1
Distribution: Debian 10 Buster x64 Bits (AMD64)
Desktop environment: Cinnamon 3.8

Hello, I'm using my new headphones on Linux Debian 10 Buster.

When I link it to my laptop everything works perfectly the first time (although I unfortunately do not seem to benefit from the LDAC codec for which I bought this headset, it works satisfactorily in A2DP Sink). If I turn off this headset and I want to reuse it later, the connection is made but instead of being of good quality (A2DP Sink) it is done in SBS (HSP / HFP) which is of very poor quality. I am very unhappy with the result...

Is there a way to force the connection in A2DP Sink or to deactivate the codec SBS (HSP / HFP) which I do not use and thus to force the connection in A2DP mode Sink ? Is it possible to use the LDAC codec from Sony which is available for free for Android phones which is based on Linux ?

Best regards.

@infirit
Copy link
Contributor

infirit commented Apr 7, 2020

What codec is used it up to pulseaudio and blueman has no control over it. From blueman and most audio mixer you can select A2DP again.

If you want LDAC you need different pulseaudio bluetooth modules, see https://github.com/EHfive/pulseaudio-modules-bt

@Phil995511
Copy link
Author

Hello, I cannot select A2DP again, it remains blocked in SBS (HSP / HFP). I have to turn off the headphones and reconnect manually, which is very annoying in the long run.

I will change OS if I do not find a viable solution...

I found the package "libldac_2.0.2.3-2_bionic1_amd64.deb" which is precompiled for kernel 4.19, it installs without difficulties but it is impossible to make it work with other softwares to enjoy sound in LDAC quality ;(

Regards.

@hugokerstens
Copy link

@Phil995511 What works for me as well is disconnecting the headset from the blueman manager and reconnect as audio sink, no need to turn off the headset itself.

This issue has been reported multiple times: #1031 #1242

@Phil995511
Copy link
Author

Phil995511 commented May 7, 2020

Hello Hugo Kerstens,

Thank you for your good advice, from memory it seems to me to have already tested this idea without success with each reboot I have the same problems...

Debian 10.4 comes out on Saturday 07.05.2020, I will reinstall my laptop on this occasion on an external disk to repeat the test according to your advice.

https://release.debian.org/

For the moment the only solution I have found is using Ubuntu 20.04 for fix this problem... Unfortunately under Debian 10.3 in addition to that, I can not use the double GPU of my laptop either, none tutorial for the installer of Bumblebee / Nvidia Optimus works. Only the Intle GPU work ;-(

Regards

@Phil995511 What works for me as well is disconnecting the headset from the blueman manager and reconnect as audio sink, no need to turn off the headset itself.

This issue has been reported multiple times: #1031 #1242

@Phil995511
Copy link
Author

Phil995511 commented May 10, 2020

@hugokerstens The problem persist on Debian 10.4. If you reconnect as audio sink (or with an other option), then you disconnect and reconnect the Sony WH-1000XM3, you are on "HSP/HFP" codec with horrible audio quality, not on "A2DP Sink" codec for good audio quality.

@cschramm Please dont close prematurely tickets. The problem is not solved, Please solve it...

@cschramm
Copy link
Member

@Phil995511: To my knowledge, BlueZ 5.51 brings a solution for this (pointed out by @hugokerstens). Feel free to continue the thread but it's nothing we need to track from the blueman perspective, thus closed.

@Phil995511
Copy link
Author

@cschramm Thank you for this information, in this case, the Debian people should update BlueZ on version 5.51 !! Can you give them a request to this effect, to prevent other users from being stuck with this problem ?? Regards.

@cschramm
Copy link
Member

@Phil995511: The way to ask for that would be to report a bug against the bluez package, however, rest assured that the Debian maintainers in general are well aware of updating packages to new release versions unless the package is orphaned (which bluez is not) in which case nobody would be there to handle the request. Also note that bluez 5.52 is packaged and available in the experimental repository, so that your request would be rather pointless, and as you seem to use a stable release you would not receive any possible update anyway. The way to go for a stable release would be a backport. You might consider asking for one at the respective mailing list but I'd expect the community to respond with "go ahead, start working on it" 😉.

@Phil995511
Copy link
Author

Phil995511 commented May 10, 2020

@cschramm As you can see below for example the version 10.4 of Debian fixes many bugs but, but not that of Bluez ;-(

https://www.debian.org/News/2020/20200509

Further down, there is also a list of security updates and removed packages.

I've already reported the bug on Debian, but they haven't done anything so far, I haven't heard from them.

The problem will continue to affect users as long as the Debian people do not update it to version 5.51 or 5.52.

A backport package would be welcome, it could be released faster than if we wait for a new minor version of Debian like 10.5, 10.6 or later...

I subscribed to the backports packages mailing list, thank you for notifying me.

I will be very happy that the community says "go ahead, start working on it" :)

Best regards

@cschramm
Copy link
Member

cschramm commented May 10, 2020

@Phil995511: As I wrote, the Debian maintainers are aware of the fact that new versions get released and their packages need updates, there is no need to remind them and it will not make them do their volunteer work faster for you, a newer version of BlueZ than 5.50 is available in the archives and will not be brought to an existing stable release that you're using.

Also, I'd hardly consider the behavior you're experiencing to be a bug and if it is one at all, it is a bug of your device, so please complain to Sony who you paid for their stuff and not the communities behind BlueZ, Debian, or blueman. People at BlueZ even improved your life with those devices (committed 06/2018 (kudos to @Vudentz), first released 09/2019, packaged in Debian (kudos to @iwamatsu) just two weeks later).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants