This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 527
Xprivacy maybe causing OmniROM ActiveDisplay to crash SystemUI #951
Labels
Comments
A little more detail. Reproduction:
|
The exact notification in step 4. is "Unfortunately, the process com.android.systemui has stopped." |
Please provide a new log with XPrivacy logging enabled (menu > settings). |
Scratch that, I already found the cause. |
M66B
pushed a commit
that referenced
this issue
Dec 14, 2013
Can you please try if this version fixes your problem: http://d-h.st/7xB |
Unfortunately that didn't work. Here's the log with XPrivacy logging enabled: |
The follow up exception in XPrivacy is gone now in any case. The real problem is within the ROM itself:
This has nothing to do with XPrivacy (but maybe it has to do with Xposed). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I get a SystemUI crash every time I try to open a notification from ActiveDisplay. I'm on OmniROM 20131214 and Xprivacy 1.10.43. I'm not quite the right person to interpret the logcat but there's always something about Xprivacy just before the crash.
Log from the newest Omni with newest Xprivacy:
https://dl.dropboxusercontent.com/u/56292020/2013-12-14-14-39-59.txt
Older logs:
https://dl.dropboxusercontent.com/u/56292020/2013-12-13-23-43-31.txt
https://dl.dropboxusercontent.com/u/56292020/2013-12-12-23-52-18.txt
The text was updated successfully, but these errors were encountered: