-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
[BUG] "Bad file descriptor" when using "Enter pairing mode" option #422
Comments
OK so this option seems to send an undocumented command which may not present on Live.
It's also mentioned in the manual but buried way down under the "using our app to pair" stuff so that's probably why I missed it. So simply put: This feature in the app should not be used or should be disabled on older buds. Or better: hint the user about the alternative way of entering pairing mode when the buds are a known set that don't support the pairing command. |
Describe the bug
"Enter pairing mode" option does not put the buds into pairing mode, instead "Bad file descriptor" is shown and causes the app to not communicate to the buds unless the app is restarted.
To Reproduce
Steps to reproduce the behavior:
System -> Enter pairing mode
Expected behavior
Buds entering pairing mode.
Screenshots
Desktop (please complete the following information):
Additional context
Hardware: Galaxy Buds Live (rev0.5)
Firmware: R180XXU0AVJ1 (2022.10.12/00.02.33/SWHD7404)
Log files
The text was updated successfully, but these errors were encountered: