HR (internal) issue with updates

I believe this issue started on my 5x with the 5.90 Sensor Hub update, as I really noticed a change as soon as that occurred, but may have been the general 8.00 firmware update and I just did not notice.

The issue/change is that the updating of the internal HR data in various watch faces that display that field is very slow and out of sync with the default HR app. There appears to be as much as a 10 to 15 second delay, (and sometimes much longer) before an update on the watch face HR display occurs, while the internal app appears to update fairly quickly and as it did prior to the latest firmware. This is a change in the watch and/or sensors behavior since the sensor hub update I suspect. Prior to the update, the HR info on the watch faces updated very quickly and appeared to be in sync with the default app.

I usually use the Gearmin watch face with the heart rate display. Checked the behavior in a couple of other watch faces that display HR data, such as Optimus HR, and the issue is consistent across each.

To test to see if it was the sensor update, I attempted a `downgrade` by downloading the 5.80 version from http://gawisp.com/perry/edge/ - renamed the sensor update to GUP2663.GCD and placed it in the REMOTESW folder - however it appears that the watch will not allow a sensor downgrade by this method. I then updated to the beta 6.00 version by this method - and that worked fine - but the issue is still the same.

I was going to raise the issue with the watchface developers to see if anyone else has reported a similar issue - but thought I would post here first.

Watch is 5x
Firmware is 8.0
Sensor is now 6.0

If I could figure a way to downgrade the sensor firmware first, I would be able to see if that was the issue. Certainly would not want to stay there - but just trying to go though some steps to what change caused the issue (sensor firmware, 8.0 firmware release, etc).

Anyone else experience similar or have any troubleshooting tips?

Jim

0 renton82 over 7 years ago

I'm interested in sensor hub fw downgrade too...

0 Former Member over 7 years ago

I believe this issue started on my 5x with the 5.90 Sensor Hub update

Garmin obviously found major flaws in Sensor Hub version 5.80 - published at the same time as main firmware 8.0 around February 15 - since they silently pushed out Sensor Hub 5.90 a mere week after (Feb 22), which was nothing more than a 'rebranded' version 5.30 from January 20. See my post for an internal hex-view:

https://forums.garmin.com/forum/into-sports/running/forerunner-935-aa/1313644-sensor-hub-5-90-and-map-update-for-935-over-garmin-express?p=1313739#post1313739

I find it strange that the watch negates your effort to downgrade from beta Sensor Hub 6.00 - where you should go to fenix5X,SensorHub_590.gcd, fenix5X,SensorHub_530.gcd or the v5.30 called GUP2663.GCD in fenix5X_791Beta.zip (the versions in the beta archives are md5sum identical to the standalone files).

The gawisp link you posted was to the Edge area, the Fenix stuff (most of it) is in:

http://gawisp.com/perry/fenix_D2_tactix/

If you are comfortable with a hex editor, and have some programming/compiling experience, you could try changing the version information in 5.30/5.90 to 6.01 or something; using the information in my first post and the tool I made available in the next:

https://forums.garmin.com/forum/into-sports/running/forerunner-935-aa/1313644-sensor-hub-5-90-and-map-update-for-935-over-garmin-express?p=1313976#post1313976

Though I don't really think the software is at issue here... I'm not interested in the CIQ world, but remember that the Fenix 5X is a special case with its two CPU:s (extra cycles needed to drive the map drawing) instead of one as in the regular Fenix 5 etc. Apparently this hardware design prevents a _live_ update of heart rate on a CIQ watch face. They have to update by pulling the number from a history instead of polling directly. So, it will look as if there is a serious 'lag'.

But don't quote me on this... As I said, not really into the CIQ scene.

0 mugc over 7 years ago

Thanks for the info Fletnix - very much appreciated. I had copied the link to the firmware files from an original post as opposed to the one that I found the fenix 5x files in - same as the one you posted.

Also thanks for the link to your previous post and you program for calculating the chksum used. I updated the 580 sensor hub software to version 601 and adjusted the checksum with you program (after patching with the diff file). Worked like a charm and I was prompted to apply the update. As you pointed out though - really did not notice any difference in the behavior of the HR info on the watch face. Given there was no change - I then changed a copy of the 590 firmware to a 602 version and applied that so I was back where I started. Noticed that the watch itself reports the version correctly even when changing the 590 to a 602 - so assume it is reading version from somewhere else.

It may be that I just did not notice the lag before as your explanation about having to read off of the history files makes sense - maybe the default garmin widget is reading off of the history file more frequently than the watch faces? Either way - not enough of an issue to really pursue further....

Thanks - Jim

0 Former Member over 7 years ago

Today my internal HR was turned off

0 renton82 over 7 years ago

Thanks for the info Fletnix - very much appreciated. I had copied the link to the firmware files from an original post as opposed to the one that I found the fenix 5x files in - same as the one you posted.

Also thanks for the link to your previous post and you program for calculating the chksum used. I updated the 580 sensor hub software to version 601 and adjusted the checksum with you program (after patching with the diff file). Worked like a charm and I was prompted to apply the update. As you pointed out though - really did not notice any difference in the behavior of the HR info on the watch face. Given there was no change - I then changed a copy of the 590 firmware to a 602 version and applied that so I was back where I started. Noticed that the watch itself reports the version correctly even when changing the 590 to a 602 - so assume it is reading version from somewhere else.

It may be that I just did not notice the lag before as your explanation about having to read off of the history files makes sense - maybe the default garmin widget is reading off of the history file more frequently than the watch faces? Either way - not enough of an issue to really pursue further....

Thanks - Jim

So... what i have to do if i want to revert back sensor hub 4.10 for example? I will go to ski in a few days and ski app is unusable with current fw/sensor hub!