Thanks for reporting this. The fact that there is no message makes it pretty hard to find out what the reason is as I don't have the game. So you (or somebody else experiencing this) would have to create a logcat of the crash, sometimes errors are mentioned only there.
--------------
As for docking crash: Pliind has sent me a logcat with this error:
Code:
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to instantiate receiver com.android.systemui.DreamsDockLauncher$DockEventReceiver: java.lang.ClassNotFoundException: com.android.systemui.DreamsDockLauncher$DockEventReceiver
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2251)
at android.app.ActivityThread.access$1500(ActivityThread.java:140)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4898)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1008)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:775)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:103)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException: com.android.systemui.DreamsDockLauncher$DockEventReceiver
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2246)
... 11 more
I checked his SystemUI.apk and indeed the class doesn't exist. However, the following appears in the AndroidManifest.xml of the same APK:
Code:
<receiver android:name=".DreamsDockLauncher$DockEventReceiver" android:exported="true">
<intent-filter>
<action android:name="android.intent.action.DOCK_EVENT" />
</intent-filter>
</receiver>
So the ROM is inconsistent. Basically,
this removal commit was only included partly.
Pliind then tested without Xposed and the same FC occured. So it's not Xposed's fault, this error just has to happen when a class is referenced but doesn't exist.
------------------
@daveid: Maybe you can check if your ROM has the same problem. The destroyed widgets are probably caused by the SystemUI crash. When mine crashes, it often resets the wallpaper on GoLauncher Ex.