[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
- Thread starter M66B
- Start date
- Status
It links to http://repo.xposed.info/module/eu.faircode.xlua, which is a dead link. I think it should be https://github.com/Xposed-Modules-Repo/eu.faircode.xlua
So follow these github instructions and download hooks from the various links scattered through those github instructions? Those hooks are then applied through an interface in the xprivacy lua pro app? is that best downloaded from the in-app link as opposed to the google playstore link? I'm not understanding the difference between the xprivacy lua in-app restriction boxes versus these hooks.
I'm trying to use your app here and learn. Everyone starts somewhere. Some help and direction would be nice and appreciated. I can message you if that's helpful or preferred.
I can find "repo.xposed.info" in any of the markdown files. Where do you see this?
There is no support for custom hook definitions from my side because they are not my work.
I understand that. can you address my path to follow though and if the method to use the hooks is correct? do i need the pro companion app to do that and is the place to get that pro companion app available through the playstore and the in-app link to give to you direct as opposed to through the playstore? to both options work? is spoofing data only possible with these custom hooks?
That link was changed 9 hours ago:
Updated download location · M66B/XPrivacyLua@f464e23
Really simple to use privacy manager for Android 6.0 Marshmallow and later - Updated download location · M66B/XPrivacyLua@f464e23
github.com
The pro companion app isn't available via the Play store anymore because Google removed it.
The built-in hook definitions are mostly enough to protect your privacy.
Maybe on https://github.com/M66B/XPrivacyLua but not on https://modules.lsposed.org/module/eu.faircode.xluaThat link was changed 9 hours ago:
Updated download location · M66B/XPrivacyLua@f464e23
Really simple to use privacy manager for Android 6.0 Marshmallow and later - Updated download location · M66B/XPrivacyLua@f464e23
so is the pro app available for direct download through the in-app link in xprivacy lua? Is the benefit of that app to backup/restore settings and make these hook definitions as defined in github?
Please see here for which features the pro companion app offers:
Is it a bad idea to restrict carrier and Google play services? I blanket restricted them and battery drain shot through the roof. I assumed this was whyPlease see here for which features the pro companion app offers:
Hello, i can't figure out how to change imei for each slot in dual sim phone. can you please point me in the right direction on how to modify existing lua scripts or add new hooks to do so. I don’t know java, as I understand it, the required parameter is in the getImei(index) and getDeviceid(index) methods, I couldn’t figure it out further,does the hook in xprivacy sees the slot index in these methods and how to work with it?
Thank you
HI M66B，I can't understand the error log, only run without loading xprivacylua
Code:
[ 2022-11-18T12:50:32.935 10390: 21230: 21230 I/LSPosed-Bridge ] Loading module eu.faircode.xlua from /data/app/~~VjoWGq2F4tQUljBN-Af-5A==/eu.faircode.xlua-doDIGlFlpBe1c4fjLavNag==/base.apk
[ 2022-11-18T12:50:32.958 10390: 21230: 21230 I/LSPosed-Bridge ] Loading class eu.faircode.xlua.XLua
[ 2022-11-18T12:50:33.347 10390: 21230: 21230 I/LSPosed-Bridge ] XLua.Xposed Loaded com.pingan.paces.ccms:10390
[ 2022-11-18T12:50:33.678 10390: 21230: 21230 F/libc ] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x78c in tid 21230 (ngan.paces.ccms), pid 21230 (ngan.paces.ccms)
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] Build fingerprint: 'google/bonito/bonito:12/SP2A.220505.008/8782922:user/release-keys'
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] Revision: 'MP1.0'
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] ABI: 'arm'
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] Timestamp: 2022-11-18 12:50:33.780076733+0800
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] Process uptime: 0s
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] Cmdline: com.pingan.paces.ccms
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] pid: 21230, tid: 21230, name: ngan.paces.ccms >>> com.pingan.paces.ccms <<<
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] uid: 10390
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x78c
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] Cause: null pointer dereference
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] r0 00000000 r1 ff96096e r2 734e7abe r3 0000078c
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] r4 db85dd94 r5 00000000 r6 ff960bf4 r7 000052ee
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] r8 b6a287de r9 0000078c r10 00000042 r11 00000000
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] ip ef3d119c sp 00000000 lr 00000000 pc 0000078c
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] backtrace:
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] #00 pc 0000078c <unknown>
[ 2022-11-18T12:50:34.029 10390: 21260: 21260 F/DEBUG ] #01 pc 00000000 <unknown>
[ 2022-11-18T12:50:36.058 10390: 21281: 21281 I/LSPosed ] Loading xposed for com.pingan.paces.ccms/10390
[ 2022-11-18T12:50:36.063 10390: 21281: 21281 I/LSPosed-Bridge ] Loading module eu.faircode.xlua from /data/app/~~VjoWGq2F4tQUljBN-Af-5A==/eu.faircode.xlua-doDIGlFlpBe1c4fjLavNag==/base.apk
[ 2022-11-18T12:50:36.084 10390: 21281: 21281 I/LSPosed-Bridge ] Loading class eu.faircode.xlua.XLua
[ 2022-11-18T12:50:36.146 10390: 21281: 21281 I/LSPosed-Bridge ] XLua.Xposed Loaded com.pingan.paces.ccms:10390
[ 2022-11-18T12:50:36.443 10390: 21281: 21281 F/libc ] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x78c in tid 21281 (ngan.paces.ccms), pid 21281 (ngan.paces.ccms)You cannot change the IMEI with XPrivacyLua. You only can block the access for individual apps to read the IMEI by blocking access to Telephony Data. With the Pro companion app you can, again for each individual app, define fake IMEI values. If you do that, the same value is reported for both SIM slots.
I don't know if you can use scripts to have different values reported for each slot.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
318XPrivacyLua
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 donationorby purchasing pro features.
About feature requests and bug reports:
XDA thanks and donations are appreciated.
XPrivacyLua is supported with Xposed only. There is no support for VirtualXposed and TaiChi.68I 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?'.59I 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.56I have just released beta version 0.25 in the Xposed repository.
Changelog:
- Added activity recognition restriction
- Added read notifications restriction
- Added send messages restriction
- Added PlaceDetectionApi hooks (get location)
- Added getPreferredPackages hooks (get applications)
- Added external applications (un)available hooks (get applications)
- Added widget listing hooks (get applications)
- Added audio manager hooks (record audio)
- Performance improvements
- Small improvements and minor bug fixes (an understatement)
- Updated documentation
- Updated FAQ
- Updated translations
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.