[APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager

Search This thread

Poebat

Senior Member
Jan 15, 2016
476
72
It has been answered here.
BTW, the information about it might be worth mentioning in the first post to prevent (at least most) of next such questions.


Try for example NetGuard or AFWall+.
But that is not a place for such discussion. Stick to the thread.
I'll try NetGaurd. Unfortunately AFWall+ doesn't work for me. I know that app ops lets you disable cellular data so I was hoping OP could plug into that.
 

k-ninja

Senior Member
Jul 27, 2011
65
13
Melbourne
@M66B, Firstly I would like to say massive thanks for you work on this project. The speed of improvements and updates so far has been amazing. I have donated and hope you will continue your great work.

Can you please explain what is the expected behavior for "restrict camera"? I tried setting this on the stock camera app (Lineagos 15.1), but was still able to use the view finder and take a photo with the app, even after rebooting. My device is a Oneplus 5T, with Lineageos 15.1 (oreo 8.1), xposed 90-1 beta, and XPL 0.16.

I guess on a related note I should ask, is 8.1 officially supported by XPL yet?

As far as the conversation about privacy vs security - I work in security too and I know it's a bit of a grey area. IMO, there is overlap, especially when it comes to certain information. In the context of IMEI numbers, in Australia (where I live), an IMEI can easily be used to identify "who I am", because the carrier can tie your IMEI to your phone number, and your phone number is tied to your identity (you can't activate a phone SIM without providing ID like drivers license number). FWIW I think it would be worth keeping the ability to restrict this information in XPL, but I respect your decision either way to write your app the way you want.
 
  • Like
Reactions: Namnodorel

mnjm9b

Senior Member
Apr 26, 2008
1,046
227
There is an obvious knee jerk reaction to learning how apps are allowed to have free reign to personal data.

we want to SHUT IT DOWN
completely and totally...

the big issue is Google allowing such a thing to happen in the first place.

there should be no need for privacy apps such as this.

It's pretty obvious that the real reason that Google allows this is because there is money to be made from personal data.

they profit from it.

so unless there is some massive lawsuit to force Google to fix the problem this is what we have.

While Google has given a lot of control over this compared to earlier Android versions.
there are still issues with many apps crashing if those permissions are denied.
Google could fix this on their end or force app developers to comply.

in the meantime we have A wonderful Dev here that is providing an alternative.
If people want to get mad at someone get mad at Google.

Marcel is pretty much the Only one really addressing this.

