Ohh, my fault. I didn't understand Lago for some reason.
Hmmm, not sure. Could be:
- A hardware issue
- A rare software bug affecting some people.
- Extremely full storage
- A massive amount of system interrupts or other constraints
Perhaps a factory reset would help after backing up everything you can think of.
You could turn on usb debugging and see if the below command turns up anything. Don't worry about 'faults' those are not a problem at all unless major faults are at 100,000 or something. The numbers at the bottom are our primary concern.
You can run this while tapping the screen on the lock screen or dialer for 2-3 minutes or so.
while true; do adb shell dumpsys cpuinfo | awk 'NR<=6{print; next} {last=$0} END{if(NR>6) print last}'; sleep 60;echo '-------------------------------------'; done
The above linux command runs adb shell dumpsys cpuinfo every 60 seconds and and cuts out everything out but the first 6 lines and last 1. It probably works on a Mac too.
This is my phone doing nothing:
Load: 1.23 / 1.25 / 1.31
CPU usage from 127089ms to 17267ms ago (2026-05-10 02:51:09.017 to 2026-05-10 02:52:58.840) with 99% awake:
3.7% 1539/system_server: 2.3% user + 1.3% kernel / faults: 15998 minor 1328 major
2.1% 18007/app.vanadium.webview:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:0: 1.5% user + 0.6% kernel / faults: 1891 minor 489 major
0.7% 15382/adbd: 0% user + 0.6% kernel / faults: 29591 minor 18 major
1.5% 90/kswapd0: 0% user + 1.5% kernel
5.4% TOTAL: 2.2% user + 2.1% kernel + 0.5% iowait + 0.3% irq + 0.2% softirq
-------------------------------------
Load: 0.99 / 1.19 / 1.29
CPU usage from 87941ms to 55144ms ago (2026-05-10 02:52:58.840 to 2026-05-10 02:53:31.637):
2.3% 18007/app.vanadium.webview:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:0: 0.1% user + 2.1% kernel / faults: 403 minor 2 major
1.5% 1539/system_server: 0.9% user + 0.6% kernel / faults: 2247 minor 72 major
1.4% 15382/adbd: 0% user + 1.3% kernel / faults: 5794 minor
0.3% 59/rcuop/5: 0% user + 0.3% kernel
1.4% TOTAL: 0.2% user + 0.9% kernel + 0% iowait + 0.1% irq + 0% softirq
-------------------------------------
Load: 0.79 / 1.07 / 1.24
CPU usage from 115203ms to 28238ms ago (2026-05-10 02:53:31.637 to 2026-05-10 02:54:58.602):
0.8% 1539/system_server: 0.5% user + 0.3% kernel / faults: 1157 minor 24 major
0.4% 1003/dhd_rpm_state_thread: 0% user + 0.4% kernel
0.2% 2193/com.android.networkstack.process: 0.1% user + 0.1% kernel / faults: 279 minor 2 major
0.2% 15382/adbd: 0% user + 0.1% kernel / faults: 2353 minor
0.6% TOTAL: 0.1% user + 0.3% kernel + 0% iowait + 0% irq + 0% softirq
Explaining the last line:
1.4% TOTAL: 0.2% user + 0.9% kernel + 0% iowait + 0.1% irq + 0% softirq
All of these are cpu usage
iowait = storage is too slow
irq, softirq = system interrupts
See if the time near the top actually changed between readings--the intervals of measurement vary greatly.