I have spent a lot of time playing and researching (including subscribing to the Mark Murphy¹s CommonsGuy stuff...excellent by the way) and I think I have enough info to be dangerous. I am just having issues coming up with best practices for doing what I need to do.
My app is collecting specially formatted incoming SMS messages (currently default port but will later be processing port-directed using Verizon proprietary header info). I also need a UI application that will view the current messages that have been received and allow the user to read/delete/reply. All this stuff is working at this point but I just need to make sure it keeps itself running at all times (or will always be available when needed at least). My initial thoughts were to have a service which starts at boot handle the sms messaging (in and out) and incorporate a content provider in it to provide access to the collection of messages (Sqlite) to other applications requiring it. I tried launching the service from an activity but if someone uses a task killer to kill the activity it seems to take the service down with it. I tried having a service that runs at boot but had trouble getting it to launch an activity when a new message arrives (probably my issue). So, after floundering back and forth with my indecisions of how best to architect it, I figured I would ask around to get some suggestions and then attack it from there. So, any ideas from anyone? Thanks, Carl -- 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
