I think there may be one additional thing worth noting.
While testing 3.12.0-beta4 (bdfd540c3), I was able to reproduce the detached-fragment crash (#8513) by navigating away from the queue and then tapping Undo on the snackbar.
Since the fix for #8513 is currently part of PR #8514 on develop, I wanted to mention that the detached-fragment crash also appears to affect the current beta release.
That crash is not new in 3.12.0 so I think it’s fine to not backport and release it in 3.13.0. I want to focus on getting the new playback service solid first.
Is there any way to force myself to get beta4? I have beta 3 but beta 4 isn’t available as an update for me yet. And I know it’s not your issue, it’s Google but it seems weird that I would get a previous beta but not a subsequent one. If I was randomly selected as a part of the first group then what sense does it make for me to not get subsequent updates and be stuck with issues in a previous build?
Is there any particular issue that you’re facing in beta3 which makes you want to update to beta4 @richardeid?
We totally agree. We’re not entirely sure how this works but if it’s indeed like this, that’d be stupid.
That said, beta3 is currently rolled out to 100% (of the beta users) while beta4 is rolled out to 50% (of the beta users). We usually wait 4-5 days and do a gradual roll-out to make sure the new beta doesn’t make things worse (than the previous beta). So you may be in that group of people currently in the beta3 but out of the beta4 group.
I personally think the roll-out strategy could be tweaked here but that’s maybe more something to discuss once this major release is done
The custom playback speed is an issue I’m seeing. I listen to a lot of podcasts and maybe 10 or 15 of them I listen to at 1x speed. Most of the hundred or so I’m subscribed to are at 1.5x. And a handful are at 2x speed. I’m not complaining at all about this beta. I never do about betas. They’re for testing. I know what i signed up for. But this issue is kind of a pain so I’d love to have it resolved.
Also…I cast podcasts to my speakers whenever I’m home and casting has had some weird quirks since maybe around the beta started. But I can’t say it started right when I got this beta. I don’t pay that close attention. If casting bugs out, I am used to it and I just recast and continue on my day. Since Chromecasting has always been iffy for me in nearly any app, I’m trying to hold out to see if it resolves itself since Google makes changes that I can never find changelogs anywhere for. I’m not going to point at AntennaPod just yet. But it is an issue I hope gets resolved in the next beta. I haven’t seen any other posts exactly relating to the problem I’m having so I’m not going to document it in a post just yet. There are more details but basically I’ll cast a pod to a speaker, it takes sometimes a full minute after I hear the chime on the speaker for the pod to start playing, and after some random (or not, I just haven’t collected much detail about the problem yet) time the pod will stop playing on the speaker, then continue playing on my phone, then recast itself to my speaker without any interaction from me. It’s weird and I haven’t had the time to pay enough attention to if anything more is going on.
And finally, LMAO as I’m typing this post up at 6am my time I checked for updates in Play Store and lo and behold…beta4! I’ll check in after using it for a few days. Thanks for responding.
When I pause listening to an episode and go to another, the previous episode still shows with the beginning time of where I paused. However when I go back to restart it, it reverts to the beginning. It worked OK in the past.
I have a similar problem.
Background info:
Environment: Android version: 16
OS version: 6.6.89-android15-8-g97a9aaefab9a-ab14519050-4k
AntennaPod version: 3.12.0-beta3
Model: V2511
Device: V2511
Product: V2511i
Manufacturer: vivo
I listen to most podcasts at 1.4x:
When I start a new podcast, the player still shows the old podcast for almost a minute, although it begins playing the new one.
While it does the above, the new podcast plays at 1x speed for a while.
Today, the new podcast began to play, but I could not see the player for nearly a minute because of which I could not fast-foward/>> the initial ads in the podcast.
These problems are new, never occurred before.
I usually don’t like to complain but I listen to the podcasts while working and the phone is not usually within reach, so it gets really bothersome to be forced to listen to stuff or be unable to make a quick change.
Still love the app and the people behind it! Thank you for creating AntennaPod