Did I ^up fingerprinting using a base-seedvault-profile because of ANDROID_ID?

ThisOldGuy

I built out a new device using a seedvault-backedup base-profile when creating my 4 new profiles.
Now I'm wondering if the ANDROID_ID and/or app IDs are identifcal for the backedup apps and the same in all my new profiles?

other8026

ThisOldGuy Now I'm wondering if the ANDROID_ID and/or app IDs are identifcal for the backedup apps and the same in all my new profiles?

I don't think Seedvault can back that up. Don't think there's any support for setting a specific ID for apps either.

Android ID isn't necessary to do this though. For example, you use some app and their server assigns some ID for the device you're using. That may be saved with the app data, backed up, then restored so it's possible a remote server can figure out you're the same person. Not saying that this kind of thing always happens, but it could happen.

Also, this section of the website might be of interest: https://grapheneos.org/faq#non-hardware-identifiers

ThisOldGuy

other8026
That is a very valid point. I made sure not to log in to any of the base apps, but small apps like flash-dim may.
I reviewed the grapheneos documentation a few times before posting; while I can understand the concept, I lack the "practical risk" or real world application. My biggest deficit is understanding how or when the ANDROID_ID or other APP ID are used or shared between apps or google or websites. Because I'm also confused why changing the wallpaper could impact device-fingerprinting; how can apps or sites or compat-play-services access this device information if it wasn't explicitly given access?

I'm struggling with ADB access, but would there be a way to access the ANDROID_ID or other unique identifiers from the terminal enabled from developer options?