Feature/docker documentation#75
Open
Tharun-deakin wants to merge 59 commits into
Open
Conversation
Created Setup for automated build
- build-develop.yml: Triggers on push to develop branch - build.yml: Triggers on push to main branch - release.yml: Triggers on version tags (v*.*.*) All workflows build .prg files for 16 Garmin devices in parallel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- build-develop.yml: Triggers on push to develop branch - build.yml: Triggers on push to main branch - release.yml: Triggers on version tags (v*.*.*) All workflows build .prg files for 16 Garmin devices in parallel.
Changed device identifiers to use underscore suffix (e.g., fenix7_ instead of fenix7) to match the SDK's device naming conventions. Simplified device list to supported devices. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Changed minApiLevel from 3.2.0 to 2.3.0 for broader device support - Removed fr235 (incompatible with supported API levels) - Updated all workflows to match supported 15-device list - Verified compilation works for fr245 and fenix7 locally Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Removed 'Download device definitions' step that was failing with exit code 8 - Removed fr235 from device list (incompatible with API level 2.3.0) - Removed pull_request trigger and feature/** branch trigger - Keep only push to develop trigger for build-develop.yml - Device list now consistent: 15 supported devices Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…52) - Removed 'Download device definitions' step that was failing with exit code 8 - Removed fr235 from device list (incompatible with API level 2.3.0) - Removed pull_request trigger and feature/** branch trigger - Keep only push to develop trigger for build-develop.yml - Device list now consistent: 15 supported devices
Narrowing down to test if ANY device works in the Linux SDK. If venu2 fails with same error, the issue is with device support in the Linux SDK environment. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Narrowing down to test if ANY device works in the Linux SDK. If venu2 fails with same error, the issue is with device support in the Linux SDK environment.
Build .prg file for fr 165 and fr 165m
<img width="384" height="661" alt="image" src="https://github.com/user-attachments/assets/3f137c1a-f4e9-4a87-8a2c-21632179faa0" />
Update
Update manifest.xml and New fix build for fr245m
Reset settings branch
Revert "Reset settings branch"
branch remade to remove changes from merged wrong main. Updated code to work with updated cadence target variables and made back button return to settings and not crash. NOTE: still crashed if screen is tapped after resetting settings.
fixed reset settings
…e clearer error messages
…mats with authorization
…mats with authorization
…zip formats with authorization
…tIQ Devices folder The monkeyc compiler (monkeybrains.jar) requires per-device compiler.json files at ~/.Garmin/ConnectIQ/Devices/<device>/. This data is separate from the SDK binary and is normally installed by the Garmin SDK Manager. Without it, monkeyc fails with 'Invalid device id specified' during compilation even though device name validation passes. Packaged all 16 target device profiles into connectiq-devices.tar.gz (8.6MB), uploaded to the sdk-assets release, and added CIQ_DEVICES_URL secret. Each workflow now downloads and extracts device profiles to the expected Linux path before compiling. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ndling and validation
Added a small vibration status indicator to SimpleView so users can see whether vibration alerts are enabled or disabled.
Updated the start recording confirmation screen layout by simplifying the title, moving the icons and colour styling.
Add vibration mode indicator to main view
Clean up start recording confirmation screen UI
Created Setup for automated build
updates features to PO's specification, fixed merge issues.
Created a build download doc
# Summary This PR adds the machine learning and Power BI dashboard work for the Garmin smartwatch project. #Files added - ML notebook for running duration prediction - cardio activities dataset - Power BI dashboard file # Notes - The ML work focuses on predicting running duration - The dashboard includes running performance and relationship analysis visuals
Created Docs foe downloading the build specific for multiple 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
6 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.
No description provided.