Intersoft Community - Crosslight - Crosslight 5 Android API < 21

Crosslight 5 Android API < 21

yudi — Tue, 14 Jun 2016 02:22:24 GMT

Glad to hear that disabling Use Shared Runtime (and Use Fast Deployment) helps.

Should you need further assistance or run into any problems regarding our controls, feel free to contact us through our live chat service or post it into our forum. We would be happy to assist you again.

Crosslight 5 Android API < 21

thomas.albert@tea-net.ch — Sat, 11 Jun 2016 10:10:31 GMT

Hello Yudi,

I tried it and it worked as you described it.

Thanks,

Thomas

Crosslight 5 Android API < 21

yudi — Fri, 10 Jun 2016 09:35:09 GMT

Hello Thomas,

Could you please try the following on Samsung GT-S7580 (API 17) and let us know the result?

Run the app on the device in Release configuration.
Try to disable Use Shared Runtime (such as shown in the attached screenshot, DisableUseSharedRuntime.jpg). It will automatically disable Use Fast Deployment.

I have Asus P01Y running Android 5.0.2 which crash right after the splash screen when running Android project in Debug mode. After disabling Use Shared Runtime, now I can debug Android app on this device.

Look forward to hearing back from you.

Crosslight 5 Android API < 21

thomas.albert@tea-net.ch — Thu, 09 Jun 2016 10:05:44 GMT

Hello Yudi,

the problem with debugging Android Material apps on Samsung GT-S7580 (API 17) was never really solved. I don't know if you have further infos from the dev team.

I tried once more on this device with the form builder sample and I got the following output (app starts in debug mode and crashed on startup):

06-09 12:00:59.854 W/monodroid-gc( 7648): GREF GC Threshold: 46080

06-09 12:00:59.854 D/Mono ( 7648): Image addref Mono.Android[0x503ab808] -> Mono.Android.dll[0x4fb07e18]: 1

06-09 12:00:59.854 D/Mono ( 7648): Assembly Mono.Android[0x503ab808] added to domain RootDomain, ref_count=1

06-09 12:00:59.864 D/Mono ( 7648): AOT module 'Mono.Android.dll.so' not found: Cannot load library: load_library(linker.cpp:746): library "/data/app-lib/FormBuilderSamples.Android.Material-2/libaot-Mono.Android.dll.so" not found

06-09 12:00:59.864 D/Mono ( 7648): AOT module '/Users/builder/data/lanes/2923/52635947/source/monodroid/builds/install/mono-armv7/lib/mono/aot-cache/arm/Mono.Android.dll.so' not found: Cannot load library: load_library(linker.cpp:746): library "/data/app-lib/FormBuilderSamples.Android.Material-2/libaot-Mono.Android.dll.so" not found

06-09 12:00:59.894 D/Mono ( 7648): Config attempting to parse: 'Mono.Android.dll.config'.

06-09 12:00:59.894 D/Mono ( 7648): Config attempting to parse: '/Users/builder/data/lanes/2923/52635947/source/monodroid/builds/install/mono-armv7/etc/mono/assemblies/Mono.Android/Mono.Android.config'.

06-09 12:00:59.904 D/Mono ( 7648): Assembly Ref addref Mono.Android[0x503ab808] -> mscorlib[0x402ab3a8]: 2

06-09 12:00:59.904 D/Mono ( 7648): Assembly Ref addref Mono.Android[0x503ab808] -> Java.Interop[0x503b2e40]: 2

06-09 12:00:59.904 D/Mono ( 7648): Assembly Loader probing location: '/Users/builder/data/lanes/2923/52635947/source/monodroid/builds/install/mono-armv7/lib/mono/gac/System.Runtime/4.0.0.0__b03f5f7f11d50a3a/System.Runtime.dll'.

06-09 12:00:59.904 D/Mono ( 7648): Assembly Loader probing location: '/Users/builder/data/lanes/2923/52635947/source/monodroid/builds/install/mono-armv7/lib/System.Runtime.dll'.

06-09 12:00:59.904 D/Mono ( 7648): Assembly Loader probing location: '/Users/builder/data/lanes/2923/52635947/source/monodroid/builds/install/mono-armv7/lib/System.Runtime.exe'.

