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

"Privacy service not found" issue #1602

Closed
baleu opened this issue Mar 26, 2014 · 8 comments
Closed

"Privacy service not found" issue #1602

baleu opened this issue Mar 26, 2014 · 8 comments
Labels

Comments

@baleu
Copy link

baleu commented Mar 26, 2014

Xprivacy won't work anymore since I updated from 1.10.38 to versions 2.0 or higher.

Shown errors:
"Xprivacy not activated" and
"Device reboot necessary. Privacy service not found."

Log:
https://gist.github.com/baleu/9787358

UID: 10057
(lines 26, ~500, ~1100 onwards may be interesting)

Of course, I shortened the log, I hope it's informative.

@M66B
Copy link
Owner

M66B commented Mar 26, 2014

The problem is this:

Could not find class 'android.os.UserHandle', referenced from method biz.bokhorst.xprivacy.fz.a

Your SDK version is 16, but this class is added in API level 17. XPrivacy checks for this version number, but apparently this is not enough. I will change the code to fix this.

@M66B
Copy link
Owner

M66B commented Mar 26, 2014

Can you please try if this version fixes the problem: http://d-h.st/xfi

@baleu
Copy link
Author

baleu commented Mar 26, 2014

Thanks for the really fast try, but it does not yet seem to fix it. As far as I can see, the exact same line does not appear again. I'll provide another log in a few hours, or maybe tomorrow.

@M66B
Copy link
Owner

M66B commented Mar 26, 2014

Try disabling all other Xposed modules to see if any of them is causing this problem. If that doesn't help please provide a new logcat.

@baleu
Copy link
Author

baleu commented Mar 26, 2014

Xprivacy as only module did not change anything - so no other modules seem to interfere.

New Log:
https://gist.github.com/baleu/9794720

My guess: the interesting part starts at line 675.

@M66B
Copy link
Owner

M66B commented Mar 27, 2014

XPrivacy is loaded without error messages now, but there is no trace of XPrivacy execution in the logcat. I have no idea why. This happens when LBE is installed, so make sure it isn't installed or bundled with your ROM.

If you were upgrading, it might be worth to try removing XPrivacy, reboot, install the new version, execute it once and reboot.

@M66B
Copy link
Owner

M66B commented Mar 27, 2014

This version won't fix the problem, but has extra logging, so we can see whether XPrivacy is started by Xposed or not: http://d-h.st/hdU
Can you please capture a new logcat with this version?

@baleu
Copy link
Author

baleu commented Mar 27, 2014

OK, I'm a bit embarassed right now. Your comment about LBE made me think. Before Xposed was available for my x86-phone and therefore before I was able to use XPrivacy, I tried LBE. It feels like this was ages ago, so I did not really think there could be anything left.
To cut to the chase: apparently, I did not uninstall LBE, I rather froze it via Titanium Backup. It's gone now and everything works perfectly.

Thanks a lot for solving my problem and sorry for the inconvenience - I'm quite mad at myself. If I hadn't already donated for the Pro licence two weeks ago, I certainly would do so now ;)

@M66B M66B closed this as completed Mar 27, 2014
Phylon pushed a commit to Phylon/XPrivacy that referenced this issue Mar 31, 2014
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