I think the first issue is that you raced somewhere in Africa, not San Francisco.

I kid.. but replied so that I can hear what happened so it doesn't happen to me.

Weird. I mean on the bike it could have been getting your speed from a rear wheel sensor (unless you don't have one), but that still wouldn't explain the run.

I'm gonna chalk this one up to a textbook case of the personal problems...

---

__________________________

I tweet!

I heard about elevation problems... but not this! I wonder what Garmin techsupport said.

What software version are you running?

I am still on 2.4, too afraid to upgrade. I heard some people were having issues with the multisport switching through, but can't recall the version etc.

could you post links to all 3 files? It might help.

cadence sensor on the bike and foot pod on your shoe will give speed/pace and distance. If you dont have those then who knows???

There is no cadence sensor, or it would show up under details.

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.

Nope....no cadence sensor on the bike and no foot pod on my shoe.

According to the Garmin track, I rode my bike there.

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!

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

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

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...

---

---

Coach TJ Tryon - Open Water Swim Clinics | Facebook | @tjtryon

Ask me about: T3 Multisport | Gu Energy | Torhans | Xterra Wetsuits (discount code) | Karbon Speed - discount code: COACHTJ | Uvex Helmets

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

---

-----

"i’m the one guy who says don’t force the stupid people to be quiet — i want to know who the morons are." -- mark cuban

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.

---

VDOT O2 Run Coaching
Team INFINIT Discount Code: RowanJones

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. :-)

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!

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. ;-)

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

---

Trust me I’m a doctor!
Well, I have a PhD :-)

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/

---

I'm just this guy ya know?

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.

Well, this gives me hope Garmin will fix the bug. Seems like a big problem for a Multi-sport watch to flake out in Multi-sport mode. Ironically, Garmin told me 2.7 was intended to fix the problem.

The master reset seems to have fixed the problem for now. But this remains one more to worry about on race day.

Scott

So, you're on 2.7, you did a master reset on your 910 and then did a "mock tri" with OWS, and did not get the Lat/Lon 0,0 issue?

---

I'm just this guy ya know?

Given my experience with Garmin and their updates... to me Firmware Update equals one thing --- NEW WATCH.

Had elevation issue on mine, got a replacement and have not replaced the firmware since. Still on 2.6 and will stay there as I believe a lot or Garmin issues are from the updates frying components

Perhaps not hardware frying, if you go back to a previous version and the feature is restored or bug is removed.

---

I'm just this guy ya know?

We tried doing that with my first one. Didn't help. Once the altimeter/barometer is shot, it is pretty much shot from what I have seen.

Maybe some of these are software issues in some of the later versions, but my issue last year happened immediately after the firmware and was non-recoverable (i.e. new watch)

If you set up auto-multisport as a run/bike/run, does it work correctly?

I do not doubt you, I just want to be sure. You successfully "downgraded" your firmware (i.e. 2.6 ->2.5) and the altimeter/barometer problem was still there? Or you did a "hard reset" or "Factory Reset" and the problem was still there (same firmware)?

---

I'm just this guy ya know?

Most people only experience the issue with OWS followed by another sport. I believe one person has reported it with a brick.

Do a "mock" run-through of your event (say 10 minutes of each sport) and see what happens.

---

I'm just this guy ya know?

I've read that until Garmin fixes their problem with the OWS, this^^^^^^is the work around if you are using 2.7. I do not have a 910 but if I did, I would down grade my firmwre to 2.6 as Blanco has pointed out and given instructions on how to do it.

Yup, I am going to do that. I have a bike-run race tomorrow and seeing this got me thinking I should test that out tonight.
btw, your work on reverting to old firmware is very cool. I'm sure lots of people really appreciate it.

Correct. Although my mock tri involved just a short walk from the beach. I will conduct a more thorough test soon and report back.

Scott

Not fixed. Now I'm frustrated. First I lose my Alcatraz data, now I have no elevation on a fantastic ride while on vacation in Maui. I used the multi-sport feature to record an OWS swim yesterday, then hit lap to simulate a bike / run on the walk back home. Seemed to be working. Then got this after my ride today:

Sorry to hear its not working. You can try to upload 2.6 via my instructions above. Good luck.

