first i would love to thank you guys for the hard work on this new version !
and look i really appreciate the convincing arguments of @opusforlife2 and the deadly comments of @avently ,but despite that i am still opposing the idea of having two seperate players while watching a video (the main player and the one in the notifications).
nonetheless here are a few issues that i've encountered probably due to that (i might be wrong) :
(initial conditions: no trending page, autoplay is off, and a smile?)
issue number 1:
issue number 2:
issue number 3:
(another issue related to this one is that when you press the back arrow you close the stream instead of minimizing it)
issue number 4:
issue number 5 (not sure how to reproduce):
Opusforlife2 will be here soon and will close the issue...
But thanks for a great start! I'm not sure how to translate the "deadly comments" but the post is something I wanted to read
@avently You know the code. If all 5 issues written here are related to the same underlying problem, then we don't need to close it. If 2 of them are one problem and 3 are another problem, then we make two issues, and so on.
@avently i was just kidding about the deadly comments let's say not "user friendly" ones haha
@opusforlife2 sorry for putting a bunch of issues in the same place again !
@opusforlife2 an out of subject question : is it fine to post issues that i have no idea how to reproduce?
(in the background)? I'm just tried to open a video in background player with steps provided but didn't find anything unusualis it fine to post issues that i have no idea how to reproduce?
@panacist You should, because someone else may find out how to reproduce it. But make sure you give as many details as possible.
@avently

@panacist After you find out which are real issues and which aren't, I expect you'll open separate bug reports for each because, as avently rightly said, I will close this.
(2). You can open an issue if you want but I don't think this rare situation should cost hours of finding a solution which don't look ugly
(4). If I don't stop the previous video you'll get video working in the background without displaying it. It will load a video (not an audio) which is a bad situation. We didn't talk about this implementation because it has no alternatives
We talked about when to stop the video: right after choosing another or when another one has downloaded info to show. We chose the second way.
(1) Show a screenrecord please
@avently
Not angry. Just firm in my stance. :3
@opusforlife2 why are you sooooo angry? We just listening people's problems...
no need to open an issue
@panacist Open an issue, please. Whether or not someone fixes it is not your problem.
@avently What is the cause of (2)? Why doesn't the minimised player stay?
For (5), should we avoid showing buttons until video details have loaded?
@opusforlife2 because when you press back and your backstack is empty, activity with all fragments gets destroyed (mini player located inside a fragment). After returning back you have a blank activity without loaded videodetailsfragment
@avently Okay. Can there be a condition added that if the foreground service is active/playing a stream, not to close the minimised player on back press? The entire point of the minimised player was that it would let streams play uninterrupted until the user manually closed it.
@opusforlife2 not like you said, but in a different way. Once new activity gets created the service needs to be found in running processes and in case it's found activity should send a broadcast related to the need to open and connect mini player. The broadcast i'm talking about I added in the last my PR. These are all instructions I can give you. If you know Android it's enough
@avently Could you open a new issue with these instructions? I'll see if someone can work on it.
@opusforlife2 no, I'm not. You may open if you want.
@panacist I'm closing this. Please open separate issues now.
Most helpful comment
@opusforlife2 why are you sooooo angry? We just listening people's problems...