• Replies 15 replies
  • Subscribers 23 subscribers
  • Views 1164 views
  • Users 0 members are here
Options
Related

Launcher icon in datafield

scottbeam
over 4 years ago

does anyone know what circumstances cause the launcher icon to show in a datafield?  I've always just had the launcher icon in my code, but it's not used and i've never seen it until just this past week or so with my latest version update.  All of a sudden, it shows after installation and the only way i've found to remove/get past it is to change the datafield to another built in field and then switch back to my datafield.

  • over 4 years ago

    I've only ever seen the icons used in the menus on my watch when I set up a data field...

  • over 4 years ago

    figured this out.  the launcher icon has REPLACED the IQ! crash icon - at least in datafields.  Must have happened in the most recent firmware for devices that now support CIQ 3.2.   I don't see anything in the release notes, so heads up to anyone else.  maybe this post will save you a few days of grief wondering what is going on.

  • over 4 years ago in reply to scottbeam

    if you are seeing IQ!, the data field crashed.  Check the garmin\apps\logs\ciq_log file.

  • 25 days ago

     I've having this issue with one user on an EDGE 1030. About 2-3 mins into the activity, the CIQ data field pops up the Launcher Icon. Nothing in the code references this icon. This is NOT a crash. You suggested Garmin replaced the IQ crash logo with the Launcher logo. Not true. It seems like the datafield is still running, but the firmware decided for some unknown reason to show the launcher icon instead of my onUpdate() UI view. Must be a rare situation since there is very little mentioned in this forum and this is reported by only one user. Did you ever figure out what caused that? I'm not sure how to identify the cause since no LOG entries are made and I can't replicate it in the SIM or on my device. 

    The data fields do reference local storage, and does perform a makeWebRequest. They are running two data fields that do somewhat similar operations in an otherwise pristine EDGE 1030 setup. And both show the launcher icon when this happens. So it almost seems like the two data fields are conflicting somehow. But this happens minutes after the successful web fetches and storage retrievals, so that seems to rule out device conflicts for those operations.

  • 25 days ago in reply to DaveBrillhart

    1. why do you write that "It seems like the datafield is still running"? What indicates that?

    2. if 2 of your DF-s are installed, then it can have some effect. I mean there's this bug that even if I have a watch-app (Hiker App), that records a Walk session, and that causes the Walk activity's CIQ datafield (Hiker DF) to record to the fit file, then it's even easier to imagine that 2 DF-s both installed in the same activity profile do strange things to each other, especially if both were created by you and they have some part of their codebase in common.

  • 25 days ago in reply to DaveBrillhart

    i actually haven't seen this issue in a long time.   assumed it was some bug on garmins end that they have corrected at some point since

  • 25 days ago in reply to windfield

    I solved it! On older devices that use Bg processing (before the 1040/5.1 devices), my data field accumulated a memory footprint that exceeded the limit. Not sure WHY it decided to not crash with the IQ logo and an Out Of Memory error in the CIQ_LOG file... but rather decided to present the Launcher logo to the user. But it did. I found an array I didn't use/need that consumed 6kb! Ugh. Thanks to the Memory Profiler in the sim. All good now. Weird. It worked on my 1050 that doesn't require BG processing, and on an EDGE 1000 that is a 2.4.1 device that doesn't use some other functions, so it kept that one under the limit.

  • 25 days ago in reply to flocsy🤠

    luckily found it! see my update. thanks!! I assumed it was still running because there wasn't a crash - no IQ logo and nothing in the LOG file. Now that I know what happened I guess it did stop running.

  • 25 days ago in reply to DaveBrillhart

    ah, so my original guess 5 years ago was right.   certain crashes cause the launcher logo instead of the IQ!.   very confusing.  guess that means i've gotten my memory issues under control since then since i haven't experienced it in a long time.  good find!

  • 25 days ago in reply to flocsy🤠
    DaveBrillhart said:
     I've having this issue with one user on an EDGE 1030. About 2-3 mins into the activity, the CIQ data field pops up the Launcher Icon. Nothing in the code references this icon. This is NOT a crash. You suggested Garmin replaced the IQ crash logo with the Launcher logo. Not true. It seems like the datafield is still running

    I mean:

    - you are responding to a post from December 2020. (For reference, it's 2025 now)

    - you are literally arguing with scottbeam as if he said just now that your situation (in 2025) is the same as his (in 2020). But actually he hasn't posted in this thread since 2020. You are the one who resurrected this thread from the dead.

    You realize that it's absolutely possible that for him, the launcher icon did replace the IQ logo, at that time, for the devices he tested. And it's also possible that Garmin reversed this change at some point (maybe it was a bug, as somebody else suggested)?

    Either way, do you think he still cares? Like I kinda get why you are responding to this 4 year old post (although I don't agree with it), but it's wild how you literally tagged OP and started arguing with him, as if it matters that something he said 4 years ago seems to contradict what you're seeing now.

    Imagine if some random replies to your comment in 2030 like this: "@DaveBrillhart I'm having this issue with one user on EDGE 2077+ (Super Pro Edition), running Connect IQ System 43.π. You suggested that when a data field shows the launcher icon, it's not a crash. NOT TRUE. This IS a crash. It seems like the data field is NOT still running..."

    That would be kinda weird, right?