Josh wrote: > I can have a program start up on boot Yes, you can have a program start up on boot. That's OK if you are using it to schedule tasks via AlarmManager or something. Trying to have something run forever is not a good design move:
http://www.androidguys.com/2009/09/09/diamonds-are-forever-services-are-not/ > then begin a background thread You cannot just have a random thread floating around the ether. It needs to be associated with some component (usually an activity or service). > that will listen to certain system events and when those events happen > I could send a notification alert Most "system events" are broadcast Intents. You do not need to have anything start at boot or have any long-running threads for that. Just set up BroadcastReceivers, registered in your manifest, that will get control on those events and register Notifications. > (actually, would really like to pop > a dialog box or some other view up over what is currently showing on > the phone's display) If you do that, users will attempt to perform anatomically inappropriate things to you. Users really dislike being interrupted in the middle of their game, phone call, text message, browsing, etc. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.6 Available! -- 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
