How does my watch know that I am stress ?

I am pushing them hard on this, and all we can do is hope that more and more people raise it. I have had a bit more stability since going to ver 8.0.0 and doing another hard reset to try and cure an elevation data issue. But the jury is out on it at the moment, and it could go any day now back to the usual crap. But so far, we have had 48 hours of accurate data.

OK, so I have an update that I think those that are suffering will be quite keen on. Since purchasing my 935, the all day stress has always been bad. A hard reset wouyld always curte it, but after a day or two it would go back to crap data. I also had an issue when upgrading to version 8.0, which screwed my elevation stats. Essentially Garmin did nothing to try and fix this issue, the only update was, we are working on it.

I called Garmin to chase up this issue early last week. Straight away I was offered an RMA, as he stated that as the issue had been escalated, this would fix the issue.

The new 935 duly arrived in two days and it came loaded with 7.60. I waited a few days, and as expected, the elevation and barometer was perfect.

All day stress started to work fine for the first two days, and then went bad again. This was my second RMA in the space of 6 weeks, as Garmin had previously replaced it due to issues over all day stress, but even on version 8.0, it made no difference.

So after a couple of days of use on 7.6, the all day stress went bad again on 7.6. Damn I thought. I then thought i would upgrade to 8.0 as i had nothing to lose. I am slightly amazed that five days later, all day stress is recording perfectly, and now looks to be sorted.

So what conclusion can we come to? I can only presume that this was a combined fix of hardware and software, as the new RMA watch only worked for all day stress on ver 8.0, and not 7.6. There was a patch in 8.0 for all day stress, so in my case, it l;ooks to have resolved my issue.

BUT, it is worth noting that a similar path, 6 weeks earlier with my other RMA, and putting 8.0 on it, did not produce the same effect. So it appears that the new watch (2nd RMA) must be different in some way to the first RMA watch.

RMA seems to be the answer, and i would encourage you to get on the phone, definately if you are still in warranty, but also if you are out of warranty and your all day stress has never worked.

I would like to know how much cheaper could the watch be if people wouldn't return it for every minor issue they think they have.

OK, so I have an update that I think those that are suffering will be quite keen on. Since purchasing my 935, the all day stress has always been bad. A hard reset wouyld always curte it, but after a day or two it would go back to crap data. I also had an issue when upgrading to version 8.0, which screwed my elevation stats. Essentially Garmin did nothing to try and fix this issue, the only update was, we are working on it.

I called Garmin to chase up this issue early last week. Straight away I was offered an RMA, as he stated that as the issue had been escalated, this would fix the issue.

The new 935 duly arrived in two days and it came loaded with 7.60. I waited a few days, and as expected, the elevation and barometer was perfect.

All day stress started to work fine for the first two days, and then went bad again. This was my second RMA in the space of 6 weeks, as Garmin had previously replaced it due to issues over all day stress, but even on version 8.0, it made no difference.

So after a couple of days of use on 7.6, the all day stress went bad again on 7.6. Damn I thought. I then thought i would upgrade to 8.0 as i had nothing to lose. I am slightly amazed that five days later, all day stress is recording perfectly, and now looks to be sorted.

So what conclusion can we come to? I can only presume that this was a combined fix of hardware and software, as the new RMA watch only worked for all day stress on ver 8.0, and not 7.6. There was a patch in 8.0 for all day stress, so in my case, it l;ooks to have resolved my issue.

BUT, it is worth noting that a similar path, 6 weeks earlier with my other RMA, and putting 8.0 on it, did not produce the same effect. So it appears that the new watch (2nd RMA) must be different in some way to the first RMA watch.

RMA seems to be the answer, and i would encourage you to get on the phone, definately if you are still in warranty, but also if you are out of warranty and your all day stress has never worked.

Keep us updated because I had the all day stress work for a week and a half after my first hard reset until it went bad again, yet the second time it lasted only a couple of days after a second reset, so may be that you are not out of the woods yet.

Also, I don't think there is anything hardware related since until firmware 7.60 it was working perfectly, and its affecting different Garmin models (Fenix, 935, Vivoactive3, etc) . I'ts more likely something they did in the code of 7.60 and haven´t been able to fix it IMO.

OK, an update as requested on the all day stress. It has been nearly two weeks since the new 935, and things are running smoothly. I have been ill with a virus this week, and had a really bad nights sleep on Monday. I checked the all day stress stats and sure enough, the recording looked as though it had gone bad, just ike before. However, the following day/night did appear to show accurate rest and stress patterns.

The following nights have also been a bit up and down in terms of sleep quality, and again has been recorded perfectly.

So in conclusion, the new RMA has fixed the issue. The second RMA I receieved has to be slightly different hardware from the first RMA received.

The watch is sold as a product with a number of features and functions. If one of those functions does not work corectly, then the consumer has a right to expect things to just work. As you state, the product is not cheap, so why should people settle for second best?

All day stress wasn't advertised at launch and came ~6 months into the lifecycle of the device as bonus. Also, regarding your points on RMA fixing Stress, it's 99% not even possible that that's what happened. Yes, there seem to be glitches with stress, but they are almost certainly software related.

Well, I am only stating facts. It was the 2nd new watch that made the difference for me.

Of course, you are clearly the expert, so if you say it is software, it must be software!

I'm getting a little tired of this myself. I have chronic "high stress" especially when I am asleep, including deep sleep. I don't know how much more relaxed I could be. The app berates me for inciting my impending exhaustion. The ONLY blue bars I get, sometimes, are when I have a Diet Coke and read the news once a day, and when I push the cart around the grocery store. Day in, day out, my % high stress is many times over my % rest. I have literally had a 12-lead ECG and 24 hour Holter monitor exam because this was so unnerving, given that low HRV (= Garmin high stress) is tied to heart malfunctions. Those tests along with the blood labs were normal.

When I initially got the 5S, it had a lot of drop-outs during sleep, but a lot more reasonable levels, including some rest (blue) during sleep, and rest at times in the day that I felt were restful. About the time of the firmware update, I also had the flu, so I attributed the horrific overnight levels and elevated day levels to that. However, I've long since recovered and the watch has not.

I sure am hoping this is a bug and they will soon fix it. I have reported it, got a "thanks for letting us know" message, and then radio silence since.

I'm just glad to see it is not just me.

Interesting safeandsilent. My Stress values did go back to bad when I had a virus, and I sort of hoped that they would go back to normal levels, indicating overnight rest when I got better. It is probably a little too early to say that it is broken, but I am only seeing around 25 minutes rest a day now, which again does not appear right. The nexy step for me is to hard reset in a few days time if it does not settle down and see how long it lasts again. It could be recording correct data, but again from how I feel, it does not appear representative.