Car Bluetooth Auto Plays AntennaPod

Bug report
1

App version: 3.9.0

Android version: 15 (Please mention if you are using a custom rom!)

Device model: Google Pixel 9 Pro

Expected behaviour: When I connect to my car’s bluetooth, AntennaePod doesn’t automatically start playing the last Podcast I had playing. Which no other app or podcast app does this.

Current behaviour: AP starts playing when I switch my car radio’s source to my phone. Worse, if I start playing something else, AP will override what I was listening to, and start playing the podcast again. Thus I can rarely listen to anything other than AP.

First occurred: (e.g. about x days/weeks ago) Months, maybe years. Ever since I started using AP.

Steps to reproduce:

  1. Start car.
  2. Switch source on radio to phone.
  3. AntennaPod starts playing
  4. Stop AP’s playback
  5. Switch to different app and play audio
  6. 15-30 seconds later, AP starts playing Podcast again.
  7. Hit play on other app again, audio starts playing from app.
  8. Few seconds later AP starts playing again causing second app to stop.
  9. Currently I have to tell my phone to sleep/pause AP to stop this, which prevents AP from running.
  10. As of now, I’ve uninstalled AP. I just can’t deal with it anymore until it’s fixed.

Environment: (Settings you have changed (e.g. Auto Download). “Unusual” devices you use (e.g. Bluetooth headphones).)
2014 RAM 1500 Uconnect based factory radio. (Which has no option to disable auto playback)

Crash info:

2

Hi @HeyRadar
Thanks for chipping in! (I suppose it was you also who wrote the Google Play review (internal link for my reference) on the same topic?)

Can you go to Settings » Playback and then check the state of the setting “Headphones or Bluetooth disconnect”?

Edit: would you be willing to reinstall, check this setting and try again? (I hope you did make a back-up of the database before uninstalling to keep app your data.)

3

I have a Pixel 9 Pro as well (and even drive a 2014 car with factory infotainment system) but I’ve never seen this issue. I also haven’t seen it with previous AP versions and Pixel models, so I’d definitely recommend troubleshooting as @keunes recommends.