maxrave-dev / maxrave-dev/SimpMusic
Music stopping in 2.0.0 (broken since 1.0.4)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 11.4k
- Forks
- 599
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 7
Description
Music still stops on its own in 2.0.0. Play a queue, lock the phone, and after 10 to 20 minutes it stops between two songs. It also stops after a tunnel, a lift, or a switch between Wi-Fi and mobile data, sometimes straight away, sometimes only a couple of songs later once you are already back online.
If this still happens to you on 2.0.0, please comment with your phone model and Android version. Numbers help get it fixed.
@Lunar-Flame69 @Allzweck @Kahz3l @afabmoro97 @Guarmanda @rodrigosfreire86-collab @reixerus @enterman9000 @m-val-co @blank108
Three bugs. The first cuts the app off from the internet, and the other two turn any brief loss of internet into permanent silence:
- #2233: ten minutes after a song change, Android stops treating SimpMusic as a music player and cuts its internet. The next song then cannot load.
- #2239: if a song fails to download ahead of time, whether from a tunnel or from the first bug, SimpMusic keeps the broken copy forever. You get 00:00 and silence.
- #2429: if the connection hiccups mid-song, playback stops and never retries, even though pressing play fixes it instantly.
Broken since v1.0.4, only partly fixed in 1.5.0. Recent (v2.0.0) logs and detailed repro steps in the three issues above.
Probably the same: #2222, #2268, #2260, #2219, #2155, #2022, #1948, #1965, #1894
@maxrave-dev thank you for everything you put into SimpMusic, it is a genuinely great app. This one has haunted us since February. If you can find time to look into these three bugs (possible fixes maxrave-dev/core#10 and maxrave-dev/core#12, my phone plays over 6 hours uninterrupted with them), it would mean a lot. Happy to test anything or send more logs.
Contributor 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.
Research direction
Start with issues #2233, #2239, and #2429, which contain the recent logs and detailed reproduction steps for the three reported failure modes. Compare the possible fixes in maxrave-dev/core#10 and #12, then verify playback across phone locking, brief network loss, and Wi-Fi/mobile switching without stopping or retaining a broken download.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100