Android/Termux: 0 CPU cores detected - permanent backoff

[17thlonestar-design]

EvoMap on Android/Termux reports 0 CPU cores, causing permanent backoff:

System load 29.58 exceeds max 0.0 (auto-calculated for 0 cores). Backing off 60000ms.

Impact: 100% of Android users blocked from EvoMap network.

Environment

• Device: Samsung Galaxy A14 5G
• Platform: Termux, Android 13
• Node.js: v25.8.2
• EvoMap: Current version

Reproduction

1. Install EvoMap on Android/Termux device
2. Run evolver cycle
3. Observe backoff due to 0 core detection

Root Cause

Node.js2

• EvoMap: Creturns empty array on Android/Termux.

This causes max load calculation of 0.0, triggering immediate backoff.

Evidence:

[2026-04-19T09:00:08.283Z] [FIX] os.cpus() returned 0, forcing 4 cores
[2026-04-19T09:00:08.284Z] [FIX] os.loadavg() capped: [29.29, 29.36, 29.38] => [2, 2, 2]

Workaround (Tested & Working)

Runtime patch EvoMap network(attached):

• Forces 4 cores minimum on Android
• Caps loadavg at 2.0 per core
• Zero breaking changes

Test Results:

• 50+ stable evolution cycles
• 0 errors
• Status: RUNNING

Suggested Fix

Add Android detection in load calculation:

const cores = os.cpus().length || 4;
const load = os.loadavg().map(l => Math.min(l, cores * 2));


**Note:** fix_load.js runtime patch available on request. Contact @OslidaBinLotta on Telegram.

Submitter: AO (@OslidaBinLotta)
Node ID: node_29a3275b475f7258

[autogame-17]

Fixed in v1.69.3 (just shipped to npm and GitHub Releases).

Root cause: on your Android/Termux build os.cpus() returns [], which collapsed the auto-calculated load ceiling to 0.0. Every cycle then saw load1m=29.29 > 0.0 and backed off forever.

What changed in 1.69.3:

• New detectCpuCount() helper with a hard floor of 4 cores when os.cpus() is empty or throws.
• getDefaultLoadMax() now always returns at least 0.9, so the ceiling can never be zero.
• Runaway loadavg values (common on Android when the kernel reports cumulative load across dormant cores) are clamped to 2 * detected_cores before the comparison.

Please upgrade and let us know if it resumes on your device:

npm install -g @evomap/evolver@1.69.3
evolver run

Thanks for the detailed report and the full [Evolver] log output, it pinpointed the bug immediately.