Antennapod: Play button stops working, works again after forced stop of app

[hzulla]

App version: 1.7.3b from Google Play

Android version: 9

Device model: Nokia 7.2

Expected behaviour: Play button should work

Current behaviour: Sometimes, after I paused using AntennaPod for a few hours and then want to resume listening, the Play button does not respond. I see the UI feedback that the system noticed the tap, but playback doesn't start and the play symbol doesn't change to a pause symbol. To solve this, I have to force-stop the app and restart it, after which the play button works again and resumes the episode at the saved position, as expected.

First occurred: Don't know. At least two weeks ago.

Steps to reproduce: No idea. It happens after I stopped listening to an episode (by pressing pause) and then want to continue listening a long time later. It doesn't occur if I want to resume just a few minutes later. Something seems to cause this while the app idles.

Environment: Based on where I want to listen, I'm using Bluetooth headphones, a Bluetooth car stereo or the phone's speaker and cannot tell if a particular switch from or to Bluetooth causes this.

[ByteHamster]

Seems to be the same as #3574. If you have time, it would be great if you could enable beta testing on Google Play and try if this is fixed in version 1.8.0-RC3. We updated the media player library in the new beta.

[hzulla]

Nope, still happening with the beta.

No crash report recorded
[ Environment ]
Android version: 9
OS version: 4.4.153-perf+
AntennaPod version: 1.8.0-RC3
Model: Nokia 7.2
Device: DDV_sprout
Product: Daredevil_00EEA
Time: 2019-12-20 23:01:58

[hzulla]

Force-stop once again resolved this.

[hzulla]

And once again. So I can confirm: The current beta doesn't resolve this, sorry.

[hzulla]

I have no idea when this started to happen. Been using AntennaPod with no such problem since years (thanks!), but some weeks ago this problem occured.

[ByteHamster]

Do you use ExoPlayer in Settings/Playback/Media Player? It's usually the best one but maybe others are better on your device.

[hzulla]

Thanks, I'll see what happens if I change that setting.

[hzulla]

Sorry to report that it just happened again, using the setting "Android's built-in player".

No crash report recorded
[ Environment ]
Android version: 9
OS version: 4.4.153-perf+
AntennaPod version: 1.8.0-RC3
Model: Nokia 7.2
Device: DDV_sprout
Product: Daredevil_00EEA
Time: 2019-12-23 23:05:53

Force-stop and restart of the app resolved it once again.

[onny]

I have the same issue, using the latest AntennaPod version from F-Droid

[hotlittlewhitedog]

@hzulla I had the same problem several times, due to network disconnections.

[hzulla]

It's seems unlikely that network problems are the cause. However, I'll be glad to help debugging this issue.

[hzulla]

Every night, I switch my phone to "do not disturb". Possibly that's doing something funky to the AntennaPod service? In the morning, there is a permanent notification telling me "AntennaPod service is running". That notification usually should contain the player controls, but here it only shows that status message.

[ByteHamster]

This is a different thing. Please create a new issue for that.

[hzulla]

Is it? I had assumed that something crashes/freezes the service overnight, which might be the reason why a force-stop is necessary in the morning? I mentioned the service notification issue as it might be a symptom to explain this issue here.

[onny]

One workaround for me, instead of killing and restarting the app, is to start an other stream of an other episode or podcast and then go back to the former episode and stream that again. After that, streaming continues correctly.

[hzulla]

Thanks, @onny, I never tried that before but can confirm that your workaround works for me, as well.

So something seems to go haywire while the player is paused for a long time, but changing episodes resets it.

[tywunon]

Same here, I first encountered this after the update to Android 10, but cannot confirm that it is causing it.

[hzulla]

My phone is on Android 9, so that's not it.

[BenjaminHae]

Same here, play in the current podcast does not work. After changing the episode, playing, stopping and going back to the desired episode makes it work again.

[godkarmachine]

I have been seeing a similar issue on my OnePlus 6. After leaving a podcast paused for some time, the playback controls notification is replaced by a "Service is running" notification and I am unable to resume playing even if I go to the app and tap play. Force stopping the app and restarting restores normal behavior. Issue was present on Android 9 and is still present on Android 10.

[onp]

