Related

So many issues with SW 23.20 makes me wonder why is Garmin not pulling it and offering a rollback?

4955375
1 month ago

I can't help but notice that there's a litany of complaints (literally three pages on this forum) from users who updated to 23.20. This looks like one of the buggiest software versions Garmin released for the 955, and that says a lot considering that all have been more or less bugged. Intriguingly, Garmin stopped testing other versions after releasing this almost a month ago. I'm on 22.24 and happy not not have other bags besides routing in maps, which I don't use anyway. I would expect Garmin to pull back the 23.20 and offer a rollback to 22.24, which had very few complaints. That it hasn't done it yet is puzzling, especially as it sold the 955 until very recently and many are under warranty (mine was bought in October). I expect development to end now that 970 is out, but at least it should end with a functional build like 22.24 instead of the failed 23.20. Especially as it will install the moment you hook your watch to a computer with Garmin Express if you're not paying attention.

  • 0 28 days ago

    has anyone checked with the passcode lock? My 955 has passcode enabled but when i remove it off my wrist it doesnt lock where as my fenix 8 locks automatically when i take it off my wrist any one else facing this?

  • 0 16 days ago in reply to 2148361

    I'll cross post this here for completeness:

    In the end, from my side, I arranged an exchange with them. Specifically, on my watch at least, they pointed to an actual hardware problem: "A manufacturing improvement has been made to solve this issue."

    In another thread (actually, I think this thread), someone mentioned that there were some generations of forerunner watches that had trouble with the flash memory controller, which was of lower quality and would start to fail after a while. If that was the case, then my problems could have been caused by the flash memory, but then triggered by the firmware update, since the firmware update presumably does a lot of flash writes, which could have pushed it over the edge. If I think back, I was having occational (2 or 3 times) hardware freezes already back in January / Feb, long before the 23.20 upgrade, which would also suggest more in the direction of a hardware failure (triggered by the flash writing of OS upgrade) rather than an actual OS bug. 

    In any case, I now have a refurb replacement for a week running 23.20 and have not had one crash yet. Also, my original watch suffered from a lot of pauses / glitches when playing spotify through my bluetooth headphones. I was never sure if it was a problem with my watch or my headphones, although I did not have such glitches with my headphones and my phones. Now, with my replacement watch, I have virtual no short glitches / pauses when playing music during and activity, which could also point to poor performance of the flash memory on my old watch. 

    If 24.07 fixes your problems (which someone had in a different thread), then probably your flash controller is fine and you do not need the unspecified "manufacturing improvement". Otherwise, you may consider further dialogue with Garmin support so see what they can do for you. 

  • 0 13 days ago in reply to 2148361

    I am the someone from the other thread whose FR255 got fixed for 3 days with 24.07... then it crashed again. Will be going for a replacement option. As you pointed out it might be a faulty memory controller...

    Do you by any chance remember where you read about this flash memory problem?