Broadcast Timeout when ResolverActivity is to be launched
694 views
Skip to first unread message
Gary Wang
unread,
Apr 14, 2011, 2:14:05 AM4/14/11
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to android-platform
Dear Experts,
I always met the following process system ANR when launching
ResolverActivity (due to multiple Launcher). When I remove all
launchers expert default one (i.e. ResolveActivity is not to be
displayed). All work are done well.
I know the broadcast timeout is not the root cause (sometime the ANR
is happened on ImageWallpaper for BOOT_COMPLETED action).
Can everyone give any advices for my reference?
Thanks!
Gary
04-14 05:54:46.156 912 940 W WindowManager: Window freeze timeout
expired.
04-14 05:54:46.156 912 940 W WindowManager: Force clearing
orientation change: Window{483ef9b8 StatusBar paused=false}
04-14 05:54:46.166 912 940 V WindowManager: Layout:
mDisplayFrozen=true holdScreen=null
04-14 05:54:49.156 912 940 W WindowManager: App freeze timeout
expired.
04-14 05:54:49.156 912 940 W WindowManager: Force clearing freeze:
AppWindowToken{48447e78 token=HistoryRecord{48446ef0 android/
com.android.internal.app.ResolverActivity}}
...
04-14 05:54:53.996 912 918 V ActivityManager: Finish receiver:
android.os.BinderProxy@48446c70
04-14 05:54:54.007 912 918 V ActivityManager:
processNextBroadcast: 0 broadcasts, 1 ordered broadcasts
04-14 05:54:54.007 912 918 V ActivityManager: Delivering to
component ComponentInfo{android/com.android.server.BootReceiver}:
BroadcastRecord{484c3e60 android.intent.action.BOOT_COMPLETED}
04-14 05:54:59.996 912 939 V ActivityManager: Broadcast: Intent
{ act=android.intent.action.TIME_TICK flg=0x40000004 (has extras) }
ordered=true
04-14 05:54:59.996 912 939 V ActivityManager: Enqueing broadcast:
android.intent.action.TIME_TICK replacePending=false
04-14 05:54:59.996 912 939 V ActivityManager: Enqueueing ordered
broadcast BroadcastRecord{484b2f60 android.intent.action.TIME_TICK}:
prev had 1
04-14 05:54:59.996 912 939 I ActivityManager: Enqueueing broadcast
android.intent.action.TIME_TICK seq=-1
04-14 05:54:59.996 912 939 V ActivityManager: Schedule broadcasts:
current=false
04-14 05:54:59.996 912 928 V ActivityManager: Received
BROADCAST_INTENT_MSG
04-14 05:54:59.996 912 928 V ActivityManager:
processNextBroadcast: 0 broadcasts, 2 ordered broadcasts
04-14 05:54:59.996 912 928 D ActivityManager:
processNextBroadcast() called when not idle (state=1)
04-14 05:55:03.986 912 928 V ActivityManager: Premature timeout @
33750: resetting BROADCAST_TIMEOUT_MSG for 33770
04-14 05:55:04.006 912 928 I Process : Sending signal. PID: 912
SIG: 3
04-14 05:55:04.006 912 914 I dalvikvm: threadid=3: reacting to
signal 3
04-14 05:55:04.006 912 928 W ActivityManager: Timeout of broadcast
BroadcastRecord{484c3e60 android.intent.action.BOOT_COMPLETED} -
receiver=android.app.ActivityThread$ApplicationThread@48362ac8
04-14 05:55:04.006 912 928 W ActivityManager: Receiver during
timeout: ResolveInfo{484ea818 com.android.server.BootReceiver p=0 o=0
m=0x108000}
04-14 05:55:04.006 912 928 V ActivityManager: Schedule broadcasts:
current=false
04-14 05:55:04.036 912 914 I dalvikvm: Wrote stack traces to '/
data/anr/traces.txt'
...