I have upgraded my Forerunner 935 about 4 months ago with a Forerunner 955 and came across multiple issues which render the Training Status widget useless for training. I was wondering if more people have had the same experience? The following issues occurred:
Training Status:
Once the watch had gathered enough data to predict racetime, HR variability and training status. I started a 15 week training program for a half marathon. During this entire period my training status stayed on "Maintaining". In this period my endurance had gone up significantly, I felt really fit and come race day I broke my PB with ease. So it is safe to say that the training was effective but the Training Status did not reflect the process.
My theory is that the Training Status is partly based on the Load Focus widget. It kept saying that based on my Load Focus I was "Maintaining" my fitness and I had to do more anaerobic training to increase my fitness. If this is the case it would make the whole Training Status widget completely useless for a half marathon or longer distance training, since the focus will be more on aerobic and threshold training.
VO2Max Steady?:
During the whole training period my VO2max status kept saying "Steady" even though the graph showed a continuous incline. I went up about 4 points in total. I am really happy that the VO2max doesn't jump up and down with each run as much as it used to but a "Steady" status during 15 weeks of training with 4 points of VO2max increase just seems silly. The VO2max status does not reflect the VO2max measurements of the device. Again it seems that the status of the VO2max is also based on the Load Focus and not on the actual measurements.
All in all the 955 has been a great companion during my training in providing HR data and GPS/Pace. But sadly in 4 months of running the Training Status, one of the cornerstones of the Garmin setup, has been not useful at all. I don't think it is a bug rather than what data the 955 software uses to determine the Training and VO2max status with. It seems that in both areas the software gives priority to calculation/prediction as to actual measurements in determining the status. I hope that whatever is causing this will be updated soon.
Are there more people who have noticed this?