Just guessing, but based on method names it looks like the main activity loop is starting the Activity.
On Dec 24, 2:49 pm, Frank Weiss <[email protected]> wrote: > I've had similar issues. In my case, it was a result of trying to manipulate > the UI from the wrong thread. Once I used AsyncTask correctly, the > exceptions went away. > > On Dec 24, 2009 1:44 PM, "jotobjects" <[email protected]> wrote: > > Usually there is a "caused by" line futher down in the stack trace. > Is this the entire stack trace? > > On Dec 24, 6:36 am, Martin <[email protected]> wrote: > Hi! > > What > could be the reason, if I... -- 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
