Fenix 6 Series - 17.74 Public Beta

I had similar issues in general, non related to this beta. 

Enabling/disabling the "phone" app in the app list in Garmin Connect Mobile app I have the quick answer button but missing the missed call notification or I have the missed call notification but without the quick answer button during call notification.

The quick answer button in call notification works, the quick answer button in missed call notification never works, it simply ope SMS app in the smartphone. 

I am using a OnePlus 6T smartphone. 

Which widget? I found the Health Stats Widget doesn't list the status properly in the options (part of this bug I think) , but the Separate Pulse Ox one does. Easiest way to check is look at the pulse ox widget in Garmin Express and see when the last reading was.

Interesting... Again seems to act as it thinks is appropriate, but without logic  ok will try with phone app disabled, though this would suggest to me... No notification from that app, so no incoming call advise... Strange strange thing, i dropped an email as bug report, will see if this is listened to

For all the people that complain about pulse ox auto turn on... Which includes myself... Surfing through the web connect app i noticed in the setting of my watch that it appeared ON while on watch (Checked at that moment for being sure) was off... I suspect there could be some glitch with the web app not getting the setting made on watch and actually randomly applying its own...

This was the same for me on Fenix 6S but also on forerunner 245 for the move IQ function... It wouldn't turn really on and work if activated from phone or watch (though looking like active), worked if activated from web.

I think the web settings have some sort of priority, and sometimes don't get the updates coming from watch or mobile, this randomly re-apply their own status during some syncs.

Cheers

I've seen something very similar regarding Move IQ around 18 months ago. The watch and GC seemed to get out of sync and it was a bit of a mess of semi random toggling on/off. In the end I managed to disable Move IQ everywhere and get it to stick. It has not turned on again since, through countless firmware iterations, including many betas. I think you are right that GC takes priority over the watch settings. Very frustrating when the sync of settings doesn't flow equally in either direction.

Yes frustrating, also since... After sincing an activity later today it did it again! My theory that it would stay put if I had set it from web connect failed, in the end, however surely something strange goes on... Makes no sense it showed active on web while inactive on watch... Seems to think it has to evaluate my sp02 after activity... Could be it needs this for the EPOC evaluation, which makes sense... But why not just taking the readings it needs in the background without impact on the general setting? If you don't notice it i guess it will stay on forever... No sense

Thanks for the heads-up re: GC Web. Just had PO re-enable itself and yes, it was on according to GC Web...

For all the people that complain about pulse ox auto turn on... Which includes myself... Surfing through the web connect app i noticed in the setting of my watch that it appeared ON while on watch (Checked at that moment for being sure) was off... I suspect there could be some glitch with the web app not getting the setting made on watch and actually randomly applying its own...

This was the same for me on Fenix 6S but also on forerunner 245 for the move IQ function... It wouldn't turn really on and work if activated from phone or watch (though looking like active), worked if activated from web.

I think the web settings have some sort of priority, and sometimes don't get the updates coming from watch or mobile, this randomly re-apply their own status during some syncs.

Cheers

Hi, I seem to have high battery drain issues as well... about double the usual.

Reverting to a previous beta will reset the watch, i guess... Like reverting to the latest stable?

EDIT: after a watch reboot consumption seems to have gotten much better... there could have been something Wich remained locked ON overnight as it happens for the pulseox sensor (was not it this time, though...)