Open
Conversation
|
|
JJ-69
force-pushed
the
add-vibio-protocol
branch
from
ba14994 to
2166a5c
Compare
Author
|
@blackspherefollower could you go over the code and possibly test it against other the other devices? |
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.
Added support for all 5 vibio devices. Implementation is very similar to that of vibcrafter, so I tried to keep layout and style of the code similar.
Only tested against 2 of the 5 vibio devices (dodson and rivera). Ble identifier might be wrong for the other 3 (though seems to be predictable), but looking at the original vibio apk aactual protocol implementation for these devices is the same.
Related to this feature request:
#840