That screen simply means your app has crashed. The best way to debug this is to create a CIQ_LOG.txt file in the /GARMIN/APPS/LOGS folder. When an app crashes a stack trace will be saved there. The stack trace should be able to point you in the right direction as to what's going wrong. If you need some help understanding the stack trace there are several developers on these forums that can lend a hand.
I can consistently reproduce the crash by starting and stopping an activity and discarding it. After the "Recovery Time" screen, the crash screen is shown.
Should I make a new thread, or will you be able to help out?
To be fair, I do acknowledge that the layout and function are a copy. I wanted to see if I could make my own data field and started out with yours as inspiration. I wasn't aware of the fact that I could side-load the app on my Fenix and thought the only way to get it on my watch was to put it on Garmin Connect.
I'm more than willing to remove it from Garmin Connect, should you feel that that is necessary..
To elaborate a bit more: I also wanted to have more freedom on what fields would be displayed, e.g. I wanted to include heart rate zones. A data field with climbing info is also planned..
The screen you have posted an image of is not the crash screen. It looks almost the same as the crash screen. However, this graphic contains a "..." in the orange circle, and the crash screen contains a "!" in the orange circle.
The "..." graphic is used by the Fenix 3 because it is not able to start up ConnectIQ data fields until after a session has been started. Other devices (e.g. the Forerunner 920XT) start the fields when the profile is selected, prior to the start of the activity.
Does this mean there is no way around this limitation for the Fenix3?
The screen you have posted an image of is not the crash screen. It looks almost the same as the crash screen. However, this graphic contains a "..." in the orange circle, and the crash screen contains a "!" in the orange circle.
The "..." graphic is used by the Fenix 3 because it is not able to start up ConnectIQ data fields until after a session has been started. Other devices (e.g. the Forerunner 920XT) start the fields when the profile is selected, prior to the start of the activity.
To be fair, I do acknowledge that the layout and function are a copy. I wanted to see if I could make my own data field and started out with yours as inspiration.
I wasn't aware of the fact that I could side-load the app on my Fenix and thought the only way to get it on my watch was to put it on Garmin Connect.
I'm more than willing to remove it from Garmin Connect, should you feel that that is necessary..
<soapbox on>
And putting untested stuff in the app store is a bad idea. More reason it should be pulled from the store ASAP. I hope you've learned about sideloading now! :)
Untested stuff in the app store gives ALL CIQ stuff a bad name!
<soapbox off>
<soapbox on> And putting untested stuff in the app store is a bad idea. More reason it should be pulled from the store ASAP. I hope you've learned about sideloading now! :)
Untested stuff in the app store gives ALL CIQ stuff a bad name! <soapbox off>
I've just pulled it off CIQ. Will continue to use for personal use :) Hope to learn more on this forum, so I can implement some features that set the app apart from NIKEOWs. Thanks for the advice.
coming back to topic : what's your memory usage like? (From the simulator, lower right hand side) I've come into situation where my memory usage is 14/16kb and then one little thing will push it off the edge and kaboom.
coming back to topic : what's your memory usage like? (From the simulator, lower right hand side) I've come into situation where my memory usage is 14/16kb and then one little thing will push it off the edge and kaboom.
Previously, the mem. usage was around 12/16kb. I was using a layout to draw screen filling rectangle to make the background white. In addition, I was drawing lines by making 1px rectangle shapes. I know, right....
This morning I changed all that and am doing my drawing of static content in "onUpdate(dc)" instead of using layouts. Also found this handy function called 'drawLine' ;). This reduced mem. usage considerably to about 8/16kb.
What I do notice is that after I side-load the app on my Fenix, when I open the Bike app, the transition animation is very choppy (I have the data field set as Field 1). Do you have any idea what could be the cause? I can share code if needed..
