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

Xprivacy maybe causing OmniROM ActiveDisplay to crash SystemUI #951

Closed
theCroh opened this issue Dec 14, 2013 · 7 comments
Closed

Xprivacy maybe causing OmniROM ActiveDisplay to crash SystemUI #951

theCroh opened this issue Dec 14, 2013 · 7 comments
Labels

Comments

@theCroh
Copy link

theCroh commented Dec 14, 2013

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

@theCroh
Copy link
Author

theCroh commented Dec 14, 2013

A little more detail. Reproduction:

  1. Lock the phone
  2. Get a notification to pop up in ActiveDisplay (I've tried at least with Play Store and Xprivacy notifications and SMS)
  3. Click on the notification.
  4. Android shows the SystemUI crash notification.
  5. The phone shows an unlocked view for a while, the notification bar and softkeys disappear and the phone goes to lockscreen.

@theCroh
Copy link
Author

theCroh commented Dec 14, 2013

The exact notification in step 4. is "Unfortunately, the process com.android.systemui has stopped."

@M66B
Copy link
Owner

M66B commented Dec 14, 2013

Please provide a new log with XPrivacy logging enabled (menu > settings).

@M66B
Copy link
Owner

M66B commented Dec 14, 2013

Scratch that, I already found the cause.

M66B pushed a commit that referenced this issue Dec 14, 2013
@M66B
Copy link
Owner

M66B commented Dec 14, 2013

Can you please try if this version fixes your problem: http://d-h.st/7xB

@theCroh
Copy link
Author

theCroh commented Dec 14, 2013

Unfortunately that didn't work. Here's the log with XPrivacy logging enabled:
https://dl.dropboxusercontent.com/u/56292020/2013-12-14-22-14-14.txt

@M66B
Copy link
Owner

M66B commented Dec 14, 2013

The follow up exception in XPrivacy is gone now in any case.

The real problem is within the ROM itself:

12-14 22:13:39.369 E/AndroidRuntime(2441): FATAL EXCEPTION: main
12-14 22:13:39.369 E/AndroidRuntime(2441): Process: com.android.systemui, PID: 2441
12-14 22:13:39.369 E/AndroidRuntime(2441): android.content.res.Resources$NotFoundException: Array resource ID #0x0

This has nothing to do with XPrivacy (but maybe it has to do with Xposed).

@M66B M66B closed this as completed Dec 14, 2013
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