• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Normal Normal
    • ListenBrainz Android
    • None
    • Device: Samsung Galaxy A40
      Android version: 11
      App Version: 2.4.0

      Accidentally had LB Android and PanoScrobbler both submit listens at the same time, but noticed that the submitted listened_at times between these two differred by several minutes. in fact, the times didn't really differ, but the tracks these times were associated with: LB android was submitting the tracks using the listened_at timestamps that PanoScrobbler had used for the previous track.

      see e.g. here: PanoScrobbloer submitted "Cheerleader" at 12:39 in my timezone but LB Android submitted the same song at 12:42.
      This is exactly the timestamp that PanoScrobbler submitted for the next song, "Break Your Heart".

      Testing out which timestamp is actually correct i discovered that PanoScrobbler is right and LB is somehow lacking behind one track.

      This was observed on the current version 2.4.0.

      Screenshot of the mentioned example:

          [MOBILE-174] Wrong listened_at submitted

          MaxEtMoritz added a comment -

          Seems good now.
          Since the issue of LB Android submitting the PanoScrobbler notification can finally be fixed by turning off the "Auto-submit new players" option, i was able to evaluate this.
          Now i only see one listening event per track, submitted by LB Android -> the listen timestamp seems to match the one by PanoScrobbler and the LB server is de-duping the listens.

          Closing the issue as resolved now.

          MaxEtMoritz added a comment - Seems good now. Since the issue of LB Android submitting the PanoScrobbler notification can finally be fixed by turning off the "Auto-submit new players" option, i was able to evaluate this. Now i only see one listening event per track, submitted by LB Android -> the listen timestamp seems to match the one by PanoScrobbler and the LB server is de-duping the listens. Closing the issue as resolved now.

          Jasjeet added a comment -

          Please try version 2.4.1 (in Beta)

          Jasjeet added a comment - Please try version 2.4.1 (in Beta)

          Jasjeet added a comment -

          Thankyou for reporting! We are looking into this.

          Jasjeet added a comment - Thankyou for reporting! We are looking into this.

            Unassigned Unassigned
            MaxEtMoritz MaxEtMoritz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package