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

1030 turns off during ride

Former Member
Former Member over 7 years ago
Hello

I have had my 1030 for 3 months now, and manily used for indoor training, but now I have startet on outdoor training.
I have never had any problems with the 1030 before, but 2 days in a row, I have experienced that it suddently shuts down during a ride, I am not sure, but it could be in relation to some Strava segments starting.
I can start it again, and when it starts it asks if I want to save my ride, if I cancel, I can continue the ride in the same file.

Does anybody have suggestions on what to do?
  • 0 over 7 years ago
    There are likely improvements in the most recent public beta that will help resolve some of the issues reported here. For those of you who are willing to please see the post here for information on updating to 3.97.
  • 0 over 7 years ago
    I am on the beta 3.97 but since I've only seen the issue once in two months not sure I am a good test subject for the crashing issue, will be trying it out tonight and hopefully it's fixed my new set of issues of having to manually pair all of my sensors before a ride.
  • 0 over 7 years ago
    I'm not even sure where to begin. I experienced three units in total, the first one crashed so often that I returned it because the err_logs were so varied, and occurred with seemingly no pattern, I was sure it's defective, maybe not.

    I now have two units which I would like to keep, but both also crash randomly due to bluetooth related and other issues. My personal unit only has bluetooth related crashes and a total of 3 err_logs. The unit of a relative has a total of four crashes, with three bluetooth related like mine and one seemingly unrelated when bluetooth pairing was turned off.

    I'm attaching the crash logs here and hope that Garmin uses these to help them investigate the issues, as I'm not the only one and it seems unlikely that I got 3 lemons in a row.
  • 0 over 7 years ago
    Same issue as many others even after the 3.97 update. Will send logs if you need even more of them.
  • 0 over 7 years ago
    Logs definitely help. Thank you for continuing to report feedback.
  • 0 over 7 years ago
    Updated just fine this time. Running 3.97.
  • 0 over 7 years ago
    Updated to 3.97 Beta and continues the same behavior. coming to a Strava segment in which other times no problem, today the Edge 1030 was turned off. With bluetooth off and Gps on and glonass off. It is incredible that we have to suffer these problems in a continuous manner and with no solution in sight. I leave the error log:

    [
    {
    "unit_id":"3960841888",
    "product_name":"Edge 1030",
    "software_part_number":"006-B2713-00",
    "ms_since_epoch":1524750802000,
    "system_version":"3.97",
    "build_type":"PRODUCTION",
    "backtrace":"
    Function Address: 0x0038C090
    Call Address at Function: 0x0038C170

    Function Address: 0x001DE2FE
    Call Address at Function: 0x001DE35E

    Function Address: 0x001D7424
    Call Address at Function: 0x001D749E

    Function Address: 0x00580EDC
    Call Address at Function: 0x0058102E

    Function Address: 0x00502364
    Call Address at Function: 0x00502396

    Function Address: 0x006B49E8
    Call Address at Function: 0x006B4A44

    Function Address: 0x0033596C
    Call Address at Function: 0x003359A6

    ",
    "error_cause":"RTL Trap",
    "proprietary_info":{
    "Commit ID":"e3284e34031d393be0f590acd07b05ec026140f7",
    "Time":"2018-4-26 15:53:22",
    "Ram Dump":"0",
    "ESht PC":"0x00103409",
    "ESht SP":"0x024555A8",
    "RTL Error Number":"6E5D8024",
    "Error Message":"Data abort, system r0-15 + cpsr",
    "Task Name":"CDP main",
    "Saved SP":"01DD1BE8",
    "Saved LR":"00404155",
    "Saved PC":"0038C170",
    "R[0]":"6E5D8024",
    "R[1]":"FB2001E0",
    "R[2]":"00001000",
    "R[3]":"01DD1BF4",
    "R[4]":"00481965",
    "R[5]":"007A0061",
    "R[6]":"00000000",
    "R[7]":"00000008",
    "R[8]":"0048A0D1",
    "R[9]":"00000000",
    "R[10]":"00000000",
    "R[11]":"00000000",
    "R[12]":"00000000",
    "R[13]":"00000000",
    "R[14]":"01DD1BE8",
    "R[15]":"00404155",
    "cpsr":"0038C170"
    }

    }
    ]
  • Former Member
    0 Former Member over 7 years ago
    Another experiencing the same thing here. I even went through and unstarred all of the segments on Strava, given Garmin are seemingly unable to resolve this widespread issue. However segments remain on the device - probably because the thing simply refuses to connect to my phone.
  • 0 over 7 years ago
    DavidKroter Try the following. With the Edge connected to the PC move all the files in the Garmin\Segment folder to the Garmin\NewFiles folder. This will force each segment to be reload. It sounds like the segments cached in memory may have gotten corrupted.