This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bug when going back to music widget

After selecting the music widget and making some selections, when you press back and go to the widget initial screen, the characters of the songs appear incorrectly. It should be fixed immediately.

  • Please take a short video of this and post it. It's much easier for people to see the issue (including Garmin) an then you have a better chance of a fix. Also before you post, try rebooting the watch to see if that cures it 

    HTH

    Paul

  • I have same issue.  I get a lot of <?> type characters until I close the widget and open it back up.

  • Exactly the same happens to me.

  • I contacted Garmin support with a video of the bug. I'm posting it here too, just for reference. I don't know why it's upside down, lol.

    it should be an easy fix, it just looks like the character encoding is lost when switching between those two screens. 

  • Just so I understand, which screens this is? It looks like you are going from the screen in the widget loop and then pressing start which is taking you to the music app (with the controls on), right? I see you have no album art. Is the file an mp3? Does it happen with all files or only some? Hopefully Garmin support have asked you all this. I’m not seeing it

  • This is the music controls widget. I'm playing music on my phone and controlling with the watch.  When i click back to the widget I get the messed up screen. It happens 100% of the time. If I click to a different widget and back it looks OK.  Garmin told me to restart hte watch blah blah blah and now they are waiting for the team to get back on Tuesday.

  • thanks for the extra info, I was working with music on the watch, not from the phone. The more info the better, make sure all these points are raised to Garmin so they can replicate.

  • Garmin was able to recreate the issue and a case has been entered. I see there's already a new FW version in beta, but I don't know if this got in soon enough to get fixed in that rev.

  • This is fixed in the 2.82 beta.