DETAILS:
DoggCatcher Version: 1.2.4139
Device: Samsung Galaxy S7
Android Build: 6.01 MMB29M.G930PVPU1APB5
Carrier: Sprint
Bluetooth Device: LG HBS-750
SUMMARY: Next and Previous buttons on Bluetooth headset have no effect in Doggcatcher
STEPS TO REPRODUCE:
1. Start DC
2. Start a podcast
3. Press (or long press) next or previous button on bluetooth headset.
WHAT HAPPENS: Nothing.
WHAT SHOULD HAPPEN: With current configuration, next should fast forward and previous should rewind.
FREQUENCY: 100%
SEVERITY: Serious
ADDITIONAL INFORMATION: This headset worked perfectly with Doggcatcher on another phone. I will do additional testing with other Bluetooth devices. I tested the headset with Amazon Music on the Galaxy S7, and it worked as expected, so the S7 is receiving the button presses, it's just not making it to Doggcatcher.
Also, it's only next/previous. Play/Pause works fine. I can press the play/pause button on the headset, and Doggcatcher responds as expected.
EDIT: Pebble Smart Watch exhibits the same behavior. Play/Pause works, next/previous does not. I'm assuming this isn't going to be an issue with the Bluetooth devices themselves, but with DoggCatcher's interaction with the S7's Bluetooth system.
Thanks,
Henry Adams
Press the next/previous buttons again and right after that send a log (DC Menu>More>Report Problem) and we'll check it out
Thanks
I sent the log. Thanks.
I have the same issue with my G7 Edge. My previous phone worked fine with the bluetooth controls (in my car). Play/pause seems to work all the time but previous/next rarely work and sometimes detect a long press instead of short press when they do work. I also noticed when watching the Event Log in Doggcatcher that play/pause would show up fine, but when I would press previous/next and it was one of the common cases where the button didn't do anything, it woudn't show in the Event Log (probably expected since it isn't being responded to). But what was really interesting was after this occurred, I could still play/pause but the button event would no longer show in the Event Log until I pressed a button in the app itself.
I meant S7 Edge.....
Thanks for posting. Can you also send a log, press the next/previous buttons again and right after send a log (DC Menu>More>Report Problem)
I'm having the exact same issue reported in this thread, but it did not start happening until I upgraded to Marshmallow (6.0.1) from Lollipop (5.1.1) on my Galaxy S6. I'm wondering if it's a version specific issue. Perhaps something changed with how android handles bluetooth media button presses in Marshmallow?
I'm pretty sure this is a bug in the samsung marshmallow rom. I've gotten logs from a few people and I can see what's happening. We are supposed to get two events when you press a button, one when the button goes down, and another when it goes up. They should always come in pairs. Sometimes, the up is missing.
This explains why DC is affected by this and other apps may not. DC responds to the UP, not the DOWN. I'm guessing the other apps respond to the DOWN.
I'll mess around a little bit and see if I can switch to responding to the down press.
For anyone that hasn't sent me a log, could you please do a 'send report' in the DC navigation drawer. I'd like to make sure the same thing is happening for everyone, even though I'm pretty sure it is. Also, please include your forum username so I can match the logs up to people here.
Thanks.
So I was trying to test out the long press (after not working on the part of the app for a very long time) with a wired headset with next/prev buttons but android is intercepting those to change the volume. I tested all the way back to an android 4.0.4 device with the same result. I'm positive that the wired headsets used to not control volume but send the next/prev events to DC.
Does anyone have a wired headset/android device that lets you press on prev/next buttons that do NOT control volume?
My LG headset has separate buttons for volume and prev/next. Do you want a log with some prev/next long presses?
Actually I want that headset :-)
Is there a model/part number on it?
Do those buttons change the volume or do they rew/ff? I've got a very old htc headset with ff/rew buttons but those are changing the volume on all my devices.
It's LG HBS-750 bluetooth headset. Volume buttons are on the left side and prev/next are on the right. Long pressing prev/next does ff/rw.
That's a bt headset, I wasn't aware of any that supported long presses....which apps does long press with that headset work with?
I have had the same problem on my Note 5 since updating to marshmallow. Logs sent just now.
I've got a new release that I will publish to the beta testers on Friday night. It would be great if a couple of you could join the beta and test it out since I don't have a way to test this (no samsung marshmallow devices).
It's easy to join the beta, details are here - www.doggcatcher.com/beta
Thanks.
I am in the beta now. I will try to test out tonight. What version should I be looking for (on 5257 now)?
Eric will release the new beta tonight , the version number will either be 1.2.5258 or 59
See DC - Roadmap listed under DoggCatcher - 1.2.next (Scheduled For Release 2016-04-22) http://mantis.doggcatcher.com/roadmap_page.php
Issue 0002228: Headset rew/ff buttons do not work on samsung devices with Marshmallow
5258, just released it.
Just got time this morning to test. Unfortunately no change in operation for my Note 5. FFW and REW button presses have no effect on either device I am using to test.
Can you please press ff and rew a few times, then play/pause, and then 'report problem' in the navigation drawer and I'll check it out.
Thanks.
I agree that the problem still exists with 5258. I've sent a log with the prev/next as well as ff/rw (long press) followed by play/pause.
Sorry I misspoke, I am using prev/next buttons on my device.
I haven't forgotten about this. I have a suspicion that I know what is causing this and it's going to take at least a few days before I have anything ready for testing.
I submitted a bug and sent in logs a couple weeks ago for my Galaxy Note 5 that previously worked fine but then "broke" after Marshmallow . This week I had to replace my phone and after saving/restoring DC settings and installing all my apps and bluetooth and stuff again the buttons were working today!
I don't know what the trick was or if it will last but it was working. This is with the Satechi bluetooth button in the car. I haven't tried other devices (bluetooth earbuds, pebble watch) yet.
jv
I also have the same problem as the OP, so I'm looking forward to see what Eric can do.
Samsung Galaxy S7 Edge (International model. Carrier is EE (UK) )
2015 VW Tiguan with Discover MIB2 "Infotainment" stereo system.
Doggcatcher Ver 1.2.4141
Release Channel: Paid
Many thanks Eric.
--
Jake
Just published a beta release that I hope fixes this but I can't know for sure because I don't have a device to test this problem.
It would be great if someone in the beta group could let me know if this does or doesn't work.
Thanks.
I just checked the latest build, and it works! Thanks for fixing this so quickly. There's still no better podcast app in my opinion.
Works great now. Thanks!
That is great news, thanks for letting me know the fix worked.
For those not on the beta, I'll be releasing this fix to the market this coming Friday.
Thanks for everyone's patience with this.
Since the update, my phone won’t connect to my cars built in hands-free. I’ve already tried all the suggested fixes to method 6, but if Samsung thinks I’m going through the nause of a full factory reset they’ve got another thing coming. As someone who buys their phone outright, Samsung better fixes whatever toss they’ve screwed up or I’ll be demanding a refund