Broken song current length when re-entering music app.

[ilutchenko]

Pinetime: 0.9.0-dev Gadgetbridge: 0.48 Android: 10

If you start playing from music app, then click side button and enter music display again, the current playing time will be wrong. And it is stays still. If display will be turned off with timeout and turned on with button, the time will be shown properly.

It looks like this time the same as uptime:

[JF002]

From your description, the issue might come from here : When you quit and re-run the Music app, the variable lastIncrement is probably initialized to 0, which would explain why the display time corresponds to the uptime of the device.

[Avamander]

I'll try to submit a patch for the next release.

[pfeerick]

A possible secondary behaviour is one where the elapsed time stays at 00:00 until you pause the song, either from the watchapp or from the phone. As soon as you do this it 'catches up' and is correct from then onwards. Pinetime: 0.9.0-dev and Gadgetbridge: 0.48 also.

[Avamander]

@pfeerick No, that specifically is a limitation of your music app, it simply doesn't send the needed information until some event is triggered.

[pfeerick]

Interesting that you would just jump to the conclusion that it it must be a limitation of the music app, without asking which app it is, and do I have any other devices to compare it to. I get the same behaviour with VLC and Spotify, but not if I use my Pebble watch. It updates perfectly, whereas Gadgetbridge + the music app do not. Nor does changed track progression through seeking get detected (which it does on the Pebble). Perhaps it's a limitation in Gadgetbridge, since I'm using the Pebble app with that?

[Avamander]

@pfeerick because I know it's an universal limitation, the app doesn't matter. There's no way for a music app to know it needs to re-broadcast the track info intent.

Seeking updates the progress of the song assuming your music app sends the necessary intent.

[pfeerick]

Perhaps you didn't read my last comment fully. I am using two watches - infintime and pebble (classic) and one works fine with two different music apps, and the other doesn't.

• Infinitime watch Music app - does not update when seeking, and often when starting playback from it will not start counting elapsed time, unless you pause/play again, from either the phone or the watch. With Gadgetbridge, and Spofity or VLC

• Pepple watch Music app - DOES update when seeking, and when starting from it - no pause/play required. With Pebble app, Spotify or VLC.

Thus it isn't the music app, because the Pebble would have the same problem, which it does not. If it were the vendor bundled music app, I would agree with you, because it does have issues generally, for both, but this is not what is being spoken about.

[Avamander]

@pfeerick perhaps you haven't seen this video https://youtu.be/YvER1JsuPOg?t=26 - progress is updated on seek assuming your player sends the information. It uses the very much the same code path for receiving/sending events/intents as Pebbles do.

Thus it is something about your setup that's weird.

[pfeerick]

Thank you, I had seen that video, but it reminded me to try in PowerAmp as well, to see if that behaves differently, which it does.

So, the Infinitime+Gadgetbridge+Poweramp combo works flawlessly from that I can tell, but Infintime+Gadgetbridge+[VLC or Spotify] does not. But Pebble+Pebble app+[PowerAmp or VLC or Spotify] also works perfectly, suggesting the issue may be in the companion/bridging app, not the music app on the phone.

The Pebble watch music app would not be able to update to show the seek if the information was NOT being made available to the companion app. Perhaps apps like VLC and Spotify are not presenting it to GadgetBridge in a form it wants (or there is yet another bug in it).

[JF002]

If I understand correctly, this is more an issue on the companion app (or music app or smartphone or ...) side than on InfiniTime side?

[pfeerick]

Yes, these last few comments have come down to being issues with the companion apps (specifically: Gadgetbridge not sending seek updates when the Pebble app does, with certain music apps), not InfiniTime. The first three are still relevant as the issue hasn't been patched yet.

[JF002]

So we still have to try to fix this : https://github.com/JF002/Pinetime/issues/127#issuecomment-723422720 :)