Forerunner 45 (FR45) Layout Problems

Rookie dev here. After creating a watch face for personal use on my Vivoactive 3, I was asked to make it available for others. I started with just the round-240x240round-218x218 and semiround-215x180 watches which seemingly covers 85% of all hardware. But it seems the men can't settle on 1-2 devices, and the 15% started coming out of the woodwork requesting a face for their device as well.

Yesterday I took a stab at the Forerunner 45. I tried creating a resource directory for round-208x208 but the simulator did not appear to be using the custom resources. I had better luck with resources-fr45 although the simulator still did not recognize the custom settings folder (limited color choices).

When viewing the FR45 in the simulator, I was seeing this:

When my user downloads the app from the CIQ store, he is seeing this:

Note the difference in font for TIME between simulator and real world -- I used a custom bitmap font (Roboto Black/Medium) for the other devices, but purposely used FONT_NUMBER_MILD in the resources-fr45 layout. It appears like the FR45 is using the default resources folder (240x240) which uses the custom bitmap font. Although you would think that using a layout for a 240x240 device would spread the elements apart rather than cause them to scrunch together on a smaller screen.

I confirmed with my user that several custom faces have the scrunched look. He also stated that he received an error when attempting to go into the settings:

Interestingly enough any custom watch face is doing this scrunch thing. When I try to load settings it says there was a problem communicating with your Garmin device.

Is anyone having any luck with the FR45? Is there a trick I am not finding in documentation/forums that would allow the FR45 to correctly use my watch face? FWIW, I am using SDK 3.0.12 in the Eclipse IDE.

  • There have been posts about the layout in the fr45 device forum, and I've seen it myself, and is a firmware bug.  From what I've seen it looks to be a problem that involves dc.getFontHeight() (which is still involved if you use layouts).  So, not much to do until the fw bug is resolved.  I have 9 of my watchfaces I've yet to publish for the fr45 due to this.

    The GCM/settings thing may also be FW, but I've not heard of that one before.

  • Thanks. Your answers to several questions in these forums have been a huge help as I am getting started with Monkey C.

    Being new to the forums, I was unaware of the device-specific areas. I now see a couple of threads there that mention problems with communication between Connect app and FR45. They all say to use the Garmin Express (Mac/PC) app instead.

  • I've verified this and see the same thing. I tried running the 3.1.0.beta3 sim as well to see if this was an issues where sim was off, but it looks like it might be device integration side. I've reopened this ticket we had for layout issues before.

  • There is new 2.80 FW being rolled out to the fr45, and at least for all my watch faces, fixes the layout problems.

    I'm using the 3.0.12 SDK.