Hi! I listen to pods at work with AntennaPod, and after some time the app gets shut down entirely, so I have to restart it and play from where it stopped. This started happening recently and was not a problem before. I have turned off battery optimization in Android settings. What could be the reason?
And when does it stop exactly?
There is a known issue when steaming, meanwhile downloading and then leaving the internet connection (like WLAN), the Playback doesn’t switch to the downloaded file and just stops, is that what’s happening?
Maybe you can try to write some concrete steps on how to reproduce this issue, like what do you do exactly so that the issue occurs?
At work (where there’s no wi-fi) I have a queue of podcasts I listen to. I think they’re streaming rather than having been downloaded beforehand (how can I find out?). After listening for some time - it seems to be random - playback stops and the app has been shut down (it’s no longer in tabs or what it’s called), so I have to start it again and start playback again.
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@8be3bce rejected from java.util.concurrent.ScheduledThreadPoolExecutor@e8c6aef[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1559]
at de.danoeh.antennapod.core.service.playback.-$$Lambda$LocalPSMP$qJO6fE9RrQzc5jd_fVqGKQZ-MqQ.run(Unknown Source:2)
at de.danoeh.antennapod.core.service.playback.-$$Lambda$LocalPSMP$1$bWQm-SvHzg-23xcSmeXJeDjoCno.run(Unknown Source:4)
at java.lang.reflect.Method.invoke(Native Method)
I’ve checked three times now, and none of these times when I’ve restarted the app is their a stack trace available. My provisional conclusion is that the app is not crashing per se, but some external process is closing it. But what could that be?
Some vendors make crappy modifications to Android trying to save battery that don’t follow Google’s specs (see https://dontkillmyapp.com) but I have not seen that from Motorola yet. Did you try adding an exception from battery optimization?