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

Watch Reboot During Activity After v22.10 Software Update

Note: This thread is for the Fenix 6 series watch rebooting during an activity after updating to the v22.10 software. This original post is over a year old and is not the current issue. Since this is the thread everyone has made their reporting thread, this 1+ year old post remains the starting post but the conversation is for the v22.10 software. Thank you.


Hi,

This weekend I did a 24k trail using the Trail Run activity. At about 17km the watch rebooted and after the reboot I was able to resume the activity. Luckily I looked at the watch just when it happened so I didn't miss more than a few hundred meters and everything seemed ok except for the recovery advisor which probable only looked at the remaining part.
connect.garmin.com/.../6382781712

I had a course loaded but the screen was my standard screen showing only Garmin built in DF's (HR, Distance, Timer, Pace, Lap Pace, Lap HR, Elevation and Altitude). Another screen with the Stryd DF but apart from that no CIQ DFs.
SW 15.20, GPS 5.00, WiFi 2.60, CIQ 3.2.4, BMX 1.0.2, WHR 1.00.02, ANT/BLE/BT 6.11, Sensor Hub 8.00
Stryd Zones 1.8

I've read other threads with similar problems and one thing they have in common is notifications. I can't fo sure say that I got a notification and responded to it but I don't think so. A couple of questions:

  • Is it worth contacting support? I think that it is a serious problem but on the other hand hard to reproduce.
  • Any configuration or features that I should avoid? I don't want this to happen again.
  • Same problem here with my Fenix 6 pro on 22.10 - will it be worth it to do a hard reset?

  • will it be worth it to do a hard reset?

    No - that is not the appropriate response.

    Get a copy of the crash logs from /Garmin/Debug - RAM.txt and err_log.bak

    It worries me that users are so conditioned to poor quality software updates the knee jerk response is to hard reset. Hard resetting loses any chance to do a root cause analysis on the cause of the crash.

  • Thanks for the reply - i located err_log.bak but not RAM.txt - must i attach a copy of the file here?

  • I have sent Garmin a query about this as well to [email protected].
    Added the Forum Discussion, and sent my latest Garmin Device xml file.

    THEY NEED TO FIX THIS!
    Really not happy

  • Yes i was very happy with almost 3 years trouble free usage, but now this is bad!

  • Bumping the thread. Garmin respond please.

  • If you want Garmin to respond mention the watch strap gives you a rash - it summons then like a rubbing a lamp summons a genie so they can lock the thread

    They are very selective in what they choose to respond to.

    Bumping the thread. Garmin respond please.
  • Same on my fenix 6 with SW 22.10. Unregular reboots during activity. It seems to happen much more often if navigation is active (on fenix 6 without map) or a segment is shown. I already tried a factory reset with erase of all data and installed only a minimum of add-ons but this does not help. Very disappointing.

  • I really hope Garmin can do something about this!! It is very frusrating!!

  • Once again, my watch reboot this morning after about 1 hour of walk activity GPS, HRM pro, and music with BT Headphones

    Here's the error_log file

    3291 (fenix 6X Pro Solar) SW ver: 2210
    Build Type: RELEASE
    Commit:c96a7bc00a3dd9df4aa849dbc6841b70c6483579
    ESN: 3319620039
    06/28/22 10:59:48
    RTL
    errnum: 0x00f
    r0: 0x1fff6888
    r1: 0x000bc3db
    r2: 0x00008000
    r3: 0x0000013f
    r4: 0x0003acd0
    r5: 0x00000603
    r6: 0x00706c70
    Stack frame PC, SP: 0x00003383, 0x1fff6680
    Call Stack - SP at 0x1fff6680:
    0x000023f1
    0x00003a95
    0x000bc3db
    0x000bc3db
    0x000bc3db
    0x00003da3
    0x000b90dd
    0x000bc3db
    0x000b9507
    0x000bb3e5
    0x000bb8bb
    0x00004a0d
    0x000bb601
    0x00004a0d
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    Uptime: 515974939