06-09 12:00:59.904 D/Mono ( 7648): Assembly Loader probing location: '/System.Runtime.dll'.

06-09 12:00:59.904 D/Mono ( 7648): Assembly Loader probing location: '/Users/builder/data/lanes/2923/52635947/source/monodroid/builds/install/mono-armv7/lib/System.Runtime.dll'.

06-09 12:00:59.904 D/Mono ( 7648): Assembly Loader probing location: '/System.Runtime.exe'.

06-09 12:00:59.904 D/Mono ( 7648): Assembly Loader probing location: '/Users/builder/data/lanes/2923/52635947/source/monodroid/builds/install/mono-armv7/lib/System.Runtime.exe'.

06-09 12:00:59.904 W/Mono ( 7648): The following assembly referenced from Java.Interop.dll could not be loaded:

06-09 12:00:59.904 W/Mono ( 7648): Assembly: System.Runtime (assemblyref_index=1)

06-09 12:00:59.904 W/Mono ( 7648): Version: 4.0.0.0

06-09 12:00:59.904 W/Mono ( 7648): Public Key: b03f5f7f11d50a3a

06-09 12:00:59.904 W/Mono ( 7648): The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/).

06-09 12:00:59.904 D/Mono ( 7648): Failed to load assembly Java.Interop[0x503b2e40]

06-09 12:00:59.904 W/Mono ( 7648): Could not load file or assembly 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.

06-09 12:00:59.904 E/mono-rt ( 7648): Stacktrace:

06-09 12:00:59.904 E/mono-rt ( 7648):

06-09 12:00:59.904 E/mono-rt ( 7648): Attempting native Android stacktrace:

06-09 12:00:59.904 E/mono-rt ( 7648):

06-09 12:00:59.914 E/mono-rt ( 7648): at ???+1134420 [0x541acf54]

06-09 12:00:59.914 E/mono-rt ( 7648): at ???+83836 [0x4ff0577c]

06-09 12:00:59.914 E/mono-rt ( 7648):

06-09 12:00:59.914 E/mono-rt ( 7648): =================================================================

06-09 12:00:59.914 E/mono-rt ( 7648): Got a SIGSEGV while executing native code. This usually indicates

06-09 12:00:59.914 E/mono-rt ( 7648): a fatal error in the mono runtime or one of the native libraries

06-09 12:00:59.914 E/mono-rt ( 7648): used by your application.

06-09 12:00:59.914 E/mono-rt ( 7648): =================================================================

06-09 12:00:59.914 E/mono-rt ( 7648):

06-09 12:00:59.914 F/libc ( 7648): Fatal signal 11 (SIGSEGV) at 0x00000018 (code=1), thread 7648 Android.Material)

Maybe it helps.

Thanks,

Thomas

Crosslight 5 Android API < 21

yudi — Tue, 29 Mar 2016 09:49:06 GMT

Hello Thomas,

We don't have the device. It is difficult for us to perform debugging on the reported problem.

Provided sys log from the phone API17 are now being investigated. I'll keep you informed with any news I heard from the team regarding this.

Edited on April 5, 2016 10:00 PM
Reason: Update latest progress

On April 4, 2016, a signed APK of MaterialSamples has been sent to @Thomas Albert (directly to his registered email account) to be tested on Samsung GT-S7580.

After install the APK, there is no crash when start the app and can navigate around the sample without crashing.

It turns out that the project, MaterialSamples, doesn't cause the problem (since the signed APK doesn't crash on Samsung GT-S7580 (running API 17) device).

The reported problem occured when starting the app out of VS or Xamarin Studio while debugging.

Crosslight 5 Android API < 21

thomas.albert@tea-net.ch — Wed, 23 Mar 2016 18:17:38 GMT

Hello Yudi,

could you reproduce the problem with the Samsung GT-S7580 device?

Thanks,

Thomas

Crosslight 5 Android API < 21

yudi — Fri, 18 Mar 2016 02:03:05 GMT

I just re-tested. The problem with "Floating Action Button inside ViewPage" seems to be fixed. The app no longer crashes on my API 19 and API 21 devices.

