Strange "Crash" last ride (Display freeze)

Hello,

encountered a strange sort-of-crash last ride:

- after around 30km the display was frozen. Buttons did not do anything, looked like a complete crash

- after another 10km im managed to turn it off (i thought) using long presses on power and lap button (it was hard cause I was wearing long gloves and was riding in a group, so did not want to pause)

- then no restart was possible with hitting power button, the display stayed black

- at home i did fiddle around with power + lap button long press and suddenly the unit turned on again

- strange result: it showed the complete ride including all sensor data and I could save it. So the unit never really crashed.

Anyone else experienced this?

  • In my case, this issue occurred when I updated the firmware to 11.24.

    When this occurs, the values ​​of various sensors on the training screen are not updated, and even though it is stopped, the speed remains the same as when the issue occurred.
    Depending on the situation, the radar warning of VARIA515 will sound, but the screen will remain frozen.

    Forced restart as a measure to save the activity. Is it because a forced restart will corrupt the file? I cannot upload it to Garmin Connect.

    At first, I suspected that the firmware update was affecting it, but I was convinced that it was the cold (temperature) from the forum.
    The temperature has been dropping since around this time in the northern hemisphere where I live. After that, I went for a few rides to check the problem, but this issue always occurs because of the cold days.
    I think Garmin, which has support centers all over the world, can easily reproduce and investigate it.
    It has been two months since I became aware of the issue.

    I am currently using the 1030 (not the Plus).
    I was considering discarding it, but it is aging, so I am worried about when the 1030 will no longer be usable.

     

  • What were the temperatures near Denver and in Italy?

  • In Italy 50-60 degrees F. I have been riding recently in Denver in temps in the 30s-40s F with no issue. I have not had this happen at all recently.

  • Just happened again at a nightride. Right after start (around 2°C).  I see the 1050 as unuseable as bikecomputer when it is not reliable in all weather conditions.

    As happy as I was with my previous 830  which was totaly stable from the beginning and I havent had more then 1 or 2 crashes over years as annoyed I am with the 1050 now.
    I accepted (even defended) some bugs in the beginnig, assuming that they will be solved soon and that the 1050 will be as rock solid as previous models. Some more or less minor bugs got solved with firmware updates since launch, but the major problems consist over half a year later. And the temperature issues are a clear sign, that the hardware has problems. For a 700€ top of the line model that is simply not aceptable. I will try to get my money back, i feel really cheated by Garmin :-(.

  • Everyone, in my case, I found a workaround.

    I disabled battery saver.

    I saw a related post about turning off auto sleep, so I tried it. Unfortunately, I couldn't avoid it and the screen froze.

    When I got home and disabled battery saver, I went out, and the issue didn't occur and the screen movement returned to the way it was before firmware 11.24.

    My activities were also automatically uploaded to Garmin Connect via my home wifi and reflected on Strava.

    I was able to avoid the freeze, but unfortunately the battery saver power saving feature will no longer be available.

  • I had the display freeze with and without the battery saver mode on. So I dont see it connected to this. Also on my device it does not happen in every ride, so hard to track it down...

  • Today, after changing the settings, I drove in a cold environment for about 2 hours.

    I'll check again tomorrow to see if there are any problems.

  • Just happened again on 12.16. Might really be connected to battery save mode (as I was testing it again). I am sure my first crash happend in normal mode...but lately it really happens at least always when in battery save mode....

    please fix!

  • I also updated to 12.16, so I thought I would try the battery saver, but I'll give up because it seems pointless.

    I've driven 140km with the battery saver disabled on firmware 11.24, and there have been no freezes. As for the sleep function, the manual and automatic sleep functions work correctly, and the device seems to wake up from sleep normally. There are no freeze problems.

    I posted in the past that it is strange that when you start up the 1050 with battery saver set up on the forum, you are asked whether you want to disable it at startup, and it becomes disabled unless you respond. However, Garmin support and forum users didn't respond either.

    (Garmin support aside, I was impressed by how generous the users were.)


    Experiencing this problem makes me wonder if Garmin is putting some of the blame on users for any problems they may experience when using it, since the battery saver is incomplete.Please give me your answer.

    If you say otherwise, please resolve the freeze (I think battery saver is the culprit), remove the disable prompt on startup, and release it in the next version.

    I saw a post from someone who doesn't have a 1050 saying that using battery saver is wrong. Is Garmin support of the same opinion? Please answer this as well.

     

  • Still not fixed on v12.17 :-(

    This time I testded it from home. just loaded a route, put it in battery save mode and started recording at home sitting on my desk. Crashed as "always". At least its safe to say, that it is not a temperature issue....