It always helps to give an explicit example of a Google query he could have used to answer his question. I found the answer in the top item listed after searching google with "android developer anr", which is titled "Design for responsiveness" and says:
"Generally, the system displays an ANR if an application cannot respond to user input. ... In both of these cases, the recommended approach is to create a child thread and do most of your work there." It is almost certain that that is the right answer for his problem. If not, then he should still read the rest of the article -- as well as look for what platform methods he might be using that are running on the main UI thread when they should not be... On Jun 23, 8:39 am, TreKing <treking...@gmail.com> wrote: > On Thu, Jun 23, 2011 at 7:01 AM, Sapna Srivastav > <sapna.ari...@gmail.com>wrote: > > > Please tell me in which condition an application goes in ANR state and how > > can I avoid this state? > > Please check the documentation for stuff like > this.http://developer.android.com/guide/practices/design/responsiveness.html > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
