7.60 on Fenix 5X Plus, walking/hiking heart-rate off

I hit pause during hiking when i drink or I take some photos, but I've never seen correct hr value after restarting the activity. Now I try to push button after one minute... 

Thanks for the suggestion 

I've noticed the same issue when running. Theres are instances where I've found the HRM will report inordinately high values (180+ on a warm up when I'm more than likely at around 100-110bpm) in cold weather and if the watch is jostling (even slightly) on the wrist.

I'm able to fix this by taking the watch off, wiping the sensor down and then reseating it higher and tighter on the wrist to prevent the movement. Shaving the arm over where the sensor sits also appears to solve the issue.

My assumption here is that the sensor is picking up the movement of the watch across the arm hairs and misinterpreting it as blood flow.

Unfortunately not a new issue to me :(

forums.garmin.com/.../another-wrist-hr-thread t

The wrist HR for hiking was useless to me since I bought this 800 EUR marketing gag and I actually stopped wearing 24/7 as I do not want to fight with technology all the time. Such a device has to simply work as advertised, otherwise it just costs my personal time....

Unfortunately it only works some times for me. Weirdly when running, I have no issues with HR reading very low.

This has to be a software bug, 

I've tried to pause activity and restart after a minute. But HR remains too low.

I've upgraded watch to 8.40 version but seems to be the same.

Yesterday i used Fenix 5x plus for hiking : 80 - 90 bpm instead 140-150. Incredible. I'tried also trail running but HR remains very low. 

No issues after updating to 8.40. 

Super happy about this. 

Strange. Some days, HR works very well while on walk/hike mode, then some other days, it is not. If I do not iniitiate a walk and just look at my HR on the widget, it is fine. I thought 8.4 fixed this but not really. 

Same happens to me since I purchased the 5x plus at the end of last year. No firmware update since then changed anything. On some hikes it does work but on most it doesn‘t. I reported it to Garmin months ago and just received some standard answer. They also offered to send in the watch to check, bit due the behaviour, which does not point to a general hardware problem, this did not make sense to me. 

As I expected that they will simply do a check of the HR and then send it back with no result, I gave up on this

I‘m tired of fighting with an 800 Euros device. On the last hike, my tracked even „lost“ 400 elevation meters. According the track I started 400 meters higher than the endpoint, although start and end was the same location ;)

right, I can confirm that, but it‘s far away from a proper solution:(