Fix annoying Linux bluetooth connection bug#405
Merged
Conversation
Owner
|
Thanks! I think several people had this issue, but I wasn't able to reproduce it on my machine for some reason. |
|
Thank you! I haven't been able to use this app because of this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When you try to open up the app after your earbuds are paired and connected, it will throw you this error: "org.bluez.Error.Failed Operation already in progress". This happens because the BluetoothService attempts to connect to an already connected device. I see that in the code you expect BlueZException to be thrown with the error code "AlreadyConnected", but that usually doesn't happen, and instead you get the "Failed" error code with the above-mentioned error message. This is what basically causes the bug. And to fix this issue, we just need to check if the device already connected. It is easily fixable with just two lines of code.
Has anyone encountered this issue before? Because it looks like a common issue