timschneeb/GalaxyBudsClient

[REQ] Support for Galaxy Buds FE and multi-device.

nathan60107 opened this issue ยท 8 comments

Is your feature request related to a problem? Please describe.
I purchased the Galaxy Buds FE and attempted to connect them to the GalaxyBudsClient. However, I discovered that the GalaxyBudsClient doesn't support the FE model, and it also lacks multi-device support. I found a workaround by manually adding the FE to the GalaxyBudsClient by selecting a different model type.
ๅœ–็‰‡

Describe the solution you'd like
Support Buds FE and multi-device.

Describe alternatives you've considered
None

Additional context
Nothing. Thanks for creating this app.

I too would love to see the Galaxy Buds FE support! <3

same issue. would love to see support implemented

Hello guys, yesterday I buy the Galaxy Buds FE (and because that I was replying later).

You guys can connect the "Galaxy Buds FE" as "Buds2" manually into connection page.
image

Is my first time testing, recently 5 minutes testing and without any problems
image

Hello guys, yesterday I buy the Galaxy Buds FE (and because that I was replying later).

You guys can connect the "Galaxy Buds FE" as "Buds2" manually into connection page. image

Is my first time testing, recently 5 minutes testing and without any problems image

If you do this and change touchpad settings it breaks the touchpad. I can't fix my touchpad now as it is stuck in a broken state presumably until I can get an Android phone to fix it. Everything else works but beware not to change touchpad settings with this app til FE is properly implemented.

Yeah I'd love to have all my Buds on one app. I'm stuck using this one for my Buds+ and the Samsung one for my FE because there is inevitably one not in both and I swap between those two.

any update on this?

Any update on this?

Buds FE support is available in the latest release: https://github.com/ThePBone/GalaxyBudsClient/releases (although mostly untested)

I haven't started working on multi-device support yet, but there's already another issue (#214) open about that, so I'll close this one.