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

Fenix 7 X experiencing random restarts during outdoor activity with GPS

Hi,

I have a Fenix 7 X solar since it was launched in Spring 2022. I have been experimenting during several occasions random restarts in my outdoor activities when using GPS.

First time it happened after two or three months of usage I tried first to make a soft restart which did not fix the issue. Then I tried a hard reset where I deleted everything I had installed in my watch (screens, IQapps, etc) that did not fix anything although it is a really pain in the a%s thing to do because you have to waste time configuring everything as you had before.

At some point, I do not really do not not why, the problem stop appearing. I have been reading different posts in the forum and it looks that the problem could be caused because of the maps our devices have installed. If that would be the case maybe a map version update or a firmware update fixed the problem.

Unfortunately the problem started appearing again in February this year. I do not know either the reason. Could it be a maps or firmware update? This time I got really upset. I was not able to follow my running planned training with a watch I paid more than 1.000€ for. The restarts were random and in some activities which lasted around 60 minutes happened twice or even three times.

I decided to contact customer support. It was a long process in which I spent lot of time sending all the information that was requested which was for nothing as I was not getting a proper answer back. Finally I asked if I could send the watch and receive a new one which was not having the issue. Garmin accepted and I sent the watch, after several weeks my watch was returned. They did not change the watch though, they just tried to reproduce the problem during several outdoor tests but as they were not able to reproduce they returned it.

After the watch was returned on 4th May this year I did not experiment the problem so I was happy. Unfortunately the problem appeared once again last week. For example last Sunday in a 70 minutes football activity tracked with GPS the restart happened more than 10 times. I am really frustrated now with this watch. I have been reading more and more information about people who has suffered this problem. Some of this people have asked Garmin to get a new device which works, as a 1.000€ device it is suppose to work, and  they have got a new one after sending the faulty watch.

I think I will need to proceed again contacting Garmin support and ask for it again. I hope this time they return me a new one instead of trying during two outdoor activities to reproduce the problem. The problem is that contacting support it is a time consuming activity and I do not have free time at the moment. It is also a pain for me to be without the watch during one month between sending the watch and waiting for a new one.... so I am still not contacting support again.

I have decided to open this post to inform people who have a similar problem and Garmin employees which can read this message. I have just deleted the maps from my watch and will test without them to track outdoor activities. Let's see if the problem disappears. In this case I will inform about it and I hope Garmin employees can check what is wrong with the Maps they install in the devices. Although I have to say that I believe it is not only a problem in the map (in case it is). There must be also a hardware problem in some devices as this is not happening for all the Fenix 7 devices (fortunately).

PS: I am thinking that when I sent the watch to Garmin support and the Garmin employees were trying outdoor activities was a good thing for my watch. My watch was working without restarts for 5 months after that. Can it be that changing the GPS location a lot during few days made that the problems with the maps got disabled? These are just suppositions that I want to write in case any Garmin employee reads this and can give ideas to them about which is the reason of this problem in some Fenix 7. I have also read in some forum posts that this problem was happening at some specific coordinate point, that would explain than in my last Sunday football match the restart happened 10 times as I was moving all the time around the same 100 x 40 meters zone.

I will keep informing about the result of my tests.

  • Just located this in the forum, 20.13, fixes Live crash" 

    20250125 - System - Beta 20.13

    Version updates - sub-components

    • System Update : 20.13 (was 19.41)
    • GPS : 13.00 (was 12.00)
    • CIQ : 5.1.0 (was 5.0.2) --> CIQ System 8
    • WiFi : 28.27 (was 28.19)
    • Sensor Hub : 33.13 (was 32.22)
    • BMX : 19.1.2 (was 18.1.4)
    • WHR : 19.01.02 (was 18.01.04)
    • FirstBeat ETE : 6.23.0.4 (was 6.22.0.3)
    • FirstBeat LHA : 2.9.0.4 (was 2.8.0.3)
    • NFC : 3.4.8 (was 3.4.4)
    • WLT : 3.2.8 (was 3.2.3)

    20.13 Beta / forums.garmin.com/.../beta-version-20-13---now-available-ota-over-the-air-for-all-models

    Fixed Potential LiveTrack Crash.

  • Joined the beta program and have now updated to 20.13. Had more crashes over the weekend prior to the update this evening. Rebooted and didn't notice it for almost 5 minutes on a run Sat, it did again as I was saving the activity after finishing. Luckily no data was lost. Can always tell if it's a reboot even if I don't see it because once I restart the activity from pause, the screen no longer scrolls as it would normally prior to the reboot.

  • 20.13 only addresses the issue caused by LiveTrack being enabled. I reported this bug when 20.12 was released - Beta 20.12 - Crash after stopping and saving running activity

    Some users here seem to be talking about random reboots, which is different.

  • With Beta 20.xx

    Map & Navigation issues

    • quarter of the screen is blank "white"
    • location cursor is place way below as before, then popup direction (TbT) sometimes override important part of the map for navigation
    • Navigation is awful, because map take more time than before to render

    Crash with 20.xx

    • always crash during activity
    • always crash during navigation

    Thanks for using my changelog info ;-)

  • Since a few weeks, I am also encountering reboots during run activities (Fenix7 Saphire Solar, v19.41). The watch comes back up and continues the activity. However, the Stryd Zones datafield does not reconnect, so this is seriously impacting my power-based training program.

    Initially, I thought it had something to do with the Stryd Datafield, but the reboots also happen with the datafield removed. Subsequently, I thought it occured when adding a course to the run.but I also had crashes on runs without navigation.I have had runs with multiple crashes during the activity.

    Suffice it to say that this is extremely frustrating, and gives me little confidence to use the watch during races.

  • I have the exact same issue. Very annoying…

  • Update January 29, 2025:

    Our engineers are anticipating a fix for the potential device crash/reboot while recording activities and/or navigating. This fix with be included with the next full Public software release. This is likely to be released mid to late February. In the mean time, this fix is included with the latest BETA software release 20.13. If you are experiencing this, and are wanting to, you can install the BETA software version here: 

    https://forums.garmin.com/beta-program/fenix-7-series/f/announcements/401874/beta-version-20-13---now-available-ota-over-the-air-for-all-models

  • I did a run on 20.13 and still experienced a reboot.

  • this doesn't look good at all! please keep working on it! I tried the 20.13 beta software a few days ago, but it also restarted while walking, running, or hiking, so you couldn't fix it! please fix it to be usable! I strongly recommend that you use the 16.22 stable software to fix the bug, because it has been working perfectly for me for 6 days, it doesn't restart while recording an activity! thanx

  • I did a run on 20.13 and still experienced a reboot.

    Thank you for your feedback. I have updated our engineers with this experience.