Tony, Your receiver is getting called - that's good. Can't comment on notifications without seeing the code.
There should not be any reason why startActivity from within onReceive wouldn't work (use the context object that's passed into onReceive to fix the compile error you mentioned), but I don't think your users are going to appreciate a window popping up like that. -- Kostya Vasilyev -- http://kmansoft.wordpress.com 12.09.2010 1:10 пользователь "tony obrien" <[email protected]> написал: Actually I have LOGGING all over the place. I was able to determine that the SMS Receiver is actually getting called ... but it has trouble doing the NM.Notify(); (I'm still trying to decode what *that* error is all about...) And I have Thread.sleep(lots-o'seconds) and Thread.yeild() in the runnable so I am being careful regarding your concerns. What I would REALLY like to do is a startActivity() from inside the Receiver... but I don't suppose that's possible? (In my first timid attempts to do that awhile ago I could not get it to compile, I think the "extends BroadcastReceiever" makes the compiler not understand what startActivity() means.) On Sep 11, 5:02 pm, Kostya Vasilyev <[email protected]> wrote: > 12.09.2010 0:37, tony obrien ... -- You received this message because you are subscribed to the Google Groups "Android Developers" g... -- 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
