Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] system freezes with repeated native crashes (lmkd SIGSEGV, commcenterd SIGABRT) on Android 16

Aperta
  • Qualcosa non va?
#923 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
android, kotlin
Ambito
mobile-dev, operating-systems

Direzione di ricerca

Inizia esaminando gli archivi dei log di Vector allegati e i crash segnalati di lmkd, commcenterd, zygote64, USB HAL e root-daemon. Riproduci il problema con il dispositivo Android 16 e i moduli indicati, quindi determina se Vector è coinvolto disabilitando i moduli uno alla volta. Il lavoro è considerato completato quando viene identificata una causa riproducibile correlata a Vector e una correzione convalidata, oppure quando vi sono prove chiare che i crash siano esterni.

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

Descrizione

bug
Steps to reproduce/复现步骤

Steps to reproduce:

  1. OnePlus 8T (KB2001IN), rooted: KernelSU (SukiSU ultra) + NeoZygisk + Vector.
  2. Enable Vector and the installed Xposed modules (Oxygen Customizer nightly, CorePatch, disableflagsecure).
  3. Use the device normally (open apps, USB, browsing). After a while the UI starts freezing /
    apps become "Not Responding" for ~15s, recurring throughout the day.
  4. Attached Vector log zip contains many same-day ANRs for system_server plus repeated native
    daemon crashes.

Expected behaviour:
System stays stable. No native daemon crashes and no UI freezes with the installed module set.

Actual behaviour:
Repeated native SIGSEGV/SIGABRT crashes causing UI freezes and ANRs:

  • /system/bin/lmkd : SIGSEGV (SEGV_MAPERR) on its HwBinder thread. Recurring multiple times on
    2026-08-17 (13:09, 15:02, 23:28, 23:40). Crash frame is unmapped ; the crashed
    thread's IPC buffer contains "Status(EX_TRANSACTION_FAILED): DEAD_OBJECT".
  • /odm/bin/commcenterd : SIGABRT + SIGSEGV, also recurring (e.g. 2026-08-17 23:42).
  • zygote64 : SIGSEGV (SEGV_ACCERR) - tombstone_00.
  • [email protected] : SIGABRT (2026-08-14) - USB HAL crash.
    Result: system_server ANRs (9 on 2026-08-17, mostly "Blocked in handler on main thread for 15s"),
    UI freezes, unresponsive apps. Freeze recurred at 23:52 and 23:55 while capturing these logs.

Xposed Module List:

it.dhd.oxygencustomizer  (Oxygen Customizer nightly-206 #1977)
org.lsposed.corepatch
io.github.lsposed.disableflagsecure
Root implementation:
KernelSU (SukiSU ultra, package com.sukisu.ultra); root daemon also crashed with SIGABRT.
Installed via OrangeFox R12.1 recovery.
System Module List:
zygisk_vector    Vector v2.2 (3097-35b510cb-JingMatrix-Vector)
zygisksu         NeoZygisk v2.4 (290-c1b5e42-release)
OxygenCustomizer 0.0.60
playintegrityfix v4.7-1-inject-s
specter          1.4.4-17-g7d4ad6a
teesim           v4.0
Re-Malwack       v8.2-test (disabled: modules/Re-Malwack/disable)
Vector version:
v2.2 (3097-35b510cb-JingMatrix-Vector)
Android version:
Android 16 (SDK 36), security patch 2026-07-01
OnePlus 8T stock-based ColorOS/Oxygen android16 image
ro.build.fingerprint: OnePlus/KB2001IN/OnePlus8T:16/TP1A.220905.001/U.R4T3.e84bcb_160c4b6_160c4a0:user/release-keys
Version requirement:
- I am using the latest debug build from GitHub Actions (https://github.com/JingMatrix/Vector/actions?query=branch%3Amaster).
Logs:
Attached: Vector-logs-release-20260817-234739 (2).zip
(Newer capture at 23:54:38; includes the two most recent ANRs.)



[Vector-logs-release-20260817-234739 (2).zip](https://github.com/user-attachments/files/31150708/Vector-logs-release-20260817-234739.2.zip)

### Expected behaviour/预期行为

System stays stable. No native daemon crashes and no UI freezes with the installed module set.

### Actual behaviour/实际行为

Repeated native SIGSEGV/SIGABRT crashes causing UI freezes and ANRs:

- `/system/bin/lmkd`: SIGSEGV (SEGV_MAPERR) on its HwBinder thread, recurring multiple times on 2026-08-17 (13:09, 15:02, 23:28, 23:40). Crash frame unmapped `<unknown>`; IPC buffer contains `Status(EX_TRANSACTION_FAILED): DEAD_OBJECT`.
- `/odm/bin/commcenterd`: SIGABRT + SIGSEGV, recurring (e.g. 2026-08-17 23:42).
- `zygote64`: SIGSEGV (SEGV_ACCERR) — tombstone_00.
- `[email protected]`: SIGABRT (2026-08-14) — USB HAL.

Result: 9× system_server ANRs on 2026-08-17 ("Blocked in handler on main thread for 15s"), UI freezes, unresponsive apps. Freeze recurred at 23:52 and 23:55 while capturing these logs.

### Xposed Module List/Xposed 模块列表

```shell
it.dhd.oxygencustomizer  (Oxygen Customizer nightly-206 #1977)
org.lsposed.corepatch
io.github.lsposed.disableflagsecure
Root implementation/Root 方案

KernelSU (SukiSU ultra, package com.sukisu.ultra); root daemon also crashed with SIGABRT. Installed via OrangeFox R12.1 recovery.

System Module List/系统模块列表
zygisk_vector    Vector v2.2 (3097-35b510cb-JingMatrix-Vector)
zygisksu         NeoZygisk v2.4 (290-c1b5e42-release)
OxygenCustomizer 0.0.60
playintegrityfix v4.7-1-inject-s
specter          1.4.4-17-g7d4ad6a
teesim           v4.0
Re-Malwack       v8.2-test (disabled)
Vector version/Vector 版本

v2.2 (3097-35b510cb-JingMatrix-Vector)

Android version/Android 版本

Android 16 (SDK 36), security patch 2026-07-01 OnePlus 8T stock-based ColorOS/Oxygen android16 image ro.build.fingerprint: OnePlus/KB2001IN/OnePlus8T:16/TP1A.220905.001/U.R4T3.e84bcb_160c4b6_160c4a0:user/release-keys

Version requirement/版本要求
Logs/日志

Vector-logs-release-20260817-234739 (2).zip

Lingua principale
Kotlin
Stelle
12.6k
Fork
850
Merge medio
20m
PR unite (30g)
1

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 JingMatrix/Vector

Tutte le issue di JingMatrix/Vector

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.