Seeing very similar issue to @hzulla.
After being paused for a long time(usually hours), the play button in the app does not work. When this happens, there's a persistent "antennapod service is running" notification that does not have any playback controls. Hard reset of the app fixes it, as does starting a different podcast.

Device: OnePlus 6
Android version: 10
Using exoplayer for playback

[ByteHamster]

Maybe related: #2716

If that notification is shown, it means that we get an intent (disconnected bluetooth etc) and somehow can not handle it. Then the service gets stuck in a strange state (where it is started but playback is not initialized). In order to find out what is causing this, we need logs of the time the notification is shown (what might be a bit difficult because it happens after a long time). If someone who is affected could try to capture a logcat output, this would help a lot.

[onp]

logcat output below, uncertain if this is enough to be useful? Inexperienced logcat user here, let me know if there's a more useful query to be running. I plugged in the phone and ran this shortly after I noticed "that notification" showing and the playback button issue occurring. I had paused the podcast in questions less than 2 hours before.

logcat output.txt

[ByteHamster]

Hi @onp, thanks a lot for the logs!

Unfortunately, we need more than just the error and warning levels because the reason for starting the service is logged as debug level (remove *:W). The stack traces in the log you uploaded are normal. That sometimes happens and is only related to loading the episode icon (does not crash or anything). Also, not all interesting log entries contain the word antennapod. If you want to filter for this specific issue, filtering for PlaybackService would be better. It would be cool if you could execute the following after the problem appears again:

adb logcat -e (PlaybackService)

By the way, what version of AntennaPod are you using? Do you use the version from Google Play or from F-Droid?

[onp]

More logs!
Happened again this evening, filtered log (shown below, filtered on PlaybackService as requested) doesn't show much so I've attached an unfiltered logcat dump.

--------- beginning of crash
--------- beginning of system
02-14 18:09:02.702  1101  1385 W ActivityManager: Stopping service due to app idle: u0a112 -19m50s223ms de.danoeh.antennapod/.core.service.playback.PlaybackService
--------- beginning of main
02-14 18:12:08.902  9357  9479 W BrowsedMediaPlayer_ext: package = de.danoeh.antennapod svc class de.danoeh.antennapod.core.service.playback.PlaybackService
02-14 18:12:11.507  9357  9479 W BrowsedMediaPlayer_ext: package = de.danoeh.antennapod svc class de.danoeh.antennapod.core.service.playback.PlaybackService
02-14 18:19:25.758 29933 29933 D PlaybackController: PlaybackService is running, trying to connect without start command.

Story of my evening:
17:49 Plugged in audio cable for the drive home and playback resumed automatically as it should.
18:08 Pulled the audio cable out to stop playback as I got out of the car.
Went inside, updated a few apps through Google Play.
Looked at the phone again and noticed "that notification". Went into Antennapod and confirmed that the "Play" button was not working.
18:19 Hooked up to the computer and dumped this logcat file.

logcat.txt

File is trimmed from 17:30 to shortly after I hooked up to the computer.

I'm using version 1.8.1 (6e6a64f50), from Google Play.

Let me know if there's anything else I can do to help troubleshoot this! Seems to recur fairly frequently for me, but I haven't yet figured out exactly how to reproduce it.

*edits for typos / clarification

[ByteHamster]

filtered log (shown below, filtered on PlaybackService as requested) doesn't show much

That's pretty strange. On my phone, I get tons of log messages from AntennaPod (below is when pulling out the headphone jack, just for comparison). I have no idea why your log is so empty... Sorry, I can not find anything that would help to resolve the notification issue.

02-16 18:40:05.959 21380 21380 D PlaybackService: Pausing playback because audio is becoming noisy
02-16 18:40:05.959 21380 21380 D LclPlaybackSvcMPlayer: Pausing playback.
02-16 18:40:05.960 21380 21380 D PlaybackSvcMediaPlayer: LocalPSMP: Setting player status to PAUSED
02-16 18:40:05.960 21380 21380 D PlaybackServiceTaskMgr: Cancelled PositionSaver
02-16 18:40:05.960 21380 21380 D PlaybackService: Saving current position to 9576489
02-16 18:40:05.961 21380 21380 D PlaybackServiceTaskMgr: Cancelled WidgetUpdater
02-16 18:40:05.965 21380 21380 D PlaybackService: setupNotification
02-16 18:40:05.965 21380 21380 D PlaybackService: setupNotification: startForegroundPAUSED
02-16 18:40:06.014 21380 21380 D PlaybackController: Received statusUpdate Intent.
02-16 18:40:06.015 21380 21380 D PlaybackController: status: PAUSED

