[Feature request] Enable automatic start of mpris-proxy

asked 2019-04-01 12:57:19 +0300

Giacomo Di Giacomo gravatar image

Expanding on the question https://together.jolla.com/question/174156/bug-bluetooth-media-control-with-android-apps-and-native-apps/, I wish to explicitly request inclusion of a switch to enable start of mpris-proxy at system startup without having to modify system files which can lead to unpredictable results in case of system updates.

edit retag flag offensive close delete

Comments

1

I believe it is being worked on by @abranson. See https://git.merproject.org/mer-core/bluez5/merge_requests/37

pat_o ( 2019-04-01 14:52:05 +0300 )edit

Thank you!

louisbob ( 2019-04-01 22:18:11 +0300 )edit

I've asked Andrew about this and he was nice enough to give me an update on that merge request.

In short, we'll have to keep waiting, because it doesn't work well: the trouble is that the bluez mpris-proxy solution isn't really good enough. it breaks on flight mode, and a daemon like that shouldn't be running all the time when it applies to such a rare situation. it's likely to get solved in a different way, but I don't know when.

cheers!

velox ( 2019-12-02 10:37:42 +0300 )edit

Maybe it's a rare situation for his pattern of use, but for mine it's different. I have a shell constantly open with mpris-proxy launched in background. It could be left as a user-selectable option.

Giacomo Di Giacomo ( 2019-12-02 11:01:48 +0300 )edit
1

Having a terminal open all the time for this sounded so ugly that I made a quick "launcher application" in my lunch break. https://openrepos.net/content/velox/bttons I hope it works, didn't have much time to test. You should be able to close that window then. Cheers!

velox ( 2019-12-02 18:02:39 +0300 )edit