Skip to content

Long pause before next song is played #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cweiske opened this issue May 12, 2025 · 3 comments
Open

Long pause before next song is played #162

cweiske opened this issue May 12, 2025 · 3 comments

Comments

@cweiske
Copy link

cweiske commented May 12, 2025

I'm using YAACC 4.3.2 on an old Wileyfox Swift phone (Android 10 /LineageOS 17.1) that I use on my night stand as alarm clock.

When playing a whole album, YAACC does not play the second song when the first song is complete - it takes several minutes until the next song is played. My guess is that the controller does not notice that the song is finished and thus does not switch to the next song correctly.

Currently the music of song 2 just ended and the UI shows a play position 02:15 of 04:32.

Song 3 play position went until ~1:35, when the play position reset to 00:00 and started increasing again.
Song 4 exhibits the same problem; at 01:34 it reset the play position back to 00:00. When it reaches 01:34 again, the play position continues to increase - until the end time of 04:25, with much silence at the end.

All songs exhibit this problem: At 01:34 or 01:35 the play position resets to 00:00.

There are no yaacc log messages to see around the 1:35 timestamp in "adb logcat".


Note that this problem does not occur on a Fairphone 4 running Android 15 (LineageOS 22).

@cweiske
Copy link
Author

cweiske commented May 12, 2025

This also happens when manually jumping to a specific position:

  1. Start playback
  2. Jump to 01:00
  3. Let YAACC continue to play
  4. at ~02:37 it jumps back to 01:00.

@tobexyz
Copy link
Owner

tobexyz commented May 13, 2025

Does this happen also in an older version or only in the new one 4.3.2?

@cweiske
Copy link
Author

cweiske commented May 13, 2025

This bug is bugging me since over a year, but I only took the time to report it yesterday. So it's not the new version only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants