Ask / Submit
11

Regression [2.1.1]: bluetooth controls in other media players

asked 2017-08-31 09:58:22 +0300

Federico gravatar image

updated 2017-09-01 15:45:11 +0300

jovirkku gravatar image

After the upgrade, the buttons in my Bluetooth headset (e.g. play/stop) stopped working with Daedalus (note that media keys support in Daedalus was added in 2015, but the last time I checked the version on the Jolla Store was not updated yet).

Audio is still routed correctly through the device, and the buttons still work with Jolla Media Player. Other users in the comments reported that the buttons do not work also with other players other than the jolla-mediaplayer, so it looks like this is an issue with a changed API.

For reference, in Daedalus the Bluetooth controls are handled by a very short piece of QML code that uses the Sailfish.Media library API.

Any hints to which API change could have caused it and how to update the code?

edit retag flag offensive close delete

Comments

I noticed that play and stop music stopped working as well with a sony 1000-MDRX at least with Quasarmx (did not take time yet to test with the standard music player).

pat_o ( 2017-08-31 11:04:37 +0300 )edit

Never Worked for me and my Sony radio

pawel ( 2017-08-31 13:28:01 +0300 )edit

@pawel what never worked for you? Bluetooth buttons in general? Do they work with jolla-mediaplayer?

Federico ( 2017-08-31 13:32:36 +0300 )edit

You should contact the original author of the app, either through Jolla Store comments or on Openrepos or both!

Author: djselbeck

Openrepos: https://openrepos.net/content/djselbeck/daedalus-musicplayer

Edz ( 2017-08-31 15:41:30 +0300 )edit

Yes, Buttons in General. I Thing with Mediaplayer too

pawel ( 2017-08-31 18:49:27 +0300 )edit

6 Answers

Sort by » oldest newest most voted
3

answered 2017-09-01 13:21:51 +0300

r0kk3rz gravatar image

updated 2017-09-02 20:37:28 +0300

Which device? Jolla Phone and Jolla C now use different Bluez versions and so I expect this is going to be some kind of Bluez5 change.

For proper integration with the system it should be listening for both MPRISv2 control as well as key press style controls, does it show up with the lock screen controls? do they work?

EDIT: Looks like Bluez5 does implement MPRISv2 controls but its a bit picky about the implementation of the interface, i will continue to investigate and document my findings here: https://together.jolla.com/question/128886/bluetooth-avrcp-mprisv2-controls/ . So this is up to the developer of the app to get it right.

edit flag offensive delete publish link more

Comments

Jolla C for me, so Bluez5. The lock screen controls work with Daedalus, and they also worked before the Github patch linked in the question (which only adds the Bluetooth part).

Federico ( 2017-09-01 13:35:54 +0300 )edit

then in which case Jolla needs to configure Bluez5 to work properly, afaik no code changes will be required for the music player at all.

r0kk3rz ( 2017-09-01 14:08:09 +0300 )edit

This is for Jolla C, sorry for not being clearer earlier but indeed this is clearly affected by the transition to Bluez 5. That being said, jolla-player seems not affected (in my case) but only using QuasarMX so there is maybe something to change in the application side? I will try and contact the developper. (btw there is another bug I face, see https://together.jolla.com/question/166687/regression-211-bluez-5-bluetooth-audio-route-not-activated-at-first/)

pat_o ( 2017-09-01 16:11:43 +0300 )edit

Media control on android app is not working anymore... In Spotify for instance

louisbob ( 2017-09-11 23:52:36 +0300 )edit
3

answered 2018-05-10 13:53:56 +0300

louisbob gravatar image

Hey Sailors,

This MUST HAVE feature has still not been fixed. What can I do to awake Jolla from this issue?

edit flag offensive delete publish link more

Comments

2

Pray and then pray some more ;)

Edz ( 2018-05-10 14:14:55 +0300 )edit
2

answered 2017-09-01 20:12:48 +0300

Federico gravatar image

While we wait for Jolla to fix bluez5, a workaround is removing the whole bluez5 stack and replacing it with the old bluez4:

