Firmware 13.13: 6 crashes during a 35km ride...

KUKUK
9 days ago

When I got the offer to update my Edge 1050 to firmware 13.13 I made the mistake to update Disappointed

During a 35km ride this evening I had 8 freezes: after about 5 km, 10 km,  20 km, 30km, 34 km, 34.2 km, when saving at 34.5 km and a minute later when I wanted to switch it off.

The device is with this firmware completly unuseable. The freeze happend on all screens and in all modes. Never had that before.

  • 0 2 days ago in reply to NicoKossen
    NicoKossen said:
    They replied, that they are working on a software solution and that disabling popularity routing would solve the problem for now.

    That explanation they gave you is total crap. I have, and always have had, popularity routing disabled on the two profiles I use, and with 13.13 I get lockups every few kilometres on both profiles.

  • 0 2 days ago in reply to woutlepelaar

    When I phoned with garmin support they told me that it would be a problem with former gpx-tracks, which i generated with basecamp. I transformed all my tracks to gpx and sent them via Garmin connect to my Edge. In combination with garmin maps this seems to work well. So the freezing can be caused, in my opinion, also by a „former track“.

    Kind regards 

    Stefan

  • 0 2 days ago in reply to SHAUSLADEN
    SHAUSLADEN said:
    So the freezing can be caused, in my opinion, also by a „former track“.

    Have you tried to return to OpenMTBMaps? Do they work after your gpx action?

  • 0 2 days ago in reply to mcinner1

    Yes I tried. My Edge does't work with OpenMTBMaps; only the garmin maps are working.

  • 0 2 days ago in reply to SHAUSLADEN

    I‘m still on beta version 13.12 which works without OpenMTBMaps problems. No freezes.
    I hope I can suppress the update to 13.13 until there is a solution…

  • 0 2 days ago

    I had my last freeze with firmware 12.14 in March and my Garmin 1050 never freezed again - until today with 13.13. I have used firmware from 12.16 to 13.12 with no problems (regarding freeze and reboot issues) and installed 13.13, when it was avaiable some days ago, still with no problem. Until I updated my maps to TopoActive, since the CycleMap apparently is outphased. So, to me, freezing started, after the map upgrade with maps Garmin forced us to use. To me this is quite ridiculuous. Are we now at the point of pre 12.16 again, when permanent freezes and crashes prevailed?

    Garmin had more than nine months time, to make its most premium cycling product ever (which I enjoy to use when it works) stable, but it still fails. Now apparently by switching to a new standard map product.

    On my 1050, only the TopoActive Europe (18.0 GB) and the CycleMap Europe (551 MB) are installed plus a Lidar map with elevation contour lines (which never caused problems).

  • 0 1 day ago

    I've had two instances where the Garmin 1050 ate a ride (with firmware 13.13), both fortunately very short rides, and then yesterday, about halfway into a 31 mile ride, it first stopped reading sensors (power went first) and then the screen froze, couldn't do anything. Here's where it gets weird. I pressed the on/off button and lap button together for about 10 seconds, after which it rebooted and... it continued as if nothing had happened, and accurately recorded the entire ride. 

    Sensor disconnects in general have been an issue with 13.13.

  • 0 13 hours ago in reply to mikejacoubowsky

    Is there a list with the standard cards that are on the Garmin when you buy it new?

    Last ride for 30 km i did not have any problems. I checked out all the cards and no navigation.

    Before i had hickups after each 10 km.

    Now i wil activate the cards again and remove some gpx tracks iff the are on my device.

  • 0 10 hours ago

    Today, on a 7.7 km ride three freezes / crashes.

    I bought my Garmin 1050 on Dec. 27th 2024 with firmware 11.19 installed. Reboots and freezes stopped around two (!!!) months later, with firmware 12.16, which in my opinion is too long to fix such severe bugs. After 12.16 my 1050 ran stable. I joined the beta program, because there were some annoying bugs still open, but everything worked fine until beta 13.12.

    Then came production release firmware 13.13 and a little later the elimination of the cyclemaps, which got replaced by topoactive maps. And then erverything went down the drain to a state even worse than before 12.16.

    I appreciate that around one week after the first problem reports occured in the forum, Garmin is proactively seeking for help in a thread on this forum.

    forums.garmin.com/.../crashes-on-13-13---specific-info-request

    However, some remarks are necessary:

    - the beta process doesn't seem to work. How can it happen that everything is fine (at least on my 1050) with 13.12 and only one increment later, with the official release 13.13, everything is worse than ever before? How can it happen that the change from cyclemap to topoactive wasn't tested through the beta phase before release? How is it possible, that with a minor increment such severe bugs were released for production? Something is very wrong with the beta program and test management.

    - Apparently, it is at least difficult for Garmin to ensure stable production releases for their 1050 device even 9 months after the 1050 got on the market. I don't understand, that Garmin with knowledge, how unreliable it is to provide a stable production release, that there is still no standard offer to roll back for the last stable release. Do they really expect that customers will be patient again for months, to wait for the next stable firmware, with the outlook anything like the current situation might happen again any time?

    - Garmin needs to seriously analyse its product and software development process. The edge devices got plenty of new features, like bell, group ride, social media etc., which I would never use. The main usage is to navigate a course and provide orientation on a map, plus recording activities. These things are the core, for which the devices are bought. Garmin should focus product development on these things and quality assurance.

    - The current crashy 13.13 release, which makes the Edge 1050 unusable as a reliable training device, has eroded the trust in the product and Garmin significantly. The Edge did *not* grow in maturity after nine months since market release, the opposite became true.

    Generally, I appreciate that the Edge 1050 finally got a readable display, which my 1040 does not have in too many lighting conditions. I like the device when it works. However, when this mannor of providing unstable production releases pertains, I am afraid sooner or later I have to look for other alternatives, unfortunately. Even if the alternatives have less features and less operating times (like Karoo 3).

  • 0 10 hours ago in reply to SHAUSLADEN

    Yes, that could be. But a former track is not the real problem. Most of us did not change their device configuration since 12.16 or 13.12 beta, perhaps with the exeption that now we have topoactive on the device instead of cyclemap. So if 12.16 or 13.12 did not cause problems even with your former gpx-tracks, the problems must be in the changes made between 12.16 / 13.12 to 13.13. 13.13 was never published in the beta program, so it was never tested by the community participating in the beta program.

    Perhaps some changes where introduced by the anticipated change of the standard map type or the new map itself. Only Garmin knows (hopefully).