I can install Carbon ROM or AOKP and test if you want, but last time I tried with all my apps the SysteUI startup delay still happened even without Xposed but was way shorter (a few seconds), cause of that I moved to AOSP+ till now, but that didn't get updated so I switched to SlimBean now till we get android 4.4, then I'll go back to pure AOSP/AOSP+ (if it gets updated), cause of your framework I could give up "AOSP custom roms" like AOKP and Carbon for roms as close to pure AOSP as possible. Anyway tell me if you want me to test AOKP or Carbon, but it will take me a whole night to restore all my apps with titanium after I flash?
Someone I know currently has a Galaxy S4 complete stock with 4.3. He has knox on his phone.
Let's say I root his phone with the method that does not trip the knox counter (rooted with knox 0x0). If I install the Xposed framework and the modules, will it trip the knox counter?
@rovo89, I am not sure is this error is Materdualfix's or Xposed's. Please check.
----------------- 30 Nov 2013 05:39:15 UTC Loading Xposed v41 (for Zygote)... Loading modules from /data/app/com.dr8.sbicons.sgs-1.apk Loading class com.dr8.sbicons.sgs.mod.StatusBarMods Loading modules from /data/app/com.oasisfeng.greenify-2.apk Loading class com.oasisfeng.greenify.pro.FrameworkPatch Loading modules from /data/app/ma.wanam.youtubeadaway-2.apk Loading class ma.wanam.youtubeadaway.module.Xposed Loading modules from /data/app/tungstwenty.xposed.masterkeydualfix-1.apk Loading class tungstwenty.xposed.masterkeydualfix.XposedMod java.lang.IllegalStateException: Cannot broadcast before boot completed at com.android.server.am.ActivityManagerService.verifyBroadcastLocked(ActivityManagerService.java:13982) at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:14000) at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method) at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:547) at com.android.server.am.ActivityManagerService.broadcastIntent(Native Method) at com.oasisfeng.greenify.pro.i.a(SourceFile:33) at com.oasisfeng.greenify.pro.a.r.a(SourceFile:58) at com.oasisfeng.b.a.afterHookedMethod(SourceFile:27) at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:561) at com.android.server.am.ActivityManagerService.startProcessLocked(Native Method) at com.android.server.am.BroadcastQueue.processNextBroadcast(BroadcastQueue.java:777) at com.android.server.am.BroadcastQueue$1.handleMessage(BroadcastQueue.java:129) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:137) at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1557) -----------------
I am having some serious issues with bootloops, this if my 5th on 3 days and I suspect that it might have to do something with xposed. The only problem I have is when I get one I have to format /data and I believe its where xposed is keeping its logs? I am now using ADB on a windows machine and I have not yet formatted /data. How do I pull the logs with ADB? I have tried "adb logcat.txt /C:\ but that doesn't work.. Maybe I have usb debugging deactivated... I can't see the logs if I try adb -s Xposed aswell.
|don't ask questions about modules here!!!, framework, xposed|
|Thread Tools||Search this Thread|