I have the same problem and it only showed up recently, so i guess the issue is due to the latest update. While it first started, while listening via bluetooth in my car, i can safely say, that it also occurs on my device while listening without any bluetooth speakers/headphones connected. Manually skipping forward until reaching the end of the podcast worked for me to break out of the loop.
I also noticed the problem with 3.12. The continuos loop happens when using Bluetooth and with phone plug. It doesn’t happen when using the phone speaker. I don’t reorder the queue. Normally I could start anywhere on the queue and it would play down the list from where I started.
i have to say, the only place, where i can more or less reliably reproduce this, is in my car. i had the problem once just listening on the phone, but can not reproduce this and neither when listening on bluetooth headphones.
Thanks! From the logs, I can see that AntennaPod decided to stop playback because there was nothing more to play. The service got stopped completely. But then 30 seconds later your car sent a “play” button press and somehow started the most recently played episode again. Can you confirm the following please?
Do you have “continuous playback” enabled or disabled? Does it make a difference?
Do you have more episodes in the queue below the one you played?
Can you confirm the 30 seconds delay before it started playing again?
Continous playback is on, let me check tomorrow, what happens if i turn it off.
Yes, there are more episodes following the one that loops.
There was no delay and there never is. The episode i played was only like 45 seconds, so i dont have to skip to the end. Maybe the pause you see is me manually starting/stopping something before. There is a lot of trial and error in this log from trying to reproduce anything.
Just want to add. Today I used AntennaPod with a USB-Headset while biking and there were no issues regarding continuous playing the episodes. Seems to be either an issue with bluetooth and/or playing it in a car.
i changed continous playback to off, but that doesn’t change anything.
also i left the episode running and it keeps looping, as long as i don’t manually skip/fast forward.
i sent you another logfile from just this morning and just looping this one 45 second episode two times. when it started again the second time, i stopped it manually.
I wonder if the extremely short episode might be a clue. I’ve never experienced this issue, either in the car or with my earbuds, but the shortest episodes I play are around 5 minutes.
good idea, but no, it loops also much longer episodes. i only chose this very short trailer for testing purposes, so i don’t have to skip forward a lot and to interfer with testing as little as possible.
Thank you and @Axel for responding to my observation. My usual episodes are between 5 and 70 minutes and I’ve been trying different things to see if I can duplicate what you’re seeing. Other potential variables that come to mind are things like:
Auto-download (which I don’t use)
Stream vs. download (I never use mobile data for podcasts; I stream or download episodes at home via Wi-Fi)
Sorting the playlist (I move things around manually; I don’t use the sort function)
Here’s a long shot, but I’m mentioning since it’s not the default configuration:
Enque location: My downloaded episodes are added to the “Back” (bottom) of the queue rather than the default “Front” (top) of the queue.
I’m still puzzled about the apparent Bluetooth correlation. I always use Bluetooth in the car, but generally use the phone’s speakers at home. I’ve made a point of using buds at home most of the time, but still haven’t encountered any unexpected behaviors.
this is, when it works (on my bluetooth headphones):
08-24 21:11:37.000 12481 12481 D AudioPlayerFragment: currentPosition 00:00:43
08-24 21:11:37.002 12481 12481 D EpisodeItemViewHolder: currentPosition 00:00:43
08-24 21:11:37.292 12481 2483 D CCodecBufferChannel: [c2.android.mp3.decoder#502] input EOS
08-24 21:11:37.457 12481 2481 D AudioTrack: stop(811): 0xb400007a903d9390, prior state:STATE_ACTIVE
08-24 21:11:37.457 12481 2481 D AudioTrackShared: this(0xb400007a9fc967b0), mCblk(0x79468e3000), front(1962508), mIsOut 1, interrupt() FUTEX_WAKE
08-24 21:11:37.458 12481 2481 D AudioTrack: stop(811): 0xb400007a903d9390 stop done
08-24 21:11:37.999 12481 12481 D AudioPlayerFragment: currentPosition 00:00:44
08-24 21:11:38.001 12481 12481 D EpisodeItemViewHolder: currentPosition 00:00:44
08-24 21:11:38.488 12481 829 D DBReader: getNextInQueue() called with: itemId = [21499]
08-24 21:11:38.491 12481 12481 D ExternalPlayerFragment: Loading media info
08-24 21:11:38.491 12481 12481 D ItemDescriptionFragment: load()
08-24 21:11:38.491 12481 12481 D QueueFragment: loadItems()
08-24 21:11:38.494 12481 829 D DBReader: Extracting Feedlist
08-24 21:11:38.501 12481 12529 D DBReader: Extracting Feedlist
08-24 21:11:38.507 12481 12522 D DBReader: Extracting Feedlist
08-24 21:11:38.511 12481 12510 D DBReader: Extracting Feedlist
08-24 21:11:38.512 12481 12481 D AudioPlayerFragment: currentPosition 00:00:45
this is the logfile, when it fails (it always looks +/- like this):
08-24 11:22:28.386 12481 12481 D AudioPlayerFragment: currentPosition 00:00:43
08-24 11:22:29.226 12481 12737 D CCodecBufferChannel: [c2.android.mp3.decoder#161] input EOS
08-24 11:22:29.371 12481 12731 I MediaCodec: (0xb4000079dfd4df30) flush
08-24 11:22:29.371 12481 12737 D MediaCodec: [0xb4000079dfd4df30] setState: 7
08-24 11:22:29.372 12481 12737 D MediaCodec: [0xb4000079dfd4df30] setState: 8
08-24 11:22:29.373 12481 12731 I MediaCodec: (0xb4000079dfd4df30) start
08-24 11:22:29.373 12481 12731 D MediaCodec: keep callback message for reclaim
08-24 11:22:29.373 12481 12737 D MediaCodec: [0xb4000079dfd4df30] setState: 6
08-24 11:22:29.374 12481 12737 I CCodecConfig: query failed after returning 8 values (BAD_INDEX)
08-24 11:22:29.374 12481 12737 W Codec2Client: query -- param skipped: index = 1342179345.
08-24 11:22:29.375 12481 12737 W Codec2Client: query -- param skipped: index = 2415921170.
08-24 11:22:29.386 12481 12481 D AudioPlayerFragment: currentPosition 00:00:44
08-24 11:22:30.386 12481 12481 D AudioPlayerFragment: currentPosition 00:00:00
08-24 11:22:31.387 12481 12481 D AudioPlayerFragment: currentPosition 00:00:01
so for some reason, when it fails, the current media is never stopped and so the next one is never loaded (my understanding, maybe i’m completely wrong).
If it helps in my 2016 VW connected by Bluetooth (not Android Auto) I have seen this and noticed that the repeat current track icon is enabled. I never enable this and have to disable it. So, it looks like AntennaPod is somehow enabling this option.
Huh. This looks like AntennaPod does not get any kind of notification/callback on finishing and the media player library (media3 ExoPlayer) just silently replays from the beginning. There should be a gazillion log lines between those two lines normally