Interesting idea... So if I understand correctly, you suggest: 1. From the phone state receiver I'll start a service 2. The service will register a content observer 3. When the content observer calls back I'll stop the service
Couple of questions re this idea: - I'll have to check in (1) and in (2) if the new calls are already in the call log to avoid a race condition, right? - Is there a difference if I register a content observer from the service or from the code that starts the service? If I understand correctly the only purpose of the service is to reduce the chance of Android killing the app, so where I register the content observer makes no difference. - Do you think I should still implement a timer and stop the service after the timer expires? The way I see it there's no guarantee that the content observer will hold all the calls on the first call back, so my only choice is to give it some time and see that there's no more callbacks... I appreciate your help - from my experience, these delicate matters make the difference between a piece of software that works 80% of the time than a piece of software that works 99% of the time (and that 1% is really out of our hands - someone should name it like any other physical constant :) Tal -- 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
