search

arkq / bluez-alsa

Bluetooth Audio ALSA Backend
MIT License
864 stars 189 forks source link

Buttons not working during callback recording #683

Closed jeffersonchua closed 6 months ago

jeffersonchua commented 9 months ago

Problem

I’ve written a python program pyaudio callback with both input and output enabled, and I can hear and speak at the same time, but the bottons on the headsets are not detected while the callback is running. Is this a bug?

Buttons work fine after recording stopped. I’m listening to evdev.Inputdevice() read_loop() for that in a separate process.

Using latest version of bluealsa git.

borine commented 6 months ago

You give very little information on which anyone can begin to investigate, but as a random guess perhaps the "buttons" (you do not even say what function you expect each button to perform) send AVRCP profile messages, you have connected the HFP or HSP profile, and the headset disables AVRCP when HFP or HSP are active. Perhaps the headset instead uses the buttons to send HFP or HSP rfcomm messages when using HFP or HSP, in which case Bluez does not generate evdev events, but BlueALSA will handle the rfcomm volume change messages but ignore the call handling ones.

jeffersonchua commented 6 months ago

You give very little information on which anyone can begin to investigate, but as a random guess perhaps the "buttons" (you do not even say what function you expect each button to perform) send AVRCP profile messages, you have connected the HFP or HSP profile, and the headset disables AVRCP when HFP or HSP are active. Perhaps the headset instead uses the buttons to send HFP or HSP rfcomm messages when using HFP or HSP, in which case Bluez does not generate evdev events, but BlueALSA will handle the rfcomm volume change messages but ignore the call handling ones.

My bad. Buttons refers the Play/Stop which as you mentioned "disables AVRCP when HFP or HSP are active". So, that's why I'm not seeing the events.

My best., Jeff

On Mon, Apr 29, 2024 at 7:14 PM borine @.***> wrote:

You give very little information on which anyone can begin to investigate, but as a random guess perhaps the "buttons" (you do not even say what function you expect each button to perform) send AVRCP profile messages, you have connected the HFP or HSP profile, and the headset disables AVRCP when HFP or HSP are active. Perhaps the headset instead uses the buttons to send HFP or HSP rfcomm messages when using HFP or HSP, in which case Bluez does not generate evdev events, but BlueALSA will handle the rfcomm volume change messages but ignore the call handling ones.

— Reply to this email directly, view it on GitHub https://github.com/arkq/bluez-alsa/issues/683#issuecomment-2082450391, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3RVP52XQJX54QHTX4XAITY7YTPZAVCNFSM6AAAAABDORLM4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGQ2TAMZZGE . You are receiving this because you authored the thread.Message ID: @.***>