My Media Center Crashes After Splash Screen

Discuss My Media Center for Windows 8, Windows RT, iOS, Android, and WP, and ask Ceton for support.
Forum rules
Ceton no longer participate in this forum. There is no official support mechanism for My Media Center.
Post Reply
islipfd19

Posts: 3
Joined: Mon Oct 08, 2012 11:20 pm
Location:

HTPC Specs: Show details

My Media Center Crashes After Splash Screen

#1

Post by islipfd19 » Wed May 21, 2014 11:04 am

OK, so I haven't used 'My Media Center' for android for some time. I tried starting it the other day and it crashes after the splash screen. I'm running one of the latest CM11 (kitkat 4.4) nightlies (5/20/2014) and all partitions are formatted to F2FS. I've tried uninstalling and reinstalling the app. I've tried restoring it from titanium backup, the logs indicate that is tries loading a lib from /data/app-lib/com.ceton.companion-1/libmonodroid.so, it then adds it and the process dies.

What I'm asking is, who or where should I upload log files to to help investigate the reason why it crashes and to help get it fixed. If this isn't the proper forum/subforum please let me know and which forum/subforum this should be posted in. I appreciate all the help anyone can give! This is a great app.

Another note, I have seen a couple posts similar to what I've been experiencing.

User avatar
Crash2009

Posts: 4357
Joined: Thu May 17, 2012 12:38 am
Location: Ann Arbor, Michigan

HTPC Specs: Show details

#2

Post by Crash2009 » Wed May 21, 2014 3:49 pm

Do you see any similarities http://www.thegreenbutton.tv/forums/vie ... =63&t=6200

Failing that.....Submit a support ticket http://cetoncorp.com/product-support/

kmp14

Posts: 131
Joined: Sat Sep 08, 2012 7:23 pm
Location:

HTPC Specs: Show details

#3

Post by kmp14 » Wed May 21, 2014 5:19 pm

Are you by chance running the ART runtime instead of Dalvik? (Settings..Developer Options..Select Runtime). My Media Center does not work with the ART runtime and crashes immediately after the splash screen.

islipfd19

Posts: 3
Joined: Mon Oct 08, 2012 11:20 pm
Location:

HTPC Specs: Show details

#4

Post by islipfd19 » Thu May 22, 2014 9:25 am

Crash2009 wrote:Do you see any similarities http://www.thegreenbutton.tv/forums/vie ... =63&t=6200

Failing that.....Submit a support ticket http://cetoncorp.com/product-support/
No, all of my PC's are running Windows 7 and the "crash" is happening on my android phone. I suppose I could open a support ticket.

islipfd19

Posts: 3
Joined: Mon Oct 08, 2012 11:20 pm
Location:

HTPC Specs: Show details

#5

Post by islipfd19 » Thu May 22, 2014 9:28 am

kmp14 wrote:Are you by chance running the ART runtime instead of Dalvik? (Settings..Developer Options..Select Runtime). My Media Center does not work with the ART runtime and crashes immediately after the splash screen.
No, I'm running Dalvik; I have no interest in ART at this time. I use xposed with quite a number of apps and xposed will only work with Dalvik. My partitions though are formatted F2FS, I don't think that should have anything to do with it because everything else works, but who knows.

breakthestatic

Posts: 24
Joined: Wed May 15, 2013 7:19 pm
Location:

HTPC Specs: Show details

#6

Post by breakthestatic » Fri May 30, 2014 1:43 pm

I'm experiencing the exact same issue with the latest oem software for my Verizon Moto X, which I believe uses f2fs as the filesystem for the data partition as well. Either way, this is a problem and needs to be remedied, but I don't think we'll see any action from Ceton though as they have gone dormant on the app since their android dev (James) left.

breakthestatic

Posts: 24
Joined: Wed May 15, 2013 7:19 pm
Location:

HTPC Specs: Show details

#7

Post by breakthestatic » Fri May 30, 2014 10:25 pm

I did a bit more digging and it seems this might be a problem with mono, I'm guessing the app uses shared code that gets compiled to android, win8 & iphone... Here's the logs of what's going on. I'm not an Adnroid dev, but maybe someone can make more sense of it:

