Beta Software Version 6.78 Now Available!

My backlight is set to only come on manually but when I press the start button to go into activities the light comes on and also causes quite a lag. The TE is also way too low but I think it was off from the previous beta too.

Resting HR resetting bug still in place :(

After the 6.78b I did a bike/run with transition activity.
This activitiy did not was take in count for my trainning load/status.

As far I am able to remember, this kind of activity usually appeared on my trainning status.

Am I wrong or it is new?

Resting HR resetting bug still in place :(

Which bug? I ask this because there's been either a change in how Garmin is interpreting our all-day RHR or it's just a bug and overreporting. I know somewhere on these forums someone posted how Garmin is doing it (for people that wear it all day including sleeping with it and those that take it off for sleep), but I can tell you that change is NOT a universal change if it is one in fact.

I wear the 935 all day, and to bed. This watch has empirically reported my RHR in line with my actual RHR up until this change (38-42 bpm). Right now the watch is reporting my RHR exactly 10 BPM higher than my actual. How do I know that? Because when I did take off my 935 to charge, I true-up my data to my vivosmart HR and wear that until the 935 is ready. The moment I put the vivosmart on and it synced to CGM, magically GCM reported my RHR was right in line with my average. I literally watched the RHR change from 53 bpm (what it was getting from the 935) to 43 (after the vivosmart HR synced). When the 935 was done charging...it did the same thing in reverse.

So either it's now how Garmin interprets our RHR here on the 935 and the way the Vivosmart HR is the old way of doing it and hasn't been updated, or the 935 is bugged and has been even before 6.78.

If it's the latter, Hey Garmin, fix it in the next beta! If it's the former, it's wrong, by a proverbial mile. On a side note, the green filling watchface to designate charge status is nice...if redundant, especially when there is a giant percentile right smack in the middle of the watch face telling you how much of the watch is charged.

That's it, thank you. And yea, that pretty much proves the bug in the 935. It's something in the interpretation of the data on the 935, because the Vivosmart HR gets the whole day (with Sleep) correctly, the 935 is then either ignoring my sleep and basing it on RHR the one minute time measurement, or is just plain wrong.

Which bug? I ask this because there's been either a change in how Garmin is interpreting our all-day RHR or it's just a bug and overreporting. I know somewhere on these forums someone posted how Garmin is doing it (for people that wear it all day including sleeping with it and those that take it off for sleep), but I can tell you that change is NOT a universal change if it is one in fact.

I wear the 935 all day, and to bed. This watch has empirically reported my RHR in line with my actual RHR up until this change (38-42 bpm). Right now the watch is reporting my RHR exactly 10 BPM higher than my actual. How do I know that? Because when I did take off my 935 to charge, I true-up my data to my vivosmart HR and wear that until the 935 is ready. The moment I put the vivosmart on and it synced to CGM, magically GCM reported my RHR was right in line with my average. I literally watched the RHR change from 53 bpm (what it was getting from the 935) to 43 (after the vivosmart HR synced). When the 935 was done charging...it did the same thing in reverse.

So either it's now how Garmin interprets our RHR here on the 935 and the way the Vivosmart HR is the old way of doing it and hasn't been updated, or the 935 is bugged and has been even before 6.78.

If it's the latter, Hey Garmin, fix it in the next beta! If it's the former, it's wrong, by a proverbial mile. On a side note, the green filling watchface to designate charge status is nice...if redundant, especially when there is a giant percentile right smack in the middle of the watch face telling you how much of the watch is charged.

Resting HR (in User profile settings) gets reset to no value after some time no matter what value gets inserted - either average or custom.

Please remove the first step of calibrating altimeter when calibrating barometer.
It's redundant and annoying.
We don't need to calibrate altimeter before calibrating barometer!
And there is already an altimeter calibration function in altimeter app.

We don't need to calibrate altimeter before calibrating barometer!

Air pressure changes with altitude, and barometers measure changes in air pressure. So it makes sense to me that you should know the altitude at which you are calibrating your barometer.

Air pressure changes with altitude, and barometers measure changes in air pressure. So it makes sense to me that you should know the altitude at which you are calibrating your barometer.

But it’s the air pressure at sea level that the barameter reads. Therefore, if you calibrate that properly it can tell you the exact altitude I believe