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

Remove UID parameter for XPrivacy #2085

Closed
Cyclu opened this issue Dec 12, 2014 · 4 comments
Closed

Remove UID parameter for XPrivacy #2085

Cyclu opened this issue Dec 12, 2014 · 4 comments

Comments

@Cyclu
Copy link

Cyclu commented Dec 12, 2014

Can you remove please for "getPackagesForUid" UID parameter for XPrivacy itself there is too many lines in usage log about one hundred in two seconds. We lose many things in usage log and also it should be better for performance.

@M66B
Copy link
Owner

M66B commented Dec 13, 2014

I have looked into this, but I see no way to get the uid for XPrivacy from within the package manager without risking instability. Moreover, usage data about not enforced functions were added sometime ago, because there were complaints XPrivacy was not transparent about this, so I guess I cannot make everybody happy again :-(

@M66B M66B closed this as completed Dec 13, 2014
@Cyclu
Copy link
Author

Cyclu commented Dec 13, 2014

Your thoughts on the ability of disabling usage data log per application maybe with an quirk for example "nolog"? It's the most important thing and I think in this way everybody will be happy ;-) I have the logging always enabled because I like to take a glance at what things are going on but now is impossible to know for example what happened over night because the log is spammed with not about one hundred lines but with in my case 190 lines so as much as I have of applications and and it is at each launch of XPrivacy that the usage log begins with these lines 190 lines.

There is a misunderstanding I think about removing the UID parameters for XPrivacy itself for getPackagesForUid/Srv_getPackagesForUid which you have added in version 3.5.1

screenshot_2014-12-13-18-24-35

@Cyclu
Copy link
Author

Cyclu commented Dec 14, 2014

I have rechecked and these entry's going to occupy almost half of main usage data log because of this I can only see the last 40-60 minutes in global usage data and we lose a lot of valuable input.
We must scroll and scroll to see others entry's, additionally there is sometimes isolated entry between that long sequences of entry's so this becomes very painful to manage.
.

M66B added a commit that referenced this issue Dec 15, 2014
M66B added a commit that referenced this issue Dec 15, 2014
@hollal
Copy link

hollal commented Jan 16, 2015

Finally, I can stop Dolphin browser from spamming hundreds of /proc/* requests!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants