well you could Thread.currentThread().sleep(period) #hack :-)
>So, your saying use something like a wait(); statement? >Since I really don't do much before running the activity, all is done >in services before hand.... > > >On Sep 11, 2:49 pm, Jason Proctor <[email protected]> >wrote: >> "officially", you can't replace the stock call UI. however, i've >> discovered that if your receiver hangs out for a bit before starting >> your UI activity, then you can displace the stock UI. it's quite >> funny, you see the system obligingly slide the stock one out of the >> way and bring in the new one. and the hot keys for pickup etc still >> work. heehee, score. >> >> i put all my networking etc in the receiver, then launch the UI >> activity when all is sorted. that turns out to be long enough... :-) >> >> it's not *too* reliable though, and i'm sure the Googs would frown on >> this practice... >> >> hth >> >> >My broadcast receiver for Call_State_Changed works fine and I >> >successfully start a different activity than the standard CallLog >> >after a call, but every once in a while, the original Activity gets >> >displayed after mine, in effect not showing mine! >> >This is annoying. >> >Is there a call that I can make to turn off the default Broadcast >> >receiver for Call_State_Changed, or what can I do to stop this? >> >Thanks in advance. >> >> -- >> jason.vp.engineering.particle > -- jason.vp.engineering.particle --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
