Initial lag

[Tassos-i]

Normally, after rebooting and entering my pin code, my I9505 needs about 2 secs to confirm that date and time have been updated and another 2-3 secs to confirm that wifi has been connected as well as to activate "day by day" app widget.
However, upon activating xprivacy, date and time confirmation still come after 2 secs, BUT wifi confirmation and widget activation come after a whole 90 secs !!! And it is indifferent if I have restricted or not some permissions in "day by day" (identification, phone).
Is this normal behavior ?

[M66B]

Could you let me know if version 0.30 fixes this problem?
This version will be released today (soon probably).

[Tassos-i]

No. v0.30 fixed for me the skype problem, but not at all this one.

[M66B]

Could you please try if this version fixes the lag?

http://www.faircode.eu/xprivacy/XPrivacy_0.30.1.apk

[28Black]

Hi, I got the same problem here! (Galaxy S3, StockROM)
I just installed v0.30, but nothing has changed.
After reboot, apps which will start by default, such as avast!, Green Power Premium etc. need an extremely long time to be loaded! All widgets as well.

Usually, the entire boot process was completed after 5 to 10 seconds.
Now it takes more than 2 minutes! :/

I'll now test your v0.30.1 and then give a feedback!

[28Black]

I'm sorry to say this, but the problem persists! :(

[M66B]

Can you please try this version too:

http://www.faircode.eu/xprivacy/XPrivacy_0.30.2.apk

(I am trying to pinpoint the problem)

[M66B]

Could you please capture a logcat from the moment you turn your device on?
On the command line, assuming adb (part of the Android SDK) is installed:

adb logcat | grep XPrivacy

Please post it on pastebin or similar and link it from this issue.

[28Black]

Of course! One moment please;)

[M66B]

Maybe a complete logcat is better.

[28Black]

I am not familiar with "logcat". Can you tell me the detail how I need to use it?

[M66B]

http://forum.samdroid.net/f38/tutorial-how-get-logcat-example-check-battery-drain-2543/

But replace the command by

adb logcat

And enter that before you turn on your device

[28Black]

The problem still persists!

[28Black]

I'm going to make a logcat. I am concerned about my privacy, can I send you the results by e-mail? (Maybe a trash-mail;))

[M66B]

It would be a little stupid to say 'no' ;-)
Send me a PM through GitHub or XDA and I will reply with my e-mail address.

[28Black]

I send you a PM through XDA ;)

[28Black]

I have a little problem. Not the entire log is displayed in my cmd! How can extract the complete log?

[M66B]

Try this:

adb logcat >path/to/some_file.txt

You want see output, it will go into the file

[28Black]

It's working, I'll let you know when I send the mail (~ 5 min ;) )

[28Black]

Send! Let me know when it's arrived! :)

[28Black]

Got it?

[M66B]

Yes, I will look into it, thanks.

[28Black]

Okay, :)

[M66B]

I have been staring to the logcat for a while, but I see nothing strange related to XPrivacy.

Super user is repeatably denied, so maybe that is the cause.

To be sure, make a backup of XPrivacy (or export the settings if you can) and reset the settings of XPrivacy as described in the FAQ and reboot to see if this problem is still there. If you are concerned about your privacy, disable all networks before resetting the setting of XPrivacy. If the delay is still there, then disable XPrivacy using the Xposed installer and reboot again.

I could be that some restriction is causing this.

[28Black]

Super user is repeatably denied, so maybe that is the cause
--> It was intended that way ;) The App "Triangle Away Pro" from the godfather Chainfire disables root for several min after reboot, so the system status remains "original". That allows me to use OTA Updates and several "special" apps ;)

The problem now seems to be curbed.
I backed up Xprivacy (app + data). Then I uninstalled it (for testing) and rebooted. Et voilà, my S3 booted
largely "normal".
The whole boot procedure now takes only about 10 to 15 seconds longer than previously (without Xposed Framework & Privacy).
I have reinstalled and reconfigured Xprivacy and it has remained at the aforementioned time.

[M66B]

Thanks for reporting back!
I am glad this problem is solved.