Hi George Are you using the Acelerometer? If so are you using the one from the MonoGame repo or have you implemented your own android specific one?
Dean On Thu, Apr 25, 2013 at 3:30 PM, George Banfill (Linknode Ltd) < [email protected]> wrote: > Thanks for the suggestions, > > Paul: > Not doing anything external, no network requests ongoing. However the > Rotation_Vector sensor is active (see below) > > Dean: > I copied the logcat log to my machine, first run not useful, second run > gave me a SIGILL from the SensorService. > > F/libc ( 393): Fatal signal 4 (SIGILL) at 0x70da0d10 (code=1), thread > 407 (SensorService) > I/DEBUG ( 125): *** *** *** *** *** *** *** *** *** *** *** *** *** *** > *** *** > I/DEBUG ( 125): Build fingerprint: > 'google/mantaray/manta:4.2.2/JDQ39/573038:user/release-keys' > I/DEBUG ( 125): Revision: '8' > I/DEBUG ( 125): pid: 393, tid: 407, name: SensorService >>> > system_server <<< > I/DEBUG ( 125): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr > 70da0d10 > I/DEBUG ( 125): r0 0000000c r1 00000000 r2 725891f0 r3 00000003 > I/DEBUG ( 125): r4 70aca5a8 r5 71e62068 r6 00000000 r7 726b6008 > I/DEBUG ( 125): r8 726b6008 r9 00000010 sl 00000001 fp 726b31ec > I/DEBUG ( 125): ip 72577f60 sp 726b31d8 lr 7257df90 pc 70da0d10 > cpsr 20000010 > I/DEBUG ( 125): d0 0000000000000001 d1 0000000000000000 > I/DEBUG ( 125): d2 00000000000000f0 d3 00000000000000ff > I/DEBUG ( 125): d4 000000003d52557f d5 0000000000000000 > I/DEBUG ( 125): d6 0000000000000000 d7 0000000000000000 > I/DEBUG ( 125): d8 0000000000000000 d9 0000000000000000 > I/DEBUG ( 125): d10 0000000000000000 d11 0000000000000000 > I/DEBUG ( 125): d12 0000000000000000 d13 0000000000000000 > I/DEBUG ( 125): d14 0000000000000000 d15 0000000000000000 > I/DEBUG ( 125): d16 000001a7d9acf79f d17 000001a7cb89c1b7 > I/DEBUG ( 125): d18 000000000e2335e8 d19 3f6cfbf50f863526 > I/DEBUG ( 125): d20 3fc9a5bea64b73cc d21 40000d539f42569b > I/DEBUG ( 125): d22 bfd4910a73fa94d4 d23 3fd2a06af20626dd > I/DEBUG ( 125): d24 c002e3bec7ec4fcc d25 3fc477ea5a08f90f > I/DEBUG ( 125): d26 3e35e09c00000000 d27 0000002f0000002f > I/DEBUG ( 125): d28 0001000000010000 d29 0001000000010000 > I/DEBUG ( 125): d30 0003000000030000 d31 0003000000030000 > I/DEBUG ( 125): scr 60000090 > I/DEBUG ( 125): > I/DEBUG ( 125): backtrace: > I/DEBUG ( 125): #00 pc 0002ed10 /system/lib/libbcc.so > I/DEBUG ( 125): #01 pc 00004f8c /system/lib/libmllite.so > (inv_execute_on_data+292) > I/DEBUG ( 125): #02 pc 00005653 /system/lib/libinvensense_hal.so > (MPLSensor::executeOnData(sensors_event_t*, int)+10) > I/DEBUG ( 125): #03 pc 00001d7d > /system/lib/hw/sensors.manta.so(sensors_poll_context_t::pollEvents(sensors_event_t*, > int)+124) > I/DEBUG ( 125): #04 pc 0000e285 /system/lib/libsensorservice.so > (android::SensorDevice::poll(sensors_event_t*, unsigned int)+20) > I/DEBUG ( 125): #05 pc 0001035d /system/lib/libsensorservice.so > (android::SensorService::threadLoop()+100) > I/DEBUG ( 125): #06 pc 00011267 /system/lib/libutils.so > (android::Thread::_threadLoop(void*)+114) > I/DEBUG ( 125): #07 pc 0004679f /system/lib/libandroid_runtime.so > (android::AndroidRuntime::javaThreadShell(void*)+66) > I/DEBUG ( 125): #08 pc 00010dcd /system/lib/libutils.so > I/DEBUG ( 125): #09 pc 0000e3d8 /system/lib/libc.so > (__thread_entry+72) > I/DEBUG ( 125): #10 pc 0000dac4 /system/lib/libc.so > (pthread_create+160) > > > Any suggestions as to what this means and what I could do about it? > > George > > Date: Thu, 25 Apr 2013 11:38:03 +0100 > From: Dean Ellis <[email protected]> > To: [email protected], Discussions related to Mono for > Android <[email protected]> > Subject: Re: [mono-android] Debugging Nexus 10 reboots while app open > > George > > you can try running > > adb -d logcat > android.log > > while the device is attached via USB and just leave it running. It should > log everything to the log file then. > > Dean > > > On Thu, Apr 25, 2013 at 11:23 AM, Paul Johnson > <[email protected]>wrote: > > > Hi, > > > > > > What I need is suggestions on how to debug this as I have exhausted > > all > >> my ideas. I suspect the app is using too many resources / threads / > >> memory and this is causing Android to reboot. However I can?t prove > >> this as the logcat log is cleared on reboot, so I have no idea what > >> happened immediately before the device rebooted. > >> > > > > Is it crashing in the same place all the time or does it die when > > you're trying to (say) do a network access? > > > > Paul > > > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid >
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
