-
Notifications
You must be signed in to change notification settings - Fork 527
"Privacy service not found" issue #1602
Comments
The problem is this:
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. |
Can you please try if this version fixes the problem: http://d-h.st/xfi |
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. |
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. |
Xprivacy as only module did not change anything - so no other modules seem to interfere. New Log: My guess: the interesting part starts at line 675. |
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. |
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 |
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. 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 ;) |
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.
The text was updated successfully, but these errors were encountered: