Support Thread for Simple Walk

Store Link: https://apps.garmin.com/en-US/apps/028c5a06-48ed-4a5d-9910-236a7ef10ce0

While this may look like a watch face, it's actually an application to to record a simple walk!



While running, the main screen looks very much like a watch face, with all the typical things, but behind it are three additional screens. (swipe or up/down to get to them)

  • additional data including Temperature (Tempe required), Pressure (on watches with a baro altimeter), Altitude, Pace, Speed, Calories, and Laps (A-Laps means you are using auto laps! - Default is Auto-Lap each 1 mi or km)
  • a chart of your walk, with dots to indicate your start and each lap mark, as well as current heading
  • "Back to Start" with the direction and distance, your current heading, and current lat/lon


When the app starts, it will waits for GPS, and you'll be told to press start when GPS has a lock. Pressing start again pauses the recording, and gives you the option to resume, save, or discard the recording.

A number of things can be changed by using "settings" in Garmin Connect Mobile or Garmin Express, including the bottom like on the main screen. It will show you daily steps, daily cals, daily distance, and on watches that support it, floors and intense minutes.


I want to keep this a simple alternative to Hike/Hike2, so please look at those if you want additional features, as they may already have the feature. (My sig is a link to my other apps)
  • You may want to contact the developer of the Optimus watchface, as it might be something when the watchface is restarted. Simple Walk leaves things the same as when it started (it can't change anything in the firmware, etc). Does it also happen if you use the standard "Run" app?


    I will. It doesn't seem to happen with other apps but I will let the other guy know. My gut feeling is it's being caused by all the beta version or the changes to the developer framework.
  • It could be the firmware, as on the fenix3 devices, memory is managed a bit differently. Another thing you could try is use a different CIQ watchface and see if it happens.

    Update: I'm looking into this and may have found something......
  • brookes2622 -

    I found something that might explain what is happening (if so, the way I exited the app may not be working correctly in the f3-hr FW, so I used another method). Version 0.15f is now in the app store. could your install it and see if the watch face still has problems?

    Thanks in advance...
  • Simple Walk 0.15f + fenix 3 HR + Optimus watch face = problem

    Hello,

    I installed Simple Walk 0.15f on my fenix 3 HR with software version 4.0 and Optimus watch face.
    I'm experiencing the same problem reported by another user. After quit from Simple Walk, the watch face revert to default. I need to enable Optimus again.

    With Simple Walk installed I see that ERR_LOG.TXT is created in the root of the watch storage with the following information inside it:

    2413 (fenix 3 HR) SW ver: 400
    Build Type: RELEASE
    ESN: 3935725539
    Battery Voltage: 4.181000V
    11/08/16 20:26:36
    RTL
    errnum: 0x00f
    r0: 0x2002fb88
    r1: 0x00004865
    r2: 0x00000818
    r3: 0x00000099
    Return Address (LR): 0x00004737:Call Stack - PSP at 0x2002f9c0:
    0x00006ae1
    0x00004737
    0x00054c57
    0x00004865
    0x00004865
    0x00002533
    0x00004865
    0x00054ce3
    0x00004865
    0x000b3d43
    0x00004865
    0x0005359f
    0x00053a51
    0x0004000b
    0x000a9e45
    0x00103aa9
    0x000db9fd
    0x00103aa9
    0x00004c8f
    0x000a9faf
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x0012971d
    Uptime: 24704729

    2413 (fenix 3 HR) SW ver: 400
    Build Type: RELEASE
    ESN: 3935725539
    Battery Voltage: 4.167000V
    11/09/16 11:47:30
    RTL
    errnum: 0x00f
    r0: 0x20009638
    r1: 0x00134833
    r2: 0x00000070
    r3: 0x000000a6
    Return Address (LR): 0x00004737:Call Stack - PSP at 0x20009418:
    0x000bdd8d
    0x00004737
    0x00054c57
    0x00134833
    0x00134833
    0x00002681
    0x00134833
    0x00054ce3
    0x00134833
    0x00134833
    0x000b3d27
    0x0010da6b
    0x00134833
    0x00159635
    0x00004481
    0x00004479
    0x0009ed99
    0x0009ff4b
    0x0009ff7d
    0x0009ff87
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x0012971d
    Uptime: 55245658

    2413 (fenix 3 HR) SW ver: 400
    Build Type: RELEASE
    ESN: 3935725539
    Battery Voltage: 4.167000V
    11/10/16 06:29:00
    RTL
    errnum: 0x00f
    r0: 0x2002fb88
    r1: 0x000048ef
    r2: 0x000003d8
    r3: 0x00000090
    Return Address (LR): 0x00004737:Call Stack - PSP at 0x2002f9c8:
    0x00004737
    0x00054c57
    0x000048ef
    0x000048ef
    0x00002613
    0x000048ef
    0x00054ce3
    0x000048ef
    0x000b3d43
    0x000048ef
    0x0005359f
    0x00004c3d
    0x0009fd53
    0x00053a9b
    0x000a9e45
    0x00103aa9
    0x000db9fd
    0x00103aa9
    0x00004c8f
    0x000a9faf
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x0012971d
    Uptime: 67281496

    2413 (fenix 3 HR) SW ver: 400
    Build Type: RELEASE
    ESN: 3935725539
    Battery Voltage: 4.176000V
    11/10/16 13:42:22
    RTL
    errnum: 0x00f
    r0: 0x2002fb88
    r1: 0x000048ef
    r2: 0x000003d8
    r3: 0x00000092
    Return Address (LR): 0x00004737:Call Stack - PSP at 0x2002f9c8:
    0x00004737
    0x00054c57
    0x000048ef
    0x000048ef
    0x00002619
    0x000048ef
    0x00054ce3
    0x000048ef
    0x000b3d43
    0x000048ef
    0x0005359f
    0x00004c3d
    0x0009fd53
    0x00053a9b
    0x00040011
    0x000a9e45
    0x00103aa9
    0x000db9fd
    0x00004c3d
    0x000a9faf
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x0012971d
    Uptime: 25315925

    2413 (fenix 3 HR) SW ver: 400
    Build Type: RELEASE
    ESN: 3935725539
    Battery Voltage: 4.178000V
    11/10/16 20:25:32
    RTL
    errnum: 0x00f
    r0: 0x2002fb88
    r1: 0x00004865
    r2: 0x00000818
    r3: 0x00000090
    Return Address (LR): 0x00004737:Call Stack - PSP at 0x2002f9c0:
    0x00004737
    0x00054c57
    0x00004865
    0x00004865
    0x00004865
    0x0000ffff
    0x00054ce3
    0x00004865
    0x000b3d43
    0x00004865
    0x0005359f
    0x00053a9b
    0x000a9e45
    0x00103aa9
    0x000db9fd
    0x00103aa9
    0x00004c8f
    0x000a9faf
    0x000a9e45
    0x00000000
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x0012971d
    Uptime: 24183047


    Apparently, after removing Simply Walk no more error was recorded.
    I hope that the above information can be useful in finding the problem. Thanking in advance for any help attempt.
  • The Error_log.txt is the result of a full device crash (starts back at the Garmin logo) and is only meaningful to Garmin. All I can tell from it is that the file was written 11/08/16 20:26:36, so it's from 5 days ago.

    If the watchface fails to start, the file to post is in \garmin\apps\logs and called CIQ_LOG.txt

    Does it happen with other watchfaces? I suspect it's a firmware problem with the f3, maybe resulting in the watchface not having enough memory to run. The file I indicated may provide a clue.

    There is really nothing that Simple Walk could do which would case the watchface to crash - Another reason I think it's something in the firmware. What version of FW do you have? Is it a beta version?
  • Thanks for your investigation and help attempt.

    The content of the CIQ_LOG.TXT is simply "@PC = 0x00000000"

    But in the same folder (GARMIN > APPS > LOGS) there are another file named CIQ_LOG.BAK with the following inside:

    ERROR: Unhandled Exception
    DETAILS: Failed invoking <symbol>
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c
    CALLSTACK:

    WARNING: Unfreed memory on exit
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c

    ERROR: Unhandled Exception
    DETAILS: Failed invoking <symbol>
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c
    CALLSTACK:

    WARNING: Unfreed memory on exit
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c

    ERROR: Unhandled Exception
    DETAILS: Failed invoking <symbol>
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c
    CALLSTACK:

    WARNING: Unfreed memory on exit
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c

    ERROR: Unhandled Exception
    DETAILS: Failed invoking <symbol>
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c
    CALLSTACK:

    WARNING: Unfreed memory on exit
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c

    ERROR: Unhandled Exception
    DETAILS: Failed invoking <symbol>
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c
    CALLSTACK:

    WARNING: Unfreed memory on exit
    STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Too Many Arguments Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: bdc61482b5d741b689ba00472e0c5def
    CALLSTACK:
    @PC = 0x00000000

    ERROR: Out Of Memory Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: 31543af28d8a4299834837439829fb5f
    CALLSTACK:
    ERROR: Out Of Memory Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: 31543af28d8a4299834837439829fb5f
    CALLSTACK:


    I run the official v4.0 firmware release pushed via Garmin Express.
    At the moment Optimus is the only watch face installed in my fenix.
  • "STORE_ID: bdc61482b5d741b689ba00472e0c5def" are things reported for Optimus
    and "STORE_ID: 713d70e50c3b43b6aa49924ecbb0a34c" is from "Big Time" (but don't know when it happened).

    The "ERROR: Too Many Arguments Error" says to me that there's a bug in Optimus, maybe in a code path it doesn't normally take.

    Are you running the newest version of Optimus? Could it be that uninstalling/re-installing (that way you know you have the latest)
    resolve the problem?

    If not, try using a different watchface as a test, as I suspect that this is specific to Optimus, and won't happen with others

    This could also be something where the FW, for some reason thinks it's got less memory when it starts Optimus, and Optimus has errors.
  • Version 0.16

    In the next day or two I'll be updating Smile Walk with a few new items:

    • Added a screen with a large display of Elapsed Time and Distance so these two items are easier to see
    • Added the open where you can select how you are "alerted" to things. Vibration, Tones, or neither (Tones are only available on devices other than the va-hr, and vibration on devices that support vibrations (none of the non-wearables)
    • Added "floors" on devices that support them. When you ascend or descend stairs, you get a screen that indicates they were counted, and on the chart screen, a "U" will mark the location where you went up stairs, and a "D" where you when down stairs. This can be disabled in settings. Also, if you miss stairs, I'm just reporting what the firmware thinks happened :)
  • Hi Jim,

    This is my walking app now.

    Going back to my original suggestion; would it be possible to consider a screen with less details vs a larger font. The time font size works for me.

    Items that are of interest are:
    1. Clock
    2. Distance Walked
    3. <Duration / Speed>

    Thanks,
    Alan
  • In 0.16 there is a new screen with elapsed time and distance, using a large font. Use the up/down button to more through the screens.