• Replies 9 replies
  • Subscribers 20 subscribers
  • Views 1608 views
  • Users 0 members are here
Options
Related

Apps interfering with firmware functionality

Woody

Hi! Maybe someone can help me out: i created an app that is running overnight monitoring data. This seems to interfere with functions like the proprietary sleep analysis or stress tracking ,because these are not active when an app is running. Backgrounding would probably solve this  but is only possible every 5 minutes for a few seconds. Is there a way to solve it? 

  • When a CIQ device app is running in the foreground, CIQ background services don't run.  While running a device app may also impact things like syncing.  Are you seeing stress on the watch itself?

  • in reply to Former Member

    What you want to do is collect the data in a background service and not leave the main device app running.  For something like this you could do it as a widget where the widget itself only runs a short time and returns to the watch face or maybe even do it as a watch face.

  • in reply to jim_m_58

    For example, if you want to do things like sleep phase tracking (just an example, i know garmin is doing it :) ), it won't be enough to have a few seconds window every 5 minutes to analyze the data. You can write a device app, but because it seems it runs as an activity  no data like stress or sleep seems to be  collected (the stress graph starts when the device app finishes). I'm not aware about how widgets do this, if they run permanently in the background, that would solve it...

  • in reply to Woody

    All background services have the every 5 minute restriction.

    There are lots of things that garmin apps can do that can't be done in CIQ.  The native apps are not written in CIQ.

  • in reply to jim_m_58

    That's to good to know, thanks. I guess if you need some kind of ongoing analysis, you have to develop a device app, with the disadvantages i mentioned.

    Is there a reason for the limitation of background processes? I mean, of course I'm aware that limitations for standard processes make sense, but if it is possible to have an app running for several hours, it should be possible ro query for a high priority process that is less limited? 

  • in reply to Woody

    It's directly related to the battery.  You don't want them running all the time.  And only one background service can run at a time, so if you have a watch face and a widget with a background service and they are both set to run at the exact same time, one runs and then the other.  And a background service can only run for 30 seconds at a time.

  • in reply to jim_m_58

    Notice that for apps in the store with a background service, there is already this warning

    • Run in the background when it is not active (potentially affecting battery life)

    and that's with the current restrictions.

  • in reply to jim_m_58

    Okay, thanks for the info:) I guess the only chance is using a device app to achieve things like this then.