[Android Apps and Games] VD171:
- TelephonyManager.getDeviceId 15digit IMEI, apps get it reportedly. In any case, hope we do dual attack.

Both methods are read by app.

- Build.getSerial , can we somehow pretend we're one of the privileged apps.

- TelephonyManager.getSimSerial , same as above.

- TelephonyManager.getSubscriberId , same as above.

There is no way to pretend that. Android is Linux and Linux checks privileged apps by UID. Therefore, if the application does not have a system UID, you can never fake it.

***** what's hidden by default (the Android 11 protection).

Finally. The app should be able to read only what is necessary for its operation. In addition, permission should be requested for any specific-user info.

***** what's hidden/masked by xprivacy.

. Sim quantity is not much relevant.

. XprivacyLua can mask SIM OPERATOR easily. You need to disable "Use tracking".

. Builds are really exposed for every app. Sad...

. Wi-Fi can be masked but some apps can crash. For this, really needs a specific-app testing.

***** what's revealed in the second line while xprivacy tries to mask it.

There are many ways to read them. They really need more attention.

***** what's not hidden by xprivacy and it is for otherapps.

Unhappy, XPrivacyLua doesn't change the Ads ID by default.

But this hook by Fif_ can does this: https://lua.xprivacy.eu/repo/view?id=130

(You need to disabled the default hook first.)

***** what's not hidden by xprivacy.

. Fingerprint can be masked without issues.

. User-agent is probably the most easy way to read device infos. It really exposes you. I never found an application that wanted to hide it.

. Builds Prop can be masked without issues too.

***** whats revealed when we upgrade VDInfo to root app despite xprivacy.

***** whats revealed when we upgrade VDInfo to system app.

If the app has the same system UID, it will certainly read a lot more.

But the proposal here is to read what can be read for non-system applications.

didn't realize AppOpps actually adds permissions when READ_DEVICE_IDENTIFIERS is activated. When this is set to true, IMEIs are shown. This choice is off by default. Surprising that this is proactively unmasking data, if i'm correct.

READ_DEVICE_IDENTIFIERS only matter if this is a system app.

NO one system permission will be added to the app.

This is not the proposal.

btw what a stupid decision by LSPosed to apply only on specific app, need to find workaround for this huge mistake! But it really works smoother than EDXposed.

I'm totally agree with out. I loved LSPosed, but I will not select app by app. Never.

1) But I care about vendor/firmware apps and this is where it gets complex.

System app can be totally disabled without uninstalling them.

2) XPrivacy shows that it is hiding device IDs even for very normal apps. It shows old and new value.

It is not an issue with XPrivacy. The point is that my app tries other non-conventional ways.

But, of course, they should all be masked.

3) I found with AppOpps is as good as XPrivacy if point 2 is ok.

AppOpps works different than XPrivacyLua. It modifies alarms, receivers, services and other things related with the structure of the app. XPrivacyLua will never try to modify it.

4) Another great choice is LineageOS AOSP with their permission manager and tons of manufacturer's precooked stuff gone.

Unhappy, I prefer original stock rom. I don't like "custom" roms. So, I'm not fimiliarized.