-
Notifications
You must be signed in to change notification settings - Fork 44
Introducing support for Garmin Connect IQ devices #10
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
Open
marccardinal
wants to merge
41
commits into
JumpMaster:master
Choose a base branch
from
marccardinal:garmin-connect-iq
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
Add Russian localisation and kingsong alarms preferences.
mBtName isn't populated (is an empty string) if we don't start from a fresh bluetooth pairing with the GT16, so the battery gauge is wrongly calculated based on a 67.2V battery instead. Instead, check mName for a "ROCKW" prefix, as this is available even on subsequent sessions.
Fix usage of carriage returns in csv exports to google drive
…tion Fix rockwheel detection
Update README.md
… nanohttpd Details about the issue can be found here: https://forums.garmin.com/developer/connect-iq/f/legacy-bug-reports/5144/failure_during_transfer-issue-again-now-using-comm-sample People have reported receiving a FAILURE_DURING_TRANSFER when sending messages to the watch with a short interval, this also seems to happen after a certain number of messages have been sent to the watch according to people on the forum. On my end two people one with a F5X+ and another with a VivoActive 3 Music have reporting the issue intermittently too. So instead of having the android app push the data I am now having the watch poll the data via a /data request to localhost on an ephemeral port. This is a workaround until Garmin decides to tackle the underlying issue (the forum post is from 2yrs+ ago)
cedbossneo
pushed a commit
to cedbossneo/WheelLogAndroid
that referenced
this pull request
Oct 27, 2019
Introducing support for Garmin Connect IQ devices
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.
This has been tested on various versions of the Garmin Fenix 3 and Fenix 5 watches. I also submitted a companion watch app to the ConnectIQ store: https://apps.garmin.com/en-US/apps/07a231a9-3f2f-4762-b0bb-b8a0b5594f40.
Let me know if you have any questions or need any clarification!