IssueTracker

Running `google/bramble/bramble:11/RQ3A.211001.001/7641976:userdebug/dev-keys`, we don't throw an error for locking.

Guessing we need to be a bit more exhaustive about our inspection of the cpufreq directory, and even consider throwing, or using shell if we're rooted and can't read the important values via `File` access.

See also b/284201431 where the locking decision on the device isn't great, may want to solve that first.


Currently, we consider clocks locked if both of the following are true:

1) all online cpus with the same active frequencies share the same `scaling_setspeed` (or `scaling_min_freq` if we can't access that)
2) all online cpus aren't using min clocks

What's happening though is that all cores are pinned to max frequency during process init, perhaps because we're launching something? We're just initializing a test process (which at this point in execution hasn't launched an activity), so I'm surprised this would hit boost clocks, but maybe that's expected behavior (+cc Carmen)

```
02-16 22:02:48.976 12032 12032 D Benchmark: cpu0 CoreDir(path=/sys/devices/system/cpu/cpu7, online=true, availableFreqs=[806400, 1094400, 1401600, 1766400, 1996800, 2188800, 2304000, 2400000], setSpeedKhz=2400000, maxFreqKhz=2400000)
02-16 22:02:48.976 12032 12032 D Benchmark: cpu1 CoreDir(path=/sys/devices/system/cpu/cpu5, online=true, availableFreqs=[300000, 576000, 614400, 864000, 902400, 1363200, 1516800, 1651200, 1804800], setSpeedKhz=1804800, maxFreqKhz=1804800)
02-16 22:02:48.976 12032 12032 D Benchmark: cpu2 CoreDir(path=/sys/devices/system/cpu/cpu3, online=true, availableFreqs=[300000, 576000, 614400, 864000, 902400, 1363200, 1516800, 1651200, 1804800], setSpeedKhz=1804800, maxFreqKhz=1804800)
02-16 22:02:48.976 12032 12032 D Benchmark: cpu3 CoreDir(path=/sys/devices/system/cpu/cpu1, online=true, availableFreqs=[300000, 576000, 614400, 864000, 902400, 1363200, 1516800, 1651200, 1804800], setSpeedKhz=1804800, maxFreqKhz=1804800)
02-16 22:02:48.976 12032 12032 D Benchmark: cpu4 CoreDir(path=/sys/devices/system/cpu/cpu6, online=true, availableFreqs=[652800, 940800, 1094400, 1478400, 1728000, 1900800, 2092800, 2208000], setSpeedKhz=2208000, maxFreqKhz=2208000)
02-16 22:02:48.976 12032 12032 D Benchmark: cpu5 CoreDir(path=/sys/devices/system/cpu/cpu4, online=true, availableFreqs=[300000, 576000, 614400, 864000, 902400, 1363200, 1516800, 1651200, 1804800], setSpeedKhz=1804800, maxFreqKhz=1804800)
02-16 22:02:48.976 12032 12032 D Benchmark: cpu6 CoreDir(path=/sys/devices/system/cpu/cpu2, online=true, availableFreqs=[300000, 576000, 614400, 864000, 902400, 1363200, 1516800, 1651200, 1804800], setSpeedKhz=1804800, maxFreqKhz=1804800)
02-16 22:02:48.976 12032 12032 D Benchmark: cpu7 CoreDir(path=/sys/devices/system/cpu/cpu0, online=true, availableFreqs=[300000, 576000, 614400, 864000, 902400, 1363200, 1516800, 1651200, 1804800], setSpeedKhz=1804800, maxFreqKhz=1804800)
```

If that is expected behavior, we can just look for boosted clocks like this.