Bluetooth playback controls don't work

[yodies]

I've been chalking this up to Oreo, but I haven't been able to find any other Oreo phone with this issue.  Both my phone and my BT headphones have playback control buttons.  I've never had an issue before with other phones.  But my XZ1 Compact does not respond to pause, play last, or play next buttons on my headset or in my car.  Prior to the last system update, it would work one time after a reboot and break on the next time it paired.  Now it just doesn't work.

Any way to investigate this?

[Snapples]

Bose QC35 here.

I notice similar behaviour.

The most annoying part for me is actually that I can't control my phone's volume anymore with the Headphone's volume control buttons.

Worked fine on my Galaxy S5.

[Voyteck]

Same problem for me with Sony WH-1000X2... The sound is great, but the controls does not work at all...

[matseraf]

I think that a lot of bluetooth problems should be solved with november security update: https://source.android.com/security/bulletin/pixel/2017-11-01

Let's wait and see.

[semelko]

To me it's fixed after phone reboot. Not a graceful solution but better than nothing. 

[SunnyEricsson]

this seems intermittent and random. SBH80 couldn't use bt buttons most of the time, though once in a while it was OK.  

Tried the new bt headsets in the sony showroom wi-h700 and 1000 both buttons work fine.

xz1 compact.

[TheDukeofPrunes]

Yep, I have exactly the same problem with my Sony car stereo and XZ1. After a reboot it will work fine, controls respond and display shows what it should - but connecting without a reboot something soewhere seems to have crashed and I have to control the audio on the phone.

Also - smartlock doesn't work at all

[yodies]

SmartLock you can fix by disabling it and re-enabling it.  I found a how-to on a troubleshooting article I can't find right now.  You have to disable SmartLock, restart, and then re-enable it.

[Strampke]

The problem with Bose QC35 is known. You can Google for it and find the answer that is a Google initiated problem.

The other thing is that there seems to be another bluetooth problem which can be resolved easily.

Take a look over here.

Report back please if it brought a relief.