Linux ARM64 clients receive an Android worker binary from the pool

[Wesley666Wesley]

Setup

• Client: qli-Client 3.8.5.0 (official package qli-Client-3.8.5-Linux-arm64.tar.gz)
• OS: Ubuntu 24.04.4 LTS aarch64 (Radxa Dragon Q8B, Snapdragon SC8280XP)

Problem

After successful pool authentication, the worker pushed by the pool
(workerConfig-CPU.lock is decoded by the client into qli-worker-ARM64)
is an Android/bionic build, not a glibc Linux build:

$ file /q/qli-worker-ARM64
/q/qli-worker-ARM64: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV),
dynamically linked, interpreter /system/bin/linker64, stripped

The interpreter /system/bin/linker64 is the Android dynamic linker and does
not exist on Linux, so the worker can never start:

$ /q/qli-worker-ARM64 --help
-bash: /q/qli-worker-ARM64: cannot execute: required file not found

The client log then loops forever:

[ERRO] Failed to start qli-worker-ARM64: An error occurred trying to start
process '/q/qli-worker-ARM64' with working directory '/q'. No such file or directory
[ERRO] qli-worker-ARM64 Error in Process Watchdog.
System.InvalidOperationException: No process is associated with this object.

Verified facts

1. The official Linux-arm64 packages (3.8.3 / 3.8.4 / 3.8.5) contain only
   appsettings.json, qli-Client and qli-Service.sh — no worker is bundled.
2. No direct worker download URL exists on dl.qubic.li
   (tried many naming patterns, all 404).
3. Deleting the worker only results in the same Android binary being re-pushed
   (workerConfig-CPU.lock and qli-worker-ARM64 timestamps match).
4. The same token/client works fine on x64 (worker auto-downloaded and mining
   normally there), so this is specific to the ARM64 worker distribution channel.

Result

Linux ARM64 mining is currently impossible: auth works, tasks are assigned,
but the delivered worker can never execute on glibc Linux.

Request

Please push a proper glibc Linux ARM64 worker build
(interpreter /lib/ld-linux-aarch64.so.1) for Linux ARM64 clients.