Fenix 5X - 10.53 Beta Release

Try maybe to just use the map page briefly......then scroll to another screen.....If you keep it on the map page for the entire activity....you'll see more battery loss per hr.....

I did Email the beta team on this, though I am sure most of their efforts are going into getting the new "Plus" devices up to snuff to address review concerns, so I doubt we will see a ton of effort going into resolving this battery life on the 5X. If they do address it, and get down to <10% per day with a 1hr activity thrown in, I will be happy. 25% loss per day? Not happy. I ideally want the watch to be good for a week of back woods hiking and camping without needing to charge it.

I am thinking of reverting back to the plain old 5 and forget the maps (and stop bruising my arm on my bike). Apart from the +/-100ft errors on my specific Fenix-5 device's GPS, resulting in large accumulated errors, it was a perfect device for me. I was in the process of swapping my old display unit for a recent production unit when I ran into the 5X on a ridiculous sale price at L.L Bean. I couldn't resist going to the 5x for less than I paid for the 5. Now I am regretting it and embarrassed to swap it out yet again. (VA3 (Bottom of lake) -> F5S (to small) -> F5 (Bad GPS) -> F5X (Bad battery life, too big) ->?) The question mark is making me feel like a nut. I am willing to bet the new F5 GPS will be just as flaky. Perhaps I am a nut. I feel that if I spend this much on a fitness tracker, I want to be sure I will regularly use it, not leave it on the dresser.

I tried 10.53 today, no adverse effects. Had a bit of a fun time trying to get my watch to connect as a Mass Storage device, it took a soft reset and some connector re-seats.

Somebody else reported that EPO is always expired as per this thread https://forums.garmin.com/forum/on-the-trail/wrist-worn/fenix-5x/1394275-gps-version-223

I've noticed a bit more battery drain than with 9.20. I would lose around 7-8% a day with circa 1hr run using GPS. 24/7HRM and sleep tracking.

On 10.53 i'm doing 9-10% a day. So not excessive but still a little higher than normal and nothing changed on the watch (Tactix Charlie)

Also the Altitude isn't correct. I was sat on a boat on the Red Sea a couple days ago and it told me i was at 17m ASL. Thought the boat was affecting it so tried it on the beach and it said 15m ASL.

I'm currently sat at home where i know my altitude is 929m but the watch is showing 952m ASL.

Otherwise though everything else is ok.

...Also the Altitude isn't correct. I was sat on a boat on the Red Sea a couple days ago and it told me i was at 17m ASL. Thought the boat was affecting it so tried it on the beach and it said 15m ASL.
I'm currently sat at home where i know my altitude is 929m but the watch is showing 952m ASL...

Carl, I may be missing something here but you do know that you need to calibrate on a regular basis if you want the altitude to be correct? Any barometric altimeter will drift and, depending on the mode the watch has set, the best it can do is try to determine if changes in pressure are due to weather or actual altitude changes - something that it can do fairly well at times, or fail terribly at other times. For a sport watch, the advantage is that it can generally provide much better elevation change profiles and data, even if not calibrated to the correct actual altitude at start. In general this data is much more accurate than GPS altitude derived data (and YES, there are times it messes up).

I get a "storm alert" at the start of every activity. Even when there is no change in barometric pressure.

MDGr - what are your settings? I had this happen once on the previous beta about 2 minutes into an activity. I was using Auto Calibrate (with watch-mode being "auto" and it looked like a calibration may have taken place early in the activity which caused a noticeable change in the altitude which tripped a storm alert. I turned off Auto-calibrate as I do not want it on anyway and have not seen this again. I admit I did not report it to the beta team. If a calibration is tripping a storm alert, that would be a bug. Have you reported it?

Has anyone experienced problems with the auto shot tracking? I cant seem to get my distance shots accurate, or at least to show, as I used to in previios SW versions.

After upgrading to 10.53, can you connect to the device as a mass storage?

Since the upgrade, I'm unable to connect it. The screen on the F5x is the same like if I'm using the device in Garmin mode.
I've done some soft-resets, restarts, switch from mass to Garmin mode and switch it back, etc. but it doesn't work for me.

Any ideas?

Thank you!