Closed z9xx7o0 closed 8 months ago
i did experiment with the "resume if was paused by interruption" with no luck, should investigate further. about resuming from notification, this really weird as the notification is kept alive so it should work normally, most probably an issue with android side, whats ur device model & Android version? logs might help too.
I see the "resume if was paused by volume" is working just fine. I don't know why the other one doesn't work. I am currently running oneUi 6.0, which is android 14, and I am on the Samsung Galaxy s23 ultra. Sorry, I don't know how to get the logs, but I hope that helps!
Edit: I wanted to mention that I am running the app as unrestricted, so my phone doesn't just kill the app after it stops playing.
volume works cuz they are both handled differently, a listener just keeps listening to device volume and plays/pauses accordingly
while the other one is managed internally by android media session token, i suspected at first that the other apps dont send back that they stopped playing, but it seems there is more than that
investigating will surely take time
about the play from notification issue, i highly doubt its due to android 14 shakalaka thingy, logs might be needed idk so try sharing it from "settings > about > share logs" otherwise ill install android 14 emulator and check things, but later
@z9xx7o0 as mentioned,
thanks for pointing these out
Thanks for the update it fixed a lot of problems and added so many new features, but there is still one that is the most important, when the track is paused I can't resume it from the notifications. Also, the "resume if was paused by interruption" option doesn't work, so anytime the track gets paused by an interruption and the interruption is finished, I want the track to resume but it doesn't. So I go to the notifications and try to resume it, but i can't do that, so I have to stop what I'm doing, open the namida app, resume the track, and then come back.