Actually I was developing a step counter app and I wanted to send the steps to my app from the sensors of the device and then directly upload it to my server...
From what i understad is, xlua does not block the sensor itself. Rather xlua blocks apps or certain app from reading sensor's real data.
XPL does work on A13. Probably you're not using LSposed correctly. In LSposed, you have to bring each and every app into the scope of the module. This problem has been addressed over and over again in this thread and is only caused by LSposed itself. These constant questions about the LSposed problem has even been a major reason for the developer to stop supporting XPL.
Just want to throw in my thanks for all the years of Xlua you made. Im only a rookie but you allowed me to feel safe in this increasingly surveillanced world we live in. To thee who is moving on, we salute you.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.
Please share your source code to the community so someone can maintain it, appreciate it and good luck.
Marcel, you've certainly good reasons for your decision to close this and the two other threads. Their closure has been accomplished.
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.
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:
As said before, development will also depend on Xposed development, which is just minimal unfortunately.