"Alarm Clock" and "Alarm Done" events simply not firing

[gtdp]

Basically neither of the Alarm events seem to be firing at all for me;
having set up the most simple task possible (Context: Event -> Alarm
Done, with a resulting pop-up box that says "test"), I've tried over
and over with alarms every minute with every single possible option
changed and I simply cannot get Tasker to realise that I've dismissed
or snoozed an alarm. Lots of other (non-alarm-related) profiles work
fine, so I'm really not sure what's wrong or how I can fix it, the
alarms are definitely the standard Android alarms.

I'm running a HTC Desire HD, Android 2.3.3, Tasker version 1.0.21u2m.

[Pent]

> Basically neither of the Alarm events seem to be firing at all for me;
> having set up the most simple task possible (Context: Event -> Alarm
> Done, with a resulting pop-up box that says "test"),
> I've tried over
> and over with alarms every minute with every single possible option
> changed and I simply cannot get Tasker to realise that I've dismissed
> or snoozed an alarm. Lots of other (non-alarm-related) profiles work
> fine, so I'm really not sure what's wrong or how I can fix it, the
> alarms are definitely the standard Android alarms.

I tested this on my Nexus S (2.3.4) without problem, probably it's
HTC's alarm clock app. But if the events are available, I'm surprised
they don't work.

You can send a log (straight after the event is not recognized) if you
like:

http://tasker.dinglisch.net/faq-how.html#x

Pent

[Pent]

Thanks for the log.

Unfortunately the intents are not visible, though the alarm package is
correct. Maybe you can find the alarm apk in /system/app and send it
to me so I can have a look.

BTW, did you try Alarm Clock without specifying any label ?

Pent

[gtdp]

Thanks for having a look, sorry that my internet access is so sporadic
at the moment... I did try alarms with no labels, it didn't make a
difference.

As for getting the apk from /system/app, I'm not entirely sure how to
do that... I've tried with ESFileExplorer and on a regular file
explorer when the phone's connected to a computer and can't find that
directory anywhere, even with hidden folders etc turned off. My phone
isn't rooted, if that's important.

On May 25, 5:25 pm, Pent <supp...@apps.dinglisch.net> wrote:
> Thanks for the log.
>

> Unfortunately the intents are not visible, though thealarmpackage is
> correct. Maybe you can find thealarmapk in /system/app and send it

> to me so I can have a look.
>

> BTW, did you tryAlarmClock without specifying any label ?
>
> Pent

[Koolcracker]

I'm on a Samsung Galaxy S and I'm not getting it either.

[bgschaid]

> > > BTW, did you tryAlarmClock without specifying any label ?
>
> > > Pent

Same for me. AlarmClock and AlarmDone do not work on my LG Optimus
Black (Android 2.2)

Bernhard

[bgschaid]

Is it possible that this problem is even more general: as a
"workaround" I installed GentleAlarm (as it is supported in 3rdParty)
but the events for this don't work either.

What additional information would be requred to diagnose this problem?

Something I noticed when quickly looking at the logs is that vendor
name (lge) is in the package name of the alarm-application:
D/Receiver(32158): ==[[ ALReceiver intent ]]===>
com.lge.alarm.alarmclocknew
Don't know if this is normal in Android. If not: could this be the
reason that Tasker does not pick this up?

Bernhard

[Pent]

> Is it possible that this problem is even more general: as a
> "workaround" I installed GentleAlarm (as it is supported in 3rdParty)
> but the events for this don't work either.

[I assume you have the latest Tasker version]

The code for Gentle Alarm is completely different. Are you sure you
have version 3+ of Gentle Alarm ?

> What additional information would be requred to diagnose this problem?
>
> Something I noticed when quickly looking at the logs is that vendor
> name (lge) is in the package name of the alarm-application:

Is that Gentle Alarm or your builtin one ?

> D/Receiver(32158): ==[[ ALReceiver intent ]]===>
> com.lge.alarm.alarmclocknew
> Don't know if this is normal in Android. If not: could this be the
> reason that Tasker does not pick this up?

It's likely that the cause for you, yes. There is unfortunately no
standard signal for alarms.

If you send me a log of an alarm going off I might be able to add it:

http://tasker.dinglisch.net/faq-how.html#x

Pent

[bgschaid]

On Sep 6, 10:26 am, Pent <supp...@apps.dinglisch.net> wrote:
> > Is it possible that this problem is even more general: as a
> > "workaround" I installed GentleAlarm (as it is supported in 3rdParty)
> > but the events for this don't work either.
>
> [I assume you have the latest Tasker version]

Hope the Android Market updated me to the latest: 1.1u2m

> The code for Gentle Alarm is completely different.  Are you sure you
> have version 3+ of Gentle Alarm ?

3.3.2

But when preparing a log it suddenly triggered. I believe this was a
new profile where instead of Type "Main" (which I believe is the
default) I set the Type to "Any". But I'm not sure because both
profiles for Gentle Alarm were active and I'm not sure which one
triggered.

> > What additional information would be requred to diagnose this problem?
>
> > Something I noticed when quickly looking at the logs is that vendor
> > name (lge) is in the package name of the alarm-application:
>
> Is that Gentle Alarm or your builtin one ?

That is the built in one from an old log. I'm preparing a new log and
will send it to the support-address.

>
> > D/Receiver(32158): ==[[ ALReceiver intent ]]===>
> > com.lge.alarm.alarmclocknew
> > Don't know if this is normal in Android. If not: could this be the
> > reason that Tasker does not pick this up?
>
> It's likely that the cause for you, yes. There is unfortunately no
> standard signal for alarms.

That's too bad.

>
> If you send me a log of an alarm going off I might be able to add it:
>
> http://tasker.dinglisch.net/faq-how.html#x

I will. Thanks

Bernhard

[bgschaid]

On Sep 6, 11:18 am, bgschaid <bgsch...@gmail.com> wrote:
> On Sep 6, 10:26 am, Pent <supp...@apps.dinglisch.net> wrote:
>
> > > Is it possible that this problem is even more general: as a
> > > "workaround" I installed GentleAlarm (as it is supported in 3rdParty)
> > > but the events for this don't work either.
>
> > [I assume you have the latest Tasker version]
>
> Hope the Android Market updated me to the latest: 1.1u2m
>

> > The code for GentleAlarmis completely different.  Are you sure you

> > have version 3+ of GentleAlarm?
>
> 3.3.2
>
> But when preparing a log it suddenly triggered. I believe this was a
> new profile where instead of Type "Main" (which I believe is the
> default) I set the Type to "Any". But I'm not sure because both

> profiles for GentleAlarmwere active and I'm not sure which one
> triggered.

Sorry to have bothered you about this. Last Time I tried it
GentleAlarm didn't trigger anything, but now it does. But that was two
weeks ago. I suspect that either there was an update in-between or
that a reboot fixed this

The problem with the built-in alarms persists

Bernhard

[Apertotes]

Samsung Galaxy S3, "Alarm done" profile does not work with the built-in alarm/clock app.