por gordol » domingo dez 18, 2022 10:06 pm
Stop/Pause has always just Paused playback, and remembers the position in the track when resumed, even when the program actually ends (task switcher force-close, swipe the paused Notification thing off screen, reboot the phone). And IMO, this is the way it should work. Like a tape cassette picks up where you left off.
The issue here appears to be one of timing. Not being a developer myself, I do not know what changes in Android 13 / OneUI 5 would have caused this, I just know that if "enough time" has passed since stopping playback, I can end or let end the MMA process and pick up where I left off later, but if I do not the track resets to the beginning.
I haven't actually timed it, but it feels like it needs at least 45 seconds, maybe a full minute or more. There is a substantial gap in my unintentional testing here: It's always been less than a minute when this reset happens, and more than 5 minutes when it does not.
Stop/Pause has always just Paused playback, and remembers the position in the track when resumed, even when the program actually ends (task switcher force-close, swipe the paused Notification thing off screen, reboot the phone). And IMO, this is the way it should work. Like a tape cassette picks up where you left off.
The issue here appears to be one of timing. Not being a developer myself, I do not know what changes in Android 13 / OneUI 5 would have caused this, I just know that if "enough time" has passed since stopping playback, I can end or let end the MMA process and pick up where I left off later, but if I do not the track resets to the beginning.
I haven't actually timed it, but it feels like it needs at least 45 seconds, maybe a full minute or more. There is a substantial gap in my unintentional testing here: It's always been less than a minute when this reset happens, and more than 5 minutes when it does not.