[Android Apps and Games] doggydog2:
It works!

What might be missing (but i can be easily fooled by xprivacy Pro in root mode):

- TelephonyManager.getDeviceId 15digit IMEI, apps get it reportedly. In any case, hope we do dual attack:

TelephonyManager telephonyMgr = (TelephonyManager) getSystemService(TELEPHONY_SERVICE);

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {

IMEINumber = telephonyMgr.getImei();

} else {

IMEINumber = telephonyMgr.getDeviceId();

would be interesting if deprecated way still worked

- Build.getSerial , can we somehow pretend we're one of the privileged apps? https://developer.android.com/reference/android/os/Build#getSerial()

- TelephonyManager.getSimSerial , same as above

- TelephonyManager.getSubscriberId , same as above

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

Serial, IMEI, Accounts, Running services, Running Processes

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

above and Android ID, Google Service Framework, Radio/Modem/Baseband, Telephony (except Quantity), SIM (except SIM Operator), Builds (most), Wi-Fi (the first part), Calls, Installed Packages, Installed Applications

***** what's revealed in the second line while xprivacy tries to mask it (masked and correct field - interesting, you must use additional method here):

Keys, Device, Brand, Model, Product, Manufacturer, Hardware

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

ID Advertising (could be simply cached?)

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

Fingerprint (cannot hide), User-Agent (browsers will deal with it via extensions or maybe Bromite WebView can do this globally), Bounded Bluetooth Devices (as per permission given), Builds Prop (cannot hide), Networks

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

nothing, there's no special effort in root mode, just root detection (not saying it's needed, in root apps we trust more than in the normal/system apps)

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

nothing. with READ_PRIVILEGED_PHONE_STATE added, also nothing. this would probably require app to be more demanding (manifest, different calls) but not sure, i thought at least some identifiers would show up automatically with /etc/permissions/priv-app* prop..

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.

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.

conclusions, doubts:

1) no doubt AppOpps/XPrivacy protects most apps. The apps you download from the play store. But I care about vendor/firmware apps and this is where it gets complex. There are so many extra rules. Since VDInfo is a normal app, it's difficult to find out what data the sleezy apps really get. Device manufacturers go extra mile to precook fine permission profiles for apps like facebook and don't hesitate to slap them to vendor/priv-app or product/priv-app folder.

2) XPrivacy shows that it is hiding device IDs even for very normal apps. It shows old and new value. This gives impression that those IDs are available, but it could be just that the root app can read and show those IDs beforehand?

3) I found with AppOpps is as good as XPrivacy if point 2 is ok. I want to hide device IDs, and have a great discipline in setting other Android UI permissions. The main abuser GMS can be fixed with both apps (to fix the annoying popups if you don't give it all permissions in Android UI). For lame users, with zero discipline as expected, I need to manage their phones with either XPrivacy or AppOpps Pro as each can restrict permissions for new apps. This is helpful as new users simply reinstall facebook and 30 seconds later the sleezy company has all call records and contacts, while the user happily clicks on "sweet default" choices. Obviously, LSPosed cannot be used for these users as it doesn't auto include new apps.

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