Fenix 5S/5 Plus - 4.59 Beta Release

Question for those using the "continuous mode" for the altimeter.
At the start of an activity, are you just letting the GPS acquire signal (turns green) and then you start your activity?
If so, are you seeing correct altimeter readings during and at the end of your activity (+/- 100 feet) ?

I do a MTB ride that starts at ~7500 feet and climbs to about ~9000 feet. I live at 4500 feet where my watch is calibrated regularly.
If I manually calibrate my altimeter in the parking lot using GPS or DEM before I do this ride, I get the correct altimeter readings all through the ride and the data saved for the ride is correct.
If I do not manually calibrate my altimeter in the parking lot and just rely on the "continuous mode" for calibration I see that the data stored for the ride has defaulted to the last manual altimeter calibration elevation which is usually my house at 4500 feet.
The map data in this scenario is correct, but the beginning, during and end elevations are off by ~3000 feet. Anyone else experiencing this or I am I doing something wrong?

Massive battery drain on b4.59

See this post: https://forums.garmin.com/forum/on-the-trail/wrist-worn/fenix-5-5s-plus/1367209-disappointing-battery-life?p=1392732#post1392732

Rebooted the watch before nighttime yesterday. Had about 5% drain over 7 hours during the night. That would around 17% pr day. Or the same as about 5 days of standby - without any activity!

This is really dissapointing :-(

I noticed massive battery drain too!

Question for those using the "continuous mode" for the altimeter.
At the start of an activity, are you just letting the GPS acquire signal (turns green) and then you start your activity?
If so, are you seeing correct altimeter readings during and at the end of your activity (+/- 100 feet) ?

I do a MTB ride that starts at ~7500 feet and climbs to about ~9000 feet. I live at 4500 feet where my watch is calibrated regularly.
If I manually calibrate my altimeter in the parking lot using GPS or DEM before I do this ride, I get the correct altimeter readings all through the ride and the data saved for the ride is correct.
If I do not manually calibrate my altimeter in the parking lot and just rely on the "continuous mode" for calibration I see that the data stored for the ride has defaulted to the last manual altimeter calibration elevation which is usually my house at 4500 feet.
The map data in this scenario is correct, but the beginning, during and end elevations are off by ~3000 feet. Anyone else experiencing this or I am I doing something wrong?

This picture is from my trail run this morning. I probably waited a few minutes past the "green" GPS fix while getting my headlamp, flipbelt, etc setup for the run. The start and stop are about 1 foot from each other on the chart and the overall elevation for the run seems correct. This is just relying on the DEM data.

With that said, your situation sounds a little goofy because 3000 feet of difference is huge! That almost sounds like hardware or bad DEM data. You might be able to check the sensor in the service menu. If it seems okay, then I'd recommend that you put a saved location in the parking lot of your next run. Edit the elevation of that saved location to the known elevation of the parking lot. This will force a calibration to that elevation every time the system gets a fix near that spot and you'll likely not have to manually calibrate again in that location.

I also add a 2 field data page on my trail runs. Field 1 is GPS, field 2 is elevation. I can look at this while the system is getting a fix and see once it settles down. This is probably a better indication of a true 3d fix than the green bar filling up.

ciq.forums.garmin.com/.../1393093.jpg

This picture is from my trail run this morning. I probably waited a few minutes past the "green" GPS fix while getting my headlamp, flipbelt, etc setup for the run. The start and stop are about 1 foot from each other on the chart and the overall elevation for the run seems correct. This is just relying on the DEM data.

With that said, your situation sounds a little goofy because 3000 feet of difference is huge! That almost sounds like hardware or bad DEM data. You might be able to check the sensor in the service menu. If it seems okay, then I'd recommend that you put a saved location in the parking lot of your next run. Edit the elevation of that saved location to the known elevation of the parking lot. This will force a calibration to that elevation every time the system gets a fix near that spot and you'll likely not have to manually calibrate again in that location.

I also add a 2 field data page on my trail runs. Field 1 is GPS, field 2 is elevation. I can look at this while the system is getting a fix and see once it settles down. This is probably a better indication of a true 3d fix than the green bar filling up.

Thanks!
It seems as though the "continuous mode" isn't actually calibrating the altimeter during the activity.
I have posted the elevation profiles from one of my recent rides with the "elevation correction disabled and enabled.

I will give that a shot. I also noticed the new beta 4.61 has some new GPS firmware.
I will give the beta a go and see what happens.

Thanks!

I will give that a shot.
I see the new beta 4.61 has some GPS firmware update.
I'll give that a try as well.

Thanks!