Tracking: Whisper-class offline ASR on Android — engine-side P0
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
- 20/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Ambito
- machine-learning, mobile
Direzione di ricerca
Start with the linked P0 issues #1275–#1281 to identify a bounded engine-side task; this tracking issue spans native kernels, scheduling, VAD, ONNX import, and numerical tooling. Use the stated Pixel-class whisper-tiny.en exit criterion and M2-A5 harness as the completion guide: the encoder must be at least 5× faster than the scalar path, matmuls must name their kernels, and Silero VAD must match ONNX Runtime within 1e-4 without an ORT dependency.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Goal
Make SKaiNET the obvious engine for a fully offline, Whisper-class transcription app on Android. The reference case is an existing app on LiteRT (Whisper large-v3-turbo split encoder/decoder on OpenCL FP16, Parakeet TDT 0.6B, Silero VAD on ONNX Runtime, a 350M LLM for titles on LiteRT-LM): three native runtimes in one APK, hand-written mel/FFT/resampler/tokenizers/decode loops, and model-file surgery plus byte-patched runtime AARs to work around GPU numerics bugs. Its author's Pixel 7 Pro numbers are the bar:
| Path | 14 s memo | RTF |
|---|---|---|
| LiteRT CPU, XNNPACK, 2×3 threads | 82.2 s | 5.9 |
| LiteRT GPU, OpenCL FP16 | 34.4 s | 2.5 |
Target for this milestone: CPU-only SKaiNET Whisper large-v3-turbo at or below 82 s on the same class of device, token-identical to whisper.cpp, with the audio side and VAD served by SKaiNET libraries.
What 0.54.0 already provides
- JNI NEON backend (
skainet-backend-jni-cpu) for every GGML quant format, runtime dotprod dispatch, threaded packed matmuls, self-installing dispatch (#920 → 0.50–0.52). - Off-heap mapped weights on Android (
AndroidGguf.loader,WeightForm(residency = MAPPED)), memory plan and device fit check before load; a 1.0 GB Q4_K_M LLM decodes at 61–66 ms/step on a Pixel 8a. Lstmwith explicit state (#823);transformer-coreKV cache; tape → StableHLO export at billion-parameter scale (0.53.0).
Engine-side P0 (this repo)
- #1275 — dense FP32/FP16 matmul on the JNI tier (attention is scalar on Android today)
- #1276 — native fused LayerNorm / GELU / softmax / conv1d kernels
- #1277 —
Scheduleon Android verified and measured for SDPA - #1278 — native Silero VAD model on
Lstm, weights from the upstream ONNX file - #1279 — ONNX importer: LSTM, Gather, Unsqueeze/Squeeze, Cast, Where, If
- #1280 —
TensorDump+TensorComparefor divergence localisation - #1281 — FP16 simulation context + FP32-accumulating LayerNorm lowering rule
Out of this repo, tracked with the ASR projects
- Whisper v3 128-mel
MelConfigin the audio library (HF-exact constants). - Whisper large-v3-turbo model + self-attention KV cache + timestamp rules + long-form windowing in the Whisper project, on top of the current engine pin.
- Consumer docs: the artifact picker must list
skainet-backend-jni-cpu; theAndroidGgufKDoc still says packed tensors heap-stage (fixed in 0.50.0).
Follow-ups already identified (P1, separate issues when P0 lands)
AndroidGguf.loaderover anAssetFileDescriptorso anoCompressGGUF is mapped straight from the APK instead of copied out.- Windowed mapping to lift the 2 GB single-region cap.
- HF
tokenizer.jsonbyte-level BPE loader for Whisper vocab. - Parakeet TDT cartridge reusing
Lstmand the 128-mel config.
Exit criterion
whisper-tiny.en runs on a Pixel-class phone through the JNI tier with mapped weights and the M2-A5 harness names the kernel behind every matmul; the encoder is ≥ 5× faster than the 0.54.0 scalar path; Silero VAD matches ONNX Runtime within 1e-4 with no ORT dependency.
- Lingua principale
- Kotlin
- Stelle
- 52
- Fork
- 15
- Merge medio
- 1g 8h
- PR unite (30g)
- 37
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di SKaiNET-developers/SKaiNET
-
coding good first issue platform size:xs skill:js sub-issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
SKaiNET-developers/SKaiNET#1232 ·
I maintainer di solito rispondono entro 1 giorno
-
skeep tracking
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
SKaiNET-developers/SKaiNET#1331 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
assessment size:s skill:review sub-issue
Difficoltà 4/5 1-2 giorni Idoneità per principianti 18/100
SKaiNET-developers/SKaiNET#1330 ·
I maintainer di solito rispondono entro 1 giorno
-
documentation good first issue size:s skill:docs sub-issue
Difficoltà 3/5 1-2 giorni Idoneità per principianti 78/100
SKaiNET-developers/SKaiNET#1329 ·
I maintainer di solito rispondono entro 1 giorno
-
coding good first issue size:s skill:kotlin-core sub-issue
Difficoltà 3/5 Mezza giornata Idoneità per principianti 75/100
SKaiNET-developers/SKaiNET#1328 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di SKaiNET-developers/SKaiNET
Issue simili
-
[BUG] Navigation drawer drops library-name suffixes without ellipsis (1.0.8, NVIDIA Shield)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
damontecres/Wholphin#2069 ·
I maintainer di solito rispondono entro 1 giorno
-
Android (vision-camera-location): HybridLocationManager never quits its HandlerThread on disposeAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
margelo/react-native-vision-camera#4217 ·
I maintainer di solito rispondono entro 4 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
saisaharsh3/Leftovers#13 · 1 commento ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 67/100
navikt/esyfo-narmesteleder#700 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
nightscout/AndroidAPS#5280 ·
I maintainer di solito rispondono entro 1 giorno