there’s just this vague recommendation to “turn it off in settings.” no link, no toggle, nothing.
had to hunt for the relevant setting in the app(even their settings menu is down under in the list when you tap on your avatar.
image transcription:
a screenshot of Google play store which has a popup that can only be disabled by pressing OK button at the bottom.
the popup contains the following text:
Google is optimising app installs with your help
Google Play makes apps faster to install, open and run based on what people are using most.
The first time that you open an app after installing, Google notes which parts of the app you use. When enough people do this, your apps will install faster.
App install optimisation is automatically turned on, but you can turn it off in settings. Learn more
My only question now is, What parts are in AOSP and what parts are Googled Android? Is reading and installing with these optomization files/API sys-app only? Are they using accessability to track thd open activity, or via the optomization API provided by android.
I cant really tell you if their acting in bad faith without this info.
I’ve done a dive of the source code and I can provide a partial answer.
The execution logging functionality is publicly available source code right here.. The code reveals how Android decides what and when to save hot methods.
Dex2oat uses the profile data. You can see references here to the profile directory.
Now, where is the code that ships and downloads these profiles? I can’t find it. I suspect it’s part of Play services. Thus, AOSP provides all the machinery, but Play probably handles the actual profile data delivery.
Thats what I feared. Its either ptrace, root file access or a non public android API