With the release of Android 5.0, Google removed support for lock screen widgets. If I want to control DoggCatcher (or any music app) I have to use the notification widget on the lock screen. DoggCatcher's widget works, but its in the expanded view and that causes the album art and control buttons to run outside the bounds of the widget. You can see the attached screenshot for reference.
DoggCatcher on Lollipop Lockscreen
Another issue is the new way users can interact with widgets on the lock screen. In Android 4.0-4.4 if you had a pin code or pattern lock enabled access to the notification shade was disabled. With 5.0 you now have the option in settings to show all notifications, hide notifications with sensitive information, or hide all notifications when the device is locked. I think by default, all notifications are marked as sensitive unless the developer says otherwise. So right now if I enable the option to hide sensitive information, the controls for DoggCatcher are not accessible from the lock screen. Google has already updated the Google Music app to work with the lock screen so this issue should be fixable.
DoggCatcher with sensitive notifications hidden
Google Music Lock Screen Notification Widget
Again, thank you for developing DoggCatcher. It has been my podcast app for over 2 years.
Agreed on both points, I created two issues for these. Thanks for the feedback.
http://mantis.doggcatcher.com/view.php?id=1988
http://mantis.doggcatcher.com/view.php?id=1987
Just logged in to report same issue, and saw this thread. So I guess this is a forum bump.
Thanks for that app, I tried pretty much all the podcast apps available when I switched to android 3-4 years ago, i choose doggcatcher as the on I liked best and have never had a reason to look into switching since.
Another issue is that the fwd button in the lockscreen skips to the next episode but on kit kat, it did the 10sec skip.
Yup, that's a bug - http://mantis.doggcatcher.com/view.php?id=1996
Thanks for reporting it.
I just got the Moto X Lollipop update and it has the same behavior.
Same experience for me on Samsung Galaxy S5 running Android 5.0