Blank screen on startup with Xprivacy and SuperSU

[paour]

Xprivacy used to work fine. Then I installed SuperSU (from CM Superuser, based on the security fixes) and upgraded Xprivacy to 1.10.14 (from.12). Both of these became active on the same boot, so I can't distinguish the two. This is on CM 10.2 on i9300.

On boot, I do not get the SIM unlock prompt and the screen is black. After a while I can unlock the screen, but it remains black and only the Restart window can be used.

Disabling Xposed in recovery fixes the issue. Reinstalling it without activating Xprivacy also works. I successfully used TB to return to 1.10.12 but that didn't fix the issue.

SuperSU works adequately apart from this.

Another user (ikarus) captured a log trace:

I'm experiencing the same problem since yesterday (running PA 4.3 on my Nexus 10)
I've made a logcat

http://pastebin.com/E26A7khY

and another one with xprivacy debugging

http://pastebin.com/2AtURu0S

[M66B]

Did you try to clear XPrivacy data? (see the FAQ)

[M66B]

I don't see any problem in the provided logcats, except maybe this:

E/SELinux (  126): avc:  denied  { specifyids } for  scontext=u:r:system:s0 tcontext=u:r:system:s0 tclass=zygote
E/SELinux (  126): avc:  denied  { specifyseinfo } for  scontext=u:r:system:s0 tcontext=u:r:system:s0 tclass=zygote

I don't think these messages are related to XPrivacy, but to be sure I like to see a logcat with XPrivacy disabled.

[M66B]

"I successfully used TB to return to 1.10.12 but that didn't fix the issue.": this lets me wonder if XPrivacy is really the cause.

[M66B]

May be related to #785

[josoft-jos]

This sounds a lot like the problem I got after upgrade to 1.0.14. The only difference is that I had been running the latest supersu for a while before the upgrade.
https://dl.dropboxusercontent.com/u/67519405/xprivacy_logcat.log

[M66B]

Could you please try the test versions provided in issue #785 ?

[M66B]

W/ActivityManager(719):  Process ProcessRecord{42bc42d0 1334:com.android.bluetooth/1002} failed to attach
W/ActivityManager(719):  Forcing bringing down service: ServiceRecord{42bc32a0 u0 com.android.bluetooth/.pan.PanService}
W/ActivityManager(719):  Forcing bringing down service: ServiceRecord{42c7c560 u0 com.android.bluetooth/.hfp.HeadsetService}
W/ActivityManager(719):  Forcing bringing down service: ServiceRecord{434612e8 u0 com.android.bluetooth/.btservice.AdapterService}
W/ActivityManager(719):  Forcing bringing down service: ServiceRecord{43470810 u0 com.android.bluetooth/.a2dp.A2dpService}
W/ActivityManager(719):  Process ProcessRecord{42afb048 1349:com.getpebble.android/u0a10219} failed to attach
W/ActivityManager(719):  Forcing bringing down service: ServiceRecord{42bae3e8 u0 com.getpebble.android/.receivers.PebbleAccessibilityService}
D/PowerManagerService(719):  [api] Check if boot animation finished...
W/ActivityManager(719):  Process ProcessRecord{42b247c0 1362:com.dattasmoon.pebble.plugin/u0a10236} failed to attach
W/ActivityManager(719):  Forcing bringing down service: ServiceRecord{42b3e040 u0 com.dattasmoon.pebble.plugin/.NotificationService}
W/ActivityManager(719):  Process ProcessRecord{42b4e980 1379:net.dinglisch.android.taskerm/u0a10100} failed to attach
W/ActivityManager(719):  Forcing bringing down service: ServiceRecord{42b4c668 u0 net.dinglisch.android.taskerm/.MyAccessibilityService}
W/ActivityManager(719):  Process ProcessRecord{42add3f0 1394:biz.bokhorst.xprivacy:provider/u0a10244} failed to attach
I/ActivityManager(719):  Kill com.touchtype.swiftkey (pid 1118): provider biz.bokhorst.xprivacy.PrivacyProvider in dying process biz.bokhorst.xprivacy:provider
W/ActivityManager(719):  Unable to launch app biz.bokhorst.xprivacy/10244 for provider biz.bokhorst.xprivacy.provider: launching app became null

D/dalvikvm(719):  GC_CONCURRENT freed 3387K, 28% free 22609K/31076K, paused 5ms+9ms, total 120ms

' failed to attach' may be a memory issue:
https://groups.google.com/forum/#!msg/android-platform/XVlGKL3-iI0/ImfWwZkQLY4J

Maybe it is worth trying to make a backup of your device, wipe everything except system and only install Xposed and XPrivacy to see if this is working.

[josoft-jos]

Noandroid hangs and the other two works.
https://dl.dropboxusercontent.com/u/67519405/XPrivacy_1.10.17_noandroid.txt
https://dl.dropboxusercontent.com/u/67519405/XPrivacy_1.10.17_noprovider.txt
https://dl.dropboxusercontent.com/u/67519405/XPrivacy_1.10.17_nousagedata.txt

Didn't get any failed to attach this time.

[M66B]

Thanks for trying!
This does narrow down where to search in any case.
I will build another version to test to further narrow down where to search.

[josoft-jos]

I did another test with 1.10.16 a got failed to attach.

[M66B]

Could you please test these version too:
No extra usage data (Android): http://d-h.st/KuV
No extra usage data (all): http://d-h.st/tdd

[josoft-jos]

XPrivacy_1.10.17_nocwallusagedata works and the other don't.
https://dl.dropboxusercontent.com/u/67519405/XPrivacy_1.10.17_nocwallusagedata.txt
https://dl.dropboxusercontent.com/u/67519405/XPrivacy_1.10.17_nocwusagedata.txt

[donald67duck]

Imprecice, hope it helps:

Using Samsung Galaxy S3 Mini, i8190. Stock firmware, just rooted.

When starting it 2013-11-14 (maybe the 15th) I got the symtoms described by paour above. Managed to install a clockworkmod backup dated 2013-10-31. It booted in a normal way and still does after all the updates initiated by this outdated version of all apps. The difference is that I KEPT VERSION 1.10 of Xprivacy. Now running Google Play services version 4.0.33 and SuperSU version 1.69.

Don't know if it is connected but before installing the backup avast!Mobile Security behaved in an erratic way. The icon at the top of the screen not always appearing. Behaves OK now.

[M66B]

@donald67duck (kwek, kwek ;-) thanks for reporting. It is consistent with my conclusion.

My best guess is that this version will solve the problem: http://d-h.st/Zsa
There is a new setting "Extra usage data", if you enable it then the problem should be there again.

[josoft-jos]

That works. If I enable the setting it still works but seems to take longer to boot. I haven't measured it's just how it feels.

[M66B]

Thanks for reporting back!

[donald67duck]

OK, you have closed the thread, anyhow you were right:

1.10.18 worked. Enabling "Extra usage data" and booting gave the blank
screen again.

On 2013-11-17 19:52, Marcel Bokhorst wrote:

@donald67duck https://github.com/donald67duck (kwek, kwek ;-) thanks
for reporting. It is consistent with my conclusion.

My best guess is that this version will solve the problem:
http://d-h.st/Zsa
There is a new setting "Extra usage data", if you enable it then the
problem should be there again.

—
Reply to this email directly or view it on GitHub
#783 (comment).