Acknowledged
4 months ago

Can widget run in background and drain battery?

1. f7 13.22, backlight settings

- activity - 50%, 5s, gesture off

- general - 80%, 8s, gesture on

2. no activity

3. CIQ watch face (e.g. PSX-6)

4. gesture - backlight on - OK - general rule

5. go to widgets list

6. gesture - backlight off - why? there is no activity, general rule should be applied

7. select CIQ widget (e.g. PSX-8 without background service) and press start

8. main view PSX-8, gesture - backlight off - why? there is no activity, general rule should be applied

9. do nothing and wait to close widget by system and return to CIQ watch face

10. watch face PSX-6, press start and from time to time I can see main view of PSX-8 instead of activities/apps list

_psx_
  • over 1 year ago

    > I've read this article and don't really understand how to manage this new feature (e.g. should I stop to use attention and have to use if to check state).

    I would say the answer is probably "yes", but it's hard to say for sure. For one thing, with Attention.backlight() there's already a precedent where it throws an exception if you call it too often:

    > Calling this repeatedly can hold the display on, but if the product has burn in protection an exception will be thrown if you attempt to keep the display enabled for too long (e.g. over 1 minute).

    Also, looking at the table for "Active" and "Inactive" permissions, there's roughly 3 kinds of wording to describe access:

    1) access allowed/permitted

    2) access denied/limited/blocked

    3) access may fail in a non-fatal way

    For 3), Garmin went out of their way to say *may* fail in a *non-fatal* way, which implies that for 2), access could fail in a *fatal* way. The description for Attention in the Inactive state matches 2) (Access Is Denied)

    That's just me trying to read between the lines tho. It could also be that the docs are inconsistent or don't tell the whole story. And it's not clear whether limiting/denying access would generate an exception (which can be caught) or an uncatchable error.

    Would be nice if all of this was explicitly documented, but hopefully it can be tested in the simulator.

  • over 1 year ago in reply to jim_m_58

    It happens on f7 with older firmware...

    In point 10. user wants to start activity! User knows nothing about multitasking and even doesn't remember that 5 hours before he has forgotten to exit from widget (using back button) and system suspended widget.

    I've read this article and don't really understand how to manage this new feature (e.g. should I stop to use attention and have to use if to check state).

  • over 1 year ago

    Just found this a few hours ago https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/venu-3-now-available-on-connect-iq-sdk-manager

    and specifically the section on on Multitasking.  All I know right now is I think "onInactite()" may come into play when it comes into shutting things down after something like a glance timeout.