I'm using DoggCatcher on my HTC Hero (GSM version). I really like having the ability to use the play/pause button on the headset with DC. In the latest version, however, the behaviour of the play/pause headset button has changed somehow.
When I press the button and DC is not running, DC launches! Not ideal when I'm trying to use the headset to control my music, since I then end up with music and podcasts playing at the same time (some weird mashups, I can tell you :)).
In the previous version I used to quit DC (using Advanced Task Killer or TasKill) and I could then use the headset controls with the Hero music player.
Now, if I disable the headset binding, DC still launches if it's not running, but I am able to control my music. I would really prefer the old behaviour, though :).
It sounds like that's a bug that is also being reported here - http://snoggdoggler.com/node/457
I understand where you are coming from with the old behavior but that was actually a bug. There's some weakness in the android api when it comes to handling of headset events by different applications. I hope it's something that gets addressed shortly.
I update the mantis issue for this.
http://mantis.snoggdoggler.com/view.php?id=267
Thanks for the post.
Hah, I wasn't aware that that great feature was actually a bug, LOL :).
So what you are saying is that pressing the headset button is supposed to launch DC, when Bind headset button is enabled?
Yes, when you enable the binding in DC, then DC 'owns' the button. I haven't been able to figure out a way to provide a more relaxed way of intercepting the button presses because it's not always possible to know which app you want to respond to the button press. I supposed one preference could be to be either
-own the button
-only respond to the button if DC is running
but since the user doesn't always have control (without a task killer) over whether the app is running, plus it can start back up when the update alarm fires.