Plugged in audio cable for the drive home

You mean the headphone jack, right? Not something Android Auto related?

[hzulla]

Just curious, I'm using a Bluetooth headphone and wonder if the others reporting this issue do so, too.

[onp]

Yes, refering to the 3.5mm headphone jack. You can see a bunch of activity from WiredDeviceManager at 18:08 when that happens, and almost simultaneously the Bluetooth disconnecting from the car - phone connects via Bluetooth for call audio only, not for media playback. Nothing from playbackservice seems to show up.

I also use Bluetooth headphones, but I don't think I ever turned them on on the day I dumped that log.

[lanigb]

I have the same issue, since around november I think. I have reinstalled Antennapod many times, tried to subscribe to less channel and the like, but no success.
The only work around I have found is to download first all the podcasts I want to listen to and then all downloaded podcast play one after another which makes me think that the bug comes from the fact that Antennapod doesn't understand when a stream is finished.

[ByteHamster]

A friend of mine just experienced something that might be related. The play button did not work. When pressing play, the service always just started for a few seconds and then stopped (no persistent notification) but the behavior seems to be quite similar. Logs below.

Interesting logs just before behavior started:

02-29 16:34:47.448 23919 23919 D PlaybackService: Service created.
02-29 16:34:47.449   797 11811 D AudioPolicyService: setRecordSilenced() uid 10107 on silenced 0
02-29 16:34:47.449   797 11811 D AudioPolicyService: setRecordSilenced() uid 99291 on silenced 0
02-29 16:34:47.465 23919 22465 D DBReader: getQueue() called
02-29 16:34:47.465 23919 22465 D DBReader: getQueue()
02-29 16:34:47.467 23985 24057 I chatty  : uid=1002(bluetooth) BluetoothAvrcpH expire 247 lines
02-29 16:34:47.475 23919 22465 D DBReader: getFavoriteIDList() called
02-29 16:34:47.478 23919 22465 D DBReader: getQueueIDList() called
02-29 16:34:47.480 23919 22465 D DBReader: Extracting Feedlist
02-29 16:34:47.489 23919 23919 D ccl_BaseCastManager: [v2.9.1] Successfully added the new BaseCastConsumer listener de.danoeh.antennapod.core.service.playback.PlaybackServiceFlavorHelper$1@7f9ea1f
02-29 16:34:47.489 23919 23919 D CastManager: Successfully added the new CastConsumer listener de.danoeh.antennapod.core.service.playback.PlaybackServiceFlavorHelper$1@7f9ea1f
02-29 16:34:47.490 23919 23919 D PlaybackService: OnStartCommand called
02-29 16:34:47.495 23919 23919 D PlaybackService: Received media button event
02-29 16:34:47.495 23919 23919 D PlaybackService: Handling keycode: 126
02-29 16:34:47.499 23919 23919 D DBReader: getFeedItem() called with: itemId = [16710]
02-29 16:34:47.499 23919 23919 D DBReader: Loading feeditem with id 16710
02-29 16:34:47.500 23919 23919 D DBReader: getFavoriteIDList() called
02-29 16:34:47.500 23919 23919 D DBReader: getQueueIDList() called
02-29 16:34:47.501 23919 23919 D DBReader: Extracting Feedlist
02-29 16:34:47.506 23919 23919 D LclPlaybackSvcMPlayer: playMediaObject(...)
02-29 16:34:47.507 23919 23919 I ExoPlayerImpl: Init db8516c [ExoPlayerLib/2.10.8] [OnePlus5, ONEPLUS A5000, OnePlus, 28]
02-29 16:34:47.508 23985 24060 I chatty  : uid=1002(bluetooth) uipc-main expire 65 lines
02-29 16:34:47.508 23919 23919 D PlaybackSvcMediaPlayer: LocalPSMP: Setting player status to INITIALIZING
02-29 16:34:47.515 23919 23919 D PlaybackService: reloadUI callback reached
02-29 16:34:47.516 23919 23919 D LclPlaybackSvcMPlayer: Playback speed was set to 1.0
02-29 16:34:47.517 23919 23919 W System.err: java.io.IOException: Unable to read local file null
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.LocalPSMP.playMediaObject(SourceFile:252)
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.LocalPSMP.lambda$playMediaObject$1$LocalPSMP(SourceFile:187)
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.-$$Lambda$LocalPSMP$5kNdyipM_M6Bo3d8le_FUz75a90.run(Unknown Source:10)
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.LocalPSMP$PlayerExecutor.submit(SourceFile:79)
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.LocalPSMP.playMediaObject(SourceFile:184)
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.PlaybackService.startPlayingFromPreferences(SourceFile:639)
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.PlaybackService.handleKeycode(SourceFile:582)
02-29 16:34:47.517 23919 23919 W System.err:    at de.danoeh.antennapod.core.service.playback.PlaybackService.onStartCommand(SourceFile:468)
02-29 16:34:47.517 23919 23919 W System.err:    at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3812)
02-29 16:34:47.517 23919 23919 W System.err:    at android.app.ActivityThread.access$1800(ActivityThread.java:207)
02-29 16:34:47.517 23919 23919 W System.err:    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1789)
02-29 16:34:47.517 23919 23919 W System.err:    at android.os.Handler.dispatchMessage(Handler.java:106)
02-29 16:34:47.517 23919 23919 W System.err:    at android.os.Looper.loop(Looper.java:193)
02-29 16:34:47.517 23919 23919 W System.err:    at android.app.ActivityThread.main(ActivityThread.java:6898)
02-29 16:34:47.517 23919 23919 W System.err:    at java.lang.reflect.Method.invoke(Native Method)
02-29 16:34:47.517 23919 23919 W System.err:    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
02-29 16:34:47.517 23919 23919 W System.err:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
02-29 16:34:47.517 23919 23919 D PlaybackSvcMediaPlayer: LocalPSMP: Setting player status to ERROR
02-29 16:34:47.521 23919 22399 D DBReader: getFeed() called with: feedId = [118]
02-29 16:34:47.522 23919 22399 D DBReader: getFeedItemList() called with: feed = [de.danoeh.antennapod.core.feed.Feed@76]
02-29 16:34:47.523 23919 22399 D DBReader: getFavoriteIDList() called
02-29 16:34:47.524 23919 22399 D DBReader: getQueueIDList() called
02-29 16:34:47.524 23919 22399 D DBReader: Extracting Feedlist
02-29 16:34:47.529 19177 19177 D NotificationListener: onNotificationRemoved# hash: 138322705 sbn: StatusBarNotification(pkg=de.danoeh.antennapod user=UserHandle{0} id=1 tag=null key=0|de.danoeh.antennapod|1|null|10107: Notification(channel=playing pri=0 contentView=null vibrate=null sound=null defaults=0x0 flags=0x8 color=0x00000000 category=transport actions=3 vis=PUBLIC))
02-29 16:34:47.531  2429  2429 D StatusBar: updateMediaMetaData: hasArtwork = true, mState:1, false, mDozing:false, delay:0, true, vis:0, alpha:1.0, false, meta:false, fading:false, 0, false
02-29 16:34:47.547 23919 23919 D PlaybackService: Service is about to be destroyed

