It was a notification inside the lsposed manager and was available through the LSPOSED repository from within the app.
It was a notification inside the lsposed manager and was available through the LSPOSED repository from within the app.
LSPosed developers does NOT talk about xposed modules.
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.I am considering to terminate support on January 5th 2023 because:
(*) They refuse to add an API to access scopes, resulting a too many questions and also loosing users.
- 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
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 sureI am considering to terminate support on January 5th 2023 because:
(*) They refuse to add an API to access scopes, resulting a too many questions and also loosing users.
- 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
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.
Works properlyI have moved over the hook definitions repository to GitHub, so it won't be lost
The project is unsupported now, so nothing will be changed anymore, sorry.Can you do something about the overlapping text in hook description?
A sad day but I can understand.I am considering to terminate support on January 5th 2023 because:
(*) They refuse to add an API to access scopes, resulting a too many questions and also loosing users.
- 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
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.
Yes, it does, even on Android 13First 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?
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.
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.