First off, thanks Mark and Dianne for trying to help with this. Now, on to the meat:
I tried it with startForeground, and now it works: so it must be something to do with the service life cycle. This isn't something I'd really like to have to do, because as I've mentioned it doesn't need to be front of mind to the user at all times, it just needs to passively sit in the background and be restarted once it's killed: it's not mission critical. This used to happen before, but now it isn't. When I have a chunk of time where I can hook my phone up to gather logs for a while, I will turn off the startForeground thing and see if anything interesting pops up in the logs when the service is killed. -- 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
