CIQBUG - Crash with performance condition splash screen

hi garmin,

With the recent 6.5 firmware upgrade on the Fenix 3, there is a new feature called "performance condition" which replaced the previous recovery check feature.

This new feature, when it splashes up to the screen during an ongoing app session (app and not datafields), all inputs to the running app are lost and the existing running app will exit (and current activity will not get saved)

This "bug" seems to be similar to the one previously with autolap coming up at 8.05km and taking over the entire device/app and then crashin the app.

I have tested and determined that it is affecting my custom apps (Generic Recorder, My Custom RunFields) as well as the DWMap application.

This has made these apps to cease to function properly.

Please take a look and revert accordingly.

Nikeow over 9 years ago

Are you reading the thread properly?
I have actually mentioned it more than a couple of times.

Brandon.ConnectIQ over 9 years ago

I filed a report for this yesterday, but forgot to post back to the thread to let you know. We'll look into this--thanks!

Former Member over 9 years ago

Are you reading the thread properly?
I have actually mentioned it more than a couple of times.

I asked you if there were other apps besides yours that have the same problem, you said yes. So which ones are they?

Because all you're doing is saying that your apps are crashing. Common denominator here is your apps.

Nikeow over 9 years ago

thnaks Brandon. Hence, this is confirmed by garmin as an issue?

I tested again this morning. The MoxyRun app is also affected. Hence, till date the list of affected apps that I've tested is as follows

MyCustom RunField
DwMap
MoxyRun
Generic Recorder (when using trail run activity profile)

I tried various debugging methods, all didn't seem to work as a workaround. Initially I tot it was my custom lap code. Removed it and still the same behaviour.
Then I removed the timer callback (this essentially made the app screen non moving as the view doesn't update) but the same thing still happened.

This seems like it's a worst bug than the 8.05km splash screen bug.

Thanks!

jim_m_58 over 9 years ago

Reading this thread, it reminds me of the "fireworks crash" with the 2.80 FW for the vivoactive.

When you hit your daily step goal, you got a "fireworks" display, and if you had a CIQ watchface, it would often crash when going back to that watchface.

"fireworks" went into CIQ memory space and could damage that, IIRC, causing the crash, so it impacted any CIQ watchface, but often the watchface got blamed.

I'm thinking this is similar, in that when this is displayed, CIQ may get danced on. So it may not be a CIQ problem, but a FW problem.

Nikeow over 9 years ago

Agree. Per garmin, current CIQ implementation is shared memory space with garmin FW and thus garmin has the right to "sit" on any CIQ apps and squeeze the memories out.

but all in all, this is bad.. very bad.

jim_m_58 over 9 years ago

Agree. Per garmin, current CIQ implementation is shared memory space with garmin FW and thus garmin has the right to "sit" on any CIQ apps and squeeze the memories out.

but all in all, this is bad.. very bad.

In the 2.90 version of the vivoactive FW, Garmin FW folks contained the fireworks and stopped the problem. I'd bet the same happens here.

Nikeow over 9 years ago

Hopefully

Former Member over 9 years ago

As with the issues we had with the Lap banners appearing in the past, these native device screens should not be appearing during a ConnectIQ activity at all. This is something that we will correct in the device firmware.

JAMESMCS over 9 years ago

Also happening to me when trying to use dwMap on Fenix 3