You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
Are you sure? It only happens if I use xprivacy. I'm using other modules (Greenify, BootManager, ...)
without problems.
On the other hand, I only see this problem with Android 5.1.1. On Android 4.3, xposed / xprivacy were
working without such issues.
With Android 5.1.1 cyanogen mod custom ROM, I noticed that glympse doesn't start properly if
XPrivacy is installed and enabled within the XPosed modules.
If XPrivacy is enabled, glympse starts and is terminated immediately.
If XPrivacy is disabled, glympse starts properly.
I used the xposed module xposed-v71-sdk22-arm-by-romracer-20150816.zip taken from http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979, together
with XposedInstaller_3.0_alpha4.apk from http://forum.xda-developers.com/showthread.php?t=3034811
The custom ROM that i'm using is taken from here: http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/exclusive-antaresone-alucard24-s-t3066696
Please find below the device info for my Samsung Galaxy S4 Smartphone and the error.log
file from XPosed.
build.board: MSM8960
build.bootloader: I9505XXUEMKE
build.brand: samsung
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: jfltexx
build.display: LMY48G
build.fingerprint: samsung/jfltexx/jflte:5.0.1/LRX22C/I9505XXUHOB7:user/release-keys
build.hardware: qcom
build.host: JDCTeam
build.id: LMY48G
build.manufacturer: samsung
build.model: GT-I9505
build.product: jflte
build.radio: unknown
build.serial: 4612052d
build.tags: test-keys
build.time: 1439821114000
build.type: userdebug
build.user: b--b
version.codename: REL
version.incremental: 9c1298432f
version.release: 5.1.1
version.sdk_int: 22
Error.log file from XPosed Framework:
The text was updated successfully, but these errors were encountered: