Here’s the final command I used, which includes killing the app, waiting a second, then launching it. I looped it for 10

Finding moments of stillness throughout your day will allow you to better appreciate the little things, to notice the beauty around you. It will keep your mind sharp and calm. It will help you to live a good life.,Running the clocks at high frequencies for too long tends to make them overheat. I don’t know how the system would respond to this (hopefully it would down-clock them or shut down the system automatically before there were serious problems), but I don’t really want to find out.,Note that you will want to unlock the clocks when you are done with your testing. The device will unlock them on reboot, but you can also unlock them by running the opposite gradle task:,You want test results with realistic, or even poor, performance, like many of your users will see in the field. You do not want to only see best-case performance, which is not what people would typically see in reality.,Note: There’s actually a much simpler way to loop start-activity using -S (which force-stops the activity first) and -R COUNT (which runs thestart-activity command COUNT times), so I could have used this instead:,After locking the clocks, I had everything in place: a system that could reproduce my startup situation with reliable consistency, and a simple command-line I could execute that would return a stream of results. I was able to copy the results, paste them into a spreadsheet, and analyze them (by comparing my startup averages to various before/after situations I wanted to experiment with).,In any case, if you can lock your clocks, I suggest you do so. It may not matter significantly for your particular testing situation (and in fact the system generally runs the clocks at a high frequency specifically when starting up apps, so that might already provide the consistency you need). But it’s good to at least eliminate CPU frequency as a variability factor.,The benchmark utility locks clocks at an easily sustainable level, not a high-performance level. If the clocks were running as high as possible instead, you might get better performance, but:,The deal is meant to familiarize new audiences to the early 2000s variety show with hopes of luring them to Paramount when it’s introduced in 2021. Yeah, that’s how much is behind this joke. Because Chappelle exclaims that he’s getting nothing from the deal which is the set-up for the punchline, said in the voice of his great-grandfather, “this nigga got bought and sold more than I have.”,Ideally, you should have control over the CPU frequency when running performance tests. Unfortunately, your ability to do this depends on the device(s) that you have; you need to have root access to a device to control the CPU governor, which controls the frequencies, and different devices may have different ways of altering this behavior.,The following information only pertains to you if you happen to have access to a device which allows it, and for which you can get root access. On the device front, I know that Pixel devices allow this access; I can’t speak for other devices.,That output was a pretty good indication that it worked on my Pixel 2. An even better indication was that my startup tests now took significantly longer than they did before. But wait, why are locked clocks slower?,Unfortunately, locking CPU frequency manually can be tricky. Fortunately, the AndroidX benchmark library makes it simple. In fact, you don’t even need to write code for the benchmark APIs; you can use the library just to get the handy lockClocks and unlockClocks utilities that it provides.,But to ensure a buffer of inactivity between teardown and startup, I wanted that sleep 1 command, so I went with the more verbose loop approach. Besides, shell script code is sooooo elegant, right?,One of the factors in mobile device performance is the CPU architecture, and the CPU frequency in particular. Specifically, one of the main ways that mobile devices preserve battery life, and avoid major problems of overheating, is by throttling the CPU speed.