Btw. I have the goals alerts ON and I've never seen it during activity although many times I made the goal. And if we're treat alerts as light on they run in the different way.
Maybe it's a bug idk. Garmin has lots of bugs for sure.
I think the thing with the "During Activity" settings (with activity in "background") is intentional, although I realize it doesn't matter if you want it to work differently.
Garmin also has a lot of weird/bad design decisions (especially when it comes to UI), but I the During Activity design makes sense to me.
You are right only if we assume that switching on the light by gesture is quite different then making it by pressing the button. For me it's true exactly the same thing so.
For me they're very different (how many times a day do you use the gesture purposely or accidentally, as opposed to pressing the button?) and I understand why Garmin needs the option to turn off the gesture but not to turn off the light button. Their original reason (for MIP) must be battery life, although of course your reason or the user's reason may be different.
Then again, for AMOLED, I can see wanting to also disable the Light button, because of:
- slightly increased chance of burn-in every time the display brightness goes to max
- more importantly, the chance of annoying people with the full brightness of the display in some situations. e.g. if you're in a dark movie theatre
-- generally, user shouldn't see anything (black screen) just because activity is in background...
The user made the choice to turn the gesture off During Activity. This can be easily remedied by turning the gesture on During Activity
- for most user it doesn't matter :-) and we waste our time for showing our own opinion :-)
For sure haha :)
I do think it would be a good feature request to be able to disable single-clicking or double-clicking the Light button. If you post that feature request I will upvote it, although unfortunately there isn't a good subforum for that here.
Accidental double-click of Light is far worse than accidental siglge-click, since double-click turns on the flashlight, which never times out
- for tactic activity or real war activity watch should ask 10 times before it switch the light on
Yeah, I was thinking that Tactix is also a good use case for disabling the Light button (i.e. being able to disable the light completely). I actually searched the internet to see if this is possible, but ofc it isn't. (Tactix AMOLED does have "night vision" mode)
The most important thing is the PURPOSE of a functionality. So, what is the purpose of
- introducing the gestures,
-- switch on the light (and this the reason the gesture settings are in display group)
-- inform about exit from sleep for watch face (user can't see this but he can see only the light on)
-- generally, something connected with situation when USER wants to see something on watch, from the user's point of view: gesture = light on ONLY
- limitation of gestures during activity
-- the light shouldn't be on
-- during activity watch face is all the time in the high power but gesture calls onExitSleep :-) (but not the light on)
-- generally, user shouldn't see anything (black screen) just because activity is in background...
You are right only if we assume that switching on the light by gesture is quite different then making it by pressing the button. For me it's true exactly the same thing so.
Everything depends on the situation:
- for me and my user seeing qr code (even during activity in the background) its good to have gesture because I don't have to press button, screen (e.g. it is very cold outside and I have to take off the gloves)
- for tactic activity or real war activity watch should ask 10 times before it switch the light on
- for most user it doesn't matter :-) and we waste our time for showing our own opinion :-)
Btw. I have the goals alerts ON and I've never seen it during activity although many times I made the goal. And if we're treat alerts as light on they run in the different way.
Similarly, there is a setting called Health & Wellness > Goal Alerts - its options are Off, On, and Not During Activity. If you set this option to Not During Activity, and you reach your step goal while you're recording an activity, but you're looking at a watchface, glance or system settings, do you expect the goal alert to be displayed?
I expect it not to be displayed, based on my understanding of what "during activity" means. I'm curious what you would expect.
You never answered my question. If you think "during activity" has a certain meaning (i.e. "when an activity screen is visible") then you should stick to that meaning in most or all cases. What do you think Health & Wellness > Goal Alerts > Not During Activity should mean? "Not while an activity is being recorded" (my interpretation and Garmin's interpretation) or "Not while an activity screen is visible" (your interpretation). If I using the "goal alerts > not during activity" setting I certainly wouldn't want to get a goal alert during an activity just because I happened to be looking at the watchface or a glance.
It's simply illogical and inconsistent...
Gesture = ONLY light on.
If the gesture is ONLY used to turn on the light, why is it possible to turn on the light with the button? So e.g I start tactic activity and I don't want any light but settings give me the ability to prevent accidental switching on of the light by gesture but not y accidental pressing of the button...
This is the 3rd issue you have raised here, in addition to the other 2, unless I missed it before.
"If the gesture is ONLY used to turn on the light, why is it possible to turn on the light with the button? "
Like I said, this doesn't really make any sense.
---
So here's the 3 separate, yet kind of related issues I see in this bug report:
1) On Fenix 7, Connect IQ device apps (e.g. PSX-7) use the Display > During Activity settings even though no activity is recorded. In the same situation, native glances use Display > General Use settings, as expected.
I agree with this one.
2) When switching to a watchface during an activity, you think that the watchface should use Display > General Use settings, but in fact the watch uses Display > During Activity settings.
Like I said, I strongly disagree with this. It's very consistent behaviour, and it makes sense. "During Activity" means "while an activity is active/happening/being recorded", and nothing about "During Activity" suggests that an activity screen has to be visible. If I return to the watchface during an activity, I know that the activity is still being recorded in the background.
3) Garmin should allow the Light button to be disabled
To me this is a completely different feature request. It's perfectly fine (I would vote for it), but I disagree that it's illogical or inconsistent that Garmin doesn't already have this feature. The gesture is not the same as the Light button (see below).
settings give me the ability to prevent accidental switching on of the light by gesture but not y accidental pressing of the button...
First of all, it's a lot easier to accidentally do the gesture than it is to accidentally press the Light button.
Second, you usually have to purposely do do the gesture just to look at the watch (unless you just glance down and your arm is at the correct angle), so it makes a lot of sense that Garmin has an option to prevent the light from turning on when you do the gesture. Otherwise there would be a huge battery impact from the people doing the gesture all day, just to look at their watch.
On the other hand, you don't have to press the Light button to look at the watch, not to state the obvious. And if you do press the Light button by accident, it's usually not going to happen that often, so it's not the end of the world that the light always turns on. It certainly won't have a large battery life impact (unless you have a MIP device, you configure the backlight to have no timeout, and you don't notice the backlight is on, maybe because it's daytime). But ofc that would require you to purposely change the backlight timeout setting.