05-30 06:31:12.395 5659 5760 I ActivityManager: Start proc com.ceton.companion for activity com.ceton.companion/veronaandroid.activities.FirstRunActivity: pid=29144 uid=10168 gids={50168, 3003, 1028, 1015}
05-30 06:31:12.412 6385 8644 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1244 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.util.TriggerHelper$TriggerBuilder.send:76 com.motorola.motocare.internal.frameworkevents.PauseResumeTrigger.handleFrameworkEvent:53 com.motorola.motocare.internal.frameworkevents.FwEventMonitor$FrameworkListener.processFrameworkEvent:114
05-30 06:31:12.425 5355 5355 D Zygote : Process 29126 exited cleanly (255)
05-30 06:31:12.451 29144 29144 D dalvikvm: Trying to load lib /mnt/asec/com.ceton.companion-1/lib/libmonodroid.so 0x42294de0
05-30 06:31:12.453 29144 29144 D dalvikvm: Added shared lib /mnt/asec/com.ceton.companion-1/lib/libmonodroid.so 0x42294de0
05-30 06:31:12.491 29144 29144 W libc : WARNING: generic atexit() called from legacy shared library
05-30 06:31:12.512 29144 29144 W monodroid-gc: GREF GC Threshold: 46800
05-30 06:31:12.933 5659 5704 D WifiStateMachine: handleMessage: E msg.what=151572
05-30 06:31:12.933 5659 5704 D WifiStateMachine: processMsg: ConnectedState
05-30 06:31:12.933 5659 5704 D WifiStateMachine: processMsg: L2ConnectedState
05-30 06:31:12.943 5659 5704 D WifiStateMachine: handleMessage: X
05-30 06:31:13.062 29144 29144 E dalvikvm: ERROR: tried to execute code in unprepared class 'Landroid/content/res/XResources$XTypedArray;' (3)
05-30 06:31:13.062 29144 29144 I dalvikvm: "main" prio=5 tid=1 RUNNABLE
05-30 06:31:13.062 29144 29144 I dalvikvm: | group="main" sCount=0 dsCount=0 obj=0x41661e40 self=0x416505f0
05-30 06:31:13.062 29144 29144 I dalvikvm: | sysTid=29144 nice=0 sched=0/0 cgrp=apps handle=1074168148
05-30 06:31:13.062 29144 29144 I dalvikvm: | state=R schedstat=( 0 0 0 ) utm=58 stm=4 core=1
05-30 06:31:13.062 29144 29144 I dalvikvm: at android.content.res.XResources$XTypedArray.getString(XResources.java:-1)
05-30 06:31:13.062 29144 29144 I dalvikvm: at mono.android.TypeManager.n_activate(Native Method)
05-30 06:31:13.062 29144 29144 I dalvikvm: at mono.android.TypeManager.Activate(TypeManager.java:7)
05-30 06:31:13.062 29144 29144 I dalvikvm: at veronaandroid.ActionBar.<init>(ActionBar.java:25)
05-30 06:31:13.062 29144 29144 I dalvikvm: at java.lang.reflect.Constructor.constructNative(Native Method)
05-30 06:31:13.062 29144 29144 I dalvikvm: at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
05-30 06:31:13.062 29144 29144 I dalvikvm: at android.view.LayoutInflater.createView(LayoutInflater.java:594)
05-30 06:31:13.062 29144 29144 I dalvikvm: at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:696)
05-30 06:31:13.062 29144 29144 I dalvikvm: at android.view.LayoutInflater.rInflate(LayoutInflater.java:755)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:492)
05-30 06:31:13.063 29144 29144 I dalvikvm: at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
05-30 06:31:13.063 29144 29144 I dalvikvm: at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.view.LayoutInflater.inflate(Native Method)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:397)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.view.LayoutInflater.inflate(LayoutInflater.java:353)
05-30 06:31:13.063 29144 29144 I dalvikvm: at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:290)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.Activity.setContentView(Activity.java:1937)
05-30 06:31:13.063 29144 29144 I dalvikvm: at veronaandroid.activities.FirstRunActivity.n_onCreate(Native Method)
05-30 06:31:13.063 29144 29144 I dalvikvm: at veronaandroid.activities.FirstRunActivity.onCreate(FirstRunActivity.java:32)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.Activity.performCreate(Activity.java:5248)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1110)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2173)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2269)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.ActivityThread.access$800(ActivityThread.java:139)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1210)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.os.Handler.dispatchMessage(Handler.java:102)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.os.Looper.loop(Looper.java:136)
05-30 06:31:13.063 29144 29144 I dalvikvm: at android.app.ActivityThread.main(ActivityThread.java:5102)
05-30 06:31:13.063 29144 29144 I dalvikvm: at java.lang.reflect.Method.invokeNative(Native Method)
05-30 06:31:13.063 29144 29144 I dalvikvm: at java.lang.reflect.Method.invoke(Method.java:515)
05-30 06:31:13.063 29144 29144 I dalvikvm: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
05-30 06:31:13.063 29144 29144 I dalvikvm: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
05-30 06:31:13.063 29144 29144 I dalvikvm: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
05-30 06:31:13.063 29144 29144 I dalvikvm: at dalvik.system.NativeStart.main(Native Method)
05-30 06:31:13.063 29144 29144 I dalvikvm:
05-30 06:31:13.063 29144 29144 E dalvikvm: VM aborting
05-30 06:31:13.063 29144 29144 E mono-rt : Stacktrace:
05-30 06:31:13.063 29144 29144 E mono-rt :
05-30 06:31:13.063 29144 29144 E mono-rt : at <unknown> <0xffffffff>
05-30 06:31:13.063 29144 29144 E mono-rt : at (wrapper managed-to-native) object.wrapper_native_0x415adc33 (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
05-30 06:31:13.063 29144 29144 E mono-rt : at (wrapper delegate-invoke) <Module>.invoke_intptr__this___intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
05-30 06:31:13.063 29144 29144 E mono-rt : at Android.Runtime.JNIEnv.CallObjectMethod (intptr,intptr,Android.Runtime.JValue[]) <0x00053>
05-30 06:31:13.063 29144 29144 E mono-rt : at Android.Content.Res.TypedArray.GetString (int) <0x00137>
05-30 06:31:13.063 29144 29144 E mono-rt : at VeronaAndroid.ActionBar..ctor (Android.Content.Context,Android.Util.IAttributeSet) <0x003e7>
05-30 06:31:13.064 29144 29144 E mono-rt : at (wrapper dynamic-method) object.1d496647-feca-425f-acc4-87798850ef2d (intptr,object[]) <0x0005f>
05-30 06:31:13.064 29144 29144 E mono-rt : at Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0x000ff>
05-30 06:31:13.064 29144 29144 E mono-rt : at (wrapper native-to-managed) Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0xffffffff>
05-30 06:31:13.064 29144 29144 E mono-rt : at <unknown> <0xffffffff>
05-30 06:31:13.064 29144 29144 E mono-rt : at (wrapper managed-to-native) object.wrapper_native_0x415ac94d (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
05-30 06:31:13.064 29144 29144 E mono-rt : at (wrapper delegate-invoke) <Module>.invoke_void__this___intptr_intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
05-30 06:31:13.064 29144 29144 E mono-rt : at Android.Runtime.JNIEnv.CallNonvirtualVoidMethod (intptr,intptr,intptr,Android.Runtime.JValue[]) <0x00067>
05-30 06:31:13.064 29144 29144 E mono-rt : at Android.App.Activity.SetContentView (int) <0x001e3>
05-30 06:31:13.064 29144 29144 E mono-rt : at VeronaAndroid.Activities.FirstRunActivity.OnCreate (Android.OS.Bundle) <0x00083>
05-30 06:31:13.064 29144 29144 E mono-rt : at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (intptr,intptr,intptr) <0x0005b>
05-30 06:31:13.064 29144 29144 E mono-rt : at (wrapper dynamic-method) object.39233f7e-fffd-4b08-8fd2-ee7e9c460d0a (intptr,intptr,intptr) <0x00043>
05-30 06:31:13.064 29144 29144 E mono-rt : at (wrapper native-to-managed) object.39233f7e-fffd-4b08-8fd2-ee7e9c460d0a (intptr,intptr,intptr) <0xffffffff>
05-30 06:31:13.064 29144 29144 E mono-rt :
05-30 06:31:13.064 29144 29144 E mono-rt : =================================================================
05-30 06:31:13.064 29144 29144 E mono-rt : Got a SIGABRT while executing native code. This usually indicates
05-30 06:31:13.064 29144 29144 E mono-rt : a fatal error in the mono runtime or one of the native libraries
05-30 06:31:13.064 29144 29144 E mono-rt : used by your application.
05-30 06:31:13.064 29144 29144 E mono-rt : =================================================================
05-30 06:31:13.064 29144 29144 E mono-rt :
05-30 06:31:13.089 5659 6863 I ActivityManager: Process com.ceton.companion (pid 29144) has died.
05-30 06:31:13.089 5659 6863 W ActivityManager: Force removing ActivityRecord{424bec50 u0 com.ceton.companion/veronaandroid.activities.FirstRunActivity t66}: app died, no saved state

erkotz

Posts: 1378
Joined: Mon Aug 22, 2011 9:23 pm
Location:

HTPC Specs: Show details

#8

Post by erkotz » Mon Jun 02, 2014 4:32 pm

Can you guys uninstall, restart the phone, and then reinstall? I know Motz used a Moto X so it does/did work on it.
Quality Assurance Manager, Ceton Corporation

breakthestatic

Posts: 24
Joined: Wed May 15, 2013 7:19 pm
Location:

HTPC Specs: Show details

#9

Post by breakthestatic » Mon Jun 02, 2014 4:44 pm

erkotz wrote:Can you guys uninstall, restart the phone, and then reinstall? I know Motz used a Moto X so it does/did work on it.
I've done that quite a few times. I think this is a bit beyond the reboot/reinstall level. I've also gone ahead and made sure that all the remnants of the install are gone before rebooting and attempting a reinstall.

erkotz

Posts: 1378
Joined: Mon Aug 22, 2011 9:23 pm
Location:

HTPC Specs: Show details

#10

Post by erkotz » Mon Jun 02, 2014 4:50 pm

Can you try removing Xposed and see if the issue is resolved - we think that may be related.
Quality Assurance Manager, Ceton Corporation

breakthestatic

Posts: 24
Joined: Wed May 15, 2013 7:19 pm
Location:

HTPC Specs: Show details

#11

Post by breakthestatic » Mon Jun 02, 2014 5:09 pm

erkotz wrote:Can you try removing Xposed and see if the issue is resolved - we think that may be related.
I have 3 devices:

2012 Nexus 7, rooted & running xposed - no issues with MMC
Verizon Galaxy Nexus, rooted & running cm11 m6 - no issues with MMC
Verizon Moto X, complete stock, unrooted - MMC crashes w/ the errors above

erkotz

Posts: 1378
Joined: Mon Aug 22, 2011 9:23 pm
Location:

HTPC Specs: Show details

#12

Post by erkotz » Mon Jun 02, 2014 5:11 pm

breakthestatic wrote:
erkotz wrote:Can you try removing Xposed and see if the issue is resolved - we think that may be related.
I have 3 devices:

2012 Nexus 7, rooted & running xposed - no issues with MMC
Verizon Galaxy Nexus, rooted & running cm11 m6 - no issues with MMC
Verizon Moto X, complete stock, unrooted - MMC crashes w/ the errors above
The stack trace you posted mentioned Xposed:
breakthestatic wrote: <snip>
05-30 06:31:13.063 29144 29144 I dalvikvm: at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
05-30 06:31:13.063 29144 29144 I dalvikvm: at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
</snip>
Quality Assurance Manager, Ceton Corporation

breakthestatic

Posts: 24
Joined: Wed May 15, 2013 7:19 pm
Location:

HTPC Specs: Show details

#13

Post by breakthestatic » Mon Jun 02, 2014 5:17 pm

breakthestatic wrote:
erkotz wrote:Can you try removing Xposed and see if the issue is resolved - we think that may be related.
I have 3 devices:

2012 Nexus 7, rooted & running xposed - no issues with MMC
Verizon Galaxy Nexus, rooted & running cm11 m6 - no issues with MMC
Verizon Moto X, complete stock, unrooted - MMC crashes w/ the errors above
Hmm, that log might actually be from the N7 then... I had all 3 devices plugged in while trying to debug. I thought that the N7 was running it fine, but now that I've tried it again just now, it does appear to be exhibiting the same behavor.

In any event though, my Moto X can't be rooted... I got it with 4.4.2 direct from VZW, and there is no known exploit for it yet and can't be downgraded.

erkotz

Posts: 1378
Joined: Mon Aug 22, 2011 9:23 pm
Location:

HTPC Specs: Show details

#14

Post by erkotz » Mon Jun 02, 2014 5:24 pm

Is there any chance you can get a log from the X (or the N7 with Xposed removed).
Quality Assurance Manager, Ceton Corporation

breakthestatic

Posts: 24
Joined: Wed May 15, 2013 7:19 pm
Location:

HTPC Specs: Show details

#15

Post by breakthestatic » Mon Jun 02, 2014 5:50 pm

erkotz wrote:Is there any chance you can get a log from the X (or the N7 with Xposed removed).
No need, as I actually just worked around the issue myself. The whole idea of Xposed causing the issue got me googling a bit, and I came across the follow stack overflow issue (http://stackoverflow.com/questions/2042 ... ndom-crash). Towards the bottom I noticed a bunch of talk regarding accessibility services and one of the posts itself speaks of TalkBack being turned on, but in my case I remembered that to the contrary, I actually had TalkBack fully disabled via the Android Package Manager. According to the discussion it seems that some accessibility flags in the views are causing issues. To fix the issue, I just re-enabled TalkBack (didn't turn on, rather just "enabled" via the Package Manager), but I know lots of people that freeze TalkBack to free up some system resources, and it's something that can easily be done by end-users, root or not. I'd look into the post linked, and try and find the underlying cause that isn't meshing well with accesibility services.

obrechte

Posts: 3
Joined: Thu Jun 05, 2014 3:37 pm
Location:

HTPC Specs: Show details

#16

Post by obrechte » Thu Jun 05, 2014 3:41 pm

I am running in to the same problem on my rooted GS4 SCH-I545 running 4.3. I tried launching the app with talkback both frozen and unfrozen, turned on/off, and rolled back to the unupdated app and I'm still crashing. How can I grab the log file like you did?

breakthestatic

Posts: 24
Joined: Wed May 15, 2013 7:19 pm
Location:

HTPC Specs: Show details

#17

Post by breakthestatic » Thu Jun 05, 2014 4:33 pm

obrechte wrote:I am running in to the same problem on my rooted GS4 SCH-I545 running 4.3. I tried launching the app with talkback both frozen and unfrozen, turned on/off, and rolled back to the unupdated app and I'm still crashing. How can I grab the log file like you did?
The issue with TalkBack appears to be a 4.4.x issue, so it most likely wouldn't be the cause of your crashes on 4.3. To get the logs, you can either install an app that captures logs, or use the built in bug reporting tool from the Developer menu. If you don't have the Developer menu, you can access it by going to settings > about phone, and tapping the build number field 7-8 times. Once you do that the developer options should appear in the main settings menu towards the bottom of the list.

obrechte

Posts: 3
Joined: Thu Jun 05, 2014 3:37 pm
Location:

HTPC Specs: Show details

#18

Post by obrechte » Fri Jun 06, 2014 7:02 pm

Sorry, I'm not sure if I'm supposed to start a new thread but I'm having the same issue looks like with a similar error.

Code: Select all

build.board: MSM8960
build.bootloader: I545VRUEMK2
build.brand: Verizon
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: jfltevzw
build.display: JSS15J.I545VRUEMK2
build.fingerprint: Verizon/jfltevzw/jfltevzw:4.3/JSS15J/I545VRUEMK2:user/release-keys
build.hardware: qcom
build.host: R0210-09
build.id: JSS15J
build.manufacturer: samsung
build.model: SCH-I545
build.product: jfltevzw
build.radio: unknown
build.serial: 649e6c87
build.tags: release-keys
build.time: 1384919477000
build.type: user
build.user: se.infra
version.codename: REL
version.incremental: I545VRUEMK2
version.release: 4.3
version.sdk_int: 18

06-06 14:11:46.658 E/mono-rt (32202): Stacktrace:
06-06 14:11:46.658 E/mono-rt (32202): 
06-06 14:11:46.658 E/mono-rt (32202):   at <unknown> <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper managed-to-native) object.wrapper_native_0x40b3fcff (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper delegate-invoke) <Module>.invoke_intptr__this___intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202):   at Android.Runtime.JNIEnv.CallObjectMethod (intptr,intptr,Android.Runtime.JValue[]) <0x00053>
06-06 14:11:46.658 E/mono-rt (32202):   at Android.Content.Res.TypedArray.GetString (int) <0x00137>
06-06 14:11:46.658 E/mono-rt (32202):   at VeronaAndroid.ActionBar..ctor (Android.Content.Context,Android.Util.IAttributeSet) <0x003e7>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper dynamic-method) object.ad77d637-5106-43d8-b663-f6b60dc87884 (intptr,object[]) <0x0005f>
06-06 14:11:46.658 E/mono-rt (32202):   at Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0x000ff>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper native-to-managed) Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202):   at <unknown> <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper managed-to-native) object.wrapper_native_0x40b3ea19 (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper delegate-invoke) <Module>.invoke_void__this___intptr_intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202):   at Android.Runtime.JNIEnv.CallNonvirtualVoidMethod (intptr,intptr,intptr,Android.Runtime.JValue[]) <0x00067>
06-06 14:11:46.658 E/mono-rt (32202):   at Android.App.Activity.SetContentView (int) <0x001e3>
06-06 14:11:46.658 E/mono-rt (32202):   at VeronaAndroid.Activities.FirstRunActivity.OnCreate (Android.OS.Bundle) <0x00083>
06-06 14:11:46.658 E/mono-rt (32202):   at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (intptr,intptr,intptr) <0x0005b>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper dynamic-method) object.dd1221bf-854b-4273-af72-5a72ff01697b (intptr,intptr,intptr) <0x00043>
06-06 14:11:46.658 E/mono-rt (32202):   at (wrapper native-to-managed) object.dd1221bf-854b-4273-af72-5a72ff01697b (intptr,intptr,intptr) <0xffffffff>
06-06 14:11:46.658 E/mono-rt (32202): 
06-06 14:11:46.658 E/mono-rt (32202): =================================================================
06-06 14:11:46.658 E/mono-rt (32202): Got a SIGSEGV while executing native code. This usually indicates
06-06 14:11:46.658 E/mono-rt (32202): a fatal error in the mono runtime or one of the native libraries 
06-06 14:11:46.658 E/mono-rt (32202): used by your application.
06-06 14:11:46.658 E/mono-rt (32202): =================================================================
06-06 14:11:46.658 E/mono-rt (32202): 
06-06 14:11:47.408 E/mono-rt (32236): Stacktrace:
06-06 14:11:47.408 E/mono-rt (32236): 
06-06 14:11:47.408 E/mono-rt (32236):   at <unknown> <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper managed-to-native) object.wrapper_native_0x40b3fcff (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper delegate-invoke) <Module>.invoke_intptr__this___intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236):   at Android.Runtime.JNIEnv.CallObjectMethod (intptr,intptr,Android.Runtime.JValue[]) <0x00053>
06-06 14:11:47.418 E/mono-rt (32236):   at Android.Content.Res.TypedArray.GetString (int) <0x00137>
06-06 14:11:47.418 E/mono-rt (32236):   at VeronaAndroid.ActionBar..ctor (Android.Content.Context,Android.Util.IAttributeSet) <0x003e7>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper dynamic-method) object.c18ea8f9-479a-40b0-b8ba-952b43959a31 (intptr,object[]) <0x0005f>
06-06 14:11:47.418 E/mono-rt (32236):   at Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0x000ff>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper native-to-managed) Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236):   at <unknown> <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper managed-to-native) object.wrapper_native_0x40b3ea19 (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper delegate-invoke) <Module>.invoke_void__this___intptr_intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236):   at Android.Runtime.JNIEnv.CallNonvirtualVoidMethod (intptr,intptr,intptr,Android.Runtime.JValue[]) <0x00067>
06-06 14:11:47.418 E/mono-rt (32236):   at Android.App.Activity.SetContentView (int) <0x001e3>
06-06 14:11:47.418 E/mono-rt (32236):   at VeronaAndroid.Activities.FirstRunActivity.OnCreate (Android.OS.Bundle) <0x00083>
06-06 14:11:47.418 E/mono-rt (32236):   at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (intptr,intptr,intptr) <0x0005b>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper dynamic-method) object.f77a069b-f67a-49ae-b059-c0c2ad5121d4 (intptr,intptr,intptr) <0x00043>
06-06 14:11:47.418 E/mono-rt (32236):   at (wrapper native-to-managed) object.f77a069b-f67a-49ae-b059-c0c2ad5121d4 (intptr,intptr,intptr) <0xffffffff>
06-06 14:11:47.418 E/mono-rt (32236): 
06-06 14:11:47.418 E/mono-rt (32236): =================================================================
06-06 14:11:47.418 E/mono-rt (32236): Got a SIGSEGV while executing native code. This usually indicates
06-06 14:11:47.418 E/mono-rt (32236): a fatal error in the mono runtime or one of the native libraries 
06-06 14:11:47.418 E/mono-rt (32236): used by your application.
06-06 14:11:47.418 E/mono-rt (32236): =================================================================
06-06 14:11:47.418 E/mono-rt (32236): 
06-06 14:11:48.149 E/mono-rt (32252): Stacktrace:
06-06 14:11:48.149 E/mono-rt (32252): 
06-06 14:11:48.149 E/mono-rt (32252):   at <unknown> <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper managed-to-native) object.wrapper_native_0x40b3fcff (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper delegate-invoke) <Module>.invoke_intptr__this___intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252):   at Android.Runtime.JNIEnv.CallObjectMethod (intptr,intptr,Android.Runtime.JValue[]) <0x00053>
06-06 14:11:48.149 E/mono-rt (32252):   at Android.Content.Res.TypedArray.GetString (int) <0x00137>
06-06 14:11:48.149 E/mono-rt (32252):   at VeronaAndroid.ActionBar..ctor (Android.Content.Context,Android.Util.IAttributeSet) <0x003e7>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper dynamic-method) object.29311cd3-3f86-4930-8673-a142b0089549 (intptr,object[]) <0x0005f>
06-06 14:11:48.149 E/mono-rt (32252):   at Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0x000ff>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper native-to-managed) Java.Interop.TypeManager.n_Activate (intptr,intptr,intptr,intptr,intptr,intptr) <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252):   at <unknown> <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper managed-to-native) object.wrapper_native_0x40b3ea19 (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper delegate-invoke) <Module>.invoke_void__this___intptr_intptr_intptr_intptr_JValue[] (intptr,intptr,intptr,intptr,Android.Runtime.JValue[]) <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252):   at Android.Runtime.JNIEnv.CallNonvirtualVoidMethod (intptr,intptr,intptr,Android.Runtime.JValue[]) <0x00067>
06-06 14:11:48.149 E/mono-rt (32252):   at Android.App.Activity.SetContentView (int) <0x001e3>
06-06 14:11:48.149 E/mono-rt (32252):   at VeronaAndroid.Activities.FirstRunActivity.OnCreate (Android.OS.Bundle) <0x00083>
06-06 14:11:48.149 E/mono-rt (32252):   at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (intptr,intptr,intptr) <0x0005b>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper dynamic-method) object.9b50c525-8996-48c2-8048-2f2a09e801f4 (intptr,intptr,intptr) <0x00043>
06-06 14:11:48.149 E/mono-rt (32252):   at (wrapper native-to-managed) object.9b50c525-8996-48c2-8048-2f2a09e801f4 (intptr,intptr,intptr) <0xffffffff>
06-06 14:11:48.149 E/mono-rt (32252): 
06-06 14:11:48.149 E/mono-rt (32252): =================================================================
06-06 14:11:48.149 E/mono-rt (32252): Got a SIGSEGV while executing native code. This usually indicates
06-06 14:11:48.149 E/mono-rt (32252): a fatal error in the mono runtime or one of the native libraries 
06-06 14:11:48.149 E/mono-rt (32252): used by your application.
06-06 14:11:48.149 E/mono-rt (32252): =================================================================
06-06 14:11:48.149 E/mono-rt (32252): 

obrechte

Posts: 3
Joined: Thu Jun 05, 2014 3:37 pm
Location:

HTPC Specs: Show details

#19

Post by obrechte » Tue Jun 17, 2014 2:05 pm

For anyone interested I did fix the problem.

With the new root for the gs4 I thought updating to 4.4.2 might solve the problem but it did not. Ultimately I reinstalled the app, uninstalled xposed, and the app worked after I went back through setup. I have since been able to reinstall xposed without any issue.

Scot7

Posts: 1
Joined: Mon Jul 07, 2014 2:41 pm
Location:

HTPC Specs: Show details

#20

Post by Scot7 » Mon Jul 07, 2014 2:45 pm

breakthestatic wrote:I'm experiencing the exact same issue with the latest oem software for my Verizon Moto X, which I believe uses f2fs as the filesystem for the data partition as well. Either way, this is a problem and needs to be remedied, but I don't think we'll see any action from Ceton though as they have gone dormant on the app since their android dev (James) left.
With Android L close to release, I began searching for the status on ART development as Dalvik is simply being removed from Android later this year - This is not the answer I was hoping to find.

Is Ceton going to re-open development or is the Android version now an EOL product?

Post Reply