Background task sending alerts / notifications

Former Member
Former Member

Hello,

Working on a fairly simple widget, which has a background tremporal event process. What I would like to do is create a simple alert / notification for the user - think something along the lines of the "Move!" messages that pop up from the system, but require no action.

I can (and for my development am using) the Background.requestApplicationWake() to create a message, which requires the user to click the accept or decline option, with accept opening the widget. This is fine as far as it goes, but would like to be able to do a simple "alert" like message if possible, without the user needing to do more.

Is this possible?

  • Former Member
    0 Former Member over 6 years ago in reply to jim_m_58

    Hi,

    Was hoping I had just missed something in the documentation. 

    I am working around it as I said, but wonder if other people might like an alert / notification from the background process as well. Something that would just be a quick update, without having to launch the entire application / widget.

  • I'd definitely would want this buzz + flyby message too (and have gone in lengthy discussions a few years ago about this very subject)

    (The Background.requestapplicationwake is handled very differently on different devices btw (some devices do a buzz + message, some devices show the message without buzz, some devices hang after showing the message,...). It's not so easy to align this as it's not 1 team in charge of fixing this, but every device team needs to apply the fix.)

    In case you're in for a lengthy read: https://ciq.forums.garmin.com/developer/connect-iq/f/discussion/5130/feature-request-vibration-from-watchface-and-or-vibration-from-background-process/34814

  • Former Member
    0 Former Member over 6 years ago in reply to peterdedecker

    Hi,

    It would really be nice to be able to do a simple alert from the background.

    Also have another issue with the Background.requestapplicationwake, in that if the user uses the check to open the widget then the widget never closes itself they way it would if you had opened it from the widget wheel - something I reported in another post.

    I can appreciate Garmin trying to control the users experience, and battery usage, but if your going to open up the platform to development and expect people to help by making cool additions, you really need to give the developers some reasonable access.

    Since the background tasks are already limited to how frequently they can run, I don't think this would really represent much of a battery issue.

    As Jim also pointed out, and your other post, a lot of these limits were put in place under older devices with smaller capacity batteries, lower powered and faster processors, etc. Time for a revamp and revisit some of these limits and rules may be in order.

  • Since the background tasks are already limited to how frequently they can run, I don't think this would really represent much of a battery issue.

    I agree but you don't have to convince me, I'm all for it since 2 years ago (see the other post) ;)