Samsung Alarm Label recognition

Bryce Anderson

unread,

Feb 14, 2011, 4:39:15 PM2/14/11

to Tasker

I have Samsung SCH-I500 (Verizon Fascinate) and I'm trying to use an
alarm context to trigger a random song to play. It works fine for all
alarms, but if I try to specify an alarm label ("Tasker Music"), the
context fails to activate.

Am I doing something wrong here?

Here is the pertinent section of a log:

14-02-2011 ReceiverDynamic: 15.20.00#ReceiverDynamic: onReceive: pID:
42 action: com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT
14-02-2011 WakeLockManager: 15.20.00#WakeLockManager: acquired lock
for M autorelease: true warn: true
14-02-2011 ReceiverDynamic: 15.20.00#ReceiverDynamic: onReceive: pID:
42 done
14-02-2011 M: 15.20.00#M: pi: time since last process end: 6315, reset
qcpt
14-02-2011 M: 15.20.00#M: process inbox, size 0 startID: 271
14-02-2011 M: 15.20.00#M: extra: eventAct:
com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT
14-02-2011 M: 15.20.00#M: extra: eventConID: 42
14-02-2011 M: 15.20.00#M: extra: eventType: 9996
14-02-2011 M: 15.20.00#M: extra: eventExt:
Bundle[mParcelledData.dataSize=440]
14-02-2011 M: 15.20.00#M: B android.intent.extra.ALARM_COUNT: 1
14-02-2011 M: 15.20.00#M: B
com.samsung.sec.android.clockpackage.alarm.ALARM_DATA: [B@47cf4dc0
14-02-2011 M: 15.20.00#M: handleAlarmEvent: no alarm data and no label
extra
14-02-2011 TaskerContext: 15.20.00#TaskerContext: arg no 0
matchString: Tasker Music
14-02-2011 TaskerContext: 15.20.00#TaskerContext: STRING MATCH: Tasker
Music OCC:
14-02-2011 TaskerContext: 15.20.00#TaskerContext: not active, break
14-02-2011 TaskerContext: 15.20.00#TaskerContext: active: false
14-02-2011 M: 15.20.00#M: this item ptime: 115 qcpt now 115
14-02-2011 WakeLockManager: 15.20.00#WakeLockManager: release: M

Pent

unread,

Feb 15, 2011, 3:55:40 PM2/15/11

to Tasker

> I have Samsung SCH-I500 (Verizon Fascinate) and I'm trying to use an
> alarm context to trigger a random song to play. It works fine for all
> alarms, but if I try to specify an alarm label ("Tasker Music"), the
> context fails to activate.

They've changed the format of the alarm data that's broadcast so that
Tasker doesn't see the label. I can try to pick up the new one, but I
don't have a device with that alarm package to experiment with, so
don't get your hopes up :-)

Pent

Bryce Anderson

unread,

Feb 16, 2011, 1:30:28 PM2/16/11

to Tasker

Thanks for the reply. I'd be happy to provide you with whatever I can
that might help fix the problem, but I understand that you've got a
lot going on. Let me know if I can help.

bdanders

unread,

Feb 25, 2011, 12:46:57 PM2/25/11

to Tasker

For anyone that might be looking for a work around for this problem,
you can easily use the notify event created by the alarm and assign
the alarm name as the notification title.

On Feb 16, 1:30 pm, Bryce Anderson <the.bryce.ander...@gmail.com>
wrote:

> > Pent- Hide quoted text -
>
> - Show quoted text -

Glen

unread,

Aug 19, 2014, 12:53:44 AM8/19/14

to tas...@googlegroups.com

Just wondering, how did you make it recognize the samsung alarm label?

Reply all

Reply to author

Forward