---

I'm just this guy ya know?

Thanks. I'm gonna try to get a new watch from Garmin first.

Any idea why this effects some watches on 2.7 and not others?

No, I thought it would be related to unit id/when manufactured , but from the IDs I've collected it doesn't appear that way. But I figure if I get enough IDs we can go to garmin saying it's a real problem effecting x amount of people.

Also, if you read the garmin forums thread, you'll see that some folks had their units replaced by garmin and the news ones shipped with 2.7 and exhibited the problem.

Unfortunately, I have a feeling we're going to hear more reports of this after California 70.3 as the season starts to ramp up.

---

I'm just this guy ya know?

Selfishly, I'm hoping to see others having the same problem. Just to get some momentum behind a permanent fix from Garmin.

I informed the tech who assisted me originally that my problems persist and have not received a response.

Lets face it, it comes down to one thing, and one thing only.

The 910XT is a fragile and funky watch of POOR quality.

It may work for some and run like a champ, but a large number have issues and seems to be GPS/barometer related and fairly consistent.

My issue did not develop until a firmware upgrade, but I am on my second watch, fingers crossed, and a year ago, it was still a big problem, i.e. when I was going through tech support it was a known issue and only took a few calls until they were setting me up with a replacement. Thankfully mine failed quickly, so was still under warranty.

The fact that a year later, people are still either getting GPS putting them all over the map, or going out and doing a 50 mile bike with 60,000 ft elevation gain... This is the hardware, and once the watch goes under some use, the GPS or the barometer are failing.

Whether it is a poor design, or was a bad batch of components over a short period still has not been determined, but seems to be the quality of Garmin is not what it used to be.

Garmin "quality" has, and always will be "go buy a new one in 1-2 years." The junk they make is designed to make you a customer in perpetuity. I haven't had a single Garmin product that actually lasted for any measurable period of time. The sad thing is most people on here are on their 5th, or even 6th model (sometimes multiple replacement versions), and they will still go out and buy the next one.

Based on what we all paid for the 910, you would think a firm in the sector would take the time to develop a solid product. That though of course follows the thought that Garmin might want to raise the tone of the chatter about its brand, spend some focused time on the 910, and get a more consistent user experience.

I've lost race data as well. Always watching the alternatives to see if someone makes a move...

Completely agree here, but so far I've been mostly at a loss. I've had several models of Garmin's devices from the 305 through the 910xt (including the Edge series) and am not sure that any of the devices were "solid" from a bug perspective. The 305 probably had the least software issues, although I bought it once it was in maturity. Still it had battery, charger, and piezo problems.

Since then I've had HW and SW problems on my 310xt (3-4 warranty exchanges), a charging issue with my 610, dead pixels and SW growing pains on my Edge 800...

The 910xt, for me, has been mixed, with the issues seemingly software related thus far. The barometer has improved with the newer software, at least to not be ridiculous in my flat portion of the country. Courses initially crashed the device, this is fixed, but the overall course function is still poor. My ANT+ reception to my PowerTap suffers when worn on my right wrist... probably the biggest issue I have now and it is likely a hardware problem.

Either way I am also still interested in seeing other, improved competition. It does seem like the only way we can hope for improved products in the market.

That's an epic ride, but I'm impressed with your ability to ride straight in the water!

I'm very content with my 4 yr old 305 that keeps on truckin' - paired with a 500 on the bike, it gets the job done.

---

Blog: http://262toboylstonstreet.blogspot.com/
https://twitter.com/NateThomasTri
Coaching: https://bybtricoaching.com/ - accepting athletes for 2023

Just had this same thing happen to me this weekend on my first race of the year. I wish I would've seen this thread beforehand, I wouldn't have used the multisport mode. Has anyone tried just using the OWS mode then switching it to bike mode and having problems with it still?

Similar issues and now I've had to wipe all data twice. My recent half Mary PR is lost to eternity . . . But now it's working again.

---

_____________________________________
What are you people, on dope?

—Mr. Hand

Sorry guys. The good news is that Garmin replaced my unit, and the replacement is working. Garmin is aware of the issue, and those with problems should contact Garmin. They really need to fix this glitch.

