Mine fogs up terribly and that’s without ever taking it in the pool. Besides not being able to see it, it’s great!
Can’t imagine what sort of big company crappy service Im in for dealing with them!
I wonder what Garmin techsupport said.
Apparently this was a pervasive problem with versions prior to 2.7. Basically, the Multi-Sport mode drops the GPS elevation and distance when transitioning from swimming to another sport. Which seems like a big deal for a multi-sport device.
Version 2.7 was supposed to be the fix. Of course, I am running 2.7. They have seen a few cases where the bug is embedded in the device and version 2.7 does not correct the problem. The solution there to run a Master Reset of the device. They are sending me instructions for the Master Reset, and will await my feedback before closing the ticket.
Oh, and my race data is not recoverable. Other than that, it’s all good!
Scott
Can’t imagine what sort of big company crappy service Im in for dealing with them!
They were actually pretty good. Just spent 20 minutes on the phone with customer service, and didn’t have to wait more than a minute for a rep. But the rubber will meet the road when I see if the fix actually fixes the problem.
Interesting. I had something similar happen to me about a month ago. It was just during training, a swim then run, and I wanted to test out the multisport feature. I did include a “T1” just to see what would happen.
During the swim, my GPS seemed to go a bit goofy. It showed me doing a weird loop on the way out, then halfway back, it totally stopped tracking. It was a clear day, the water was calm, so I don’t know what the issue was. I did feel the watch vibrate a few times which may have been that it lost GPS signal.
After my insanely long 23 minute T1, I started running and noticed the only fields that were working was the timer and current pace. Distance and average pace were displaying a blank. I also got no data except for time on the run…and that supposedly I guess I swam to Africa as well.
I wasn’t so concerned about the swim data…as I didn’t get the watch to track my swim times. But I was concerned that the run portion was screwed up. In all my other runs with the watch (not in multisport mode), the watch has worked flawlessly.
I’ve been too lazy to retest it, but now that I’ve seen someone else with the problem, I’ll probably give it another try.
Swim -http://connect.garmin.com/activity/271431221
Run - http://connect.garmin.com/activity/271431229
I wonder what Garmin techsupport said.
Apparently this was a pervasive problem with versions prior to 2.7. Basically, the Multi-Sport mode drops the GPS elevation and distance when transitioning from swimming to another sport. Which seems like a big deal for a multi-sport device.
Version 2.7 was supposed to be the fix. Of course, I am running 2.7. They have seen a few cases where the bug is embedded in the device and version 2.7 does not correct the problem. The solution there to run a Master Reset of the device. They are sending me instructions for the Master Reset, and will await my feedback before closing the ticket.
Oh, and my race data is not recoverable. Other than that, it’s all good!
Scott
Thanks for the info. I’ll try the master reset. I went to 2.6 when I first got the watch, and later went to 2.7 before I had my issue.
Last spring, I had a run register a stray GPS point somewhere off the coast of Liberia as well. I’m sure, if you look at the raw data, you will find there is just a single stray point somewhere in the data. Remove the stray data point, and you should be fine…
Um, your first mistake was buying a Garmin 910. I have been so frustrated with this watch. Real time run pace is non-existent and it currently serves as the most expensive stop watch I have ever purchased. The 310 is back in service with no problems. I haven’t use the 910 in 6 mos. Until I hear that all the quirks have been worked out, it is gathering dust.
And, apparently, the quirks haven’t been worked out.
I have heard others with similar complains, but I have to say I use mine all the time - Runs, Bikes, Swims, and love it and have no such issues. There is certainly a short lag in the run pace, but I find it to be pretty accurate.
I would be happy to buy yours if you want to sell it. My wife would love one too.
message me if you want to sell it
Yeah, mine shows me at 26,000’, but all of the other functions work as advertised. It worked fine for several months and then the barometric altimeter just flaked out about 3 weeks ago. I filled out a questionnaire that Garmin sent me and gave them several files to examine last week. I haven’t heard back from them yet.
Um, your first mistake was buying a Garmin 910. I have been so frustrated with this watch. Real time run pace is non-existent and it currently serves as the most expensive stop watch I have ever purchased. The 310 is back in service with no problems. I haven’t use the 910 in 6 mos. Until I hear that all the quirks have been worked out, it is gathering dust.
And, apparently, the quirks haven’t been worked out.
Have you upgraded to 2.7? A lot of people hold off on upgrading till the magical firmware that gives 100% of people 100% functionality. Since it is just sitting around, why not?
My instant pace works amazingly. It is a short delay (obviously needs a few points at the new pace to register) before showing the new, seemingly accurate pace.
I have upgraded with every new firmware (I checked last night and have 2.7) but my real time run pace continues to jump all over the place. 45sec this way, 1 min that way, etc. The bike pace is pretty good but it’s useless as a running watch. Again, I haven’t used it in some time. I’ll give it another shot tomorrow but I’m not too optimistic. 
could you post links to all 3 files? It might help.
Swim: http://connect.garmin.com/activity/280580473
Bike: http://connect.garmin.com/activity/280580474
Run: http://connect.garmin.com/activity/280580479
Note the GPS track on the swim (which sucked…I was headed for Japan!), then nothing.
Scott
PS - I just noticed the bike track starts in North America and ends in Africa.
Looking at the bike TCX file, it does have a GPS lock, but it blinks in and out throughout the ride.
The run TCX file has no GPS lock, but a ‘Column R’ called: ‘ns2:Speed’. It is the only column besides ‘time’ that changes, so it isn’t a calculation, but a direct output from the watch. Wherever that data comes from, it is the reason you were able to get a speed graph.
Also, columns Q-T are blank if you run with a cadence sensor and good GPS.
Columns Q-T are unchanging if you turn the GPS off to run indoors without cadence (not sure if GPS-off, /w cadence). Otherwise, I was hoping that the watch’s built in acceleration was guessing speed.
I hope the master reset helps!
I have upgraded with every new firmware (I checked last night and have 2.7) but my real time run pace continues to jump all over the place. 45sec this way, 1 min that way, etc. The bike pace is pretty good but it’s useless as a running watch. Again, I haven’t used it in some time. I’ll give it another shot tomorrow but I’m not too optimistic.
That sucks. It was one of the big fixes in 2.7. Are you using ‘every second’ or ‘smart recording’? I would guess that if it is ‘smart recording’ and you are on a straight line, the GPS refresh rate would drop. That would obviously be very bad for fast refreshing instant pace.
I use ‘every second’ and it works pretty well.
Thanks. I do use “smart recording”. I’ll try it with “every second” and cross my fingers.
OK, I’m hopeful again, kinda. 
Thanks. I do use “smart recording”. I’ll try it with “every second” and cross my fingers.
OK, I’m hopeful again, kinda.
Good luck! In any case, write back on here with the outcome.
Ughh… hopefully these issues get worked out. It seems like a great piece of gear!
There’s a thread about this over on the Garmin Forums with somebody else having similar issues, even after having units replaced - I think he’s in Australia. Clearly you are not the only one with the problem. We don’t experience this so you might be best placed to start a conversation with Garmin as soon as possible.
Check out the Garmin Forums too
I had exactly the same problem this weekend at the Mooloolaba Tri. Swim recorded well but the bike and run started me in Africa and no data was recorded. Frustrating.
This is a copy of my post from another thread here http://forum.slowtwitch.com/gforum.cgi?post=4482116 that describes the same 910xt issue.
This appears to be an issue that effects certain people’s 910xt after it has been updated to 2.7 firmware. The bug is being discussed the Garmin forums. I lost my bike and run data at San Juan 70.3
The main symptom appears when using the unit in Multi-Sport mode that has an open water swim, the Latitude and Longitude of the segments after the swim (T1, Bike, T2 and Run) will be 0,0 (which happens to be off the west coast of Africa in the Gulf of Guinea). You will not get mile spits or other distance based reminders while it’s happening.
I suspect It has not effected a lot of people yet as the 2.7 firmware was released on November 28th, which is off-season for most of the Northern Hemisphere. It would not surprise me at all if good handfull of people come back from Oceanside 70.3 this weekend and post here about this problem.
Apparently, Garmin is not saying there’s a problem and are not offering a “downgrade to 2.6”. I have come up with a (non-Garmin approved) solution to send the 2.6 firmware to the 910xt if you are experiencing this problem. I’ve got a walkthrough set up on this page: https://dl.dropbox.com/.../910xt-firmware.html.
The Garmin forum thread about the issue is here (for continuity sake, I’m JUMPSERVE in the Garmin forums):
https://forums.garmin.com/…-in-multisport-mode/
Hey I recognize that location. Latitude 0. Longitude 0. Where Greenwich meridian and equator cross one another.
I run whatever my 910 came with. I think it’s 2.4 Too afraid to flash new firmware (and this is why!). My 910 worked just fine out of the box and still works just fine. Elevation is okay-ish. Not perfect but it works okay and I have no crazy inaccurate readings. Multisport works perfectly. Instantaneous pace is reading high but I don’t care. I run by HR and then check the average pace afterward.