Unsubscribe On Dec 12, 2011 7:54 PM, <monodroid-requ...@lists.ximian.com> wrote:
> Send Monodroid mailing list submissions to > monodroid@lists.ximian.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.ximian.com/mailman/listinfo/monodroid > or, via email, send a message with subject or body 'help' to > monodroid-requ...@lists.ximian.com > > You can reach the person managing the list at > monodroid-ow...@lists.ximian.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Monodroid digest..." > > > Today's Topics: > > 1. Thread Exceptions Without Stacktrace (Aaron Knabb) > 2. Re: Supported architectures? armeabi-v7a (Vladimir Dimitrov) > 3. Re: Supported architectures? armeabi-v7a (Jonathan Pryor) > 4. Re: Thread Exceptions Without Stacktrace (Jonathan Pryor) > 5. Re: Mono for Android 4 - Constructor injection causes > packaging failure. (Jonathan Pryor) > 6. Re: Android application crashing on device (Jonathan Pryor) > 7. Re: Android application Crash unexpectedly on device using > release version (Jonathan Pryor) > 8. Re: How to reference and use a android library project apk > (Jonathan Pryor) > 9. Re: Thread Exceptions Without Stacktrace (Aaron Knabb) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 12 Dec 2011 15:11:24 -0700 > From: Aaron Knabb <akn...@mobileepiphany.com> > Subject: [mono-android] Thread Exceptions Without Stacktrace > To: Discussions related to Mono for Android > <Monodroid@lists.ximian.com> > Message-ID: > <CAG9nUbtUtTKwyp=dv_GMDURy3DAkrAq72=mwMGR=ohx1obi...@mail.gmail.com > > > Content-Type: text/plain; charset="iso-8859-1" > > I've seen several similar issues on this topic, but the only solution seems > to be "wait for the next version." I am running the latest 4.0 build, but I > keep seeing the following problem: > > I have a worker thread that is randomly crashing and taking down the whole > app with it. I don't get any exception in the logs, and I am unable to trap > it with try/catch blocks. This thread does some web service work, disk > access, db access, and some bitmap manipulation. The only consistent thing > I can see in the logs is a GC_EXPLICIT that occurs right before the crash. > Note that other such calls execute fine on that thread, but the last call > on the thread is always a GC_EXPLICIT. > > I'm having trouble making progress on it because I don't really know where > to start looking. It seems like it might be GC related, but I can't say > that for sure. Also, a simple test app doesn't seem to be an option because > the thread apparently needs to be heavily bogged down to see the problem. > > Anyone got any ideas? > -Aaron > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.ximian.com/pipermail/monodroid/attachments/20111212/093b3c6c/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Tue, 13 Dec 2011 00:24:34 +0200 > From: "Vladimir Dimitrov" <vlad.dimit...@gmail.com> > Subject: Re: [mono-android] Supported architectures? armeabi-v7a > To: "'Discussions related to Mono for Android'" > <monodroid@lists.ximian.com> > Message-ID: <4ee67f26.051a640a.3d46.ffff8...@mx.google.com> > Content-Type: text/plain; charset="us-ascii" > > So does this mean that we should always enable armeabi-v7a in cases when we > use a lot of multi threading and floating point operations? > > I guess the trade off in this case is that if we include both there will be > a bigger .apk as a result? Anything else? > > - Vladimir > > -----Original Message----- > From: monodroid-boun...@lists.ximian.com > [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Jonathan Pryor > Sent: Monday, December 12, 2011 10:55 PM > To: Discussions related to Mono for Android > Subject: Re: [mono-android] Supported architectures? armeabi-v7a > > On Dec 12, 2011, at 2:49 PM, Neal Culiner wrote: > > Should I have both armeabi and aremabi-v7a checked in the application > properties? I can't find anything in the MD docs to advise me. > > The largest differences are in hardware floating point support and SMP > (multi-CPU) support. > > armeabi supports neither, so if you use lots of floating point math you'll > be using a software FPU, and if you run on an multi-CPU device such as the > Xoom or the Samsun Galaxy S II you'll be tied to one core. > > armeabi-v7a supports both, allowing faster floating point execution and the > use of all available cores. > > - Jon > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > > > > ------------------------------ > > Message: 3 > Date: Mon, 12 Dec 2011 20:00:02 -0500 > From: Jonathan Pryor <j...@xamarin.com> > Subject: Re: [mono-android] Supported architectures? armeabi-v7a > To: Discussions related to Mono for Android > <monodroid@lists.ximian.com> > Message-ID: <3fbdf440-4ca3-4c65-be8c-b7d14c184...@xamarin.com> > Content-Type: text/plain; charset=us-ascii > > On Dec 12, 2011, at 5:24 PM, Vladimir Dimitrov wrote: > > So does this mean that we should always enable armeabi-v7a in cases when > we use a lot of multi threading and floating point operations? > > Maybe. Depends on the app. :-) > > > I guess the trade off in this case is that if we include both there will > be a bigger .apk as a result? Anything else? > > That's pretty much it. > > Furthermore, given that armeabi is ancient, and even the API level 14 > emulator is armeabi-v7a, there is a case to be made that armeabi doesn't > need to be supported at all, leaving you with just armeabi-v7a in your > .apk. (Furthermore, I have no idea how many devices this would actually > exclude, Firefox Mobile made the choice to go with supporting only > armeabi-v7a, so this isn't an entirely unheard of decision.) > > Either way, each libmonodroid.so is ~3MB in size, though this is > compressed in the .apk to about 1.2MB, so you're looking at a minimum 1.2MB > increase for each ABI you intend to support. > > - Jon > > > > ------------------------------ > > Message: 4 > Date: Mon, 12 Dec 2011 22:25:37 -0500 > From: Jonathan Pryor <j...@xamarin.com> > Subject: Re: [mono-android] Thread Exceptions Without Stacktrace > To: Discussions related to Mono for Android > <monodroid@lists.ximian.com> > Message-ID: <45b7d3ac-dba4-46b3-a6d2-96e393d4e...@xamarin.com> > Content-Type: text/plain; charset=iso-8859-1 > > On Dec 12, 2011, at 5:11 PM, Aaron Knabb wrote: > > I've seen several similar issues on this topic, but the only solution > seems to be "wait for the next version." I am running the latest 4.0 build, > but I keep seeing the following problem: > > We have a 4.0.1 release coming out Real Soon Now, which fixes a GC assert > and a GC "hang" (along with a few other issues). Good stuff. > > It _may_ also fix your stacktrace-less exception, but it might not; if it > doesn't, we're (unfortunately) going to need a repro so that we can kill > the bug with extreme prejudice ^H^H^H^H^H^H fix the bug. :-/ > > Thanks, > - Jon > > > > ------------------------------ > > Message: 5 > Date: Mon, 12 Dec 2011 22:34:44 -0500 > From: Jonathan Pryor <j...@xamarin.com> > Subject: Re: [mono-android] Mono for Android 4 - Constructor injection > causes packaging failure. > To: Discussions related to Mono for Android > <monodroid@lists.ximian.com> > Message-ID: <860d8d36-05fd-434b-8665-40a9e6a0c...@xamarin.com> > Content-Type: text/plain; charset=us-ascii > > On Dec 8, 2011, at 6:04 AM, SpiritMachine wrote: > > This looks similar too some other packaging issues outstanding that > might have to do with generics and/or abstract classes. > > No, it has to do with faulty constructor lookup algorithms. :-) > > This is fixed in the 4.0.1 release. > > - Jon > > > > ------------------------------ > > Message: 6 > Date: Mon, 12 Dec 2011 22:41:31 -0500 > From: Jonathan Pryor <j...@xamarin.com> > Subject: Re: [mono-android] Android application crashing on device > To: Discussions related to Mono for Android > <monodroid@lists.ximian.com> > Message-ID: <c50cfabe-04d5-4dbc-9805-10ea071c7...@xamarin.com> > Content-Type: text/plain; charset=iso-8859-1 > > On Dec 8, 2011, at 6:28 AM, Amitabh Mishra wrote: > > After installation, when we run the application, we are getting the > following error on device (android version 2.2). > > The problem is that the shared runtime can't be found: > > E/AndroidRuntime( 4936): java.lang.RuntimeException: Unable to get > provider mono.MonoRuntimeProvider: java.lang.RuntimeException: Unable to > find application Mono.Android.DebugRuntime or > Mono.Android.Platform.ApiLevel_8! > > Why is it wanting to use the shared runtime? Because your project file is > misconfigured: > > <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == > 'Release|AnyCPU' "> > <AndroidUseSharedRuntime>True</AndroidUseSharedRuntime> > </PropertyGroup> > > The <AndroidUseSharedRuntime/> element should be False, not True. > > Change this value to False (i.e. deselect the Use shared runtime checkbox > for Release builds), Clean, Build, and reinstall the .apk. That should fix > your problem. > > Thanks, > - Jon > > > > ------------------------------ > > Message: 7 > Date: Mon, 12 Dec 2011 22:43:36 -0500 > From: Jonathan Pryor <j...@xamarin.com> > Subject: Re: [mono-android] Android application Crash unexpectedly on > device using release version > To: Discussions related to Mono for Android > <monodroid@lists.ximian.com> > Message-ID: <1c517690-55ab-4e7b-aab8-7201a87e2...@xamarin.com> > Content-Type: text/plain; charset=us-ascii > > On Dec 8, 2011, at 5:36 AM, pankaj1606 wrote: > > but I am getting the following error on device (android version 2.2), > > > > *The application has stopped unexpectedly. Please try again.* > > Unfortunately, we need more information than this. Please provide the > relevant Android Debug Log output: > > > http://docs.xamarin.com/android/advanced_topics/android_debug_log#Interesting_Messages > > Thanks, > - Jon > > > > ------------------------------ > > Message: 8 > Date: Mon, 12 Dec 2011 22:50:34 -0500 > From: Jonathan Pryor <j...@xamarin.com> > Subject: Re: [mono-android] How to reference and use a android library > project apk > To: Discussions related to Mono for Android > <monodroid@lists.ximian.com> > Message-ID: <ae346a2a-acc9-4025-b913-4f5cf7311...@xamarin.com> > Content-Type: text/plain; charset=us-ascii > > On Dec 9, 2011, at 5:25 PM, klimaye wrote: > > I am looking at > > > > http://code.google.com/p/android-section-list/ > > > > as a sectioned listview implementation. > > > > How would one reference the generated apk (output of library project) > with monodroid? > > > > Would I use JNI ? > > For a library of that size, porting to C# would likely be easier. :-) > > For larger libraries, yes, you can include them into your app and use JNI > to interact with them. You can look at the SanityTests sample: > > > https://github.com/xamarin/monodroid-samples/tree/master/SanityTests > > Specifically the TestJniInvocation() test: > > > https://github.com/xamarin/monodroid-samples/blob/master/SanityTests/Hello.cs#L513 > > and the <AndroidJavaSource/> within the project file: > > > https://github.com/xamarin/monodroid-samples/blob/master/SanityTests/SanityTests.csproj#L62 > > (There is also logic to build the .jar via MSBuild, which is ignorable if > you don't need to build Java source...) > > - Jon > > > > ------------------------------ > > Message: 9 > Date: Mon, 12 Dec 2011 20:54:52 -0700 > From: Aaron Knabb <akn...@mobileepiphany.com> > Subject: Re: [mono-android] Thread Exceptions Without Stacktrace > To: Discussions related to Mono for Android > <monodroid@lists.ximian.com> > Message-ID: > <CAG9nUbswqjzE=trdydb36epdzveupdtlhbirwyxjqcauogg...@mail.gmail.com > > > Content-Type: text/plain; charset="iso-8859-1" > > Well I'll give it a try when 4.0.1 comes out. I'm trying to create an > example app now. No luck so far. > > -Aaron > > > On Mon, Dec 12, 2011 at 8:25 PM, Jonathan Pryor <j...@xamarin.com> wrote: > > > On Dec 12, 2011, at 5:11 PM, Aaron Knabb wrote: > > > I've seen several similar issues on this topic, but the only solution > > seems to be "wait for the next version." I am running the latest 4.0 > build, > > but I keep seeing the following problem: > > > > We have a 4.0.1 release coming out Real Soon Now, which fixes a GC assert > > and a GC "hang" (along with a few other issues). Good stuff. > > > > It _may_ also fix your stacktrace-less exception, but it might not; if it > > doesn't, we're (unfortunately) going to need a repro so that we can kill > > the bug with extreme prejudice ^H^H^H^H^H^H fix the bug. :-/ > > > > Thanks, > > - Jon > > > > _______________________________________________ > > Monodroid mailing list > > Monodroid@lists.ximian.com > > > > UNSUBSCRIBE INFORMATION: > > http://lists.ximian.com/mailman/listinfo/monodroid > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.ximian.com/pipermail/monodroid/attachments/20111212/6a8fbde1/attachment.html > > ------------------------------ > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/monodroid > > > End of Monodroid Digest, Vol 17, Issue 63 > ***************************************** >
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
