Music app does not react to bluetooth headset buttons

Bug #1437483 reported by Akos Mate
44
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Ubuntu Music App
Triaged
Medium
Unassigned

Bug Description

On desktop, the headset uses AVRCP profile for the buttons, and sends XF86AudioNext, XF86AudioPrev, XF86AudioPlay, XF86AudioPause keystrokes, the last two are sent alternately by the play/pause button. XF86AudioPlay and XF86AudioPause should both be treated as a single play/pause button.

Related branches

Revision history for this message
Akos Mate (mateakos1) wrote :

The device is BQ Aquaris E4.5 Ubuntu Edition.

tags: added: aquaris-e4.5
Revision history for this message
Victor Thompson (vthompson) wrote :

Could you try using the attached click package?

Revision history for this message
Akos Mate (mateakos1) wrote :

It gives this error:
Cannot install com.ubuntu.music_2.0.851_all.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed.

Revision history for this message
Victor Thompson (vthompson) wrote :

Can you try to install the click package on the device using "pkcon install-local --allow-untrusted com.ubuntu.music_2.0.851_all.click"?

Revision history for this message
Akos Mate (mateakos1) wrote :

This way it installed, but now the music player does not show the artists, albums, etc, it's just empty.

Revision history for this message
Akos Mate (mateakos1) wrote :

After uninstalling and reinstalling, it now works like originally, but the remote control with bluetooth does not.

Revision history for this message
Victor Thompson (vthompson) wrote :

Thanks, Akos! The bluetooth media keys are certainly something we have on our roadmap to get working with the app.

Changed in music-app:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Akos Mate (mateakos1) wrote :

How can I determine that the headset connected with both A2DP and AVRCP profiles, or just with A2DP?

Revision history for this message
Akos Mate (mateakos1) wrote :

It shows up as /dev/input/event5, so it definitely connects with both profiles.

Revision history for this message
Gorsh (copateymandameunmail) wrote :

I can confirm this too with Samsung HS6000 headset; I'm here and willing to help in any way to make this work.

Revision history for this message
Akos Mate (mateakos1) wrote :

Half a year passed. Any progress? (Still doesn't work for me)

Revision history for this message
Andrew Hayzen (ahayzen) wrote :

We are currently working with the platform on background-playlist support [0], this allows for the indicator-sound and other parts of the platform to control the music-app's queue. Therefore once this support lands it will be possible for mediakeys (and bluetooth controls) to correctly control the music-app.

Sorry its taken us such a long time, its a rather large item with work needed upstream to the music-app as well.

0 - https://code.launchpad.net/~music-app-dev/music-app/media-hub-bg-playlists-rework

Revision history for this message
Alexey Kulik (doctor-rover) wrote :

Possible duplicate of Bug #1398193 - The bluetooth headset can not control the media playback

Revision history for this message
Akos Mate (mateakos1) wrote :

More than one and a half year passed, and this basic functionality is still not working not even on the very first phone released officially with ubuntu. I feel like canonical has no quality control at all :(
Is anybody working on this?

Revision history for this message
Andrew Hayzen (ahayzen) wrote :

The music app transitioned to using "background playlists" a while back, which allows for the system to control the playback/next/previous etc. So all that is left is for the system side, media-hub and bluez, to be linked so that when a bluetooth headset button is pressed it instructs media-hub to perform the action. The tracking of this particular feature is now in bug 1398193, therefore I am marking this bug as a duplicate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.