MONITORING
Sanctus Compute Lab
An Android scheduler research app created from a real QLI/Qubic problem: CPU throughput is healthy while visible, but collapses when the app is backgrounded or the screen turns off.
Can Android preserve useful compute when the screen is off?
Observed problemOn a Samsung Galaxy S22 Ultra, the workload stays alive in a foreground service, but V0.1 measured background and screen off throughput at only about 9% of the foreground rate.
Research questionIs Android mainly throttling the work because the process is no longer visibly important, rather than because the workload stopped or the device became thermally limited?
V0.2 probeCompare baseline foreground service, floating overlay and Picture in Picture modes while measuring foreground, background and screen off retention, process importance, CPU allowed list, thermal status and battery temperature.
Safety and scopeThe APK is deliberately a synthetic scheduler benchmark, not a Qubic miner. It does not bypass Android security or thermal protection.
Next milestoneIf a user visible mode materially improves retention, optimize that architecture first and only then evaluate a QLI compatible integration route.