Hi Eric-
I am running DoggCatcher v1.1.1668 on a stock Nexus One (Android 2.2.1, build FRG83). On Sunday I noticed a change in behavior linked to the "Play audio on connect" option. I have always had this option disabled, and still do, but now DC behaves 100% as if it were enabled. If I connect a set of headphones to the 3.5mm headphone jack, my podcast starts playing.
More concerning, however, is that if my phone connects to a Bluetooth stereo, it also starts playing. This happens every time I start my car now, regardless of whether I have the stereo set to Bluetooth Audio mode, or CD, or radio, etc. If it is set to Bluetooth Audio, it starts playing through the speakers and I can pause it. But if the stereo is set to CD, for example, it starts playing in my pocket, and I have to take it out, unlock it, and pause the podcast.
If it would help, I can post a video of this behavior to YouTube or something, as it is absolutely repeatable and I have triple-checked my settings. (Unless there is another setting hiding somewhere that can override the "Play audio on connect" option...)
Thanks,
Drew
yeah, he's looking into it. we already mentioned the problem on another thread. annoying as hell... i'm at work listening to my podcasts on hard-wire headphones because i have to keep BT turned off completely. that means no hands-free calling in my car too. he always gets the issue resolved though.
Thanks for the update, kelvin232. I searched before I posted but somehow didn't come up with the other thread.
thats because its ambiguously titled "a bug".
I've just tested the same scenarios on nexus one with FRG83 and I'm only seeing the audio start when the preference is enabled...strange.
Would one of you guys be able to go through the same steps and then send me a log file (in the dc menu). Just be sure the 'play audio on connect' pref is disabled (which you've probably already done, then connect a headset (either bluetooth or wired), and then send the log.
Sorry you guys are going through this, I'll try to get it resolved as quickly as possible.
I've tried this on a variety of devices with a variety of headsets (wired and bluetooth) and I can't make it mis-behave.
I'm gonna need some more info. Could you also do a backup of our config and send it to me, there are some steps here to do this - http://www.doggcatcher.com/node/1039
Thanks
Eric: It's not broken anymore! That's really bizarre...a clock-dependent issue? I have no idea, but if it happens again then I'll be sure to document it for you with the log, etc. Thanks for your attention.
I'm not sure exactly how it started working because after lots of trying, I couldn't cause the error to occur.
Please do send a log if it happens again.
Thanks.
Same thing here: behavior stopped.... no problems for 2 days.
I know it's been a while, but do you think that maybe you started the app with the widget after you installed the last version. I can see how maybe the preference that enables/disables the play on connect may not have been initialized correctly in that case. But I would think that setting the preference to disabled after that would resolve it.
Thanks for posting that it got resolved.
So when a user upgraded DC, the play audio on headset connect was defaulting to true, until you enter the preferences screen (even if you don't change anything). It wasn't an issue for clean installs.
Anyone experiencing this should be able to resolve it by entering the preferences screen and then exiting the preferences screen.
I'll have a fix in the next release - http://mantis.snoggdoggler.com/view.php?id=694