add headset button control
It would be really useful to configure headset buttons, for example to skip forward by double clicking and skip back by triple clicking the headset button.
This feature is available since v2.23
Only the double-click has been implemented
It works be nice to select the feature of previous/next buttons. Beyondpod allowed this. With podcasts I want to skip forward through commercials, I want previous to SKIP TO END.... Some podcasts are uninteresting or I have heard them before. Digging my phone out to skip to next podcast is annoying.
Johan Lindberg commented
I can't see why this is marked as completed - only half of the features are there. I would love to be able to skip back by triple clicking, which works fine e.g. in my phone's built-in music player. In Podcast Addict, it will skip forward and then pause, as if it interpreted it as two separate actions.
Volume is handled by the device not by the app. If your headset has volume controls then you should already be able to control the volume.
This feature request is closed, because it has already been delivered
Yes, I would love this. Also volume controls as well.
@Damian This is the default behavior
How about pause/resume control with one click?
Available in beta if you want to test it ;)
Mario G.H. commented
Hurray!, Xavier. This is a great advance in UX (user experience)
Christophe Bonnefoy commented
Morse code could be very useful here !
Next : -.
up volume ..-
-- . .-. -.-. .. .--. .- .-. .- ...- .- -. -.-. .
Mario G.H. commented
Are you talking about "skip forward" (fast forward / ffwd) or just go to the next podcast in the list?. Anyway, this is one of my gripes with podcast addict. You must be able to setup an action so every time you double or triple touch the headset button a command is triggered to fast forward the same track or just skip it and advance to the next one. Some apps even make use of long touch (hold) for volume up and down (although they do not work well in some platforms). I am about to up vote this but I get an error every time... I'll keep trying though, this is a fundamental feature and I notice your request is getting old...