Newly Created Watchface automatically changed to Default Watchface in fenix 5

Former Member over 7 years ago

Hi,

I have created a new watch face (which was used in fenix 3) with small changes and build for devices testing. I have set the new watch face in fenix 5 then it display few seconds (3 to 5) then it s automatically changed to Default watch face in the fenix 5. However when i press any button then back to home screen i can see my created watch face, but again it will change after the same interval. Is there anything i missed here in coding? This watch face was working fine in fenix 3 without any issues.

Can anyone help me here to proceed, Thank You.

Coleman.Apps over 7 years ago

Hey ras02,

It sounds like you are getting an app crash. When you app has crashed you can look for the CIQ_LOG.txt which provides information about the crash. You can find out more about handling app crashes here.

There are a few more things you can do. If you find that the CIQ_LOG is not giving you much information, you can make sure to build a development build of the watch face through Eclipse by clicking ConnectIQ> Build For Device Wizard> Select your project and device> Make sure "Build release version of project" is unchecked (scroll down if you can't see it)>Finish

This will build a development build of the PRG which can be side-loaded to the Garmin>Apps directory on the unit. Now you can run the Watch face. When it crashes, more information will be printed to the CIQ_LOG.txt file to help you better understand what is causing the crash. You can also reply here with what is in the Log and we will be happy to help.

Thanks,
-Coleman

Former Member over 7 years ago

The Fenix 5X currently has a major issue with regards to watch faces and stored data; one of those issues sometimes seems to manifest in the watch face crashing and defaulting back to a standard face.

The other issues include incorrect HR data, problems getting the required data to generate sunriese/sunset times, saving and loading settings (the settings will revert back) and a number of other problems.

I PM'd Brandon about it some of the problems and this was the reply I got:

"The problems you mention with the fenix 5X are related to a known issue--the fenix 5X is different from a hardware perspective compared to the 5 and 5S, which is at the core of these problems. It's not a hardware problem, so there's no worry about faulty hardware. Instead, the 5X has some additional processing power that we've tried to use in a novel way, and it's not working out as well we'd planned. I've had a couple of other individuals contact me this week about these same issues, and in fact, we just discussed this yesterday in a weekly team meeting we have to review the latest reported issues. At this point, there are still decisions being made about this, but once the device team determines the approach they intend to take, we should be able to get these problems fixed pretty quickly. "

jim_m_58 over 7 years ago

With the f5x and the beta 3.21 FW (and associated bits like the sensor hub and display driver), HR looks the same to me as it does on other devices to me (f5, va-hr, 235,735) and seems fine.

In the case of sunrise/sunset, that seems a bit different. For watchfaces, they need the lat/log to calculate it, and since they can't access Position", the trick used is to grab the currentLocation of out the last Activity.info. The problem is that the info in Activity.info goes stale after a bit. (often in the range of hours. On the f5x, it goes state pretty much right when you save/discard the activity, so hard for a watchface to get.) Many watchfaces with cache the location for future use in the event that Activity.Info does go stale.

for HR, I've used some of mine, as well as Hermo's NoFrills and on the 3.21 FW, it seems fine (the data itself a watchface can access on the f5/fr5x/va-hr/etc only changes every minute or too.)

In the case of sunrise/sunset (really, getting the last known lat/lon), is to get things in a state where a lat/lon is available for a WF to "stash away for future use", as in "watch mode", the data needed seems always to be stale. Here's the trick:

Make sure the watchface is the "current/active" one on the watch. Start something like the run app that uses GPS. Once it locks GPS, start recording. Using the hot-key for "widget" (default is long press of "down"). You'll see the watchfaces (and can cycle through the widegt loop). This allows for the WF to get a lat/lon and save it. You can then go back to the run app (back button), stop and discard the activity, and go back to the normal watch mode. It will probably have a "known" lat/lot as a result.

Tried this on a few of my watchfaces, and again with NoFrils and it did the trick.

For crashes, I had one that simply wouldn't start as the current watchface. No crash or anything, and could be seen in preview or off the widget loop when in an activity, and that also runs fine with 3.21.

for the OP here, the watchface does run for a bit, so it's a case where as Coleman said, info in ciq_log.txt may help, as it could just be a bug that's not seen on the f3 version.

Former Member over 7 years ago

Hey ras02,

It sounds like you are getting an app crash. When you app has crashed you can look for the CIQ_LOG.txt which provides information about the crash. You can find out more about handling app crashes here.

There are a few more things you can do. If you find that the CIQ_LOG is not giving you much information, you can make sure to build a development build of the watch face through Eclipse by clicking ConnectIQ> Build For Device Wizard> Select your project and device> Make sure "Build release version of project" is unchecked (scroll down if you can't see it)>Finish

This will build a development build of the PRG which can be side-loaded to the Garmin>Apps directory on the unit. Now you can run the Watch face. When it crashes, more information will be printed to the CIQ_LOG.txt file to help you better understand what is causing the crash. You can also reply here with what is in the Log and we will be happy to help.

Thanks,
-Coleman

Hi Coleman, Thank you for quick reply. As you suggested have checked CIQ_LOG.txt log. Here is log mentioned in the file:

ERROR: Symbol Not Found Error
DETAILS: Failed invoking <symbol>
STORE_ID: 00000000000000000000000000000000
CALLSTACK:

Former Member over 7 years ago

Hey ras02,

It sounds like you are getting an app crash. When you app has crashed you can look for the CIQ_LOG.txt which provides information about the crash. You can find out more about handling app crashes here.

There are a few more things you can do. If you find that the CIQ_LOG is not giving you much information, you can make sure to build a development build of the watch face through Eclipse by clicking ConnectIQ> Build For Device Wizard> Select your project and device> Make sure "Build release version of project" is unchecked (scroll down if you can't see it)>Finish

This will build a development build of the PRG which can be side-loaded to the Garmin>Apps directory on the unit. Now you can run the Watch face. When it crashes, more information will be printed to the CIQ_LOG.txt file to help you better understand what is causing the crash. You can also reply here with what is in the Log and we will be happy to help.

Thanks,
-Coleman

Hi Coleman,

Thank you quick reply. I have checked the log and here is what it is mentioned in the CIQ_LOG

ERROR: Symbol Not Found Error
DETAILS: Failed invoking <symbol>
STORE_ID: 00000000000000000000000000000000
CALLSTACK:

Coleman.Apps over 7 years ago

Thanks for getting back to us. It looks like your CIQ_LOG doesn't have the callstack info or any info about the symbol. Did you double check to make sure that "Build release version of project" was not checked? This should give you more information including callstack info and the specific symbol that is missing.

Thanks,
-Coleman