Thread's should never be started in a BroadcastReceiver because the containg task ends when the onReceive method ends.
The suggestion at http://developer.android.com/guide/practices/design/responsiveness.html is; "But instead of doing intensive tasks via child threads (as the life of a BroadcastReceiver is short), your application should start a Service <http://developer.android.com/reference/android/app/Service.html> if a potentially long running action needs to be taken in response to an Intent broadcast." Just as Jon has done. Al http://andappstore.com/ Jon Colverson wrote: > I don't think it's valid to start a Thread in a BroadcastReceiver. The > system doesn't know anything about that thread, so it wouldn't know > that it's supposed to keep the process hosting it around. My app > nanoTweeter does similar background polling and I acquire the WakeLock > in the BroadcastReceiver and then start a Service. That service > releases the lock when it's done. > > -- > Jon > > > > -- * Written an Android App? - List it at http://andappstore.com/ * ====== Funky Android Limited is registered in England & Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
