Handle problems during connection with a timeout#16
Open
fdlamotte wants to merge 130 commits intoizivkov:mainfrom
Open
Handle problems during connection with a timeout#16fdlamotte wants to merge 130 commits intoizivkov:mainfrom
fdlamotte wants to merge 130 commits intoizivkov:mainfrom
Conversation
Correction of typos
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
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.
Here is a first pull request with workarounds dealing with connection issues I had with my phone :
Note that I tried to make it work on my laptop but while I could pair with the watch, I've never been able to setup a proper connection, the watch stops trying to connect before the laptop connects ! (even with no timeout ...) so quality of connection depends a lot on the bluetooth chip server side ...
Not tested on a pi, as I have some but they are not setup. Did the tests on a oneplus 6 with postmarketos.
If this PR is accepted, I have some ideas on how to handle the actions linked with the watch in a more generic way than what I did on sxmo_gshock and I'll propose it afterwards. I think in the end it could even handle all the use cases I address on sxmo_gshock ;)