Glad to hear the good news.

... My device is a Samsung Galaxy phone (GT-S7580 Android 4.2.2).
... Should it work on API 17?

Both samples, MaterialSamples (ui-material repository) and ViewSliderSamples (ui-view-slider repository), work without issues on my Samsung Galaxy Nexus (API 17) running Android 4.2.1.

I'll continue my investigation specific for Samsung GT-S7580 and get back to you as soon as possible. Thank you for the patience and cooperation.

Crosslight 5 Android API < 21

thomas.albert@tea-net.ch — Thu, 17 Mar 2016 08:36:01 GMT

Hello Yudi,

I just re-tested. The problem with "Floating Action Button inside ViewPage" seems to be fixed. The app no longer crashes on my API 19 and API 21 devices.

On my API 17 device the material ui sample and the viewslider sample crash without any error message after the splashscreen disappears. This seems no fixed to me. My device is a Samsung Galaxy phone (GT-S7580 Android 4.2.2).

I updated to the latest NuGet packages (5.0.5000.565), cleaned the solution and did a rebuild. Should it work on API 17?

Thanks,

Thomas

Crosslight 5 Android API < 21

yudi — Tue, 15 Mar 2016 09:36:22 GMT

- Going toFloating Action Button inside ViewPage, I get the following error:
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException () [0x00000] in /Users/builder/data/lanes/2692/e98e9627/source/mono/external/referencesource/mscorlib/system/throwhelper.cs:70
at System.Collections.Generic.Dictionary`2[TKey,TValue].get_Item (System.Collections.Generic.TKey key) [0x00021] in /Users/builder/data/lanes/2692/e98e9627/source/mono/external/referencesource/mscorlib/system/collections/generic/dictionary.cs:176
at Intersoft.Crosslight.Android.v7.ViewPagerFragment`1[TViewModel].UpdateFloatingActionButtons (Int32 itemPosition, Single scaleTo, Boolean animate, Int32 duration) [0x00022] in <filename unknown>:0
at Intersoft.Crosslight.Android.v7.ViewPagerFragment`1[TViewModel].Android.Support.V4.View.ViewPager.IOnPageChangeListener.OnPageScrolled (Int32 position, Single positionOffset, Int32 positionOffsetPixels) [0x00189] in <filename unknown>:0
at Android.Support.V4.View.ViewPager+IOnPageChangeListenerInvoker.n_OnPageScrolled_IFI (IntPtr jnienv, IntPtr native__this, Int32 position, Single positionOffset, Int32 positionOffsetPixels) [0x00009] in <filename unknown>:0
at at (wrapper dynamic-method) System.Object:76e7776e-a617-4b1b-b636-073d33c317e7 (intptr,intptr,int,single,int)

Hotfix has been deployed to NuGet which resolves issues of Android Material found on API 15. Please apply the update of Crosslight assembly (5.0.5000.559) and let us know if you have different result.

- Testing on my API 17 device, the app still crashes after the start without any error message. I have already send you a crash log.

I tested the MaterialSample on my Samsung Galaxy Nexus (API 17). The app doesn't crash after the start. Please check the screenshot below.

Look forward to hearing back from you.

Crosslight 5 Android API < 21

technical@intersoftpt.com — Fri, 04 Mar 2016 06:22:01 GMT

Hi Thomas,

Just sync'ing the latest state of these issues from the live chat session.

Running on API 15 and 16 device appears to work fine without crash, despite issues on certain samples which we'reworking on.
With production configuration APK, the sample works fine on API 17 device and simulator.

We'll getting back to you shortly after addressing minor glitches on the Material samples.

Thanks!

Crosslight 5 Android API < 21

thomas.albert@tea-net.ch — Fri, 19 Feb 2016 12:04:22 GMT

Hello Crosslight Support,

I just made some quick tests on Android devices with API level < 21.

Installing the material UI sample on my Samsung Tablet API 19 worked. After playing around with the sample it crashed. I think it is the grid view or the loading of the images into the grid view which cause the crash. See application output:

[mono-rt] Got a SIGSEGV while executing native code. This usually indicates
[mono-rt] a fatal error in the mono runtime or one of the native libraries
[mono-rt] used by your application.

[Mono] GC_OLD_BRIDGE num-objects 2079 num_hash_entries 4047 sccs size 3757 init 0.00ms df1 6.78ms sort 1.15ms dfs2 4.10ms setup-cb 1.12ms free-data 2.80ms links 3634/3634/24601/109 dfs passes 9760/7391
[Mono] GC_MINOR: (Nursery full) pause 26.49ms, total 26.65ms, bridge 0.00ms promoted 2064K major 2064K los 38249K
[dalvikvm-heap] Clamp target GC heap from 72.294MB to 64.000MB
[dalvikvm-heap] Forcing collection of SoftReferences for 1190403-byte allocation
[dalvikvm-heap] Clamp target GC heap from 74.294MB to 64.000MB
[dalvikvm-heap] Out of memory on a 1190403-byte allocation.
[mono-rt] Stacktrace:
[mono-rt]
[mono-rt] at <unknown> <0xffffffff>
[mono-rt] at (wrapper managed-to-native) object.wrapper_native_0x41c66c15 (intptr,intptr,int,int,byte[]) <IL 0x0003d, 0xffffffff>
[mono-rt] at (wrapper delegate-invoke) <Module>.invoke_void_intptr_intptr_int_int_byte[] (intptr,intptr,int,int,byte[]) <IL 0x00083, 0xffffffff>
[mono-rt] at Android.Runtime.JNIEnv.CopyArray (byte[],intptr) [0x00011] in /Users/builder/data/lanes/2692/e98e9627/source/monodroid/src/Mono.Android/src/Runtime/JNIEnv.g.cs:2156
[mono-rt] at Android.Runtime.JNIEnv.NewArray (byte[]) [0x00024] in /Users/builder/data/lanes/2692/e98e9627/source/monodroid/src/Mono.Android/src/Runtime/JNIEnv.g.cs:1954
[mono-rt] at Android.Graphics.BitmapFactory.DecodeByteArray (byte[],int,int,Android.Graphics.BitmapFactory/Options) [0x0002d] in /Users/builder/data/lanes/2692/e98e9627/source/monodroid/src/Mono.Android/platforms/android-21/src/generated/Android.Graphics.BitmapFactory.cs:566
[mono-rt] at Intersoft.Crosslight.Android.BitmapUtility.DecodeSampledBitmap (object,int,int,Android.Content.Res.Resources) <IL 0x00031, 0x00257>
[mono-rt] at Intersoft.Crosslight.Android.BitmapUtility.DecodeSampledBitmapFromByteArray (byte[],int,int) <IL 0x00007, 0x0007f>
[mono-rt] at Intersoft.Crosslight.Android.BitmapUtility.LoadAndResizeBitmap (byte[],int,int) <IL 0x00003, 0x0005b>
[mono-rt] at Intersoft.Crosslight.Android.ImageLoaderTask.CreateDrawable (Android.Widget.ImageView,byte[],bool,bool) <IL 0x0000d, 0x000c7>
[mono-rt] at Intersoft.Crosslight.Android.ImageLoaderTask.DoInBackground (Java.Lang.Object[]) <IL 0x0008d, 0x00683>
[mono-rt] at Android.OS.AsyncTask.n_DoInBackground_arrayLjava_lang_Object_ (intptr,intptr,intptr) [0x00020] in /Users/builder/data/lanes/2692/e98e9627/source/monodroid/src/Mono.Android/platforms/android-21/src/generated/Android.OS.AsyncTask.cs:218
[mono-rt] at (wrapper dynamic-method) object.3b343073-77d4-40e6-b565-7b720f75dcea (intptr,intptr,intptr) <IL 0x00017, 0x00047>
[mono-rt] at (wrapper native-to-managed) object.3b343073-77d4-40e6-b565-7b720f75dcea (intptr,intptr,intptr) <IL 0x00029, 0xffffffff>

Installing the sample on my Samsung phone API 17 failed. The app crashed right after showing the splash screen. There is no error message or application output.

I though that your implementation of the material UI supports devices with API 15 and above. Am I wrong?

Thanks,

Thomas