Opened player screen:

02-29 16:34:51.682 23919 23919 D MediaplayerActivity: loadMediaInfo()
02-29 16:34:51.682 23919 23919 D MediaplayerActivity: currentPosition 00:00:00
02-29 16:34:51.682 23919 23919 W MediaplayerActivity: Could not react to position observer update because of invalid time
02-29 16:34:51.682 23919 22399 D DBReader: getNavDrawerData() called with: 
02-29 16:34:51.684 23919 23919 D ccl_BaseCastManager: [v2.9.1] UI is visible
02-29 16:34:51.684 23919 23919 D MediaplayerActivity: onResume()
02-29 16:34:51.684 23919 23919 D UserPreferences: Using default data folder
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment: java.lang.IllegalArgumentException: shownotesProvider = null
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at de.danoeh.antennapod.core.util.playback.Timeline.<init>(SourceFile:75)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at de.danoeh.antennapod.fragment.ItemDescriptionFragment.loadData(SourceFile:229)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at de.danoeh.antennapod.fragment.-$$Lambda$YbvEqgVyJY83-H_qazfdVNP26gs.call(Unknown Source:2)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at io.reactivex.internal.operators.observable.ObservableFromCallable.subscribeActual(SourceFile:43)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at io.reactivex.Observable.subscribe(SourceFile:12090)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at io.reactivex.internal.operators.observable.ObservableSubscribeOn$SubscribeTask.run(SourceFile:96)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at io.reactivex.Scheduler$DisposeTask.run(SourceFile:578)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at io.reactivex.internal.schedulers.ScheduledRunnable.run(SourceFile:66)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at io.reactivex.internal.schedulers.ScheduledRunnable.call(SourceFile:57)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
02-29 16:34:51.708 23919 23919 E ItemDescriptionFragment:   at java.lang.Thread.run(Thread.java:764)

