Lepton: Android titles installed on microSD fail to start: native libs not fully extracted (`libunity.so` not found), works from internal storage

Aperta
  • Qualcosa non va?
#2,934 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
8/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android
Ambito
infrastructure, mobile

Direzione di ricerca

This is a tracker report with no code in this repository, and the fault appears to sit in how Lepton prepares app data on microSD. Start with the attached lepton-steamlaunch-1079800.log and logcat-crash.log, then compare the extracted lib/arm64 directory against the APK's lib/arm64-v8a contents. Done means identifying why libunity.so is missing from the extracted directory on the SD-card install, which needs Lepton or SteamOS maintainer input.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Your system information
  • Steam client version: 1791328779 (steam_client_linux_arm64_beta)
  • SteamOS version: 0.4.5 (build 20261007.6125817, kernel 6.18.0-ge66bc2ca6f8c), Steam Frame
  • Opted into Steam client beta?: Not on the UI
  • Opted into SteamOS beta?: Not on the UI
  • Have you checked for updates in Settings > System?: Yes
Please describe your issue in as much detail as possible:

Expected: Pistol Whip (App ID 1079800, com.cloudheadgames.pistolwhip, APK versionCode 12) launches via Lepton when the game is installed on the microSD card, as it did before the recent SteamOS update.

Actual: The app shows no response and exits about 0.1 s after start. Every launch fails the same way. Moving the game to internal storage fixes it: Pistol Whip then launches normally via Lepton.

The crash is in UnityPlayer.loadNative:

F DEBUG : Abort message: 'JNI FatalError called: Unable to load library:
/data/app/~~Nu40_3Xcpfglc68Pr84GEA==/com.cloudheadgames.pistolwhip-QPLwc30x06O_4nXp9JrUPA==/lib/arm64/libunity.so
[dlopen failed: library "libunity.so" not found]'

Lepton then logs Clearing baked app data due to early exit.

Findings:

  • The APK is intact. Pistol Whip.apk (1,742,890,811 bytes) contains lib/arm64-v8a/libunity.so (25,175,672 bytes) and all other arm64 libs.
  • Extraction is partial. libmain.so loads from /data/app/.../lib/arm64/, but libunity.so is missing from that same directory.
  • Kernel warning on the SD-card game directory at launch:
    overlayfs: fs on '/run/media/steamos/SF/steamapps/common/Pistol Whip' does not support file handles, falling back to xino=off.
  • SD card: ext4 on mmcblk0p1, utf8 encoding (casefold).
  • Other compat tools: forcing a different Lepton version did not help. The Windows build via Proton/FEX runs.

Versions: Lepton v3.0.5 (rootfs v3.0.3), Android image LineageOS 18.1-20260925-UNOFFICIAL-lepton_arm64_only, XRService 2026-09-23 23:30:05 64f342ccba.

Suspected cause: a regression in how Lepton prepares or overlays app data when the game is on the microSD card. Native libraries do not fully end up in the app's lib/arm64 directory.

Logs attached: lepton-steamlaunch-1079800.log, lepton-logcats/steamlaunch-1079800/ (main/system/crash/kernel/radio). Failing launch: 2026-10-13 22:42 CEST.

Steps for reproducing this issue:
  1. Install Pistol Whip (App ID 1079800) to a microSD card (ext4) on Steam Frame.
  2. Launch it with the default compatibility tool (Lepton).
  3. The app does not respond and exits within a second. logcat-crash.log shows libunity.so not found. Moving the game to internal storage and launching again works.

It was working on SD card before I upgraded to SteamOS 0.4.5 therefore I suspect it is an OS

SteamFrame_logs.zip

Lingua principale
Nessun dato sulla lingua
Stelle
2.7k
Fork
88
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ValveSoftware/SteamOS

Tutte le issue di ValveSoftware/SteamOS

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.