You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AG-216: hardware decoders stop working until reboot — all cells receive, none decodes #145
Seen on Aceline-1 (AG-216, Android 10) on 2026-10-13 after a long test session (many APK installs, app restarts, a Majestic restart on a camera, an app killed by Back while in multi-view).
Symptom: every multi-view cell receives frames (in_fps 5–30) but none decodes (out_fps 0, corner … key frames · 0.0 fps). Only the first two decoders log Start video decoder; their decode threads then block and the queue overflows (Quad-0 queue full, NAL dropped). The other cells never get a decoder.
Not the app build: force-stop + relaunch, the newest build and an older build that had worked 20 minutes earlier all behave the same. A device reboot fixes it at once (same APK).
So the platform's decoder service is stuck. Ideas:
detect it: no cell decoded anything for N s although all receive → say so in the corner / on the debug page ("Video decoder of the device not responding — restart the device") instead of 0.0 fps;
find out what leaves it stuck (a codec not released when the process dies mid-configure?) and how to reproduce it.
Detection merged in #147 (af88fb7): banner "The video decoder of this device does not respond … Restart the device", decoder_stuck in /stats.json, red note on the debug page — after 20 s with H.264/H.265 slices arriving in ≥ 2 clean cells and no cell decoding. The cause (what leaves the platform decoder service stuck) stays open here.
Closed as not reproducible: seen once (2026-10-13, after a long test session), fixed by a reboot; no recurrence since. The app now detects it and asks for a restart (#147). Reopen if the banner The video decoder of this device does not respond / decoder_stuck shows up again, on any device — with what ran before it (logcat, dumpsys media.codec).
Activity
fix: the stuck banner goes into the root layout by id (#145)
Merge pull request #147 from OpenIPC/fix/decoder-stuck
compot-dev commentedon Oct 13, 2026
Detection merged in #147 (af88fb7): banner "The video decoder of this device does not respond … Restart the device",
decoder_stuckin/stats.json, red note on the debug page — after 20 s with H.264/H.265 slices arriving in ≥ 2 clean cells and no cell decoding. The cause (what leaves the platform decoder service stuck) stays open here.compot-dev commentedon Oct 13, 2026
Closed as not reproducible: seen once (2026-10-13, after a long test session), fixed by a reboot; no recurrence since. The app now detects it and asks for a restart (#147). Reopen if the banner
The video decoder of this device does not respond/decoder_stuckshows up again, on any device — with what ran before it (logcat,dumpsys media.codec).feat: say when the device's video decoder stands still — frames arriv…
fix: the stuck banner goes into the root layout by id (#145)
Merge pull request #147 from OpenIPC/fix/decoder-stuck