I compare the logcat to the success one,and find the point
the success logcat
________________________________________________________________________
I/ActivityManager( 558): Displayed activity android/
com.android.internal.app.ResolverActivity: 6361 ms (total 6361 ms)
________________________________________________________________________
my logcat
_____________________________________________________________________
W/ActivityManager( 1840): Activity idle timeout for
HistoryRecord{2e7faa70 android/
com.android.internal.app.ResolverActivity}
W/ActivityManager( 1840): Timeout of broadcast
BroadcastRecord{2e9996e0 android.intent.action.SCREEN_ON} -
receiver=android.app.ActivityThread$PackageInfo$ReceiverDispatcher
$innerrecei...@2e9cf498
W/ActivityManager( 1840): Receiver during timeout:
BroadcastFilter{2e97f6b0 ReceiverList{2e9a83e0 1840 system/1000 local:
2e9cf498}}
______________________________________________________________________
jordan wrote:
> yes，it is the point.
> but I lmost use the source code entirely, there isn't my own app.
> it seem to be happen when the launcher start.Do some apps in the
> launcher cause it?
> Do I need to edit the launcher source code? or disable some service?
>
>
> fadden wrote:
> > On Jun 4, 3:10 am, jordan <lulujor...@126.com> wrote:
> > > hi,everybody,I have some problem when porting eclair to my hareware.it
> > > seem to be ANR error,but i have not solution for it.can you give me
> > > some advise.thanks at all.
> > ...
> > > I/Process ( 1813): Sending signal. PID: 1813 SIG: 3
> > > I/dalvikvm( 1813): threadid=7: reacting to signal 3
> > > W/dalvikvm( 1813): threadid=7: spin on suspend #0 threadid=17
> > > (h=1640360)
> > ...
> > > W/dalvikvm( 1813): threadid=7: spin on suspend resolved in 2317 msec
> > > I/dalvikvm( 1813): Wrote stack trace to '/data/anr/traces.txt'
> >
> > You didn't include the ANR portion, just the spin-on-suspend that
> > resulted. "Spin on suspend" means it took 2.3 seconds for the VM to
> > fully suspend itself in order to take a snapshot of the running
> > threads and deposit it in /data/anr/traces.txt.
> >
> > The interesting bit would be why the system was inspired to generate
> > that thread snapshot in the first place. Presumably it was running
> > slow and the Application Not Responding detector fired?
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
