Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

XPrivacy force close #2087

Closed
jack980517 opened this issue Dec 14, 2014 · 14 comments
Closed

XPrivacy force close #2087

jack980517 opened this issue Dec 14, 2014 · 14 comments
Labels

Comments

@jack980517
Copy link

I'm using ver 3.5 of the app on PAC-ROM KitKat RC-3. XPosed framework version 58/54. Before an update (I'm not sure which one) XPrivacy works fine. Now it can't be run from the launcher icon (it force closes), while the restrictions I configured before the update is still functional. The notification is also being displayed properly whenever an app is upgraded or newly installed. Plz provide instructions on how to get log files, and I'll send it to you.

@M66B
Copy link
Owner

M66B commented Dec 14, 2014

There are instructions in the FAQ:
https://github.com/M66B/XPrivacy#FAQ14

@M66B M66B added the question label Dec 14, 2014
@M66B
Copy link
Owner

M66B commented Dec 15, 2014

Please note that I cannot do anything without logcat.
XPrivacy is tested by me and several other people and nobody has this problem.

@M66B
Copy link
Owner

M66B commented Dec 16, 2014

I am closing this issue for now, but if you provide a logcat I will look into it.

@M66B M66B closed this as completed Dec 16, 2014
@jack980517
Copy link
Author

I know the importance of logcat, that's why I wrote the last sentence. The problem is, however, that I cannot start XPrivacy at all (it force closes immediately), so it's not possible to "turn on debug logging". Any workaround?

@M66B
Copy link
Owner

M66B commented Dec 17, 2014

I don't think that debug logging is needed to find the cause of this.

@jack980517
Copy link
Author

@jack980517
Copy link
Author

I Ctrl-C'ed after the force close window showed up and I tapped OK.

@M66B
Copy link
Owner

M66B commented Dec 18, 2014

I/dalvikvm( 3448): Rejecting re-init on previously-failed class Lcom/saurik/substrate/MS$2; v=0x0
W/dalvikvm( 3448): Link of class 'Lcom/saurik/substrate/MS$2;' failed
F/libc    ( 3448): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 3499 (Thread-192)
I/dalvikvm( 3448): Failed resolving Lcom/saurik/substrate/MS$2; interface 1239 'Lcom/saurik/substrate/_MS$MethodHook;'
W/dalvikvm( 3448): Link of class 'Lcom/saurik/substrate/MS$2;' failed
I/DEBUG   (  192): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   (  192): Build fingerprint: 'google/occam/mako:4.4.2/KOT49H/937116:user/release-keys'
I/DEBUG   (  192): Revision: '11'
I/DEBUG   (  192): pid: 3448, tid: 3499, name: Thread-192  >>> biz.bokhorst.xprivacy <<<
I/DEBUG   (  192): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000

This problem is caused by Cydia Substrate.

@M66B
Copy link
Owner

M66B commented Dec 18, 2014

XPrivacy has limited, mostly untested, support for Cydia Substrate.
Cydia Substrate itself doesn't seem to be supported at all.
My advice: disable Cydia Substrate and use Xposed.

@jack980517
Copy link
Author

I have both Cydia Substrate and Xposed installed. I need Cydia Substrate for RootCloak Plus, which is the only working app I know to bypass root detection for the game, LoveLive. And Cydia Substrate doesn't have the option to disable modules individually, unlike Xposed. So to use XPrivacy I must abandon Cydia Substrate and LoveLive?

@jack980517
Copy link
Author

On Android 4.4, with the help of SELinuxModeChanger, Cydia Substrate can be used.
I found XPrivacy in the Xposed repo, and I didn't expect it to work with Cydia Substrate at all. Maybe you can add a switch in XPrivacy's settings to disable Cydia Substrate support for it?

M66B added a commit that referenced this issue Dec 18, 2014
@M66B
Copy link
Owner

M66B commented Dec 18, 2014

I don't want to support Cydia Substrate, since Cydia Substrate isn't supported itself too, so I have removed Cydia Substrate support altogether for the next release.
Test version: https://crowd.xprivacy.eu/XPrivacy_3.5.7c.apk
Please let me know if it works.

@jack980517
Copy link
Author

It works, but I have to disable it, reboot, enable it again, and reboot again. Just install and reboot will cause it to prompt that it's not enabled in XPosed installer, although it is enabled. Anyway, thanks for the effort!

@M66B
Copy link
Owner

M66B commented Dec 18, 2014

This is probably because you rebooted before Xposed detected the update.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants