- Aug 1, 2010
The Xposed Repo has been unavailable for many days, unfortunately.
That looks like: Build.MODEL / Build.DISPLAY.It's the app working well in Android 12? I've blocked everything to a delivery app named Rappi and only allowed location access but somehow it was able to know what kind of phone I have, isn't that supposed to be blocked by the app?
The app sent me this via e-mail:
Dispositivo: Mi A3 Build/SQ3A.220705.004
You can hide the name (email) of accounts recorded on the device.
Thanks for the help.You can hide the name (email) of accounts recorded on the device.
But you can't disallow apps from reading their login credentials, it's not same of "Read Account".
The app is just reading the credentials of a previously registered account and not requesting details from the system.
Credentials for google apps are given by google framework services.Thanks for the help.
This is new in Android 12? Because previously (like yesterday) I have been using Android 10 and this didn't happen, Maps was only detecting the fake account I set up in XPrivacyLua (it was something like [email protected]) and not my account. I'm using and always used MicroG, if that's important.
Probably, yes.Is it possible to:
1) Use XPLUA to trick an app into thinking that "Location" is enabled on a device
2) Send a fake GPS location to an app *before* the device is able to lock into it's location using just satellites.
To keep this thread from having a bunch of posts related to this issue, I created another thread and would greatly appreciate any replies to it:
I know I can fake the GPS location for many apps using XPLUE, but one app (the official McDonalds app) is causing trouble. 1) The app constantly checks to see if "Location" is enabled on the device, and it will complain when it is off and I need...forum.xda-developers.com
Gentlemen, I think I owe you a response. I approach our Forum Administrator @MikeChannon with this question and the information I've received is that it is no longer available and is no longer being developed. I'm convinced you're also aware that SRD @rovo89 who owned the repo hasn't been posted for more than 4 1/2 years. I suggest not to rely at all that any file, which was made available for download in that repo in the past, might be available in the future there.
Can you please check if this works too?I believe this is because `android.app.LoadedApk.makeApplication` works differently on Android 13, which is introduced by this commit.
Edit: Let me provide more details. I tried to hook `makeApplicationInner(bool, Instrumentation)`, but it didn't work somehow. Therefore, I looked into the function body and found that the returned `app` is actually created by `android.app.Instrumentation.newApplication`, which is why I made this modification.
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.