Of ALL THE DEVS IN THE WORLD he is the only one carrying the torch on this.
(I can't for the life if me understand why NO ONE steps up to help)

so now that's out of the way...

I understand some people feel panic thinking that Marcel is leaving them vulnerable with his decisions on some things.
HOWEVER, there is no excuse for being RUDE, DISRESPECTFUL and just plain MEAN.

To be honest, I am surprised he doesn't just pull the plug and develop just for his personal use...and forget sharing with all you ungrateful whiners.

that is all....


(and yes I know there are a few other apps that try to address privacy but NOTHING like what we have here AND OPEN SOURCE TOO)
 

kaskalow

Member
Nov 13, 2016
17
0
There is an obvious knee jerk reaction to learning how apps are allowed to have free reign to personal data.

we want to SHUT IT DOWN
completely and totally...

the big issue is Google allowing such a thing to happen in the first place.

there should be no need for privacy apps such as this.

It's pretty obvious that the real reason that Google allows this is because there is money to be made from personal data.

they profit from it.

so unless there is some massive lawsuit to force Google to fix the problem this is what we have.

While Google has given a lot of control over this compared to earlier Android versions.
there are still issues with many apps crashing if those permissions are denied.
Google could fix this on their end or force app developers to comply.

in the meantime we have A wonderful Dev here that is providing an alternative.
If people want to get mad at someone get mad at Google.

Marcel is pretty much the Only one really addressing this.

Of ALL THE DEVS IN THE WORLD he is the only one carrying the torch on this.
(I can't for the life if me understand why NO ONE steps up to help)

so now that's out of the way...

I understand some people feel panic thinking that Marcel is leaving them vulnerable with his decisions on some things.
HOWEVER, there is no excuse for being RUDE, DISRESPECTFUL and just plain MEAN.

To be honest, I am surprised he doesn't just pull the plug and develop just for his personal use...and forget sharing with all you ungrateful whiners.

that is all....


(and yes I know there are a few other apps that try to address privacy but NOTHING like what we have here AND OPEN SOURCE TOO)


Who makes the law?

Google has the money, so google makes the law, selling our personal data, Marcel is the Tesla in our time, fighting against Google and other more biggest company, eg: Facebook, Instagram, etc they all colaborate togheter with Google colecting Data (Data=Information)

Information means POWER and Control and of course result Money that we can't afford to pay Marcel to fight against the biggest company such as Google ...

You can't Imagine how much money Google have , by the way Google is among us. :)

Good work Marcel you are Tesla, Don't give up, the World is and will be thankfull with all your work, I make donation to you!
 
Last edited:

popveneer

Member
Apr 5, 2016
11
1
@M66B

Congrats Marcel on the new app. Donated €10 before I even installed. Just knowing that you are putting energy into this again is exciting.

I echo mnjm9b's observation that very very few are working on this front. I thank you. Godspeed.
 
  • Like
Reactions: M66B

M66B

Recognized Developer
Aug 1, 2010
23,754
48,652
...

Can you please explain what is the expected behavior for "restrict camera"? I tried setting this on the stock camera app (Lineagos 15.1), but was still able to use the view finder and take a photo with the app, even after rebooting. My device is a Oneplus 5T, with Lineageos 15.1 (oreo 8.1), xposed 90-1 beta, and XPL 0.16.

...
XPrivayLua should report that the camera is not available on open for both camera API 1 and 2. Could you please try to install a camera app from the Play store like Open Camera and check if you have the same problem? It could be that the stock camera app is using other, non public APIs.

I guess on a related note I should ask, is 8.1 officially supported by XPL yet?
I test and use XPrivacyLua on my Nexus 5X with Android 8.1 Oreo.
 
Last edited:

M66B

Recognized Developer
Aug 1, 2010
23,754
48,652
I have just released beta version 0.17 in the Xposed repository.

Changelog:
  • Added restrictions for tasks, services and processes (get applications)
  • Added restriction for voicemails (get messages)
  • Added restriction for SMSes stored on the SIM card (get messages)
  • Showing notification on attempt to record audio/video or use camera
  • Disabled restrictions for sensors and phone data
  • Small improvements and minor bug fixes
  • Updated translations
All details: https://github.com/M66B/XPrivacyLua/commits/master
 

Primokorn

Senior Member
  • Nov 17, 2012
    11,434
    7,680
    Sorry if it has already been discussed but my eyes are too much tired to read useless posts.

    A couple of things:
    1. I guess it could be a good thing to put the same protection as XPrivacuLua package for Xposed / get applications. Can XPL work if Xposed Installer doesn't get the list of installed apps?
    2. I get several error messages on some restrictions. The one attached is for Yalp Store and the Read contacts access.
    Errors on calendars, call log, contacts and messages for NetGuard.
     

    Attachments

    • Screenshot_20180112-081218.png
      Screenshot_20180112-081218.png
      26.6 KB · Views: 292

    M66B

    Recognized Developer
    Aug 1, 2010
    23,754
    48,652
    Sorry if it has already been discussed but my eyes are too much tired to read useless posts.

    A couple of things:
    1. I guess it could be a good thing to put the same protection as XPrivacuLua package for Xposed / get applications. Can XPL work if Xposed Installer doesn't get the list of installed apps?
    2. I get several error messages on some restrictions. The one attached is for Yalp Store and the Read contacts access.
    Errors on calendars, call log, contacts and messages for NetGuard.
    1. I am not sure what you mean, but it doesn't seem a wise idea to restrict the Xposed installer, although it might just work.
    2. Please capture a logcat. Which device/Android version did you get this on?
     

    Primokorn

    Senior Member
  • Nov 17, 2012
    11,434
    7,680
    1. I am not sure what you mean, but it doesn't seem a wise idea to restrict the Xposed installer, although it might just work.
    2. Please capture a logcat. Which device/Android version did you get this on?
    1.I know but an ounce of prevention is worth a pound of cure.
    2. OP3T / Android 7.1.2. Log attached. Test done with Yalp Store and I stopped it as soon as I got the notification.

    EDIT: for unknown reasons the checkbox of Record audio is now grey for all restricted apps. I neither reboot nor update the XPL...
     

    Attachments

    • Screenshot_20180112-091036.png
      Screenshot_20180112-091036.png
      23.4 KB · Views: 416
    • Log_2018-01-12_09-10-22.txt
      41.9 KB · Views: 10
    Last edited:

    M66B

    Recognized Developer
    Aug 1, 2010
    23,754
    48,652
    1.I know but an ounce of prevention is worth a pound of cure.
    2. OP3T / Android 7.1.2. Log attached. Test done with Yalp Store and I stopped it as soon as I got the notification.

    EDIT: for unknown reasons the checkbox of Record audio is now grey for all restricted apps. I neither reboot nor update the XPL...
    You can ignore the error message and it will be gone in the next release.

    There was a note about the Record audio restrict before: just toggle the check box off and on to get it fixed.
     

    Primokorn

    Senior Member
  • Nov 17, 2012
    11,434
    7,680
    There was a note about the Record audio restrict before: just toggle the check box off and on to get it fixed.
    I know but what's the reason? (since I didn't do anything special)
    The check box for these restrictions will show grey to indicate that not all hooks are applied
    All restrictions were applied a few minutes ago so all hooks were applied. :confused:
     

    Relativitiy

    Member
    Apr 10, 2015
    16
    3
    @M66B
    Sir or madam,
    I know you want to keep your spare time to you, and you are absolutely right with that. I just want to tell you these:
    You said, you already did the "Custom Restrictions" API thingy. And you already did implemented telephony data restriction. Can't you turn it to a Custom Restriction for one time and only, and not maintain it.

    All I am asking is this, just make one last effort and so we could use these restrictions as custom restrictions. I dont know lua, I dont even know any language but I am thinking to learn it just for the sake of this app. Its your time, but you already spent your time on this.

    Thanks for this project.
     

    k-ninja

    Senior Member
    Jul 27, 2011
    65
    13
    Melbourne
    XPrivayLua should report that the camera is not available on open for both camera API 1 and 2. Could you please try to install a camera app from the Play store like Open Camera and check if you have the same problem? It could be that the stock camera app is using other, non public APIs.

    I can confirm that the restirction seems to work for Open Camera, app asks for camera permission, even when I allow it, the screen is black and camera controls unresponsive :good: Is there anything I can do to help identify the API calls for the LOS stock camera?

    I test and use XPrivacyLua on my Nexus 5X with Android 8.1 Oreo.

    Good to know, I will keep using the same then.

    I upgraded to v0.17 tonight, and now almost every app is throwing up exceptions for Privacy.ContentResolver.query1/[calendar|call_log|voicemail|contacts]. In the XPL app there is a very long stack trace which I can view by clicking the ! icon. I haven't captured a log cat at this point, as I think maybe you have already indicated the issue will go away next release in another post, but please let me know if you would like one.
     

    Primokorn

    Senior Member
  • Nov 17, 2012
    11,434
    7,680
    You can ignore the error message and it will be gone in the next release.
    Too much error messages... My phone doesn't respond anymore.
    Is there a file that I can remove from TWRP file manager to? Or do I have to delete the whole app and start again from scratch?
    "eu.faircode.xlua_preferences.xml" maybe?
     
    Last edited:

    scutworker

    Senior Member
    Jan 5, 2010
    619
    231
    Too much error messages... My phone doesn't respond anymore.
    Is there a file that I can remove from TWRP file manager to? Or do I have to delete the whole app and start again from scratch?
    "eu.faircode.xlua_preferences.xml" maybe?
    Same problem: errors all over the place and the restrictions weren't working either. Deleted app, installed older version and set up again

    Sorry, but no logcat this time: need my phone for work today and have to have it all working
    .
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 9
      I am visiting this thread rarely anymore because most comments are about Xposed and not about XPrivacyLua. So, if it takes a long time until you get an answer from me, you know why now. If you don't get an answer at all, it is most likely about an Xposed issue.
      6
      Can you demonstrate where you see the Xposed issue so I can log a bug with them?
      This thread is full of comments about this problem, but the Xposed developers are too busy fighting with each other. Basically, XPrivacyLua itself isn't hooked.

      Read a little back here to see which version/combinations Riru/Xposed work.
      4
      Okay, it is really enough now. I won't follow this thread anymore. If you need support, you can use the support menu item in the pro companion app.
      4
      i think by Android(framework) it means Google Service Framework (com.google.android.gsf)
      Android framework is Android system, not GSF.
      3
      I tried the clipboard and recorded it on WeChat, but Suning did not. . . .

      I found this error code
      Code:
      04-10 11:45:26.389  5323  5323 I EdXposed: Riru hooks installed
      04-10 11:45:26.452  5323  5323 I EdXposed: ART hooks installed
      04-10 11:45:26.522  5311  5311 I EdXposed-Bridge: XLua.Xposed Loaded com.android.traceur:10090
      04-10 11:45:26.532  5323  5323 I EdXposed: Loading modules for com.suning.mobile.ebuy
      04-10 11:45:26.532  5323  5323 I EdXposed-Bridge: Loading modules from /data/app/~~hcjuv6HzQbZOKMB3ug7WSw==/eu.faircode.xlua-vNspZ6pSQTrjHf23gYkdcA==/base.apk
      04-10 11:45:26.572  5323  5323 I EdXposed-Bridge:   Loading class eu.faircode.xlua.XLua
      04-10 11:45:26.806  5359  5359 I EdXposed: Start to install inline hooks
      04-10 11:45:26.806  5359  5359 I EdXposed: Using api level 30
      04-10 11:45:26.806  5359  5359 I EdXposed: Start to install Riru hook
      04-10 11:45:26.907  5323  5323 E EdXposed: error when hooking bindApp: pkg=com.suning.mobile.ebuy, prc=com.suning.mobile.ebuy
      04-10 11:45:26.907  5323  5323 E EdXposed: java.lang.ArrayIndexOutOfBoundsException: length=1052; index=1263817555
      04-10 11:45:26.907  5323  5323 E EdXposed:     at pxb.android.axml.AxmlParser.getNamespacePrefix(AxmlParser.java:151)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at pxb.android.axml.AxmlReader.accept(AxmlReader.java:80)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at com.elderdrivers.riru.edxp.util.MetaDataReader.<init>(MetaDataReader.java:27)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at com.elderdrivers.riru.edxp.util.MetaDataReader.getMetaData(MetaDataReader.java:19)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at com.elderdrivers.riru.edxp._hooker.impl.HandleBindApp.beforeHookedMethod(HandleBindApp.java:69)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at de.robv.android.xposed.XC_MethodHook.callBeforeHookedMethod(XC_MethodHook.java:51)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at com.swift.sandhook.xposedcompat.hookstub.HookStubManager.hookBridge(HookStubManager.java:361)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at SandHookerNew_42b8453bf7df105343083f1377c32094be493c49.hook(Unknown Source:51)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at android.app.ActivityThread.access$1300(ActivityThread.java:237)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at android.os.Handler.dispatchMessage(Handler.java:106)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at android.os.Looper.loop(Looper.java:223)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at android.app.ActivityThread.main(ActivityThread.java:7660)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at java.lang.reflect.Method.invoke(Native Method)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
      04-10 11:45:26.907  5323  5323 E EdXposed:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
      04-10 11:45:26.935  5359  5359 I EdXposed: Riru hooks installed
      04-10 11:45:26.983  5359  5359 I EdXposed: ART hooks installed
      This is a bug in Riru.
    • 299
      XPrivacyLua

      banner_play_store.png


      Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy).

      Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data instead of real data.

      Features:

      • Simple to use
      • Manage any user or system app
      • Extensible
      • Multi-user support
      • Free and open source

      See here for all details, including installation instructions and download link.

      Please read the frequently asked questions before asking a question.

      This XDA thread is about using the latest version of XPrivacyLua. Off topic comments are allowed as long they are related to XPrivacyLua and are in the general interest of the followers of this thread, but anything not related to privacy is not allowed. However:

      Discussions about Xposed are not allowed here, please use the Xposed forums instead.

      If XPrivacyLua doesn't work and/or when "module not running or updated" is shown, this is almost always caused by an Xposed problem.

      Discussions about purchases are not allowed here, please contact me via here instead.

      XPrivacyLua is being maintained and supported, but new features won't be added anymore.

      Custom hook definitions will always be part of XPrivacyLua, but there will be community support only. This means that I won't respond to questions about defining custom hooks anymore. See this thread for the reasons.

      If you value your privacy, please consider to support this project with a donation or by purchasing pro features.

      XPrivacyLua is not a permission manager, but a privacy manager. XPrivacyLua doesn't block things and doesn't revoke permissions, but does replace real data by fake data. This means you can grant Android permissions to an app and still let XPrivacyLua prevent the app from seeing privacy sensitive data. Revoking permissions can result in an app refusing to work and/or to crash. However, replacing real by fake data generally doesn't let an app crash.

      Currently restrictions are quite crude because they mostly replace real data by no data. For example restricting the contacts app from getting contacts will result in an empty contact list. In the near future it might be made possible to select the data an app may see, for example just one group of contacts.

      About feature requests and bug reports:

      The goal is to have a tool that can properly protect the privacy of many in the near future. However, it isn't paid work, so I do whatever I like whenever I like it.

      You can request features in this XDA forum. I will read them, but I will not respond to them and they might or might not be implemented. If I know for sure something will not be implemented, I will let you know.

      You can report any problem you have here. There will be no issue tracker on GitHub.

      For now I have decided to not implement restrictions that are useful to prevent tracking only. There are simply too many data items that can be used for tracking and it would take too much time to develop restrictions for all these data items.

      The basic idea is to restrict only things that 'define' you, so which contacts you have, where you are, which apps you use, etc.

      Maybe we can widen the definition of things that the core of XPL covers to "What defines you, and what can be used to spie on you"? This would include camera/audio, but not tracking.

      XPrivacyLua is pretty feature complete and will be maintained and supported and when there is a need new hook definitions will be added to better protect your privacy. For the rest this FAQ applies:

      https://github.com/M66B/XPrivacyLua/blob/master/FAQ.md#FAQ4

      As said before, development will also depend on Xposed development, which is just minimal unfortunately.

      XDA thanks and donations are appreciated.

      XPrivacyLua is supported with Xposed only. There is no support for VirtualXposed and TaiChi.


      XDA:DevDB Information
      XPrivacyLua, Xposed for all devices (see above for details)

      Contributors
      M66B
      Source Code: https://github.com/M66B/XPrivacyLua

      Xposed Package Name: eu.faircode.xlua

      Version Information
      Status:
      Beta

      Created 2018-01-05
      Last Updated 2020-03-10
      68
      I have just released beta version 0.5 in the Xposed repository.

      The XPrivacyLua framework and user interface seems to be stable enough to call this a beta release.

      Besides several bug fixes and improvements two new restrictions were added:
      • Read account name, which mostly holds your e-mail address and will be replace by '[email protected]' when restricted
      • Read clipboard, which will be replaced by the text 'Private' when restricted

      Furthermore the ability to restrict Android system (be careful!) and to restrict system apps was added. It is possible to restrict all of these individually (XPrivacy could not do that).

      Be sure to take a look at the help page in the app again (use the ?-icon), since there were some useful hints added.

      If you appreciate what I am building here, please let me know by means of an XDA thanks and/or a donation, so that I don't get the feeling 'What am I doing this for?'.
      59
      I have just released alpha version 0.12 in the Xposed repository.

      This version has been redesigned for Android Oreo compatibility. The user interface and the restrictions work properly for me, but be aware that a lot has been changed on the inside ("it is bigger on the inside", lol), also for earlier Android versions. There is one thing I know of that needs improving and that is that the user interface might be updated too often with a lot of restrictions, which might cause delays and hangs. I will look into this tomorrow.

      This change was necessary, but it was a lot of work, so XDA thanks and donations are appreciated.
      56
      I have just released beta version 0.25 in the Xposed repository.

      Changelog:

      With this release XPrivacyLua restriction's can be compared with XPrivacy's. There are now over 100 restriction definitions!

      XDA thanks and donations are appreciated.
      53
      @CHEF-KOCH You have been given enough time to respond here. Now I just think it is pretty cowardly to write critical about XPrivacyLua, but not to tell what can actually be improved, especially because you were invited to do so.

      I still like to hear how XPrivacyLua can be improved, but I don't want to hear what is wrong with XPrivacyLua. You'll need to keep the scope of XPrivacyLua in mind (in short: privacy, not security), see the opening post and previous discussions about this for more information.

      Also, if you really know better, I like to see an original work from your hands to prove that. Actions speak louder than words.

      As it is now, you are discouraging one of the few people in the world who really did something substantial to improve privacy on Android. And don't go talking about VPNs, TOR, etc because your private information, like your contacts, will still leak.

      I also think you are pretty ungrateful for what I did so far.

      To others: if you see someone reference one of his blogs, please reference this comment in response.

      Edit: if you agree with this, please add an XDA thanks to this comment, so it will show up in the right column as a reference for others.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone