OS version: 6.1.145-android14-11-gfa1d6308d1fe-ab14691759
AntennaPod version: 3.12.0-beta3
Model: Pixel 9a
Device: tegu
Product: tegu
Manufacturer: Google
## Crash info
Time: 18-06-2026 09:02:17
AntennaPod version: 3.12.0-beta3
StackTrace
java.lang.OutOfMemoryError: Failed to allocate a 64 byte allocation with 1767552 free bytes and 1726KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.
at android.media.MediaCodec.getBuffer(Native Method)
at android.media.MediaCodec.getOutputBuffer(MediaCodec.java:4879)
at androidx.media3.exoplayer.mediacodec.AsynchronousMediaCodecAdapter.getOutputBuffer(SourceFile:264)
at androidx.media3.exoplayer.mediacodec.MediaCodecRenderer.drainOutputBuffer(SourceFile:2233)
at androidx.media3.exoplayer.mediacodec.MediaCodecRenderer.render(SourceFile:945)
at androidx.media3.exoplayer.RendererHolder.render(SourceFile:392)
at androidx.media3.exoplayer.ExoPlayerImplInternal.doSomeWork(SourceFile:1378)
at androidx.media3.exoplayer.ExoPlayerImplInternal.handleMessage(SourceFile:707)
at android.os.Handler.dispatchMessageImpl(Handler.java:138)
at android.os.Handler.dispatchMessage(Handler.java:125)
at android.os.Looper.loopOnce(Looper.java:269)
at android.os.Looper.loop(Looper.java:367)
at android.os.HandlerThread.run(HandlerThread.java:139)
Many new issues since recent app update for beta. Auto skip no longer works. Queue no longer works. Now playing no longer docked at the bottom of the page. I tried leaving beta but the issues didn’t resolve. I posted this on Google play & was told to post here instead.
App version: x.y.z
Android version: 5.x (Please mention if you are using a custom rom!)
Device model:
Expected behaviour:
Current behaviour:
First occurred: (e.g. about x days/weeks ago)
Steps to reproduce:
This
Then that
Then this
Etc.
Environment: (Settings you have changed (e.g. Auto Download). “Unusual” devices you use (e.g. Bluetooth headphones).)
I’ll add here that per feed playback speed settings are also not being honored. Instead, only the global default playback speed is used.
Additionally, playback control from the widget seems unresponsive most of the time.
Finally, I’ve noticed that on playback pause and resume (as a result of a notification sound from Android, etc.) has a much more noticeable “rewind” where maybe half of a second of audio is replayed on resume.
Could one of you please take a screen recording showing the non-working per-podcast speed? The per-podcast speed does work for me. So something must be different in the way you use AntennaPod. This is easiest to figure out with a recording
Minor bug, but I spotted that in inbox,
swipe left (mark as unplayed) generates a notification “%d episode marked as unplayed”
Also, I’ve been having problems with the widget controls in a nightly build from a few nights ago, but can’t reproduce it in beta-3. Let me know if you want me to dig further
I’ve been having problems with the widget controls in a nightly build from a few nights ago, but can’t reproduce it in beta-3.
Am definitely seeing it in beta-3. It seems to simply be “don’t use antennapod for a while” and the widget stops responding.
Also “Pause playback when headphones or Bluetooth devices get disconnected” is unreliable. Often audio will start playing via my phone’s external speaker after disconnection
PS: Do you want beta3 bugs reported here, or via github?
…so I poked around and see that there is lots of code related to Bluetooth and headset disconnection that was in the old PlaybackService class that is missing in Media3PlaybackService. Adding in some bodged code fixes the playing after Bluetooth disconnect problem for me, but I’ve hardly done it “properly”. Is this on someone’s to-do list?
Beta 4 is now under review by Google. It still has a couple of known issues (see GitHub · Where software is built) but it should fix most of the cases where the new playback service and the user interface got out of sync.
…but 3.12-beta 4 was built using develop? I’m just confused because I’ve been running into a bug that appears to have been fixed in develop, but not master.
Or perhaps I’ve just gone mad (which is entirely possible)
That one is only on develop, yes. It only happened on debug builds, so no need to have it on master. Debug builds deliberately crash more often to indicate non-fatal problems, they are not meant for daily use. They are also much slower/more laggy.
I don’t know if this is a common bug to some people in here.
Since version 3.12.0-beta4 (bdfd540c3) if I am listening to a long downloaded episode (beyond 4 hrs long), and give it a rest to go to a shorter downloaded one (no longer that 30 mnts ) and then I close the app / take a rest from listening; if I go back to the app, play another one and set that first long episode to automatically go next, it restarts from the zero minute. I don’t remember it has happened to me before.
The rest of the app seems to work perfectly on my Redmi 9A/Android 11.