Actually this is one of the problems that was fixed in beta version 0.26, so make sure you have version 0.26 installed and did hard reboot your device.
Both problems should be fixed in beta version 0.29. Eventually we'll get there.On 0.26 before, 0.27 now. Retested. Full reboot, twice. Still getting same error. Privacy.PlaceLikelihoodBuffer.get
Tried Maps and WhatsApp and there is no error on these with Course fake. (Although watching the new recalculated location fake every 5 seconds is funny).
Could this be something specific to how this app "Dark Sky" handles location? If so, I've got Logcat.
---------- Post added at 09:53 PM ---------- Previous post was at 09:35 PM ----------
New filters are awesome. V0.27. One odd behavior.
1. Select any single filter.
2. Select another single filter.
3. Red apps, when expanded, still show the first filter. While white apps are updated to the currently selected filter.
It seems that the red apps (potential problem apps) stick with the first selected filter. Setting filter to show All and then selecting new filter works fine for all apps.
I see why you didnt want to add features until core utility was very stable.
Given how XPrivacyLua works, this is not possible. Restrictions will only be applied when you select them and there can only be usage data when restrictions are applied. This is better for stability and performance.The suggestion. XPL shows time of use the restriction if the restriction is set. If showing the use of restriction will be possible if the restriction is not set, it will help much in the procces of selecting if the restriction should be set or not.
If it will be introduced, it will be a pro feature.Apologies if it has been asked and answered (a quick search didn't reveal). If and when a batch feature is introduced (for example, apply a select number of restrictions to a selection of apps), will this be a pro feature?
Please provide a logcat with the crash and I will see what I can do.@M66B with 0.24, everything is ok, then I update to 0.25, meet some problem.
I need uncheck read network data so as to make app work in the first use.
When checked, app may crash or just say network failure. But app is already in white list of afwall+, and the log says app has been blocked to 192.168.1.1
When unchecked, everything is ok. Then check, still ok. Only the first time.
Would you please fix it? Thank you very much. You're appreciated. And very sorry for bad English.
I think that if somebody want to protect his/her privacy that he/she at least should read the documentation, which describes all restrictions. The documentation will be referenced from the in-app help page in the next release.One more suggestion from point of view ordinary user , who knows only how to basic use android on his phone and nothing more ...
The current version lets to select filter and in the filter the name of it, fe:
"Read identifiers "
We know what it is , if not we can see on https://github.com/M66B/XPrivacyLua but someone else what will he think/do ? IDs oh , I do not know , better do not touch it . He/she will not go to FAQ , first because he will not know where it is , second he will have to check it very often (maybe after many checks he will remember) and will not have time or willingness. The solution is to add full description of every fileter in to app (maybe "?" button , which will show full description about selected filter with info : serial number, Android ID, GSF ID, advertising ID , IMEI and all the rest identifiers supported by XPL . The same for each filter.
The "?" button near the selected filter field , no in menu . Info should be accessable after single touch.
I have just released beta version 0.30 in the Xposed repository.
Added system properties hook (get identifiers)
Small improvements and minor bug fixes
I have checked all XPrivacy source code and discovered that system properties (serial number) could not be restricted yet, so I have added this.
If XPrivacyLua reports an error or if an restricted app crashes, please let me know and provide a logcat and I will see if it can be fixed in the next release.
You can consider this version to be an almost stable version.
XDA thanks and donations are still appreciated.
This thread is full of comments about this problem, but the Xposed developers are too busy fighting with each other. Basically, XPrivacyLua itself isn't hooked.Can you demonstrate where you see the Xposed issue so I can log a bug with them?
This is a bug in Riru.I tried the clipboard and recorded it on WeChat, but Suning did not. . . .
I found this error code
04-10 11:45:26.389 5323 5323 I EdXposed: Riru hooks installed 04-10 11:45:26.452 5323 5323 I EdXposed: ART hooks installed 04-10 11:45:26.522 5311 5311 I EdXposed-Bridge: XLua.Xposed Loaded com.android.traceur:10090 04-10 11:45:26.532 5323 5323 I EdXposed: Loading modules for com.suning.mobile.ebuy 04-10 11:45:26.532 5323 5323 I EdXposed-Bridge: Loading modules from /data/app/~~hcjuv6HzQbZOKMB3ug7WSw==/eu.faircode.xlua-vNspZ6pSQTrjHf23gYkdcA==/base.apk 04-10 11:45:26.572 5323 5323 I EdXposed-Bridge: Loading class eu.faircode.xlua.XLua 04-10 11:45:26.806 5359 5359 I EdXposed: Start to install inline hooks 04-10 11:45:26.806 5359 5359 I EdXposed: Using api level 30 04-10 11:45:26.806 5359 5359 I EdXposed: Start to install Riru hook 04-10 11:45:26.907 5323 5323 E EdXposed: error when hooking bindApp: pkg=com.suning.mobile.ebuy, prc=com.suning.mobile.ebuy 04-10 11:45:26.907 5323 5323 E EdXposed: java.lang.ArrayIndexOutOfBoundsException: length=1052; index=1263817555 04-10 11:45:26.907 5323 5323 E EdXposed: at pxb.android.axml.AxmlParser.getNamespacePrefix(AxmlParser.java:151) 04-10 11:45:26.907 5323 5323 E EdXposed: at pxb.android.axml.AxmlReader.accept(AxmlReader.java:80) 04-10 11:45:26.907 5323 5323 E EdXposed: at com.elderdrivers.riru.edxp.util.MetaDataReader.<init>(MetaDataReader.java:27) 04-10 11:45:26.907 5323 5323 E EdXposed: at com.elderdrivers.riru.edxp.util.MetaDataReader.getMetaData(MetaDataReader.java:19) 04-10 11:45:26.907 5323 5323 E EdXposed: at com.elderdrivers.riru.edxp._hooker.impl.HandleBindApp.beforeHookedMethod(HandleBindApp.java:69) 04-10 11:45:26.907 5323 5323 E EdXposed: at de.robv.android.xposed.XC_MethodHook.callBeforeHookedMethod(XC_MethodHook.java:51) 04-10 11:45:26.907 5323 5323 E EdXposed: at com.swift.sandhook.xposedcompat.hookstub.HookStubManager.hookBridge(HookStubManager.java:361) 04-10 11:45:26.907 5323 5323 E EdXposed: at SandHookerNew_42b8453bf7df105343083f1377c32094be493c49.hook(Unknown Source:51) 04-10 11:45:26.907 5323 5323 E EdXposed: at android.app.ActivityThread.access$1300(ActivityThread.java:237) 04-10 11:45:26.907 5323 5323 E EdXposed: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913) 04-10 11:45:26.907 5323 5323 E EdXposed: at android.os.Handler.dispatchMessage(Handler.java:106) 04-10 11:45:26.907 5323 5323 E EdXposed: at android.os.Looper.loop(Looper.java:223) 04-10 11:45:26.907 5323 5323 E EdXposed: at android.app.ActivityThread.main(ActivityThread.java:7660) 04-10 11:45:26.907 5323 5323 E EdXposed: at java.lang.reflect.Method.invoke(Native Method) 04-10 11:45:26.907 5323 5323 E EdXposed: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) 04-10 11:45:26.907 5323 5323 E EdXposed: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947) 04-10 11:45:26.935 5359 5359 I EdXposed: Riru hooks installed 04-10 11:45:26.983 5359 5359 I EdXposed: ART hooks installed
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:
As said before, development will also depend on Xposed development, which is just minimal unfortunately.