On Fri, Jun 10, 2011 at 4:18 PM, Matt Quigley <[email protected]> wrote: > I think we're coming to the conclusion that there is nothing that > should be done about the occasional random ANR in a broadcast receiver > that takes at most 100 ms and has 10,000 ms to complete. It's > randomness. I suspect that the Android platform is simply architected > in a way to where it is expected that .1% of users monthly to > experience ANRs without the application doing anything wrong. I > suppose that's what you get when you have an OS using garbage > collection.*
AFAIK, the users won't "experience" the ANRs. BroadcastReceivers are just silently terminated, last I checked. They may experience whatever loss of functionality occurs when the receiver is terminated, though. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 3.0 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
