Your baseline-prof.txt is committed, CI runs the generator task every release, and the dashboard shows a nice fat profile file in the APK. Cold start is still slow. Here's the thing almost nobody checks: a baseline profile can be present, committed, and completely inert — and your build will never tell you. The three ways a baseline profile silently no-ops 1. It was generated against the wrong build variant BaselineProfileRule from Macrobenchmark has to run again...