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

Status
Not open for further replies.
Search This thread

Schroeder09

Senior Member
Nov 6, 2017
1,161
230
Google Pixel 7 Pro
Does anyone have any tricks, methodology, or lost of things they're currently restricting on Google framework, carrier services, Google play services, or the Google play store? Any single restriction I add to carrier services seems to break something. I lose the continued conversation with Gboard (colored flashing indicator on around Gboard mic for talk to text), or chat messages stop sending and receiving. I've tried multiple combinations and enabling single restrictions at a time. Anything I check seems to trigger a fault and any changes made only take after a reboot unlike on some other apps. The trouble I'm having restricting carrier services is making me hesitant to restrict any google framework or play service aspects.
 
  • Like
Reactions: kaefers

M66B

Recognized Developer
Aug 1, 2010
26,751
57,984
I am considering to terminate support on January 5th 2023 because:
  • Not many people use the module anymore
  • The support of the project is pretty limited
  • Android has become more privacy-friendly over time
  • The LSposed developers do not support the module (*)
  • The module is too often misused, for example to cheat in games, etc.
  • I have received enough hate mail
(*) They refuse to add an API to access scopes, resulting a too many questions and also loosing users.

This means that XPrivacyLua has been supported for exactly 5 years. XPrivacy was first released on June 12, 2013, so that's in total about 10 years of XPrivacy(Lua). I think that is a pretty long time.
 

M66B

Recognized Developer
Aug 1, 2010
26,751
57,984
To elaborate on not supported by the LSposed developers:


This issue has been open for almost 2 years. I don't know what the goal of the LSposed developers is, but it doesn't seem to include supporting module features. Maybe there are not enough LSposed developers, or they don't have enough time for development, or they think XPrivacyLua isn't worth it, all of which would be a problem in itself. In fact, I expected the Xposed project to collapse a few years back already, and even though it still seems to be going, I am not convinced it will keep going. As a consequence, I have not been motivated to put much time into XPrivacyLua in the past years, which makes it basically a dead project anyway.
 

M66B

Recognized Developer
Aug 1, 2010
26,751
57,984
Another factor in the decision to stop supporting the project is that XDA stopped hosting the Xposed module repository without any prior notice. Apparently, XDA doesn't support Xposed modules anymore.

Note that the hook definitions repository will be taken down as well. Not right now, but there is no point in hosting this anymore (and paying for it) while the project isn't supported anymore.

Edit: the hook definition repository is in read-only state now.
 
Last edited:

Amd4life

Senior Member
Dec 30, 2010
1,892
480
I am considering to terminate support on January 5th 2023 because:
  • Not many people use the module anymore
  • The support of the project is pretty limited
  • Android has become more privacy-friendly over time
  • The LSposed developers do not support the module (*)
  • The module is too often misused, for example to cheat in games, etc.
  • I have received enough hate mail
(*) They refuse to add an API to access scopes, resulting a too many questions and also loosing users.

This means that XPrivacyLua has been supported for exactly 5 years. XPrivacy was first released on June 12, 2013, so that's in total about 10 years of XPrivacy(Lua). I think that is a pretty long time.
It always makes me sad to see these posts, but I guess it's just time. I wish you would focus on the positive messages, happily paid customers verus all the users that don't even want to read the thread for help. Take the app private, charge an annual fee and keep away from trolls. This is the best app on Android period. Without it, might as well buy a Iphone 14 pro max.

Good luck to you.
 

westhaking

Senior Member
Jan 18, 2009
251
124
Google Pixel 2
Google Pixel 6 Pro
I am considering to terminate support on January 5th 2023 because:
  • Not many people use the module anymore
  • The support of the project is pretty limited
  • Android has become more privacy-friendly over time
  • The LSposed developers do not support the module (*)
  • The module is too often misused, for example to cheat in games, etc.
  • I have received enough hate mail
(*) They refuse to add an API to access scopes, resulting a too many questions and also loosing users.

This means that XPrivacyLua has been supported for exactly 5 years. XPrivacy was first released on June 12, 2013, so that's in total about 10 years of XPrivacy(Lua). I think that is a pretty long time.
This is so disappointing to hear as there are exactly zero apps that offer similar functionality. Sad day for sure 😢
 

M66B

Recognized Developer
Aug 1, 2010
26,751
57,984
Last edited:

dope77

Senior Member
Aug 8, 2018
397
121
Can you do something about the overlapping text in hook description?
 

