It's time for my own question about this API, that I think some people here refer to as a "nuclear bomb" =)
Yes, I'm an author of a "task killer" app, and for months it has seemed to work out OK - the process is killed, and doesn't restart the activity. Lately, however, I have started getting complaints about my app "randomly starting other apps". I don't get very many returns so this has led me to the hypothesis that this is carrier / hardware specific. This is a mystery to me since all my app essentially does is call restartPackage(). Two thoughts: 1) Is it possible that some carrier build out there has changed the functionality of this method to *actually* restart the package after it's process is killed? 2) I haven't tested with a SenseUI phone - I'm thinking there might be a situation where my app is killing a process that is shared by their SenseUI business or something, which is then relaunched on TIME_TICK or TIMEZONE_CHANGED or something. (similar behavior to myFaves on the G1). For example, their Facebook UI might share com.android.mms? Can anyone confirm this? /braces for the coming assault. -- 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
