I don't think we can count on the user automatically making this association, that using the task killer to kill an app will also kill the alarm. Sure, that is the logical thing to do, once you think about it, but of course, we cannot count on the user to think about it in that way. The user might expect the app to restart when the alarm requires it to do so -- especially if he is already somewhat mystified by how the Android system already decides to restart apps the user never asked for in the first place, such as "My Downloads";)
On Sep 10, 4:06 am, Mark Murphy <[email protected]> wrote: > 2010/9/10 Albert <[email protected]>: > > > I have all that set up. The thing is that if an user kills my app/ > > service with a task killer app, then my alarm would go away. > > If they did that, then they do not want your alarm. And, starting with > Android 2.2, they can't do this anyway. > > Hence, I would not worry much about it. Keep a log of work you do in > the alarm handler, and if the user starts your activity and you > determine, via the log, that your alarm had been stopped, restart it > and perhaps pop a dialog to tell the user the ramifications of them > having attacked you with a task killer. > > > I would like to be able to do a check about whether I have a alarm > > ready to go off at some point in the future. > > Sorry, there's no API for that. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android Training in London:http://skillsmatter.com/go/os-mobile-server -- 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
