[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: micker zap.png (533 KB, 749x749)
533 KB
533 KB PNG
I have literally never gotten bluetooth devices to work on linux, at all.
This is after trying like 5 or 6 different BT dongles and every bluetooth frontend like blueman and bluetoothctl.
Headphones will pair and connect but their pipewire sink doesn't show up in pavucontrol and I can't play audio through it.
Controllers will connect and pair but quickly unpair for some reason.

Is this a feature?
Linux's bluetooth stack is so garbage that it forces you to get a superior latency free experience via the wired mode on bluetooth devices?
>>
works on my machine
>>
File: it just.png (77 KB, 883x952)
77 KB
77 KB PNG
>>103232372
Lemme guess some Arch abomination?
>>
>>103232372
All bluetooth devices I ever owned literally just worked. Never even installed or configured anything (Fedora). If you use Arch thats a you problem.
>>
You're a worthless person.
>>
>>103232426
>>103232440
debian

>>103232472
what?
>>
>>103232372
I exclusively use uBit WiFi/BT antennae for all my builds both personal and customer and they've always work ootb.
Pretty sure they use an intel chip.
>>
>>103232372
just werks on Linux mint
>>
>>103232500
I'd be tempted to test a buntu/mint live cd on the same hardware. If there are still issues it's probably the dongle else you get configs/logs to compare.
BT always a bit jank tho innit, I get occasional controller disconnects and have to set LDAC profile in pavucontrol each time XM5 connects
>>
>>103232500
Its always the same. Either its
>Uses rice tinker distro known for breaking often
Or its
>Uses antique distro known for shipping ancient software made during Pharaonic times
This is a you problem.
>>
>>103232673
in my case it's probably both because I use debian but in a stripped down state where I only use bare xorg and an autistic tiling wm, I don't even have a display manager.

>>103232660
I'll try this next.
>>
>>103232372
> sink doesn't show up in pavucontrol and I can't play audio through it.
Could be more of an audio config problem, I've seen similar issues with HDMI. Maybe boot a few live sessions of other distros and see if they handle it better. EndeavourOS in particular usually helps me a lot when trying to diagnose issues with my config, or software support, for my hardware.
>>
I have never had a single issue with Bluetooth on Linux since 2007.

Ubuntu, Arch, Debian, Fedora, OpenSUSE, NixOS, literally every distro I have ever tried. 0 issues.

The only time I ever though I did I just had to use rfkill to turn bluetooth on after installing Arch at some point.

Have you checked rfkill?
>>
works on my machine
>>
>>103232372
bluetooth pairing is currently broken if you use 6.11 kernel
rolling release trannies btfo
>>
>>103232372
my kDE jsut wekrs
>>
interference from other 2.4GHz stuff?
>>
>>103233469
Even doe I just pair my cvntroller on nyarch linux
>>
>>103232372
Nigger, even the cheapest $1 USB BT "dongles" work fine. It's probably your shitty distro.

>>103232500
>Debian
Why are you using a server distro on a desktop? Use something like Bazzite or at least Mint.
>>
I have NEVER used anything bluetooth.
>>
>>103232426
What font?
>>
Bluetooth has been flawless for me for the past decade or so. Especially bluetooth audio works much better than on Windows. The default configs of bluez, pipewire and KDE are sufficient to just work out of the box, even on Arch.
>>
I don't use bluetooth but when I tried a keyboard and a controller both worked just fine on Linux. I used plain blues to connect (check Gentoo wiki). Had to do it as root, I think.
>>
>>103234547
Can't believe it took until now for someone to mention bluez.

OP, your bluetooth isn't working because you're using shit bluetooth utilities. Bluez just works on the back end, for the front end I like Blueman.

This is one thing Windows users struggle to understand about Linux. If bluetooth isn't working for you, it doesn't mean Linux sucks, it means your bluetooth program sucks.
>>
>>103232426
On my arch system bluetooth works so well that I threw out all my wired headphones
>>
>>103234305
Lato
>>
>>103232372
Try KDE.
I don't know what make it work at this point.
But KDE is the only thing that made it work consistently.
>>
>>103234979
bluetoothctl is a part of bluez and there are no other relevant Linux kernel bluetooth stacks anyway
>>
>>103232372
I never use bluetooth before but I just tried with an old dongle we had lying around. Debian immediately recognized it and showed the symbol in the taskbar and with two clicks I could connect my phone. Literally just works. Seems to be a (you) problem here.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.