Problems with pool count with the new Forerunner 955

There is no Garmin response to this. Same is for Fenix 7 users who have same issue. I am starting to believe it is hardware issur and Garmin does not want to admit it.

it should not be a HW issue. it seems a memory full problem: when I switch off-on, then the pool count is perfect. After some days it shows "--" again. switching off-on brings back to correct operation.

It is like a variable is filling the available memory (just a guess).

Garmin could spend a couple of words to say that the investigation is ongoing.  Due to this poor support probably the 955 will be my latest Garmin.

After many days without the issue (after deactivating stroke detection) yesterday I my watch stopped counting the distance again. It got stucked at 121mts and I had to reset it and start again.

I see a lot of people here with the same issue, I´m seriourly thinking about returning the watch, I´m a swimmer and I need a watch that do the work.

Yeah not the best way they are handling all the MANY issue here. No proper bug reporting system to make it easy to record and check status on items. lack of recognition of the fact that this rollout has been a mess ...putting it mildly. Had Garmin since the 201 ...never experienced such a shambles! Almost at the stage of doing without this and using the AW 6 ...sad to say!

It should also not be that this issue remains open 6 months after reporting it if ut was software issue - it would have been fixed by now.

Vizi said:

It should also not be that this issue remains open 6 months after reporting it if ut was software issue - it would have been fixed by now.

The FR955 watch was released in June. It's now the start of October. I make that 4 months.

Bugs are getting fixed. We don't know how many people Garmin have working on these bugs nor how they're prioritized. I'd expect running bugs would be the ones treated with a higher priority in a watch primarily aimed at runners.

Fenix was released before 955, and swimming issues have been reported soon after Fenix/Epix release. Those issues affect 955 and 255 as well.

Be it 4 or 6 months, does not matter. What matters is that swimming issues are present since release and Garmin did not fix it or provide feedback on its plans to fix it. 

I have a lap counting issue, but it seems different than what people are describing here. In a 25 yard pool, with my 955 configured for 25 yards, I have Stroke Detection and Auto Rest on. One out of every 10 or 20 lengths gets lost. I might swim a 300 yard interval, and once I've stopped, let my watch auto-pause and get all caught up, it reports a 275 yard interval, which is impossible since I'm back at my starting point. When I look at my data in Connect, every missing length has a corresponding length with twice the strokes, that took twice the time.

For me, this is random pool lengths getting merged in the middle of intervals. Not something that happens and doesn't recover for awhile. Does this sound like a separate issue?

Update: I've confirmed this still happens with Stroke Detection turned off.

My 955 will be here next Monday.  Not really looking forward to it after this thread.  The 945LTE suffered with a pool workout bug that made workouts with repeats unusable for 11 months on it, being fixed just 2 weeks ago.  Sigh.  Hold on for the long haul 955 peeps.