Sorry but I still need clarification here. This new 1.6 feature distinguishes between foreground and background and would seem to alter thread priorities based on that characteristic despite all priorities being normal.
Assume that when the broadcast receiver is called, another application might have the "UI Thread" by running an interactive window with the Android end user. In this case, does onReceive run in the foreground or background? Dianne made clear that the System Service is not starved and the broadcast is sent. It still looks to me like the resulting broadcast receiver may not be getting the CPU. Is there any way to defensively code for this situation? Regards, Beth On Oct 30, 2009 11:03 AM, "Mark Murphy" <mmur...@commonsware.com> wrote: Beth Mezias wrote: > OK, but my application is not running at the time. Sure it is. If your code runs, your application is running. > Does that mean it > goes into the foreground thread pool even if there is no window? Unless specifically documented, all threads in Android are normal priority. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Program... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
