WheelLog Android App - With Garmin ConnectIQ Support

[AllSySt3msG0]

@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

[Pedro Capitão]

2 hours ago, AllSySt3msG0 said:

@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

Ok,I did it.

1 - Unistalled version on the phone, installed from the App (github)

2 - Open Garmin Connect

3 - Connect Bluethooth

4 - Power on wheel

5 - Open WheelLog (on the phone) + option Garmin Connect (permit)

6 - Open WheelLog (on the watch)

 

My levels, temp and batt power left running OK.

@AllSySt3msG0 may temp and bat power be with an higher font... we cannot see anything - too small - please. I like to know the time from the last power on (ridding) if possible. Many, many thanks, man!

today I'll test it on the road... 'll give you feedback...

[AllSySt3msG0]

@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]

5 hours ago, AllSySt3msG0 said:

@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!

I ve got the FAILURE_DURING_TRANSFER msg I think it was when I paired with the other Bluetooth of the wheel to put music in the wheel speakers... I am not sure.

If possible the ViviactiveHR back button return to Home page to the watch instead of get off app. Just keep 5 seconds at home page (hours, minutes, etc.) and then return to wheelLog app... cause, again... the font of time in the app are so small too that you can't see nothing unless you stop and take off your sunglasses.

Very good to have those features and a second screen

Many thanks

 

[AllSySt3msG0]

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]

26 minutes ago, AllSySt3msG0 said:

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).

Ok, thanks in advance but don't rush. I will test and give you feedback.

[AllSySt3msG0]

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!

[Pedro Capitão]

15 hours ago, AllSySt3msG0 said:

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!

Ok, seems the same as before, you should go 36px, if possible... like 3/4 of the speed font size, maybe. It's working fine in my 65kms today in Lisbon, sometimes apears the "FAILURE_DURING_TRANSFER" msg... it seems to appear in a regular time, like after 1 minute or so or if loses connetion with Garmin, if Garmin shuts down - after a long period of time, 30 minutes or so, seems that "Garmin closes the door" and WheeLog loses conection. You have to open Garmin again?!?!? Thats because of this situation the msg appears many many times till you close everything...

[AllSySt3msG0]

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.

[Pedro Capitão]

2 hours ago, AllSySt3msG0 said:

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.

Ok, glad to hear that from you.

I was wondering if it's possible to keep Garmin watches running Garmin app, like tracking a trail with Gps and alternate with WheelLog just to see how wheel is going on? I realised that we can do one of the 2 things... or an other solution, it will be very usefull, don't you think?

[palachzzz]

By the way, the WheelLog with Garmin support already in Play Market.

[Mitch]

Newbie question here, I have an iPhone and a Garmin forerunner. Am I able to do anything with those 2 devices when my MSuper X arrives? 

[AllSySt3msG0]

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!

[Mitch]

28 minutes ago, AllSySt3msG0 said:

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!

Thanks that would be great. Its a forerunner 235 

[an5vf]

Hey @AllSySt3msG0, thank you so much for your wonderful contribution to wheelLog! So if I'm understanding this thread correctly, wheelLog can now support the following garmin watches:

Fenix series

Forerunner series

Vivoactive series

Is that right? Also do you or anyone else know if these watches are compatible with magnetic watch bands/straps? If you have one you could recommend I would greatly appreciate it. Thank you and my apologies if this information is available elsewhere!

 

[an5vf]

Also does anyone have recommendations for which watch they would use? 

[AllSySt3msG0]

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

[Mitch]

15 minutes ago, AllSySt3msG0 said:

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

Nice! 

[Pedro Capitão]

Hi,

 

my Garmin Vivoactive HR fail to dead... I'm working with Garmin support to gat another one. For now I cant do any tests regarding WheelLog... sorry @AllSySt3msG0.

 

[an5vf]

On 8/14/2019 at 6:41 PM, AllSySt3msG0 said:

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

Any update on the availability of the forerunner series? If possible could you add the forerunner 45 as well?

[AllSySt3msG0]

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.

[AllSySt3msG0]

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

[Jia Liu]

Just chime in to say "Thank you!" 

Before the FAILURE_DURING_TRANSFER fix, the app was unusable, it could show wheel status for a few seconds, then the dreadful FAILURE_DURING_TRANSFER toast appeared and never went away, and the status was never updated. So I gave up and waited for the fix.

Today I updated Garmin Connect to 4.22, installed wheellog-v0.3-garmin.apk from the github repo, and just did a few minutes test ride around the house. It works great! I will do a long ride tomorrow and see how it goes.

My equipments are Gotway Nikola Plus, Samsung S7 edge (my old disposable phone ), and Garmin fenix 5X.

[Seba]

On 8/23/2019 at 5:50 AM, AllSySt3msG0 said:

@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!

Sure, here is my GitHub repo - https://github.com/slastowski/WheelLogAndroid

[Leucistic]

On 8/24/2019 at 7:01 AM, Jia Liu said:

Just chime in to say "Thank you!" 

Before the FAILURE_DURING_TRANSFER fix, the app was unusable, it could show wheel status for a few seconds, then the dreadful FAILURE_DURING_TRANSFER toast appeared and never went away, and the status was never updated. So I gave up and waited for the fix.

Today I updated Garmin Connect to 4.22, installed wheellog-v0.3-garmin.apk from the github repo, and just did a few minutes test ride around the house. It works great! I will do a long ride tomorrow and see how it goes.

My equipments are Gotway Nikola Plus, Samsung S7 edge (my old disposable phone ), and Garmin fenix 5X.

I`m here too to say "big thank you!""  for all the hard work you guys have done. Now with the fix i can use my watch.

My equipment is King Song 16S, Huawei P9 and Garmin Vivoactive 3. After some polishing this will be exellent.