UPDATE: 220 (620, too?) users, time to update (Wtf, Garmin)

[water*drop]

On my sucky run this morning, my 220 acted up like crazy. First, it would only give me distance OR pace, but not both. The distances were royally effed up, too, because even though it was a sucky run, I'm pretty sure I wasn't running a 40:XX pace, and on the rate occasions that it gave me pace info, it seemed right (9:XX, though it wasn't showing any distance change at all during those times). Then it started giving me heart rate data, which is interesting since I wasn't wearing a HRM.

The battery is fully charged, and I let it go into power save and re-locate satellites twice during the run with no improvements.

I'm going to go out for a couple miles again this afternoon to see if it randomly starts working. If not, Garmin is getting a phone call tomorrow. Ugh.

Update: After looking at the Garmin forums, it seems like this is a recent common problem with the 220s (and 620s?). There are new updates - at least for the 220s - that may or may not fix it. It seems that the updates may or may not be showing up in Garmin Connect, but WebUpdater found them for me. The first on that came up was the new firmware update to 2.60. You should also be on GPS version 3.00...and apparently even though I'd been updating the firmware regularly, I was still on GPS 0.00 (go to Menu, Settings, System, About on your Garmin to see what versions you have). The GPS update shows up AFTER the 2.60 update when you use WebUpdater. You'll do the update to 2.60, and then there'll be a list of language updates that you can do. The GPS update is allllllll the way at the bottom of the list, and that's probably how I've missed it a bunch of times since I always assumed that was just the list of languages and didn't care about those updates.

It's not really clear to me whether or not doing the update fixes the problem, but I wanted to at least let people know that there are updates available...I'm seriously unhappy with all of the Garmin issues lately.