GmsCore icon indicating copy to clipboard operation
GmsCore copied to clipboard

Stable randomized per-app advertising ID

Open lucasmz-dev opened this issue 2 months ago • 2 comments

Is your feature request related to a problem? Please describe. If an app were to fingerprint a device, its algorithm may be fooled by microG's randomization of the advertising ID, but it also could be easily detected by just checking if it changes right away and it can then ignore it.

Describe the solution you'd like As an alternative to the advertising ID full on randomization, my suggestion would be to have stable but still randomized IDs returned for each app, that way they can't tell the advertising ID is randomized. If keeping a database of these is undesirable, then I believe hashing could help, e.g. hash(uniqueValue.. appPackageName.. appSigningKey)

Describe alternatives you've considered Nothing

Additional context This does have the potential of making detection even stronger and then they may start detecting microG instead.

Also if an app were to use the advertising ID just to keep track of activity within itself, it would still be able to do that

lucasmz-dev avatar Oct 23 '25 00:10 lucasmz-dev

This is more of a concept I wanted to share, I'm unsure if fingerprinting is happening, if it even uses this ID, or other methods are used like pure inter-app communication, since that would probably be more reliable.

lucasmz-dev avatar Oct 23 '25 00:10 lucasmz-dev

i also thought of stuff like this but also with a additional UI inside microG to view what apps accessed the AD ID and how much they did that in that day. a semi stable approach could also work that randomizes the ID in a random intervall from a day to 5 weeks so that this is turned into a unreliable data source.

also would a log-file or something be cool that logs how often what apps access anti-feature api's.

Idcrafter avatar Oct 30 '25 22:10 Idcrafter