bschuhma wrote: > Would this most easily be accomplished by publishing high priority > intents to handle everything, then just not handling them?
I am assuming you meant: "Would this most easily be accomplished by publishing high priority broadcast receivers to handle everything, then just aborting the broadcasts?" If my interpretation is correct, then the answer is no. For example, you can't prevent activities from starting or prevent services from running via this technique. More importantly, many broadcasts are not ordered, and so are not abortable. > I guess > I'm asking if this is a complex thing or whether there's a simple two- > line solution to this before I go down the rat hole of figuring out > the 32 different things I need to change to make this happen. I sincerely hope that it is an impossible thing for a plain Android SDK application to to. While you say your intentions are good, if this *is* possible, then those with ill intentions will do the same thing. Android 2.2 has device administration capabilities (e.g., remote wipe), which may be better suited to your scenario. If you feel those capabilities are insufficient, you are welcome to propose and help implement modifications to Android itself that cover your scenario via the device administration framework. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- 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
