If it didn't run, there is likely a message in the log at the point it tried to executing saying what happened.
Also ApiDemos has examples of using the alarm manager, which use an intent specifying an explicit component to launch. And you could look at the DeskClock app to see how the platform's alarm clock works. On Mon, Nov 1, 2010 at 1:28 PM, Anil Philip <[email protected]> wrote: > >> Anyway, I am not able to get the alert happen with explicitly > >> specifying the component. > > > > You failed to make your inner class be static. You cannot reference > > non-static inner classes in the manifest, because Android has no way > > of creating an instance of that non-static inner class. > > > I made it static. That did not work - the alarm is not delivered > though it is being run. > adb shell dumpsys alarm > com.iovercomer > 22ms running, 2 wakeups > 2 alarms: dat=content://com.iovercomer/alerts/99 flg=0x4 > cmp=com.iovercomer/.TestIntentResolution$MyAlarmReceiver > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