Every time he pressed the in-app play button:

02-29 16:35:32.243 23919 23919 D PlaybackService: Service created.
02-29 16:35:32.264 23919 22558 D DBReader: getQueue() called
02-29 16:35:32.264 23919 22558 D DBReader: getQueue()
02-29 16:35:32.267 23985 24057 I chatty  : uid=1002(bluetooth) BluetoothAvrcpH expire 223 lines
02-29 16:35:32.276 23919 22558 D DBReader: getFavoriteIDList() called
02-29 16:35:32.277 23919 22558 D DBReader: getQueueIDList() called
02-29 16:35:32.278 23919 22558 D DBReader: Extracting Feedlist
02-29 16:35:32.287 23919 23919 D ccl_BaseCastManager: [v2.9.1] Successfully added the new BaseCastConsumer listener de.danoeh.antennapod.core.service.playback.PlaybackServiceFlavorHelper$1@1f796e4
02-29 16:35:32.287 23919 23919 D CastManager: Successfully added the new CastConsumer listener de.danoeh.antennapod.core.service.playback.PlaybackServiceFlavorHelper$1@1f796e4
02-29 16:35:32.288 23919 23919 D PlaybackService: OnStartCommand called
02-29 16:35:32.289 23919 23919 E PlaybackService: PlaybackService was started with no arguments
02-29 16:35:32.294 23919 23919 D PlaybackService: Service is about to be destroyed

Looks like AntennaPod tried to play a local file even though it should stream. That then failed and caused some unexpected behavior. I fixed resuming a streamed episode in #3881. The lines I touched are also present in the stack trace above, so this issue might be fixed by #3881, as well.

Most of you who are affected are streaming, right?

[BenjaminHae]

Most of you who are affected are streaming, right?

I'm not streaming.

[bacam]

I'm having this problem reliably with a Nokia 8 running Android 9 when connecting to a computer running Ubuntu 18.04. It doesn't happen with a Nexus 5 running 6.0.1, or if I use my Sony Bluetooth headphones.

The way I reproduce it is to

