Committed Android Baseline Profiles Can Silently Do Nothing
A baseline profile can be checked into a project and bundled into the APK yet still have no effect on startup speed. A common cause is generating it against a debug build rather than a release-shaped build, since R8 renames classes and the profile then references symbols absent from the shipped app. The profile also goes stale when new screens or navigation destinations are added without regenerating it, leaving those code paths unoptimized. Because none of this fails the build, developers are advised to verify installation and compilation state directly with adb commands like dumpsys package compiler-stats. Regeneration should be treated as a release-checklist item, with before-and-after startup measurements used to confirm the profile is working.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in