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

Bad Stryd Experience

Really bad outing with Stryd today.

I have used the Stryd exclusively for pace/distance for a handful of runs, and been very impressed until today.

My settings for the footpod are pace and distance "always" and auto calibration "off"

Right off the bat, my pace, power, and distance were all way too low, such that my watch clocked 0.89 miles at the one mile mark. At this point, I turned the footpod pace and distance settings to "off", and ran the rest of my run using GPS.

You could see on the pace track that there were no dropouts, but the pace track was VERY erratic for that first mile, then smoothed out considerably once I switched over to GPS.

Of note this was the first time I started a run using a scheduled workout, but I'm not sure why that would be a factor.

Disappointed, because what I'm really looking for is repeatability and reliability.

0 tx911 over 8 years ago

Here's the Pace track from GC:

0 Flackc over 8 years ago

You might try posting on the Stryd Support site. They are good at responding.

0 timgrose over 8 years ago

Largely why I use GPS for distance and pace except on a treadmill. Unless if you do all your runs in city centres or dense forests then current pace from GPS I find good enough and distance from GPS rarely out by any significant amount.

Most of the time, in say general easy/steady runs, my exact current pace is of little consequence to me anyway but I might glance at it and also lap pace and HR to see where am at.

In workouts away from the track, I would tend to look at lap pace perhaps in conjunction with current pace. Then again I have been running now well over 30 years so a lot of the time I can "guess" my pace without even looking as if you do something often enough it becomes ingrained.

But yes ask Stryd about Stryd issues like this. I can't say have seen similar and even if you don't take pace from it on a Garmin you can still download from the Stryd directly into their Power Center to see what it is doing.

0 tx911 over 8 years ago

Largely why I use GPS for distance and pace except on a treadmill. Unless if you do all your runs in city centres or dense forests then current pace from GPS I find good enough and distance from GPS rarely out by any significant amount.

I understand this mentality, but really what happened today with my footpod shouldn't happen.

Sometimes I wonder if the 935 doesn't have a little touch of the connectivity issues that plague the Fenix 5, especially with dual Ant+/BTLE devices.

Hopefully some updates in the pipeline will address it.

0 timgrose over 8 years ago

Agreed, it should not but a little ironic that you don't like distance/pace from a such an expensive watch as this that you turn to an expensive 3rd party device and then that does not appear to do the job either.

You don't appear to have any drop outs there so don't think that is the issue.

Suggest if you use the Stryd app to download the stored data into Power Center then you may be able to see if the pod itself recorded this data or it was somehow "mangled" by the 935.

0 Dr Phil over 8 years ago

@tx911 Of course these things shouldn't happen but, as with most technology, they do on occasion. I would not be jumping to conclusions too hastily unless you have a history of bad experiences. If this is the first time, then you need to look at what you did and see if it happens again by repeating the same steps. As they say, one swallow doesn't make a summer.

If it happens again, then you might consider there to be a problem. In which case the the first thing to do is to start from the very beginning. Re-initialise everything to factory values. Read the manuals. Set up the devices and try again. These devices are complex to operate and often do not behave as intuitively as we would like. Besides, what might be intuitive to one person might be very difficult to comprehend by another.

0 Former Member over 8 years ago

Hopefully just a one time occurrence. I'm also planning to upgrade from FR235, which has been nearly drop out free so far (knock on wood).

I wonder why Garmin don't do any kind of error correction on foot pod data? It should be fairly easy to fill in the blanks with aid from watch accelerometer for example... Probably wouldn't help much with bigger errors like that, but currently nothing is done for occasional odd dropouts either...

0 timgrose over 8 years ago

> I wonder why Garmin don't do any kind of error correction on foot pod data?
A while back they wanted to remove most support for them on running watches as were focusing on the GPS experience. Certain amount of change of mind there but not gone full circle and so foot pods are not suddenly the "answer". It would be like going back 20 years...

Generally with things like HR then the firmware in the HRM "module" does the "error correction" and the watches just collect the data - good or bad. It's largely why it is fruitless to "blame" your watch when you see dodgy HR strap data.

Presume it is similar here. There is also the "fact" that a Stryd is not of course a Garmin product and there is no native support for it other than treating it as a standard foot pod sensor just like a Garmin one.

0 rtperna over 8 years ago

Hopefully just a one time occurrence. I'm also planning to upgrade from FR235, which has been nearly drop out free so far (knock on wood).

I wonder why Garmin don't do any kind of error correction on foot pod data? It should be fairly easy to fill in the blanks with aid from watch accelerometer for example... Probably wouldn't help much with bigger errors like that, but currently nothing is done for occasional odd dropouts either...

I can assure you that as somebody who upgraded from the 235, the 935 is 100% on par with it. My running partner still uses a 235, and our distances/paces are largely identical. Well, WELL within the margin of error. Our paces this morning were the same, down to the last second. Granted this is the first time this has happened in the 2 1/2 weeks I've owned the watch, but if you think about just how precise we have to be for that to happen even if we were using identical watches...

The GPS maps are also the same between us. The 935 is a surprisingly rock solid watch considering how new of a Garmin device it is. That 235, for as great of a watch as it is, had horrendous teething problems (as I'm sure you remember if you've had it for a while). Yeah, the 935 has a couple bugs, but I've found nothing so far that materially impacts the core functions of the watch. I can recommend it without hesitation. Now whether or not it's worth the cash to upgrade from a 235, that's your call.. :D

0 Former Member over 8 years ago

> I wonder why Garmin don't do any kind of error correction on foot pod data?
A while back they wanted to remove most support for them on running watches as were focusing on the GPS experience. Certain amount of change of mind there but not gone full circle and so foot pods are not suddenly the "answer". It would be like going back 20 years...

Generally with things like HR then the firmware in the HRM "module" does the "error correction" and the watches just collect the data - good or bad. It's largely why it is fruitless to "blame" your watch when you see dodgy HR strap data.

Presume it is similar here. There is also the "fact" that a Stryd is not of course a Garmin product and there is no native support for it other than treating it as a standard foot pod sensor just like a Garmin one.

That is probably the reason yes. Anyway IMO Garmin watches are currently the only option if you wish to use Stryd, with all other watches you will face even more limitations in functionality. So for now better get a watch with minimum connection problems :)