1. Open AntennaPod and start playback (on the phone's speaker)
2. Pause playback, dismiss the playback notification
3. Remove AntennaPod from the task list
4. Connect Bluetooth (on the computer)

Then the "Service is running" notification appears and if I open AntennaPod again I can't resume playback from the main play/pause button. Note that I can resume playback from the play buttons next to the episode on the feed view, which might be useful for anyone suffering from this problem.

I've got Android Studio set up so I can do a bit of debugging, although I'm not very familiar with Android development. So far I've found that

• The "Service is running" notification comes from PlaybackServiceNotificationBuilder.build when playable is null. I still don't know why this is run at all.
• The main play/pause button doesn't work because PlaybackController.playPause doesn't expect the status to be STOPPED.

[ByteHamster]

Hi @bacam, It would help a lot if you could capture logs:

• Connect phone
• Open the logcat window in Android Studio
• Disable filtering
• Clear logs with trash can icon
• Reproduce the issue like you did in your post above
• Copy the logcat messages

I would be very interested in getting access to the logs. If you do not want to post them, you can also email me at info@<my username>.com

[bacam]

@ByteHamster The full log is a bit much to eyeball for sensitive information, so here's everything that matches playback or antennapod from starting the app (I force killed it beforehand) until the notification appears.

One line that stands out to me is where Android starts the service after bluetooth connects:

03-01 20:23:27.835  1414  1445 D ActivityManager: handleProcessStartedLocked mDoneFinishBooting && app.pid != 0 ---> notifyProcessStart, app.processName = de.danoeh.antennapod.debug, app.info = ApplicationInfo{3cb2d13 de.danoeh.antennapod.debug}, app.hostingType = service, getHostingName() = ComponentInfo{de.danoeh.antennapod.debug/de.danoeh.antennapod.core.service.playback.PlaybackService}, getIntentFlag() = 0, getIsPackageRunning() = false, app = ProcessRecord{b262697 31533:de.danoeh.antennapod.debug/u0a23}, getExtraData() = Bundle[{SERVICE_INTENT=Intent { act=android.media.browse.MediaBrowserService cmp=de.danoeh.antennapod.debug/de.danoeh.antennapod.core.service.playback.PlaybackService }, CALLER_PACKAGE=com.android.bluetooth}]

Perhaps AntennaPod isn't doing some part of the MediaBrowser management properly?

202003-antennapod-log-filtered.txt

[ByteHamster]

Thanks for the logs!

03-01 20:23:14.470 31327 31327 D PlaybackService: Service created.
...
03-01 20:23:14.513 31327 31327 D PlaybackService: OnStartCommand called
...
03-01 20:23:15.878 31327 31327 D PlaybackService: Received PAUSE_PLAY_CURRENT_EPISODE intent
03-01 20:23:15.878 31327 31327 D LclPlaybackSvcMPlayer: Pausing playback.
03-01 20:23:15.878 31327 31327 D PlaybackSvcMediaPlayer: LocalPSMP: Setting player status to PAUSED
03-01 20:23:15.878 31327 31327 D PlaybackServiceTaskMgr: Cancelled PositionSaver
03-01 20:23:15.879 31327 31327 D PlaybackService: Saving current position to 17143
03-01 20:23:15.879 31327 31327 D PlaybackServiceTaskMgr: Cancelled WidgetUpdater
03-01 20:23:15.880 31327 31327 D PlaybackService: setupNotification
03-01 20:23:15.881 31327 31327 D PlaybackService: setupNotification: startForegroundPAUSED
...
03-01 20:23:20.956  1414  4216 I ActivityManager: Killing 31327:de.danoeh.antennapod.debug/u0a23 (adj 1001): remove task
03-01 20:23:20.989 21308 21308 V Avrcp_ext: Player 11 package: de.danoeh.antennapod.debug
03-01 20:23:20.989  1414  4624 W ActivityManager: Scheduling restart of crashed service de.danoeh.antennapod.debug/de.danoeh.antennapod.core.service.playback.PlaybackService in 1000ms
...
03-01 20:23:27.822 21308 21359 D Avrcp_ext: getBrowseServiceName for packageName: de.danoeh.antennapod.debug, browseServiceName = de.danoeh.antennapod.core.service.playback.PlaybackService
03-01 20:23:27.822 21308 21359 D BrowsedMediaPlayer: setBrowse for packageName = de.danoeh.antennapod.debug
03-01 20:23:27.822 21308 21359 D Avrcp_ext: startBrowseService for packageName: de.danoeh.antennapod.debug, status = true
03-01 20:23:27.835  1414  1445 I ActivityManager: Start proc 31533:de.danoeh.antennapod.debug/u0a23 for service de.danoeh.antennapod.debug/de.danoeh.antennapod.core.service.playback.PlaybackService
03-01 20:23:27.835  1414  1445 D ActivityManager: handleProcessStartedLocked mDoneFinishBooting && app.pid != 0 ---> notifyProcessStart, app.processName = de.danoeh.antennapod.debug, app.info = ApplicationInfo{3cb2d13 de.danoeh.antennapod.debug}, app.hostingType = service, getHostingName() = ComponentInfo{de.danoeh.antennapod.debug/de.danoeh.antennapod.core.service.playback.PlaybackService}, getIntentFlag() = 0, getIsPackageRunning() = false, app = ProcessRecord{b262697 31533:de.danoeh.antennapod.debug/u0a23}, getExtraData() = Bundle[{SERVICE_INTENT=Intent { act=android.media.browse.MediaBrowserService cmp=de.danoeh.antennapod.debug/de.danoeh.antennapod.core.service.playback.PlaybackService }, CALLER_PACKAGE=com.android.bluetooth}]
03-01 20:23:28.495  1414  4684 V ActivityManager: publishContentProviders ProcessRecord uid = 10023 processName=de.danoeh.antennapod.debug
03-01 20:23:28.569 31533 31533 D PlaybackService: Service created.
...
03-01 20:23:28.643 31533 31533 D PlaybackService: OnGetRoot: clientPackageName=com.android.bluetooth; clientUid=1002 ; rootHints=null
03-01 20:23:28.645 31533 31533 D PlaybackService: OnLoadChildren: parentMediaId=AntennaPod Debug

The second time the service is started, there is no line with OnStartCommand called. That explains the notification. AntennaPod assumes that after a call to onCreate, it will afterwards get a call to OnStartCommand.

Android docs:

https://developer.android.com/reference/android/app/Service
Clients can also use Context.bindService() to obtain a persistent connection to a service. This likewise creates the service if it is not already running (calling onCreate() while doing so), but does not call onStartCommand()

So apparently, the Bluetooth connection starts the service in a way we do not expect.

[jmichael2497]

so maybe two related issues involved, because i don't use bluetooth (except for very rare device pairing file transfers) since wired headphones just work.

noticed the issue of non-productive play/pause button after lengthy pause to do other things while running LOS 8 O and LOS 9 P all while i've been using store beta for maybe a year (i forget, sorry).

i use battery saver mode which could be related due to limiting background threads.

i've seen behavior of sometimes the lock or playback notification will disappear after i hit play to resume (usually streaming at home, pre-download for while i'm out and about, edit: i think maybe it can happen in either situation, but didn't in a recent test of a downloaded episode paused for an hour).

otherwise typically i just have to back out of the playback screen with the non-productive play button and go back into the same episode, seems to refresh the status, and i'm able to tap the stream word again at the top, rather than then bottom bar queue play button to resume.

honestly this is the one bug that makes me hesitant to recommend the app to people who want something that "just works"... but i still do anyway, because other than that, this has most all the popular features that seem useful.

cheers.

[cryobry]

Just ran into this bug. Force stop fixed it for me. I'm listening to local media via bluetooth headphones and paused my podcast over night.

OP6T, Android 10

[71walceli]

It also happens to me just as described by @jmichael2497 in as little as three minutes being paused in my case. The thing is, when I pause for some time, I started to go into the playback activity, which has all media controls. There, when I resume playback, it does work, and seems to act as intended.

I'm on Android 8.1. I did that many times. For some reason, the activity actually starts playback normally, even for long periods or time. For that workaround to work, DO NOT touch any control in the notification, it would break functionality as described. Just get into the podcast playback activity and touch the play control.

Let me know if it works for you. I'll try to submit a log.

[dcjkfgdjhd]

I have the same issue.

In my case, it helps to manually select the episode from the playlist, and then in the full screen episode view use the Play button (next to the delete button) there.

Clearly a bug.

[dcjkfgdjhd]

New info: This problem seems to be associated with the weird "AntennaPod - Service is running" notification. The problem seems to occur only when that weird and useless notification is displayed.

When you force playback to continue (through the episode view screen as described above), the notification goes away as well.

[keunes]

Anyone still experiences this in 2.1.1?

[lanigb]

Recently, I noticed that Antennapod icon had changed, so I thought that it has been updated and gave it another try. I didn't encounter any of the problems I had reported here but in "About..." I still have 2.0.3 as current version. Google play tells me that I am on a beta program, so I am quite unsure about the version I am running.

[keunes]

@lanigb The icon changed with version 2 , I believe the beta. In any case the latest version on Google play beta channel is 2.1.1. The version listed on the About page should be the correct one. So you might want to check in Google Play if there's an update that was not automatically downloaded.

[lanigb]

@keunes Thanks for your answer. As you wrote, I had not the latest version on Google Play, but the latest in F-droid.
I have updated it and will report if I encounter the same bug again. But it did disappear from the 2.0.3 version.

[bacam]

I can't reproduce this any more using the method I posted before with the current play store 2.1.1 release. Looking at the code I see some changes by @ByteHamster that look like they were intended to fix it.

[lanigb]

I second this comment. With former versions, I was encountering this bug each time I read a file. I have not encountered it during 2 weeks so it should be really gone.
Thanks for fixing it.