Fenix 5S/5 Plus - 4.64 Beta Release

Since it is very tricky to measure the remaining capacity of a Li-Ion battery, it is not certain that this indicate that the drain is more during the period after the workout.
This could be an effect of the battery measuring system since during the gps period the voltage drops more and would indicate even less %, but is probably compensated for. Most likely this compensation is too big and it then appears that the drain is biggger after a gps period.

it is not certain that this indicate that the drain is more during the period after the workout.

That's a possibility, but then it's behaving much differently than my 935 does. And, as it is, the indicating battery drain during my GPS activities are already on the high side.

Since it is very tricky to measure the remaining capacity of a Li-Ion battery, it is not certain that this indicate that the drain is more during the period after the workout.
This could be an effect of the battery measuring system since during the gps period the voltage drops more and would indicate even less %, but is probably compensated for. Most likely this compensation is too big and it then appears that the drain is biggger after a gps period.

It’s not tricky.
State of the art is using a coulomb counter chip.
Using voltage alone to determine the capacity is very bad engineering.

The sensor hub in this beta version has helped with the ohrm but still needs more fine tuning. Installing this beta has given me some hope that they will fix it sooner than later.

"Sensor hub" remains exactly/binary same in all publicly released versions until now (i.e. 3.10 -- 4.64):
Fenix5PlusSeries_464Beta\5_SensorHub_v210\GUP3014.GCD, DateTime 2018-05-31 13:07:40.

New units from factory were reported with v200 (2.00) inside, but this v200 is overwritten by updates. We cannot rollback to this v200 of sensor hub, as it was never released to public and we cannot take it from new unit.

If there is any better behaviour, it is done by changes in the system, not by the sensor hub, because sensor hub is still v210.

I had no problems with EPO using Garmin Express 6.6.0.0 and now it is also fine for me with new Garmin Express 6.8.1.0.

I had issues with 6.7.x.x, so I used the older 6600 and now testing latest 6810, but there are no release notes for 6810 yet:
https://forums.garmin.com/forum/garmin-express/garmin-express-pc/1388958-garmin-express-release-notes

"Sensor hub" remains exactly/binary same in all publicly released versions until now (i.e. 3.10 -- 4.64):
Fenix5PlusSeries_464Beta\5_SensorHub_v210\GUP3014.GCD, DateTime 2018-05-31 13:07:40.

New units from factory were reported with v200 (2.00) inside, but this v200 is overwritten by updates. We cannot rollback to this v200 of sensor hub, as it was never released to public and we cannot take it from new unit.

If there is any better behaviour, it is done by changes in the system, not by the sensor hub, because sensor hub is still v210.

In the beta download there’s a sensor hub folder so that’s what I was referring to.

Installed 6.8.1 and now EPO is "current" again, so you are more helpful than Garmin staff around (?) here.

There is an official Garmin response on the thread on the 935 forum that specifically related to this issue. I imagine the problem for the Garmin mods is that this issue has been reported in multiple places and it would be a challenge keeping up with all of them. The most specifically named thread was on the 935 forum, so that’s where official updates got posted. https://forums.garmin.com/forum/into...31#post1397031

My apologies for the late reply to this thread (I have been out of the office). We are aware of this issue and working with the Garmin Express team to determine why in some instances an EPO file is being sent to devices that is too large and causing this issue. I will update this thread when the issue is resolved. We apologize for any inconvenience in the mean time.

If you are still seeing this issue after updating Garmin Express to version 6.8.1.0, please post in this thread so that we can take a closer look.

In the beta download there’s a sensor hub folder so that’s what I was referring to.

The beta probably contains anything which has been changed in any firmware version since the original release of the watch. Otherwise, there would have to be requirements for which firmware version the beta can be installed on top of. I have not been able to find any such requirements.

Consequently, your observation of a folder in the beta does not contradict what JiriAPet wrote.

And if you look in the sensor hub folder in the latest beta, you will see a file date of May 31. So nothing new there.