[Android] All applications are displayed as "Unknown App" on KernelSU-Next with custom GKI kernel

Chiusa
  • Qualcosa non va?
#3,017 0 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
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android
Ambito
mobile

Direzione di ricerca

The report points at the Android side of app identification: the reporter suspects ConnectivityManager.getConnectionOwnerUid() and the UID-to-package lookup that follows it. Start by reading the attached diagnostic log to see whether the UID is captured and whether the package lookup fails or returns nothing. Reproducing needs a KernelSU-Next device, so a newcomer should expect to rely on the log alone. Done means app names and package names appear instead of "Unknown App" on that device.

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

Descrizione

Image
Device Information
  • Device: Samsung Galaxy S25+ (SM-S936N)
  • Android: Android 15
  • One UI: 7
  • Reqable version: 3.3.9
  • Root solution: KernelSU-Next
  • Kernel: Custom-built Samsung GKI kernel with KernelSU-Next and SUSFS
  • SUSFS version: 2.3.0
Problem Description

Reqable successfully captures network traffic and performs HTTPS traffic analysis normally. The root CA certificate is also correctly installed.

However, all applications are displayed as "Unknown App". Neither the application names nor their package names are identified.

This issue affects every application, not just specific apps.

Additional Observations
  1. Application identification worked correctly when I was using Magisk.
  2. The issue started after switching from Magisk to KernelSU-Next.
  3. I am currently using a custom-built Samsung GKI kernel with KernelSU-Next and SUSFS.
  4. The legacy HttpCanary app (the predecessor of Reqable) correctly identifies application names on the exact same device, while Reqable 3.3.9 displays all applications as "Unknown App".
  5. Reqable's traffic capture and HTTPS analysis work normally. The only problem is application identification: app names and package names are missing.
  6. The issue occurs with all applications, not just specific ones.
Log File

[Reqable diagnostic log](https://github.com/user-attachments/files/34233074/20261101040347-622f6140-d5c2-11f1-91c4-174ad829004f.1.log)

Questions

Could this issue be related to ConnectivityManager.getConnectionOwnerUid() or UID-to-package name resolution in a custom GKI / KernelSU-Next environment?

Could you investigate whether Reqable has compatibility issues with KernelSU-Next or custom GKI kernels?

Thank you.

Lingua principale
Nessun dato sulla lingua
Stelle
6.9k
Fork
276
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 reqable/reqable-app

Tutte le issue di reqable/reqable-app

Issue simili

Altre issue su Mobile Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.