That was not much help as I don't see any stacktrace.
Are you passing the right context when you create the dialog, when you say it doesn't show up ? like so ... new ProgressDialog(YourActivity.this); Also you cannot touch any UI components in threads except the main UI thread or the Handlers, which might explain the force close. Please refer the docs for more info at : http://developer.android.com/guide/topics/ui/dialogs.html#ProgressDialog On Dec 27, 10:10 pm, andrew android <[email protected]> wrote: > Here is the logCat from one method I have tried - using basic thread > with progressdialog: > 12-27 11:07:46.365: INFO/ApplicationChangeReceiverAbc(5537): > com.hawkmoon.locabot.alpha added > 12-27 11:07:46.443: INFO/ApplicationChangeReceiverAbc(5537): > com.hawkmoon.locabot.alpha disable 1 > 12-27 11:07:46.764: INFO/ActivityManager(1018): Process com.svox.pico > (pid 5532) has died. > 12-27 11:07:47.021: INFO/Process(5503): Sending signal. PID: 5503 SIG: > 9 > 12-27 11:07:47.041: INFO/ActivityManager(1018): Process > com.android.vending (pid 5524) has died. > 12-27 11:07:47.053: INFO/WindowManager(1018): WIN DEATH: Window > {448c7438 Please wait... paused=false} > 12-27 11:07:47.053: INFO/ActivityManager(1018): Process > com.hawkmoon.locabot.alpha (pid 5503) has died. > 12-27 11:07:47.060: WARN/UsageStats(1018): Unexpected resume of > com.android.browser while already resumed in > com.hawkmoon.locabot.alpha > 12-27 11:07:47.068: ERROR/JavaBinder(1018): !!! FAILED BINDER > TRANSACTION !!! > 12-27 11:07:47.146: DEBUG/dalvikvm(5537): GC freed 774 objects / 66528 > bytes in 273ms > 12-27 11:07:47.287: WARN/InputManagerService(1018): Window already > focused, ignoring focus gain of: > com.android.internal.view.iinputmethodclient$stub$pr...@4467cf08 > 12-27 11:07:47.357: DEBUG/dalvikvm(5537): GC freed 312 objects / 17904 > bytes in 94ms > 12-27 11:07:47.381: INFO/ActivityManager(1018): Start proc > jp.benishouga.clipstore:remote for broadcast > jp.benishouga.clipstore/.ClipboardObserver: pid=5544 uid=10061 gids= > {1015} > 12-27 11:07:47.412: INFO/dalvikvm(5544): Debugger thread not active, > ignoring DDM send (t=0x41504e4d l=38) > > On Dec 26, 12:58 am, Chander Pechetty <[email protected]> wrote: > > > post your stack trace on force close ... > > > On Dec 25, 11:41 pm, Wayne Wenthin <[email protected]> wrote: > > > > When you find out let me know. I've had no luck either. > > > > On Fri, Dec 25, 2009 at 6:50 > > > AM,andrewandroid<[email protected]>wrote: > > > > > ProgressDialog during location tasks either won't show or force closes > > > > - I have tried everything! > > > > > I now have it in a Handler with a full 1 second delay (one method > > > > another post suggested) but it doesn't show. I simply am stuck. > > > > Threads are usually force closing when I use those methods. > > > > > What other tricks are there for this? > > > > > Thanks! > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "AndroidDevelopers" group. > > > > To post to this group, send email [email protected] > > > > To unsubscribe from this group, send email to > > > >[email protected]<android-developers%2bunsubs[email protected]> > > > > For more options, visit this group at > > > >http://groups.google.com/group/android-developers?hl=en > > > > -- > > > Writing code is one of few things > > > that teaches me I don't know everything. > > > > Join the Closed Beta of Call Girl > > > Managerhttp://www.fuligin.com/forums-Hide quoted text - > > > - Show quoted text - -- 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
