MPRIS controls don't reflect the current player state

[Jim Hodapp]

The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect:

1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect.

2. The play button should show when media-hub reports that the current player is stopped or pause.

3. The pause button should show instead of the play button when media-hub reports that the current player is playing.

[John McAleely (john.mcaleely)]

I understand the fixes for this bug belong in silo 55 for testing with the media-hub changes

[John McAleely (john.mcaleely)]

This bug blocks bug #1373313 from landing.

[Xavi Garcia (xavi-garcia-mena)]

Hi,

I've installed silo 055 and check the result with the new code of the indicator-sound from branch:
lp:~xavi-garcia-mena/indicator-sound/next-play-prev-buttons-bug-1373313

The code instead of setting the MPRIS controls by default reads the CanPlay, CanGoNext and CanGoPrevous properties.

The MPRIS player always return true to CanPlay, but returns always false for CanGoNext and CanGoPrevious, the result is obviously that the play control is the only only one showing as active.

I've also noticed that the player is not emiting any signal when the properties change.
The indicator-sound is subscribed to the PropertiesChanged signal with the following code:

/* Connecting to GDBusProxy's "g-properties-changed" signal here, because vala's dbus objects don't
    emit notify signals */
var gproxy = this.proxy as DBusProxy;
gproxy.g_properties_changed.connect (this.proxy_properties_changed);

To debug the code I'm listing all the properties that changed.
The method proxy_properties_changed is never called.

This works fine on the desktop, but not on the phone with silo 55.

Should we register to the signal in a different way? or should we consider the above issues as a bug?

In relation with the play/pause button: the desktop changes from the play to the pause button correctly with the current indicator-sound code, but not on the phone. (could this be a bug in the UI?)

We can maybe set a different value for the play property in the indicator menu, but as I said the PropertiesChanged signal is not working...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alejandro J. Cura (alecu)]

This needs to land together with the MPRIS silo, and it has been postponed to OTA-8.

[Jouni Helminen (jounihelminen)]

Does't look like there is design input required. Let me know if otherwise