On Mon, Mar 15, 2010 at 3:34 PM, Mark Murphy <mmur...@commonsware.com>wrote:
> Hmmmm...the upshot of this is that pretty much anything using > AlarmManager for scheduled operations will, at least briefly, steal CPU > time from foreground operations. If the alarm routes to an > IntentService, the "heavy lifting" will still be done at low priority. > But, those who elect to implement more smarts directly in the > BroadcastReceiver will run at foreground priority for that work. > Very true, though applications are strongly encouraged to keep the work done as a result of receiving a broadcast short and focused, and this is semi-enforced through the timeout (currently 10 seconds) until the system gives up on the app finishing. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
