Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Crash log when trying to use Forerunner 645 watch face

floppyrom
over 4 years ago

Hi

As nobody from Garmin responded to my previous post I am making a new one, hoping that someone from Garmin will read this and look into this.

I have a Garmin Forerunner 45 on the latest version 2.50. I installed the Forerunner 645 watch face from here https://apps.garmin.com/en-US/apps/eaa32b01-2868-4620-93f6-1e689bc5c75a

When I try to select it the watch crashes.

Here is the SNS_ERR.BIN file https://gofile.io/?c=nh8XIa

And this is the err_log file


3282 (Forerunner 45) SW ver: 250
Build Type: RELEASE
Commit:3637662d6284649f8afced008c419c6cbea74f80
ESN: 3996809814
06/13/19 18:28:07
RTL
errnum: 0x00f
r0: 0x20008b98
r1: 0x0005c4e7
r2: 0x000000c8
r3: 0x00000129
r4: 0x00019f80
Stack frame PC, SP: 0x0007d65d, 0x200081b8
Call Stack - SP at 0x200081b8:
    0x0005e3e1
    0x00005685
    0x0005c4e7
    0x0005c4e7
    0x00071dfd
    0x000728f5
    0x0005c4e7
    0x0005d10d
    0x000711f5
    0x0005c4e7
    0x0005c401
    0x0005c4e7
    0x0005cbe5
    0x0005d04f
    0x00020001
    0x00017383
    0x0005d0fb
    0x0005d9e5
    0x0005c401
    0x0005c401
    0x00013109
    0x1030f2a7
    0x000728f5
    0x000728f5
    0x10323c27
    0x000726c5
    0x103238a9
    0x10323c27
    0x000728f5
    0x103244e1
    0x000728f5
    0x00008001
Uptime: 35619131


  • 0 over 4 years ago

    Hello, in my opinion the device is quite new and the watch faces are not all updated to read all the watch sensors' correctly yet.

  • 0 over 4 years ago

    Hmmm, works fine in the emulator so not sure what's going on... do you have a ciq_log.txt or ciq_log.yml you can share? Can be found in the garmin/app/log folder of your watch when connected to the computer...

    I also responded to your question in the forum, the log there seems more like a general crash log and not directly related to my watch face.

    Do you get a connectiq error (usually an exclamation mark) or does the watch crash completely/restart? (The log seems to indicate the latter)

  • 0 over 4 years ago in reply to FlipStone

    CIQ WFs have been causing the fr45 to crash.  It's not your WF, it's a FW bug and it's been reported to Garmin.  I've seen it myself with my WFs on a fr45.  They only thing to do is to wait for new firmware - it's not your code.  I'll do a post about this in the CIQ bug report forum.

  • 0 over 4 years ago in reply to FlipStone

    Hi

    I just checked and there is no file in the garmin/app/log folder!

    The crash (the watch restarts and shows a triangle icon) almost always happens when browsing the watch faces and selecting your watch face. It's the only one I have which triggers the crash.

    Also the Garmin 645 watch face is not displayed properly on the Garmin 45 watch. I took a photo so you can see how it looks!

    This is the err_log.txt from GARMIN\Debug\ folder

    Both crashes happened when I wanted to select to your watch face or select away from it.

    3282 (Forerunner 45) SW ver: 250
    Build Type: RELEASE
    Commit:3637662d6284649f8afced008c419c6cbea74f80
    ESN: 3996809814
    06/23/19 10:29:21
    RTL
    errnum: 0x002
    r0: 0x20008b98
    r1: 0x00000000
    r2: 0x10331d73
    Stack frame PC, SP: 0x0007d65d, 0x200089d0
    Call Stack - SP at 0x200089d0:
        0x0005e3e1
        0x10331d73
        0x000719d3
        0x10331d73
        0x00008001
        0x000726c5
        0x10331d73
        0x1020bbb3
        0x101f76bf
        0x101fb671
        0x101fb669
        0x10205ded
        0x00040003
        0x0000ffff
        0x00010001
        0x00010001
        0x00010001
        0x000706ed
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
    Uptime: 81502851

    3282 (Forerunner 45) SW ver: 250
    Build Type: RELEASE
    Commit:3637662d6284649f8afced008c419c6cbea74f80
    ESN: 3996809814
    06/23/19 10:31:04
    RTL
    errnum: 0x002
    r0: 0x20008b98
    r1: 0x00000000
    r2: 0x10331d73
    Stack frame PC, SP: 0x0007d65d, 0x200089d0
    Call Stack - SP at 0x200089d0:
        0x0005e3e1
        0x10331d73
        0x000719d3
        0x10331d73
        0x00008001
        0x000726c5
        0x10331d73
        0x1020bbb3
        0x101f76bf
        0x101fb671
        0x101fb669
        0x00040003
        0x00010001
        0x00010001
        0x000706ed
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
    Uptime: 91875

    3282 (Forerunner 45) SW ver: 250
    Build Type: RELEASE
    Commit:3637662d6284649f8afced008c419c6cbea74f80
    ESN: 3996809814
    06/23/19 10:31:32
    RTL
    errnum: 0x002
    r0: 0x20008b98
    r1: 0x00000000
    r2: 0x10331d73
    Stack frame PC, SP: 0x0007d65d, 0x200089d0
    Call Stack - SP at 0x200089d0:
        0x000041b3
        0x0005e3e1
        0x10331d73
        0x000719d3
        0x10331d73
        0x00008001
        0x000726c5
        0x10331d73
        0x1020bbb3
        0x101f76bf
        0x101fb671
        0x101fb669
        0x10205ded
        0x00040003
        0x00010001
        0x00010001
        0x000706ed
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
    Uptime: 16823

  • 0 over 4 years ago in reply to jim_m_58

    That would be awesome if you could submit the bug with more input from your dev perspective. I added an extra log in my response juse now.

  • 0 over 4 years ago in reply to floppyrom

    I already have  submitted the info to Garmin.  Now it's just waiting for a fix....

  • 0 over 4 years ago in reply to jim_m_58

    Thanks for clarifying that jim, hope garmin fixes it soon then...

  • 0 over 4 years ago in reply to floppyrom

    That indeed looks way messed up, can't reproduce it though because it works fine on the emulator (including layout)... Can you let me know what fields you have where, and what settings you adjusted?

    Even though I can't imagine it making a difference, just in case... I calculate layout based on the dimensions of the watch, so not hard coded, no clue how this can happen unless it's also something in the firmware messing up.

    The log is not something related to the watchface, it is indeed a hard crash of the watch itself... very weird. (Connectiq app rel;ated crashes end up in the ciq_log.txt/ciq_log.yml and contain references to the lines causing the crash... as well as the app id. I don't know how to make sense of the log you posted).

    Hope garmin releases a firmware update soon as I don't have anything to go on for now...

  • 0 over 4 years ago

    Former Member could you also pass this to the developers please? 

  • 0 over 4 years ago

    Decided to remove FR45 support for now. Also getting negative reviews because of this.

    I can give you a version to sideload for future try-out (not sure if the current version will stay installed when I remove support). Won't be able to change the default settings though, but as soon as the fw-issue is fixed I'll add support again.