Play speed not remembered, media bar closing since upgrade to 1.1.1 #114

New Issue

Closed

opened 2023-05-24 13:46:47 +00:00 by d7415 · 2 comments

d7415 commented

2023-05-24 13:46:47 +00:00

Hi,

Since upgrading to v1.1.1, which mentions in its changelog "playback speed is remembered correctly", Escapepod no longer remembers my play speed when closed. Additionally, it is removed from the "media" bar in the notifications area much more quickly than before (or than other media apps on my phone).

v1.1.1 installed on a Samsung S23 via F-droid.

ETA: I think v1.1.0 had an issue where the playback speed would display as 1.0x when restarted, but for me it played at the correct speed.

Hi, Since upgrading to v1.1.1, which mentions in its changelog "playback speed is remembered correctly", Escapepod no longer remembers my play speed when closed. Additionally, it is removed from the "media" bar in the notifications area much more quickly than before (or than other media apps on my phone). v1.1.1 installed on a Samsung S23 via F-droid. ETA: I think v1.1.0 had an issue where the playback speed would *display* as 1.0x when restarted, but for me it played at the correct speed.

y20k commented

2023-05-30 13:10:24 +00:00

Owner

Hi,

thanks for the bug report. (BTW. I prefer separate tickets for separate issues. But let's not complain ;-) I am actually super-glad about every bug report!!)

I. Playback speed

I tried to replicate the issue using the following steps:

start playback of episode a
change playback speed to 2x
start playback of episode b
playback speed remains at 2x

and I tried:

start playback of episode a
change playback speed to 2x
pause playback
quit Escapepod using the app switcher (swipe)
start playback of episode b
playback speed remains at 2x

=> Can you give me instructions on how you were able to reproduce the issue

II. Media notification is cancelled too early

The Android System kills inactive background processes pretty aggressively. Escapepod's notification is cancelled during a regular sweep. I used a trick to prevent this in older versions of Escapepod: I added a cancel button to the notification. With v1.1.1 I use the new media3 library which among other things handles an app's media notification. I cannot easily add a cancel button anymore. And since keeping a background service forcefully alive seems to be viewed as unwanted behavior, I have no plans to customize/hack around that limitation. There is another way: If Escapepod would "announce" a media library to the system, it could use the official Media Resumption behavior. I plan to implement this some time in the future. But I know from Transistor that this is a bit tricky.

Hi, thanks for the bug report. (BTW. I prefer separate tickets for separate issues. But let's not complain ;-) I am actually super-glad about every bug report!!) ### I. Playback speed I tried to replicate the issue using the following steps: 1. start playback of episode a 2. change playback speed to 2x 3. start playback of episode b 4. playback speed remains at 2x and I tried: 1. start playback of episode a 2. change playback speed to 2x 3. pause playback 4. quit Escapepod using the app switcher (swipe) 5. start playback of episode b 6. playback speed remains at 2x => Can you give me instructions on how you were able to reproduce the issue ### II. Media notification is cancelled too early The Android System kills inactive background processes pretty aggressively. Escapepod's notification is cancelled during a regular sweep. I used a trick to prevent this in older versions of Escapepod: I added a cancel button to the notification. With v1.1.1 I use the new media3 library which among other things handles an app's media notification. I cannot easily add a cancel button anymore. And since keeping a background service forcefully alive seems to be viewed as unwanted behavior, I have no plans to customize/hack around that limitation. There is another way: If Escapepod would "announce" a media library to the system, it could use the official [Media Resumption](https://developer.android.com/guide/topics/media/media-controls#supporting_playback_resumption) behavior. I plan to implement this some time in the future. But I know from [Transistor](https://codeberg.org/y20k/transistor) that this is a bit tricky.

d7415 commented

2023-06-02 16:37:00 +00:00

Poster

As this will make finding the problem all but impossible, I'll close this until I can make it happen.

Glad to head that the Media notifications are on the roadmap - Thanks!

Now that I try, I can't reproduce it that way either, even with force stopping and playing with power settings. It's been happening to me fairly frequently after EscapePod has been closed (and presumably cleaned up in the background), but I'm unable to reproduce on command. As this will make finding the problem all but impossible, I'll close this until I can make it happen. Glad to head that the Media notifications are on the roadmap - Thanks!