GalaxyBudsClient icon indicating copy to clipboard operation
GalaxyBudsClient copied to clipboard

[BUG] Doesn't recognise Galaxy Buds2 if they have custom name

Open iliqiliev opened this issue 2 years ago • 1 comments

The app doesn't recognize the buds even though they are connected and work normal.

You can open the app on the phone, reset them and then they are recognized correctly and work even after renamed so it's not really a big problem.

Both on Windows 10 and Arch Linux App version 4.5.2

iliqiliev avatar Aug 28 '22 08:08 iliqiliev

For the time being, I've added a workaround, which allows you to select the correct Bluetooth device from an unfiltered list (see the 'manual connection' button on the bottom of the device selection page). You'll also need to choose the correct device model.

You can download a precompiled beta build on these pages:

Samsung also detected the earbuds using their Bluetooth device name until they introduced personalized device names. Now, they store a bunch of metadata in the 'manufacturer' property of the Bluetooth device. However, for some reason, I cannot read this information on Linux at all (always empty). I haven't checked on Windows yet, but for now, I'll stick with the workaround mentioned above until I find a reliable way to retrieve this data.

timschneeb avatar Aug 29 '22 14:08 timschneeb

Kinda unrelated, but is there anyway to change the name from this client?

AbhayAysola avatar Feb 05 '24 14:02 AbhayAysola

Kinda unrelated, but is there anyway to change the name from this client?

No, at least not yet. I can look into adding it, but I don't have a device that supports personalized names for testing.

timschneeb avatar Feb 10 '24 23:02 timschneeb

Ah no problem, thanks for your work on this wonderful client though.

AbhayAysola avatar Feb 12 '24 13:02 AbhayAysola