Attachments

  • Screenshot_20221125_235911_XPrivacyLua Pro.jpg
    Screenshot_20221125_235911_XPrivacyLua Pro.jpg
    687.8 KB · Views: 89

the00guy

Senior Member
Jul 14, 2010
231
44
Damn, I knew this day would eventually come, I just hoped it wouldn't. It's one of the few that I've donated to because I honestly couldn't see myself using Android without it.

Even though Android has incorporated more permissions over the years, being able to restrict an app's ability to see what other apps are installed on the phone, SIM card/subscriber data, sensor data such as accelerometer and gyroscopic data which can be used to track user movements from a wifi or gps determined location, and of course, being able to read all of the stored SSIDs stored on a phone which a malicious app could also use to determine where a person spends their time and has been via the many glob SSID location maps, many of which have been crowd sourced such as wigle.net.

As a digital privacy advocate, I'll continue to advise people use this framework until some other developer hopefully picks this mantle back up, or such a time as these aspects of privacy become baked into mobile OSs.

I want to say thank you for all the work you've done on this project, Marcel. You've not only empowered many people like myself to better our own operational security, but have also raised awareness that many of these forms of tracking are even possible, and are also preventable. I wish you the best of luck with your other projects, which I'll continue to support as well.
 

mopst

New member
Apr 10, 2019
4
2
@the00guy Well said.

M66B, I'm very sad to hear this news, but as a fellow developer, I get it. You gotta do what's best for you, and if it's been such a negative force, I think you should drop it. Another developer can fork it if they want, and if not, that's an answer in itself. I love your other projects as well, and I wish you peace.
 

beeshyams

Senior Member
Dec 29, 2014
1,748
670
Bangalore
@M66B, all good things come to an end and your reasons are valid, though I will sorely miss it and my support is with you should you decide otherwise.

Aside, please don't discontinue FairEmail, despite all the negativity

Thanks for everything and take care 🙏
 
  • Like
Reactions: kaefers

Baymaeela

New member
Nov 26, 2022
4
1
First of all, does XprivacyLua work on Android 10? And if it does, is it possible to change the values in the pro version, or even the free version?

Like for Read account name, it gives fake name, mostly e-mail address. What is the fake name and email address it gives, and can I change the name and email address to the one I want it to give?
 
  • Like
Reactions: oldman20

christantoan

Senior Member
Oct 9, 2015
258
108
OnePlus 3T
OnePlus 7 Pro
I am considering to terminate support on January 5th 2023 because:
  • Not many people use the module anymore
  • The support of the project is pretty limited
  • Android has become more privacy-friendly over time
  • The LSposed developers do not support the module (*)
  • The module is too often misused, for example to cheat in games, etc.
  • I have received enough hate mail
(*) They refuse to add an API to access scopes, resulting a too many questions and also loosing users.

This means that XPrivacyLua has been supported for exactly 5 years. XPrivacy was first released on June 12, 2013, so that's in total about 10 years of XPrivacy(Lua). I think that is a pretty long time.
A sad day but I can understand.
Thank you very much for supporting the project so far.

Sorry for maybe insensitive question but will the Pro companion app be open-sourced after the support is terminated? As I think both apps are important to be open-sourced just in case someone else want to continue the project.

Thank you once again.
 
  • Like
Reactions: kaefers

M66B

Recognized Developer
Aug 1, 2010
26,751
57,984
A sad day but I can understand.
Thank you very much for supporting the project so far.

Sorry for maybe insensitive question but will the Pro companion app be open-sourced after the support is terminated? As I think both apps are important to be open-sourced just in case someone else want to continue the project.

Thank you once again.

If somebody wants to continue this project, which needs to be proven with actually contributions, that somebody can contact me to get the source code of the pro companion app. With this, I am trying to prevent misusing the pro companion app. Check the Play Store for clones of NetGuard, and you'll understand.
 

beeshyams

Senior Member
Dec 29, 2014
1,748
670
Bangalore
First of all, does XprivacyLua work on Android 10? And if it does, is it possible to change the values in the pro version, or even the free version?

Like for Read account name, it gives fake name, mostly e-mail address. What is the fake name and email address it gives, and can I change the name and email address to the one I want it to give?
Yes, it does, even on Android 13
You can configure fake email address globally / on per app basis (though I haven't tried it but quoting from rusty memory) but then you need the pro version
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 318
    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.

    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 community 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.
    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.