• Replies 9 replies
  • Subscribers 21 subscribers
  • Views 1304 views
  • Users 0 members are here
Options
Related

Epix 2 with AOD off turns off after 10s when timeout is set to 15s

97531
over 3 years ago

I have an Epix 2 and am seeing that if I set the display to turn off after 4 or 8 seconds it will in fact turn off after 4 or 8s depending on the setting. When I set the timeout to 15s it seems to turn off after 10s on connectiq watchfaces. I have coded a few watchfaces and they all seem to act the same way. I have also downloaded a few watchfaces and they have the same issue. The native garmin watchfaces timeout at 15s as I would expect. I also ran a test and saw and saw that when onExitSleep executed onUpdate was called multiple times within the first second. I'm kind of thinking that this may be why it is actually turning off after 10s rather than 15. Maybe when I set the watch setting to 15s timeout it is actually looking at 15 onUpdate calls, assuming one per second and then going back to sleep after the 15th call. Has anyone else seen or experienced this and does anyone know how I can keep my connectiq watch faces up for 15s when AOD is off?

  • over 3 years ago

    I’ve noticed this as well and would really like an explanation from Garmin.

    The Epix beta software turned off the AOD after 6 seconds regardless of system settings. Then they “fixed” it to 10 seconds when the system settings are 15. The main thing that bothers me is that there’s seemingly no logic to it.

  • over 3 years ago in reply to nonparametric

    Connect IQ watch faces will go into low power mode after approximately ten seconds on all products. Watch faces can be designed to have a low power mode state that will display a version of the watch face to avoid screen burn in, but if the app is not implemented with a separate low power mode, it will effectively just turn off the display.

  • over 3 years ago in reply to Brandon.ConnectIQ

    Hi Brandon,

    Thanks, this is indeed what I've observed. I guess my question is more the reason behind this choice... ie, why it ignores system timeout settings, and why there's an intentional difference in behavior between built-in versus CIQ watch faces. That's the part that doesn't make much (any) sense to me.

  • over 3 years ago in reply to nonparametric

    Connect IQ watch faces follow some basic rules to allow "always on" functionality on OLED screens:

    1. When the watch face is not active, it updates once a minute
    2. When the watch face is not active, it can only enable 10% of the pixels of the screen
    3. If the watch face violates #2, disable always-on mode, turning the screen off

    In this context, "active" can be likened to high power mode, like when the display is turned on with a gesture or button press. Connect IQ watch faces have historically used a high power mode/low power mode scheme with ~10 second time out, but I can check to see whether there is a reason why we don't use the system settings to govern the timeout.

  • over 3 years ago in reply to Brandon.ConnectIQ

    A small bit of follow-up on this: apparently the device is in control of when CIQ watch faces enter low power mode, so I've filed a ticket to have this changed to honor the system's screen timeout setting. If it's rooted in device firmware, then this may be fixed in a future firmware release.

  • over 3 years ago in reply to Brandon.ConnectIQ

    For those of you seeing this issue, can you let me know which firmware version you're using?

  • over 3 years ago in reply to 97531

    I appreciate the reply - we were able to confirm the issue on 7.35 and I've been talking with the product team about getting this corrected.

  • over 3 years ago in reply to Brandon.ConnectIQ

    Hi! I'm on 8.16 and the issue is the same. More that 10 seconds will not happen with a ciq watchface. The stock watchfaces honor the system settings.

    I also see a lot of fast screen updates when the watch changes to low power (aod).