Android intent-filter SET_ALARM no longer works?

Asked May 25 '16 at 15:21

Active Jun 22 '16 at 00:08

Viewed 261 times

Until recently, this manifest declaration allowed my app to be listed as provider for alarms in response to voice commands (i.e. "set timer for 5 minutes"):

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.SET_ALARM"/>
        <category android:name="android.intent.category.DEFAULT"/>
    </intent-filter>
</activity>

As explained here: System Voice Actions

After Google I/O 2016, without notice, only Google's default Clock (deskclock) is listed. It's impossible to unset it from being default, and tapping the "more" button show deskclock as the only option to choose from.
But when disabling it, other timers are listed as before. It looks like Google did something to mandate deskclock if available, and allow other timers only if it's not available.

(I used different voice command, but the effect is the same)

logcat doesn't reveal the cause, but just the effect:

ActivityManager: START u0 {act=android.intent.action.SET_TIMER pkg=com.google.android.deskclock cmp=com.google.android.deskclock/com.android.deskclock.HandleApiCalls (has extras)} from uid 10024 on display 0

I couldn't find any mention for such change, no bug report so far.

Any information or work around would be appreciated.

edited Jun 22 '16 at 00:08

Avi K.

1,734
2
18
28

asked May 25 '16 at 15:21

Amir Uval

14,425
4
50
74

Same to me. I have discovered this today. Any solution yet? – chrisonline May 25 '16 at 19:28
@chrisonline nothing so far AFAIK... I hope it's a bug and not intentional – Amir Uval May 25 '16 at 21:36
@chrisonline someone has opened an issue for this: https://code.google.com/p/android/issues/detail?id=212326 – Amir Uval Jun 07 '16 at 08:39
Great, thanks for the info. – chrisonline Jun 07 '16 at 09:12

Android intent-filter SET_ALARM no longer works?

0 Answers0