Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Playback robustness: process death, queue restore, resume

Open
  • Is something wrong?
#11 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
audio-video-rtc, mobile

Research direction

Start by locating the Android playback service and its media session, then trace how the queue, playback index, position, and shuffle order are saved and restored. Check the existing playback and notification tests, if present. Done means playback resumes after process death and reboot through the listed entry points, with state restored and no duplicate notifications or stale sessions.

Written by the indexing model from the issue text.

Description

area/playback priority/p0 type/verification
  • Kill the process while playing and resume from the notification
  • Reboot and resume via media button / Bluetooth
  • Queue, index, position and shuffle order restored
  • Playback resumption from Android's media resumption UI
  • No duplicate notifications or stale sessions
Dominant language
Kotlin
Stars
1
Forks
0
Avg merge
30m
Merged PRs (30d)
62

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from isaacault/polyphony

All issues in isaacault/polyphony

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.