Check the decoder errors on the Stick with the series that failed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Half a day
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- mobile-dev, testing-qa
Research direction
The work needs a Fire TV Stick and the failing IPTV series, which a newcomer probably lacks, so the check cannot be run from the repository alone. Start by reading the #107 and #121 history and the decoder fallback code in the v0.4.0 tag to see which format messages are logged. Done means the failing series' format is recorded on this issue and the audio-only and decoder-busy cases are either ruled out or split into new tickets.
Written by the indexing model from the issue text.
Description
Follow-up to #107. The code from #121 shipped in v0.4.0; this ticket holds the check that needs the Fire TV Stick and the series that failed.
What to check
Using v0.4.0 or later:
- Record the format. Play the failing series and note the format it reports here. If the episodes now play, decoder fallback may have fixed them and no error will name the format, so take it from the log:
adb logcat -s OpenTV:* - Audio over a black picture. Check for audio with no picture and no error. Media3 may skip a video track it has no decoder for, in which case the format message never appears. This is unconfirmed and #121 doesn't fix it.
- A decoder that's only busy. Decoders that won't start no longer restart automatically, including one that fails only because something else is holding it. Check that playback from Home doesn't hit this now that the preview stops first.
Acceptance criteria
- The failing series has been played on the Stick, and the format it reports is recorded here
- Checked for audio over a black picture, with a new ticket opened if it happens
- Checked that playback from Home doesn't fail because something else is holding the decoder, with a new ticket opened if it does
- Dominant language
- Kotlin
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 12m
- Merged PRs (30d)
- 77
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from neutraltone/settee
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
neutraltone/settee#157 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
neutraltone/settee#184 ·
Maintainers usually reply within 1 day
-
enhancement needs-triage
Difficulty 5/5 Over a week Newbie friendliness 30/100
neutraltone/settee#181 ·
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 5/5 Over a week Newbie friendliness 25/100
neutraltone/settee#180 · 3 comments ·
Maintainers usually reply within 1 day
-
Build Settee's lookOpenneeds-triage
Difficulty 5/5 Over a week Newbie friendliness 15/100
neutraltone/settee#172 ·
Maintainers usually reply within 1 day
All issues in neutraltone/settee
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ProdigyV21/ARVIO#874 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
user-grinch/RivoPhoneApp#358 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
andreknieriem/open-headunit#1261 ·
Maintainers usually reply within 1 day
-
e2e-failure
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
home-assistant/android#7809 ·
Maintainers usually reply within 1 day