In go/hello-chrome-hackathon we discovered that about 300ms worth of CPU activity happens in the framework before code in Chrome's APK starts executing. We should dig into what's happening during this time period and see if there's a way to reduce it (e.g., Java code ordering).