On Wed, Aug 11, 2010 at 8:36 AM, William Ferguson <[email protected]> wrote: > Ahh, thanks Marc. I have been using Intent.ACTION_NEW_OUTGOING_CALL to > determine if an outgoing call was being placed. > I wasn't aware of the TelephonyManager.ACTION_PHONE_STATE_CHANGED > Intent. > Won't it fire for both incoming and outgoing calls? > Seems strange the 2 Intents are not co-located.
The ways of the core Android team are mysterious... :-) > But assuming I want some action to occur during the lifetime of a > phone call. > What's the best way of ensuring it isn't killed by the system? > If I start a service, which monitors the call, I can't guarantee it > won't be killed. Pray to the deity of your choice. Or use startForeground(). Or bank on the fact that the phone call is unlikely to be long (i.e., hours) and that it won't be a problem. The best answer, in many ways, is to figure out how to solve the business problem without needing "some action to occur during the lifetime of a phone call". -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 2.2 Programming 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
