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

Galaxy buds 2 Pro dont work #102

Open
FlareFlo opened this issue Jul 10, 2023 · 4 comments
Open

Galaxy buds 2 Pro dont work #102

FlareFlo opened this issue Jul 10, 2023 · 4 comments

Comments

@FlareFlo
Copy link

using earbuds
Kernel: 6.4.2-zen1-1-zen
Earbuds version: https://aur.archlinux.org/packages/earbuds 0.1.9

@clotodex
Copy link

For me reconnecting multiple times does the trick
On the other hand https://github.com/ThePBone/GalaxyBudsClient sometimes works where earbuds does not
I wildly prefer the cli version but they seem to do still something different

@grazzolini
Copy link

I have a galayx buds2 pro and the earbuds tool works for it. It doesn't detect if ambient sound is enabled, but otherwise, it detectes the battery level, if noise cancellation is enabled or not, and lots of other info. Only thing I noticed is that, if the daemon is running and you use the touch controls to enable noise cancellation using the touch controls and not earbuds, it won't detect the change, unless the daemon is killed.

@clotodex
Copy link

I had a similar issue since the beginning with the buds2 (also in other tools, this is a samsung issue i think)
The way i connect:

while true                 
         if pactl list sinks short | grep -q "bluez"
                 echo "Device connected successfully!"
                 break
         else
                 earbuds disconnect
                 earbuds connect
                 sleep 5
         end
end

This works very well for me after samsungs update of last week. Keep in mind to keep the case open. And in some cases I need to disconnect on my phone first since it seems to take priority.
Hope this helps and hope this describes your issue.

@grazzolini
Copy link

I noticed that the daemon stops working after you resume from suspend. Even after you reconnect the buds, the daemon doesn't pick up the new status and still shows an error.

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

3 participants