Is it possible to unconditionally wake up my app from the background service?

I'm trying to develop a truly user friendly Alarm Clock application. I have my user interface just about where I want it to be, but I'm finding that it may not be possible to make it actually functional because I can't simply wake my app on demand from the background service and paly tones or vibrate for user attention.

Alternatively, is it possible to leave the app running but close all the Views and return to the watchface? (similarly to what music play apps appear to be doing) Then I could just use Timer() to monitor alarm times and trigger attention when needed, etc.

Top Replies

All Replies

  • Isn't that all you're saying for a couple of days in this thread? Devs shouldn't ask for stupid things, users want things that is detrimental for battery life and they don't know it, the fact that something is desired doesn't mean anything (well maybe the marketing department would disagree with that)

  • It doesn't seem likely at all that Garmin would add what is being asked for here.

    If there's a general problem with setting alarms, modifying IQ isn't the way to fix that.

    Devs shouldn't ask for stupid things

    ??? Are you saying devs should ask for stupid things? (I didn't say what was being asked for was stupid.)

  • users want things that is detrimental for battery life and they don't know it

    In this case I don't think anyone is saying that Garmin prevents this functionality due to battery life considerations. Battery life was brought up as a way that Garmin watches are different from other smartwatches.

    Also, I think users are asking for better alarm functionality, not necessarily for this functionality to be provided by a CIQ app. Indeed, if they knew how limited CIQ apps are (in terms of functionality and UI) compared to native functionality, they would probably explicitly *not* want this to be delivered via CIQ.

    Newer developers sometime treat the Garmin devices as being “general purpose” computers that they can program anyway they want. The reality is that Garmin severely restricts what programs are allowed to do. One basic idea is that IQ programs enhance the device but can’t “take it over”’ in arbitrary ways. This preserves the behavior of the device.

    I think this is the main point that was being argued. Garmin wants to tightly control the user experience of their devices, which is why CIQ apps are severely restricted. That's why data fields can't accept input on watches and device apps can't open themselves without user intervention. CIQ apps were never meant to be general purpose apps, they were always meant to augment the existing functionality of the watch in a tightly restricted manner.

    I agree that Garmin will likely never allow CIQ apps to do what's being asked here, and I also agree that if alarms suck on Garmin devices, the best way to fix that would be for Garmin to fix the built-in alarms.

    I also agree that most Garmin users don't know or care about CIQ. Most of the people I run with:

    - can barely open the settings menu on their watch (some ppl have no idea how to change activity settings, even if they've had their Garmin for years)

    - freely admit they use 1% of their watch's features

    I don't think there's any general problem with Garmin watches that can be fixed with CIQ - yes, this is by Garmin design.

  • You definitely get what I was saying. 

    IQ is pretty weird. It’s not an open “do what you want” environment.