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

Track recording currupts... again (16.17)

UltraKapitan
over 1 year ago

The watch started to record my runnings incorrect again after the update to 16.17. The watch again writes the distance incorrectly for the first 1-2 km. Again the watch is broken and again it is impossible to run normally. What a nonsense! I was so happy with 15.19. This watch is a disappointment. I have never had so many problems with a Garmin before. 

Normal with 15.19 - https://connect.garmin.com/modern/activity/11819738061

Incorrect with 16.17 - https://connect.garmin.com/modern/activity/12793016816

https://connect.garmin.com/modern/activity/12531127139

If you can't make a normal firmware, then give the option to rollback to a working firmware. Stop joking of users!

  • 0 over 1 year ago in reply to parentoft

    Yes, all of them off.

  • 0 over 1 year ago in reply to Volkan

    I will do it on suturday morning. But, actually I use this settings every time. Will check it once agin and turn it on/off. Will keep you informed.

  • 0 over 1 year ago in reply to UltraKapitan

    Unfortunately Gps fail. I will share to results with screen shots. 

  • 0 over 1 year ago in reply to Volkan

     

    Route distance: 7Km
    GPS Comparison: 7 km

    Forerunner 245: 7.0 Km
    Forerunner 955: 7.45 Km

    There is a bug in the 16.17 software. Just like we have mentioned before, just like we have given examples in this way.

  • 0 over 1 year ago in reply to Volkan
    Volkan said:
    There is a bug in the 16.17 software

    OR there is a bug in your devices GPS chip. OR some special circumstances, that do not effect others (like - most) users.

    I can only repeat: I've had plenty activities with FR955 and 16.17 and I review my tracks and they are fine! Nothing wrong here, calculation of distance is consistent and drawing of tracks also. Nothing better or worse then with firmware before.

    BTW, I use "Smart recording" and "Autoselect" aka "SatIQ" for all my activities. Nothing wrong with that. My often used 10,3 km track (according to Google Maps) is always measured as 10,31, 10,32 oder 10,33 km, with 10,32 in 80% at least. Consistent since I have the FR955, with different firmwares.

  • 0 over 1 year ago in reply to Grumpy from dawn till dusk

    If it is not software related, how is the same route correct in 15.19?

  • 0 over 1 year ago in reply to Volkan

    Thats right. On 16.17 FW it accidently became broken.

    By the way - many people have "special" bugs on their wathces. Nobody tel them that their whatches are bugged.

  • 0 over 1 year ago in reply to Volkan

    Hey Volkan, I did not say "it has NOTHING to do with the firmware".
    I said, maybe it is a combination of firmware and hardware bug, or external factor (like GPS jam/spoofing), or maybe a specific revision of the hardware, or ... Who knows?
    Probably this would need a detailed analysis with the developers.

    I have no doubt that you and UltraKapitan experience this problem and I understand it is messing up your stats - you have every right to be unhappy about it and ask for a fix.

    It is just, that UltraKapitan wrote something like "Garmin, you can't even make a firmware, that records tracks right". But for a lot of users, including me, that is not true. I have absolutely no problems with 16.17 in terms of track recording correctness (and also had no problems with this aspect with previous firmwares).

  • 0 over 1 year ago

    Unfortunately there is no warranty that Garmin will solve this problem on next FW. It shown on previous FW as an example. So if I understand it correctly we should calm and wait, and hope, that everithing will fall into place with FW17.XX 

  • 0 over 1 year ago in reply to UltraKapitan
    UltraKapitan said:
    So if I understand it correctly we should calm and wait, and hope, that everithing will fall into place with FW17.XX

    Don't know.
    If I were you, I would contact support.garmin.com and complain about it and insist, this will be analyzed by the developers.
    You know, this is "just" a forum (not a real bugtracker and not the support) and sometimes Garmin officials react, but often they don't.