Skip to content

Android

Fabrizio Degni edited this page Nov 16, 2026 · 14 revisions

Add an Android phone

Download the 0.2.31 ARM64 laboratory APK. It is debug-signed, not a Play Store release. Update an existing same-key installation without uninstalling to retain pairing. If the OS reports a signature conflict, stop and report it; do not erase the app’s data as a first workaround.

  1. Sign in to NodeLift Account, complete account Authenticator and select the intended personal cluster. Create its QR in Link and confirm.
  2. Scan the QR in the companion. Read the private eight-character confirmation code in Home and type it in the portal. Pending devices cannot download or execute work before confirmation.
  3. Set the node's permitted operating times in the portal. In companion Settings prepare the matching Hive model, enable participation and resume the session. The current catalog serves an approved SHA-256-verified model of at most 1 GiB.
  4. Leave the app in the foreground. In the portal verify actual worker/model readiness and run a first task. Connection status, model readiness and consent remain distinct.
  5. Inspect output, first-token/service timings and energy provenance. The new customer flow still needs physical phone qualification. See Customer onboarding.

The 0.2.31 Home card shows the actual saved connection mode and coordinator hostname/port. A retained local protocol-1/2 Mac pairing has no direct customer code or Hive assignment; create a new scoped Hive enrollment deliberately. Current protocol-3 metadata does not advertise a cluster/region to the companion, so it is explicitly unreported. Device locale is not a hub assignment.

The separate owner console remains available for existing operator-managed pilot devices. Do not change ownership records or reinstall to force an adoption.

The current worker uses ARM64 CPU. GPU/NPU acceleration is not enabled. The mobile GGUF limit is 1 GiB; context is 512–4096 and CPU threads 1–8. Battery and thermal checks may pause work. Changes to context/threads apply at the next model load.

Language supports English, 简体中文 and Italiano. Pairing does not automatically share the phone’s RAM. A foreground service is not evidence of sustained background execution on every Android vendor.

Detailed engine guide · Benchmark protocol

See the QR pairing guide for camera permissions, manual fallback and invitation lifecycle.

Historical build evidence

The records below describe their dated builds. They do not replace the current engine status.

Version 0.2.6 replaced the legacy QR scanner with CameraX, adds retry/cancel feedback, and distinguishes disabled, pressed and busy controls. At that release, its Xiaomi scan repair still needed an on-device trial. See validation scope.

Version 0.2.8 adds installation-scoped enrollment identity and local dashboard session recovery. In the November 1 exploratory test, a Xiaomi completed the draft download and CPU calibration, but two network jobs timed out and stable remote inference could not be qualified. A draft-ready label is not proof of a working inference route. See the exploratory QA report.

Version 0.2.11 organizes the companion into Home, Activity and Settings. Export logs directly from Activity. See device assessment and KPI definitions. Physical accessibility and LLM speedup remain unqualified.

Direct Hive LLM pilot

Hive now owns bounded complete-model generation without a mandatory Mac coordinator. See the LLM engine, setup, physical Linux measurements and remaining mobile gates. Complete-model placement does not pool device memories.

Clone this wiki locally