AllSySt3msG0

@Dan Hillary yes unfortunately the Garmin watches are mostly single thread in the sense that they can run one main program at a time. I'm not 100% sure but I think the tracking for running and skiing is done in the garmin connect phone application and I should be able to make the watch app send the proper activity tracking information. I'll double check this week. On another note I have been in touch with Seba and we will look at bringing Garmin watch support to euc.world. Thanks all!

@Dan Hillary I'll take a look at supporting the Vivoactive 4 and 4s this evening! We have a lot of snow here right now and that means less wheel, more dev I'll let you know how it goes

Thanks for the feedback @Pedro Capitão, I'll take a closer look at the layout on the vivoactive3 and will report back

Good morning all, The version 1.0.13 of the watchface now supports additional watches: Fenix 6 Fenix 6 Pro / 6 Sapphire Fenis 6S Fenis 6S Pro / 6S Sapphire Fenix 6X Pro / 6X Sapphire / 6X Pro Solar Forerunner 630 Forerunner 645 Forerunner 645 Music Forerunner 935 Forerunner 945 As usual let me know if you run into trouble

I will add support this weekend, it will be available soon

Good evening, @Mitch I added support for Forerunner 230, 235, 245, 245 Music in the version 1.0.12 of the watch application. I still need to tweak the layout a bit for the semi round/truncated screen but it should get you started. @an5vf I will need a bit of time for the Forerunner 45, it looks like that one doesn't support applications so I need to see if I can make a watch face instead. If all goes well that work won't just be for the 45 but for all of them... there will be a choice between watch face or watch app (face has battery constraints and might sleep / have a slower refresh). Let me know if you run into issues

Good evening all! I have been hard at work on finding a solution to the intermittent FAILURE_DURING_TRANSFER message that some people have reported. In retrospect, it looks like it was caused by a well known bug on the Garmin ConnectIQ platform that has been going on for quite a bit of time and the details can be found here: https://forums.garmin.com/developer/connect-iq/i/bug-reports/failure_during_transfer. Given the level of annoyance from this I worked on a workaround that other folks have also implemented (like the guys from Locus Map) and unfortunately I hit a wall when on the release of Garmin Connect v4.20 they broke that one too (https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-version-4-20-broke-local-http-access). So they have now released the version 4.22 of Garmin Connect and that one should finally give us a stable platform. I opened a PR for @palachzzz to have the fix upstreamed and available on the Play Store (https://github.com/palachzzz/WheelLogAndroid/pull/11) in the meantime if anyone want to try it out you can: - Use the v0.3-garmin that I have made available here: https://github.com/marccardinal/WheelLogAndroid/releases/tag/v0.3-garmin - Install the watch application version 1.0.10 or above (https://apps.garmin.com/en-US/apps/07a231a9-3f2f-4762-b0bb-b8a0b5594f40) - Make sure that you have the Garmin Connect application at version 4.22 or above @Mitch and @an5vf I didn't forget about you regarding the Forerunner 235 and 45. I should be able to tackle those Friday or this weekend. @Seba I had a couple of people ask if it was possible to add the Garmin ConnectIQ support on your version of WheelLog available on your website. Let me know where I can submit a PR! Thanks for your help and the great feedback everyone, additional devices and features are coming... you can find my TODO here: https://trello.com/b/vhZBxL05/wheellog-garmin-connectiq.

Hi guys! I have an update from Garmin pertaining to the FAILURE_DURING_TRANSFER messages, the direct cause of that is not being addressed yet but I have a workaround ready for it that completely makes them disappear. That workaround however broke with the release of Garmin Connect v4.21... given the big headaches that the 4.21 issue caused to owners of many long running garmin apps, they decided to backtrack and a fix will be in v4.22 (for more information: https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-version-4-20-broke-local-http-access?CommentSortBy=CreatedDate&CommentSortOrder=Descending). In the meantime you might still see the FAILURE_DURING_TRANSFER errors from time to time and I'll work on the features outlined on the trello board here: https://trello.com/b/vhZBxL05/wheellog-garmin-connectiq. Let me know if you have questions! Regarding @an5vf's question, a list of supported watches is available here: https://apps.garmin.com/en-US/apps/07a231a9-3f2f-4762-b0bb-b8a0b5594f40#0. I don't have the forerunner yet but I will start on the ForeRunner 235 that was requested by @Mitch. More will come

Hi Mitch, not right away but there are talking of bringing support for this to DarknessBot, the iPhone equivalent of Android's WheelLog. I am currently focussing on fixing some of the kinks we have seen on Android with the ConnectIQ SDK (I have two threads on the dev forum) and we will try to bring the support to iPhone too. Can you tell me the forerunner model? I'll make sure that there is a layout planned for that one (there are a lot of forerunner). Thanks!

What you describe is very similar to what other people have been getting with Android + ConnectIQ + Garmin Watches in general. There is a ticket open on Garmin's side regarding this and I added my comments to it but in the meantime I am implementing a workaround that should make those FAILURE_DURING_TRANSFER disappear.

Hi @Pedro Capitão, in v1.0.10 you will find that I increased the size of the time, battery and temperature fonts from 19px to 25px for the watches with a resolution of 148x205 like the VivoActive HR. Let me know if that helps!

Thanks for testing @Pedro Capitão, I'll work on modifying the layout to allow for larger font for time, temperature and battery this evening and I will check if I can do what you describe (go back to the watch face and then switch back after 5 sec).

@Pedro Capitão I'll add that to the roadmap so I don't forget I put the layout together pretty fast to unblock that but I was expecting to have to come back to it. Regarding the time from the last power on it will be part of another screen, I received feedback to display the distance since last power on, time from power on and lifetime distance. Coming up are also vibration / beep alerts on the watch that are connected to alarm1 alarm2 and alarm3 on the wheellog application. Also have the display change color based on the speed. Let me know how it goes!

@Pedro Capitão I will double check the VivoActive HR in the simulator on 1.0.8, did you install WheelLog from the play store or from the APK here https://github.com/marccardinal/WheelLogAndroid/releases? Do you also have the Garmin Connect application installed installed? On another note I received reports of people getting a FAILURE_DURING_TRANSFER intermittently, there is currently a thread regarding this on the Garmin developper forum, it looks like many other projects are getting that one after sheer number of message or when they are sent at a quick interval from the phone to the watch. There are talks of workaround and I am currently working on that implementation. The watch would poll the phone instead and this would actually ease an integration with DarknessBot (fyi @Ilya Shkolnik). There are some kinks to iron out but I'm confident we will get it to work reliably

Thanks a lot for the feedback so far @palachzzz, it is much appreciated and it certainly helps to avoid yet another fork of wheellog I created a Trello board to put some order in my todo list, feel free to comment on tasks or contribute to it: https://trello.com/b/vhZBxL05/wheellog-garmin-connectiq.