Related
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

beta 15.15 out

derek87
over 2 years ago

This update, version 15.15, is a Release Candidate. "Release Candidate" means that this exact software version is planned to “Go Live” as a public update as long as no critical issues are observed. All copies of version 15.15 will be identical, so there are no differences in functionality whether you install version 15.15 as a Public Release Candidate or wait for the update to be a Live public update.

As a member of the Public Beta program, this update will be automatically delivered to your watch through GCM. Please note that GCM will check for an available update once every 24 hours, and after that it may take several hours for the update to finish transferring and be available on your watch to install.

Changes since version 15.12

  • Adds support for accessing a cycling event’s associated power guide from the race widget.
  • Improves the wording used for cycling daily suggested workouts.
  • Adds support for showing the course point name on course point toasts.
  • Adds support for the battery life remaining in days field on CIQ watch faces.
  • Fixes an issue where icons were not displayed properly on watch faces with white backgrounds.
  • Fixes an issue that could cause a flat line graph for heat acclimation.
  • Fixes an issue that could cause sleep data and HRV not to be calculated overnight.
  • Fixes an issue where the map orientation could change from track up to north up when panning or zooming.
  • Fixes an issue that could cause segments not to be ended correctly.
  • Fixes an issue where the calendar glance could show an all-day event as scheduled one day ahead of the correct day.
  • Fixes an issue where images used on the Virtual Partner page were cut off.
  • Fixes an issue that could cause the stopwatch not to sound an alert even though alert tones are enabled.
  • Fixes other minor issues.
  • 0 over 2 years ago in reply to hassan987

    Hi 

    It is correct it is a "feature" and not a bug.

    The reason is not related to how the Garmin Watch or the Connect app  works - but how WhatsApp shows a Notification on Android phones. On an iPhone a Notification for at call is a one-line-message split into two lines automatically.

    On Android phones it depends of the phone vendors UI. WhatsApp have "hardcoded" phone model numbers/Android OS to send the notifications to a locked/unlocked screen and sometimes that could be with a special character for that specific UI that Connect does not know about.

    A solution can be made i the Android Connect app (to remove all characters in a specific range - but the result could be more display errors on the watch).

    The proper solution would be that the Vendor of the UI on notifications follow standard notification rules (which WhatsApp does not).

    If you have more example then bring them on.


  • 0 over 2 years ago in reply to parentoft

    This happens with all calls other than cell. It's not specific to WhatsApp.

    Another example is already quoted above. Are you a Garmin employee?

  • 0 over 2 years ago in reply to hassan987

    No, I am not an garmin employee!

    If the same happens with other apps that are not normal calls (it could be Skype, Teams etc) - the reason is still how the Vendor of the UI adds notifications.

    The Main problem is number of charactors. Lets say that your display is 40 characters wide and the notification is 52. The Notification then needs to be spilt into two lines. The OS itselv will do a hard spilt 40 characters in line one and 12 in line two. The problem with that is words will be split wrongly. 

    Example:

    "It is hard to be a developer in this amazing world" will be split into two lines:

    1) It is hard to be a developer in this ama
    2) zing world

    So as a Developer I would change the notification in code to

    1) It is hard to be a developer in this
    2) amazing world

    If it is done wrongly it is actually two notifications and not one - and that raises the problem.


    (I have been struggling with exact same problem when I worked as a developer at Microsoft).

  • 0 over 2 years ago in reply to parentoft

    The notification is not divided. There are 2 separate individual notifications.

     

    The empty one obscures the one that's not empty. 

    P.S. I'm a computer engineer as well. 

  • 0 over 2 years ago in reply to parentoft

    here's a short clip hope you can diagnose. Quick replies are also broken.

    need your help.