[root@Sailfish ~]# pkcon remove bluez5
[...]
The following packages have to be removed:
 bluez5-5.43+git5.1-1.6.2.armv7hl   Bluetooth daemon
 bluez5-libs-5.43+git5.1-1.6.2.armv7hl  Bluetooth (bluez5) library
 bluez5-obexd-5.43+git5.1-1.6.2.armv7hl OBEX server (bluez5)
 droid-config-l500d-bluez5-0.10.5.5-10.112.1.jolla.armv7hl  l500d packages for BlueZ 5
 kf5bluezqt-bluez5-5.24.0+git12-1.4.1.armv7hl   KF5BluezQt - Qt wrapper for BlueZ 5 DBus API
 kf5bluezqt-bluez5-declarative-5.24.0+git12-1.4.1.armv7hl   Declarative plugin for kf5bluezqt
Proceed with changes? [N/y] y
[...]
[root@Sailfish ~]# pkcon install bluez bluez-libs obexd droid-config-l500d-bluez4 kf5bluezqt-bluez4 kf5bluezqt-bluez4-declarative
edit flag offensive delete publish link more

Comments

Work like a charm for getting QasarMX media control back to work. Unfortunately, Android app doesn't seems to be fixed this way...

louisbob ( 2017-09-11 23:59:55 +0300 )edit

With 2.1.4.14 on JollaC, Bluetooth does not start anymore after this downgrade.

feodoran ( 2018-04-17 23:00:41 +0300 )edit
2

answered 2017-10-27 23:46:46 +0300

louisbob gravatar image

I do have the same issue with Android App (like Spotify). Can Jolla team fix this issue with QuasarMX and android apps such as Spotify? I tried on a sailfish X today and there is the same problem.

We need a fix for that! Thanks!

edit flag offensive delete publish link more
1

answered 2018-05-25 01:27:52 +0300

deloptes gravatar image

updated 2018-05-30 00:41:21 +0300

I think very few understand that it is not the job of Jolla to update 3rd party applications. The interface of bluez5 changed massively and all application utilizing the interface should follow.

The problem I have with Jolla regarding bluez5 is, that they do not bother to provide compatible and smooth transition from bluez4 to bluez5. In my case installing bluez4 was not possible and did not work even when enforced - I spent hours on that without success.

I can not confirm this as I don't have a BT headset - I would never put anything close to my head for longer than 5 min that emits any kind of waves, radiation or whatever, but I have found out while playing a lot with BT and pulseaudio lately, that it helps to remove ~/.pulse (well you can rename the directory) and reboot.

Now PA would recreate the directory and setup device configurations again. (I don't recall if it was necessary to pair again, but I think no). Perhaps you try this and see if it helps.

Read this regarding BT - very brief and amusing article http://www.lightofdawn.org/blog/?viewDetailed=00031

regards

edit flag offensive delete publish link more

Comments

1

I am just not so sure, that it really is the applications doing something wrong. Because while running mpris-proxythe keys suddenly work (see https://together.jolla.com/question/128886/bluetooth-avrcp-mprisv2-controls/). Even if it really is not the job/fault of Jolla, it would be nice to have some statement saying so, because everything else is just speculation.

feodoran ( 2018-05-27 16:59:45 +0300 )edit

You are right - that gave me brain food and I updated the answer.

I just read this article once again after reading it couple of years ago http://www.lightofdawn.org/blog/?viewDetailed=00031

deloptes ( 2018-05-30 00:34:37 +0300 )edit
1

I'm not asking for Jolla to update Daedalus. It would be enough for me to have an answer with a pointer to some documentation about this Sailfish.Media module, and a hint to what changed in its interface regarding Bluez5. For instance,

Federico ( 2018-05-31 20:20:00 +0300 )edit

Yes it would have been nice at least - cause I wouldn't have spent 350,- for Sailfish X. I would have rather bought Intex Aquafish for 200,- and would have working BT in my car.

Have a look here BlueZ 5 API introduction and porting guide

It is indeed a lot of effort to port and even more if you want to support bluez4 and bluez5 at the same time

regards

deloptes ( 2018-06-01 13:09:44 +0300 )edit
0

answered 2018-06-01 23:26:10 +0300

mase gravatar image

Is AVRCP generally routed to Android apps? I don't think so. I tried Antennapod which has fine AVRCP support in Android, but no reaction in SFOS. And yes, bt control is a must have feature. Not only for headsets, also for in-car handsfree. It should be routed either to the running player, or the one in focus.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
8 followers

Stats

Asked: 2017-08-31 09:58:22 +0300

Seen: 991 times

Last updated: Jun 01