Scott

Is the new unit working on 2.7 ? I've read that some folks have gotten replacements on 2.7 that had the problem.

---

I'm just this guy ya know?

Yep. Just one test so far. Pool swim in Multi sport mode (set to open water), followed by locker room "transition" and a "bike" and "run" on the drive to the office. All readings functioned.

I plan to continue testing up through my next race, ideally with some true OWS. Just need warm(er) water. I will update this thread if it fails a test.

Scott

Most of the people have issues with OWS multisport. I'm going to try that out this weekend.

Yes, I was "open water multi sport", but in a pool.

I agree a true OWS would be a better test and will get out there soon.

Good product, but frustrating to need these measures.

Scott

I tried the master reset about a month ago and it didn't cure the OWS multisport problem for me. I'm running 2.7 (again). I also had problems with just OWS (not in multisport) where the watch would beep/vibrate after 15-30 minutes because it lost gps signal. This was in the middle of swimming...not while treading water or while the watch was submerged for a significant period of time.

Then I realized I don't care about OWS gps data, so I tried using the multisport version starting with a pool swim. I figured there is no way for the 910 to drop gps and elevation data if it never was looking for it to begin with. Ended up working fine. I got my swim time, then the GPS transitioned to the bike and run with gps data.

After my A race HIM, I may look into actually fixing the problem or getting the unit replaced, but as for now, it works just fine for what I need it to do.

Just chiming in.
First tri of the season was last weekend.

Running 2.7 on my 910 and had no issues with multi sport and open water swim

Garmin has posted an official response to the issue: http://forums.garmin.com/...ps-Tracking-Location

---

I'm just this guy ya know?

Ha! You were right all along! YTM.

Scott

The worst part was Garmin telling everyone with the problem that it is not possible to downgrade a unit back to 2.6. Now all of the sudden, they're offering it as a solution.

---

I'm just this guy ya know?

Mine worked fine for an Oly race this weekend except for power data from my Stages PM. I have had the problem that if I am in aero and the watch is on top of my arm (palm down on the extension) it loses connection to the PM. I am blaming that on the Stages at this point. I can't believe that the little bit of aluminum in the handle bars would disrupt the ANT+ signal but it seems to.

Now post race it is all over the place with distance. I start out on a run and it starts racking up distance faster than I am actually going. I suppose from an ego perspective that is fine but not from a useful information perspective.

All this technology is harshing my exercise mellow!

Well, I raced this weekend and experienced failure #2. The puts me at 0-2 on racing with the Garmin. Apparently the replacement watch was not a solution.

I read your post before the race, but was reluctant to make changes right before race day. And the watch had been working in tests of Multisport mode. Lesson learned.

Today I followed your instructions and "upgraded" to 2.6. Quite simple really, and I suck at computers. Now I will sit back and wait to see how long Garmin takes to release their permanent fix.

Thanks for your help, and keep up the good work.

Scott

My 3 year old 305 has about had it and its threads like these every 2 weeks here which lead me to deciding to get the 310xt instead of the 901.

If people want Garmin to fix these issues, there is one simple answer... Blow up their facebook page with comments. Send emails to their social support and executives. It is obvious that the management team that is working on the software side doesn't care, but the more public and loud people are about this, the faster things get fixed...

Hi Everyone.............E-MAIL GARMIN................ social.support@garmin.com.

Ask for.....and they will send you the version 2.6 files and instructions to roll back the system......as system 2.7 IS FAULTY

Make a note of all settings/data fields first...as this roll back will wipe all back to factory standard. It took me around 20 mins to put on the 2.6 system........and 15 minutes to re- configure all settings.

Well worth it....until they fix the problem............now i have my old working watch back.

Cheers....

Rudy

I went with the 910XT - and down graded to 2.6 before my first tri with it and it worked fine.
will use it again in race this weekend - other than that have used it for each sport no problems

Garmin has posted a firmware update to v2.8 that they claim fixes the bug :

Today Garmin released a software update to correct the issue described below. Please click here in order to view instructions on how to install this latest software to your device. We appreciate your patience and apologize for the inconvenience that this issue has caused.

---

I'm just this guy ya know?