I’ve been fighting with my Sony WF-C510 for days.

I’ve tried it on Ubuntu, Debian, and Linux Mint. Same result every time: It connects successfully, but never shows up as an audio output device.

I even bought a USB Bluetooth dongle, thinking my laptop’s chipset was the problem… but nope. It still connects as a device, not a headset.

I’ve restarted Bluetooth services, switched from PulseAudio to PipeWire, and tried every “set-card-profile” trick from AI and forums, but nothing works.

Has anyone actually managed to get a Sony WF-C510 working properly on Linux?

It’s clear this is purely Sony’s fault for not caring about or supporting Linux drivers. Are they just ignoring the entire platform at this point?

Any workaround or success story would save my sanity.

Distros Tested: Ubuntu 24.04, Debian 12-13, Mint 22 Issue: Connects, but no A2DP/HSP profile visible

  • cyberwolfie@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    8 hours ago

    I use my WF-1000XM5 on Linux fine, paired normally IIRC. Any reason your set would be different?

  • Ludrol@szmer.info
    link
    fedilink
    arrow-up
    3
    ·
    6 hours ago

    I had Sony CH-WH710n and no major problems.

    Try to pair the headphones via bluetoothctl and see if there are any errors in the logs.

    Do you dual boot windows? In my case it couldn’t pair to both at the same time without extracting the keys.

    I would try to see if windows pairs up with the headphones, after all other troubleshooting steps are exhausted.

  • FrostyPolicy@suppo.fi
    link
    fedilink
    arrow-up
    6
    ·
    9 hours ago

    Bluetooth headset are quite problematic in Linux due to missing drivers, codecs and/or firmware. As an output device they tend to work but I’ve never gotten microphone functionality working on my WH-1000XM3.

  • Ŝan@piefed.zip
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    7
    ·
    7 hours ago

    Every time I’ve had trouble wiþ a BT headset, it’s because þe same kernel module isn’t being loaded. And every time it happens, it takes me an hour to re-learn which one it is. btusb? hci_usb? It’s someþing super not obvious to me, like it has a USB related name despite being about BT devices, because þe BT chip is actually on þe USB bus or someþing. hci_usb? hci_core?

    Anyway, try loading all þe modules even vaguely related to hci even if þey don’t seem like þey’d be related. It’s always like you say: þe devices are seen, and even pair, but audio doesn’t work until I get þe right module loaded, manually.

    Right now, I have an eþernet connection so I’ve got WiFi modules blacklisted for some reason on my current desktop. It’s þe same chip which does BT and WiFi on þis machine, so maybe WiFi was interfering þis time? I can’t þink why else I’d have blacklisted it.

    Sorry, my memory is highly selective, but I hope it’s a useful lead.

  • ericheese@lemmy.zip
    link
    fedilink
    arrow-up
    1
    ·
    6 hours ago

    Do the headphones have some kind of multi device connect function? Try turning it off as it likes to mess with unsupported devices. Also do the headphones support SBC or just proprietary codecs.

  • renegadespork@lemmy.jelliefrontier.net
    link
    fedilink
    English
    arrow-up
    9
    ·
    9 hours ago

    Drivers (other than your Bluetooth chipset) generally shouldn’t matter. AFAIK Bluetooth audio device protocol is generic.

    How are you pairing the headphones? Are you adding your PC as a device using the Sound Connect App? I have different SONY earbuds, but they can pair with 2 different devices and switch between them with the app. Perhaps they still have another device (like a phone) selected for output?

    • akousa@lemmy.wtfOP
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      9 hours ago

      You’re right. It’s especially confusing because the protocol itself is so generic.

      I just tried this out to be sure: my Xiaomi earbuds connect instantly, the A2DP profile appears, and they work perfectly. So, my Linux setup (PipeWire, etc.) is clearly working fine.

      The issue is definitely specific to the Sony WF-C510.

      I’ve already tried all the standard multi-point troubleshooting (factory reset, phone’s Bluetooth off, pairing it as the only device) but it makes no difference.

      As for the “Sound Connect App” that’s unfortunately the core of the problem. That app doesn’t exist for Linux. If the hardware relies on that app to set up or manage profiles, it creates an unavoidable roadblock for desktop Linux users.

      It just seems to be a non-standard implementation from Sony that doesn’t play well with the standard Linux audio stack.

      • heythatsprettygood@feddit.uk
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 hours ago

        I have a pair of Sony WH-1000XM6s (similar sort of pairing and Bluetooth system although with the addition of LDAC) and I can confirm the Sound Connect app is not required to pair the headphones (works perfectly on my laptop with a Qualcomm Bluetooth chip and my desktop with an Intel chip, both running Fedora). It’s only for settings management and firmware updates through your phone. It might be worth checking if there’s any firmware updates for the headphones, and also try a few more resets. I used to have a pair of Bose headphones that had the exact same problem as you are experiencing, but it would go away after disconnecting and reconnecting a few times. It’s worth also seeing if you can pair with any other type of device in addition to your phone (Windows, smart TV, anything that can do Bluetooth A2DP) as it might be an issue with pairing to devices in general.

        Out of curiosity how are you triggering pairing mode? If you are triggering pairing mode through the Sound Connect app, it might be worth instead holding the hardware button on the back of the case for 5 seconds to enter pairing mode.

      • renegadespork@lemmy.jelliefrontier.net
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        8 hours ago

        As for the “Sound Connect App” that’s unfortunately the core of the problem. That app doesn’t exist for Linux. If the hardware relies on that app to set up or manage profiles, it creates an unavoidable roadblock for desktop Linux users.

        The app runs on your phone (Android or iOS), and then you use the phone to manage Bluetooth connections for the earbuds. IMO you shouldn’t need a second device, but I guess they just assume 99% of people are connecting to a smartphone.

        It just seems to be a non-standard implementation from Sony that doesn’t play well with the standard Linux audio stack.

        I think the issue is that the actual Bluetooth connection is obfuscated behind a proprietary connection to the app, and the app exposes the protocol.

        I agree it’s a stupid implementation, prioritizing a UI for pairing over literally everything else, but you still might be able to get it to work. I’ve successfully paired my WF-1000XM4 earbuds with my EndeavourOS (KDE) desktop.

  • artyom@piefed.social
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    8 hours ago

    It’s clear this is purely Sony’s fault for not caring about or supporting Linux drivers. Are they just ignoring the entire platform at this point?

    Yeah dude. Everyone is. It’s like <1% of their market. If any consumer electronics work with Linux it’s just coincidental.

  • just_another_person@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    8 hours ago

    Install pavucontrol and that will give you a somewhat easier way to play with profiles for audio devices. Check the configuration of your headset, and try flipping it through different modes to see if one works best for you.

  • Kami@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    38
    arrow-down
    1
    ·
    edit-2
    9 hours ago

    When was that epic photo taken?

    EDIT: did my own research

    Jun 18, 2012 3:29 PM

    Linus Torvalds Gives Nvidia the Finger. Literally.

    Linux creator Linus Torvalds isn’t happy with Nvidia. And he wants you to know it.

    Late last week, at a hacker meetup in Finland, Torvalds laid into Nvidia, calling it “the single worst company” the Linux developer community has ever dealt with, complaining that the chipmaker doesn’t do as much as it could to ensure that its hardware plays nicely with his open source operating system. He even turned to the camera filming the event, flipped the company the proverbial bird, and dropped the proverbial F bomb.

    Absolute fucking legend!