[mono-android] Debugging Nexus 10 reboots while app open

[George Banfill (Linknode Ltd)]

HI all,

My monogame based app is causing our Nexus 10 to reboot every so often. So I 
have a few standard activities (axml layouts etc) that show the user some stuff 
/ choose some settings. Then the user can start up a 3D viewer based on 
Monogame. After a while of running the Monogame page nexus 10 device restarts. 
This could take anywhere between 5 minutes and an hour.

We also test on Nexus 7 and Samsung Note neither of which do this random reboot.

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.

Suggestions, ideas, pointers would help.
Thanks
George Banfill
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Debugging Nexus 10 reboots while app open

[Paul Johnson]

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


--
"Space," it says, "is big. Really big. You just won't believe how 
vastly, hugely, mindbogglingly big it is. I mean, you may think it's a 
long way down the road to the chemist's, but that's just peanuts to 
space, listen..."

Hitch Hikers Guide to the Galaxy, a truly remarkable book!

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Debugging Nexus 10 reboots while app open

[Dean Ellis]

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
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
>
>
> --
> "Space," it says, "is big. Really big. You just won't believe how vastly,
> hugely, mindbogglingly big it is. I mean, you may think it's a long way
> down the road to the chemist's, but that's just peanuts to space, listen..."
> Hitch Hikers Guide to the Galaxy, a truly remarkable book!
>
> __**_
> Monodroid mailing list
> Monodroid@lists.ximian.com
>
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/**mailman/listinfo/monodroid
>
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

[mono-android] error occuring after updating my android version in vs2010 while building the previous projects

[krish]

hi,
 while i was using mono for android 4.0 i m unable to deploy to real
android devices ...thats y i updated my android version to 4.6.04 as when i
open my vs2010 IDE it popups with window 

 
i just click on download and dwnloaded mono-android-4.6.04000 exe and run it
...it updated successfully to 4.6 and i reopened my solution in vs2010 and i
tried to open previous project...it giving message that plz confirm xamarin
account details and i also sign in with my account details again i went to
vs2010 i opened my previous(old) project...it is opening and when i tried to
test to deploy in emulator for this purpose i build it ,it is giving error
that:

Error   1   Unexpected error - Please fill a bug report at
http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could
not load assembly 'System.DirectoryServices, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Perhaps it doesn't exist
in the Mono for Android profile?MonoCalculator
Error   2   Unexpected error - Please fill a bug report at
http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could
not load assembly 'System.DirectoryServices, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Perhaps it doesn't exist
in the Mono for Android profile?MonoCalculator
Error   3   Unable to determine license edition.MonoCalculator
 so,it is not deploying to emulator also...




--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/error-occuring-after-updating-my-android-version-in-vs2010-while-building-the-previous-projects-tp5713209.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Debugging Nexus 10 reboots while app open

[George Banfill (Linknode Ltd)]

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 000c  r1   r2 725891f0  r3 0003
I/DEBUG   (  125): r4 70aca5a8  r5 71e62068  r6   r7 726b6008
I/DEBUG   (  125): r8 726b6008  r9 0010  sl 0001  fp 726b31ec
I/DEBUG   (  125): ip 72577f60  sp 726b31d8  lr 7257df90  pc 70da0d10  cpsr 
2010
I/DEBUG   (  125): d0  0001  d1  
I/DEBUG   (  125): d2  00f0  d3  00ff
I/DEBUG   (  125): d4  3d52557f  d5  
I/DEBUG   (  125): d6    d7  
I/DEBUG   (  125): d8    d9  
I/DEBUG   (  125): d10   d11 
I/DEBUG   (  125): d12   d13 
I/DEBUG   (  125): d14   d15 
I/DEBUG   (  125): d16 01a7d9acf79f  d17 01a7cb89c1b7
I/DEBUG   (  125): d18 0e2335e8  d19 3f6cfbf50f863526
I/DEBUG   (  125): d20 3fc9a5bea64b73cc  d21 4d539f42569b
I/DEBUG   (  125): d22 bfd4910a73fa94d4  d23 3fd2a06af20626dd
I/DEBUG   (  125): d24 c002e3bec7ec4fcc  d25 3fc477ea5a08f90f
I/DEBUG   (  125): d26 3e35e09c  d27 002f002f
I/DEBUG   (  125): d28 00010001  d29 00010001
I/DEBUG   (  125): d30 00030003  d31 00030003
I/DEBUG   (  125): scr 6090
I/DEBUG   (  125): 
I/DEBUG   (  125): backtrace:
I/DEBUG   (  125): #00  pc 0002ed10  /system/lib/libbcc.so
I/DEBUG   (  125): #01  pc 4f8c  /system/lib/libmllite.so 
(inv_execute_on_data+292)
I/DEBUG   (  125): #02  pc 5653  /system/lib/libinvensense_hal.so 
(MPLSensor::executeOnData(sensors_event_t*, int)+10)
I/DEBUG   (  125): #03  pc 1d7d  /system/lib/hw/sensors.manta.so 
(sensors_poll_context_t::pollEvents(sensors_event_t*, int)+124)
I/DEBUG   (  125): #04  pc e285  /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 e3d8  /system/lib/libc.so (__thread_entry+72)
I/DEBUG   (  125): #10  pc dac4  /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 
To: p...@all-the-johnsons.co.uk,  Discussions related to Mono for
Android 
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
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
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Debugging Nexus 10 reboots while app open

[Dean Ellis]

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) <
george.banf...@linknode.co.uk> 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 000c  r1   r2 725891f0  r3 0003
> I/DEBUG   (  125): r4 70aca5a8  r5 71e62068  r6   r7 726b6008
> I/DEBUG   (  125): r8 726b6008  r9 0010  sl 0001  fp 726b31ec
> I/DEBUG   (  125): ip 72577f60  sp 726b31d8  lr 7257df90  pc 70da0d10
>  cpsr 2010
> I/DEBUG   (  125): d0  0001  d1  
> I/DEBUG   (  125): d2  00f0  d3  00ff
> I/DEBUG   (  125): d4  3d52557f  d5  
> I/DEBUG   (  125): d6    d7  
> I/DEBUG   (  125): d8    d9  
> I/DEBUG   (  125): d10   d11 
> I/DEBUG   (  125): d12   d13 
> I/DEBUG   (  125): d14   d15 
> I/DEBUG   (  125): d16 01a7d9acf79f  d17 01a7cb89c1b7
> I/DEBUG   (  125): d18 0e2335e8  d19 3f6cfbf50f863526
> I/DEBUG   (  125): d20 3fc9a5bea64b73cc  d21 4d539f42569b
> I/DEBUG   (  125): d22 bfd4910a73fa94d4  d23 3fd2a06af20626dd
> I/DEBUG   (  125): d24 c002e3bec7ec4fcc  d25 3fc477ea5a08f90f
> I/DEBUG   (  125): d26 3e35e09c  d27 002f002f
> I/DEBUG   (  125): d28 00010001  d29 00010001
> I/DEBUG   (  125): d30 00030003  d31 00030003
> I/DEBUG   (  125): scr 6090
> I/DEBUG   (  125):
> I/DEBUG   (  125): backtrace:
> I/DEBUG   (  125): #00  pc 0002ed10  /system/lib/libbcc.so
> I/DEBUG   (  125): #01  pc 4f8c  /system/lib/libmllite.so
> (inv_execute_on_data+292)
> I/DEBUG   (  125): #02  pc 5653  /system/lib/libinvensense_hal.so
> (MPLSensor::executeOnData(sensors_event_t*, int)+10)
> I/DEBUG   (  125): #03  pc 1d7d  
> /system/lib/hw/sensors.manta.so(sensors_poll_context_t::pollEvents(sensors_event_t*,
>  int)+124)
> I/DEBUG   (  125): #04  pc e285  /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 e3d8  /system/lib/libc.so
> (__thread_entry+72)
> I/DEBUG   (  125): #10  pc dac4  /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 
> To: p...@all-the-johnsons.co.uk,  Discussions related to Mono for
> Android 
> 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
> 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
> Monodroid@lists.ximian.com
>
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/mailman/listinfo/monodroid
>
__

Re: [mono-android] Debugging Nexus 10 reboots while app open

[Jonathan Pryor]

On Apr 25, 2013, at 10:30 AM, George Banfill (Linknode Ltd) 
 wrote:
> 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

What's are processes 393 and 125? Specifically are either _your_ process?


http://docs.xamarin.com/guides/android/deployment%2C_testing%2C_and_metrics/android_debug_log#4.interesting-messages

I'm going to guess that neither are your process, which means there's not 
anything you can do about it per-se; it look like an OS bug.

Now, it's plausible that your app is doing something to trigger the OS bug, 
which means you'll need to possibly insert some trace messages, re-run, and see 
what your app is doing (if anything) before the device crashes and reboots.

 - Jon

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] error occuring after updating my android version in vs2010 while building the previous projects

[Jonathan Pryor]

On Apr 25, 2013, at 9:03 AM, krish  wrote:
> Error 1   Unexpected error - Please fill a bug report at 
> http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could 
> not load assembly 'System.DirectoryServices, Version=4.0.0.0, 
> Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Perhaps it doesn't exist 
> in the Mono for Android profile?   MonoCalculator

Your project has an assembly reference to System.DirectoryServices.dll, and 
this assembly isn't supported. Please remove the assembly reference from your 
project and rebuild.

 - Jon

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Debugging Nexus 10 reboots while app open

[George Banfill (Linknode Ltd)]

Hi Dean,

No I am not using the accelerometer or the Monogame wrapper around it. I have 
written my own:

defaultRotationVectorSensor = 
sensorManager.GetDefaultSensor(SensorType.RotationVector);
sensorManager.RegisterListener(_watcher, defaultRotationVectorSensor, 
SensorDelay.Fastest);

I have tried fiddling with the SensorDelay value, but still the same result 
(just a  more jerky experience whilst using the app). I have also added the 
exception handling in the same way as there is the monogame code, but that 
doesn't catch it.

George

Date: Thu, 25 Apr 2013 15:38:35 +0100
From: Dean Ellis 
To: Discussions related to Mono for Android

Subject: Re: [mono-android] Debugging Nexus 10 reboots while app open
Message-ID:

Content-Type: text/plain; charset="iso-8859-1"

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) < 
george.banf...@linknode.co.uk> 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.
>


___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Debugging Nexus 10 reboots while app open

[Dean Ellis]

hi George

I assume you are disposing of the rotation vector values you get back from
the Sensor, like we do in the MonoGame accelerometer as that did produce a
memory leak that exibited similar behaviour.

Dean


On Thu, Apr 25, 2013 at 5:03 PM, George Banfill (Linknode Ltd) <
george.banf...@linknode.co.uk> wrote:

> Hi Dean,
>
> No I am not using the accelerometer or the Monogame wrapper around it. I
> have written my own:
>
> defaultRotationVectorSensor =
> sensorManager.GetDefaultSensor(SensorType.RotationVector);
> sensorManager.RegisterListener(_watcher, defaultRotationVectorSensor,
> SensorDelay.Fastest);
>
> I have tried fiddling with the SensorDelay value, but still the same
> result (just a  more jerky experience whilst using the app). I have also
> added the exception handling in the same way as there is the monogame code,
> but that doesn't catch it.
>
> George
>
> Date: Thu, 25 Apr 2013 15:38:35 +0100
> From: Dean Ellis 
> To: Discussions related to Mono for Android
> 
> Subject: Re: [mono-android] Debugging Nexus 10 reboots while app open
> Message-ID:
>  k0vsihm1...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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) <
> george.banf...@linknode.co.uk> 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.
> >
>
>
> ___
> Monodroid mailing list
> Monodroid@lists.ximian.com
>
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/mailman/listinfo/monodroid
>
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] Debugging Nexus 10 reboots while app open

[George Banfill (Linknode Ltd)]

Your correct, my process is 1747. Don't have the full log any more (just the 
relevant bits to this crash).

I've also set a simple app to run the rotation_vector sensor and display the 
results to see if it is running the sensor that is doing it or if it is 
something coming from running in monogame (memory leak, starting too many 
threads etc) and this crash only happens when something is resource starved.

George

On Thu, 25 Apr 2013 11:42:35, Jonathan Pryor  wrote:

On Apr 25, 2013, at 10:30 AM, George Banfill (Linknode Ltd) 
 wrote:
> 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

What's are processes 393 and 125? Specifically are either _your_ process?


http://docs.xamarin.com/guides/android/deployment%2C_testing%2C_and_metrics/android_debug_log#4.interesting-messages

I'm going to guess that neither are your process, which means there's not 
anything you can do about it per-se; it look like an OS bug.

Now, it's plausible that your app is doing something to trigger the OS bug, 
which means you'll need to possibly insert some trace messages, re-run, and see 
what your app is doing (if anything) before the device crashes and reboots.

 - Jon



___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] HttpWebRequest freezing when turning off screen

[Jonathan Pryor]

On Apr 22, 2013, at 8:52 AM, Stephan Steiner  wrote:
> I'm wondering - is there any setting that I should use to ensure that the 
> phones will keep the Wifi active while I have an ongoing HttpWebRequest?


http://stackoverflow.com/questions/3871824/how-do-i-keep-wifi-from-disconnecting-when-phone-is-asleep

 - Jon

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Re: [mono-android] SIGSEGV on global::Java.Lang.Object.GetObject<>

[Jonathan Pryor]

This thread has moved to the forums:


http://forums.xamarin.com/discussion/3473/sigsegv-on-globaljava-lang-object-getobject

 - Jon

On Apr 16, 2013, at 11:34 PM, baramuse  wrote:

> Hi,
> 
> I'm struggling with using a third party JNI library.
> I've managed to build the BindingLibrary project, use the just-built library
> in my Monodroid app, call some methods etc, basically it's working..
> 
> BUT now i'm facing more vicious crashes inside my app.
> 
> Basically, the library is a video player.
> when I play videos, i get some events. 
> Some of them just work fine, but "sometimes" it just crashes the app with a
> SIGSEGV.
> 
> here is the stack trace :
> 
> 
> as soon as this method (inside the generate source for the BindingLibrary)
> is called :
> 
> 
> 
> Am I facing a threading issue ? an object disposed ?
> I'm really in the dark here, can't figure out what's happening or even how
> to understand what's happening...
> 
> Thanks a lot to anyone with any advice on that.
> 
> Regards.
> 
> 
> 
> --
> View this message in context: 
> http://mono-for-android.1047100.n5.nabble.com/SIGSEGV-on-global-Java-Lang-Object-GetObject-tp5713159.html
> Sent from the Mono for Android mailing list archive at Nabble.com.
> ___
> Monodroid mailing list
> Monodroid@lists.ximian.com
> 
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/mailman/listinfo/monodroid

___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid