Android AlarmClock ACTION_SET_ALARM intent produces exception

Question

The given example produces an Exception (android.content.ActivityNotFoundException: No Activity found to handle Intent)

Intent i = new Intent(AlarmClock.ACTION_SET_ALARM); 
i.putExtra(AlarmClock.EXTRA_MESSAGE, "New Alarm"); 
i.putExtra(AlarmClock.EXTRA_HOUR, hours); 
i.putExtra(AlarmClock.EXTRA_MINUTES, mins); 
startActivity(i);

on my SGS2 Android Version 2.3.3. Do you have any ideas, what can be going wrong? An another intent request (e.g. selecting a contact from the address book) works fine.

Thank you, Artjom

Look at this question [Android AlarmClock causing force close](http://stackoverflow.com/questions/8571768/android-alarmclock-causing-force-close/8571916#8571916), I think its same as yours, and Also look at the answer, is it solved your problem? If that answer solved your problem then please let me know.. — user370305, Dec 20 '11 at 09:17

score 9 · Answer 1 · answered Jul 16 '12 at 11:27

9

You need to set permission in manifest file also.

<uses-permission android:name="com.android.alarm.permission.SET_ALARM"/>

answered Jul 16 '12 at 11:27

Manshi

111
1
2

score 5 · Accepted Answer · answered Sep 05 '11 at 11:17

5

Do you have any ideas, what can be going wrong?

The device does not support that activity. This is not unheard of. Either catch the exception and let the user know, or use PackageManager and queryIntentActivities() to see if anything will respond to your Intent in advance of calling startActivity().

answered Sep 05 '11 at 11:17

CommonsWare

986,068
189
2,389
2,491

Is this is a vendor specific behavior? The same activities can also work with some devices and do not with other? – artkoenig Sep 05 '11 at 13:24

Android AlarmClock ACTION_SET_ALARM intent produces exception

2 Answers2

Linked