Fenix 5X+ has started to shut off on it's own

And so it happened again while editing this post... I'm now going to factory reset it and charge it to 100% (I was at around 50% now).
I'll keep updating.

Made a factory reset, started having major connectivity issues when connecting it to the phone again. Connection dropped in and out and now during a sync that was at about 50% after 10 minutes it shut off again.

Which SW Version are you on?

Also, what phone do you have?

My recommendation would be to turn off the Bluetooth connection to your phone and see if things stabilize. I'm currently trying to diagnose the issues with Bluetooth and IOS devices. It's been very temperamental. You have to do a lot of pairing and fiddling, but once you get it paired and data is being transferred *without* having the application open or minimized, it will continue to work. Problem is, once you re-open the Connect app, the communication get messed up again... Frustrating to say the least.

Were you the one with the multiple HR rates being shown on the watch face? If so, I have a theory on that too. I don't think the device is defective. I think it has to do with polling, contention, and MIP refresh.

Which SW Version are you on?

4.20.00

Died on me again today... going to factory reset it once more then contact Garmin if it happens even once more.

And again this night (updating this instead of doing multiple replies). Hadn't done the factory reset yet. Doing it for the second time now, then we'll see.

CBSalad I would really like to hear what your thoughts were on all of these issues. Sending my watch back for a replacment tomorrow since it is now unable to stay on for even 5 minutes, can't connect to the pc or app anymore and crashes to shutdown almost no matter what i try to do on the watch... I really love it if it could just work. The next watch is going to me my third 5x plus and my second replacment... don't really know what's a good alternative to this amazing watch, but if the next one acts up as well I will have to look elsewhere. Either another watch in the line up or something like Suunto... but I really like my 5X plus when it works.

Krissche that watch should certainly go back. That's for sure. What you're experiencing is crazy. My only thought regarding the watch crashing was that the BT connection might be drawing a lot of power and causing crashes because there is too much draw. The BT connection in v4.20 and even the betas is terrible. 4.65 is better, but still bad. Mine is using more than 15% per day with normal usage.

I have to crash the IOS app on purpose during a sync to keep the background BT connection with the 5X+ or my battery will use more than 20% a day with normal use.

What I was alluding to regarding the HR display is that, the HR is not a linear reading - your HR fluctuates - unless you're meditating or dead... Anyway, the HR data is more like a waveform and as each widget on the watch face asks for a reading the number can naturally fluctuate. That can introduce minor discrepancies, but you were seeing a little more than that. I think if that is compounded by contention and the wait to update the MIP display, you could experience seconds of delay between each request for a HR reading. Remember, each widget is asking for HR data and at different intervals. Undoubtedly those requests are trouncing on one another.

Take all of that and then ask the display, which tries to minimize updates to save power, to update itself several times in an attempt to display each HR reading and I think what you were seeing was the limitation of the architecture and not a defect. It's just too much polling, screen updating, and fighting for the same resources.

So, that being said, I decided to replicate the issue on my watch to prove my hypothesis and... it does the same thing....




ciq.forums.garmin.com/.../1401892.jpg

Krissche that watch should certainly go back. That's for sure. What you're experiencing is crazy. My only thought regarding the watch crashing was that the BT connection might be drawing a lot of power and causing crashes because there is too much draw. The BT connection in v4.20 and even the betas is terrible. 4.65 is better, but still bad. Mine is using more than 15% per day with normal usage.

I have to crash the IOS app on purpose during a sync to keep the background BT connection with the 5X+ or my battery will use more than 20% a day with normal use.

What I was alluding to regarding the HR display is that, the HR is not a linear reading - your HR fluctuates - unless you're meditating or dead... Anyway, the HR data is more like a waveform and as each widget on the watch face asks for a reading the number can naturally fluctuate. That can introduce minor discrepancies, but you were seeing a little more than that. I think if that is compounded by contention and the wait to update the MIP display, you could experience seconds of delay between each request for a HR reading. Remember, each widget is asking for HR data and at different intervals. Undoubtedly those requests are trouncing on one another.

Take all of that and then ask the display, which tries to minimize updates to save power, to update itself several times in an attempt to display each HR reading and I think what you were seeing was the limitation of the architecture and not a defect. It's just too much polling, screen updating, and fighting for the same resources.

So, that being said, I decided to replicate the issue on my watch to prove my hypothesis and... it does the same thing....

But you never get any wierd pixel-mixes between numbers on any screen? Because I'm way past caring about the heart rate being different in the different fields and way more interested in understanding why the screen architecture seems to be so bad that it can't even handle small updates to the screen without messing up.ciq.forums.garmin.com/.../1402058.jpg