-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
v20 background playback stops and doesn't recover #4432
Comments
Do you know how to capture a log? |
@opusforlife2 I'll try to reproduce and have a log |
@opusforlife2 No idea :D I thought there was an option in the menu, somewhere, but I guess not. |
Do you have root? |
@opusforlife2 no root. I've reinstalled v20 yesterday and it was impossible to listen to anything of long duration in the background. I'd be really surprised if it wasn't a widespread issue. |
I have encountered this issue several times as well. Mostly on my tablet - Teclast T30, stock Android 9. |
@aand18 |
Wat in tarnation!? |
@ventilaar: Does your phone have some battery saving thingy? If so, could you try turning that off? |
Getting a very similar problem. If I have more than one video in my background queue, Newpipe will immediately stop loading audio for the background player. It will keep playing anything that's in the cache, but as soon as it runs out it will start buffering and never resume playback. This doesn't seem to be 100% consistent, but I'm having a really hard time identifying what specific set of circumstances cause it to occur or not occur. Playback won't recover even if I remove all items from the queue except 1. The only way to get the background player going again is to completely empty the queue and then add a singular item back to it. I can try to obtain a log myself as well, if it'd be useful. |
Please do. We really need to pin this down. |
Also have this issue. A majority of the time it stops at 1:04 time, but I've had it in the 2 minutes area before as well. Hopefully I did the log thing correctly. It happened at 9:37. I think the 'exact' log where it broke is: "10-16 09:37:59.988" It shows as a red error and then after that error are a bunch of messages saying "Newpipe tried to update with no new data" |
I tried to extract some infromation from that logcat, here is what I have found. Up until 09:37:27 there was no activity for more than 30s, so I guess that data before that is pretty much useless. Then some notification updates can be seen:
Then the app goes to foreground (why wasn't it already foreground before?!?)
Then everything seems to still be fine, since playback and notification updates are sent.
Then for some reason the MediaSession disconnects from NewPipe and is destroyed, and from then on the playback isn't updated correctly anymore (see
Then the media session is recreated and reattached to NewPipe, but playback updates are still not sent correctly by NewPipe.
After a while
|
@Stypox Assuming you mean just do the same thing with that apk, and I don't have to do anything different within settings of that version or something then: logcat 22-49.txt logcat 22-53.txt If I have to do something in the app to capture the log and the above are just the same as the previous one then lmk. |
Thank you! Did you manually open the app at 22:49:21? I assume you didn't. So what happens is basically that Android resumes NewPipe's MainActivity completely at random in the background. The player receives the |
I'm having this problem only since the phone upgraded itself to android 10, and one comment up there made me look at the battery optimization, I think that new pipe is being throttled by the battery manager. In my phone it is placing a buffering newpipe into the notification area. When tapping that it opens to the Trending screen and happily plays anything I tap. Maybe put a timeout on the buffering module to completely flush and close? |
Checklist
Steps to reproduce the bug
Actual behaviour
I was playing a long video in background and it stopped after a few minutes. I think it was buffering (notification showed the
hourglass
instead of theplay
button).It never recovered.
I tried jumping to next in queue, but it still stayed on buffering (I don't remember if it switched to next video or ignored the "next video" command).
This could be a different bug - on v19 you could press
next
when the current video was stuck and it would play the next queued video.Finally, I exited with the
X
notification button.Expected behavior
Background playback should recover from connectivity issues.
Screenshots/Screen recordings
Logs
Device info
Just installed v20 and this hasn't happened with v19 so I think it's a bug.
Immediately after, I reinstalled v19 and it played back the same videos with no problems.
If you need more info, please advise on a way that I can contribute further.
The text was updated successfully, but these errors were encountered: