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
Odyssey loses state when closed #113
Comments
Yes you are right. Actually Odyssey saves it state if you swipe the notification away (in pause state) or after 5 Minutes. The problem is that with the migration to android 8 api we are not running for this long. We'll fix this |
Hi, |
Seems to work (LineageOS 7.1, Odyssey 1.1.11 via Fdroid).
However, on killing the app (force stop via task manager - similar to OOM) does not restore the latest state, but the previous one is restored. |
OOM kills are SIGKILL terminations. There is nothing Odyssey can do, thats the definition of kill. Android usually does not use SIGKILL for termination operations but gracefully terminates services. also 1.1.11 is not the newest version |
@djselbeck Sorry, I was expecting Fdroid to be up to date and did not verify it. |
They automatically follow the tagged releases on github and then build it from source. Which is nice, because this way applications are guaranteed to match the provided source code. Today version 1.1.12 landed it f-droid ;) |
That's seen evidently as the tracks in queue are those I listened some time before, not the latest.
This happens at OOM situation which is the part of Android world, sorry.
I think that Odyssey should take extra care of it:
The text was updated successfully, but these errors were encountered: